Define System Elements
Establish the foundational system hierarchy by creating system elements at multiple levels.
Create System Hierarchy
Build a multi-level decomposition from system down through subsystems and components.
Allocate Functions to Elements
Map functional requirements to physical system elements for design traceability.
Use System Structure Navigator
Visualize and navigate your complete system hierarchy with interactive diagrams.
Key Concepts
System structure defines the architecture and decomposition strategy for your product. In TestAuto2 — Automotive Safety Solution, system structure provides the foundation for:- Traceability: Linking requirements, functions, and characteristics to physical elements
- FMEA Organization: Grouping failure modes by system element (SFMEA, DFMEA, PFMEA)
- Risk Analysis: Allocating safety goals and ASIL ratings to system components
- Design Verification: Mapping verification activities to system elements
Common Workflow
When to Use Each Guide
| Task | Guide |
|---|---|
| Create new system elements at any level | Define System Elements |
| Establish parent-child hierarchy and decomposition | Create System Hierarchy |
| Link functions to specific system elements | Allocate Functions to Elements |
| Visualize system structure and navigate hierarchy | Use System Structure Navigator |
Related Topics
- Create System Requirements — Define system-level functional needs
- Create Design Requirements — Allocate system reqs to design specs
- Create System FMEA Document — Failure analysis per system element
- Use Characteristics PowerSheet — Design characteristics linked to elements
- RTM Domain Model — System element entity configuration