Requirements used consistently in combination with agile development (SCRUM) and SOA

(1)

Requirements used consistently in combination with

agile development (SCRUM) and SOA

Date: March 10th, 2009

(2)

Produced by: Heinz Ehrsam, Ralf Fahney Date: 10.03.2009 Slide 2

Credit Suisse is the second largest Swiss bank, and is

dependent on an efficient IT



The Credit Suisse Group is a modern

descendent from the Schweizerische

Kreditanstalt founded 1856



Banking business divides into Investment

Banking, Privat Banking and Asset Management



19 application domains, which subdivide into

closely related applications

–

more than 1'200 different applications

–

32 million lines of code PL1

–

11 million lines of code Java



Over 20 million processed securities

transactions per year

(3)

Securities operations platform must be fit for the future

Starting position:



30 year old application landscape,

based on PL/1



Lack of documentation for current applications



Lack of PL/1 knowledge in the future

Objectives:



more flexibility for business by changes



Service Oriented Architecture (SOA)



Transaction process on Java platform



Trend to standard software

(4)

New technologies require new methodological approach



Business process management (BPM)



Service Oriented Architecture (SOA)



Business process modeling including use

case descriptions



Business process model transformation

into process engine



Centralized Business rules engine



Event Driven Process Chain (EPC)



Unified Modeling Language (UML)

(5)

Tool Chain

₅

5. Integrated SW development Tool Chain for

improve efficiency and quality

of STAR

rollout

Key Topics "SOA Framework"

1. Business Process Management for

executable process models

by the

integrated IT-transformation

IT-Service A

IT-Service C

IT-Service B

P

ro

ce

ss

O

rc

he

str

ati

on

B

us

in

es

s

R

ule

s

In

te

ra

cti

on

2

2. Structured IT-architecture for

more agility

and flexibility

with autonomous IT-Services,

central process orchestration and central

managed Business Rules

Requirement - Management

R

eq

ue

st

/

3

3. Request- and Requirement Management for

transparent release planning

and view

definitions per stakeholder

Testing

₄

4. Test environment and automatic test

applications for

faster and continuous

integration

Business Process Mgt:

architecture, component,

activity, processes

(6)

BPM/SOA and RE&M:

Different perspectives to system development

Tool Chain

IT-Service A

IT-Service C

IT-Service B

P

ro

ce

ss

O

rc

he

str

ati

on

B

us

in

es

s

R

ule

s

Business Process Mgt:

architecture, component,

activity, processes

Requirement - Management

R

eq

ue

st

-

/

Testing

In

te

ra

cti

on

(7)

BPM/SOA perspective: Solution-oriented

Meta model terms



Business Process



Data (e.g. Business Object)



Services



Rules



CIM



PIM



PSM



Feature



Requirement



Approval



Acceptance



System Specification



Design Specification

(8)

RE&M perspective: Requirements-oriented

Meta model terms



Business Process



Data (e.g. Business Object)



Services



Rules



CIM



PIM



PSM



Feature



Requirement



Approval



Acceptance



System Specification



Design Specification

(9)

(10)

User

Requirements

System

Specification

"Design To"

Specification

"Build To"

Specification

Implementation

"Build To" Level

Integration

"Design To" Level

Integration

System Level

Integration

User Level

Integration

D

efin

itio

n,

_D

ec

om

po

siti

_on

,

Ap

pro

va

_l

"Trace To"

In

te

gr

at

io

n,

Ve

rif

ic

at

io

n,

Ac

ce

pt

an

ce

1st Business approval

2nd Business approval

Step 1

Align Vee-Model levels of abstraction

Implementation

PSM Level

Integration

PIM Level

Integration

CIM Level

Integration

Business Request

Level Integration

D

efin

itio

n,

_D

ec

om

po

siti

_on

,

Ap

pro

va

_l

"Trace To"

In

te

gr

at

io

n,

Ve

rif

ic

at

io

n,

Ac

ce

pt

an

ce

Business Request

CIM

PIM

PSM

1st Business approval

2nd Business approval

(11)

Implementation

Platform Specific Model

(PSM)

Platform Independent

Model (PIM)

Computation Independent

Model (CIM)

Business Request

Business

Rules

Services

Data

Business

Processes

Level of

Abstraction

Deliverable

Step 2

Introduce "Approval" into BPM/SOA perspective

Implementation

Platform Specific Model

(PSM)

Platform Independent

Model (PIM)

Computation Independent

Model (CIM)

Business Request

Business

Rules

Services

Data

Business

Processes

Level of

Abstraction

Deliverable

1st Business approval

2nd Business approval

(12)

Step 3

Make 3D perspective out of both 2D perspectives

L

e

v

e

ls

o

f

A

b

s

tr

a

c

ti

o

n

Del

iver

able

Cat

ego

ries

Requ

ireme

nts, A

ccepta

_nce

(13)

CIM level example

L

e

v

e

ls

o

f

A

b

s

tr

a

c

ti

o

n

Del

iver

able

Cat

ego

ries

Requ

ireme

nts, A

ccepta

_nce

(14)

CIM level example



Requirement

REQ142: 'Process Registered

Share Delivery Order' business

process must include to create

customer documents



Deliverable

(15)

PIM level example

L

e

v

e

ls

o

f

A

b

s

tr

a

c

ti

o

n

Del

iver

able

Cat

ego

ries

Requ

ireme

nts, A

ccepta

_nce

(16)

PIM level example



Requirement

derived from

‚

Create customer

documents (purchase)

‘

function

solution design

REQ235: System must create

customer documents as per

customer document types list

determined from customer delivery

instructions

(17)

PSM level example

L

e

v

e

ls

o

f

A

b

s

tr

a

c

ti

o

n

Del

iver

able

Cat

ego

ries

Requ

ireme

nts, A

ccepta

_nce

(18)

PSM level example



Requirements

‚

Create customer documents (purchase)

‘

event-driven process chain

REQ326: System must use ALBPM as

process engine

REQ327: Project must use XPDL to

transform event-driven process chain to

ALBPM internal process representation

REQ328: Project must consider mismatch

between ARIS and ALBPM XPDL

interpretation



Deliverable

ARIS = A business process modeling tool

XPDL = A business process model exchange standard ALBPM = A business process engine

(19)

... and everything's fine again ...

(20)

2nd Business approval must include PIM aspects

CIM

PIM

PSM

'Business-View'

RE&M /

Sol.Eng.

1st Business approval

2nd Business approval

(21)

2nd Business approval must include PIM aspects

CIM

PIM

PSM

'Business-View'

RE&M /

Sol.Eng.

1st Business approval

2nd Business approval

(22)

Models are complete

Requirements are documented incompletely

CIM

PIM

PSM

'Business-View'

RE&M /

Sol.Eng.

1st Business approval

30 –

60 %

10 –

40 %

5 –

20 %

Requirement

Storage

=

Explicitly

documented

requirements

2nd Business approval

(23)

Models are complete

Requirements are documented incompletely

CIM

PIM

PSM

'Business-View'

RE&M /

Sol.Eng.

1st Business approval

30 –

60 %

10 –

40 %

5 –

20 %

Requirement

Storage

=

Explicitly

documented

requirements

40 _–

70 %

60 _–

_{90 %}

80 –

_{95 %}

Undocumented

requirements

Undocumented

requirements

2nd Business approval

(24)

Lessons Learned



Tools are not yet mature



Early prototypes of the development process

and with the solution



Waterfall model is not applicable



Textual description requirement, compared

with models



Define the policy modulation



Culture Changes



Daily communication with all roles

(daily SCRUM-Meetings)



Continuous process improvement

(25)

Thank you for your attention.

Do you have questions?

(26)

References



CIM, PIM, PSM

–

Joaquin Miller, Jishnu Mukerji, "MDA Guide Version 1.0.1", 2003,

http://www.omg.org/docs/omg/03-06-01.pdf



Vee Model

–

Kevin Forsberg, Harold Mooz,

“

The Relationship of System Engineering to the

Project Cycle

”

, presented at the joint conference sponsored by: National

Council On Systems Engineering (NCOSE) and American Society for

Engineering Management (ASEM), Chattanooga, TN, 21

–

23 October 1991,

http://www.csm.com/repository/model/rep/o/pdf/Relationship%20of%20SE%

20to%20Proj%20Cycle.pdf