WP5

26.02.2014 © 2010 UNIVERSITÄT ROSTOCK | Fakultät für Informatik und Elektrotechnik | Lehrstuhl Wirtschaftsinformatik

CaaS Methodology

Kurt Sandkuhl

14.10.2009 2© 2009 UNIVERSITÄT ROSTOCK | FAKULTÄT FÜR INFORMATIK UND ELEKTRONIK

Capability Driven Development Methodology

• Objective: establish a capability driven development for congruent digital business and

information system development methodology by integrating together empirical experiences

and developments elaborated in WP2, WP3 and WP4 with theoretical developments

• Partners: Stockholm University (S), Riga Technical University (LV),

University of Rostock (D), Universitat Politecnia de Valencia (ES)

Tasks:

T5.1: Develop State-of-the-Art Overview on Relevant Methodology Areas [Month 4 - 5]

T5.2: Develop Core for the Methodology [Month 6 - 7]

T5.3: Develop Pattern Repository [Month 8 - 12]

T5.4 Develop Algorithms for Capability Composition, Assessment, Delivery Adjustment [M 13 - 24]

T5.5: Methodology Refinement, Integration and Acceptance (2 cycles) [M 16 – 18 and 28 - 32]

T5.6: Methodology Description and Pattern Repository [Month 31 - 33]

Methodology work package (WP5)

14.10.2009 3© 2009 UNIVERSITÄT ROSTOCK | FAKULTÄT FÜR INFORMATIK UND ELEKTRONIK

Capability driven development and delivery (CDD)

Method Overview

Business Case driven methodology development

Business

Analyst

Solution

Engineer

Worker/

Operator

Task Task Task

Conceptual solution

workflow workflow workflow

Technical solution

service service Service

Executed solution

Engineering Process

Te

ch

no

log

y S

tack

CaaS project approach is business case driven

Methodology development needs to take into account:

• Established engineering processes in business cases

• Technology stack used in business cases

CDD in Action – an Illustrative Scenario

Business

Analyst

Solution

Engineer

Worker/

Operator

Task Task Task

Conceptual solution

workflow workflow workflow

Technical solution

service service Service

Executed solution

Engineering Process

Te

ch

no

log

y S

tack

Pattern Repository

1 Select context to be considered and capability model to be adapted

2 Recommend /

select pattern

3 Pattern is inserted

largely automatically

4 Adaption of solution

fully automatic

5 Context monitoring

is adapted

0 Existing reference processes

extended to capability models

6 Change needs detected

identify specific aspects to address

7 Patterns matching change

needs are recommended

Conceptual Foundation: Capability Meta-Model

class Capability metamodel

Capability Goal

Indicator

Context IndicatorKPI

ContextSet

ProcessProcessVariantPattern

ContextElementRange

Measurable

Property

ContextElementContextType

ResourceContext Situation

Context Element

Value

1..*

related to

0..1

*

measured by

0..1

1..*

requires

0..1

1 1..*

*

influences

* 1..*

requires

1..*

0..1

supported by

1

1

requires

0..1

1

defines

*

0..1

requires

1..*

1..*

motivates

1..*

1..*

consists of

1

1

requires

0..1 *

requires

1

11..*

1

consists of

1..*

11..*

1

has value

1..*

1

has

*