Keynote for EEWC2015
Download as PPTX, PDF1 like559 views
The document summarizes the key concepts and methodology of Capability Driven Development (CDD) for designing context-aware enterprise applications. It discusses CDD's focus on an enterprise's capabilities - the ability and capacity to achieve business goals in different contexts. The document outlines CDD's life-cycle process and development environment, including modeling capabilities, contexts, and variability. It also provides examples of applying CDD at industrial partners, and discusses challenges and future work in fully realizing the CDD approach.
Keynote for EEWC2015
- 1. Capability Driven Development of Context-aware Enterprise Applications – Challenges, Approach and Experiences Janis Stirna based on FP7 project CaaS:
- 2. Short info about Janis • PhD from KTH, 2001 • Prof at SU, 2015 • Teaching UML to 500 students • Research interests: EM, EA, EE, RE
- 3. Outline The general need for capability Overview of the CaaS project Overview of the application cases at SIV (Germany) and Everis (Spain) Overview of the CaaS methodology and development environment Other work done Reflection on challenges and the work ahead
- 4. Motivation: context changes, businesses need to adapt Bakery Factory Stockholm Arlanda has a goal not to shut down the flight operations due to snow ….but
- 5. Capability as a Concept • Enterprises must focus on their capabilities: the ability and capacity that enables an enterprise to achieve a business goal in a certain operational context • What is a Capability? The goal to accomplish The ability to engineer a bridge, e.g skills, experience The capacity such as money or tools to build a bridge The context in which the bridge must be built and used (location, weather, etc.) ? Capability
- 6. Key Concepts: Capability & Context • Capability is the ability and capacity that enable an enterprise to achieve a business goal in a certain context. • Context refers to situational properties relevant to capability delivery. • The company wants to sell ice creams on streets as long as it is sunny and the temperature is within a given range. • Context influences: rain, public events, season
- 7. Solution • Capability as a Service • A (reasonably) novel paradigm supported by four cornerstones Defined Best Enterprise Practices as Patterns Capability-driven Development (CDD) Methodology Capability Delivery Adjustments According to Context Capability Design and Delivery Environment
- 8. The overall approach Use case driven WP2 Use case (SIV) WP3 Use case (CLMS) WP4 Use case (Everis) WP5 Methodology (UR) WP6 Environment (Croz) WP7 Exploitation (Everis) WP8 Dissemination (UPVLC) WP9 Management (SU) WP1 Requirements (RTU) Deliverable D3.1 Page 52 Table 11: Medical compliance pattern le Compliance Pattern for medical issues (BPM) deal with the need of automated rule compliance of vessels approaching different rts with different legislations regarding medical issues ● Vessel approaching a new port ● Compliance with local regulations regarding the crew medical status required M Pattern er can exploit this set of processes for the overall business process of the rule mpliance system regarding medical status of the vessel’s crew le compliance, Port authorities, Maritime, Business process o Compliance Pattern (Business Process View) iness process model applicable in the cases where a vessel, approaching a ensure compliance regarding its cargo. Table 12 summarizes all the basic e proposed pattern.
- 9. Capability Driven Development - overall meta-model - Enterprise Modeling Reuse and Variability Context
- 10. Capability Driven Development - life-cycle process -
- 11. CDD Development Environment Architecture Overview 11
- 12. Architecture Overview of Capability Context Platform (CCP) 12
- 13. Capability Driven Development life-cycle process, navigation and adjustment at run-time
- 14. Capability Elicitation Capability elicitation, starting perspective: – Goal-first: business strategy – Service-first customer needs – Context-first: business conditions
- 15. Elicitation – A Case at SIV • The CaaS partner SIV is a Germany-based independent software vendor (ISV) and a business process outsourcing (BPO) provider for the utilities industry. • SIV has developed a domain-specific ERP platform kVASy® that supports all relevant value-added processes of market players. • All BPO services offered to SIV’s customers – mostly grid access providers and balance suppliers – are based on the functionalities of kVASy®. • SIV’s business goal is to deliver a maximum of business value to its customers by to combining best practice business processes with compliance to the market’s ever changing business rules and regulatory requirements.
- 16. Elicitation – A Case at SIV Goal 1 To constantly deliver business value to its customers Goal 9 To increase the degree of automation of case handling supports Goal 5 To support any communication protocol between market partners supports Goal 1.1 To implement change requirements for the kVASy® platform in an agile way Goal 1.2 To run the kVASy® platform as a cloud based service Goal 1.3To significantly reduce the complexisty of the kVASy® platform Goal 6 To support new market roles supports Goal 3 To implement customer change requests in an agile way supports Goal 4 To quckly adapt to regulatory changes that affect market communication supports Goal 8 To transform kVASy® into a SOA based platform supports Goal 7 To reduce time-to- market of product enhancements supports supports Goal 2 To efficiently control the business processes Goal 2.1 To optimize case throughput Goal 2.2 To achieve high process quality supports Goal 10 To reduce process costs supports Iteration
- 17. Elicitation – A Case at SIV “Message Validation” business process: …the recipient is supposed to validate each message (such as “energy consumption data”) against the underlying message specification. The sender is to be notified about any invalid message within a deadline specified by the regulatory authority Given the large number of messages to be processed, there are usually many concurrent cases that need some clearing. Hence, the size of the backlog can grow considerably over time leading to missed deadlines and/or overtime work. Thus - customer’s workload, the current backlog size, message type, exception types, and other, are represented by (different) context models, and (different) capabilities are elicited to handle those contexts.
- 18. Elicitation – A case at SIV Depending on the concrete context situation, the task “Remedy case” can be dynamically routed to the external business service provider (BSP), or left with the customer.
- 19. Documentation in the CDT • Model-oriented, with natural language for annotations • Open to different modeling languages • Intra- and inter-model links can be defined for traceability
- 20. Summary of experiences at SIV • The main objective of the process is to facilitate the specification for capability requirements in an integrated way following the multi-perspective views defined in the CMM to facilitate further application development. • Where to start - from business goals, services, or from relevant business contexts. In any of these strategies, both the functionality and the quality aspects of capability are captured, where the first are dictated by the CM, and latter by the setting of the goals and KPIs.
- 21. eGovernment SOA Platform at Everis Figure3: Situation beforetheSOA platform e adoption to the new law requirements, it was decided to create a common ucture (the SOA platform) for the whole network of councils to share common . In this way, all the councils could accessed to the services offered by the m, even though they could customized some aspects depending on each one t is shown in Figure 4: Figure4: Situation after SOA platform ble (Table 2) describes the main functions carried out by the SOA platform: Ca 100 municipalities Varying contexts Ca 10000 services running Many external providers Manual activation and maintenance
- 22. Capability Design Model for Dynamic Service Registration EC FP7 Project 611351 Figure37: Context model for the Dynamic Service Registration capability Process Variants: Capability: Pattern: Context model fragment: Goal: KPI:
- 23. Service Promotion Goals Model
- 24. Capability design for automatic service promotion EC FP7 Project 611351 Figure52: Context model for theService Promotion capability
- 25. Meta-model (current version) Capability GoalIndicator Context Indicator KPI ContextSet Process ProcessVariantCapability Delivery Pattern ContextElementRange Measurable Property ContextElement ContextType Resource Context Situation Context Element Value Variation Point Capability Delivery Variation Point Process Variant Variation Point Variation Aspect Adjustment ContextCalculation CapabilityAdjustment AdjustmentConstant EventBasedAdjustment ScheduledAdjustment KPIValue Calculation KPICalculation 1 uses instance specific values for calculation 0..* 1..* requires 1..* 1 calculates 1 0..* uses for calculation 0..* 1..* motivates 1..* 1..* defined in 0..* 1..* requires 0..1 0..* uses for calculation 1..* 1..* consists of 1 * influences * uses for calculation 0..* 0..* supports implementing 1 11..* 1 calculates value for 1 * measured by0..1 1 has * 1 supports decision making at 0..* * requires 1 1 has value 1..* 0..1 requires 1..* 1..* 0..* 1 requires 0..1 1 1..* 1..* 1 defines * 0..* 1..* 0..1 supported by 1 0..* defined in 1..* 0..* uses for calculation 0..* 1 consists of 1..* 1..* related to 0..1 1 has value 1..* 0..* use for calculation 0..* 1 requires 0..1 1 depends on 0..* 0..* supports decision making for 1 1 1..* For capability design, incl. goals, KPIs, context, measurable properties, etc. For variability design For specifying adjustment algorithms
- 26. How should this work? Elements of a Capability Model Patterns Enterprise Model Business Service Model Context Model Capability Model 26
- 27. 27 Business Service (Example: Process + Variants) Policy Type = advanced forward = specific to size = …. Context Model Weather = long cold period = …. Removal of Meter Installation of Meter Change of Meter Period Meter Reading Determine reading reason Period meter reading Determine metering point master data Write meter reading Determine and check register master data Loop over all Registers A B C Validate meter reading Write meter readin Removal of Meter Installation of Meter Change of Meter Period Meter Reading Archive messages Determine reading reason Period meter reading Determine metering point master data Write meter reading Determine and check register master data Loop over all Registers A B C Validate meter reading Write meter reading Removal of Meter Installation of Meter Change of Meter Period Meter Reading Archive messages Determine reading reason Period meter reading Determine metering point master data Write meter reading Determine and check register master data Loop over all Registers A B C Validate meter reading Write meter reading Patterns Policy Type SpecificAdvanced Enterprise Model (Concepts/Goals) Variation depending on Joint meta-model same modeling tool How should this work? Elements of a Capability Model Capability Model 27
- 28. The third use case: Model Driven Development of CDAs CNA CDT CCP Data providers MP value push CDA MP value push MP information Model and implementations Adjustment information zAppDev tool by CLMS, UK
- 29. Other work done • Requirements for the CDD methodology and CDD environment • Pattern repository • CDD methodology for designing capabilities and solutions (1st version) • Application of the CDD methodology at three industrial companies • CDD environment (two releases) • Market and exploitation plan • Dissemination: (1 journal paper, 10+ conference and workshop papers, 2 workshops organized)
- 30. Where would we use this approach? • Strategic planning and organizational design • Assessing the impact of context on the business design • Operational running of business • Monitoring the KPIs, adjusting the business delivery • Making use of emerging theories and technologies • E.g. consumer values and preferences, sensors, and big data • Addressing cross-sectorial challenges • E.g. energy efficiency, sustainability, cyber resilience Capability Goal V Context V Capacity V Ability V Best practice V
- 31. Plan: CaaS to market Year 3: Business feasibility Year 2: Technological feasibility Year 1: Conceptual feasibility current state:
- 32. Contacts • http://caas-project.eu/ • Papers (among many): • Solvita Berzisa, George Bravos, Tania Cardona González, Ulrich Czubayko, Sergio España, Janis Grabis, Martin Henkel, Lauma Jokste, Janis Kampars, Hasan Koç, Jan-Christian Kuhr, Carlos Llorca, Pericles Loucopoulos, Raúl Juanes Pascual, Oscar Pastor, Kurt Sandkuhl, Hrvoje Simic, Janis Stirna, Francisco Giromé Valverde, Jelena Zdravkovic: Capability Driven Development: An Approach to Designing Digital Enterprises. Business & Information Systems Engineering 57(1): 15-25 (2015) • Workshops: ASDENCA 2014, CoBI 2014, ASDENCA 2015, CoBI 2015, ASDENCA 2016 • PoEM 2015 in Valencia, paper deadline July 17 • Janis Stirna, js@dsv.su.se