Tool Mentor: Bridging Rational Rose® to Object BuilderPurposeThe Component Broker (CB) tool kit provides a bridge between the Rational Rose design domain and the Object Builder implementation domain. The Rose bridge allows the design team to move their design directly into Object Builder from Rose, and to reflect changes made in Object Builder back into the original Rose model. This reduces the amount of time spent developing the application and ensures that the implementation in Object Builder matches the original design. Related Rational Unified Process activity: Activity: Design Implementation Model. Overview
1. Prepare the Rational Rose
environment
The bridging process requires the Rational Rose Developer's edition or the Enterprise edition (preferred). Follow the instructions in the Component Broker Application Development Tools Guide to prepare Rational Rose prior to attempting a bridge. The setup procedure is provided section "Using Rational Rose with Object Builder". In addition, the Component Broker .cat file may be imported into Rose to allow designers to specify inheritance from Managed Object Framework (MOFW) classes. The .cat files are as follows:
2. Create the Rational Rose model
The Rational Rose model must be structured appropriately to allow team development with Object Builder.
3. Bridge the Rational Rose
model to Object Builder
4. Verify the Object Builder model
Once the model is bridged, verify the Object Builder model. This operation is necessary because the Rational Rose Bridge will not add any references in the Object Builder model that will cause the model not to compile. So, when the bridge finds a reference to a class that will not be included in the Object Builder model, it will not add it to the Object Builder model. Instead, it will write a log entry in the .tmp file. There is one .tmp file for each Object Builder project. This file is located in the project directory. Using the collated file, make the following changes to the various Object Builder projects:
5. Update the Rational Rose model
A Rational Rose model can be modified and re-bridged. However, certain restrictions need to be considered when doing so. Changing scope from public to private will not remove the public interface during a re-bridge. Deletions in the Rose model will not propagate and delete the corresponding elements from the Object Builder model. A class that is moved from one project to another will create a new class in the second package, but will not remove the class from the original package. This information is provided by IBM
Corporation
© Copyright IBM Corporation 1999-2000 |
|
Rational Unified
Process |