Chapter 2 UP

Outline
What is UP? UP History UP Axioms UP Core Workflows UP Structure Details on UP Phases
1/32

What is UP?
A software development process (SDP) or software engineering process (SEP) defines the who, what, when, and how of developing software The Unified Software Development Process (USDP) or, in short, the Unified Process (UP) is an industry standard process created by the authors of UML
2/32

UP History
UP evolution,

3/32

UP Founders
Grady Booch
Video: why engineering? Video: the promise, the limits, the beauty of software Video: smarter products for a smarter planet

Ivar Jacobson Jim Rumbaugh

4/32

UP Axioms
Use case and risk driven Architecture centric Iterative and incremental
Each iteration contains all the elements of a regular software development project: planning, analysis, design, construction, integration, testing, internal or external release

5/32

UP Core Workflows.
Requirements: Determining what the system should do Analysis: Refining and structuring the requirements Design: Defining system architecture to satisfy requirements Implementation: Building the software Testing: Verifying that the implementation is correct

A baseline is the result of an iteration, a partially complete version of the final system. An iteration is the difference between two consecutive baselines.

6/32

.UP Core Workflows

7/32

UP Structure.

8/32

UP Structure

9/32

UP: Details on Phases.

Each of the four phases of UP (inception, elaboration, construction, transition) has:
A goal A focus of activity One or more core workflows A milestone, with a number of conditions of satisfaction

Details of the above for Inception are given next. The remaining three phases are described in Subsection 2.9 of the textbook
10/32

UP: Details on Phases

Inception
Goal: Get the project off the ground Tasks:
Assess feasibility Create a strong business case Capture essential requirements Identify critical tasks

Focus: Requirements specification and analysis Milestone: Life-cycle objectives

11/32

Inception
amount of work in each core workflow
Requirements establish business case and scope. Capture core requirements
Inception Elaboration Construction Transition

Analysis establish feasibility

Design design proof of concept or technical prototypes Implementation build proof of concept or technical prototype Test not generally applicable Establish feasibility of the project - create proof of concept/technical prototypes Create a business case Scope the system - capture key requirements Identify critical risks Focus Goals

12

Inception - milestone
Life Cycle Objectives - conditions of satisfaction:
System scope has been defined Key requirements for the system have been captured. These have been defined and agreed with the stakeholders An architectural vision exists. This is just a sketch at this stage A Risk Assessment A Business Case Project feasibility is confirmed The stakeholders agree on the objectives of the project
13

Elaboration
Requirements refine system scope and requirements Analysis establish what to build
Inception Elaboration

R A D

Construction

Transition

Design create a stable architectural baseline

Implementation build the architectural baseline Test test the architectural baseline Create an executable architectural baseline Refine Risk Assessment and define quality attributes (defect rates etc.) Capture use cases to 80% of the functional requirements Create a detailed plan for the construction phase Formulate a bid which includes resources, time, equipment, staff, cost

Focus Goals

14

Elaboration - milestone
Lifecycle Architecture - conditions of satisfaction:
A resilient, robust executable architectural baseline has been created The Risk Assessment has been updated A project plan has been created to enable a realistic bid to be formulated The business case has been verified against the plan The stakeholders agree to continue 15

Construction
R A
Requirements uncover any requirements that had been missed Analysis finish the analysis model
Inception Elaboration Construction

Transition

Design finish the design model

Implementation build the Initial Operational Capability Test test the Initial Operational Capability Complete use case identification, description and realization Finish analysis, design, implementation and test Maintain the integrity of the system architecture Revise the Risk Assessment

Focus Goals

16

Construction - milestone
Initial Operational Capability - conditions of satisfaction:
The product is ready for beta testing in the user environment

17

Transition
D
Requirements not applicable Analysis not applicable
Inception Elaboration Construction

Transition

Design modify the design if problems emerge in beta testing

Implementation tailor the software for the user site. Fix bugs uncovered in beta testing Test perform beta testing and acceptance testing at the user site Correct defects Prepare the user site for the new software and tailor the software to operate at the user site Modify software if unforeseen problems arise Create user manuals and other documentation Provide customer consultancy Conduct post project review

Focus Goals

18

Transition milestone
Product Release - conditions of satisfaction:
Beta testing, acceptance testing and defect repair are finished The product is released into the user community

19