Icon class icon_class fas fa-quote-left icon_class_computed fas fa-quote-left Related content The Copy relationship 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 composite (compound) requirement Previous snippet Full quote The use of namespace containment to specify requirements hierarchies precludes reusing requirements in different contexts since a given model element can only exist in one namespace. Next snippet Since the concept of requirements reuse is very important in many applications, SysML introduces the concept of a slave requirement. Related snippets Compound requirements can be created by using the nesting capability of the class definition mechanism. 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. Related snippets (backlinks) Since the concept of requirements reuse is very important in many applications, SysML introduces the concept of a slave requirement. A slave requirement is a requirement whose text property is a read-only copy of the text property of a master requirement. The text property of the slave requirement is constrained to be the same as the text property of the related master requirement. The master/slave relationship is indicated by the use of the copy relationship. AbstractRequirement::/master : AbstractRequirement [0..*] This is a derived property that lists the master requirement for this slave requirement. The master attribute is derived from the supplier of the Copy dependency ... Visit also Visit also (backlinks) Flags
