enterprise architecture management tool survey ...enterprise architecture management tool survey...

Fakultät für Informatik Technische Universität München

Enterprise Architecture Management Tool Survey 2008Management Tool Survey 2008Iteratec IT-Management Workshop 8.10.2008

Florian MatthesSoftware Engineering for Business Information Systems (sebis)

081008-MatthesEAMTS2008--Iteratec Workshop © sebis

Software Engineering for Business Information Systems (sebis)wwwmatthes.in.tum.de

1

Agenda

Background & partnersOverview of main resultsTrends compared with 2005Outlook and research topics

© sebis081008-MatthesEAMTS2008--Iteratec Workshop 2

The application landscape is a key asset of the enterprise. Its evolution has to be managed

IT-Governance Processes

E t i A hit t M t

[Wi07]

Enterprise Architecture Management

IT Architecture Management

IT Project Lifecycle

DefineMeasure

Plan Measure

Prioritize& Commit

Implement Measure

Deploy& Migrate

Requirements Management

IdentifyMeasure

Strategy & Goal Management

Measure Measure & Commit Measure & MigrateManagement Measure

S h i ti M t

Project Portfolio Management

gy g

Synchronization Management

centralized ↔ decentralized top-down ↔ bottom-up core ↔ periphery


centralized ↔ decentralized top-down ↔ bottom-up core ↔ periphery ….

A holistic model of an application landscape

Layers and crosscutting functionsRelationships are more important than element detailshas consists of depends on uses controls owns produces consumeshas, consists of, depends on, uses, controls, owns, produces, consumes,…

B i L

Geschäfts-Service-Schicht

Business Layer

Pro

ject

s

bjec

tives

rics

atte

rns

Business Service Layer

Application & Information Layer

men

ts &

ies

& O

b

Is &

Met

rints

& P

a

Infrastruktur-Service-Schicht

Infrastructure LayerReq

uire

Stra

teg

KP

Blu

epr

Infrastructure Service Layer

Infrastructure Layer


Sponsors and partners of EAMTS2008

Main Sponsors

Co-Sponsors

Partners


Contributions by the sponsors and partners

Participation in study design workshops• Functional evaluation criteria• Scenarios for process evaluation

Online questionnaire• “Interesting” / “relevant” EAM toolsg

Participation (Q&A) in tool presentations


Tools sorted by interest of partnersRank compared with 2005

Vendor Toolalfabet AG planningITIDS Scheer ARIS IT ArchitectTelelogic System ArchitectTroux Technologies Metis Architect, Metis Server, Metis Collection

* IDS Scheer ARIS ArchiMate Modeler* Hewlett Packard Mercury Project and Portfolio Management Center

Casewise Corporate Modeler Suite, IT Architecture Accelerator* IBM Rational Soft are Architect

Short List* IBM Rational Software Architect

MEGA International MEGA Modeling SuiteBOC ADOit/ADOxxAdaptive Adaptive EAM Proforma ProVision Modeling SuiteProforma ProVision Modeling Suite Embarcadero EA/StudioBEA AquaLogic Enterprise RepositoryCA ClarityComma Soft infoneaAgilense EA WebModelerQualiWare EAM SuitePrimavera ProSightprocess4.biz process4.biz Avolution ABACUSAvolution ABACUSSparx Systems Enterprise ArchitectASG ASG Enterprise Management/Rochadepulinco TopEase SuiteVisible Systems Corporation Visible Enterprise Products

* Tool excluded from evaluation

Visible Systems Corporation Visible Enterprise Products… …


Overview on the evaluation process and its criteria

9 Tools are evaluated by 3 teams

Functional CriteriaOnline questionnaire for every vendorSimulation of functional scenarios with every toolDocumentation of the functional aspects and the

EA Management Task CriteriaSimulation of typical EA Management tasks with every toolOne scenario per EA Management taskDocumentation of the functional aspects and the

evaluation results in simulationOne scenario per EA Management task

Documentation of the evaluation results in simulation

Final evaluation based on the results documentedEach evaluation criterion is assigned an ordering of tools reflecting their specific support

9 Spider diagrams eachwith 8 specificfunctionalitites

8 Spider diagramseach with 9 EAmanagement tasksmanagement tasks


Online questionnaire EAMTS2008

Categories• Vendor data• Tool data• General tool architecture• Collaboration supportpp• Internationalization / Localization• Integration with related domains

M th d l• Methodology• Integration with other modeling tools


EAMTS2008 Scenarios

Scenarios for Analyzing Specific Functionalities

Importing Editing and Validating Model

Scenarios for Analyzing EA Management Support

Landscape Management• Importing, Editing, and Validating Model Data

• Creating Visualizations of the Application Landscape

• Landscape Management• Demand Management• Project Portfolio Management

S h i ti M tApplication Landscape• Interacting with and Editing of

Visualizations of the Application Landscape

• Synchronization Management• Strategies and Goals Management• Business Object Management

• Annotating Visualizations with Certain Aspects

• Supporting light weight Access

• SOA Transformation• IT Architecture Management• Infrastructure Management

• Editing Model Data using an external Editor

• Adapting the Information Model• Handling large scale Application

Landscapes• Supporting multiple Users and

ll b ti W kcollaborative Work


Scenario: Landscape Management

Concerns of this scenarioInformation about the application landscape should be stored in the tool. Starting with the pp p ginformation about the current landscape, potential development variants should be modeled. The information about the current application landscape and future states should be historicized in the tool to enable comparisons.Chosen versions of the application landscape, e. g. current, planned, and target landscapes should be analyzed and compared using different visualizations and reports.

Major changes (since 2005)In-depth analysis of versioning and support for previous version statesAnalysis of deduction of a planned landscape from an existing project portfolio

© sebis 11081008-MatthesEAMTS2008--Iteratec Workshop

Scenario: Landscape ManagementCurrent, Planned, and Target Landscapes


What is SoCaStore?

Simulation is based on a fictitious department store, called SoCaStore.Information model of SoCaStore consists of

• Business Processes• Organizational Units• Application Systemspp y• Domains• Projects• ….

Information objects are maintained in an Excel sheet


SoCaStore: A Set of reference data for evaluating EA management tools

SoCaStore Model SoCaStore Metamodel Utilities

Generated data for „handling large scale application

landscapes“

…Microsoft Excel Files UML / Ecore 3 different sizesMicrosoft Excel Files

totalca. 200 instances,

UML / Ecore

ca. 25 classes,

3 different sizes

total,ca. 700 links (using

foreign keys)

,ca. 30 associations,

ca. 90 attributesca.1000/5000/10000 instances

with eachca. 70 attribute values

and ca. 15 links


Analyzing specific functionalities –Minimum and maximum achieved results

Importing, Editing, and Validating

4

5

6

7

Creating VisualizationsUsability

1

2

3

4

Interacting with Editing0

1 Interacting with, Editing of, and Annotating

Visualizations

Impact Analysis and Reporting

Flexibility of the f

Support of large scale Information Model

Communication and C ll b ti S t

Data

Collaboration Support


Analyzing specific functionalities –details of the evaluation results

Communication und Collaboration SupportWell supported with interesting features for collaboration,

kfl d tifi ti h i4

5

6

7

Importing, Editing, and Validating

Creating VisualizationsUsability

e.g. workflows and notification mechanismsCreating Visualizations

Different approaches to visualizing the EA or parts0

1

2

3

Interacting with, Editing of, and Annotating

Visualizations

Impact Analysis and Reporting

thereof - retaining potential for improvement• (Semi)-Automatic generation of visualizations still has

its limitations

Flexibility of the Information Model

Communication and Collaboration Support

Support of large scale Data

• Flexible models without predefined semantics are not supported out-of-the-box and mostly have to be created manually

Interacting with Editing of and Annotating VisualizationsInteracting with, Editing of, and Annotating VisualizationsInteraction is mostly „drawing“ – semantic changes could provide an improvement towards graphical modeling

Importing Editing and ValidatingImporting, Editing, and ValidatingNo standard exchange format for EA modelsNo common information model or core concepts thereof exist


Analyzing EA management support –minimum and maximum achieved results

6

7Landscape Management

4

5

6Demand ManagementInfrastructure Management

1

2

3

Project Portfolio ManagementIT Architecture Management

0

Synchronization ManagementSOA Transformation

Strategies and Goals ManagementBusiness Object Management


Analyzing EA management support –details of the evaluation results

Landscape ManagementDifferent levels of support for the concept of time

3

4

5

6

7Landscape Management

Demand ManagementInfrastructure Management

Versioning application landscapes retainspotential for improvementNot all tools provide methods for deriving the

0

1

2

Project Portfolio ManagementIT Architecture Management

planned landscape from the plannedproject portfolio



Strategies and Goals ManagementBusiness Object Management

SOA Transformation

y gNo tool directly supports the concept of project delay

SOA Transformation ManagementTool support for indentifying services retains potential for improvementTool support for indentifying services retains potential for improvement

Infrastructure ManagementNot all tools provide concepts for lifecycle aspects of infrastructure components


Approaches of EA management tools

Flexibility vs. Guidance regarding process, method, and information model for supporting EA management

M t d l d i h ll th t f l fi th i f ti• Metamodel driven approach – allows the user to freely configure the information model complemented with generic visualization types, analyzes, and reports, which can be adapted flexiblyM th d l d i h id d fi d i f ti d l ith• Methodology driven approach – provides a predefined information model with specially designed visualization types and analyzes, allowing the user to choose when to use which of them

• Process driven approach – complements the predefined information model, visualization types, and analyzes with a process guiding the user through an EA management endeavor

Preconfigured vs. Customization regarding the functionality provided by the tool out of the box – two approaches exist: EA management solution vs. EA management platformIntegration vs. Single-Point-of-Truth regarding the information base of the tool, which in the one approach is collected from a variety of sources, while in the other approach being under data sovereignty of the tool itself


EAM tools and repositories in 2008

Focus on entities, relationships and attributesBasic principles of software cartography adopted by

j lmajor playersLimited versioning capabilitiesSignificant differences in the approachesto managing model histories (revisions)Collaboration support has been enhanced significantly

• triggering & notificationtriggering & notification• web-based access (read & write)• customizable workflows

[Ma08]


Related research topics and industry cooperation

Improved EA knowledge representation (Hybrid Wiki)

Tailored EA models, views and methodologies (EAM Patterns)

Commons-based model peer-production (Content Factory)p p ( y)

More information: www.systemcartography.info


enterprise architecture management tool survey ...enterprise architecture management tool survey...

Documents