Typical lifecycle of a model stored in a CM tool (CM tool integration) — Storing a model the first time
There are typically three stages for storing and working with a model stored in a CM tool (a CM tool model):
• Storing a model in a CM tool the first time
• Creating a replica of a CM tool model
• Changing items in a CM tool model
Storing a model in a CM tool the first time
When you first create a Model in the Modeler environment, that Model is not associated with the CM tool environment, that is, the Model is not under configuration control. You perform a check in operation to copy the Model and its Packages to the CM tool.
A check in operation copies a Package or Model from the Modeler environment to the CM tool environment. You use a check in operation the first time you want to copy new Models and Packages to the CM tool environment, and thereafter to check in Packages and Models that are checked out to you.
The first time you check in a Model and its Packages, you are prompted to create a CM tool project in which to store the Modeler Model (with some CM tools you must create the project through the CM tool).
Notes
• If you attempt to check in a diagram or sub-Package that is locked, Modeler abandons the check in operation and displays a message informing you who has the diagram or item locked. Typically a diagram will be locked because a user has the diagram open. Ask the user to close the diagram, and then repeat the check in operation.
• When using IBM Rational ClearCase you must create a subfolder of the vob for the model. You must set this up manually, because the check in operation cannot create a subfolder of a vob.
• When using SYNERGY/CM, you must create an empty project in which to store the model and then baseline it. You must set this up manually, because the check in operation cannot create a project in a database.
• After checking in a Modeler Model, the Model and its Packages are under configuration control, which is indicated in Modeler through an arrow on the Model and Package icons:
◦ Means the Model or Package is checked out by you to this Model.
◦ Means the Model or Package is not checked out by you to this Model.
• Modeler records information about an associated CM tool Model or Package through the following properties; SCC Project Path, SCC Aux Path and SCC File Name. You can determine these property values through the Configuration Management > Advanced > Detailed Report command. If the drive mapping recorded in the SCC Project Path and SCC Aux Path properties is different from the drive mapping you are using for the CM tool, the CM tool integration will not find the associated files in the CM tool database. Should this happen, you can reconnect the Packages to configuration management, storing the paths that you use locally on your computer through the 'Configuration Management > Advanced > Reconnect to Configuration Management > Store CM Tool Paths Locally on my Computer' command (unless you are using Telelogic SYNERGY/CM).
• When you use the CM tool integration commands, Modeler attempts to connect to the CM tool using your Windows log in name.
Example - Checking in a Model the first time
In this example, we check in the Ticket Allocation Model. This example uses Microsoft Visual SourceSafe (VSS.)
Initially, the Ticketing System Model is not stored in the CM tool.
From the Packages pane in Modeler, we right-click the Model, point to Tools > Configuration Management, and then click Check In. We are prompted to create a VSS project to store the Model and its Packages. To check in the complete Model, we select the Check in sub-Packages check box.
Notice the following:
• The Ticketing System project is created in VSS, and files are created for the Model and each Package.
• The Model and Package icons in Modeler have an incoming (left pointing) arrow on their symbols, which indicates that they are under configuration control.
For more information about interpreting the Package and Model symbols, see
Model and Package Symbols.
The files created are as follows:
After the Ticketing System Model is checked in, the Modeler copy of the Model must now be considered out-of-date because other users may have checked in changes to the CM tool model.
Means the Model or Package is checked out by you to this Model.
Means the Model or Package is not checked out by you to this Model.
