Package merge (UML Standard profile)

A Package Merge relationship shows that a Package merges the content of another Package.

Create Package Merge relationships through a Package Diagram - click the

Package Merge button, click the start Package, and then click the end Package. If an existing Package Merge relationship exists, a popup menu appears - you can then click New or select an existing Package Merge relationship to add.

On a Package Diagram, a Package Merge relationship's notation is as follows.

A Package Merge relationship is a UML Dependency that is stereotyped by the «merge» stereotype from the UML Standard profile.

The following sections provide information about how a Package Merge relationship is used in the model. For more information about a UML Standard profile diagram or item - click it.

Package - a Package Merge relationship is owned jointly by the two Packages it links.

Allocate (only if SysML Profile present) - the Allocate is owned jointly by the Package Merge 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.

Constraint (UML item)

Problem (only if SysML Profile present)

Rationale (only if SysML Profile present)

Refine - the Refine relationship is owned jointly by the Package Merge 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 (only if SysML Profile present) - the Satisfy relationship is owned jointly by the Package Merge and the associated Requirement. The access permissions you have to a Satisfy relationship are determined by the access permissions you have to the Package Merge.

Trace - the Trace relationship is owned jointly by the Package Merge 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 (only if SysML Profile present) - the Verify relationship is owned jointly by the Package Merge and the associated Requirement. The access permissions you have to a Verify relationship are determined by the access permissions you have to the Package Merge.