Rose model to import details

The Rational Rose sample model focuses on 15 diagrams accessible from the Start Here diagram in the Logical view. This diagram serves as a beginning point and overall table of contents (TOC) for the sample model. Each note that resides on the Start Here diagram contains a hyperlink to the corresponding diagram; just double-click any note to automatically navigate to the diagram.

In addition to the diagrams, the Rose model also contains packages with Java and C++ source code used in Rose round-trip engineering (RTE). You can use this code to experiment with and help understand the Software Architect visual editing and transformation capabilities. For details on how to move your application code into Software Architect, refer to this IBM developerWorks article: How to migrate from code-centric to model-centric development using Rational Software Architect.

The following sections include the name of each featured diagram (including the diagram type), along with a short summary of the differences that appear on each diagram. Refer to the actual diagrams in the model to see the differences.

01 Basic Use Case (Use-case diagram)

The imported diagram looks very similar to the original; however, the imported diagram does not contain the (from Model Items) parent name. Software Architect and Software Modeler do not support a similar capability that shows the short version of the parent name in the diagram editor.

Tip: In your imported diagram, you can display the parent name through the Show Parent Name display option; however, this option displays the fully qualified name, which is typically long and may clutter the diagram editor, depending on the diagram.

02 Include, Extend, Generalize (Use-case diagram)

In the imported model, you may want to manually adjust some of the use cases so the use-case names do not overlap each other.

03 Common Use Case Stereotypes (Use-case diagram)

During the import process, use-case realizations import as UML 2.0 collaborations. In the diagram editor, collaborations contain the name label within the ellipse shape rather than below it, so the collaboration appears larger than in Rose.

Tip: You can eliminate larger sized collaboration shapes in the diagram editor by clearing the Use Case check box on the Preferences page of the Rose Model Import wizard (the last page of the wizard).

04.1 Evaluate Loan Request - Activity Flow of Events (Activity diagram)

In the imported diagram, notice the structured activity nodes, which are different from previous versions of UML. Activity diagrams changed significantly in UML 2.0.

04.2 Evaluate Loan Request Activities, Swimlanes (Activity diagram)

During the import process, transitions between activities import as UML 2.0 control flows. In the diagram editor, longer diagram element names are truncated to fit within the diagram element.

04.3 Evaluate Loan Request sequence (Sequence diagram)

The text that appears above the lifeline heads in Rose appears behind the lifelines in the imported model. UML 2.0 sequence diagrams place all lifeline heads at the top of the diagram except when they are created by creation messages.

In the Rose model, the sequence diagram is owned by a use case. In the imported model, the diagram is owned by an interaction. Interactions are the only model elements that can own sequence diagrams in UML 2.0.

Communication diagrams do not show return messages.

Use cases cannot own interactions. Collaborations reference interactions from the use case as a subject classifier.

The business modeling stereotypes icons do not appear on lifelines in interaction diagrams.

04.4 Evaluate Loan Collaboration (Communication diagram)

In UML 2.0, collaboration diagrams have been renamed to communication diagrams.

In the Rose model, the collaboration diagram is owned by a use case. In the imported model, the diagram is owned by an interaction. Interactions are the only model elements that can own communication diagrams.

Return messages do not appear in communication diagrams.

The business modeling stereotypes icons do not appear on lifelines in interaction diagrams.

05.1 Use Case Realization Traceability Diagram (Class diagram)

The use cases stereotyped as use-case realizations import as collaborations.

In the imported model, you may want to manually adjust the collaborations (with a use-case realization keyword) in the diagram editor. While use-case realization names appear underneath the diagram element in the Rose diagram, the name compartment appears within the diagram element in the imported model. Due to this difference, the collaboration diagram elements are larger in the imported diagram and the diagram looks a little different than the Rose original.

05.2 Generate Normal Payment Notice Use Case Realization (Sequence diagram)

In the Rose model, this diagram is owned by a use case. In the imported diagram, the diagram is owned by a collaboration. Interactions are the only model elements that own sequence diagrams.

05.3 View of Participating Classes (Class diagram)

Multiplicity notation is slightly different in UML 2.0. In Rose and UML 1.4, a simple n represents an unlimited upper bound; in UML 2.0, an unlimited bound is represented by an asterisk (*).

05.4 Withdraw funds From Checking State Diagram (State diagram)

In UML 2.0, state diagrams have been renamed to state machine diagrams.

In the imported model, some of the transition labels need to be manually adjusted. The start and end state label names should be adjusted as well.

In the Model Explorer view, notice that all of the model elements that appear in the diagram are owned by a region.

06.1 C++ Implementation Package Overview and 06.2 Java Implementation Package Overview (Class diagrams)

The imported diagrams look very similar to the original diagrams in Rose.

Important: The Rational Rose model import process does not import code associated with your model. You must import your code using the standard Eclipse capabilities.

07 Main Component Diagram (Component diagram)

In the imported diagram, the components in the diagram editor do not have the classic component shape, as in Rose.

08 Deployment Loan Processing System (Deployment diagram)

The processor shapes that appear in the Rose deployment diagram import as execution environments. The connection relationships that connect the processors import as communication path relationships.

Due to differences in name labels between each tool, you may need to resize some of the execution environment shapes to clearly read the name labels.

Duplicate GUIDs

Duplicate GUIDs are retained as a prefix of the one that the Rose Model Import wizard generates; the wizard attaches the suffix _0, _1, and so on to the duplicates.