These slides describe the EVR case study that focuses on capability modelling within a service-oriented architecture development project. The paper discusses the lessons learned, as well as open challenges to feedback the improvement of the CDD methodology.

1. Capability-driven development of
a SOA platform:
a case study
FP 7 ICT Programme Collaborative
Project no: 611351
International Workshop on Advances in Services DEsign based on the Notion of CApability
ASDENCA 2014
S. España,T. González, J. Grabis,
L. Jokste, R. Juanes and F. Valverde

2. Capability-driven development of
a SOA platform:
a case study
FP 7 ICT Programme Collaborative
Project no: 611351
International Workshop on Advances in Services DEsign based on the Notion of CApability
ASDENCA 2014
Agenda
Introduction
Research methodology
Case study
Lessons learned
Conclusion

3. Introduction
Capability-driven development of a SOA platform: a case study
This story has fictional elements!
What
is
a
capability?
I
want
to
sell
ice
creams
in
all
Spain

4. Introduction
Capability-driven development of a SOA platform: a case study
GoalCapability requires
Indicator
requires
influences
Context Set requires
Context
Type
measured by
Pattern
requires
Process
motivates
Process
Variant
Resource
Context Element
Measurable
Property
KPI
Context
Indicator
requires
defines
supported by requires
related_to
Context
Situation
has value
requires
has
Context
Element
Range
consists of
Contex
Element
Value
consists of

5. Introduction
Capability-driven development of a SOA platform: a case study
GoalCapability requires
Indicator
requires
influences
Context Set requires
Context
Type
measured by
Pattern
requires
Process
motivates
Process
Variant
Resource
Context Element
Measurable
Property
KPI
Context
Indicator
requires
defines
supported by requires
related_to
Context
Situation
has value
requires
has
Context
Element
Range
consists of
Contex
Element
Value
consists of
Capability-­‐driven
development
No
empirical
valida;ons
We
conduct
a
case
study

6. Capability-driven development of
a SOA platform:
a case study
FP 7 ICT Programme Collaborative
Project no: 611351
International Workshop on Advances in Services DEsign based on the Notion of CApability
ASDENCA 2014
Agenda
Introduction
Research methodology
Case study
Lessons learned
Conclusion

7. Practical problem investigation
• Investigate the need for a capability-driven development
methodology and tools (stakeholders, goals, criteria).
• Phenomena, diagnosis.
Solution design
• Explore available solutions by reviewing state of the art
• Design a new solution; i.e. the CDD proposal under
development in project CaaS:
• Capability modelling (goals, context, enterprise).
• Pattern-based solution (repository, rules).
• Support tools (design and runtime environment).
Solution validation
• Demonstrate feasibility with lab demos.
• Evaluate the benefits, the trade-offs, and
the sensitivity of the solution
Research problem investigation
• Current knowledge (see Section 2).
• Research questions (see Section 3).
• Unit of study (see Section 4.1).
Research design
• Select project (see Section 3).
• Define research protocol and agree with company
(see Section 3).
• Define instruments
Research design validation
• Ensure effectiveness of protocol and instruments
• Validity threats trade-off (see Section 5).
Research execution
• Conduct interviews, report project enactment
(see Section 4.2).
Analysis of results
• Collect lessons learned
• Identify challenges (see Section 4.3).
Engineering cycle (performed in CaaS project) Research cycle (reported in this paper)
Research
Capability-driven development of a SOA platform: a case study
This paper

8. Capability-driven development of
a SOA platform:
a case study
FP 7 ICT Programme Collaborative
Project no: 611351
International Workshop on Advances in Services DEsign based on the Notion of CApability
ASDENCA 2014
Agenda
Introduction
Research methodology
Case study
Lessons learned
Conclusion
Company
Project
Capability modelling

9. Capability-driven development of a SOA platform: a case study
Case study

10. Capability-driven development of a SOA platform: a case study
Case study

11. Capability-driven development of a SOA platform: a case study
Case study

13.
Current
situa;on
200
services
250
municipali;es
1.000.000
Spanish
ci;zens
Complex
and
dynamic
context
Customisa;on
at
code
level

16.
Main
challenges
Model
the
desired
capabili;es
Model
impact
of
context
Towards
context-­‐aware,
self-­‐adap;ve
plaIorm
Capability-driven development of a SOA platform: a case study
Case study

17.
People
involved
Public
Sector
and
R&D
Manager
Business
Consultant
Technological
Consultant
4
researchers
from
UPV
and
RTU
Capability-driven development of a SOA platform: a case study
Case study

18. Capacity: IT infrastructure, monitoring tool, developers, technicians.
Ability: being able to deploy a maintenance portal.
Enterprise: everis
Goal: keep services available despite platform errors.
Context: loss of connectivity w. other subsystems.
Goal KPI: time service available / time error in platform
Capacity: swimming pool facilities, swimming coaches.
Ability: offer the electronic service to request swimming course registration.
Enterprise: municipality
Goal: reduce cost of service provision.
Context: amount of requests.
Goal KPI: amount of money saved
Capability-driven development of a SOA platform: a case study
Case study
everis staff originally created 8 distinct definitions
issues related to
Perspective
Granularity
everis
municipality
offer the electronic service
deploy a maintenance portal

19. Capability-driven development of a SOA platform: a case study
Case study
LEGEND
ACTIVITY
PRECEDENCE
RELATIONSHIP
GOAL MODELLING
KPI
SPECIFICATION
STAKEHOLDER
MODELLING
CONCEPT
MODELLING
CAPABILITY
MODELLING
IT ARCHITECTURE
DESIGN DRAFT
CONTEXT
MODELLING
BUSINESS
PROCESS
MODELING
PATTERNS
MODELLING OR
SELECTION
Then researchers entered the scene and, together,
we followed this process

20. Capability-driven development of a SOA platform: a case study
Case study
G-13: TO IDENTIFY
CHANGE PATTERNS
G-14: TO USE
PATTERNS
G-15: TO MONITOR
SERVICE DATA USAGE
IN THE PLATFORM
G-17: TO AUTOMATE
RESPONSE CREATION
G-16: TO ENSURE
INTEGRATION WITH
OTHER SYSTEMS
G-12: TO KEEP
SERVICES UP TO
CURRENT
REQUIREMENTS
G-18: TO ENSURE
CONTEXT AWARENESS
DURING THE RUN TIME
G-11: TO ENSURE
COMPLIANCE WITH
LEGAL FRAMEWORK
G-10: PROVIDE
ADEQUATE IT
INFRASTRUCTURE
G-1: TO IMPROVE THE
USAGE OF SERVICES
G-2: TO PROVIDE
SMART SERVICES
G-3: TO STREAMLINE
SERVICE ACTIVATION
G-4: TO PROVIDE A
CHIOCE BETWEEN
AUTOMATED AND
FACE-TO-FACE
SERVICES
G-5: TO PROMOTE
SERVICE USAGE IN
SERVICE CATALOG
G-6: TO BE ABLE TO
IDENTIFY SERVICE
CHANGES IN ADVANCE
G-7: TO IDENTIFY
REASONS FOR
CHANGES IN USAGE
G-8: TO SUPPORT THE
CHANGE
MANAGEMENT
PROCESS
G-9: TO USE EXTERNAL
DATA SOURCES TO
IDENTIFY THE NEED
FOR THE SERVICES
SUPPORTS SUPPORTS SUPPORTS SUPPORTS
SUPPORTS
SUPPORTS
SUPPORTS SUPPORTSSUPPORTS
SUPPORTS SUPPORTS
SUPPORTS
SUPPORTS
SUPPORTS
SUPPORTS
SUPPORTS
SUPPORTS
Goal model
Strategic goals
Business goals
Technical goals
Design-time goals
Run-time goals

21. Capability-driven development of a SOA platform: a case study
Case study
G-13: TO IDENTIFY
CHANGE PATTERNS
G-14: TO USE
PATTERNS
G-15: TO MONITOR
SERVICE DATA USAGE
IN THE PLATFORM
G-17: TO AUTOMATE
RESPONSE CREATION
G-16: TO ENSURE
INTEGRATION WITH
OTHER SYSTEMS
G-12: TO KEEP
SERVICES UP TO
CURRENT
REQUIREMENTS
G-18: TO ENSURE
CONTEXT AWARENESS
DURING THE RUN TIME
G-11: TO ENSURE
COMPLIANCE WITH
LEGAL FRAMEWORK
G-10: PROVIDE
ADEQUATE IT
INFRASTRUCTURE
G-1: TO IMPROVE THE
USAGE OF SERVICES
G-2: TO PROVIDE
SMART SERVICES
G-3: TO STREAMLINE
SERVICE ACTIVATION
G-4: TO PROVIDE A
CHIOCE BETWEEN
AUTOMATED AND
FACE-TO-FACE
SERVICES
G-5: TO PROMOTE
SERVICE USAGE IN
SERVICE CATALOG
G-6: TO BE ABLE TO
IDENTIFY SERVICE
CHANGES IN ADVANCE
G-7: TO IDENTIFY
REASONS FOR
CHANGES IN USAGE
G-8: TO SUPPORT THE
CHANGE
MANAGEMENT
PROCESS
G-9: TO USE EXTERNAL
DATA SOURCES TO
IDENTIFY THE NEED
FOR THE SERVICES
SUPPORTS SUPPORTS SUPPORTS SUPPORTS
SUPPORTS
SUPPORTS
SUPPORTS SUPPORTSSUPPORTS
SUPPORTS SUPPORTS
SUPPORTS
SUPPORTS
SUPPORTS
SUPPORTS
SUPPORTS
SUPPORTS
Goal model
Goal
templates
G-1. To improve the usage of the services
Currently, EVR provides up to 200 services for 250 municipalities, but 100 are in active use and not
in all municipalities.The goal is to improve the usage of the services.
Category: Strategic goal
Stakeholder: S-3. EVR
KPIs:
Percentage of users consuming the services (target=25%)
Percentage of completed service actions / submissions (target=90%)
G-5. To promote service usage in service catalog
EVR provides a huge amount of services in SOA platform service catalog. Each service must
contain sufficient up-to-date information to help to the end users find and use the services.
Category: Strategic goal
Stakeholder: S-3. EVR, S-4. Municipality
KPIs:
Frequency of catalog update
Number of services in catalog

22. Stakeholders model
Capability-driven development of a SOA platform: a case study
Case study

23. Concepts model
Capability-driven development of a SOA platform: a case study
Case study

24. Context model
Capability-driven development of a SOA platform: a case study
Case study

25. Context model
Capability-driven development of a SOA platform: a case study
Case study
Context
element
specifica;on
Element
Values
Measur. prop.
Mapping rules
Municipality size
{Small,
Medium,
Large}
NC =
Number of citizens
If NC <10000 then ‘small’
If 10000 <= NC < 30000 then ‘medium’
If NC >= 30000 then ‘large’
Service usage in
other
municipalities
{High,
Medium,
Low}
PMUS = Percentage
of municipalities
using the service
If PMUS < 20%, then ‘low’
If 20% <= PMUS < 50% then ‘medium’
If PMUS >= 50% then ‘high’
Type of
highlighting
{Automatic,
Manual}
NA
NA (unknown at design time)

26. : CONTEXT INDICATOR SP : KPI TO PROMOTE THE
USAGE OF THE
SERVICES : GOAL
SP : CONTEXT SET SERVICE PROMOTION
(SP) : CAPABILITY
PROMOTION OF THE
SERVICE : PROCESS
HIGHLIGHT THE
SERVICE : PATTERN
HIGHLIGHT THE
SERVICE : PROCESS
VARIANT
INFORM
MUNICIPALITIES WITH
SIMILAR PROFILE
ABOUT HIGHLY USED
SERVICES : PATTERN
INFORM
MUNICIPALITIES WITH
SIMILAR PROFILE
ABOUT HIGHLY USED
SERVICES : PROCESS
VARIANT
Capability-driven development of a SOA platform: a case study
Case study
Capability model

27. Capability-driven development of a SOA platform: a case study
Case study
Process model
"GROUP" PATTERN
"GROUP"
COMPOSITE STRUCTURE PROCESS VARIANT
"GROUP"
COMPOSITE STRUCTURE PROCESS VARIANT
"GROUP" PATTERN
USAGE OF THE
SERVICE IN OTHER
MUNICIPALITIES:
CONTEXT ELEMENT
AMOUNT OF ACTIONS /
SUBMISSIONS PER
MONTH:
CONTEXT ELEMENT
FEEDBACK IN SOCIAL
NETWORKS:
CONTEXT ELEMENT
MASSIVE MAILING TO
OTHER
MUNICIPALITIES WITH
SIMILAR PROFILE
CONTACT PMO FOR
SERVICE
DISSEMINATION
RUN HIGHLIGHTING
PROCEDURE ONCE
EVERY 72 HOURS
RUN HIGHLIGHTING
PROCEDURE ONCE
EVERY 24 HOURS
HIGHLIGHT
THE SERVICE
CHECK THE AMOUNT
OF AVAILABLE
SERVICES IN
MUNICIPALITY'S
HOMEPAGE
INFORM OTHER
MUNICIPALITIES
ABOUT HIGHLY USED
SERVICES
+
HIGHLIGHT SERVICE
THAT IS HIGHLY
USED IN SIMILAR
MUNICIPALITY
+

28. Capability-driven development of a SOA platform: a case study
Case study

29. Capability-driven development of
a SOA platform:
a case study
FP 7 ICT Programme Collaborative
Project no: 611351
International Workshop on Advances in Services DEsign based on the Notion of CApability
ASDENCA 2014
Agenda
Introduction
Research methodology
Case study
Lessons learned
Conclusion

30. Capability-driven development of a SOA platform: a case study
Lessons learned
Motivation to adopt CDD
everis is highly motivated due to:
• Perception of current limitations in the platform.
• Expectations of new features that the CDD methodology
and tools can enable (self-adaptation).

31. Capability-driven development of a SOA platform: a case study
Lessons learned
Modelling issues
Difficulties with perspective and granularity.
CAPABILITY
PROBLEM
SOLUTION
GOAL CONTEXT
RESOURCES PROCESSES
INFORMATION TECHNOLOGY
Capacity:
Ability:
Enterprise:
Goal:
Context:
Goal KPI:
Capability definition template

32. Capability-driven development of a SOA platform: a case study
Lessons learned
Modelling issues
Difficulties with perspective and granularity.
We envision the need of relationships among capabilities:
C1MUNICIPALITY
OWNER
EVERIS
C2
OWNER
ENABLER
SOA1
SOA1.1 SOA1.2 SOA1.3
<
C_SLA1
C_SLA2
<
C_SLA3
Perspective
Refinement
Context or
quality levels

33. Capability-driven development of a SOA platform: a case study
Lessons learned
Modelling issues
How to start capability modelling.
LEGEND
ACTIVITY
PRECEDENCE
RELATIONSHIP
GOAL MODELLING
KPI
SPECIFICATION
STAKEHOLDER
MODELLING
CONCEPT
MODELLING
CAPABILITY
MODELLING
IT ARCHITECTURE
DESIGN DRAFT
CONTEXT
MODELLING
BUSINESS
PROCESS
MODELING
PATTERNS
MODELLING OR
SELECTION
Who should be involved in modelling.

34. Capability-driven development of a SOA platform: a case study
Lessons learned
Modelling issues
What modelling notations to use.
How to elicit and model relevant context elements.

35. Capability-driven development of a SOA platform: a case study
Lessons learned
Modelling issues
What modelling notations to use.
How to elicit and model relevant context elements.

36. Capability-driven development of a SOA platform: a case study
Lessons learned
Modelling issues
How to identify and model variability
1
2 3
4
5
6
1
2 3
4
7
8
6
1
2 3
4
9
10 11
6
+
+
(A or B) and C D and E F and G and H
1
2 3
4
x
5 7
8
9
10 11
6
+
+
x
(A or B) and C
D and E
F and G and H

37. Capability-driven development of a SOA platform: a case study
Lessons learned
Modelling issues
How to identify and model variability
1
2 3
4
6
PRODUCT
READY TO
BE 6-ED
PRODUCT
JUST 4-ED OPTION1
INSERT
START
5
END
START PRODUCT
JUST 4-ED
OPTION2
INSERT
START
7
END
START PRODUCT
JUST 4-ED
8
OPTION3
INSERT
START
END
START PRODUCT
JUST 4-ED
END PRODUCT
JUST 4-ED
9
10 11
+
+
END PRODUCT
JUST 4-ED
END PRODUCT
JUST 4-ED
(A or B) and C
D and E
F and G and H

38. Capability-driven development of a SOA platform: a case study
Lessons learned
Modelling issues
How to identify and model variability
END PRODUCT
JUST 4-ED
END PRODUCT
JUST 4-ED
1
2 3
4
6
PLACEMENT
5 7
8
9
10 11
+
+
PLACEMENT
REPLACEMENT1
REPLACEMENT2
REPLACEMENT3
(A or B) and C D and E F and G and H

39. Capability-driven development of
a SOA platform:
a case study
FP 7 ICT Programme Collaborative
Project no: 611351
International Workshop on Advances in Services DEsign based on the Notion of CApability
ASDENCA 2014
Agenda
Introduction
Research methodology
Case study
Lessons learned
Conclusion

40. Capability-driven development of a SOA platform: a case study
Conclusion
Summary
• Capability modelling is central to capability-driven
development (CDD).
• Case study research on the industrial application of CDD to
a SOA platform project
• CDD facilitates a systematic analysis of organisational needs
and designing a context-aware IT solution.
• The CDD methodology still needs improvement.
Future work
• Method: guidelines for goal-first capability modelling,
variability modelling, context elicitation and modelling,
run-time adjustment…
• Validation: controlled experiment, case studies
Thanks!