Glossary

· API: Application Protocol Interface. Interfaces between application layers and communicating layers defined in the ISO model.

· CMS: Configuration management system. Application used to store different versions of files, to keep a file history and to retrieve the state of these files as they were on a given date. This tool is used in group work.

· Check-in: The restitution of reserved elements.

· Check-out: The reservation of shared elements in the repository. Operation used to request the modification of model elements. An element cannot be modified by several users at one time, and to this end a locking mechanism managed by the CMS (configuration management system) checks requests for modification.

· Inter-project import: Transfer of data between Objecteering modeling projects, without going through a repository.

· Label: A version label which allows you to associate an identifier to an important version of an element.

· Teamwork MDAC: MDAC allowing a model to be shared, so that teamwork can be carried out on a project. Objecteering Multi-user, Objecteering ClearCase, Objecteering SCC, Objecteering Dimensions and Objecteering CM Synergy are teamwork MDACs.

· Multi-user atomic unit: Modeling element which is stored in a file and on which MDAC commands are available. Multi-user atomic units are packages, classes, actors, use cases, signals, components, nodes and data types. Other types of element are not multi-user atomic units and are externalized in the component multi-user atomic unit file.

· Objecteering project: Often called "project", this corresponds to the Objecteering Modeler area of functioning, and to a user's work area.

· Read-only mode: Mode in which an element may not be modified in any way. An element is put in read-only mode after a check-in operation.

· Read-write mode: Mode in which an element may be modified. An element is put in read-write mode after a check-out operation.

· Repository: Area containing data shared between several developers.

· SCC: Source Code Control. Unified interface common to several CMS (configuration management systems) (VSS, PVCS Version Manager, etc). This interface only exists in the Windows environment.

· SCC provider repository: Database internal to a CMS (configuration management system), where information is stored.

· User: A person identified by a name, and whose Objecteering project constitutes a work area.