Each controlled unit is usually owned by one developer. A developer may own more than one controlled unit.
To make a package a controlled unit Click right on the package in the Browser to make the pop up menu visible. Select the Units:Control<package name> menu command. Navigate to the desired directory. Enter the name of the controlled unit in the File Name field. Click Save. Each package in the model should be made a controlled unit.
To display unit visibility Select the Tools:Options menu command. Select the Diagram tab. Click to select the Unit Adornments checkbox to toggle the selection. Click OK to close the Options window.
To load a controlled unit Click right on the package in the Browser. The pop up menu appears. Select the Units:Load menu command. OR To demand load a controlled unit, double click on the package representing the controlled unit on a class diagram.
If a package is a controlled unit, an icon is added to the Browser to indicate if the unit is loaded or unloaded.
To display unresolved reference adornments Select the Tools:Options menu command. Select the Diagram tab. Click the Unresolved References checkbox to toggle the selection.
To manually write protect a controlled unit Click right to select the controlled unit (package) in the Browser. Select the Units:Write Protect <package name> menu command .
To use the version control system integration, the Version Control Add-In must be active. It is active if the Tools menu contains a Version Control menu. Note that the Version Control Add-In is available only on Windows. To activate the Version Control Add-In: Click Add-In Manager on the Add-Ins menu. Select the Version Control add-in and click OK. If the Version Control add-in is not present, the Version Control Add-In is not installed. To install the Version Control Add-In: Run the Rational Rose setup program. Select a Custom install, and select the Version Control Add-In feature. If the Version Control Add-In feature is not present, the add-in is not available in your Rational Rose edition. See Rose Help for setting up your version control system .
To open the Rose Model Integrator Go to the Tools menu. Select Model Integrator. The Model Integrator dialog box opens. Go to the File menu and select Contributors. Select the files to compare/merge for your project. Select the Compare or Merge button. Notice that the first button changes names to Compare or Merge based on your selection. Click the Compare/Merge button. The Rose Model Integrator allows a team of developers to: work on different model components that reside in different .cat files merge their components into one base model compare differences between model elements and merge the changes as needed
To unload a controlled unit Select a unit that has a status of LOAD. Click on the status field for the controlled unit. The unit changes to a status of unloaded. Click OK. To load a controlled unit Select a unit that has a status of unloaded. Click on the status field for the controlled unit. The unit should change to a status of LOAD. Click OK. Note: Only previously controlled units will have a status of LOAD or unloaded. A non-controlled unit will have a status of ‘not a unit’. These units can not be loaded or unloaded.
Compare shows all differences between contributor files. The symbols that indicate the results of a Compare are displayed in the ‘C’ column. Item Changed : An item has been changed in one of the contributor files. Item Moved : An item has been moved in one of the contributor files. Item Added : An item has been added in one of the contributor files. Item Deleted : An item has been deleted in one of the contributor files. Note: For a complete list of symbols that can appear in the Compare mode, refer to Rose’s online help or documentation. The user can switch to the Merge mode by clicking on the Set Merge Mode toolbar icon.
To resolve a conflict between contributor files Select the unresolved item from the Browser. From the toolbar, select the number of the Contributor from which to accept changes. Note: The recipient field displays only in the Merge mode. To return to the Compare mode clicking on the Set Compare Mode toolbar.
The Version control add in includes the frequently used configuration management commands and is located on the Version Control submenu (from the Tools menu) and the CM submenu (from the Units submenu). Add to Version Control: place a new unit under configuration control; associate an element that was controlled outside of Rose with the current CM project; define a CM project. Remove from Version Control: remove units from the current CM project. Start Version Control Explorer: start your SCC provider application from Rational Rose Check in: put a controlled unit into the CM system. Check out: get a controlled unit from the CM system (read-write access, unit is locked) Undo Check out: return unit to CM system, undo any edits by the current developer. Get Latest: update Rose model with any check-ins by other developers which impact the current developer’s view. File Properties and File History: display property and history information about controlled units that have been added to the version control system.
Access to the integrated workspace may be provided by various means. Examples: NFS, Novell, Windows for Workgroups The integration workspace can be accessed by all users. The integration workspace is typically located on a server. In ClearCase, the integration workspace is a view.
Private workspaces typically contain work in progress. Developer workspaces may be on a view server or on a local disk.
The model may be moved or copied among workspaces by redefining the actual directory associated with the model.
To place a package under version control, the owning package must be checked out.
To get the latest version of a controlled unit (read-only versions) Select the Tools:Version Control: Get Latest menu command. Select the desired controlled units. Click the Get button.
Moe now has a read-write version of database.cat, which is locked (no other developer can check out database.cat). Larry now has a read-write version of register.cat, which is locked (no other developer can check out register.cat). Curly now has a read-write version of errors.cat, which is locked (no other developer can check out errors.cat). By checking out a package to a private workspace, developers can make changes to it without impacting our development.
To check out a controlled unit In the Browser, click-right to select the package representing the controlled unit. The pop up menu appears. Select the Check Out menu command.
To check in a controlled unit In the Browser, click-right to select the package representing the controlled unit. The pop up menu appears. Select the Check In menu command. Other developers will not automatically get the changes to register.cat. They have to execute the Get Latest command to copy the latest version into their private workspaces.
Hint: Right click on the package in the Browser and select the Control <package name> menu command.
To open the Business Objects main class diagram In the Browser, click the + next to the Business Objects package to expand the package. Double click on the Main class diagram.
Introduction to Rational Rose 98i Module 10: Team Development
Team Development Step by Step 1. Identify configuration management system 3. Identify developer workspaces 2. Identify integration workspace 4. Define integration strategy 5. Create virtual pathmap symbols 7. Determine controlled units and place them under CM control 6. Provide access to the configuration management tool
Rose will automatically make a package a controlled unit when the package is added to a version control system
Nested packages should also be controlled units
Allows two developers to check out packages “belonging” to the same higher level package
Team Development Example LARRY Y:model_vobdatabase.cat, register.cat, errors.cat CURLY X:model_vobdatabase.cat, register.cat, errors.cat Z:model_vobdatabase.cat, register.cat, errors.cat Get Latest Get Latest Get Latest MOE W:model_vobdatabase.cat, register.cat, errors.cat
Moe, Larry, and Curly views do not contain checked-out copies of packages in the model
The following updates need to be made
Moe needs to update database.cat
Larry needs to update register.cat
Curly needs to update errors.cat
Each developer will check out the package they need
They will have read-write access to the packages they check out of the CM system
Team Development Example LARRY Y:model_vobdatabase.cat, register.cat, errors.cat CURLY X:model_vobdatabase.cat, register.cat, errors.cat Z:model_vobdatabase.cat, register.cat, errors.cat Check out database.cat Check out register.cat Check out errors.cat MOE W:model_vobdatabase.cat, register.cat, errors.cat
Team Development Example LARRY Y:model_vobdatabase.cat, register.cat, errors.cat Z:model_vobdatabase.cat, register.cat, errors.cat Check in register.cat Larry finished his changes and asked the CM system to check-in register.cat A new version of the file is checked in on the element branch that is referenced by Larry’s view Changes to register.cat are available to other developers after it is check-in to the VOB provided their views reference Larry’s branch