Applying UML in The Unified Process Ivar Jacobson Rational Software email: ivar @rational

1. Applying UML in The Unified ProcessIvar JacobsonRational Softwareemail: ivar @rational.com

2. Before the UML • 1960’s - 70’s • COBOL, FORTRAN, C • Structured analysis and design techniques • 1980’s - early 1990’s • Smalltalk, Ada, C++, Visual Basic • Early generation OO methods • Mid/late 1990’s • Java • UML • Unified Process

3. Models and Diagrams A model is a complete description of a system from a particular perspective State Diagrams State Diagrams Class Diagrams Use Case Diagrams Use Case Diagrams State Diagrams Use Case Diagrams State Diagrams Use Case Diagrams Object Diagrams Use Case Diagrams Sequence Diagrams Scenario Diagrams State Diagrams Scenario Diagrams State Diagrams Component Diagrams Collaboration Diagrams Models Component Diagrams Scenario Diagrams Component Diagrams Scenario Diagrams Deployment Diagrams Statechart Diagrams Activity Diagrams

4. Team-Based Development Modeling Language Unified Process But, the UML Is Not Enough

5. Creating the Unified Process Rational Unified Process 5.0 Functional testing Performance testing Requirements mgmt Conf. and change mgmt Business engineering Data engineering UI design 1998 Rational Objectory Process 4.1 1996-1997 UML The Rational Approach Objectory Process 1.0-3.8 1987-1995 The Ericsson Approach

6. What Is a Process? • DefinesWho is doing What, When to do it, and How to reach a certain goal. New or changed system New or changed requirements Software Engineering Process

7. Overview of the Unified Process • The Unified Process is • Iterative and incremental • Use case driven • Architecture-centric

8. time Lifecycle Phases • Inception Define the scope of the project and develop business case Inception Elaboration Construction Transition • Elaboration Plan project, specify features, and baseline the architecture • Construction Build the product • Transition Transition the product to its users

9. time Vision Baseline Architecture Initial Capability Product Release Major Milestones Inception Elaboration Construction Transition

10. Release Release Release Release Release Release Release Release Phases and Iterations Inception Elaboration Construction Transition ... Prelim Iteration ... Arch Iteration ... Dev Iteration Dev Iteration ... Trans Iteration An iteration is a sequence of activities with an established plan and evaluation criteria, resulting in an executable release

11. P h a s e s C o r e W o r k f l o w s I n c e p t i o n E l a b o r a t i o n C o n s t r u c t i o n T r a n s i t i o n A n i t e r a t i o n i n t h e e l a b o r a t i o n p h a s e P r e l i m i n a r y i t e r . i t e r . i t e r . i t e r . i t e r . i t e r . i t e r . I t e r a t i o n ( s ) # 1 # 2 # n # n + 1 # n + 2 # m # m + 1 I t e r a t i o n s Iterations and Workflow Requirements Analysis Design Implementation Test

12. Use Case Model Analysis Model Design Depl. Model Model Impl. Model Test Model Workflows and Models UML diagrams provide views into each model Requirements Analysis Design Implementation Test Each workflow is associated with one or more models.

13. Use Case Model Analysis Model Design Depl. Model Model Impl. Model Test Model Use Case Model Use Case Diagrams Class Diagrams Object Diagrams Component Diagrams Deployment Diagrams Sequence Diagrams Collaboration Diagrams Statechart Diagrams Activity Diagrams

14. Use Case Model Analysis Model Design Depl. Model Model Impl. Model Test Model Analysis & Design Model Use Case Diagrams Class Diagrams Object Diagrams Component Diagrams Incl. subsystems and packages Deployment Diagrams Sequence Diagrams Collaboration Diagrams Statechart Diagrams Activity Diagrams

15. Use Case Model Analysis Model Design Depl. Model Model Impl. Model Test Model Deployment and Implementation Model Use Case Diagrams Class Diagrams Object Diagrams Component Diagrams Deployment Diagrams Incl. active classes and components Sequence Diagrams Collaboration Diagrams Statechart Diagrams Activity Diagrams

16. Use Case Model Analysis Model Design Depl. Model Model Impl. Model Test Model Test Model Use Case Diagrams Class Diagrams Object Diagrams Component Diagrams Deployment Diagrams Test model refers to all other models and uses corresponding diagrams Sequence Diagrams Collaboration Diagrams Statechart Diagrams Activity Diagrams

17. Use Case Driven Analysis Req.ts Design Impl. Test Use Cases bind these workflows together

18. Use Cases Drive Iterations • Drive a number of development activities • Creation and validation of the system’s architecture • Definition of test cases and procedures • Planning of iterations • Creation of user documentation • Deployment of system • Synchronize the content of different models

19. Inception Elaboration Construction Transition time Architecture Architecture-Centric • Models are vehicles for visualizing, specifying, constructing, and documenting architecture • The Unified Process prescribes the successive refinement of an executable architecture

20. Use Case Model Analysis Model Design Depl. Model Model Impl. Model Test Model Architecture and Models Models Views • Architecture embodies a collection of views of the models

21. Function versus Form Use cases Architecture • Use case specify function; architecture specifies form • Use cases and architecture must be balanced

22. A unit of work A role played by an individual or a team Activity Worker Artifact A piece of information that is produced, modified, or used by a process Use case The Unified Process is Engineered Describe a Use Case Analyst responsible for Use case package

23. The Unified Process is a Process Framework • There is NO Universal Process! • The Unified Process is designed for flexibility and extensibility • allows a variety of lifecycle strategies • selects what artifacts to produce • defines activities and workers • models concepts

24. Two Parts of a Unified Whole The Unified Modeling Language The Unified Process • OMG standard • Convergence in the future • Convergence through process frameworks