F8_SRQT System Requirement Traceability Viewpoint
| Domain | Aspect | Maturity |
|---|---|---|
| Functional | Traceability & Mapping |  released |
Example
Purpose
The System Requirement Traceability Viewpoint specifies for every System Requirement the traceability to the functional domain level
- System Use Case
- System Capability
- System Context Definition
- System Context Exchange
- System Context Interaction
- System Process
- System State
Applicability
The System Requirement Traceability Viewpoint supports the activities included in the “System Requirements Definition Process” of the INCOSE SYSTEMS ENGINEERING HANDBOOK 2023 [§2.3.5.3] and contributes to the System Requirements Traceability. The System Requirement Traceability Viewpoint also contributes to the System Requirements Verification and Traceability Matrix (RVTM).
Presentation
A dependency matrix featuring relationships for every System Requirement to the functional domain level
- System Use Case
- System Capability
- System Context Definition
- System Context Exchange
- System Context Interaction
- System Process
- System State
Stakeholder
Concern
- What is the rationale for a system requirement?
- Which System Requirements are derived from Stakeholder Requirements?
- Which system function is addressed by a system requirement?
- Which system interface is addressed by a system requirement?
Profile Model Reference
The following Stereotypes / Model Elements are used in the Viewpoint:
- SAF_SystemFunctionalRequirementConstraint
- SAF_SystemFunctionalRequirementRefinement
- SAF_SystemRequirementRefinement
- SAF_SystemRequirementDerivation
- SAF_SystemRequirement
- SAF_StakeholderRequirement
- SAF_SystemUseCase
- SAF_SystemFunction
- ProxyPort
- SAF_SystemProcess
- SAF_FunctionAction contained in SAF_SystemProcess
- SAF_SystemProcessRefinement
- SAF_SystemCapability