Icon class icon_class fas fa-quote-left icon_class_computed fas fa-quote-left Related content Figure D.11 - Establishing HSUV Requirements Hierarchy (containment) Figure D.13 - Acceleration Requirement Relationships Figure 16-1: Abstract Syntax for Requirements Stereotypes A most basic Requirement with a 'name', an 'id', and 'text' 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 Satisfy Keywords requirements engineering Previous snippet Full quote A requirement specifies a capability or condition that must (or should) be satisfied. Next snippet A requirement may specify a function that a system must perform or a performance condition that a system must satisfy. Related snippets Related snippets (backlinks) A requirement may specify a function that a system must perform or a performance condition that a system must satisfy. Requirements are used to establish a contract between the customer (or other stakeholder) and those responsible for designing and implementing the system. A requirement is a stereotype of both Class and Abstract Requirement. Compound requirements can be created by using the nesting capability of the class definition mechanism. The default interpretation of a compound requirement, unless stated differently by the compound requirement itself, is that all its subrequirements shall be satisfied for the compound requirement to be satisfied. Subrequirements shall be accessed through the "nestedClassifier" property of a class. When a requirement has nested requirements, all the nested requirements apply as part of the container requirement. Deleting the container requirement deleted [deletes] the nested requirements, a functionality inherited from UML. 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. SysML provides modeling constructs to represent text-based requirements and relate them to other modeling elements. 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. 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. 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, ... Examples of additional non-normative stereotypes based on AbstractRequirement are included in E.8. Visit also Visit also (backlinks) Flags
