Warnings and restrictions

Introduction

All the Objecteering teamwork MDACs are subject to certain restrictions, which are presented in this chapter.  The restrictions described are common to all the teamwork MDACs.  For restrictions specific to each MDAC, please refer to the related section of this user guide.

Objecteering versions

All users connected to a repository must be using the same version of Objecteering and the same version of the teamwork MDAC.

Undo/Redo

During check-in, check-out and undo check-out operations, a backup of the project is made.  The "Undo/Redo" commands are not, therefore, available.

Consistency checks

A consistency check is run within the Objecteering project, but not within the repository.  It is, therefore, possible to inadvertently create inconsistencies within the model you wish to import.  In order to detect possible consistency problems within the repository as soon as possible, we recommend that you regularly execute the "Import from repository" command on the project, in order to import the entire contents of the repository, thus triggering a consistency checking operation on the project itself.

To guarantee the consistency of models built using Objecteering, checks are continually run by the tool during modeling and internalization phases.  We strongly recommend against deactivating consistency checks, and it is imperative that you NEVER publish ("Check-in") model units in the repository without them being active.

User

For the Objecteering Multi-user MDAC, it is important not to configure two Objecteering projects with the same user name.  Locking checks ("Check-out") are carried out from this name, and if several simultaneously active Objecteering projects have been configured with the same user name, then incorrect processing will be carried out by Objecteering.

The current version of Objecteering Multi-user carries out no checks on user name repetition.

For the Objecteering ClearCase, Objecteering SCC and Objecteering Dimensions MDACs, it is imperative that each user have a different login.

MDACs used

Each individual Objecteering project must respect the two lists of MDACs that figure in the "modulesList.conf" file:

· the list of mandatory MDACs, which must which must be selected in the stated version for each individual project

· the list of allowed MDACs, which are authorized for each individual project (the version numbers of allowed MDACs are not checked)

If you have deployed additional MDACs in your project and these additional MDACs provide specific note types or stereotypes, this can cause problems for the other users.

Furthermore, when MDACs are removed from a project, no warning is given at the time of unselection but rather the first time a Multi-user command is run after unselection.  You should be aware that certain information may be lost between the moment of MDAC removal from a project and the first execution of a Multi-user command.

For performance-related reasons, we recommend that a project type be created.  This project type should contain all pre-installed and pre-selected MDACs.  If this is done, connection to a repository when creating a new database is more efficient.  The teamwork MDAC can be pre-installed, but must not be selected.  For more information on this point, please see "Using project types" in the Objecteering Modeler User Guide.

All users connected to the same repository must use the same teamwork MDAC.  For example, it is not possible to have some users using the Objecteering Multi-user MDAC, whilst other users are using the Objecteering ClearCase MDAC.

Stopping commands

As soon as a command has been launched, it is not possible to stop it.

A command run on a large number of elements can take several minutes to complete.  In this case, we strongly recommend against stopping Objecteering abruptly, as certain data could be lost if it has not been saved either in the repository or in the Objecteering project.

If Objecteering stops abruptly, the procedures described in the "How should I proceed after a problem?" section should be followed.

Launching Objecteering directly on a project

When launching Objecteering, it is possible to specify the name of the project in the command line:

objing [<database name>] [<project name>]

In order not to have to make selections, and to avoid all errors, we recommend that you use this possibility via a UNIX script or a Windows shortcut.