Quick Navigation
Create Requirements
Learn how to author customer, system, and design-level requirements that form the basis of your V-Model traceability.
Refine Across Levels
Understand how to decompose high-level requirements into subsystem and design requirements while maintaining traceability.
Classify Requirements
Mark requirements as Special Characteristics (SC) or Critical Characteristics (CC) for safety-critical features.
Use PowerSheet
Leverage the Requirements PowerSheet to view, edit, and manage your entire requirements hierarchy in a single spreadsheet view.
Why Requirements Management Matters
In functional safety development, requirements form the left side of the V-Model. Every requirement must be:- Traceable — linked to customer needs, design specifications, and verification tests
- Complete — refined to design level with measurable criteria
- Classified — marked as SC/CC when they affect safety or quality
- Verified — connected to test cases that validate implementation
Workflow Overview
Management Topics
Create Customer Requirements — Author top-level requirements that capture user needs and market features. Learn how to structure and document customer-facing specifications. Create System Requirements — Decompose customer requirements into system-level capabilities. Establish traceability links to parent requirements and allocate functionality to subsystems. Create Design Requirements — Translate system specifications into design constraints for components and subsystems. Define measurable criteria that enable verification. Refine Requirements Across Levels — Understand the refinement chain from customer to design level. Learn when to split, merge, or rewrite requirements during decomposition. Classify Requirements (SC/CC) — Mark requirements as Special Characteristics or Critical Characteristics when they impact product safety or quality. Enable visual identification in dashboards and reports. Use Requirements PowerSheet — Leverage the spreadsheet-style interface to view your entire requirements hierarchy, create bulk links, and perform gap analysis.Key Integration Points
Requirements management in TestAuto2 follows IATF 16949 and APQP (Advanced Product Quality Planning) guidelines. See IATF 16949 and APQP for detailed methodology information.
Next Steps: Start with Create Customer Requirements to begin building your requirements hierarchy, or jump to Use Requirements PowerSheet if you’re working with an existing project.