Constrain (MBRE profile)
The Constrain relationship is a PTC proprietary relationship that is available only when the MBRE Profile has been added to a model.
A Constrain relationship defines that one Use Case constrains another Use Case in some way.
Create a Constrain relationship between two Use Cases in the following ways:
• On a Use Case Diagram, click the Constrain button, click the Use Case that constrains, and then click the Use Case that is constrained.
Constrain button, click the Use Case that constrains, and then click the Use Case that is constrained.• On an MBRE Traceability Diagram, click the Constrain button, click the Use Case that constrains, and then click the Use Case that is constrained.
Constrain button, click the Use Case that constrains, and then click the Use Case that is constrained.• In a Modeler pane:
◦ Right-click the Use Case that constrains, and select > . From the links editor select the Use Case that is constrained.
◦ Right-click the Use Case that constrains, and then select > ; right-click the Use Case that is constrained, and then click > . From the Relationship list, select Constrains, and then click OK.
When shown on a Use Case Diagram or MBRE Traceability Diagram, a Constrain's notation is as follows.
On a Use Case Diagram or MBRE Traceability Diagram, you can populate Constrain relationships: right-click the diagram background or an owning item, and select > > .
When you add a Constrain relationship to a Use Case, Modeler applies the «UseCaseRelated» stereotype to that Use Case. On the UseCaseRelated tab of the Use Case's Property Pages, the constrainedBy and constrains tag definitions show how that Use Case is linked to other Use Cases through Constrains relationships.
In the Dictionary pane, Constrains are listed in the UML\Dependencies folder.
The following sections provide information about how a Constrain relationship is used in the model. For more information about a property, item or diagram, click it.
Properties
A Constrain relationship has the standard properties.
Owned by
Use CaseOwns
Comment
Constraint
Dependency- The Dependency is owned jointly by the Constrain and the other associated item. The access permissions you have to a Dependency are determined by the access permissions of the dependent item.Shown on these diagrams
Use Case Diagram
Can be linked to these dictionary items
In addition to the owning items, a Constrain can be linked to the following items.
Stereotype