Learn about Webel's comprehensive SysMLv2 Workshop Seminar course!
Webel now has a SysMLv2 Online Self-Study course with self-test Quizzes!
Learn about the Webel Q&A     online self-testing system for SysML v2/v1

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.

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 Copy relationship
SysMLv1: Only the 'text' of the client Requirement of a Copy relationship need be the same as the 'text' of the supplier Requirement. The 'id' of the client Requirement SHOULD be different (unique).
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
CONSTRAINT
UML keywords
Dependency
Dependency::client
Dependency::supplier
SysML keywords
Requirement
Copy
AbstractRequirement::text
AbstractRequirement::id
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
Full quote
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.
Next snippet
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)
Copy::2_same_text The text property of the client requirement is constrained to be a read-only copy of the text property of the supplier requirement and this applies recursively to all subrequirements
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.
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 ...
16.3.2.1 AbstractRequirement: id : String [1] The unique id of the requirement.
Visit also
Visit also (backlinks)