Download - Cs554 Introduction to Rational Rose 12219
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
1/30
CS 554
TutorialIntroduction to Rational Rose
Jignesh Patel
Teaching AssistantEmail:Jignesh [DOT] Patel [AT] umkc [DOT] edu
The contents of this tutorial is derived from the Rational Rose Manual
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
2/30
Introduction to Rational Rose What is visual modeling?
Visual modeling is the process of graphically depictingthe system to be developed.
Visual modeling allows you to present essential detailsof a complex problem and filter out the nonessentialdetails.
It also provides a mechanism for viewing the system
to be developed from different perspectives.
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
3/30
Introduction to Rational Rose Why should I model my software?
Designing a model for software systems is as essential ashaving a blueprint for a large building. Good models:
identify requirements and communicate information focus on how system components interact, without gettingbogged down in specific details
allow you to see relationships among design components improve communication across your team through the use
of a common, graphical language
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
4/30
Introduction to Rational Rose
Why should I use Rational Rose?
There are a number of reasons to use Rational Rose foryour development work. Here are just a few:
Model-driven development results in increased developerproductivity. Use-case and business-focused development results in
improved software quality.
Common standard language--the Unified ModelingLanguage (UML) --results in improved team communication.
Reverse-engineering capabilities allow you to integrate withlegacy OO systems.
Models and code remain synchronized through thedevelopment cycle.
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
5/30
Introduction to Rational Rose
Rose Enterprise supports multiple languages including (VC++, VB, Java, and
CORBA)
The Rose graphical user interface
The most common elements are: Standard toolbar Diagram toolbox Browser Diagram window
Documentation window SpecificationsThese items are briefly discussed in subsequent slides.How, where, and why each of these elements is used willbecome clearer as you progress through the tutorial.
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
6/30
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
7/30
Introduction to Rational Rose
Views
Just as there are many views of a house under construction the floor plan, the wiring diagram, the elevation plan, thereare many views of a software project under development.
Rational Rose is organized around the following views ofa software project:
Use Case Logical
Component
DeploymentEach of these views presents a different aspect of themodel and is explained in subsequent slides.
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
8/30
Introduction to Rational Rose
The use-case viewThe use-case view helps you to understand and use thesystem. This view looks at how actors and use cases interact.The diagrams in this view are: Use-case diagrams Sequence diagrams Collaboration diagrams Activity diagrams
This view contains a Main diagram by default. Additionaldiagrams can be added throughout the analysis and designprocess.
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
9/30
Introduction to Rational Rose
The logical viewThe logical view addresses the functional requirements ofthe system. This view looks at classes and theirrelationships. The diagrams in this view are:
Class diagrams Statechart diagramsThis view contains a Main diagram by default. Additionaldiagrams can be added throughout the analysis anddesign process.
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
10/30
Introduction to Rational Rose
The component view
The component view addresses the software organizationof the system. This view contains information about thesoftware, executable and library components for the
system. This view contains only component diagrams.The component view contains a Main diagram by default.Additional diagrams can be added to this view throughout
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
11/30
Introduction to Rational Rose
The deployment view
The deployment view shows the mapping of processes tohardware. This type of diagram is most useful in adistributed architecture environment where you might
have applications and servers at different locations. Thisview contains only one diagram the deploymentdiagram.
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
12/30
Introduction to Rational Rose
Diagrams Simply put, a diagram is a graphical representation of the
elements of your system. Different diagram types allow you to view your system from
multiple perspectives.
You can create various types of diagrams in Rational Rose.The diagram types include: Use-Case Class Activity Statechart
Component DeploymentEach of these diagram types is explained in subsequent slides.
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
13/30
Introduction to Rational Rose
Use-case diagrams Use-case diagrams present a high-level view of system
usage as viewed from an outsiders (actors) perspective.
These diagrams show the functionality of a system or a
class and how the system interacts with the outside world. Use-case diagrams can be used during analysis to capturethe system requirements and to understand how thesystem should work.
During the design phase, use-case diagrams specify thebehavior of the system as implemented.
Rose automatically creates a Main use-case diagram inthe use-case view. There are typically many use-case diagrams in a single
model.
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
14/30
Use-case Diagram
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
15/30
Introduction to Rational Rose
Class diagrams A class diagram helps you visualize the structural or
static view of a system and is one of the mostcommon diagram types.
Class diagrams show the relationships among anddetails about each class.
Class diagrams are also the foundation forcomponent and deployment diagrams.
Rose automatically creates a Main class diagram inthe logical view. There are typically many class diagrams in a single
model.
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
16/30
Class Diagram
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
17/30
Introduction to Rational Rose
Sequence diagrams A sequence diagram illustrates object interactions
arranged in a time sequence. These diagrams are typically associated with use
cases. Sequence diagrams show you step-by-stepwhat has to happen to accomplish something in theuse case.
This type of diagram emphasizes the sequence ofevents, whereas collaboration diagrams (analternative view of the same information) emphasizethe relationship.
This type of diagram is best used early in the designor analysis phase because it is simple and easy tocomprehend.
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
18/30
Sequence Diagram
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
19/30
Introduction to Rational Rose
Collaboration diagrams Collaboration diagrams provide a view of the
interactions or structural relationships between
objects in the current model. This type of diagram emphasizes the relationship
between objects whereas sequence diagramsemphasize the sequence of events.
Collaboration diagrams contain objects, links, andmessages.
Use collaboration diagrams as the primary vehicle todescribe interactions that express decisions aboutsystem behavior.
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
20/30
Collaboration Diagram
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
21/30
Introduction to Rational Rose
Activity diagrams Activity diagrams model the workflow of a business
process and the sequence of activities in a process.
These diagrams are very similar to a flowchartbecause you can model a workflow from activity toactivity or from activity to state.
It is often beneficial to create an activity diagramearly in the modeling of a process to help youunderstand the overall process.
Activity diagrams are also useful when you want todescribe parallel behavior or illustrate how behaviorsin several use cases interact.
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
22/30
Activity Diagram
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
23/30
Introduction to Rational Rose
Component diagrams Component diagrams provide a physical
view of the current model.
They show the organization anddependencies among software components,including source code, binary code, andexecutable components.
You can create one or more componentdiagrams to depict components andpackages or to represent the contents ofeach component package.
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
24/30
Component Diagram
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
25/30
Introduction to Rational Rose
Statechart diagrams You can use statechart diagrams to model the
dynamic behavior of individual classes or objects.
Statechart diagrams show the sequences of statesthat an object goes through, the events that cause atransition from one state or activity to another, andthe actions that result from a state or activity change.
A statechart diagram is typically used to model thediscrete stages of an objects lifetime, whereas an
activity diagram is better suited to model thesequence of activities in a process.
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
26/30
Statechart Diagram
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
27/30
Introduction to Rational Rose
Specifications
Specifications are dialog boxes that allowyou to set or change model elementproperties.
Changes made to a model element eitherthrough the specification or directly on
the icon are automatically updatedthroughout the model.
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
28/30
Specifications
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
29/30
What next?
Start Requirements and Architecture phase Deliverables
Requirements Concept Map Context Diagram Use Case Diagram Use Case Goals & Steps System Interface Non-functional Requirements
Architecture Structure (Object Diagram) Components & Interfaces Component Collaborations Architecture Class Diagram
Due date: September 28th 2005
-
7/31/2019 Cs554 Introduction to Rational Rose 12219
30/30
Questions ?