Icon class icon_class fas fa-quote-left icon_class_computed fas fa-quote-left Related content Figure 16-5: Use of the copy dependency to facilitate reuse The SysML Copy relationship can be used to "import" Requirements from an existing read-only library into a new project context. The SysML Copy relationship can be used to "import" Requirements from an existing read-only library into a new project context. Webel has suggested primary/replica as an alternative to master/slave terminology for the SysML Copy relationship in future SysML versions 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 UML keywords Dependency Dependency::client Dependency::supplier SysML keywords Requirement Copy AbstractRequirement::text AbstractRequirement::id Previous snippet A Copy relationship is a dependency between a supplier requirement and a client requirement that specifies that the text of the client requirement is a read-only copy of the text of the supplier requirement. Full quote A Copy dependency created between two requirements maintains a master/slave relationship between the two elements for the purpose of requirements re-use in different contexts Next snippet When a Copy dependency exists between two requirements, the requirement text of the client requirement is a read-only copy of the requirement text of the requirement at the supplier end of the dependency. Webel has suggested primary/replica as an alternative to master/slave terminology for the SysML Copy relationship in future SysML versions Related snippets A Copy relationship is a dependency between a supplier requirement and a client requirement that specifies that the text of the client requirement is a read-only copy of the text of the supplier requirement. Related snippets (backlinks) Figure 16-5 illustrates the use of the Copy dependency to allow a single requirement to be reused in several requirements hierarchies. The master tag provides a textual reference to the reused requirement. A Verify relationship is a dependency between a requirement and a test case or other model element that can determine whether a system fulfills the requirement. As with other dependencies, the arrow direction points from the (client) element to the (suppl 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
