| Domain | Aspect | Maturity |
|---|---|---|
| Functional | Requirement |  released |
The System Requirement Definition Viewpoint specifies functions, non-functional properties, or constraints of the System. System Requirements are captured, the interrelationships between Functional and Non-Functional Requirements on the same level of abstraction and the traceability to Stakeholder Requirements are depicted.
The System Requirement Definition Viewpoint supports the "System Requirements Definition Process" activities of the INCOSE SYSTEMS ENGINEERING HANDBOOK 2015 [§4.3] and contributes to the System Requirements Verification and Traceability Matrix (RVTM).
A tabular format listing
- unique requirement ID, text, and attributes,
- traceability reference to Stakeholder Requirements,
- traceability reference to depended Requirements on the same level of abstraction.
- What are the exchange requirements imposed on the system?
- What are the functional requirements imposed on the system?
- What are the non-functional requirements imposed on the system?
- What are the requirements of environmental conditions imposed on the system?
- What is the range of acceptable system performance, i.e. the critical, top-level performance requirements derived from the operational needs?
- Which System Requirements are derived from Stakeholder Requirements?
- Which are the interface requirements imposed on the system?
The following Stereotypes / Model Elements are used in the Viewpoint: