Patterns in EAM

7 downloads 13070 Views 4MB Size Report
wwwmatthes.in.tum.de. A Pattern-based Approach to Enterprise Architecture Management. © sebis ... Cashier. Call Center. CallCenter. System. BoSha. System.
Fakultät für Informatik Technische Universität München

A Pattern-based Approach to Enterprise Architecture Management

Alexander M. Ernst Prof. Florian Matthes Software Engineering for Business Information Systems (sebis) wwwmatthes.in.tum.de A Pattern-based Approach to Enterprise Architecture Management

© sebis

1

Introducing EAM in an enterprise is a challenge: EA frameworks provide only limited support PERA 1989

PERA 2001 GRAI/GIM 1.0 1992

GERAM 1994

Legend:

GERAM 1.6.3 1999

CIMOSA 1984

CIMOSA 1999

superseded by

Start of development

Current version

influenced

Intermediate version

No further development

ARIS 1991

ARIS 7.1 2008 JTA 1.0 1996

TAFIM 1.3 1992

TAFIM 2.0 1994

JTA 7.0 2005

TAFIM 3.0 1996

TAFIM 2000

DoD EA TRM 0.04 2005

C4ISR 1.0 C4ISR 2.0 1996 1997

DoDAF 1.0 2003

TOGAF 1 1995

TOGAF 8.1 2003 TISAF 1.0 1997

EAP 1992

EAP 1996

TEAF 1.0 2000 FEAF 1.1 1999

NIST EA 1989 Zachman 1987

FEA 1.0 2001 NC3SAF 2000

NAF 2.0 2004

MODAF 1.2 2008

NAF 3.0 2007

Zachman 1992

Zachman 2.01 2007

IAF 1993

1990

DoDAF 2.0 2009 TOGAF 9 2009

MODAF 2005

E2AF 2003

1980s

DoDAF 1.5 2007

1993

IAF 1 1995

1996

A Pattern-based Approach to Enterprise Architecture Management

IAF 2 1997

E2AF 1.5 2006

IAF v3 2001

1999

IAF 4.0 2007

2002

2005

2008

2009 © sebis

2

Application landscape management requires a holistic view  Technical, social and economic aspects  Layers and crosscutting concerns  Relationships are more important than element details has, consists of, depends on, uses, controls, owns, produces, consumes,…

Business Service Layer Geschäfts-Service-Schicht

Application & Information Layer Infrastructure Service Layer Infrastruktur-Service-Schicht

KPIs & Metrics

Business & Organization Layer Blueprints & Patterns

Requirements & Projects

Strategies & Objectives

 Enterprise Architecture

Infrastructure & Data Layer Where to start? Which level of detail? Best practices?

A Pattern-based Approach to Enterprise Architecture Management

© sebis

3

Introducing EAM in an enterprise is a challenge: Information models are too complex

Specific examples:  ~ 50 classes (vendor A)  ~ 54 classes (vendor B)  ~ 220 classes (vendor C)  ~ 470 classes (vendor D)  At least twice as many associations  Numerous attributes per instance

Which information is required for which concerns? A Pattern-based Approach to Enterprise Architecture Management

© sebis

4

Software Cartography provides a visual language to communicate an enterprise architecture Business Areas

Multiple viewpoints  Shared problem-specific map types (base maps)  Rule-based layout of visual elements  Hide / show details based on layers

Giro

25%

25%

Construction Financing

Support Credit

10%

30% 30%

10%

40%

30% 8% 10%

BoSha System

30%

30%

Customer Relationship Management

Back Office HR

Document 30%

20%

10% 40%

30%

50% 70%

50%

FI System

HR System

DMS

30% 8% 10%

52% 52%

20%

Cash4 Cashier

30% 20% 30%

30%

Customer DB

30% 20%

30%

30%

CRM System 30% 8% 10%

52%

Clearing

Business Administration FI/CO

30% 20%

Credit4 Banker

banking. myBank. com

20%

Settlement

Customer Management Branch

30%

Clearing&Settlement

30%

30% 20%

Credit System

10% 40%

www. myBank. com

brokerage. myBank. com

20%

20% 30%

52% 70%

ConFi System

Access Channels Internet

Bonds&Shares

8%

30%

30%

10% 40%

Giro System

20%

30% 20%

CO System

Data Warehouse 30%

DW System

30%

10% 40%

30% 8% Call Center 10%

50%

52%

CallCenter System

key performance indicators

information flows application systems base map

A Pattern-based Approach to Enterprise Architecture Management

© sebis

5

Introducing EAM in an enterprise is a challenge: Lack of standardized EAM viewpoints Software Engineering: Established viewpoints for recurring and known problems  modularity, deployment, interaction, … Enterprise Architectures: Emerging modeling languages and viewpoints, e.g.  ArchiMate (http://www.archimate.com)  Software Cartography (http://www.systemcartography.info) Many organization-specific viewpoints:  rarely documented  visibility limited to a single organization

Which viewpoints for which concerns & stakeholders? A Pattern-based Approach to Enterprise Architecture Management

© sebis

6

The evolution of an application landscape can be improved by supporting management processes IT-Governance Processes Enterprise Architecture Management IT Architecture Management IT Project Lifecycle Requirements Management

Identify Measure

Define Measure

Plan Measure

Prioritize & Commit

Implement Measure

Deploy & Migrate

Strategy & Goal Management Project Portfolio Management Synchronization Management

Details s. Fischer, F.;structures Matthes, F.; Wittenburg, (2005)  Fischer, F.; Hallermeier, T.; Matthes, F.; Wittenburg, A. (2008) What are successful governance &A. management practices?

A Pattern-based Approach to Enterprise Architecture Management

© sebis

7

The peer knowledge exchange advances EAM             

EUROFORUM, IIR conferences and seminars EAM Tage, act consulting SOA Innovation Lab, Deutsche Post CEISAR, Paris Systemkartographie Stammtisch, sebis IT Management Days, iteratec Cap Gemini sd&m EAM events EAM Think Tank, Syracom Workshop SIG GA DACH Community Meetings PEAM Workshop EAMKON …

How to capture, disseminate and apply this empirical knowledge? A Pattern-based Approach to Enterprise Architecture Management

© sebis

8

Outline 1. Introducing EAM in an enterprise is a challenge • models, viewpoints, management processes 2. The EAM pattern catalog • rationale, contents, contributors • evolution 3. Case studies 4. EAM pattern catalog survey

A Pattern-based Approach to Enterprise Architecture Management

© sebis

9

Enterprise architecture management patterns An enterprise architecture management pattern (EAM pattern) is  a general, reusable solution to a common problem  in a given context  identifies driving forces,  known usages and  consequences. An EAM pattern takes a holistic perspective:  It address concerns at the enterprise (systems of systems) level.  It considers social, technical and economic forces in a balanced manner.  It is discovered in working solutions rather than being invented or hoped for.  It uses a clear, accessible and informal language that allows practitioners to describe their knowledge and experience. Pattern languages are a proven way to capture best practices and expert knowledge and to socialize it inside a group, department, entire company, or entire design discipline. A Pattern-based Approach to Enterprise Architecture Management

© sebis

10

A pattern is a general, reusable solution to a common problem in a given context Analogy to other disciplines: Address recurring problems with patterns. Alexander et al. [Al77] (Architecture)  Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice.  Each pattern is a three-part rule, which expresses a relation between a certain context, a problem and a solution Buschmann et al. [Bu96] (Software Architecture)  A pattern for software architecture describes a particular recurring design problem that arises in specific design contexts, and presents a well-proven generic scheme for its solution. The solution scheme is specified by describing its constituent components, their responsibilities and relationships, and the ways in which they collaborate Gamma et al. [Ga94] (Software Engineering)  Descriptions of communicating objects and classes that are customized to solve a general design problem in a particular context. A Pattern-based Approach to Enterprise Architecture Management

© sebis

11

The idea behind the EAM pattern catalog Tailor the EAM to the specific situation (pains) of the enterprise and follow an incremental strategy based on EAM patterns representing proven practices. Systematically document the dependencies between  individual management concerns, Which concern is relevant for which stakeholder? Concern

 methodology patterns (M-Pattern),

Landscape Planning

Which processes and roles are required to address a concern?

 viewpoint patterns (V-Pattern), and Which viewpoints help stakeholders to collaboratively perform the activities?

 information model patterns (I-Pattern) Which information has to be available to generate a view?

 anti patterns Which solutions have shown not to work in practice?

Concern

Process Support Map Concern

Process Support

Concern

Oversized Information Models

Draw attention to the consequences implied by a pattern (labor, required information, political resistance, …) A Pattern-based Approach to Enterprise Architecture Management

© sebis

12

Overview of the pattern catalog version 1.0  Basis: literature, experience from sebis research projects, structured interviews of 25 enterprise architects  Selection based on relevance and adoption by an extensive online questionnaire  43 concerns, 20 M-Patterns, 53 V-Patterns, and 47 I-Patterns

A Pattern-based Approach to Enterprise Architecture Management

120 EAM Patterns >1400 PDF downloads released February 2008 300+ pages

© sebis

13

Overview of the current online pattern catalog http://eampc-wiki.systemcartography.info 164 EAM Patterns • 34 M-Patterns • 74 V-Patterns • 54 I-Patterns • 2 Anti Patterns • 454 registered users • 50 visitors per day

A Pattern-based Approach to Enterprise Architecture Management

© sebis

14

All patterns are described using the following template: Name

Short and sound name of the pattern.

Short Description

Short summary of the pattern to get a first look at its content.

Example

An example illustrating the problem to be addressed by the pattern.

Context

The situations in which the pattern may apply.

Problem

The problem a pattern addresses, including a discussion about its associated forces. •Only one problem per pattern •Forces: Goals and constraints, which occur in the context

Solution

The fundamental solution principle underlying the pattern

Implementation

Guidelines for implementing the pattern. E.g. the need to introduce a special board

Variants

A brief description of variants or specializations of a pattern.

Known Uses

Examples where the pattern has been used. •Usage in companies •Usage in tools Also Known As: Alternative names for the pattern (if any).

Consequences

The benefits the pattern provides, and any potential liabilities

See Also

References to other patterns solving similar problems, and to patterns that help to refine the pattern under consideration

Credits

Credits to other authors, reviewers and shepherds of the pattern.

Based on [Bu96] A Pattern-based Approach to Enterprise Architecture Management

© sebis

15

Original contributors to the EAM pattern catalog

Deutsche Börse Systems

A Pattern-based Approach to Enterprise Architecture Management

© sebis

16

Using the EAM pattern catalog 1. Develop enterprise-specific EA management processes, governance structures, and information models 2. Evolve and assess existing EA management approaches in the enterprise 3. Specify EA requirements to  select an EAM tool  clarify goals of an EAM approach

4. Conduct scientific research  Evolve and validate individual patterns  Develop domain-specific patterns (financial sector, health care, …)  Analyze relationships between management patterns, maturity models, …

A Pattern-based Approach to Enterprise Architecture Management

© sebis

17

Workshop as part of Software Engineering 2010 Patterns in Enterprise Architecture Management Paderborn, February 22nd - 23rd 2010, http://www.se2010.upb.de/ The workshop addresses  researchers in software engineering and information system  IT managers, enterprise architects, software architects We seek contributions in the following areas (nonexclusive)  Enterprise-wide requirements engineering  Application portfolio management  Business-IT alignment  Service-oriented design of enterprise architectures  Modeling languages for enterprise architectures  Metrics for application landscapes and enterprise architectures  Modeling, simulation and monitoring of enterprise performance  Enterprise Architecture Management in transformation programs (mergers, carve outs)

Program Committee Members (non exhaustive)  Dr. Antonia Albani (Delft University of Technology, Netherlands)  Prof. Dr. Dr. h.c. Hans-Jürgen Appelrath (Universität Oldenburg, Germany)  Prof. Dr. Ulrich Frank (Universität Duisburg Essen, Germany)  Dr. Pontus Johnson (Royal Institute of Technology, Sweden)  Prof. Dr. Dimitris Karagiannis (Universität Wien, Austria)  Wolfgang Keller (objectarchitects, Germany)  Dr. Marc Lankhorst (Novay, Netherlands)  Prof. Dr. Florian Matthes (Technische Universität München, Germany)  Prof. Dr. Erik Proper (Archimate Foundation, Netherlands  Prof. Peter Sommerlad (Hochschule Rapperswil, Switzerland)  Johannes Willkomm (sd&m Research, Germany)  Prof. Dr. Robert Winter (Universität St. Gallen, Switzerland)  Christian Winterhalder (EAM Think Tank)  Dr. Uwe Zdun (TU Wien, Austria)

http://wwwmatthes.in.tum.de/wikis/sebis/peam2010 A Pattern-based Approach to Enterprise Architecture Management

© sebis

18

Outline 1. Introducing EAM in an enterprise is a challenge • models, viewpoints, management processes 2. The EAM pattern catalog • rationale, contents, contributors • evolution 3. Case studies 4. EAM pattern catalog survey

A Pattern-based Approach to Enterprise Architecture Management

© sebis

19

Christiana Care Health Systems: One of the largest health care providers in the US mid-Atlantic region  Usage of the EAM Pattern Catalog • Inspire and assess already existing EAM endeavors • I-Patterns, e.g. PROCESS SUPPORT, were considered in discussions about rebuilding the information model • V-Patterns, e.g. BUSINESS APPLICATION PLANNING, were very important and very valuable • Concerns to steer the EAM approach • EAM patterns were used to document a method and associated templates  Evaluation of the pattern-based approach to EAM • EAM tool did not support the required queries • Graphical navigation between EAM patterns would be helpful • Convince stakeholders, as EAM patterns were recognized as proven practice • EAM patterns allowed to focus on work than creating structure

A Pattern-based Approach to Enterprise Architecture Management

© sebis

20

Insurance Company: One of the largest primary insurers of Germany with over 6 million customers Investigate former Approach  Usage of the EAM Pattern Catalog • Establish an EAM approach Apply the EAMPC • Specify the requirements for an EAM tool • Iterative process for integrating I-Patterns Extend the EAMPC  Evaluation of the pattern-based approach to EAM Integrate I-Patterns • Large number of EAM patterns can still be managed and integrated Map Information Models • Included glossary is helpful for understanding EAM patterns and to define a common vocabulary • EAM pattern map is useful for identifying patterns and related patterns • List of concerns as a valuable starting point • EAM patterns allow for rapid prototyping • EAM Pattern Catalog is sufficient to establish an EAM approach

A Pattern-based Approach to Enterprise Architecture Management

© sebis

21

Using patterns: Constructing EAM information models based on I-Patterns

A Pattern-based Approach to Enterprise Architecture Management

© sebis

22

Outline 1. Introducing EAM in an enterprise is a challenge • models, viewpoints, management processes 2. The EAM pattern catalog • rationale, contents, contributors • Evolution 3. Case studies 4. EAM pattern catalog survey

A Pattern-based Approach to Enterprise Architecture Management

© sebis

23

EAM Pattern Catalog online survey  Conducted between 2009-05-11 and 2009-05-31 • 20 day response period  72 participants • from 15 countries • belonging to various industries • 15% response rate  20 questions in 3 sections  Goals • Evaluating the EAM Pattern Catalog • Comparing the EAM Pattern Catalog to other EAM approaches • Identify potential for improvement

A Pattern-based Approach to Enterprise Architecture Management

© sebis

24

How useful are the following approaches for identifying and supporting stakeholders?

2

2

2

3

3

DoDAF

NAF

TEAF

EAM Books

EAM Pattern Catalog

A Pattern-based Approach to Enterprise Architecture Management

3

3

4

Reference Zachman TOGAF Models Framework

© sebis

25

How useful are the following approaches for identifying and organizing concerns?

2

2

2

3

3

3

3

4

DoDAF

NAF

TEAF

EAM Books

Reference Models

TOGAF

Zachman Framework

EAM Pattern Catalog

A Pattern-based Approach to Enterprise Architecture Management

© sebis

26

How useful are the following approaches for establishing governance structures?

2

2

2

2

2

3

3

3

DoDAF

NAF

Reference Models

TEAF

Zachman Framework

EAM Books

EAM Pattern Catalog

TOGAF

A Pattern-based Approach to Enterprise Architecture Management

© sebis

27

How useful are the following approaches for defining a holistic and integrated process for EAM?

2

2

2

2

2

3

3

4

DoDAF

NAF

Reference Models

TEAF

Zachman Framework

EAM Books

EAM Pattern Catalog

TOGAF

A Pattern-based Approach to Enterprise Architecture Management

© sebis

28

How useful are the following approaches for identifying visualizations for your EAM approach?

2

2

2

2

DoDAF

NAF

TEAF

TOGAF

A Pattern-based Approach to Enterprise Architecture Management

2

2,5

Zachman Reference Framework Models

3

4

EAM Books

EAM Pattern Catalog © sebis

29

How useful are the following approaches for defining an information model for EAM?

2

2

2

2

3

3

3

3

DoDAF

NAF

TEAF

Zachman Framework

EAM Books

EAM Pattern Catalog

Reference Models

TOGAF

A Pattern-based Approach to Enterprise Architecture Management

© sebis

30

What topics in EAM are you most interested in? Application Landscape Management

38

Business Processes Support Management

30

Interface, Business Object, and Service Management

26

Standardization and Technology Homogeneity Management

20

Project Portfolio Management

20

Metrics

16

Infrastructure Management

14

IT support of business strategy

2

EA modeling

2

A Pattern-based Approach to Enterprise Architecture Management

© sebis

31

How are you using the EAM Pattern Catalog? as a reference book, e.g. for finding new visualizations

31

to inspire and assess an existing EAM approach

20

to specify goals and requirements for EAM

12

to develop a new EAM approach

12

for my academic research

11

to organize and classify problems in EAM

10

to document the currently used EAM approach

A Pattern-based Approach to Enterprise Architecture Management

9

© sebis

32

Which of the following EA frameworks are you using in conjunction with EAM Patterns? TOGAF

26

None

9

Zachman Framework

5

Other (ArchiMate)

3

Other (NORA) 1

Other (ARIS Value Engineering) 1 Other (ABACUS) 1 NAF 1

DoDAF 1

A Pattern-based Approach to Enterprise Architecture Management

© sebis

33

Some final remarks by EAM Pattern Catalog survey participants It groups things usefully and is good for quick lookups. Thanks for your efforts so far!

Overall, I want to thank you for taking this huge step in identifying and documenting these EAM patterns. The EAM Pattern Catalog is indeed a very useful resource and can some day become as well respected and recognized as GoF patterns. As future considerations, I would like to see some enabling tools (e.g. Microsoft Visio stencils for IPatterns) as well as a comprehensive meta-model. I would imagine that the M-Patterns will be refined over time to be more prescriptive and complete. Also, some direct support to SOA will be useful. A Pattern-based Approach to Enterprise Architecture Management

Being relatively new to this discipline I have found the approach in the EAM Pattern Catalog enables quick dives as well as relating concern through approach to deliverable. However, the structure of the catalog is such that it’s not always obvious where the M-Patterns (and the supporting I- and VPatterns) might fit into an overall approach.

© sebis

34

Summary  Developing and maintaining an EAM approach is a difficult task  EAM is advanced by experienced practitioners in large organizations  EAM patterns are a promising approach to capture, disseminate and apply EAM knowledge  EAM patterns have been successfully applied in academia and practice  The EAM pattern language helps to improve the communication • within an enterprise • within an industry • between industry and academia • between academic disciplines (engineering & management sciences)

A Pattern-based Approach to Enterprise Architecture Management

© sebis

35

Thank you for your attention!

More information  System Cartography: http://www.systemcartography.info  EAM Pattern Catalog Wiki: http://eampc-wiki.systemcartography.info A Pattern-based Approach to Enterprise Architecture Management

© sebis

36

Bibliography [Al77]

Alexander, C.; Ishikawa, S.; Silverstein, M.: A Pattern Language: Towns, Buildings, Construction. Oxford University Press, USA, 1977. [Bu08] Buckl, S.; Ernst, A.; Lankes, J.; Matthes, F.: Enterprise Architecture Management Pattern Catalog (Version 1.0, February 2008) . Technical Report TB 0801, Chair for Informatics 19, Technische Universität München, 2008. [Er09] Ernst, A.: A Pattern-based Approach to Enterprise Architecture Management. Ph.D. thesis, Fakultät für Informatik, Technische Universität München, 2009. (in publication) [Bu96] Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, and Michael Stal. Pattern-oriented software architecture: a system of patterns. John Wiley & Sons, Inc., New York, NY, USA, 1996. [Ga94] Gamma, E.; Helm, R.; Johnson, R.; Vlissides, J. M.: Design Patterns: Elements of Reusable Object-Oriented Software (Addison-Wesley Professional Computing Series). Addison-Wesley Professional, 1994. [se09] Technische Universität München, Chair for Informatics 19 (sebis). EAM Pattern Catalog Wiki. http://eampc-wiki.systemcartography.info (cited 2009-05-01), 2009. A Pattern-based Approach to Enterprise Architecture Management

© sebis

37