Implement team modeling with Rational Rose and VSS
E.K (Vanguar)
September 2004
Summary
This paper tells the team that uses Ratioanl Rose to model how to integrate the two integration of the team by configuring VSS and ROSE, and also proposes a relatively mature working environment configuration plan, which reduces the team communication cost, make Team modeling is more economical and practical. For high-end users, small techniques that solve complex problems are also given.
IBM Rational Rose is currently recognized as the best modeling tool in the industry. Many articles have introduced how to use ROSE to model design, but in actual project work, especially in large and medium-sized software projects, it is often impossible to complete the whole. Modeling work must be worked by the entire team. Then you will inevitably use version control tools, like Microsoft Visual Source Safe (VSS) is also a very common version control tool. This article will explain how to use the Rational Rose and VSS to achieve team modeling using Rational Rose and VSS.
First, install IBM Rational Rose Enterprise 2003
See Rose 2003 Installation Manual.
Second, install Microsoft Visual Source Safe 6.0B
To incorporate projects into the version control system, you must first create a VSS database. How to establish a VSS database, see VSS Help.
Third, agreed project document organizational structure
A recognized document organization structure can be agreed according to the team's work habits or institutional requirements, and each team member's project document organizational structure must be based on this.
For example: z: / building / sample
| -DOC
| -Business
| -Model
| -Reqirement
| -Reference
| -Projects (subproject)
| -P1
| -DOC
| - ...
| -Model
| -P2
| - ...
| -P3
| - ...
For the drive where the project directory is located, it is recommended to use a relatively large letter as the drive letter, such as: x, y, z, etc., which can minimize conflicts. It can be implemented by mapping. Click [Start] -> [Run ...] -> Enter CMD to enter the DOS operator, enter the command:
Microsoft Windows 2000 [Version 5.00.2195]
(C) All rights reserved 1985-2000 Microsoft Corp.
C: /> Subst Z: f: / my /
Figure 1 A typical project file organization structure
Fourth, set the virtual path mapping directory (Virtual Path Map)
Each team member should set the virtual path according to the actual situation of the workman. The specific method is: enter [file] -> [edit path map ...], pop-up Virtual Path Map dialog:
Figure 2 Virtual Path Settings Dialog
Enter: Key Symbol, actual path Actual, comment comment, click Add to add path to the virtual path map.
The recommended settings are as follows:
$ Curdir = & // & represents the current model file. MDL location path
$ Root = z: / building / / item root directory, all information related to the model file will be in this directory and its subdirectory
$ Sample = $ root / doc / model / / project model file directory
$ P1 = $ root / sample / projects / p1 / doc / model // p1 project model file directory $ p2 = $ root / sample / projects / p2 / doc / model // p2 project model file directory
According to the method settings described above, it is possible to ensure that the path in the CAT package in the model file is the relative path, avoiding the case where the path in different machines is different, and cannot open the link.
2 Note: The $ root path on each machine may also allow different, but it is recommended to use the same drive path. Other mapping paths are not allowed, which avoids unnecessary communication costs.
For example: team member Lee $ root = x: /
Team member Yee's $ root = Y: Y: / working / projects
Team member liu $ rott = z: / building /
V. VSS environment initialization
Initialize the VSS environment, you need to do the following things:
1. Assign a username in the VSS server side to each team member. To simplify operations, usernames and passwords should be the same as the username and password logged in on the member client. This way, you can prompt your username and password without each open VSS. It is particularly noted that the server operating system in which the VSS server must also set the same username and password, but the security should be appropriately changed as needed.
2. Each team member should set up a local working directory. Select root node $ /, press Ctrl D, pop up the [Setup Work Directory] dialog. This path should be the same as the ROOT path set in front.
3. The project configuration manager establishes a full project structure and configures the security of each Project. A relatively easy way is to select the root directory -> show Difference, all of which exist locally and the directory that does not exist in the VSS database are added to the database. In fact, there is no data in the VSS database in the VSS database in the first time, so all local directory and files will be added to the database.
6. Implement VSS operation in Rose
Since VSS is a system that complies with SCC specification, Version Control plugins through ROSE can be seamlessly integrated with VSS.
The main operations of using VSS implementation version control include: Add, Check Out, Check IN, Get Latest Version.
For a complex project with multiple sub-projects, the subcontract is an essential choice, and it is also necessary to put the package of each sub-item in the respective project catalog.
1. Add the package to the VSS, select the package to press Add to Version Control, pop up the Add to Version Control dialog, select the package you want to join, which will be saved to the same name .cat file in the current directory.
2. To customize the save package, you can select the package to right click units-> Contra
...
, Save the package to another directory.
3. To add other CAT packets to the model file, you can select a package, then select File-> Units-> Load ..., add additional packages to the model file, when other people modify the package, it can be reflected In the model file.
4. By selecting the package, press the right click check out to get the permissions of the package.
5. By selecting the package, press the right click Check IN to update the package modification results.
6. It is recommended to have the authority of the CHECK IN, Check Out model file by the project person in charge.
7. It is recommended to establish a model file for subprojects for each sub-project to share design packages with the project model file.
2 Note: Through the subcontract, you can ensure that the teams in the team are in the team, while also sharing the results of work. The security setting of VSS also guarantees that the results will not be modified freely. Seven, informal solutions
For some very special situations, it is not possible to achieve or complicated through normal methods. So this time we can solve problems quickly by directly modifying the source file.
2 Note: I only recommend a user who is very familiar with ROSE, and make a backup before operation.
For example: the original Virtual path map configuration $ root = z: / building / joa, we modified to $ root = z: / building, then open the previously modified model file, this time is incorporated when introducing a sub-package Error message:
We will find the following tips when you view the log:
09: 00: 59 | WARNING: The Directory Z: / Building / Projects / JCM / DOC / Model Does Not Exist.
This is because after modifying the Virtual Path, the relative address in the model file changes, according to the previous settings, it is naturally unable to find the file, even if it happens to find it, it is not an expected file.
Use Notepad or text editor like EditPlus, open the .mdl file, find jcm.cat we can find like this:
Logical_Models (List unit_reference_list
(Object Class_category "Business Object Model"
IS_UNIT TRUE
IS_LOADED FALSE
File_name "$ curdir // business object model.cat"
Quid "412f4917009a")
(Object Class_category "JCM"
IS_UNIT TRUE
IS_LOADED FALSE
FILE_NAME "$ root // projects // jcm // doc // model // jcm.cat"
Quid "3D256AB500B8"))))
The basic properties of a part of the subcaps in the Logical View package are described herein, where file_name refers to the file name stored by the package. The premise of such a description is that the Business Object Model package and JCM package are already a CONTROLLED UNIT to join the Add to Version Control. If the $ root changes, and cannot find the .cat file through $ root // model // jcm.cat, then we can modify this path, for example: $ root // joa //Projects//jcm//doc/model//jcm.cat, after saving, reopen the model file, everything is OK!
The same solution can also be used on a modified version control information, for example:
(Object Attribute)
Tool "SC"
Name "SourceControlProject"
Value (Value Text
| "$ / Projects / JCM / DOC / Model", FFuaaaaa
))
