Learn about Webel IT's new SysMLv2/MBSE Workshop Seminar course!

For example, a system requirement may be derived from a business need, or lower-level requirements may be derived from a system requirement.

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
Figure D.13 - Acceleration Requirement Relationships
Figure D.14 - Requirements Relationships Expressed in Tabular Format (Table)
SysML-1.6: 'Figure 16-2: Requirements Derivation' indeed shows DeriveReqt but spec text refers to it only as 'an example of a compound requirement'
Figure 16-2: Requirements Derivation
Figure 16-3: Links between requirements and design
Source
OMG Systems Modeling Language (SysML) 1.6
Copyright information
About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes
Snippet kind
INFO
SysML keywords
DeriveReqt
Requirement
Keywords
A DeriveReqt relationship is a dependency between two requirements in which a client requirement can be derived from the supplier requirement.
Full quote
For example, a system requirement may be derived from a business need, or lower-level requirements may be derived from a system requirement.
Next snippet
As with other dependencies, the arrow direction points from the derived (client) requirement to the (supplier) requirement from which it is derived.
Related snippets
A DeriveReqt relationship is a dependency between two requirements in which a client requirement can be derived from the supplier requirement.
Related snippets (backlinks)
Visit also
Visit also (backlinks)