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).

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
TIP
Policy level
INFORMATIVE
Specification keywords
SysML-1.7
SysMLv1.x keywords
AbstractRequirement::id
Requirement
Copy
Click on the image to view it full size

Only the 'text' of the client Requirement of a Copy relationship need be the same a the 'text' of the supplier Requirement. The 'id' of the client Requirement SHOULD be different (unique).

SysMLv1.7: '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.'
SysMLv1.7: '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.'
SysMLv1.7: '16.3.2.1 AbstractRequirement: id : String [1] The unique id of the requirement.'
To learn more about Copy visit also:
The Copy relationship
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.
Relates to
Related notes
[TIP] The SysML Copy relationship can be used to "import" Requirements from an existing read-only library into a new project context.
Related notes (backlinks)
Related snippets (extracts)
  [SysML-1.6] 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.
  [SysML-1.6] 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.
  [SysML-1.6] 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
  [SysML-1.7] 16.3.2.1 AbstractRequirement: id : String [1] The unique id of the requirement.
  [SysML-1.6] 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.
  [SysML-1.6] A requirement is a stereotype of both Class and Abstract Requirement.
  [SysML-1.6] 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.
  [SysML-1.6] The master/slave relationship is indicated by the use of the copy relationship.
Visit also
Figure 16-5: Use of the copy dependency to facilitate reuse
The Copy relationship
Visit also (backlinks)