Object Oriented Analysis and Design Introduction to Rational Rose

Rational Rose 2  Rational Rose is a software modeling tool that  Supports the Unified Modeling Language  Allows you to create a model of software components  Allows you to draw diagrams illustrating the relationships between components  Allows you to draw diagrams of software behaviour

The Rose Interface 3

The Browser 4  The browser shows  Different view of the model  All of the software components in the model  Various diagrams of the model

Views 5  The browser shows various view of the software  These are like different view of a building  Each view shows the software from a different perspective  Use Case  Logical  Component  Deployment

The Use Case View 6  Shows how users of the system interact with the system  Captures the requirements of the system in conjunction with the GDD  Contains  Activity diagrams to explain complex operations

The Logical View 7  Captures the functional requirements of the system  Models the classes that will form the solution  Contains  Class diagrams  Statechart diagrams  Sequence diagrams

The Component View 8  Shows the main components of the software system and how they are organized  Shows how libraries are used with the system  Contains  Component diagrams

The Deployment View 9  Shows how software is mapped onto hardware  Useful for the deployment of distributed software  Contains  Deployment diagrams

The Software Model 10  The software model consists of  Classes that will be used in the solution  Diagrams illustrating  The relationship between classes  The behaviour of classes  How classes combine to form solutions  Textual documentation providing additional information not easily described in other ways

Class Diagrams 11  Show the details of classes  Show the relationships between classes

Use Case Diagrams 12  Capture system behaviour from an outsider’s perspective  Show specific cases of how the system is used  Capture the system requirements

Sequence Diagrams 13  Shows object interactions along time lines  Shows the steps involved in performing a complex action

Collaboration Diagrams 14  Show how objects collaborate to accomplish a task  Shows messages between objects  Emphasizes relationships between objects

Activity Diagrams 15  Shows the series of steps in a process  Models the business workflow

Component Diagrams 16  Shows a physical view of the model  Shows the relationship between major software components

Deployment Diagrams 17  Shows how processes are mapped onto hardware

Statechart Diagrams 18  Models the behaviour of individual classes  Shows how a classes is driven into various states by events

Specifications 19  Specifications are property sheets for the entities in the model  They allow many attributes of the entities to be edited  This is one of the main methods of editing the model details

Stereotypes 20  A stereotype provides additional information about an object or association  For example, a stereotype DataObject could be applied to some classes to identify those that will be stored in a database  Stereotypes appear beside the object they modify in guillemets  >

Organizing the Model 21  You can create folders in the model to organize the different model components  This is similar to the views provided by the browser