Experiment – 8
Case Study on Rational Rose Tool
Key Features of Rational Rose:
1. UML-Based Modelling: Rational Rose enables users to create
UML diagrams such as class diagrams, use case diagrams,
sequence diagrams, and more, facilitating the representation of
system components and their interactions.
2. Visual Design Environment: With a graphical interface, users can
easily drag and drop elements to design and visualize system
architecture and its components.
3. Code Generation: The tool can generate skeleton code for multiple
programming languages like Java, C++, and Visual Basic,
speeding up the transition from design to implementation.
4. Reverse Engineering: Rational Rose can convert existing code into
UML diagrams, helping developers understand and manage
legacy or complex systems by providing a visual overview of their
structure.
5. Collaboration and Team Support: It allows multiple users to
collaborate on a project, with support for version control systems to
manage model changes.
6. Round-Trip Engineering: This ensures that modifications in the
model are mirrored in the code, and vice versa, maintaining
synchronization between design and implementation.
7. Platform and Language Flexibility: Rational Rose is platform-
independent and supports various programming languages,
making it adaptable for a wide range of software projects.
Characteristics of Rational Rose:
1. Unified Modelling Language (UML) Support
2. Visual Modelling Interface
3. Multiple Diagram Types:
o Use Case Diagrams: Capture system functionality and user
interactions.
o Class Diagrams: Represent the system’s static structure.
o Sequence Diagrams: Illustrate object interactions over time.
o State Diagrams: Describe object behaviour based on events.
o Activity Diagrams: Depict workflows or processes.
o Component and Deployment Diagrams: Model the system’s
physical architecture and deployment environments.
4. Code Generation
5. Reverse Engineering
6. Round-Trip Engineering
7. Team Collaboration Support
8. Integration with Development Environments
9. Component Reusability
10. Scalability
11. Simulation and Validation
12. Platform Independence
13. Customization and Extensibility
14. Documentation Generation
15. Version Control and Change Management
Common Uses:
• Object-Oriented Design: Frequently used to design object-oriented
software architectures.
• Software Documentation: Assists in documenting system
requirements, architecture, and interactions through UML
diagrams.
• System Analysis: Helps in modelling systems by analysing
component relationships, interactions, and behaviours.
• Code and Design Consistency: Ensures alignment between design
models and source code throughout the development process.
History:
Rational Rose was developed by Rational Software, which was later
acquired by IBM in 2003. It is part of the IBM Rational Suite, a collection
of tools aimed at supporting various phases of the software development
lifecycle.
