Ooad4 Rup Aima

8/16/2019 Ooad4 Rup Aima

1/31

OOAD 4. The Rational Unified Process – Core Workflow

Processes

28

The Rational UnifiedProcess –

Core Workflow Processes

Requirements

Analysis

Design

Implementation

Test


2/31


Processes

29

The Unified Process as a Common Approach:

1. Provides guidance to the order of item’s activities2. Directs the tasks of individual developers and the team

3. Specifies what artifacts should be developed

4. Offers criteria for monitoring and measuring the project’sproducts and activities

The Triangle of Success

In SW evelopment

Notation

The Unified Modeling Language

Process Tool

The Rational Unified ProcessRational Rose CASE Tool

The Triangle of Success

In SW evelopment

Notation

The Unified Modeling Language

Process Tool

The Rational Unified ProcessRational Rose CASE Tool


3/31


Processes

30

The Unified Process – History and Essence

C reating the U nified P roce ss

Funct ional test ing

Performan ce test ing

Requirements mgmt

Conf . and change mgm t

Bu siness engineering

Data engineeringUI design

Rat ional Uni f ied Process 5 .01998

R at ional Objectory Process 4 .11996-1997

O bjectory Proces s 1.0-3.81987-1995

T h e E ric s so n A p p r o ac h

The R at ional Approach U M L

C rea ting the U nified P roce ss

Functional testing

Performan ce test ing

Requirements mgmt

Conf . and change mgm t

Bu siness engineering

Data engineeringUI design

R ationa l U nified Proces s 5.01998

Ra t ional Objectory Process 4 .11996-1997

O bjectory P rocess 1 .0-3 .81987-1995

T h e E ric s so n A p p ro a c h

The R at ional Approach U M L


4/31


Processes

31

The Process Itself

Ne w o r c ha n g e d

requ i rements

Ne w o r c ha n g e d

system

S of tw are Eng ineer ing

Process

W hat Is a P rocess?

Def inesD e fin e s W h o is d o in g W h a t, W h e n to d o it, a n d H o wto rea ch a cer ta in go al .

Ne w o r ch a n g e d

requ i rements

Ne w o r c h an g e d

sys tem

S of tw are Eng ineer ing

Process

W hat Is a P rocess?

Def inesDef ines W h o is do ing W h a t, W h e n to do it , an d H o wto reac h a c er ta in goa l.


5/31


Processes

32

The Unified Process is a

Component Framework

The Un ified P rocess is a Process Fram ew ork

There is N O U niversal Process!

• The Un ified Process is des igned for flex ib ility and extens ib ility

» a llows a varie ty of lifecyc le stra teg ies

» se le cts w ha t a rtifa cts to pro du ce

» d efin es a ctiv itie s a nd w o rke rs

» m odels concepts

The U nified P rocess is a Process Fram ew ork

There is N O U niversal Process!

• Th e U nified P rocess is des igned for flexibi lity and extensibility

» al low s a variety of l ifecycle strategies

» selects wha t art ifacts to prod uce

» de fine s activi ties and w orkers

» m odels concepts


6/31


Processes

33

The Unified Process

for SW EngineeringThe Unified Process is Engineered

Describe a

Use Case

Use case

package

Use case

responsible for

Analyst

Artifact

A piece of information that is

produced, modified, or used

by a process

Worker

A role played by anindividual or a team

Activity

A unit of work

The Unified Process is Engineered

Describe a

Use Case

Use case

package

Use case

responsible for

Analyst

Artifact

A piece of information that is

produced, modified, or used

by a process

Worker

A role played by anindividual or a team

Activity

A unit of work

Th U ifi d P i


7/31


Processes

34

The Unified Process is

Architecture-Centric

A rc h ite c tu re -C e n tr ic

M od e ls a re ve h ic les fo r v isu a l iz ing , sp ec ify ing ,M od e ls a re ve h ic les fo r v isu a l iz ing , spe c ify ing ,con s truc t ing , and do cum en ting a r ch itec tu recon s truc t ing , and do cum en ting a r ch itec tu re

Th e U n ified P roce ss p resc r ibe s the succ ess iveT he U n ified P roce ss p resc r ibe s the succe ss ivere f ine m en t o f an ex ec u tab le a rch itec tu rere fine m en t o f an ex ec u tab le a rch itec tu re

tim e

A rc h ite c tu re

In c e p tio n E la b o ra tio n C o n s tru c tio n Trans i t ion

A rc h ite c tu re -C e n tr ic

M od e ls a re ve h ic les fo r v isu a l iz ing , spe c ify ing ,M od e ls a re ve h ic les fo r v isu a l iz in g , sp ec ify ing ,con s truc t ing , and do cum en ting a r ch itec tu recon s truc t ing , and do cum en ting a r ch itec tu re

Th e U n ified P roce ss p resc r ibe s the s ucce ss iveTh e U n ified P roce ss p resc r ibe s the succe ss ivere fine m en t o f an e xe cu tab le a rch itec tu rere f ine m en t o f an ex ec u tab le a rch itec tu re

tim e

A rc h ite c tu re

In c e p tio n E la b o ra tio n C o n s tru c tio n Trans i t ion


8/31


Processes

35

Architecture and Models

Architecture embodies a collection of views of the models

Views

Models

Use CaseModel

DesignModel

Depl.Model

Impl.Model

TestModel

AnalysisModel

Architecture and Models

Architecture embodies a collection of views of the models

Views

Models

Use CaseModel

DesignModel

Depl.Model

Impl.Model

TestModel

AnalysisModel


9/31


Processes

36

The Unified Process is Use-Case Driven

U s e C a s e D r i v e n

R e q . t s I m p l . T e s t

U s e C a s e s b i n d t h e s e w o r k f l o w s t o g e t h e r

A n a l y s i s D e s i g n

U s e C a s e D r i v e n

R e q . t s I m p l . T e s t

U s e C a s e s b i n d t h e s e w o r k f l o w s t o g e t h e r

A n a l y s i s D e s i g n

U s e C a s e s D r i v e I t e r a t i o n s

D r i v e a n u m b e r o f d e v e l o p m e n t a c t i v i t i e sD r i v e a n u m b e r o f d e v e l o p m e n t a c t i v i t i e s

C r e a t i o n a n d v a l i d a t i o n o f t h e s y s t e m ’ s a r c h i t e c t u r e

U s e C a s e s D r i v e I t e r a t i o n s

D r i v e a n u m b e r o f d e v e l o p m e n t a c t i v i t i e sD r i v e a n u m b e r o f d e v e l o p m e n t a c t i v i t i e s

C r e a t i o n a n d v a l i d a t i o n o f t h e s y s t e m ’ s a r c h i t e c t u r e

D e f i n i t i o n o f t e s t c a s e s a n d p r o c e d u r e s

P l a n n i n g o f i t e r a t i o n s

C r e a t i o n o f u s e r d o c u m e n t a t i o n

D e p l o y m e n t o f s y s t e m

S y n c h r o n i z e t h e c o n t e n t o f d i f f e r e n t m o d e l sS y n c h r o n i z e t h e c o n t e n t o f d i f f e r e n t m o d e l s

D e f i n i t i o n o f t e s t c a s e s a n d p r o c e d u r e s

P l a n n i n g o f i t e r a t i o n s

C r e a t i o n o f u s e r d o c u m e n t a t i o n

D e p l o y m e n t o f s y s t e m

S y n c h r o n i z e t h e c o n t e n t o f d i f f e r e n t m o d e l sS y n c h r o n i z e t h e c o n t e n t o f d i f f e r e n t m o d e l s


10/31


Processes

37

The Unified Process is

Iterative and Incremental

L ifec yc le P ha ses

tim e

In c e p tio n E la b o ra tio n C o n s tru c tio n Trans i t i on

Incep t ion D e f ine the sco pe o f the p r o jec t andD e f ine the sco pe o f the p r o jec t andd e v e lo p b u s in e s s c a s ed e v e lo p b u s in e s s c a s e

Elabo ra t i on P lan p ro jec t, sp ec ify fea tu res , an dP lan p ro jec t, sp ec ify fea tu res , an dba se line the a rch i tec tu reba se line the a rch i tec tu re

Cons t ruc t i on B u i ld t he p rod uc tB u ild t he p rod uc t Trans i t i on T ran s it ion the p ro du c t to its u se rsT ran s ition th e p rod u c t to its us e rs

L ifec yc le P ha se s

tim e

In c e p tio n E la b o ra tio n C o n s tru c tio n Trans i t i on

Incep t ion D e fine the sco pe o f the p r o jec t andD e fine the sco pe o f the p r o jec t andd e v e lo p b u s in e s s c a s ed e v e lo p b u s in e s s c a s e

Elabo ra t i on P lan p ro jec t, sp ec ify fea tu res , an dP lan p ro jec t, sp ec ify fea tu res , an dba se line the a rch i tec tu reba se line the a rch i tec tu re

Cons t ruc t i on B u ild t he p rod uc tB u i ld t he p rod uc t Trans i t i on T ran s it ion the p ro du c t to its u se rsT ran s ition th e p rod u c t to its us e rs


11/31


Processes

38

Phases and Iterations

An iteration is a sequence of activities with an established plan and

evaluation criteria, resulting in an executable release

Arch

Iteration

... Dev

Iteration

Dev

Iteration

... Trans

Iteration

...

Release Release Release Release Release Release Release Release

Prelim

Iteration

...

Inception Elaboration Construction Transition

Phases and Iterations

An iteration is a sequence of activities with an established plan and

evaluation criteria, resulting in an executable release

Arch

Iteration

... Dev

Iteration

Dev

Iteration

... Trans

Iteration

...

Release Release Release Release Release Release Release Release

Prelim

Iteration

...

Inception Elaboration Construction Transition

Th U ifi d P i


12/31


Processes

39

The Unified Process in

Software Development

Dependencies between use-case model and the other models


13/31


Processes

40

The 4 P’s

in software development


14/31


Processes

41

Team working

Workers and resources that realize them producing artifacts


15/31


Processes

42

Team workflow

A workflow with workers and activities


16/31


Processes

43

Iterations and

Core Workflows

I te r a t io n s a n d W o r k f lo w

P r e l i m i n a r y

I t e r a t i o n ( s )

i t e r .

# 1

i t e r .

# 2

i t e r .

# n

i t e r .

# n + 1

i t e r .

# n + 2

i t e r .

# m

i t e r .

# m + 1

I n c e p t io n E la b o r a t io n C o n s t r u c t io n T r a n s i t i o n

I t e r a t i o n s

P h a s e s

C o r e W o r k f lo w s

A n i te r a t io n i n th e

e la b o r a t io n p h a s e

R e q u i r e m e n t s

D e s i g n

Im p l e m e n t a t io n

T e s t

A n a l y s i s

I t e r a t io n s a n d W o r k f lo w

P r e l i m i n a r y

I t e r a t i o n ( s )

i t e r .

# 1

i t e r .

# 2

i t e r .

# n

i t e r .

# n + 1

i t e r .

# n + 2

i t e r .

# m

i t e r .

# m + 1

I n c e p t io n E la b o r a t io n C o n s t r u c t io n T r a n s i t i o n

I t e r a t i o n s

P h a s e s

C o r e W o r k f lo w s

A n i te r a t io n i n th e

e la b o r a t io n p h a s e

R e q u i re m e n t s

D e s i g n

Im p l e m e n t a t io n

T e s t

A n a l y s i s


17/31


Processes

44

Requirements capture

From vision to requirements:

List candidate requirements

Understand system context

Capture functional requirements

Capture non-functional

requirements

Use case example: Buyer, seller and payment handler areinvolved in the Sales – the payment handler transfersmoney from one account to another as specified by the

invoice.


18/31


Processes

45

From requirements towards Use Cases

The workers and artifacts involved when capturing requirements as use cases

The inputs and outputs to/from the requirements capture


19/31


Processes

46

Analysis

Defines use-case realizations as structures of stereotypicalclasses and packages; gives structure to the internal view

The workers and artifacts involved in analysis

UML provides standard stereotype classes for use in analysis

Analysis class diagrams


20/31


Processes

47

Analysis class diagrams

A collaboration diagram for realization of the Pay Invoice use case

A class diagram for realization of the Pay Invoice use case

D i


21/31


Processes

48

Design

The workers and artifacts involved in design.

Example: the invoice design class.


22/31


Processes

49

Design workflow

A hit t l d i


23/31


Processes

50

Architectural design –

inputs and outputs


24/31


Processes

51

Implementation

From design to system components - source code, scripts,executables, etc.:

1. Plans the system iterations

2. System distribution by mapping components onto nodes in the

deployment model3. Implementation of design classes

4. Component test and integration

The workers and artifacts involved in implementation

Implementation –


25/31


Processes

52

Implementation

workflow and inputs/outputs


26/31


Processes

53

Implementation – system integration

The input and result of system integration The inputs and results ofsubsystem implementation


27/31


Processes

54

Test

Verification of result from implementation by testing each build

(integration tests) and final releases (system tests).

1. Plans the tests required in each iteration

2. Test design and implementation:

test cases specifying the test; test procedures – how to perform the test; exec.

test components for test automation

3.

Perform the tests and debugging.

The workers and artifacts involved in testing.

Test


28/31


Processes

55

Test

Theworkflowduringtesting.


29/31

Th i t d t t f t ti


30/31


Processes

57

The input and output of testing


31/31


Processes

58

Test example

Documents

Ooad4 Rup Aima