1 / 23

Objectives

Objectives. After this presentation you will understand: Why organize a Rational Rose model using RUP? Using the RUP framework to create a Rational Rose model RUP structure for a Rational Rose model Sequence of UML diagram creation. Rational Rose Model: RUP Structural Overview.

ranae
Télécharger la présentation

Objectives

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Objectives • After this presentation you will understand: • Why organize a Rational Rose model using RUP? • Using the RUP framework to create a Rational Rose model • RUP structure for a Rational Rose model • Sequence of UML diagram creation

  2. Rational Rose Model: RUP Structural Overview Rational Rose Model 1 1 1 1 Component Use Case Logical Deployment View View View View • Basic Model Structure

  3. RUP Structure: Use Case View Use Case View 1 1 Business Use-Case Use-Case Model Model 1 1 Actors Use Cases Package Package • Package Hierarchy

  4. Use Case View: Use-Case Model Use-Case Model 1 1 Actors Use Cases Package Package Shows the 0..n 0..n 0..n 0..n flow of events for a UC Specific UC Included UCs 0..n 0..n Package Package 1..n Activity Diagram Actor 0..n 0..n 1..n 1..n 1 1 Use Case 1..n 1..n Diagram Software 1 1 Use Case Activity 0..n • Recommended diagrams

  5. RUP Structure: Logical View Logical View 0..1 0..1 1 Business Analysis Design Object Model Model Model 0..n 0..1 1..n 1..n Layer Use-Case Process Package Realizations View • Package Hierarchy

  6. Logical View: Analysis Model (optional) Analysis Model 1..n Class Diagram 0..n 0..n 1..n 0..n 0..n Boundary Class Entity Class Control Class • Recommended diagrams

  7. Logical View: Design Model Design Model 1 1 1 1 Architecturally Architecture "Main" Model significant Overview Diagram Diagram model elements 1..n 1..n 1..n 0..n 0..n 0..n 0..n 0..n Layer Global Package Subsystem Package Package 0..n 0..n Class • Recommended diagrams

  8. Logical View: Design Model Layers Layer Package 1 1 0..n 0..n 0..n 0..n Layer Subsystem Package Diagram Interface 0..n 0..n 1 1 1 1 Dependency Interface 1 1 1 1 Diagram Diagram Class 1..n 1..n 1..n 1..n Diagram 1..n 1..n 1..n 1..n Interface Sequence Statechart 0..n 0..n Diagram Class Diagram • Recommended diagrams

  9. Logical View: Design Model: UC Realizations Use-Case Realizations 1..n Use-Case Package 1 1 1..n 1..n Realization 1..n 1..n Dependency Diagram Use-Case Realization via script 1 1 1..n 1..n 1..n 1..n VOPC Sequence Collaboration Diagram Diagram Diagram • Recommended diagrams

  10. RUP Structure: Component & Deployment Views Component Deployment View View Implementation Model • Package Hierarchy

  11. Component View: Implementation Model Component View 1 1 Implementation Model 1..n 1..n 1 1 Implementation Model Component Structure Diagram Diagram 1..n 1..n 0..n 0..n Package Component 1..n 1..n • Recommended diagrams

  12. Deployment View Deployment View 1 Deployment Diagram 0..n 0..n 1..n 1..n Processor Device 1..n 1..n 0..n 0..n 0..n 0..n Process Thread • Recommended diagrams

  13. Objectives • After this presentation you will understand: • Why organize a Rational Rose model using RUP? • Using the RUP framework to create a Rational Rose model • RUP structure for a Rational Rose model • Sequence of UML diagram creation

  14. Sequence of UML Diagram Creation 1. Business Use Case Diagram Business UC Model (optional) 2. Activity Diagram Business Object Model (optional) 3a. Class 3b. Activity 3c. Sequence Diagram Diagram Diagram

  15. Sequence of UML Diagram Creation (2) 4. Use Case Use Case Model Diagram 5. Activity Diagram Analysis Model (optional) 6. Class Create key Diagram abstraction class diagrams in the Design Model if you are skipping the Analysis Model

  16. Sequence of UML Diagram Creation (3) 7. Architecture Design Model Overview Diagram 8a. Realization Dependency Diagram Use Case Realizations 8c. Collaboration 8b. Sequence Diagram Diagram 8d. VOPC Diagram Analysis 9. Class Model Diagram

  17. Sequence of UML Diagram Creation (4) All diagram types on this page are in the Design Model Architecturally 10. "Main" Model significant model Show main Diagram elements elements in a specific layer of the system design Show classes/ interfaces that are 11a. Layer 11b. Dependency 11c. Interface visible outside a Diagram Diagram Diagram package or subsystem Allocate Analysis 12. Class classes to specific packages/ Diagram subsystems Create subsystem 13. Class proxies and Diagram interfaces

  18. Sequence of UML Diagram Creation (5) no concurrency design requires concurrency Show a mapping of processes and threads Process 14. Process/Class to the Logical design View Containment Diagram elements (classes) they contain. no distribution design requires distribution Deployment 15. Deployment View Diagram

  19. Sequence of UML Diagram Creation (6) Integrate Subsystem interfaces onto Use Case UC Realization Realizations interaction diagrams 16a. Sequence 16b. Collaboration Diagram Diagram 17. Interface Sequence Diagram * Add/refine Operations * Add/refine Attributes * Add/refine Associations Design 18. Class * Create additional class Model Diagram diagrams as necessary to illustrate "interesting" design points For classes with 19. Statechart significant “interesting” Diagram state-driven behavior

  20. Sequence of UML Diagram Creation (7) 20. Implementation Model Structure Diagram * Create Components for code to be generated Implementation * Map classes from Model Logical View onto 21. Component components in Component View Diagram * Create Component Diagrams as necessary to illustrate physical layout of code to be generated 22. Generate Code Done! Repeat whole process as necessary

  21. Summary • Improve team efficiency by following the RUP structure of a Rational Rose model • Know where in your Rational Rose model to place the different recommended UML diagram types • Agree on a sequence of UML diagram creation that works for your project

  22. Questions?

  23. Robert Bretall Rational Software Thank You! This presentation will be posted by tomorrow to http://www.rational.com/ruc

More Related