Applying UML in The Unified Process. Ivar Jacobson Rational Software

Transcription

1 Applying UML in The Unified Process Ivar Jacobson Rational Software

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 s and A model is a complete description of a system from a particular perspective Sequence State State Class State State Object Scenario Scenario Collaboration s State State Component Scenario Scenario Statechart Activity Component Component Deployment

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

5 Creating the Unified Process Rational Unified Process Rational Objectory Process Functional testing Performance testing Requirements mgmt Conf. and change mgmt Business engineering Data engineering UI design The Rational Approach Objectory Process UML The Ericsson Approach

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

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

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

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

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

11 Iterations and Workflow Core Workflows Phases Inception Elaboration Construction Transition Requirements Analysis An iteration in the elaboration phase Design Implementation Test Preliminary Iteration(s) iter. #1 iter. #2 iter. #n iter. #n+1 ite r. #n+2 iter. #m iter. #m+1 Iterations

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

13 Analysis Design Depl. Impl. Test Class Component Deployment Sequence Collaboration Statechart Activity Object

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

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

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

17 Driven Req.ts Analysis Design Impl. Test s bind these workflows together

18 s 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 Architecture-Centric ❿ s are vehicles for visualizing, specifying, constructing, and documenting architecture ❿ The Unified Process prescribes the successive refinement of an executable architecture Inception Elaboration Construction Transition time Architecture

20 Architecture and s Analysis Design Depl. Impl. Test s 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 The Unified Process is Engineered A role played by an individual or a team Activity A unit of work Worker Analyst responsible for Describe a Artifact Use case Use case package A piece of information that is produced, modified, or used by a process

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 ing Language The Unified Process OMG standard Convergence in the future Convergence through process frameworks