Rational ROSE

An introduction

Why modeling ?
Better understanding

The advantages of visual modeling
Modeling is a way of thinking about the problems using models organized around the real world ideas.

• understanding of various interrelationships of a system • fastest way to delineate the complex relationships • easier for developers, software architects and customers to communicate on a common platform

Unified Modeling Language

UML History .

Why UML ? • Large enterprise applications • a way that enables • Scalability • security • robust execution under stressful conditions • code reuse .


History • ROSE = Rational Object Oriented Software Engineering • Rational Rose is a set of visual modeling tools for development of object oriented software. Component Object Modeling (COM). • facilitates use of the Unified Modeling Language (UML). and Booch ‘93 method for visual modeling. • Rose uses the UML to provide graphical methods for nonprogrammers wanting to model business processes as well as programmers modeling application logic. Object Modeling Technique (OMT). .

When to use Rational ROSE • Modeling can be useful at any point in the application development process. • Initial Design Work (Requirement Analysis and Definition) – Use Cases – Class Diagrams – Sequence Diagram – Generality is Good in early design. .

– Rose offers a fast way for clients and new employees to become familiar with system internals .When to use Rational ROSE • Refinement of Early Models (System & Software Design) • Introduced in Middle of Project – Rational Rose includes tools for reverse engineering as well as forward engineering of classes and component architectures. – You can gain valuable insights to your actual constructed architecture and pinpoint deviations from the original design.

Rational ROSE INTERFACE Browser Diagram window Diagram toolbar Documentation Window docked/floating * Locked and unlocked modes of icons ** Customizing the tool bar Overview .

Views and Diagrams ??? Views Diagrams .

The different Views .

Rational Rose Interface Specification window Log window .

Options window Options window Stereotype display .

5 Model • Rose 4.mdl (the current version of Rose) • Petal *.1/6. eliminating the need to select Save As.5/6.5 Model • Rose 4.ini file to always save in a specified format. • Difference between the saved model and workspace.0 Model If you prefer. you can modify the rose. .Saving in various format If you want to save a Rational Rose model as a different format. you may select any of the following options from the Save As Type list in the Save Model To dialog box: • Models *.ptl • Rose 6.0 Model • Rose 3.

exe) • Script files (. Add-Ins can install: • Menus (. • can install language (for example.Add IN Manager Extending Rational Rose • allows you to quickly and accurately customize Rational Rose environment depending on development needs. Visual Basic.pty file) • Executables (.) and non.dll file) .cnt file) • Properties (.ebs script source file and . Visual Java.mnu file) • Help files (.ebx compiled script file) • OLE servers (.language (for example Microsoft Project) tools while in Rational Rose. etc.hlp file) • Contents tab file (.

Using the browser • Hiding and Displaying the Browser • Positioning the Browser » Docked and floating • Expanding and Collapsing the Browser Tree • Selecting Multiple Elements in the Browser • Navigating a Model • Creating and Editing Model Elements • Naming an Element in the Browser .

Rational ROSE DIAGRAMS • • • • • • • • Use Case Collaboration Sequence Class Statechart Activity Component Deployment .

As you position the cursor onto the note. » 5. In the browser. 3.Rational ROSE DIAGRAMS • Creating a diagram • Linking a diagram » » » » » 1. The fully qualified name is displayed in an underline font. locate the diagram that you want to link. 4. Double-click on the note to view the linked diagram. 2. Change the text in the note (if desired) to something more meaningful to your project. Display the browser if not already visible. you will see the shortcut symbol (a dotted square and a curved arrow inside a solid square). • Displaying a diagram • Rename a Diagram • Deleting a diagram • . Drag the diagram icon from the browser onto the note icon on the diagram. Note: You may need to resize the note to see the entire name. » 7. » 6. Create a note on any diagram.

• Deep Delete • • • • Click Edit > Delete from Model Press CTRL + D Right-click on an element in the browser and then select Delete from the shortcut menu .Deleting in Rational ROSE • Shallow Delete • Click Edit > Delete • Press CTRL + X • Press the DELETE key Note: If you perform a shallow delete on an element without a name. Rational Rose will delete the model element completely out of the model.

collaboration diagrams and user interface models. This is a precise specification of the objects in the system. begin to construct a domain model (high level business objects). • Map a Use Case Model to the Business Process Model to define exact functionality. their data or attributes and their behaviour or operations. sequence diagrams. • Refine the Use Cases . the user interface model and the scenario diagrams create the Class Model. notes and scenarios. • From the inputs and outputs of the Business Process Model and the details of the use cases. constraints. • From the domain model. complexity rating.include requirements.How to use Rational ROSE modeling in real life • Capture a Business Process Model. .

e. Track any changes against the related model elements to manage 'scope creep'. Concurrent with the work you have already done. • • • • • Update and refine the model as work proceeds . Unit Test defects against classes & etc. business objects. database tables. System test defects against Use Cases. The Deployment model defines the physical architecture of the system.g.. and related components necessary to execute that Use Case. Build the system: Take discrete pieces of the model and assign to one or more developers.How to use Rational ROSE modeling in real life • As the Class Model develops it may be broken into discrete packages and components. additional requirements should have been captured and documented. Track defects that emerge in the testing phases against the related model elements . So from the Class Model a Component Model is built to define the logical packaging of classes. having them build the screens. In a Use Case driven build this will mean assigning a Use Case to the development team.

RATIONAL ROSE Diagrams in detail .

How to use Rational ROSE • Selecting a diagram • Right-clicking as short cut • • Adding diagram elements from toolbar and browser Setting up default stereotypes • Idea about the Reverse engineering • Deleting from a diagram and the browser .

including human users and other systems. which represent functionality or services provided by a system to users. which represent users of a system. • Use Cases. These diagrams contain the following elements: • Actors. .Use Case Diagram Use Case Diagrams describe the functionality of a system and users of the system.

These attributes and operations. • Classes. These features include attributes. . • Associations. which represent relationships that relate two or more other classes where the relationships have common characteristics or features. operations and associations. These diagrams contain the following elements.Class diagrams Class Diagrams describe the static structure of a system. which represent entities with common characteristics or features. or how it is structured rather than how it behaves.

»Public. implementation •The Cardinality Concurrency •A class concurrency defines its semantics in the presence of multiple threads of control.Class Specification •Export Control field. private. protected. .

Object Diagram Object Diagrams describe the static structure of a system at a particular time. Object diagrams contain the following elements: • Objects. which represent particular entities. These are instances of classes. which represent particular relationships between objects. . Whereas a class model describes all possible situations. an object model describes a particular situation. These are instances of associations. • Links.

Sequence diagrams contain the following elements: • • Class roles. • • Activations. .Sequence Diagram Sequence Diagrams describe interactions among classes. which represent communication between objects. Lifelines. Sequence diagrams are a type of interaction diagrams. These diagrams focus on classes and the messages they exchange to accomplish some desired behavior. These interactions are modeled as exchange of messages. which represent roles that objects may play within the interaction. Messages. which represent the time during which an object is performing an operation. which represent the existence of an object over a period of time.


These interactions are modeled as exchanges of messages between classes through their associations. Links transport or implement the delivery of the message. Association roles. which represent messages sent between objects via links. which represent roles that objects may play within the interaction. Message flows. Collaboration diagrams contain the following elements.Collaboration Diagrams Collaboration Diagrams describe interactions among classes and associations. • • • Class roles. . which represent roles that links may play within the interaction. Collaboration diagrams are a type of interaction diagram.


which represent relationships between the different states of an object. . which represent the situations during the life of an object in which it satisfies some condition. or waits for some occurrence. performs some activity. These diagrams contain the following elements: • States.StateChart Diagrams Statechart (or state) diagrams describe the states and responses of a class. Statechart diagrams describe the behavior of a class in response to external stimuli. • Transitions.


actions of entities or steps in the execution of an algorithm. • Swimlanes. that is. or noninterruptible. they divide the activity states into groups and assign these groups to objects that must perform the activities. which represent relationships between the different action states of an entity action states and the influence of action states on objects. These diagrams are similar to statechart diagrams and use similar conventions. which represent responsibilities of one or more objects for actions within an overall activity. • Object flows. which represent the utilization of objects by .Activity Diagrams Activity diagrams describe the activities of a class. which represent atomic. • • Action flows. but activity diagrams describe the behavior of a class in response to internal processing rather than external events as in statechart diagram. Action States.


. and executable code. including source code. which represent distributable physical units. These diagrams contain components. object code.Component Diagrams Component diagrams describe the organization of and dependencies among software implementation components.



Deployment Diagram .

Deployment Diagram .


When in doubt contact :Contact the tech support at the help desk in the labs.edu . CA 95014 Telephone: 800-433-5444 or 408-863-4000 E-mail: support@rational.com • Or else • Mail me at asharm4@ilstu. • Or else Contact rational ROSE at 18880 Homestead Road Cupertino.

.rational. Boston.htm • Online Tutorials for Rational Rose http://www.More References • UML Home Page . USA .http://www.com/mag/index.com/products/rose/prodinfo/whitepapers/index.com/products/rose/gstart/online.platinum.rosearchitect. MA.rational.com/corp/uml/uml.shtml • Visual modeling with Rational Rose and UML Source Addison Wesley Object Technology Series Year of Publication: 1998 ISBN:0-201-31016-3 Author Terry Quatrani Publisher Addison-Wesley Longman Publishing Co.jtmpl • Rose Whitepapers http://www.jtmpl • Rose Architect E-Magazine http://www. Inc.

Sign up to vote on this title
UsefulNot useful