Embed Size (px)
Citation preview
Enterprise Architecture ToolsGood enough Point of View
Behzad AndishmandSWEAN 14 : 2010-05-07
Copyright – Good enough Architecture MEthodology
Content
First , some definitions and questions How to select an EA tool Quick comparision of some EA tools Lessons learned More information
2
Copyright – Good enough Architecture MEthodology
FIRST, SOME DEFINITIONS AND QUESTIONS
3
Football Football=
< >
Copyright – Good enough Architecture MEthodology
Good enough definition of EA
Enterprise Architecture is
the art of making sure that
the right people do
the right things in
the right place at
the right time!
How?
Why?
Who?
What?
Where?
When?
4
Question 1:Which one of these do Youcover in the answersthat your EA work provides?
Copyright – Good enough Architecture MEthodology
Different usage of the information, from perspectives of different stakeholders, is a challenge for the EA repository.
5
Question 2a: What is the focus area of your EA work?Question 2b: Who are your stakeholders?Question 2c: What information do you deliver to them?Question 2d: What information do n’t you/them have?Question 2e: Where do you find/create all that information?
Copyright – Good enough Architecture MEthodology
Question 3: In which areas do you have the most current/reliable information about how your company’s EA looks like and performs in reality?
Scope definition Business definition
Scenario definition Architecture definition
Component definition
Lifecycle definition
Vision
Goals
Principles&
GuidelinesProcesses
Informationdefinitions
Functions/Services
Measurementpoints
Stakeholdes
Locations
More(if needed)
Needs &Concerns
As-Is Architecture
ArchitectureScenarios
FunctionalRequirements
Non-Functional
Requirements
To-BeArchitecture
Development& Test
Hand-over, Operation &Maintenance
As-Is definition
6
Copyright – Good enough Architecture MEthodology
Question 4
Assuming that your EA work: Is quite successful :
You have good enough information about what you need to know And You are able to provide good enough information for your
stakeholders, then what is wrong with the tools that you already use?
Or is not as successful as it should be or perhaps it is in the beginning phase and you still don’t know if it will succeed:
then what is wrong with the tools that you already use?
7
Copyright – Good enough Architecture MEthodology
HOW TO SELECT AN EA TOOL
8
Copyright – Good enough Architecture MEthodology
Gartner says
9
It is a view of the market as a whole.
Best EA tool for a given organization might well be outside of the Leaders quadrant.
Often, niche problems reuire niche solutions.
Copyright – Good enough Architecture MEthodology
How to select a tool that is better than what you already have: Decide which areas are in focus of the EA work Check evaluation guides (links available in ”More information”) Create customized checklist from above Evaluate the existing tool(s) according to the checklist Evaluate the selected EA tools according to the checklist Decide which EA tool to go on with Plan and define the scope of a Proof-of-Concept Perform a Proof-of-Concept
Through a minor (or preferably none) customization of the tool’s repository meta model and And a quick evaluation of integration with your current repository, documentation, communication
and reporting tool(s) Analyze, define and report the findings and the short-term implementation roadmap
And when the tool is in place: Implement a real-life pilot (from a real-life stakeholder’s perspective)
Analyze and make the adequate adjustments to the implementation roadmap Follow the implementation roadmap, stepwise and with the adjustments due to your own (which
should be equal to your stakeholders) prioritizations
10
Copyright – Good enough Architecture MEthodology
Areas in focus of the EA work
11
Business process landscapedesign, development & management
Data landscapedesign, development & management
In
teg
rate
d S
ec
ure
d
Governancedesign, development & management
Infrastructure landscapedesign, development & management
Application portfolio landscapedesign, development & management
Copyright – Good enough Architecture MEthodology
COMPARISION OF SOMEEA TOOLS
The evaluation was done according to a customized checklist based on the evaluation area definitions and questions in this questionnaire provided by Institute For Enterprise Architecture Developments.
12
Copyright – Good enough Architecture MEthodology
Definitions
13
Expected Minimumresults
EvaluatedTool’sresults
Evaluationarea
Copyright – Good enough Architecture MEthodology
ARIS (IDS Scheer)
14
Copyright – Good enough Architecture MEthodology
System Architect (IBM)
15
Copyright – Good enough Architecture MEthodology
Troux Transformation Platform (Troux Techn.)
16
Copyright – Good enough Architecture MEthodology
Qualiware (Qualiware)
17
Copyright – Good enough Architecture MEthodology
Enterprise Architect (Sparx systems)
18
Copyright – Good enough Architecture MEthodology
LESSONS LEARNED
19
Copyright – Good enough Architecture MEthodology
Lessons learned
If you can manage your EA approach by using the tools that you already have, then you will be able to get it done even with an EA tool
20
Documentation & Repository tools Analysis & Design tools Reporting & Communication tools
One tool does not do it all for all stakeholders Prioritize and decide what and for whom and
in which tool ”A fool with a tool is still a fool”
Copyright – Good enough Architecture MEthodology
More lessons learned
Even if an EA tool will improve the process and increase the quality of your work with EA, they usually slow it down a bit at the beginning. It is recommended to avoid to start your EA initiative by bringing in an EA tool at the same time.
An EA tool implementation is not different from other tools implementations. Start small and deliver results that your stakeholders can use in their day-to-day work from day 1.
Automated information gathering and distribution is a key success factor for the EA repository.
My personal opinion is still that most EA tools are: Really good for As-Is and To-be documentations, when it does not fit into
some Excel sheets Quite helpful for communication of your EA work As good as Excel and other Office tools for simple but yet useful analysis
21
Copyright – Good enough Architecture MEthodology
MORE INFORMATION
22
Copyright – Good enough Architecture MEthodology
More information
EA tool selection criteria (link) Togaf : Tools for Architecture Development (link) Applicable standards for tools selection:
IEEE Std 1209-1992 ISO 14102
Reports: Gartner: Magic Quadrant for Enterprise Architecture Tools Forrester Research: EA Tools and IT Planning
Open source alternatives: The Essential Project (link) Iteraplan (link) And if your EA work is focused on providing a repository for your
(customizable) Togaf 9.0 methodology: Eclipse Process Framework (link)
23
Copyright – Good enough Architecture MEthodology
Thank You
24 Copyright: GAME (Good enough Architecture Methodology)
