Fakultät für Informatik Technische Universität München
Enterprise architecture management tools
1
Sabine Buckl
Software Engineering betrieblicher Informationssysteme (sebis) wwwmatthes.in.tum.de
© sebis Enterprise Architecture Management Tools
Learning objectives of this unit
Knowing what requirements for an EA management tool exist from a practitioners point of view
Understanding how different EA management tools can be evaluated Being capable of detailing on the different approaches and origins of EA
management tools Obtaining a general idea of how a generic approach to select an EA
management tool looks like
© sebis Enterprise Architecture Management Tools 2
Outline of this unit
The Enterprise Architecture Management Tool Survey 2008 • Questionnaire • Scenarios • Results
What happened since the survey Approaches of the tools A wiki-based approach to EA management Selecting an EA management tool
© sebis Enterprise Architecture Management Tools 3
Tools for EA management – The Enterprise Architecture Management Tool Survey (EAMTS)
Several tools with different originations, different approaches, different goals and different strengths and weaknesses
Adaptive, Ltd.: Adaptive EAM
Agilense, Inc.: EA WebModeler
alfabet AG: planningIT
ASG, Inc.: ASG Enterprise Management/Rochade
BEA AquaLogic: Enterprise Repository
BiZZdesign: BiZZdesign Architect, BiZZdesigner
BOC GmbH: ADOit/ADOxx
Casewise Ltd.: Corporate Modeler Suite, IT Architecture Accelerator
Embarcadero: EA/Studio
Future Tech Systems Inc.: ENVISION VIP
Hewlett Packard: Mercury Project and Portfolio Management Center
IBM: Rational Software Architect
IDS Scheer AG: ARIS Toolset
MEGA International SA: MEGA Modeling Suite
Primavera: ProSight
process4.biz: process4.biz
Proforma Corp.: ProVision Modeling Suite
pulinco: TopEase Suite
Telelogic AB: System Architect
Troux Technologies, Inc: Metis Architect, Metis Server, Metis Collection
…
© sebis 4 Enterprise Architecture Management Tools
[Ma08]
Partners and sponsors of the EAMTS2008
Users
Consultants
© sebis 5 Enterprise Architecture Management Tools
* Tool unaccounted for evaluation
Tools sorted based on interest of sponsors & partners
Vendor Tool alfabet AG planningIT IDS Scheer ARIS IT Architect Telelogic System Architect Troux 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 Software Architect
MEGA International MEGA Modeling Suite BOC ADOit/ADOxx Adaptive Adaptive EAM Proforma ProVision Modeling Suite Embarcadero EA/Studio BEA AquaLogic Enterprise Repository CA Clarity Comma Soft infonea Agilense EA WebModeler QualiWare EAM Suite Primavera ProSight process4.biz process4.biz Avolution ABACUS Sparx Systems Enterprise Architect ASG ASG Enterprise Management/Rochade pulinco TopEase Suite Visible Systems Corporation Visible Enterprise Products
… …
© sebis 6
Short List
Enterprise Architecture Management Tools
Outline of this unit
The Enterprise Architecture Management Tool Survey 2008 • Questionnaire • Scenarios • Results
What happened since the survey Approaches of the tools A wiki-based approach to EA management Selecting an EA management tool
© sebis Enterprise Architecture Management Tools 7
Online questionnaire EAMTS2008
Categories • Vendor data • Tool data • General tool architecture • Collaboration support • Internationalization / Localization • Integration with related domains • Methodology • Integration with other modeling tools
© sebis 8 Enterprise Architecture Management Tools
EAMTS2008 scenarios
Scenarios for Analyzing Specific Functionalities
• Importing, Editing, and Validating Model Data
• Creating Visualizations of the Application Landscape
• Interacting with and Editing of Visualizations of the Application Landscape
• Annotating Visualizations with Certain Aspects
• Supporting light weight Access • Editing Model Data using an
external Editor • Adapting the Information Model • Handling large scale Application
Landscapes • Supporting multiple Users and
collaborative Work
Scenarios for Analyzing EA Management Support
• Landscape Management • Demand Management • Project Portfolio Management • Synchronization Management • Strategies and Goals Management • Business Object Management • SOA Transformation • IT Architecture Management • Infrastructure Management
© sebis 9 Enterprise Architecture Management Tools
Scenario: Creating visualizations of the application landscape
Concerns of this scenario The department store SoCaStore wants to get an overview of its application
landscape and its EA. This should be accomplished by the creation of six different visualizations for different aspects of the application landscape: a cluster map, a process support map, a time interval map, and a graphlayout map as well as a swimlane diagram and a portfolio matrix.
Exemplary Deliverables
© sebis Enterprise Architecture Management Tools 10
Scenario: Landscape management
Concerns of this scenario Information about the application landscape should be stored in the tool. Starting with the
information 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.
Typical questions to be answered What does the current application landscape look like today? What is, according to the plan of 01-01-2009, the application landscape going to look like
in January 2010? What does the target landscape look like? …
© sebis 11 Enterprise Architecture Management Tools
Scenario: Landscape management current, planned, and target landscapes
© sebis 12 Enterprise Architecture Management Tools
Scenario: Demand management
Concerns of this scenario The IT department of the SoCaStore department store has received numerous
demands, which must be documented and linked to the affected elements of the EA. To prepare the project portfolio management a subject of the fiven demands has to be selected. These demands must subsequently be transformed into project proposals, combining demands asking for similar functionality or affecting the same application systems.
Typical questions to be answered Which demands have been received? Which application systems are affected by the individual demands? Which demands can be combined into one project proposal? …
© sebis 13 Enterprise Architecture Management Tools
Scenario: Project portfolio management
Concerns of this scenario The IT department of the SoCaStore department store has received numerous
project proposals. In consideration of the processes, organizational units, and application systems affected by the project proposals a selection of the project proposals should be made. The available budget for projects is 5 million EUR.
Typical questions to be answered Which project proposals have been received? What costs are calculated for which project proposal? What is the expected return of investment of which project proposal? Which processes/organizational units are affected by the changes as they use
the application systems modified by the project proposals? Which projects should be accomplished in any case? …
© sebis 14 Enterprise Architecture Management Tools
Scenario: Synchronization management
Concerns of this scenario To support the management of ongoing projects and to plan future projects,
there has to be the possibility to model and manage project interdependencies or to derive them from affected elements of the EA.
It should be possible to analyze the project timeline using Gantt-like diagrams. This timeline shall than be updated and annotated to reflect delays of a single project as well as to identify projects, that depend on it and might also be delayed.
Typical questions to be answered Which projects affect the same organizational unit? Which dependencies exist among projects? What happens, if a particular project is delayed? Which schedules have to be
adapted and how? …
© sebis 15 Enterprise Architecture Management Tools
Scenario: Strategy and goals management
Concerns of this scenario As part of the implementation of a balanced scorecard at the SoCaStore
department store the customer perspective is considered. The strategies and goals lead to different projects and changes in the EA. These changes should be traceable to the prior defined strategies and goals.
Typical questions to be answered Which strategy leads to which goals? Have all goals been reached? Which organizational units have not reached their goals? Which projects support which goals? …
© sebis 16 Enterprise Architecture Management Tools
Scenario: Business object management
Concerns of this scenario The department store SoCaStore wants to get an overview of the business
objects involved and exchanged in the execution of the business processes. Therein, especially the data flow between the application systems performing operations on the business objects should be modeled and the kind of operation performed in a specific application system should be detailed.
Typical questions to be answered Which business objects are created, modified, or deleted by which application
systems during the execution of which business process? Which application systems exchange business objects via which interface? Which application system holds the master copy of which business object? …
© sebis 17 Enterprise Architecture Management Tools
Scenario: SOA transformation
Concerns of this scenario An enterprise wants to transform its architecture into a service oriented one, with a top-
down and bottom-up approach to identify the possible candidates for reusable services. The top-down approach starts identifying services from the business objects perspective within the conduction of different business processes. The bottom-up approach starts with technical functionalities currently provided by business applications. The services should not only be identified but also the effects of the transformation should be modeled.
Typical questions to be answered: Does the business application support a differentiating or a standardized business
process? Which business functions supported by the current landscape are used within numerous
domains? What would a service oriented target architecture aligned to business needs look like?
© sebis 18 Enterprise Architecture Management Tools
Scenario: IT architecture management
Concerns of this scenario SoCaStore regards its heterogeneous application landscape as a problem. The high
number of technologies used in different architectures calls for a high number of experts. A homogenization may reduce operating costs, e.g. by consolidation of used software licenses, and maintenance expenses.
Typical questions to be answered: Which architectural solutions are used within the different domains of SoCaStore? Which solution elements are used within SoCaStore? Which of the existing solution elements should be kept, which should be replaced? Which application systems use which solution elements? What actions have to be derived, if architectures/solution elements are replaced?
© sebis 19 Enterprise Architecture Management Tools
Scenario: Infrastructure management
Concerns of this scenario The department store of SoCaStore intends to consolidate its database systems to
decrease the costs for maintenance and licening. Also, expected support periods offered by the database vendors should be considered.
Typical questions to be answered: What DBs are in danger of running out of support? Which DBs are currently in use? Which application systems use which DB? What are the costs for operating and licensing which DB? …
© sebis 20 Enterprise Architecture Management Tools
Outline of this unit
The Enterprise Architecture Management Tool Survey 2008 • Questionnaire • Scenarios • Results
What happened since the survey Approaches of the tools A wiki-based approach to EA management Selecting an EA management tool
© sebis Enterprise Architecture Management Tools 21
What is SoCaStore?
Simulation is based on a fictitious department store, called SoCaStore. Information model of SoCaStore consists of
• Business Processes • Organizational Units • Application Systems • Domains • Projects • ….
Information objects are maintained in an Excel sheet
© sebis 22 Enterprise Architecture Management Tools
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
total ca. 200 instances, ca. 700 links (using
foreign keys)
UML / Ecore
ca. 25 classes, ca. 30 associations,
ca. 90 attributes
3 different sizes
total ca.1000/5000/10000 instances
with each ca. 70 attribute values
and ca. 15 links
© sebis 23 Enterprise Architecture Management Tools
Overview on the evaluation process and its criteria
© sebis 24
Functional Criteria Online questionnaire for every vendor Simulation of functional scenarios with every
tool Documentation of the functional aspects and
the evaluation results in simulation
EA Management Task Criteria Simulation of typical EA Management tasks
with every tool One scenario per EA Management task
Documentation of the evaluation results in simulation
Final evaluation based on the results documented" Each evaluation criterion is assigned an ordering of tools reflecting their specific
support
9 Spider diagrams each"with 8 specific"functionalitites
8 Spider diagrams"each with 9 EA"management tasks
9 Tools are evaluated by 3 teams
Enterprise Architecture Management Tools
0
1
2
3
4
5
6
7
Importing, Editing, and Validating
Creating Visualizations
Interacting with, Editing of, and Annotating
Visualizations
Flexibility of the Information Model
Communication and Collaboration Support
Support of large scale Data
Impact Analysis and Reporting
Usability
Analyzing specific functionalities – Minimum and maximum achieved results
© sebis 25 Enterprise Architecture Management Tools
Analyzing specific functionalities – Details of the evaluation results
Communication und Collaboration Support Well supported with interesting features for colla-
boration,e.g. workflows and notification mechanisms Creating Visualizations Different approaches to visualizing the EA or parts
thereof - retaining potential for improvement • (Semi)-Automatic generation of visualizations still has
its limitations • 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 Visualizations Interaction is mostly „drawing“ – semantic changes could provide an
improvement towards graphical modeling Importing, Editing, and Validating No standard exchange format for EA models No common information model or core concepts thereof exist
0
1
2
3
4
5
6
7
Importing, Editing, and Validating
Creating Visualizations
Interacting with, Editing of, and Annotating
Visualizations
Flexibility of the Information Model
Communication and Collaboration Support
Support of large scale Data
Impact Analysis and Reporting
Usability
© sebis 26 Enterprise Architecture Management Tools
0
1
2
3
4
5
6
7 Landscape Management
Demand Management
Project Portfolio Management
Synchronization Management
Strategies and Goals Management
Business Object Management
SOA Transformation
IT Architecture Management
Infrastructure Management
Analyzing EA management support – Minimum and maximum achieved results
© sebis 27 Enterprise Architecture Management Tools
Analyzing EA management support – Details of the evaluation results
Landscape Management Different levels of support for the concept of time Versioning application landscapes retains
potential for improvement Not all tools provide methods for deriving the
planned landscape from the planned project portfolio
Synchronization Management No tool directly supports the concept of project delay
SOA Transformation Management Tool support for indentifying services retains potential for improvement
Infrastructure Management Not all tools provide concepts for lifecycle aspects of infrastructure components
0
1
2
3
4
5
6
7 Landscape Management
Demand Management
Project Portfolio Management
Synchronization Management
Strategies and Goals Management
Business Object Management
SOA Transformation
IT Architecture Management
Infrastructure Management
© sebis 28 Enterprise Architecture Management Tools
Outline of this unit
The Enterprise Architecture Management Tool Survey 2008 • Questionnaire • Scenarios • Results
What happened since the survey Approaches of the tools A wiki-based approach to EA management Selecting an EA management tool
© sebis Enterprise Architecture Management Tools 29
What happened since the survey…
The first study was conducted from January to September 2005, the recent results were gathered from October 2007 to April 2008.
The market of EA Management Tools is still moving.
Some vendors included the advices and critics from the survey of 2008.
© sebis 30 Enterprise Architecture Management Tools
Tool vendors added software maps (1)
Example ARIS Toolset from IDS Scheer AG Process Support Map in ARIS 7 Time interval map in ARIS 7 „Object-in-Object“-Functionality for Cluster Maps in ARIS 7
© sebis 31 Enterprise Architecture Management Tools
Tool vendors added software maps (2)
Example planning IT from alfabet AG Time interval maps in planningIT 1.0 Visualization of metrics in planningIT 2.1
© sebis 32 Enterprise Architecture Management Tools
Tool vendors added software maps (3)
Example Troux 7.1 from Troux Technologies Automatic Cluster Maps Visualization of metrics („Heat-Maps“) SOA Transformation Methodology
© sebis 33 Enterprise Architecture Management Tools
Outline of this unit
The Enterprise Architecture Management Tool Survey 2008 • Questionnaire • Scenarios • Results
What happened since the survey Approaches of the tools A wiki-based approach to EA management Selecting an EA management Tool
© sebis Enterprise Architecture Management Tools 34
Approaches of the tools (1)
EAM-Tools have different approaches Flexibility vs. Guidance regarding process, method, and information model for
supporting EA management Preconfigured vs. Customization regarding the functionality provided by the tool
out of the box – two approaches exist: EA management solution vs. EA management platform
Integration 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
(Framework-driven)
These approaches are not disjoint! Combinations of different approaches are possible Tools follow partially several approaches with variable degree of coverage
Attention: Mostly no exact matching between tools and approaches is possible!
© sebis 35 Enterprise Architecture Management Tools
Approaches of the tools (2)
Flexibility vs. Guidance: Meta model driven approach:
• Customers can adapt the information model to their needs • Reports and visualizations have to be adapted to the changed information model • Mightiness of the tools at changing the information model is heavily variable; From
small proprietary solutions up to MOF compliant solutions Methodology driven approach:
• Predefined and documented methodology (methodology manual) How to use which models? Which elements belong to which models?
• Only small or no changes to the information model, methodology remains • Reports and visualizations are coupled to the information model
Process driven approach: • Methodology is expanded with a management processs
The “what” and “how” of the methodology ist extended by the “when” • Process connects different modules in a process model
© sebis 36 Enterprise Architecture Management Tools
Approaches of the tools (3)
Preconfigured vs. Customization EA Management Solutions (Preconfigured)
• Preconfigured functionality for typical EA Management tasks are provided by delivery • “Misuse“ is aggravated • Rampant learning curve (Training, Consulting necessary)
EA Management Platforms (Customization) • At delivery only basic functionality is provided • Implementation of a company specific EA Management approach is possible • At the beginning of the implementation of the tool a customer specific adaption is
necessary
© sebis 37 Enterprise Architecture Management Tools
Approaches of the tools (4)
Integration vs. Single-point-of-truth Single-point-of-truth
• Data of EA are stored centrally in the EAM Tool • Replication is done „manually“ via imports
conflict resolution strategy is necessary • High data consistency, clear data sovereignty
Integration • EAM-Tool acts as „Data Warehouse“ • Main target of these EAM-Tools is the maintenance of the relation information • Reuse of different data sources • Linking, integration and aggregation of different sources in one model • Demands sophisticated transformation possibilities • Is also called „Metadata Integration“
Data consistency and data sovereignty may be problematic
© sebis 38 Enterprise Architecture Management Tools
Approaches of the tools (5)
Example of the combination of approaches Methodology driven and metamodel driven approach Tool owns methodology manual and Tools allows definition of customized information model
Variant 1: Information model is customized and the given model is changed (not only
extended!) Consequence: Predefined methodology has to be replaced partially! Remark: This is often done, when the tool has good meta modeling capabilities
and the methodology does not fit. Variant 2: Predefined information model is only extended slightly Consequence: Predefined methodology has to be extended! Remark: This is often done, when the tool has a good methodology manual but
the company specifications are missing
© sebis 39 Enterprise Architecture Management Tools
Approaches of the tools (6)
Example of an unusual (or curios) approach for the usage of a methodology driven EAM tool: Meta model can not be adapted in the tool, but the methodology is bended.
• The information model is implicitly redefined • Existing models of the tool are redefined using a self-developed method manual
Consequences: An own method manual has to be written Remark:
• If a tool is already applied in an enterprise, which is (politically) set, or no funds are available for the purchasing of a new product, this method is chosen frequently
• Even UML-tools are used!
© sebis 40 Enterprise Architecture Management Tools
Outline of this unit
The Enterprise Architecture Management Tool Survey 2008 • Questionnaire • Scenarios • Results
What happened since the survey Approaches of the tools A wiki-based approach to EA management Selecting an EA management Tool
© sebis Enterprise Architecture Management Tools 41
Starting an EA management initiative does not come without problems
Emerging EA management initiatives often start informal using spreadsheets or text documents since
• the development of an information model is a labor intensive task and • no widely-accepted standard information model exists.
With the growing complexity of the management body and the rising number of stakeholders involved, problems arise regarding
• scalability and • collaborative work.
Introducing an EA management tool is often regarded to solve these problems.
How to support an evolutionary approach to EA development (esp. regarding the design of an enterprise-specific information model)?
How to map the grown structure of informal documentation to structures as incorporated in EA management tools?
© sebis Enterprise Architecture Management Tools 42
[Bu09]
A wiki-based approach facilitates EA documentation, communication, and analysis by
Watch lists and change feeds, which • allow a stakeholder to get notifications, if certain parts of the
documentation, he/she is responsible for, is changed and • support the head of a group of people to keep track on the progress made,
e.g. in an documentation endeavor. Versioning, which
• enables historization of EA descriptions or parts thereof (incl. information models)
• supports traceability of the origin of changes if comments for changes are supported, e.g. effects of a project
Collaborative tagging and bookmarking, which • enable flexible organization of resources by categorization according to
cross-cutting concerns, e.g. data security, • allow the user to keep track or inform fellows of open activities (task
organization tags) Roles and rights management
© sebis Enterprise Architecture Management Tools 43
[Bu09]
Tricia as an enterprise wiki
© sebis Enterprise Architecture Management Tools 44
WYSIWYG-Authoring
Tagging Bookmarking Awareness Commenting Linking Social networking Access control Search (full-text) Versioning …
Extending wikis with templates to support structured content
Automated data processing and visualization, which are essential in an EA management context impose additional requirements on data representation. capture data in a structured form
Existing wikis rely on text formatting conventions to express structure (e.g. www.wikipedia.org, cf. Figure), but do not offer native support of automated data processing.
Semantic wikis (e.g. http://semantic-mediawiki.org), try to exploit complex semantic web technologies but often lack usability.
Our approach: templates provide a simple extendable table containing attributes, textual values, and links.
© sebis Enterprise Architecture Management Tools 45
Templates as part of Tricia wiki pages
© sebis Enterprise Architecture Management Tools 46
The template in detail
Enterprise Architecture Management Tools 47 © sebis
Existing templates can be assigned to a wiki page to provide an initial set of attributes (labeled table rows)
Attributes are either literals or links to other wiki pages
Attributes can be edited in the same manner as wiki text
New attributes can be added easily
Links at work
Enterprise Architecture Management Tools 48 © sebis
Each association between two templates has an owning side (i.e. the side where the relation is specified in an attribute)
This avoids redundancies and inconsistencies
Navigation is facilitated by providing links to referencing wiki pages grouped by template
Management of templates
Enterprise Architecture Management Tools 49 © sebis
Overview on textual description of the underlying concept and its attributes template statistics, e.g. number of instances or attribute assignments
Activities rename templates and attributes configure further constraints on the values of attributes, e.g. type of
referenced template
Outline of this unit
The Enterprise Architecture Management Tool Survey 2008 • Questionnaire • Scenarios • Results
What happened since the survey Approaches of the tools A wiki-based approach to EA management Selecting an EA management Tool
© sebis Enterprise Architecture Management Tools 50
Generic tool selection process (1)
© sebis 51
1
Create List of Criteria • Collecting demands for tool support from stakeholders • Consolidate demands in a list of criteria • Define „must have“ criteria in order to speed up the selection process • Weighting the criteria • Define scales for the evaluation of the tools
2
Create Long List • Analyze the market for existing tools • Analysts, like e.g. Gartner, may be a source for a list of existing tools
• Be aware that they do not list all available tools! • Studies for EAM tools may be another source for available tools
3
Reduce to Short List • Apply list of criteria on long list in order to select 2-3 tools, which will be further evaluated
• Looking for „must have“ criteria speeds up the selection process • No complete objective evaluation possible
[Ke07b]
Enterprise Architecture Management Tools
Generic tool selection process (2)
© sebis 52
4
„Test-Drive“ the Tools • The 2-3 selected tools should be evaluated in depth (workshop with vendor and stakeholders) and possibly do a „test-drive“ in the context of a test installation
5
Decide • Decide for one of the tools of the short list in cooperation with the stakeholders
• Preferably in a workshop • Involving the stakeholders prevents for subsequent criticism
6
Re-negotiation and Buying Decision • Do another price negotiation with tool vendor • Afterwards make buying decision or possibly go back some of the steps
[Ke07b]
Enterprise Architecture Management Tools
Thank you very much for your attention!
Discussion...
Open source EAM Tools Essential project: http://www.enterprise-architecture.org/ Iteraplan http://www.iteraplan.de Protégé http://protege.stanford.edu/
© sebis Enterprise Architecture Management Tools 53
Bibliography
[Bu09] Buckl, S.; Matthes, F.; Neubert, C.; Schweda, C. M.: A wiki-based Approach to Enterprise Architecture Documentation and Analysis. In: 17th European Conference on Information Systems (ECIS2009), Verona, Italy, 2009.
[Ke07b] Keller, W.: Application-Portfolio-Management. Vorlesung IT-Unternehmensarchitektur; Hasso-Plattner-Institut, Potsdam, 2007.
[Ma08] Matthes, F.; Buckl, S.; Leitel, J.; Schweda, C. M.: Enterprise Architecture Management Tool Survey 2008. Technische Universität München, Munich, Germany.
© sebis 54 Enterprise Architecture Management Tools