Introduction to Rational Rose
- 2. ROSE = Rational Object Oriented Software Engineering Rational Rose is a set of visual modeling tools for development of object oriented software. Rose uses the UML to provide graphical methods for non-programmers wanting to model business processes as well as programmers modeling application logic. facilitates use of the Unified Modeling Language (UML), Component Object Modeling (COM), Object Modeling Technique (OMT), and Booch ‘93 method for visual modeling.
- 3. 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.
- 4. 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. ◦ Rose offers a fast way for clients and new employees to become familiar with system internals
- 5. Diagram window Diagram toolbar Browser Documentation Window docked/floating * Locked and unlocked modes of icons ** Customizing the tool bar
- 9. 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 *.mdl (the current version of Rose) Petal *.ptl Rose 6.1/6.5 Model Rose 4.5/6.5 Model Rose 4.0 Model Rose 3.0 Model
- 10. Use Case Collaboration Sequence Class Statechart Activity Component Deployment
- 11. Creating a diagram Linking a diagram 1. Create a note on any diagram. 2. Display the browser if not already visible. 3. In the browser, locate the diagram that you want to link. 4. Drag the diagram icon from the browser onto the note icon on the diagram. As you position the cursor onto the note, you will see the shortcut symbol (a dotted square and a curved arrow inside a solid square). 5. The fully qualified name is displayed in an underline font. Note: You may need to resize the note to see the entire name. 6. Change the text in the note (if desired) to something more meaningful to your project. 7. Double-click on the note to view the linked diagram. Displaying a diagram Rename a Diagram Deleting a diagram
- 12. 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. 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
- 13. 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
- 14. Use Case Diagrams describe the functionality of a system and users of the system. These diagrams contain the following elements: Actors, which represent users of a system, including human users and other systems. Use Cases, which represent functionality or services provided by a system to users.
- 15. Class Diagrams describe the static structure of a system, or how it is structured rather than how it behaves. These diagrams contain the following elements. Classes, which represent entities with common characteristics or features. These features include attributes, operations and associations. Associations, which represent relationships that relate two or more other classes where the relationships have common characteristics or features. These attributes and operations.
- 16. •Export Control field. »Public, private, protected, implementation •The Cardinality Concurrency •A class concurrency defines its semantics in the presence of multiple threads of control.
- 17. Object Diagrams describe the static structure of a system at a particular time. Whereas a class model describes all possible situations, an object model describes a particular situation. Object diagrams contain the following elements: Objects, which represent particular entities. These are instances of classes. Links, which represent particular relationships between objects. These are instances of associations.
- 18. Sequence Diagrams describe interactions among classes. These interactions are modeled as exchange of messages. These diagrams focus on classes and the messages they exchange to accomplish some desired behavior. Sequence diagrams are a type of interaction diagrams. Sequence diagrams contain the following elements: Class roles, which represent roles that objects may play within the interaction. Lifelines, which represent the existence of an object over a period of time. Activations, which represent the time during which an object is performing an operation. Messages, which represent communication between objects.
- 20. Collaboration Diagrams describe interactions among classes and associations. These interactions are modeled as exchanges of messages between classes through their associations. Collaboration diagrams are a type of interaction diagram. Collaboration diagrams contain the following elements. Class roles, which represent roles that objects may play within the interaction. Association roles, which represent roles that links may play within the interaction. Message flows, which represent messages sent between objects via links. Links transport or implement the delivery of the message.
- 22. Activity diagrams describe the activities of a class. These diagrams are similar to statechart diagrams and use similar conventions, but activity diagrams describe the behavior of a class in response to internal processing rather than external events as in statechart diagram. Swimlanes, which represent responsibilities of one or more objects for actions within an overall activity; that is, they divide the activity states into groups and assign these groups to objects that must perform the activities. Action States, which represent atomic, or noninterruptible, actions of entities or steps in the execution of an algorithm. Action flows, which represent relationships between the different action states of an entity Object flows, which represent the utilization of objects by action states and the influence of action states on objects.
- 24. Component diagrams describe the organization of and dependencies among software implementation components. These diagrams contain components, which represent distributable physical units, including source code, object code, and executable code.