Quick Navigation
Traceability Sheets
RTM (Requirements Traceability Matrix) configurations for bidirectional linking across system, design, and component hierarchies.
Data Collection Sheets
Characteristic, process step, and use step configurations for capturing design and process data.
Verification Sheets
Test traceability and verification evidence sheets aligned to system, design, and subsystem levels.
Function and Hierarchy Sheets
System decomposition and functional allocation sheets for system structure management.
Key Features
- 11 PowerSheet configurations supporting traceability, characteristics, functions, verification, and use case management
- Hierarchical data models with multi-level expansion paths (system → subsystem → component; requirement → test)
- Dynamic column grouping with conditional visibility and custom renderers for SC/CC classification, ASIL levels, and risk indicators
- Progressive disclosure views showing aggregated summaries, detailed analysis, and traceability chains
- Bi-directional traceability linking requirements across V-model stages: validation ← system ← design ← verification
- Work item expansion enabling in-place navigation through document hierarchies without page navigation
- Custom formatters for color-coded badges, formula-based calculations, and linked evidence rendering
- Integration with risksheet analysis cross-referencing FMEA, Control Plans, and risk controls
PowerSheet Configurations Overview
| Sheet | Primary Purpose | Data Model | Typical Users |
|---|---|---|---|
| Whole RTM | System-level bidirectional traceability (customer → system → design → verification) | Requirement + Test + Design | PM, Requirements Lead |
| Component RTM | Component-level traceability and cross-component linking | Design Requirement + Test + Characteristic | Design Lead, Component Owner |
| System Verification | System-level test coverage mapping | System Requirement ← Verification Test Case | V&V Lead, Test Manager |
| Design Verification | Design requirement test coverage and traceability | Design Requirement ← Verification Test Case | Design Engineer, V&V Engineer |
| Subsystem Verification | Subsystem functional and integration testing | Subsystem Requirement ← Test Case | Subsystem Lead, Test Engineer |
| Characteristics | Design parameter targets, tolerances, and SC/CC classification | Characteristic + Failure Mode links | Design Engineer, FMEA Analyst |
| Component Characteristics | Per-component design characteristics and test specifications | Characteristic (filtered by component) | Design Engineer, Supplier |
| Subsystem Functions | Functional decomposition and allocation to system elements | Function + System Element hierarchy | Architecture Lead, Design Lead |
| Use Steps | Operational scenario definitions and use case documentation | Use Step + Operational Phase + Hazard links | Safety Engineer, Systems Engineer |
| Process Steps | Manufacturing and assembly process definition for PFMEA | Process Step + PFMEA Failure Mode links | Manufacturing Engineer, Quality Engineer |
| User Need Validation | Customer validation traceability and acceptance criteria | User Need ← Validation Test Case | Product Manager, Validation Lead |
Configuration Architecture
| Configuration | Purpose | Work Item Types |
|---|---|---|
whole-rtm.yaml | Full RTM traceability view | All types across V-Model |
system-verification.yaml | System-level V&V | System Requirements, System Tests |
subsystem-verification.yaml | Subsystem-level V&V | Subsystem Requirements, Subsystem Tests |
design-verification.yaml | Design-level V&V | Design Requirements, Design Tests |
characteristics.yaml | Characteristic management | Characteristics, Special Characteristics |
component-characteristics.yaml | Component-level characteristics | Components, Characteristics |
process-steps.yaml | Manufacturing process | Process Steps, Control Plans |
use-steps.yaml | Use/misuse analysis | Use Steps, Hazardous Situations |
user-need-validation.yaml | User need validation | User Needs, Validation Evidence |
PowerSheet configurations reference custom fields, enumerations, and link roles defined in the RTM domain model. Changes to work item types or fields require consistency checking via the
consistency-check skill before deploying to production.