Learn about Webel IT's new SysMLv2/MBSE Workshop Seminar course!
VIDEO: The Webel SysMLv2/MBSE course has landed! Take a quick tour!
Webel now has a SysMLv2 Online Self-Study course with self-test Quizzes!

SysML provides modeling constructs to represent text-based requirements and relate them to other modeling elements.

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
Requirement
AbstractRequirement::text
Satisfy
Verify
DeriveReqt
Copy
Keywords
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 a system must achieve.
Full quote
SysML provides modeling constructs to represent text-based requirements and relate them to other modeling elements.
Next snippet
The requirements diagram described in this clause can depict the requirements in graphical, tabular, or tree structure format. A requirement can also appear on other diagrams to show its relationship to other modeling elements.
Related snippets
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 a system must achieve.
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.
Related snippets (backlinks)
The requirements modeling constructs are intended to provide a bridge between traditional requirements management tools and the other SysML models.
A requirement is defined as a stereotype of UML Class subject to a set of constraints.
A standard requirement includes properties to specify its unique identifier and text requirement. Additional properties such as verification status, can be specified by the user.
Several requirements relationships are specified that enable the modeler to relate requirements to other requirements as well as to other model elements.
These include relationships for defining a requirements hierarchy, deriving requirements, satisfying requirements, verifying requirements, and refining requirements.
A composite requirement can contain subrequirements in terms of a requirements hierarchy, specified using the UML namespace containment mechanism. This relationship enables a complex requirement to be decomposed into its containing child requirements.
A composite requirement may state that the system shall do A and B and C, which can be decomposed into the child requirements that the system shall do A, the system shall do B, and the system shall do C
An entire specification can be decomposed into children requirements, which can be further decomposed into their children to define the requirements hierarchy.
Visit also
Visit also (backlinks)