Derive reqt (SysML relationship)
Shallow Connector button to add a new Connector between BlockPropertyA and BlockPropertyB in the context of Block4, the context menu that is opened will allow you to add the Connector in the new context, because the Connector is defined in BlockProperty1's type (Block1).
Create Derive Reqt relationships between Requirements in the following ways:
• In a Modeler pane:
◦ Right-click the source Requirement, point to Links, point to Traceability, and then click Derived. From the links editor select the Requirement from which the source Requirement is derived, and then click Link.
◦ Right-click the source Requirement, and then click > . Right-click the Requirement from which the source Requirement is derived, and then click > . From the Relationship list, select Derived or Derived From.
• On a diagram, click the Derive Reqt button, click the derived Requirement, and then click the Requirement from which the Requirement you first clicked is derived.
Derive Reqt button, click the derived Requirement, and then click the Requirement from which the Requirement you first clicked is derived.In addition to creating Derive Reqt relationships, the preceding commands provide a way of viewing which Requirements derive from other Requirements. Alternatively, you can view the tagged values of a Requirement's derived and derivedFrom tag definitions.
On a Requirement Diagram, you can create a Derive Reqt relationship between two Requirements through the Derive Reqt button on the diagram's tab: click the Derive Reqt button, click the derived Requirement, and then click the Requirement from which the Requirement you first clicked is derived.
Derive Reqt button on the diagram's tab: click the Derive Reqt button, click the derived Requirement, and then click the Requirement from which the Requirement you first clicked is derived.When used on a Requirement Diagram, the notation of a Derive Reqt relationship is as follows:
On a diagram, you can show compartments on a Requirement to show which Requirements are linked through the «deriveReqt» relationship:
• To show a compartment that lists the Requirements that are derived from that Requirement: right-click the Requirement, point to Show/Hide Compartments, and then select the derived check box.
• To show a compartment that lists the Requirements from which the Requirement is derived: right-click the Requirement, point to Show/Hide Compartments, and then select the derivedFrom check box.
Alternatively, you can add a callout to a Requirement to show the derived and derivedFrom compartments.
A Derive Reqt relationship is a UML Dependency that is stereotyped by the «deriveReqt» stereotype from the SysML profile.
The following sections provide information about how a Derive Reqt relationship is used in the model. For more information about a SysML diagram or item - click it.
Owned by
Requirement - The Derive Reqt relationship is owned jointly by the two Requirements it links. The access permissions you have to a Derive Reqt relationship are determined by the access permissions you have to the derived Requirement.
Requirement Extensions - The Derive Reqt relationship is owned jointly by the two Requirements or Requirement Extensions it links. The access permissions you have to a Derive Reqt relationship are determined by the access permissions you have to the derived Requirement or Requirement Extension.Owns
Allocate - the Allocate is owned jointly by the Derive Reqt relationship and the associated item. The access permissions you have to an Allocate 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 an Allocate.
Shown on these diagrams
Derive Reqt relationships can be shown on most UML and SysML diagrams.
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).