Enterprise Architecture Management & Cloud Computing
Fachtagung FUTURE BUSINESS CLOUDS beim BMWi, Berlin, 6. Juni 2013
Prof. Dr. Alfred Zimmermann
alfred.zimmermann@reutlingen-university.de
ARL – Architecture Reference Lab & Architecture Research Group
© Prof. Dr. Alfred Zimmermann & SOA Innovation Lab
www.soa-lab.de
> AGENDA
FACHTAGUNG „FUTURE BUSINESS CLOUDS“
DONNERSTAG, 6. JUNI 2013, 10.00–17.15 UHR – BUNDESMINISTERIUM FÜR WIRTSCHAFT
UND TECHNOLOGIE (BMWi), INVALIDENSTRASSE 48, 10115 BERLIN
acatech – DEUTSCHE AKADEMIE
DER TECHNIKWISSENSCHAFTEN
Hauptstadtbüro
Unten den Linden 14
10117 Berlin
T 030 / 20
63
09
60
Geschäftsstelle
Residenz München
Hofgartenstraße 2
80539 München
T 089
/ 5
20
30
90
info@acatech.de
www.acatech.de
info@acatech.de
www.acatech.de
Fachlicher Ansprechpartner:
Dr.-Ing.; Dipl.-Inform. Christoph Vornholt
Koordinator »Stadt der Zukunft«
Bereich Technologien
T 089 / 1 89 57 48-66
vornholt@acatech.de
Organisatorischer Ansprechpartner:
Thomas Heger
Referent Veranstaltungsmanagement
T 089 / 52 03 09-21
heger@acatech.de
ZEIT
PROGRAMM
REFERENTEN
10:00 – 10:15
Begrüßung
Dr. Andreas Goerdeler, Bundesministerium für Wirtschaft und Technologie, BMWi
10:15 – 10:30
Cloud Computing und der Weg in die digitale Gesellschaft
Prof. Dr. Henning Kagermann, acatech – Deutsche Akademie der Technikwissenschaften
10:30 – 11:00
Geschäftsmodelle aus den Wolken – Cloud-basierte Geschäftsmodelle
für Nutzer und Anbieter
Prof. Dr. Helmut Krcmar, TU München
11:00 – 11:30
Logistik auf dem Weg zur hybriden Dienstleistung aus der Cloud
Prof. Dr. Michael ten Hompel, Fraunhofer-Institut für Materialfluss und Logistik
11:30 – 11:50
Kaffeepause
11:50 – 12:20
The European Cloud Partnership: Demand and Supply
Dirk van Rooy, European Commission, Software & Services, Cloud, DG Connect E2
12:20 – 12:50
Computing in the Cloud – Activities at EIT ICT Labs
Prof. Seif Haridi, EIT ICT Labs
12:50 – 13:50
Lunch
13:50 – 14:05
Future Business Clouds – Wo steht Deutschland im internationalen
Vergleich
Prof. Dr. Ulrike Steffens, OFFIS e.V.
14:05 – 14:35
Cloud-Services für den Mittelstand, ein strategisches Wachstumsfeld
Dirk Backofen, Telekom Deutschland GmbH
14:35 – 15:05
Work the way you live
Michal Korbacher, Google Germany GmbH
15:05 – 15:35
Cloud 2013+ - Reizwort oder Nutzen?
– Digitale Unternehmen, veränderte Märkte, grenzenlose Potenziale –
Karin Sondermann, DriveChange!
15:35 – 15:55
Kaffeepause
15:55 – 16:25
Enterprise Architecture Management und Cloud
Prof. Dr. Alfred Zimmermann, Universität Reutlingen
16:25 – 16:55
Using Enterprise Architecture to plan your move to the Cloud
Fabio Castiglioni, IBM Italien
16:55 – 17:25
Beyond the Clouds: Trends in Cloud Computing for Science
Dr. Kate Keahey, University of Chicago
2
© Prof. Dr. Alfred Zimmermann
Agenda
1.
EAM for Services & Cloud Computing
2.
ESAMI – Enterprise Services Architecture Metamodel Integration
3.
ESARC – Enterprise Services Architecture Reference Cube
3
EAM-SOA Innovation Lab
www.soa-lab.de
in Germany and Switzerland
Scientific and Industrial Network of ARL – Architecture Reference Lab
4
© Prof. Dr. Alfred Zimmermann
EAM - Enterprise Architecture & Management
Align Business and IT through Integral Architectural Services
Information
Systems
People
Business
Processes
Information
Systems
Architecture
Business &
Information
Architecture
Enterprise
Level
Business
Process
Level
Implementation
Level
Information
Technology
Technology &
Operation
Architecture
Enterprise
Architecture
Business
Strategy
5
© Prof. Dr. Alfred Zimmermann
The Open Group Architecture Framework (TOGAF 9.1)
6
© Prof. Dr. Alfred Zimmermann
Mapping TOGAF – ArchiMate 2.0
© 2009-2012 The Open Group, All Rights Reserved
Personal PDF Edition. Not for redistribution
ArchiMate
®
2.0 Specification
13
Implementation & Migration
Business layer
Application layer
Technology layer
Information
Behavior
Structure
Motivation
Phase A:
Architecture
Vision
Preliminary
Requirements
Management
Phase H:
Architecture
Change
Management
Phase E:
Opportunities
& Solutions
Phase F:
Migration
Planning
Phase G:
Implementation
Governance
Phase B:
Business
Architecture
Phase C:
Information
Systems
Architectures
Phase D:
Technology
Architecture
Figure 8: Correspondence between ArchiMate (including extensions) and TOGAF
Although some of the viewpoints that are defined in TOGAF cannot easily be mapped onto
ArchiMate viewpoints, the ArchiMate language and its analysis techniques do support the
concepts addressed in these viewpoints. While there is no one-to-one mapping between them,
there is still a fair amount of correspondence between the ArchiMate viewpoints and the
viewpoints that are defined in TOGAF. Although corresponding viewpoints from ArchiMate and
TOGAF do not necessarily have identical coverage, we can see that many viewpoints from both
methods address largely the same issues.
TOGAF and ArchiMate can easily be used in conjunction and they appear to cover much of the
same ground, although with some differences in scope and approach.
7
© Prof. Dr. Alfred Zimmermann
Integration Scenario of Business Architectures from
ArchiMate
®
2.0 and TOGAF 9.1
Element
Example
Model
Capability
BusinessActor
BusinessRole
Process
Service
BusinessActor =
Language
Insurance
Department
BusinessRole =
Travel
Insurance
Seller
Process = tale out
travel insurance
Service = Offering
travel insurance
BusinessActor
BusinessRole
Business
Collaboration
BusinessInterface
Location
BusinessActivator
(Viewpoint)
Element
Example
Model
Capability
Actor
Role
OrganizationUnit
Function
Process
BusinessService
Event
Location
Actor
Role
Location
Organization
(Viewpoint)
Open Group Standard
ArchiMate
®
2.0
Specification.
The Open Group
2009-2012,
ISBN 1-937218-00-3
Open Group Standard
TOGAF 9.1.
The Open Group 2011,
ISBN 978-9087536794
8
© Prof. Dr. Alfred Zimmermann
ESAMI – Enterprise Services Architecture Metamodel Integration
Consolidated EAM Reference Architecture: Analysis and Integration
Correlation Index
Integration Options
EAM Reference Architecture
Model
Element ArchiMate TOGAF ArchiMate TOGAF
Capability
Origin
ActorRole
Actor
2
2
p
Business
Activator
Role
3
2
m
Collabo-
ration
3
0
m
Organiz.
Unit
1
3
p
3
3
p
3
3
m
3
0
m
1
3
p
3
3
m
3
3
m
3
3
m
Reference
Documents
File
Pages
25-32
87-88
33-34
86
82-84
89
Authors
20130505-ESAMI
3
3
m
ArchiMate
Specific.
and
TOGAF
Standard
Organi-
zation
Organi-
zation
Location
Driver
Goal
Objective
Location
m
m
r
m
p
m
r
m
m
m
m
m
Organiz.
Unit
Business
Function
Collabo-
ration
Business
Event
0 no correlation
1
low correlation
2
medium correlation
3
strong correlation
r reject
p partially
m mandatory
(leading model)
9
© Prof. Dr. Alfred Zimmermann
ESAMI – Enterprise Services Architecture Metamodel Integration
SOA Ontology Typed Metamodel of Business Reference Architecture
Role
(HumanActor)
Collaboration
(HumanActor)
(HumanActor)
Actor
Organization
Unit
(Element)
Location
(Element)
Driver
(Element)
Goal
(Element)
Objective
(Element)
Business
Function
(Element)
Business
Process
(Process)
Business
Service
(Service)
Service
Quality
(Thing)
Contract
(ServiceContract)
Business
Event
(Element)
Product
(Element)
Business
Information
(Information Type)
Composite
(Composition)
(Element)
Element
Meaning
(Element)
Value
(Element)
Representation
(Element)
Business
Rule
(Element)
Knowledge
Skills
(Element)
10
© Prof. Dr. Alfred Zimmermann
Integrating Cloud Computing Reference Architectures with
Service-Oriented Cloud Computing Infrastructure (SOCCI)
NIST CC-RA, IBM CC-RA, CSA CC-RA, Open Group SOCCI Framework
Information Technology Laboratory Cloud Computing Program
Cloud Service Provider
The NIST Cloud Computing
Reference Architecture
Cloud Service
Management
Cloud Carrier
Cloud
Auditor
Cloud
Service
Consumer
Provisioning/
Configuration
Portability/
Interoperability
Security
Audit
Privacy
Impact Audit
Performance
Audit
Business
Support
Secu
rit
y
Pr
iv
ac
y
Cloud
Broker
Service
Intermediation
Service
Aggregation
Service
Arbitrage
Physical Resource Layer
Hardware
Facility
Resource Abstraction and
Control Layer
Service Layer
IaaS
SaaS
PaaS
19
© 2011 IBM CorporationThe Cloud Computing Reference Architecture
Governance
Security, Resiliency, Performance & Consumability
Cloud Service Creator Cloud Service
Consumer Cloud Service Provider
Common Cloud Management Platform (CCMP) Operational Support Services (OSS) Cloud Services Inf rastructure-as-a-Service Platf orm-as-a-Service Sof tware-as-a-Service Business-Process-as-a-Service Business Support Services (BSS) Cloud Service Integration Tools Consumer In-house IT Service Creation Tools Inf rastructure Existing & 3rdparty
services, Partner Ecosystems
Service-Oriented Cloud Computing Infrastructure (SOCCI) Framework
11
6
Enabling Applicable Architectural Layers
Figure 3: SOCCI High-Level View
SOCCI Architecture Building Blocks (ABBs) consist of the SOCCI elements and SOCCI
Management Building Blocks. The former leverages the latter to interface with the users. The
SOCCI Management Building Blocks are categorized as operation-centric and business-centric.
The division between the two is dependent on the type of service provided. The Business ABBs
relate to supporting the business functions needed to be able to create, support, and consume an
IaaS offering; e.g. metering, billing, and location management. The Operational ABBs relate to
operational functions supporting/leveraging the SOCCI elements to provide the operational
management services; e.g., virtualization and provisioning management.
SOCCI Management Building Blocks that enable SOCCI are described below.
Business ABBs:
Metering Manager (measured service enabler) tracks consumer usage statistics for the
11
Prof. Dr. Alfred Zimmermann
Services and
Services System
1: Principle of Services
2: Services Lifecycle
Services Technologies
3: Web Services
4: Service-Orient. Architecture
5: Services Relationships
6: Services Composition
7: Business Process
Management and Integration
Services Consulting
and Delivery
8: Business Grid
and Cloud Computing
9: Enterprise Modeling
and Management
10: Service-Oriented Consulting
Methodology
11: Service Delivery Platform
and Methodology
Services Solutioning
and Management
12: Application Services
and Standards
13: Security, Privacy,
and Trust in Services
14: IT-Services Management
Body of Knowledge Areas
of Services Computing of IEEE
Body of Knowledge Areas
of Services Computing (SC-BKA of IEEE)
12
ARL Research Programs – 2013
© Prof. Dr. Alfred Zimmermann
1. EAM Reference
Architecture
2. EAM COLUMBUS
Reference Environment
3. SCC Reference
Architecture
4. SCC COLUMBUS
Reference Environment
5. Scientific Services:
ARL Platform, Pattern Repository, Situation Room, Conferences, Research Schools, Publications
Enterprise
Architecture
Management
Services
Computing
Computing
Cloud
Semantic-based
Service
Repositories
Domain
Engineering and
Business Arch.
Service
Engineering and
BPM for SaaS
Evaluation of
Services on Cloud
Platforms
Cloud
Resources
Management
Serv. Comp.
Metamodel f. Cloud
Comp.
EsaMetamodel
EsaOntology
EsaInference
EsaDiagnostics
EsaMaturity
EsaPatterns
EsaKnowledge
EsaRefArchitecture
Evaluation of Cloud
IaaS, PaaS
Security for Cloud
13
Reference Architecture
Basic Mappings
n
Reference Models: conceptual models of a functional decomposition together with the data
flows between elements
n
Architecture Patterns: show known architecture quality attributes, and represent recurring
solutions, within architectural constraints for given problems and solutions
n
Reference Architecture: model of related software elements and typed building blocks as a
result of a pattern-based mapping of reference models to software elements
Software
Architecture
Architecture
Patterns
Reference
Models
Reference
Architecture
© Prof. Dr. Alfred Zimmermann
14
ESA – Framework: ESARC© Reference Architecture Metamodel,
Ontology, Architecture Maturity Model, Pattern Language for EAM
© Prof. Dr. Alfred Zimmermann
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen
Reutlingen University
27
ESARC© - Enterprise Services Architecture Reference Cube
Business & Information Reference Architecture
C on fig ur ati on o f B us in es s & In fo rm ati on D em an ds
Business Products and Services
B us in es s Me as ur es a nd C on tr ol s
Actors, Roles, Knowledge, Skills Business Domains and Capabilities
Business Rules for Business Products, Services, Processes Business Processes, Workflows, Policies, Procedures
Business Vision, Drivers, Goals, Objectives Location and Organization
Business Information for Products, Processes, Controls
Alfred Zimmermann © Alfred Zimmermann and SOA Innovation Lab 2011
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen
Reutlingen University
29
ESARC© - Enterprise Services Architecture Reference Cube
Information Systems Reference Architecture
C o n fi g u ra ti o n o f A p p lic ati o n Sy ste m s
Information Services for Enterprise Data
B u si n es s & Sy ste m s Mo n ito ri n g Se rv ic es Utility Services Task Services Rule Services Process Services
Collaboration Services and Integration Services Channel Consumer Interaction Services Batch
Services Access Services Operational Systems Business Objects and Components Event Handling Services
Analytics Services
Alfred Zimmermann © Alfred Zimmermann and SOA Innovation Lab 2011
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen
Reutlingen University
30
ESARC© - Enterprise Services Architecture Reference Cube
Technology Reference Architecture
Se cu ri ty Sy ste m Database System TP Monitor System Sy ste m s Ma n ag em en t Pl atfo rm MQ System Enterprise Service Bus
Rule Server Product Configuration, Process Rules, Policies
Process Orchestration Server Collaboration Framework Choreography Framework
Portal & Workflow Server Application Server Interaction Framework
Desktop, Web, Mobile
C o n fi g u ra ti o n o f In fr as tr u ctu re Pr o d u cts Alfred Zimmermann © Alfred Zimmermann and SOA Innovation Lab 2011
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen
Reutlingen University
26
ESARC© - Enterprise Services Architecture Reference Cube
Architecture Governance and Management
G o ve rn an ce a n d Ma n ag em en t Pr ac ti ce s
Service Security, Quality, Testing, Monitoring, Analytics Service Contracts, Registries, Reuse
Ma n ag em en t Me as u re s an d C o n tr o ls
Service Strategy & Life Cycle Management Planned, Development, Test, Active, Deprecated, Sunsetted
Service Ownership, Definition, Versioning Empowerment, Governance Board, Collab. & Communic.
Policies for Governance and Decision Definition Governance Cycle Plan, Define, Enable, Measure and Control Compliance with internal and external Standards
Alfred Zimmermann © Alfred Zimmermann and SOA Innovation Lab 2011
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen
Reutlingen University
31
ESARC© - Enterprise Services Architecture Reference Cube
Operation Reference Architecture
B u si n es s & Sy ste m s O p er ati o n a n d Mo n ito ri n g C o n fi g u ra ti o n o f O p er ati o n -s u p p o rte d Pe o p le a n d Sy ste m s Source: http://www.dynatrace.com Alfred Zimmermann © Alfred Zimmermann and SOA Innovation Lab 2011
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen
Reutlingen University
32
ESARC© - Enterprise Software Architecture Reference Cube
Cloud Services Reference Architecture
C o n fi g u ra ti o n o f Se rv ic es a n d Pr o ce d u re s Se rv ic e Ma n ag em en t Pl atfo rm
PRaaS (Business Process as a Service) SaaS (Software as a Service) PaaS (Platform as a Service) IaaS (Infrastructure as a Service)
Measured Service Rapid Elasticity Resource Pooling Broadband Network Access On-Demand Self Service
Pr iv ate C lo u d C o m m u n ity C lo u d Hybrid Cloud Pu b lic C lo u d
Source: Adaptation of NIST Cloud Computing Synopsis and Recommendations
Alfred Zimmermann © Alfred Zimmermann and SOA Innovation Lab 2011
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen
Reutlingen University
34
Element is the central generic service concept on which the specialized model elements
of ESARC - Enterprise Services Reference Cube are constructed
Service-Oriented Architecture Ontology, The Open Group, 2010
Service-Oriented Architecture Ontology
Detail Generic Model
Alfred Zimmermann ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen Reutlingen University
ESARC© - Business & Information Reference Architecture
Metamodel
36 S. Bourscheidt, T. Breuer, T. Brunner, B. Fetler, G. Fogel: ESARC-Ontology MSc. Project, 2012 Alfred Zimmermann ! The specialized concepts of the Business & Information Reference Architecture are
represented with associations of a class model
! These specialized concepts are integrated with the generic concepts "Element" and
"Composition" of the generic SOA Ontology from the Open Group
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen
Reutlingen University
33
Service-Oriented Architecture Ontology
Technical Standard
Service-Oriented Architecture Ontology, The Open Group, 2010 ! Meta-Modell for Service-oriented Architecture
! Ontology in OWL for Service-oriented Architecture
Alfred Zimmermann
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen
Reutlingen University
ESARC© - Business & Information Reference Architecture
Ontology wit Asserted View in Protégé
38
Asserted View from Protégé showing the „is a“-relationship between specific concepts of the Business & Information Reference Architecture and the generic SOA-Ontology Reference Architecture
Alfred Zimmermann S. Bourscheidt, T. Breuer, T. Brunner, B. Fetler, G. Fogel: ESARC-Ontology MSc. Project, 2012
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen
Reutlingen University
ESARC© - Business & Information Architecture
Ontology with Properties in Protégé
39
View from Protégé showing the structure elements of the Ontology (left side) and corresponding Properties (right side) as a base for Navigation/Interaction and Architecture Knowledge Inference
Alfred Zimmermann
S. Bourscheidt, T. Breuer, T. Brunner, B. Fetler, G. Fogel: ESARC-Ontology MSc. Project, 2012
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen
Reutlingen University
41
SOAMMI (SOA Maturity Model Integration)
Metamodel
(adapted from TOGAF, CMMI, a.o.) Hypothesis of our research! CMMI (Capability Maturity Model Integration) is well known as suitable framework to assess software processes, but not software architectures, nevertheless the meta model of CMMI can be extended to evaluate architecture capabilities of service-oriented systems
! The idea of a pattern language can be applied consistently for both architecture assessments and optimization, setting a base for effective cyclic evaluations of service-oriented systems
Specific Practice Specific Goal Architecture Area Maturity Level Generic Practice Generic Goal 0..10 1..* 1..* Architecture Domain Architecture Pattern Capability Level 1..* 1..* 1..8 1..22 1..* 1..* Alfred Zimmermann
© Alfred Zimmermann and SOA Innovation Lab 2011
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen
Reutlingen University
SOAMMI (SOA Maturity Model Integration)
Architecture Maturity Levels (adapted CMMI, Togaf 9/ACMM)
Maturity Level 1: Initial • service architecture is not performed or is incomplete or with no or initial coverage • architecture is unpredictable and poorly controlled
• initial service architecture methods and knowledge transfer about services and architectures
Maturity Level 2: Managed• service architecture is managed, having medium completeness and coverage • vendor supports learning about architectures and corrective actions are taken when necessary • vendor service architecture is institutionalized within own products
Maturity Level 3: Defined
• service architecture is defined, having large, increasing completeness and coverage • customer service architecture is agile tailored from standard vendor architecture • vendor supports service strategy, architecture governance, methods and tools
Maturity Level 4: Quantitatively Managed
• architecture artifacts and benefits are measured at vendor and customer side • architecture is based on measured parameters an monitored business services • causes of special variations are addressed
Maturity Level 5: Optimizing
• defects are prevented at customer and vendor side • innovations are added based on a vendor / client mutual roadmap • change is expected, not feared and improvements are proactive
42 © Alfred Zimmermann and SOA Innovation Lab 2011 Alfred Zimmermann
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen
Reutlingen University
SOAMMI (SOA Maturity Model Integration)
Architecture Capability and Maturity Levels
(adapted CMMI)C a p a b il ity L e v e ls Maturity Level 1: Initial Maturity Level 2: Managed Maturity Level 3: Defined Maturity Level 4: Quantitatively Managed Maturity Level 5: Optimizing 0 1 2 3
AA1 AA2 AA3 AA4 AA5 GG1 GG2 GG3 GG2 GG3 Staged Representation
! The assessment of capability levels could be applied to iterate specific architecture areas or to assess or improve a focused innovation aspect of some architecture areas
! To verify and support the persistent institutionalization of architecture areas we have introduced in the SOAMMI framework generic goals and practices
! All architecture areas are affected by the same generic goals and generic practices
44 © Alfred Zimmermann and SOA Innovation Lab 2011 Alfred Zimmermann
Continuous Representation
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen
Reutlingen University
52
Service-oriented Architecture Capability Patterns
Architecture Assessment Pattern Language Scenario
Value Chain Business Product Business Service Business Process Control Information
! We have identified and distinguish a set of 43 patterns as parts of a new researched and introduced pattern language in the context of 7 Architecture Domains and 22 Architecture Areas
! Our architecture quality patterns accord to the Specific Goals, the Specific Practices and the Generic Goals from the SOAMMI framework
Alfred Zimmermann © Alfred Zimmermann and SOA Innovation Lab 2011
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen
Reutlingen University
SOAMMI Diagnostics and Improvement
Service-oriented EAM-Patterns in Reduced Canonical Form
Diagnostics
verify solution states and determine the problem
Improvement identify suitable solution elements for a given problem
! Problem
What is the problem to be solved using the pattern?
! Solution
What are solution elements suitable to solve the problem?
53 © Alfred Zimmermann and SOA Innovation Lab 2011 Alfred Zimmermann
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen
Reutlingen University
Typical vendor workshop
Overview Architecture principles, vision, requirements 1. SOA experiences Business architecture 5. Business domains and capabilities 9. SOA deployment units Application/ Information architecture Technology architecture 12. Integration capabilities Service and operation architecture 10. SAP service lines Architecture realization 15. SOA Tools 2. Architecture strategy management 3. Architecture requirements management 4. Architecture requirements development 6. Business services 7. Business products dependency 8. Business processes 13. Security 16. Architecture governance 14. Leading technology 11. SOA methods 17. Service Level Agreements 18. SOA best practices 19. Service compositioning/ provisioning 20. Interface technology 21/22. Integration tools/ method 23. Reuse of services Key message Fulfillment degree / /
01. No big implementation, many PoCs (> 100) with midrange companies
02. SOA as important part of overall strategy (no alternative); strategy change: wrapping of existing systems; new functionality are based on service orientation
06. Solution map available, method for identification of business services 07. Wrapper for monolithic functionality; business services are tightly coupled 09. Monolith not broken, no service oriented license model
11. Method for governance, guidelines, etc. for SOA available; candidate for SOA enablement: for processes which are not commodity (SCM, SRM, CRM); most use cases are GUI related
13. Standards e.g. SAML, ... can be interpreted in different ways 15. Tools available, roundtrip, end to end engineering process not supported
Vendor Workshop
Alfred Zimmermann
© SOA Innovation Lab 2010-2011
61
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen
Reutlingen University
43
SOAMMI (SOA Maturity Model Integration)
Architecture Areas and Maturity Levels
Requirements Management Business Domains & Capabilities Business Processes & Rules Data Entities & Components Business Objects System Services & Capabilities System Domains Platform Services Technology Services & Capabilities Architecture Standards & Compliance Architecture Strategy & Management
Business Architecture Business Architecture Information Architecture Information Architecture Application Architecture Application Architecture Technology Architecture Technology Architecture Architecture Realization ARM BDC BPR DEC BOB SSC SDO PFS TSC ASC Architecture Innovation and Development Causal Analysis and Resolution Architecture Strategy & Management
Architecture Strategy & Management CAR AID
Maturity Level Architecture Domain Architecture Area ID
Architecture Strategy & Management Architecture Strategy & Management
Enterprise Architecture Management Architecture Requirements Development Architecture Governance Business Capabilities & Services Business Products & Services Business Information Alignment Service Design & Transition Architecture Contracts EAM ARD GOV BCS BPS BIA SDT ACO Architecture Strategy & Management
Architecture Strategy & Management Architecture Strategy & Management Business Architecture Business Architecture Information Architecture Service & Operation Architecture Architecture Realization
Organizational Performance Monitoring Quantitative Architecture Management OPM QAM
1: Initial 2: Managed 3: Defined 4: Quantitatively Managed 5: Optimizing Alfred Zimmermann
© Alfred Zimmermann and SOA Innovation Lab 2011
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen
Reutlingen University
45
Software Patterns
Basic Concepts
! Pattern
! the core of a solution for a recurring problem that occur in a specific context
! based on verified design and practical experience
! articulates a common vocabulary of concepts and knowledge
! essential elements: extending the causal problem – solution pair
! Pattern Name
! Problem
! Solution
! Consequences – as results and trade-offs
! Pattern Catalog: a collection of self-contained
patterns indexed by categories
! Pattern Encyclopedia: an index of patterns
! Pattern System: a collection of patterns with
references between related patterns
! Pattern Language: a network (graph) of tightly
connected patterns giving solution chains for specific problems Model Views 1.Qrtl. 2.Qrtl. 3. Qrtl. 4.Qrtl. update Subscriber1 update Subscriber2 register unRegister changed setData getData Publisher Dependents Subscriber1 Subscriber2 Alfred Zimmermann
ESARC - Enterprise Services Architecture Reference Cube Hochschule Reutlingen Reutlingen University
5
Enterprise Architecture Methodology
Business Information Innovation Cycle
! Provide business value thru innovation and information technology
! Align and improve both: business and information technology ! Extend software methods towards business process management
! Integrate software engineering, service management, systems and operations ! Manage information technology like a business
Business & Information Architecture and Management Service Oriented Architecture & Engineering Processes & Systems Operations and Cloud Services Alfred Zimmermann © Alfred Zimmermann and SOA Innovation Lab 2011
