Overview of teamwork MDAC commands
General description
The Objecteering Multi-user, Objecteering ClearCase, Objecteering SCC, Objecteering CM Synergy and Objecteering Dimensions teamwork MDACs contain certain commands which can be run from an element's context menu. This context menu is accessed by right-clicking over the element in question.
Three types of command exist:
· commands available on elements in read-only mode ("Check-out", "Import from repository")
· commands available on elements in read-write mode ("Check-in", "Check-in and check-out", "Undo check-out")
· commands available on all elements, in both read-only and read-write modes ("Project check-in", "Properties", "Diff/Merge models")
The Objecteering Multi-user, Objecteering ClearCase, Objecteering SCC, Objecteering CM Synergy and Objecteering Dimensions MDACs also provide additional MDAC-specific commands. For details on these commands, please refer to the corresponding chapter in this user guide.
Multi-user atomic units
A multi-user atomic unit is the minimum amount of information which can be reserved. Teamwork commands can only be run on multi-user atomic units.
Multi-user atomic units are instances of the following metaclasses:
·
RequirementProject
Other types of model element (attributes, operations, instances, etc.) attached to the multi-user atomic unit are managed along with the multi-user atomic unit itself. Thus, class operations or attributes are information attached to the class. To modify or add an operation to a class, the class in question must be reserved. When the class itself is archived, attributes and operations which may have been modified are also automatically archived.
To delete a multi-user atomic unit, the unit itself, as well as its embedding unit, must be reserved. The embedding unit is modified, since its composition link is altered.
Hierarchical mode
The hierarchical mode allows you to carry out reservations and imports, whilst taking into account model composition hierarchy. This mode is selected by default, in order to facilitate the consistent update of models. However, you must be careful when reserving units, as this reservation will also be hierarchical. This means that if a command is run in hierarchical mode on a high-level element (for example, a project), it can take several minutes to run, as the command will be executed on all the components.
The teamwork MDAC allows several users to carry out check-out operations on units defined in the same package, without having to run a check-out on the package itself. In a situation like this, it is recommended that you avoid running a check-out on the package itself in non-hierarchical mode, so as to allow the possible creation of new units.
When the "Check-in", "Import from repository" and "Check-out" commands are run, a confirmation dialog box (Figure 11) is displayed (only if the "Confirm operations" tick box has been checked during MDAC configuration), through which it is also possible to define whether or not the command is to be run in hierarchical mode or not.
Figure 11. The hierarchical mode confirmation dialog box
Information on repository locking
If the multi-user repository is locked by another user, a window appears, indicating the name of the user in question, the operation which is being carried out, the element concerned and since when the operation has been underway.
In this case, you are invited to try your operation again later.
Summary of commands available in read-only mode
|
The
... command |
is
used to … |
|
Check-out |
reserve an element, in order to subsequently modify it. The latest version of the element in question is imported into the Objecteering model. |
|
Import from repository |
import the complete element stored in the repository into the Objecteering modeling project. |
Summary of commands available in read-write mode
|
The
... command |
is
used to … |
|
Check-in |
free the element and export it into the repository, so that the element is available to other users in its latest version. |
|
Check-in and check-out |
check-in and then check-out model elements. By doing this, model elements are updated for all other users, but remain locked against further modifications. |
|
Undo check-out |
cancel the check-out and go back to the previous version. |
Summary of commands available on all elements (read-only and read-write)
|
The
... command |
is
used to … |
|
Project check-in |
check-in all project elements currently in checked-out state. This command cannot be run on the current element, but only the entire Objecteering project. |
|
Properties |
display the element's properties. |
|
Diff/Merge models |
compare or merge the current model with another model. This command can be run with the Objecteering Multi-user, Objecteering ClearCase, Objecteering SCC and Objecteering Dimensions MDACs. It is not available with the Objecteering CM Synergy MDAC. |
Removing the teamwork MDAC
When the MDAC is unselected, a check is run to ensure that all elements in the current project are in read-only mode, which signifies that these elements have been archived.
If elements have remained in read-write mode, a confirmation dialog box allows you to force MDAC removal (Figure 12).
Figure 12. Confirming MDAC removal
The MDAC removal operation puts all elements into read-write mode.