Rose Basics
Rose Basics
What is Visual Modeling What is Visual Modeling
Helps organize, visualize, and understand Helps organize, visualize, and understand complexity
complexity . .
Is the Is the mapping of real processes mapping of real processes of a of a system to a
system to a graphical representation graphical representation . .
Is a Is a proven and accepted engineering proven and accepted engineering technique.
technique.
Has a common vocabulary, the Unified Has a common vocabulary, the Unified Modeling Language (UML).
Modeling Language (UML).
Models Models
Models themselves are constructed using Models themselves are constructed using different views different views and diagrams
and diagrams to accurately depict different stakeholder to accurately depict different stakeholder perspectives and the system’s building blocks,
perspectives and the system’s building blocks, respectively.
respectively.
Models Models are are complete representations complete representations of the system. of the system.
Views Views allow different stakeholders to see the system allow different stakeholders to see the system from their own perspectives
from their own perspectives
Views contain Models… Views contain Models…
Models contain diagrams – some of these terms are ‘used’ Models contain diagrams – some of these terms are ‘used’
interchangeably…
interchangeably…
Diagrams: Diagrams: means by which we view of the system. means by which we view of the system.
Different building blocks (model elements) for different types. Different building blocks (model elements) for different types.
classes, interfaces, collaborations, components, nodes,
classes, interfaces, collaborations, components, nodes,
Process View Deployment View Logical View
Use-Case View
Implementation View
End-user
Functionality Programmers
Software management
Performance Scalability Throughput
System integrators
System topology Delivery, installation communication System engineering Analysts/Designers
Structure / Behaviors
4+1 Architectural View 4+1 Architectural View
Use Case View -
Use Case View - represents the system’s intended represents the system’s intended functions and environment
functions and environment as seen by its end as seen by its end users
users . .
Serves as a Serves as a contract contract between customer and between customer and developer.
developer.
Is Is essential essential to analysis, design and test activities. to analysis, design and test activities.
Includes use case diagrams, use case flow of Includes use case diagrams, use case flow of events, and supplemental documentation.
events, and supplemental documentation.
It can also include It can also include activity diagrams activity diagrams . .
Is the heart of and drives all other views Is the heart of and drives all other views . .
4+1 Architectural View 4+1 Architectural View
Logical View Logical View
Supports modeling the Supports modeling the functional functional requirements of the requirements of the system
system , meaning the services the system should provide , meaning the services the system should provide its end users.
its end users.
Includes analysis class modeling, use case realizations, Includes analysis class modeling, use case realizations, and interaction diagrams.
and interaction diagrams.
It can also include state-chart and activity diagrams. – It can also include state-chart and activity diagrams. – discuss.
discuss.
Much Much analysis and design analysis and design involve elements in this view. involve elements in this view.
In fact, ‘most’ analysis and design in done here… In fact, ‘most’ analysis and design in done here…
Much of this work is done in Elaboration and some in Much of this work is done in Elaboration and some in Construction
Construction
4+1 Architectural View = Rose 4+1 Architectural View = Rose
Implementation View (Component View in Rose) Implementation View (Component View in Rose)
Describes Describes organization of static software modules (source code, organization of static software modules (source code, data files, components, executables, and such
data files, components, executables, and such ) in terms of ) in terms of
packaging and layering and configuration management. packaging and layering and configuration management.
Addresses issues of ease of development, management of Addresses issues of ease of development, management of software assets, reuse, sub-contracting, and off-the-shelf software assets, reuse, sub-contracting, and off-the-shelf
components.
components.
Used in programming and testing Used in programming and testing . .
Most (almost all) of this work is done during Construction Most (almost all) of this work is done during Construction
phase. (Some done – clean up, rework… in Transition…)
phase. (Some done – clean up, rework… in Transition…)
4+1 Architectural View 4+1 Architectural View
Process View Process View
Includes the threads and processes that form the system’s Includes the threads and processes that form the system’s concurrency
concurrency and and synchronization synchronization mechanisms. mechanisms.
Addresses the performance, scalability, and throughput Addresses the performance, scalability, and throughput of the of the system.
system.
(Several of the ‘non-functional’ requirements are often addressed here.) (Several of the ‘non-functional’ requirements are often addressed here.)
Is not necessary for single processing environment Is not necessary for single processing environment . .
Deployment View Deployment View
This ‘View’ is used for distributed systems only This ‘View’ is used for distributed systems only . .
Shows how the various executables and other runtime components are Shows how the various executables and other runtime components are mapped
mapped to the to the underlying platforms or computing nodes. underlying platforms or computing nodes.
Do not confuse the Deployment View with ‘deployment’ and Do not confuse the Deployment View with ‘deployment’ and deployment artifacts as found in the Transition phase….
deployment artifacts as found in the Transition phase….
This here is an This here is an architectural View architectural View not a development Phase! not a development Phase!
State Chart Diagrams State Chart Diagrams
State Diagrams specify the sequences of states that an State Diagrams specify the sequences of states that an object can be in;
object can be in;
events and conditions that cause events and conditions that cause transition transition from one from one state to another;
state to another;
and and actions actions that take place that take place when when the next state is the next state is reached;
reached;
Can be attached to use cases to model a scenario. Can be attached to use cases to model a scenario.
Model the Model the dynamic aspects dynamic aspects of the system. of the system.
Particularly useful in modeling complex interactions Particularly useful in modeling complex interactions that may be difficult to capture in a Use Case – or to that may be difficult to capture in a Use Case – or to supplement the textual Use Case Description.
supplement the textual Use Case Description.
State Chart Diagrams State Chart Diagrams
Should be created
Should be created only when needed only when needed to to represent state-controlled class behavior.
represent state-controlled class behavior.
Statechart diagrams Statechart diagrams model the behavior of model the behavior of a single object over its lifetime.
a single object over its lifetime.
Statechart diagrams model the flow of Statechart diagrams model the flow of control from event to event.
control from event to event.
Activity Diagrams Activity Diagrams
Model the Model the workflow workflow of a business process or a class operation. of a business process or a class operation.
Sometimes considered a Sometimes considered a visual description visual description of a use case…. of a use case….
Often Often accompany accompany a Use Case description. a Use Case description.
Some Modelers prefer Activity Diagrams… Some Modelers prefer Activity Diagrams…
Are Are similar to a flowchart because you can model a workflow from similar to a flowchart because you can model a workflow from to activity or from activity to state. Really, model is much more…
to activity or from activity to state. Really, model is much more…
Are considered a special case of a state machine where most of the Are considered a special case of a state machine where most of the states are
states are activities activities and most the and most the transitions are transitions are implicitly implicitly triggered by completion of the actions in the source activities triggered by completion of the actions in the source activities . .
Models the Models the dynamic aspects dynamic aspects of the system. of the system.
Component View Component View
Component Diagrams:
Component Diagrams:
Sometimes called the Implementation View Sometimes called the Implementation View
Contains:
Contains:
source code (.cpp, …) source code (.cpp, …)
.dlls .dlls
.exes .exes
.h files .h files
.java files .java files
Typically configured into
Typically configured into packages packages of source code of source code modules, data base entities, tables, files, etc.
modules, data base entities, tables, files, etc.
Deployment View Deployment View
Deployment diagrams Deployment diagrams
Are modeled in the Deployment View. Are modeled in the Deployment View.
Show the Show the allocation of processes to processors in the allocation of processes to processors in the physical design of a system
physical design of a system . .
Represent all or part of the process architecture of a Represent all or part of the process architecture of a system.
system.
Deployment diagrams are Deployment diagrams are required required for for distributed distributed systems only.
systems only.
Show the physical aspects of the system. Show the physical aspects of the system.
Key elements Key elements
Use of Rational Rose … Use of Rational Rose …
Do the following on your own – in Do the following on your own – in
conjunction with the Visual Modeling Text.
conjunction with the Visual Modeling Text.
This text steps you through your This text steps you through your
diagramming efforts step by step.
diagramming efforts step by step.
The Rational Rose 2000 Interface The Rational Rose 2000 Interface
Browser: (see next slide) Browser: (see next slide)
Think of the browser as Rose’s Windows Explorer.Think of the browser as Rose’s Windows Explorer.
Displays the elements that you’ve modeled.Displays the elements that you’ve modeled.
If an element doesn’t appear in the browser, it is If an element doesn’t appear in the browser, it is not a part of your not a part of your modeled system.
modeled system.
May be visible or hidden; docked or floating.May be visible or hidden; docked or floating.
Documentation window Documentation window
Used to create, view, or modify text explaining a selected item.Used to create, view, or modify text explaining a selected item.
May visible or hidden; docked or floating.May visible or hidden; docked or floating.
Note that information added to the documentation window is automatically Note that information added to the documentation window is automatically added to the Documentation field for the the appropriate specification
added to the Documentation field for the the appropriate specification selected in the main window
selected in the main window. .
The Rational Rose 2000 Interface The Rational Rose 2000 Interface
Diagram window Diagram window
Allows you to create, update, and model Allows you to create, update, and model graphical views of the current model.
graphical views of the current model.
Diagram toolbar (show) Diagram toolbar (show)
Is unique to each diagram type and can be Is unique to each diagram type and can be customized.
customized.
Is active only when a diagram is displayed. Is active only when a diagram is displayed.
The Rational Rose 2000 Interface The Rational Rose 2000 Interface
The Specification window –
The Specification window – (right click on Use Case (right click on Use Case Package; Open Specification…)
Package; Open Specification…)
Is a Is a textual representation of a model element textual representation of a model element that that allows you to view and manipulate the element's allows you to view and manipulate the element's
model properties.
model properties.
Note that information added to the documentation Note that information added to the documentation window is automatically added to the documentation window is automatically added to the documentation
field in the specification window.
field in the specification window.
The Log window –
The Log window – (down at very bottom) (down at very bottom)
Reports progress, results, and errors Reports progress, results, and errors
Right-click on Log window to see available actions. Right-click on Log window to see available actions.
The Rational Rose 2000 Interface The Rational Rose 2000 Interface
The Options window (Select: view, toolbar, configure) The Options window (Select: view, toolbar, configure)
Allows you to customize Allows you to customize Rose to suit your needs. Rose to suit your needs.
For specific topic information, click ? in the upper right corner, then click the For specific topic information, click ? in the upper right corner, then click the field.
field.
Selections made in Options are your defaults. Selections made in Options are your defaults .
Make sure they are set up to your liking before you model Make sure they are set up to your liking before you model
Changing this information after a model is created does not alter existing Changing this information after a model is created does not alter existing information. For example, changing the default fill color applies to future information. For example, changing the default fill color applies to future additions. You would have to change existing elements manually.
additions. You would have to change existing elements manually.
General Can customize fonts, use of backup files, save setting.General Can customize fonts, use of backup files, save setting.
Browser - Can show stereotypes in the browserBrowser - Can show stereotypes in the browser
Notation – Notation – Can customize the notation and select a default language.Can customize the notation and select a default language.
Diagram - Diagram - Can customize features specific to display of Rose diagrams. Can customize features specific to display of Rose diagrams.
Let’s talk about the Stereotype display of this tab. Let’s talk about the Stereotype display of this tab.
Rational Rose 2000 Interface Rational Rose 2000 Interface
The Stereotype display The Stereotype display
Click on Use Case View; Main; (2C) Click on Use Case View; Main; (2C)
Actor from toolbar; Actor from toolbar;
Put into diagram; Put into diagram;
Select <<actor>>; Select <<actor>>;
right click for Open Specification…right click for Open Specification…
This option lets you select This option lets you select how you want how you want
stereotypes to appear on your diagrams
stereotypes to appear on your diagrams . .
Rational Rose 2000 Diagrams Rational Rose 2000 Diagrams
Diagrams Diagrams
- -
the means to view the system’s building blocks: classes, the means to view the system’s building blocks: classes,
interfaces, collaborations, components, nodes, dependencies, interfaces, collaborations, components, nodes, dependencies,
generalizations, and associations.
generalizations, and associations.
Eight diagrams can be modeled in Rose. Eight diagrams can be modeled in Rose.
Will use four for Requirements Gathering, Analysis and Design. Will use four for Requirements Gathering, Analysis and Design.
We will be dealing with these quite a bit. We will be dealing with these quite a bit.
Use Case Use Case
Collaboration Collaboration
Sequence Sequence
Class Class
Basic Tool Techniques Basic Tool Techniques
Add Model Elements Add Model Elements
Either Either the browser or diagram toolbar the browser or diagram toolbar . .
Browser: Right click on Use Case Diagram; Select Browser: Right click on Use Case Diagram; Select New; Select Model element.
New; Select Model element.
Toolbar: Double Click element; Place on diagram Toolbar: Double Click element; Place on diagram window; document…(See browser)
window; document…(See browser)
Elements added from the toolbar are Elements added from the toolbar are automatically added to the browser.
automatically added to the browser.
Elements added to the browser must be dragged Elements added to the browser must be dragged and dropped on to the diagram.
and dropped on to the diagram.
You can also drag and drop existing elements You can also drag and drop existing elements from the browser to other diagrams.
from the browser to other diagrams.
Basic Tool Techniques Basic Tool Techniques Delete Model Elements Delete Model Elements
Deleting from a diagram Deleting from a diagram
Removes the selected icon from the current diagram BUT does not Removes the selected icon from the current diagram BUT does not change the model unless:
change the model unless:
Deleted icon is unnamed, Deleted icon is unnamed, oror
Icon appears once in the current diagram and in no other diagram. Icon appears once in the current diagram and in no other diagram.
Note that all relationships associated with the deleted element are also Note that all relationships associated with the deleted element are also deleted.
deleted.
Delete from a diagram Delete from a diagram
Click the element in the diagram, then press Delete on your keyboard.Click the element in the diagram, then press Delete on your keyboard.
Click the element in the diagram. From the Edit menu, click Delete.Click the element in the diagram. From the Edit menu, click Delete.
Delete from the browser Delete from the browser
Removes the selected element from the modelRemoves the selected element from the model. .
Removes all icons representing the element from all diagramsRemoves all icons representing the element from all diagrams on which they on which they appear.