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 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 «system» Keywords requirements engineering contract customer stakeholder designer Previous snippet A requirement may specify a function that a system must perform or a performance condition that a system must satisfy. Full quote Requirements are used to establish a contract between the customer (or other stakeholder) and those responsible for designing and implementing the system. Next snippet Related snippets A requirement specifies a capability or condition that must (or should) be satisfied. Related snippets (backlinks) 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
