Objecteering Dimensions commands

 

Overview

The following commands are specific to the Objecteering Dimensions MDAC.

 

The ... command

is used to …

History

open the History window of the current element.

Diff-Merge models

compare or merge the current model with another stored model.

 

 

Advanced options

When the "Advanced options" MDAC parameter has been activated, additional options are available on the "Check-out" and "Import..." commands.  These options are used to retrieve an earlier version of the model or a model element.

 

If the "Confirm operations" parameter has been activated, a confirmation dialog box appears.

 

Figure 83. Confirming the import/check-out of a specific revision

 

 

Figure 84. Selecting a revision to be imported or checked-out

 

Steps:

1.      Select a revision to import/check-out.

2.      Confirm by clicking on "Select".

 

Note:      In this model, the import or check-out operation must be non-hierarchical and is only applied to the element on which the command has been run.

 

 

Change management

When the "Change management" MDAC parameter has been activated, the creation of a new revision of a model element (“Check-out” or “Check-in" of a new model element) imposes the selection of one or several Change Documents.  Selected Change Documents are automatically linked to new revisions with an "in-Response-to" link.

 

Figure 85. Selecting Change Documents to be linked to new revisions

 

The selection of a Change Document is made using the left mouse-button.  Change Documents are unselected using the right mouse-button.

 

If you click on the "OK" button, the selected Change Documents will only be linked to the element indicated at the top of the window.  Next, the Change Documents selection window appears for the following element.  The "OK" button is used, therefore, to select different Change Documents for each revision created during a hierarchical check-in or check-out operation.

 

If you click on the "OK to all" button, the selected Change Documents will be linked to all the revisions still to be created after the closure of the window, during the same check-in or check-out hierarchical operation.

 

 

The "History" command

This command starts a history browser on the current element, to display all revisions.

 

Figure 86. The "History" window

 

The "Only show Item revision history contained in the current Workset" toggle is used to filter the revisions displayed in the history, by only showing those revisions present in the Workset associated with the Objecteering model.

 

The "Action" button is used to move the state of the selected revision forward in its lifecycle.

 

The following error message, returned by Dimensions, indicates that the revision is in its final state:

 

2307-Please specify the new state to which Item PAYROLL:39573269878:2752.A-OBJING_EXT;3 is to be actionned (-1)

 

Note:      The name of the 39573269878:2752 item is different from one model element to the next.

 

 

The "Diff-Merge models" commands

The "Diff-Merge models" command is used to select a model you wish to compare, select the ancestor model and customize the options used by the Diff-Merge tool.  The model to be compared and the ancestor model can be retrieved in:

·         another project

·         a repository managed by Objecteering Multi-user, a ClearCase view or a simple directory containing a model in a form equivalent to that of the model in the repository. For example, it is possible to extract a Workset representing a baseline into a repository.

 

Note:      Before carrying out a model merge, you must check-out those elements which are going to be modified by the merge.  If you are running a comparison without a subsequent merge, this is not necessary.

 

 

This information is defined through a wizard containing three windows.  The first window (shown in Figure 87 below) is used to select the model which is to be compared.  Two choices are possible:

·         Select Objecteering project: by selecting this option, the list which follows contains all the projects available on the Objecteering site.

·         Select repository: by selecting this option, you can define the directory where the elements which are to be compared are stored.

 

Figure 87. Selecting the model to be compared

 

To continue with the next step, you must either select an Objecteering modeling project from the list or define a directory in which the element which is to be compared can be accessed.  After doing this, click on the "Next" button to continue with the second step.

 

The second window (shown in Figure 88) is used to select the ancestor model.  This second window behaves in the same way as the first.

 

Figure 88. Selecting the ancestor model

 

The selection of an ancestor model is optional.  In order not to define an ancestor model:

·         if the "Select Objecteering project" tickbox has been checked, no Objecteering model should be selected

·         if the "Select repository" tickbox has been checked, the "Repository" field must be left blank

 

To continue with the final step, simply click on the "Next" button.

 

The third window (shown in Figure 89) is used to define Diff-Merge customization options.

 

Figure 89. Configuring the Diff-Merge

 

 

The ... parameter

is used to ...

Log

indicate the log where information on all the modifications carried out by the Diff-Merge editor is stored.

Environment variables in $(OBJING_PATH) form can be used in this field to define the location of the log file.

External editor for merging texts

indicate the external editor used to merge all note types (C++, Java, documentation, etc).

Environment variables in $(OBJING_PATH) form can be used in this field to define the location of the external editor of your choice.

Options and arguments for merge editor

define the options and arguments of the editor used in the Diff-Merge of texts.  According to the editor used, options and arguments can be different.  Two variables must be used to represent the initial text and the text to be compared.  $(LEFTFILE) represents the initial text, and $(RIGHTFILE) represents the text to be compared.  Unlike MDAC parameters, you must not put two $ signs.

Merge result

define the file containing the result of the text merge.  According to the editor used, the editor value can be different.  For example, if the editor saves the result of the merge in the initial text, the $(LEFTFILE) value must be given to this parameter.

 

 

To activate the comparison between the current model and the model to be compared, simply click on the "Finish" button.

 

For further information on the Diff-Merge tool, please see "The Diff Merge tool".