Rational Rose

Rational Rose Tutorial
Anis Yousefi
Teaching Assistant SE3KO4 / SE3MO4 Software Development for Computer and Electrical Engineering Email: yousea2@mcmaster.ca

Introduction to Rational Rose

1

Objectives
 



Get to know Rational Rose Get Familiar with general functions of Rational Rose for Modeling Create UML Diagrams with Rational Rose

Introduction to Rational Rose

2Assumption


You are familiar with Unified Modeling Language (UML)

• Either

• Read a book on UML • Been trained in UML • Used UML on work project



You are familiar with object oriented software

Introduction to Rational Rose

3

Access To Rational Rose
 

Available at student lab Can download full version from Rational

• 15-day trial license

Introduction toRational Rose

4

What is Rational Rose?
 



ROSE = Rational Object Oriented Software Engineering Rational Rose is a set of visual modeling tools for development of object oriented software. Visual Modeling is the process of graphically depicting the system to be developed

• • •

Presenting essential details Filtering out non-essential details Viewing the system from differentperspectives

Introduction to Rational Rose

5

Why Model?
 

The UML models act as an architectural blueprint for software development. Good models:

• • • •

Identify requirements and communicate information Allows focus on how system components interact, without get bogged out in specific details Allows you to see relationships among design components Improves communication acrossyour team through the use of common graphical language

Introduction to Rational Rose

6

Visual Modeling Tools May Help Mitigate these Problems
   



Software that poorly fits user needs Inability to deal with changing requirements Software integration problems Discovery of serious flaws too late in the project Software that is hard to maintain and extend

Introduction toRational Rose

7

When Should ROSE be Used?
 

Modeling can be useful at any point in the application development process. Initial Design Work (Requirement Analysis and Definition) • Use Cases • Class Diagrams • Sequence Diagram Spend your time dealing with issues such as the planned uses of software system and how you will implement a programming environment to address these issues--not whereand how you are going to place the buttons on your first screen.
Introduction to Rational Rose

8

When Should ROSE be Used?
 

Refinement of Early Models (System & Software Design) Introduced in Middle of Project • Rational Rose includes tools for reverse engineering as well as forward engineering of classes and component architectures. • You can gain valuable insights to your actualconstructed architecture and pinpoint deviations from the original design. • Rose offers a fast way for clients and new employees to become familiar with system internals

Introduction to Rational Rose

9

Rose


Rose Enterprise:

• • • • • • • •

Supports multiple languages, including VC++, VB, Java, CORBA Standard ToolBar Diagram ToolBox Browser Diagram Window Documentation WindowSpecifications Log Window



Rose GUI:

Introduction to Rational Rose

10

Diagram Toolbox

Browser Window Your model is Really in HERE!

Diagram Window

Documentation Window Log Window
Introduction to Rational Rose

11

Rational Rose Interface


The Rose standard toolbar (near the top of the window)

• • • • • •

is always displayed - independent of the currentdiagram type. While in Rose, place your cursor over the toolbar to display a tooltip for each icon.



The browser
a hierarchical navigational tool allowing you to view the names and icons representing diagrams and model elements. The plus (+) sign next to an icon indicates the item is collapsed and additional information is located under the entry. Click on the + sign and the tree is...