Aim :-Study and usage of open proj.

Introduction to Rational Rose

Rational Rose is an object-oriented Unified Modeling Language (UML) software design tool
intended for visual modeling and component construction of enterprise-level software
applications. In much the same way a theatrical director blocks out a play, a software
designer uses Rational Rose to visually create (model) the framework for an application by
blocking out classes with actors (stick figures), use case elements (ovals), objects
(rectangles) and messages/relationships (arrows) in a sequence diagram using drag-and-drop
symbols. Rational Rose documents the diagram as it is being constructed and then generates
code in the designer's choice of C++, Visual Basic, Java, Oracle8, Corba or Data Definition
Language.

Rational Rose Interface

Fig:1 Interface Of Rational Rose

1. Menu bar: The menu bar consists of several menus like the file menu, edit menu,
view menu etc. All these menus contain several options.
2. Toolbar: The toolbar contains the most frequently used actions like New, Open, Save
etc.
3. Status bar: The status bar at the bottom displays status messages.
4. Browser Window: The browser window displays the views: Use Case View, Logical
View, Component View and Deployment View. Each of these views contains the
diagrams.
5. Diagram Toolbar: The diagram toolbar displays the symbols of the respective type
of diagram.
 6. Diagram Window: The diagram window is the place where the user draws the
diagrams using the symbols from the diagram toolbar.
7. Log Window: This window is used to display error messages, warnings and
information messages.
8. Documentation Window: This window is used to display the documentation related
to the symbols and other aspects [1].

The UML models act as an architectural blueprint for software development. The Good
models requires following key points-:
 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 across your team through the use of common graphical
language.

Usage
1. Modeling can be useful at any point in the application development process.
2. Initial Design Work (Requirement Analysis and Definition)
 Use Cases
 Class Diagrams
 Sequence Diagram [2].

Demonstration view of Software

Fig.2 Person’s diagram model

 Fig:3Server model [3]

References
1. http://www.cs.ecu.edu/sartipi/courses/SE/f09/LABS/LAB_3/RationalRoseTutorial.pd
f
2. https://www.slideshare.net/MunaamMunawar/introduction-to-rational-rose
3. https://whatis.techtarget.com/definition/Rational-Rose