SysML, UAF, UML, and UPDM Profiles > SysML profile > SysML relationships > Copy (SysML relationship)
  
Copy (SysML relationship)
A Copy relationship is a dependency between a slave Requirement and a master Requirement that specifies that the txt property of the slave Requirement is a read-only copy of the text of the supplier Requirement.
Create Copy relationships between Requirements in the following ways:
In a Modeler pane:
Right-click the slave Requirement, point to Links, point to Traceability, and then click Master. From the links editor select the master Requirement, and then click Link.
Right-click the slave Requirement, and then click Links > Start Link. Right-click the master Requirement, and then click Links > End Link. From the Relationship list, select Master, and then click OK.
On a diagram, click the Copy button, click the slave Requirement, and then click the master Requirement.
When shown on a diagram, a Copy relationship's notation is as follows.
On a diagram you can right-click the diagram background and populate Copy relationships:
To populate Copy relationships that are missing between Requirements shown on the diagram: right-click the diagram background, point to Populate, point to Links, and then click Copies.
To populate a Requirement's missing Copy relationships (Modeler adds to the diagram any missing Requirements required to show missing Copy relationships): right-click the Requirement, point to Populate, point to Links, and then click Copies.
The txt property of a Requirement is typically derived from the Description property of that Requirement. However, when a Copy relationship is created between a slave Requirement and a master Requirement, the txt property of the slave Requirement is set to the txt property of its master Requirement.
All Copy relationships are shown in the Requirements pane - expand the Copy folder.
A Copy relationship is a UML Dependency that is stereotyped by the «Copy» stereotype from the SysML profile.
The following sections provide information about how a Copy relationship is used in the model. For more information about a SysML diagram or item - click it.
Owned by
Requirement
Requirement Extensions
Owns
Allocate - the Allocate is owned jointly by the Copy and the associated item. The access permissions you have to a Copy are determined by the access permissions you have to the item that is allocated from - you require write access to both items to create or delete a Copy.
Problem
Rationale
Refine (UML Standard profile) - the Refine relationship is owned jointly by the Copy and the associated item. The access permissions you have to a Refine relationship are determined by the access permissions you have to the refined item.
Satisfy - the Satisfy relationship is owned jointly by the Copy and the associated Requirement. The access permissions you have to a Satisfy relationship are determined by the access permissions you have to the Copy.
Trace (UML Standard profile) - the Trace relationship is owned jointly by the Copy and the associated item. The access permissions you have to a Trace relationship are determined by the access permissions you have to the item that is traced from.
Verify - the Verify relationship is owned jointly by the Copy and the associated Requirement. The access permissions you have to a Verify relationship are determined by the access permissions you have to the Copy.
Shown on these diagrams
Copy relationships can be shown on most UML and SysML diagrams.
Block Definition Diagram
Internal Block Diagram
Parametric Diagram
Requirement Diagram
Traceability Diagram
Traceability Matrix
SysML Properties
allocatedFrom - lists source items that are linked through Allocate relationships (on Allocated tab when item is allocated).
allocatedTo - lists target items that are linked through Allocate relationships (on Allocated tab when item is allocated).