chap 2 for ooad

8/12/2019 Chap 2 for OOAD

1/19

1/32

Outline

What is UP? UP History

UP Axioms

UP Core Workflows

UP Structure

Details on UP Phases

Chapter2 UP


2/19

2/32

What is UP?

A software developmentprocess (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 bythe authors of UML


3/19

3/32

UP History

UP evolution,


4/19

4/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
http://en.wikipedia.org/wiki/Grady_Boochhttp://www.youtube.com/watch?v=d0HVjoTD_rohttp://www.youtube.com/watch?v=IdUNAeN7guEhttp://espanol.video.yahoo.com/watch/577305/2839970http://www.youtube.com/watch?v=IdUNAeN7guEhttp://www.youtube.com/watch?v=IdUNAeN7guEhttp://en.wikipedia.org/wiki/Ivar_Jacobsonhttp://en.wikipedia.org/wiki/James_Rumbaughhttp://en.wikipedia.org/wiki/James_Rumbaughhttp://en.wikipedia.org/wiki/Ivar_Jacobsonhttp://www.youtube.com/watch?v=IdUNAeN7guEhttp://www.youtube.com/watch?v=IdUNAeN7guEhttp://espanol.video.yahoo.com/watch/577305/2839970http://www.youtube.com/watch?v=IdUNAeN7guEhttp://www.youtube.com/watch?v=d0HVjoTD_rohttp://en.wikipedia.org/wiki/Grady_Booch


5/19

5/32

UP Axioms

Use case and risk driven

Architecture centric

Iterative and incremental

Each iteration contains all the elements of a regular softwar

development project: planning, analysis, design, constructio

integration, testing, internal or external release


6/19

6/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 baselineis the result of an iteration, a partially complete version of

the final system. An iterationis the difference between two consecutive

baselines.


7/19

7/32

.UP Core Workflows


8/19

8/32

UP Structure.


9/19

9/32

UP Structure


10/19

10/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. Theremaining three phases are described in Subsection 2.9

of the textbook


11/19

11/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


12/19


13/19

13

Inception - milestone

Life Cycle Objectives - conditions of satisfaction: System scope has been defined

Key requirements for the system have been captured. The

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


14/19

14

Elaboration

Inception Elaboration Construction TransitionRequirementsrefine system scope andrequirements

Analysisestablish what to build

Designcreate a stable architectural baseline

Implementationbuild the architectural baseline

Testtest the architectural baseline

Focus

Goals

Create an executable architectural baseline

Refine Risk Assessment and define quality attributes (defect rates etc.)Capture use cases to 80% of the functional requirementsCreate a detailed plan for the construction phaseFormulate a bid which includes resources, time, equipment, staff, cost

R AI

TD


15/19

15

Elaboration - milestone

Lifecycle Architecture - conditions ofsatisfaction:

A resilient, robust executable architectural baselinhas been created

The Risk Assessment has been updated

A project plan has been created to enable a realisbid to be formulated

The business case has been verified against theplan

The stakeholders agree to continue


16/19

16

Construction

Inception Elaboration Construction TransitionRequirementsuncover any requirements thathad been missed

Analysisfinish the analysis model

Designfinish the design model

Implementationbuild the Initial OperationalCapability

Testtest the Initial Operational Capability

Focus

Goals

Complete use case identification, description and realization

Finish analysis, design, implementation and testMaintain the integrity of the system architectureRevise the Risk Assessment

R A

ITD


17/19


18/19

18

Correct defects

Prepare the user site for the new software and tailor the software to operate at the user siteModify software if unforeseen problems ariseCreate user manuals and other documentationProvide customer consultancyConduct post project review

Transition

Inception Elaboration Construction TransitionRequirementsnot applicable

Analysisnot applicable

Designmodify the design if problems emergein beta testing

Implementationtailor the software for the usersite. Fix bugs uncovered in beta testing

Testperform beta testing and acceptancetesting at the user site

Focus

Goals

DI T


19/19

19

Transition milestone

Product Release - conditions ofsatisfaction:

Beta testing, acceptance testing and defect

repair are finished The product is released into the user

community

chap 2 for ooad

Documents