1. Advance Software Engineering LAB # 02
LAB #02
OBJECTIVE:
• Introduction To IBM Rational Rose.
What is visual modeling?
• Visual modeling is the process of graphically depicting the system to be developed.
• Visual modeling allows you to present essential details of a complex problem and filter out the
nonessential details.
• It also provides a mechanism for viewing the system to be developed from different perspectives.
Why should I model my software?
Designing a model for software systems is as essential as having a blueprint for a large building. Good
models:
• Identify requirements and communicate information·
• Focus on how system components interact, without getting bogged 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
Why should I use Rational Rose?
There are a number of reasons to use Rational Rose for your development work. Here are just a few: ·
• The tool provides the capability to
• Identify and design business objects, and then map them to software components
• Partition services across a three-tiered service model
• Design how components will be distributed across a network
• Generate Visual Basic code frameworks directly from your model
• Use reverse engineering to create models from existing components and applications
• Use round-trip engineering facilities to keep your designs synchronized with your code
• Rational Rose extends dynamic behaviors, such as business requirements analysis, business
scenario analysis with sequence and collaboration diagrams, state modeling, and additional code
generation capabilities for DDL and IDL, along with the inclusion of a scripting language to
provide access.
• Model-driven development results in increased developer productivity.
• Use-case and business-focused development results in improved software quality.
• Common standard language--the Unified Modeling Language (UML) --results in improved team
communication.
• Reverse-engineering capabilities allow you to integrate with legacy OO systems.
• Models and code remain synchronized through the development cycle.
1

2. Advance Software Engineering LAB # 02
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
• Specifications
These items are briefly discussed in subsequent slides. How, where, and why each of these elements is
used will become clearer as you progress through the tutorial.
The Standard Toolbar remains the same for all views and diagrams. It contains standard Windows
functions as well as those specific to Rational Rose Real Time. The Diagram Toolbox is used for adding
elements to the model by drawing them on a diagram. The toolbox elements change depending on the
active diagram. For example, the Use-Case Diagram has a tool for adding actors, but the Component
2

3. Advance Software Engineering LAB # 02
Diagram does not have this tool. Browsers are hierarchical and can be expanded and contracted. When
you start Rational Rose Real Time, the Model View, the Containment View, and the Inheritance View
browsers are docked on the left side of the interface in a stacked format. They can be set to
visible/invisible, docked, or floating. To activate a specific browser, select the appropriate tab located at
the bottom of the interface. There are two additional browsers, also referred to as editors, which can be
opened to perform specific tasks: the Structure/State Diagram Browser/Editor, and the Run Time System
(RTS) Browser/Editor. These browsers cannot be moved.
Rational Rose Real Time offers four main views located on the Model View browser. Each view is
related to a software lifecycle phase, and the diagrams are artifacts of those phases. Use-Case View shows
what a system (subsystem, class, or interface) does but does not specify how the system internally
performs its tasks. Logical View represents the architectural processes as the model moves from analysis,
through design, and into development. Component View contains concrete representations of the system.
Components realize the active and data classes, and provide the components for building an executable
model. Deployment View shows how the system is to be distributed. It defines the processors, and
contains a diagram of the nodes in the system.
Rational Rose is organized around the following views of a software project:
• Use Case Views
• Logical Views
• Component Views
• Deployment Views
Each of these views presents a different aspect of the model and is explained in subsequent slides.
The use-case view
The use-case view helps you to understand and use the system. 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
3

4. Advance Software Engineering LAB # 02
This view contains a Main diagram by default. Additional diagrams can be added throughout the analysis
and design process.
The logical view
The logical view addresses the functional requirements of the system. This view looks at classes and their
relationships. The diagrams in this view are:
• Class diagrams
• Statec hart diagrams
This view contains a Main diagram by default. Additional diagrams can be added throughout the analysis
and design process.
The component view
The component view addresses the software organization of the system. This view contains
information about the software, 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
4

5. Advance Software Engineering LAB # 02
The deployment view
The deployment view shows the mapping of processes to hardware. This type of diagram is most
useful in a distributed architecture environment where you might have applications and servers at
different locations. This view contains only one diagram – the deployment diagram.
Diagrams
• 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
• State chart
• Component
• Deployment
5