trace requirements to architecture, design, code, and tests
requirements traceability connects models, tests, and code with requirement definitions to help manage change and reduce waste in the design life cycle.
traceability analysis is required for compliance with industry standards such as iso 26262 and iec 61508 in the automotive industry, do-178c in commercial aviation, en 50128 for railways, and iec 62304 in the medical industry, as well as general software development standards such as cmmi and spice.
common tasks for developers working to achieve requirements traceability for simulink®, system composer™, and stateflow® include:
- viewing the requirement details within the development environment where they are being implemented
- generating traceability reports that include design, test, and requirement information in a single document
- identifying the design and tests that are linked to requirements and navigating to external requirements
- understanding the impact of a requirement change on the design and tests
the simulink environment provides capabilities for efficient linking, analysis, and reporting of requirements traceability. for details, see simulink, system composer, and requirements toolbox™.
examples and how to
user stories
software reference
see also: formal verification, requirements toolbox, model-based testing, simulink design verifier,