Upload
caas-eu-fp7-project
View
113
Download
3
Tags:
Embed Size (px)
Citation preview
Capability Driven Development – an Approach to Support Evolving
Organizations
paper at PoEM 2012
Janis Stirna1, Jānis Grabis2, Martin Henkel1, Jelena Zdravkovic1
1 Department of Computer and Systems Sciences, Stockholm University, Sweden 2 Information Technology Institute, Riga Technical University, Latvia
Outline
3
Background: Enterprise Modelling (EM) EM is a method for developing, acquiring, and communicating enterprise
knowledge and user requirements by a structured, iterative, and modelling approach.
The approach is guided by a number of conceptual sub-models, each focusing on a particular aspect of the application.
The EM process involves a group of stakeholders and a modelling facilitator
EM application in practice is usually supported bycomputerized tools – EM tools
Goals Model
Business Rules Model
ConceptsModel
Business Process Model
Actors and Resources
Model
Technical Components and Requirements Model
defines,is_responsible_for
motivates,requires affects,
defined_by
uses, refers_to
refers_to
supportstriggers
uses, produces
performs,is_responsible_for
defines
defines,is_respon-sible_for
uses, refers_to
motivates,requires
Business Rules Model
motivates,requires
Background: patterns in an organizational setting
4
generic and abstract organisational design proposals that can be easily adapted and reused in different organisational situations
Background: Patterns can be executable
5
The AKM platform,developed in the MAPPER project
The Challenge
Changing business contexts
Influences of collaborators’ business models
Limited support for changes in non-functional requirements
Inability to model execution contexts
High cost of developing applications for different contexts
Limited platform usage
Gap between EM and MDD
Capability
We need:rapid response to changes in the business context development of new capabilitiesrun-time configuration and adjustment of applications
Capability is the ability to continuously deliver a certain business value in dynamically changing circumstances.
Key Concepts
Enterprise and capability modelsGoal KPI
Capability delivery context modelsContext KPI
Capability delivery patternsResource allocationProcess variantsService and/or cloud variants
Initial meta-model for Capability Design
GoalCapability requires
KPI
requires
influences
Context requires
Context Type
measured by
Pattern
requires
Process
motivates
Process Variant
Resource
Context Situation
has
Measurable Property
Goal KPIContextl KPIrequires
defines
supported by requires
Extended meta-model considering
cloud services
GoalCapability requires
KPI
requires
influences
Context Set requires
Context Type
measured by
Pattern
requires
Process
motivates
Process Variant
Resource
Context has
Measurable Property
Goal KPIContextl KPIrequires
defines
supported by requires
Cloud Service
delivered by
IaaS PaaS SaaS
Service Component
realized Implementation (BPEL, WSDL)
has
Operational SC
Business SC
Cloud Resource
supported by
related_to
Delivery
Design
ContextSituation
has status
requires
has
Example CaseA building operator aims to run its buildings
efficiently and in an environmentally sustainable manner FP7 project EnRiMa – Energy Efficiency and Risk Management in
Public Buildings
Different buildings to be operated efficiently in different environments Market conditions Energy technologies ICT technologies
Example Case: Goal Model
Goal 1.2: To minimize CO2
emissions
Goal 1.3: To minimize energy
consumption
Goal 1.4: To minimize
energy costs
Goal 1.5: To use renewable
energy
Goal 1.1: To satisfy occupant
requirements
Goal 1: To run the building efficiently and environmentally
sustainable
GoalKPI: Occupant
satissfaction
GoalKPI: Desired
temperature (C)
require
GoalKPI: CO2 emissions (kg
per year)
requires
GoalKPI: Energy consumption
(kWh/m2)
requires
GoalKPI: Enery costs
(€)
requires
GoalKPI: Renewables
(%)
requires
FP7 project EnRiMa – “Energy Efficiency and Risk Management in Public Buildings” (proj. no. 260041)
Capability, context and capability delivery pattern for “Older building with low ICT infrastructure”
ReqContext: No PV
installed
ReqContext: No energy
storage
ReqContext: Closed ICT
infrastructure,
Cability: Older building, low ICT infrastructure
ReqContext: Fixed price
energy contracts
Pattern: Older building, low ICTSolution: Proc: Energy audit and configurationProc: Infrastructure integration processProc: Deploymen in cloudProc: negotiate temperature intervals with the occupantsProc: Passive monitoring and advisory mode for these KPIs
Context: No PV installed
Context: No energy storage
Context: Closed proprietary system
Context situation: MI building in Riga
Context: Fixed electricity and
gas prices
Context KPI: desired temperature 19 C
Context KPI: CO2 emissions 1100
kg per year)
Context KPI: Energy consumption 200
kWh/m2
Context KPI: Enery costs
100000€
Context KPI: Renewables
5 %
Pattern: Manual data entry
uses
supported by
required by
required by
ReqContext: Some data available
Context: Ambient temperature data
for 3 months
Pattern: Run template based audit
uses
required by
Capability, context and capability delivery pattern for “Modern building with high ICT infrastructure.”
ReqContext: No PV
installed
ReqContext: No energy
storage
ReqContext: Open ICT
infrastructure,
Cability: Modern building, high ICT infrastructure
ReqContext: Open energy
market
Pattern: Modern building, high ICTSolution: Proc: Energy audit and configurationProc: Infrastructure integration processProc: Deployment as external serviceProc: negotiate temperature intervals with the occupantsProc: daily update of building sensor data, weather data, pricing data, scenario generationProc: Active optimization with these KPIs
Context: No PV installed
Context: No energy storage
Context: Siemens Desigo building
management system
Context situation: AH building in Stockholm
Context: Spot pricing
model
Context KPI: desired temperature 18.5-
21.5 C
Context KPI: CO2 emissions 1100
kg per year)
Context KPI: Energy consumption 90
kWh/m2
Context KPI: Enery costs
100000€
Context KPI: Renewables
50 %
Pattern: Integrate with Siemens Desigo
supported by
required by
required by
ReqContext: Sensor data
available
Context: Sensor data available for
2 years
Pattern: Run full energy audit
uses
required by
Two Capability Delivery Patterns
Capability delivery pattern contains:
Capability: Old building, low ICT
Capability: Modern building, high ICT
ICT infrastructure integration process
Pattern: Manual data entry
Pattern: Integrate with Siemens Desigo
Energy audit and configuration
Pattern: Template based audit
Pattern: Run full energy audit
CDD Methodology
16
Business change & Required capability
What we need… Methods for
capability design pattern capturing and design; matching with capabilities Runtime adjustment …
Tools …
Actual patterns (e.g. best practices, services, etc) …
Business models
….