Patterns in Enterprise Architecture Management

Similar documents
Enterprise Architecture

Enterprise Architecture Management Pattern Catalog

Maturity Assessments of Service- oriented Enterprise Architectures with Iterative Pattern Refinement

Optimizing the User Experience of a Social Content Management Software for Casual Users

ArchiMate and TOGAF. What is the added value?

Setting up an Effective Enterprise Architecture capability. Simon Townson Principal Enterprise Architect SAP

Structuring software cities a multidimensional approach

Modelling, Analysing and Improving an ERP Architecture with ArchiMate

Enterprise Architecture Management Patterns


Chap 1. Introduction to Software Architecture

DEPARTMENT OF INFORMATICS. Scenario-based Analysis of Collaborative Enterprise Architecture Management Tools

An Integrated Quality Assurance Framework for Specifying Business Information Systems

Integration Strategies and Patterns for SOA and Standard Platforms

Trends for Enterprise Architecture Management and Tools

Leveraging Standard Software from the Cloud with Service-Oriented EAM

Building Business Capabilities

A guide for enterprise-specific design of EA models

From Capability-Based Planning to Competitive Advantage Assembling Your Business Transformation Value Network

Enterprise Architecture Management Tool Survey 2008

Using the lean startup method for an internet broker in the recycling industry

Managing the Services Lifecycle SOA & BPM

Business Process simulation with the cloud-based Massive Multi-Agent System MARS

Enterprise Architecture Management Tool Survey 2005

Business Architecture Scenarios

How to bridge the gap between business, IT and networks

Open Group SOA Governance. San Diego 2009

Unifying IT Vision Through Enterprise Architecture

Enterprise Architecture: A Governance Framework

Research Topics in Software Engineering

INTEGRATED SERVICE ARCHITECTURE FRAMEWORK (ISAF) FOR ITIL V3

Towards Automation of Enterprise Architecture Model Maintenance

Improved SOA Portfolio Management with Enterprise Architecture and webmethods

Job Description. Job Title Branch Business Group Reporting to Location. Purpose. Key Tasks

Enterprise Architecture Management Patterns. Alexander M. Ernst Chair for Informatics 19 Technische Universität München

9 Research Questions Resolved

"Pr-T1-70.data" "Pr-T2-70.data" "Pr-T3-70.data" "Pr-T4-70.data" "Pr-T5-70.data"

Service-Oriented Architecture Maturity Self-Assessment Report. by Hewlett-Packard Company. Developed for Shrinivas Yawalkar Yawalkar of CTS

Enterprise Architecture at Work

Building a strong data management capability with TOGAF and ArchiMate. Bas van Gils b.vangils@bizzdesign.com

Patterns in a Nutshell

Sparx Enterprise Architect for Business Analysts

L Impatto della SOA sulle competenze e l organizzazione ICT di Fornitori e Clienti

see >analyze >control >align < WhitePaper > planningit: alfabet s Logical IT Inventory

Developing Business Architecture with TOGAF

Enterprise Architecture Roles in Delivering Business Capabilities

Service Oriented Architecture and the DBA Kathy Komer Aetna Inc. New England DB2 Users Group. Tuesday June 12 1:00-2:15

Enterprise Architect for an Enterprise Architecture

Service Oriented Architecture (SOA) Architecture, Governance, Standards and Technologies

Master data deployment and management in a global ERP implementation

Sebis Study: Cloud Adoption and Strategy 2013

Patterns of Evolution in Enterprise Architecture Information Models

Increasing Development Knowledge with EPFC

Practice Description Business process management and enterprise architecture

Role of Enterprise Architecture in Mergers & Acquisitions. Satish Chandra, Mahindra Satyam

CRITICAL SUCCESS FACTORS FOR A SUCCESSFUL TEST ENVIRONMENT MANAGEMENT

secure intelligence collection and assessment system Your business technologists. Powering progress

FRAUNHOFER INSTITUTE FOR EXPERIMENTAL SOFTWARE ENGINEERING IESE VARIATION MANAGEMENT: USER EXPERIENCE FOR EFFICIENCY IN PROVIDING SOLUTIONS

Realizing business flexibility through integrated SOA policy management.

A Case Study on Model-Driven and Conventional Software Development: The Palladio Editor

Agenda. Seda Overview Seda EA Project Requirements Enterprise Architecture Approach

Session-1: Business Enterprise Applications- Overview

SOA Adoption Challenges

A Variability Viewpoint for Enterprise Software Systems

Business Intelligence in Oracle Fusion Applications

Sparx Systems Enterprise Architect for Team Players

Enterprise Architecture for Communication Service Providers: Aligning Business Goals to IT

Mapping Service-Orientation to TOGAF 9 - Part II: Architecture Adoption, Service Inventories and Hierarchies

Agile Change: The Key to Successful Cloud/SaaS Deployment

Design the Future of Your Human Resources with SuccessFactors Solutions

How service-oriented architecture (SOA) impacts your IT infrastructure

Microsoft SOA Roadmap

10. Service Oriented Architecture Reference Architectures and Patterns

Enterprise Information Management

A Process View on Architecture-Based Software Development

Visualizing the Business Impact of Technical Cyber Risks

SaaS Maturity Evolution for Transforming ISVs business

Introducing SOA Governance Suite. Magnus Wettemark, Solution Consultant Manager Software AG

Adapting an Enterprise Architecture for Business Intelligence

Automating the IT Operations to Business Connection

Data Mining Governance for Service Oriented Architecture

DOCUMENTOS DE TRABAJO Serie Gestión

Enterprise Portfolio Management

RE4ES: Support Environmental Sustainability by Requirements Engineering

Applying 4+1 View Architecture with UML 2. White Paper

SOA + BPM = Agile Integrated Tax Systems. Hemant Sharma CTO, State and Local Government

Service Development and Architecture Management for an Enterprise SOA

CHAPTER 4: PATTERNS AND STYLES IN SOFTWARE ARCHITECTURE

Continue the Discussion: Ask questions at: Learn More: To learn more about BPM BlueWorks, please visit:

Establishing EA teams

The new ASAP Methodology

Encapsulating Crosscutting Concerns in System Software

Project, Program & Portfolio Management Help Leading Firms Deliver Value

Enterprise Architecture 101. (Includes numerous samples/ templates produced using TOGAF methodology) Shail Sood

Data Center is the Foundation of Carrier ICT Transformation. The challenges of building a service driven data center

White Paper What Solutions Architects Should Know About The TOGAF ADM

How To Be An Architect

Service Oriented Architecture. 9. Integration Darmstadt University of Applied Sciences, Department of Computer Science Dr. Markus Voß (Accso GmbH)

Architectural Patterns (3)

Transcription:

Fakultät für Informatik Technische Universität München Patterns in Enterprise Architecture Management SI-SE Fachtagung, Zürich, 30.1.2009 Prof. Florian Matthes, Alexander Ernst Software Engineering for Business Information Systems (sebis) wwwmatthes.in.tum.de 090130-Matthes-Patterns in Enterprse Architecture Management sebis 1

Areas of research Managed Evolution of Socio-Technical Systems of Systems (EAM) Social Software Users Contexts Content Transfer Projects Domain-Driven Software Architectures 090130-Matthes-Patterns in Enterprse Architecture Management sebis 2

Outline 1. Introducing EAM in an enterprise is a challenge models, viewpoints, management processes 2. The EAM pattern catalog 1.0 rationale, contents, contributors 3. Towards an EAM pattern community 090130-Matthes-Patterns in Enterprse Architecture Management sebis 3

Introducing EAM in an enterprise is a challenge: EA frameworks provide only limited support TOGAF 9 2008? 090130-Matthes-Patterns in Enterprse Architecture Management sebis 4

Application landscape management requires a holistic view Strategies & Objectives Requirements & Projects Blueprints & Patterns KPIs & Metrics 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, Enterprise Architecture Business Layer Geschäfts-Service-Schicht Business Layer Application & Information Layer Infrastruktur-Service-Schicht Infrastructure Layer Infrastructure Layer Where to start? Which level of detail? Best practices? 090130-Matthes-Patterns in Enterprse Architecture Management sebis 5

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 090130-Matthes-Patterns in Enterprse Architecture Management sebis 6

Software Cartography provides a visual language to communicate an enterprise architecture 25% 25% 40% 30% 10% 30% 8% 10% 52% 30% 20% 50% 10% 30% 40% 70% 10% 40% 30% 8% 10% 52% 30% 8% 10% 52% 30% 30% 8% 52% 10% 50% 20% 30% 30% 20% 20% 30% 30% 20% 70% 30% 20% 30% 30% 20% 20% 30% 30% 30% 10% 20% 10% 40% 30% 40% 30% 8% 10% 52% 50% Multiple viewpoints Shared problem-specific map types (base maps) Rule-based layout of visual elements Hide / show details based on layers Business Areas Support Giro Construction Financing Credit Bonds&Shares Giro System Internet www. mybank. com banking. mybank. com brokerage. mybank. com ConFi System Credit System Clearing&Settlement Settlement Clearing Access Channels Customer Management Business Administration Back Office Branch 30% 30% Credit4 Banker Cash4 Cashier Call Center CallCenter System BoSha System Customer Relationship FI/CO HR Document Management CRM System Customer DB 30% 20% FI System CO System HR System Data Warehouse DW System 30% 30% DMS 30% 20% key performance indicators information flows application systems base map Which viewpoints for which concerns & stakeholders? 090130-Matthes-Patterns in Enterprse Architecture Management sebis 7

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 090130-Matthes-Patterns in Enterprse Architecture Management sebis 8

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 What are successful governance structures & management practices? Details s. Fischer, F.; Matthes, F.; Wittenburg, A. (2005) Fischer, F.; Hallermeier, T.; Matthes, F.; Wittenburg, A. (2008) 090130-Matthes-Patterns in Enterprse Architecture Management sebis 9

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 How to capture, disseminate and apply this empirical knowledge? 090130-Matthes-Patterns in Enterprse Architecture Management sebis 10

Outline 1. Introducing EAM in an enterprise is a challenge models, viewpoints, management processes 2. The EAM pattern catalog 1.0 rationale, contents, contributors 3. Towards an EAM pattern community 090130-Matthes-Patterns in Enterprse Architecture Management sebis 11

A Patterns 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. 090130-Matthes-Patterns in Enterprse Architecture Management sebis 12

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. 090130-Matthes-Patterns in Enterprse Architecture Management sebis 13

The idea behind the EAM pattern catalog 1.0 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? Methodology patterns (M-Pattern), Which activities 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? Draw attention to the consequences implied by a pattern (labor, required information, political resistance, ) 090130-Matthes-Patterns in Enterprse Architecture Management sebis 14

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 090130-Matthes-Patterns in Enterprse Architecture Management sebis 15

Using patterns: Constructing EAM information models based on I-Patterns I-Pattern as manageable, concern-specific units, which can be composed to an integrated information model. I-63 I-82 090130-Matthes-Patterns in Enterprse Architecture Management sebis 16

Information model with highlighted I-Patterns 081119-Pflügler-Final 090130-Matthes-Patterns Presentation in Enterprse Bachelor s Architecture Thesis Management sebis 17

Contributors to the EAM pattern catalog 1.0 Deutsche Börse Systems 090130-Matthes-Patterns in Enterprse Architecture Management sebis 18

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, 090130-Matthes-Patterns in Enterprse Architecture Management sebis 19

Outline 1. Introducing EAM in an enterprise is a challenge models, viewpoints, management processes 2. The EAM pattern catalog 1.0 rationale, contents, contributors 3. Towards an EAM pattern community 090130-Matthes-Patterns in Enterprse Architecture Management sebis 20

From a pattern catalog towards a pattern language Make EAM patterns more self-contained Each EAM pattern (M-Pattern, V-Pattern, and I-Pattern) addresses a specific problem affected by its forces Restructure EAM patterns Pattern description similar to Buschmann et al. [Bu96] Enrich existing EAM patterns Example, implementation, usage, extended solution, Develop new EAM patterns in cooperation with practitioners and academia See [Er08] for these changes and further development. [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. [Er08] Ernst, A.: Enterprise Architecture Management Patterns. Pattern Languages of Programs Conference 2008 (PLoP08), Nashville, 2008. (in publication) 090130-Matthes-Patterns in Enterprse Architecture Management sebis 21

EAM pattern catalog wiki http://www.systemcartography.info/eampc-wiki 090130-Matthes-Patterns in Enterprse Architecture Management sebis 22

Example M-Pattern Standard Conformity Management 090130-Matthes-Patterns in Enterprse Architecture Management sebis 23

Example V-Pattern Standard Conformity Exceptions 090130-Matthes-Patterns in Enterprse Architecture Management sebis 24

Example I-Pattern Architectural Solution Conformance 090130-Matthes-Patterns in Enterprse Architecture Management sebis 25

Workshop as part of Software Engineering 2009 Patterns in Enterprise Architecture Management Kaiserslautern, March 2-6 2009, http://www.se2009.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) specific EAM patterns derived from case studies and research projects EAM patterns on a metamodel level and model level organization of pattern catalogs usage of EAM patterns in industry or in education empirical studies about pattern adoption Program Committee Members Prof. Dr. Dr. h.c. Hans-Jürgen Appelrath (Universität Oldenburg, Germany) Prof. Dr. Gregor Engels (Universität Paderborn, Germany) Prof. Dr. Ulrich Frank (Universität Duisburg Essen, Germany) Dr. Pontus Johnson (KTH Stockholm, Sweden) Prof. Dr. Dimitris Karagiannis (Universität Wien, Austria) Wolfgang Keller (objectarchitects, Germany) Dr. Marc Lankhorst (Telematica Instituut, Netherlands) Prof. Dr. Florian Matthes (Technische Universität München, Germany) Prof. Dr. Ralph Reussner (Universität Karlsruhe, Germany) Dr. Michael Rohloff (Universität Potsdam, Germany) Prof. Peter Sommerlad (Hochschule für Technik Rapperswil, Switzerland) Dr. Ulrike Steffens (OFFIS, Oldenburg) Johannes Willkomm (Capgemini sd&m Research, Germany) Prof. Dr. Robert Winter (Universität St. Gallen, Switzerland) http://wwwmatthes.in.tum.de/wikis/sebis/peam-2009 090130-Matthes-Patterns in Enterprse Architecture Management sebis 26

Summary EAM is advanced by experienced practitioners in large organizations. EAM patterns are a promising approach to capture, disseminate and apply EAM knowledge. An EAM pattern language might help to improve the communication within an enterprise within an industry between industry and academia between academic disciplines (engineering & management sciences) 090130-Matthes-Patterns in Enterprse Architecture Management sebis 27

Thank you for your attention! More information: www.systemcartography.info 090130-Matthes-Patterns in Enterprse Architecture Management sebis 28