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

Examples of additional non-normative stereotypes based on AbstractRequirement are included in E.8.

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
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
AbstractRequirement
Requirement
An AbstractRequirement establishes the attributes and relationships essential to any potential kind of requirement. Any intended requirement kind should subclass AbstractRequirement.
Full quote
Examples of additional non-normative stereotypes based on AbstractRequirement are included in E.8.
Next snippet
Related snippets
Requirements are used to establish a contract between the customer (or other stakeholder) and those responsible for designing and implementing the system.
A requirement specifies a capability or condition that must (or should) be satisfied.
A requirement may specify a function that a system must perform or a performance condition that a system must satisfy.
An AbstractRequirement establishes the attributes and relationships essential to any potential kind of requirement. Any intended requirement kind should subclass AbstractRequirement.
The only normative stereotype based on AbstractRequirement is the Requirement stereotype, ...
Related snippets (backlinks)
Visit also
Visit also (backlinks)