Introduction To Rational Rose 98i

Intro to Rose 98i Instructor Notes
Introduction to Rational Rose 98i

Module 2: Introduction
Introduction to Rational Rose 98i v 5.2 Copyright 1993-1999 Rational Software, all rights reserved
Objectives: Introduction
On completion of this module participants will be able to:
Discuss the different views supported by Rational Rose 98i List the diagrams for each view Discuss elements common to each view Configure the Rational Rose 98i interface
What is Rational Rose 98i?

Rational Rose 98i is a tool with the capability to create, view, modify, and manipulate components in a Rose model Rational Rose 98i supports the Unified, Booch, and OMT notations Rational Rose 98i is available in three editions:
Rational Rose 98i Modeler Rational Rose 98i Professional for C++, Java, or Visual Basic Rational Rose 98i Enterprise
Introduction to Rational Rose 98i v 5.2 Copyright 1993-1999 Rational Software, all rights reserved 3
Page 1
Module 2 - Introduction 1
Rational Rose 98i Features

Feature UML modeling Mulit user support Visual Differencing/Merge Framework Wizard MS Repository Integration Source Code Control Integrations Data Access Add-in RoseLink Partner Support Extensibility Integration Web Publisher X X X X X X Modeler X X X Professional X X X Enterprise X X X X X X X X X X
Rational Rose 98i Features

Feature Basic Report Generation COM Component Reverse Engineering Corba 2.x Database Schema Generation C++ (including Visual C++) Java Visual Basic Oracle 8 X X C++ edition Java edition VB edition X X X X X X X Modeler X Professional X Enterprise X
What is a Rose Model?

A Rose model is a representation of the problem domain and system software
Each model contains views, diagrams, and specifications to visualize and manipulate the elements in the model There are many views of each underlying element Every object in the design is represented once in the Rose model Rose maintains a consistent semantic representation in the model
Page 2
Use Case View Diagrams

Elements in the use case view may be viewed in one or more diagrams The use case view contains any or all of the following diagrams
Use case diagrams Packages, actors, use cases, and relationships Interaction diagrams (sequence diagrams and/or collaboration diagrams) Objects and messages Activity diagrams Activities, transitions, forks, joins, decisions,
and swimlanes
Use Case Diagram

A use case diagram shows what should be performed by the system and what exists outside the system
It shows the existence of actors (outside the system), use cases (what should be performed by the system), and their relationships A use-case diagram may depict all or some of the use cases of a system
Interaction Diagrams
Interaction diagrams show the existence of objects and their relationships in the logical design of a system
They may represent all or part of the object structure of a system
There are two kinds of interaction diagrams, each shows a different view of the same interaction
A sequence diagram shows object interactions arranged in time sequence A collaboration diagram is organized around the objects and their links to each other
Page 3
Logical View Diagrams

Elements in the logical view may be viewed in one or more diagrams The logical view contains any or all of the following diagrams
Class diagrams Packages, classes, and relationships State diagrams States, events, and transitions
10
Class Diagram
A class diagram depicts the static view of the system
It shows the existence of packages, classes, and their relationships in the logical design of a system A class diagram may represent all or part of the class structure of a system
There are typically many class diagrams in a model
11
State Diagram
A state diagram is created for classes with significant dynamic behavior A state diagram shows:
The state space of a given class The events that cause a transition The actions that result from a state change
12
Page 4
Component View Diagrams

Elements in the component view may be viewed in one or more component diagrams A component diagram shows the allocation of classes and objects to components in the physical design of a system
A component diagram may represent all or part of the component architecture of a system
A component diagram shows packages, components, and dependencies
13
Deployment View Diagrams

Elements in the deployment view may be viewed in the deployment diagram
The deployment view contains only one deployment diagram
The deployment diagram shows the allocation of processes to processors in the physical design of a system A process diagram shows
Nodes Connections
14
The Rose User Interface

Rose consists of:
Standard toolbar Diagram toolbar Browser Documentation window Diagram windows Specifications Status bar
15
Page 5
Rational Rose
Standard Toolbar
Browser
Documentation Window Status Bar Diagram Toolbar

Diagram Window
Rose Standard Tool Bar

The Rose tool bar is independent of the diagram window that is currently open
Create new model Save model or log Print Diagrams View Documentation Browse Interaction Diagram Browse Deploym ent Diagram Browse Previous Diagram Zoom Out Undo Fit in Window
Copy
Open existing model
Cut
Paste
Context Sensitive Help
Browse Class Diagram
Browse Component Diagram
Browse Parent
Zoom In
Fit in Window
17
Rose Browser
The Rose Browser is used to textually view and navigate between the components in each of the views
A + sign next to an icon indicates that the icon is collapsed A - sign next to an icon indicates that the icon is fully expanded
The Browser can be

Visible or not visible Docked (positioned along a border) or floating (moved to any location)
Page 6
The Documentation Window

The Documentation Window is used to create, view, and/or modify the documentation for a selected item on a diagram
There is only one Documentation Window, which is updated as different items on a diagram are selected
The Documentation Window

May be visible or hidden May be docked or floating
19
Specifications
Most modeling elements have a Specification that contains additional information about the modeling element
20
Documentation Window and Specifications

Information added to the documentation window is automatically added to the documentation field in the appropriate specification
21
Page 7
Notes
A note may be attached to any element in a diagram
22
Linking Diagrams
Diagrams may be linked by using a note
23
Configuring the User Interface

The Rose User Interface may be customized to:
Display or not display the toolbars Add/remove buttons from the toolbars Display or not display the browser Display or not display the documentation window Make the toolbars, browser, and/or the documentation window docked or floating
24
Page 8
Rose Options
General
Fonts, use of backup files, save settings
Diagram
Display attributes, operations, visibility, focus of control, numbering for interaction diagrams, unresolved references adornments, automatic resize, snap to grid
Browser
Stereotype naming conventions
25
Rational Rose 98i Options

Notation
Default notation -- UML, Booch, or OMT Default language -- Analysis, C++, Java, or Oracle8
Toolbars
Toolbar display and customization DDL, IDL, Java, Oracle8, C++, MSVC, Visual Basic Create/modify/delete property sets for code generation
26
The Framework Wizard

Rational Rose 98i Enterprise has a Framework Wizard, which is started when a new model is created
Contains a library of frameworks that can be used as templates when creating new models Provides you with a mechanism to create additional frameworks
27
Page 9
The Framework Wizard
28
Pathmaps
The pathmap mechanism of Rational Rose 98i allows you to map an absolute path to a virtual path Example:
$MYPATH = Z:\Registration Rose will use the virtual path when the model is saved
This provides the flexibility needed to facilitate team development
29
Pathmap and &

An absolute path set to & represents the directory containing the Rose .mdl file Example
$CURDIR = & and $MYPATH = X:\registration Model file registration.mdl stored in X:\registration $CURDIR is used instead of X:\registration
30
Page 10
Defining Pathmaps
31
Exercise: Setting up Rational Rose 98i Set up the Rose user interface for this course
If you are using Rose Enterprise, do NOT use a framework (hit Cancel on the Framework Wizard) Choose the following options (defaults may be used for all the other options) Do not show all attributes Do not show all operations Show operation signatures Do not use focus of control
Exercise: Setting up Rational Rose 98i Add the pathmap CURDIR = & and ROSE_COURSE set to your working directory Save the model as registration.mdl
33
Page 11

Introduction To Rational Rose 98i

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Introduction To Rational Rose 98i

Uploaded by

Copyright:

Available Formats

Intro to Rose 98i Instructor Notes