1. Dear, ... to share my small work and search on Enterprise Architecture Visualization
2.So, my presentation today will be based on those outlines:
We will go through Introduction part that has a summary of the goal of my topic, EA, EA tools, problems and soulution
The second part will be more concentrated on EA visualization
And the conclusion
3. Introduction
4. From this definiton wi see that:
-this is the aim of visualization
-to make sense and conect all infromation available
-with different methods and models.
5. And out of this, the goal of my presentation is to give an overview of visual techniques, methods and approaches in existing EA tools, and to see what we can recommend for further and future development.
6. So, to answer what is EA we must say that the task of EA is to make the interaction between IT and business processes and to represent it.
And in this context EA should offer fast response, better efficiency and shorter adaptation time in a globalized world.
7. And, we use EA to manage change and complexity in several steps:
1. To have an overview in current or real situation
2. Connecting business and IT
3. Outsourcing
4. To support projects
5. To support portfolio management
6. Communication with stakeholders
7. Impact analysis and trade-off analysis ( is something cost-effective)
....
...
4. “Nowadays, as we are more capable of capturing all
kinds of information, the need to make sense of it is
most compelling. Besides addressing the problem of
collecting this data, the main issue is to propose
methods and models, which can turn it into reliable and
provable knowledge.” *
__________
* Keim, D.,Andrienko, G., Fekete, J.D., Gorg, C., Kohlhammer, J., Melanon, G.:Visual analytics:
Definition, process and challenges. In: Information Visualization.Volume 4950 of Lecture Notes in
Computer Science. Springer Berlin / Heidelberg (2008) 154–175.
4 Shkumbin Rrushaj
5. Goal
The goal of this presentation is to give an overview of
visual techniques, methods and approaches in existing
EA tools and to draw conclusions for future research
and development.
5 Shkumbin Rrushaj
6. What is Enterprise Architecture?
• Task of Enterprise Architecture (Management) (EA/EAM) is to
align the interaction between IT and business processes.
• IT is called for in this context - the companies gain competitive
advantage by moving to faster response times, better efficiency
and shorter adaptation times in response to changing
conditions in a globalized world.
6 Shkumbin Rrushaj
7. Why Enterprise Architecture?
Managing change and complexity:
Obtaining insight in current situation (as-is)
Aligning business and IT
Outsourcing
Project support (project start architectures)
Portfolio management
Communication with stakeholders
Impact analysis and Trade-off analyses…
7 Shkumbin Rrushaj
8. What makes EA?
EA* consists of the various structures and processes of an
organization, including both technical structures and processes
as well as business/domain structures and processes.
* Architecture = structure(s) of a system in terms of:
- components,
- their externally visible properties,
- their relations,
- and the underlying principles.
8 Shkumbin Rrushaj
9. What makes EA?
Therefore, EA requires a holistic approach. It should include:
• the business activities,
• internal processes,
• services,
• applications,
• infrastructure services, and
• platforms and databases.
9 Shkumbin Rrushaj
10. EA models
An enterprise architecture model is a representation of those
structures and processes.
• A good enterprise architecture model will depict the whole
organization and map the various views representing the
architecture to each another.
• These views include both business-oriented perspectives as well as
technical perspectives.
10 Shkumbin Rrushaj
12. EA tools
The task of EA tools is to support EA management (e.g.
maintenance of the EA models along with their information, creation
of reports, etc).
The essential component of these reports are often visualized
representations of the EA.
12 Shkumbin Rrushaj
13. Advantages of EA tools
• Increasing consistency of the architecture
• consistency and model checking mechanisms
• Automatic generation of views and visualizations
• tailored for a particular stakeholder
• Work in teams
• …
13 Shkumbin Rrushaj
14. Problem
EA is hard to perform:
The EA is basically a complex system of many systems.
Plethora of infrastructural items of different origins, types, functions…
Many stakeholders with different interests, technical literacy, expertise…
Because EA items are strongly intertwined, they are difficult to model.
In addition, EA tools are not always up to the task.
14 Shkumbin Rrushaj
15. Visualization support for EA
One of the approaches to solving this problem is
to strengthen EA tool with visual support for EA
management.
15 Shkumbin Rrushaj
16. Why is EA visualization important?
• It’s used to capture and visually represent the
infrastructure and the diverse connections and
relationships between all items!
• A visual representation can represent complex
information in a clear and understandable way to
various stakeholders, and thus promote
comprehension.
16 Shkumbin Rrushaj
18. SEBIS survey on EA visualizations
To explore the EA visualizations provided in existing EA
tools, the Software Engineering for Business Information
Systems (SEBIS) department of the Faculty of Computer
Science at theTechnische Universität München (TUM)
conducted an online survey.
18 Shkumbin Rrushaj
19. SEBIS survey findings
The findings are reported in the study "Enterprise Architecture
VisualizationTool Survey 2014" by Sascha Roth, Marin Zec and
Florian Matthes. *
The study focuses on the analysis of the visualization capabilities
of EA tools.
EA Model Maintenance, configuration, customization,
production, import and export, layouting…
* Sascha Roth, Marin Zec, Florian Matthes. Enterprise ArchitectureVisualizationTool Survey 2014.
epubli GmbH, 2014.
19 Shkumbin Rrushaj
20. SEBIS survey target group
The primary target group of the survey were users of EA tools such as:
• Responsible CXO-level,
• Strategic Enterprise Architects,
• Portfolio managers,
• Consultants and analysts,
• Suppliers,
• Consultants and
• Market researchers.
109 users were interviewed.
20 Shkumbin Rrushaj
21. SEBIS survey on EA visualizations
18 tools explored:
ABACUS of Avolution,
ADOit of the BOC AG,
ARIS Software AG,
BiZZdesign EA Tool Suite from
BiZZdesign,
Corporate Modeler Suite of Casewise,
Enterprise Architect from Sparx
Systems Ltd,
EnvisionVIP of Future Tech Systems,
iteraplan from iteratec GmbH,
Layer8 from Layer8-Solutions GbR,
• leanIX from LeanIX GmbH,
• MEGA MEGA International,
• planningIT by Software AG,
• PowerDesigner Sybase or SAP AG,
• process4.biz process4.biz of the software
development andVertriebs GmbH,
• QPR Enterprise Architect of QPR
Software,
• Rational System Architect from IBM,
• SAMU Repository by Atoll Technologies
Ltd. and
• Txture from QELaB Business Services
GmbH.
21 Shkumbin Rrushaj
22. Abacus
Flow Diagram of ABACUS -This representation shows how
ABACUS visualizes data using a flow chart.
22 Shkumbin Rrushaj
23. Enterprise Architect
ER Diagram of the Enterprise Architect
Flow Diagram of the Enterprise Architect
-This representation shows how Enterprise
Architect visualizes data using a flow chart.
23 Shkumbin Rrushaj
24. SAMU
Flow Diagram of the SAMU Repository
- A flowchart in SAMU Repository.
24 Shkumbin Rrushaj
25. Rational System Architect from IBM
Impact analysis in Rational System Architect.
- The arrow graph illustrates dependencies.
BPMN Diagram of the Rational System Architect.
-The BPMN diagram in Rational software.
25 Shkumbin Rrushaj
26. EnvisionVIP
Flow Diagram of EnvisionVIP
Thus, a flow chart with EnvisionVIP appearance.
BPMN Diagram of EnvisionVIP
The representation of business processes according to BPMN.
26 Shkumbin Rrushaj
27. SEBIS survey findings
• The survey shows that most of the 109 EA tools
users rely on Microsoft tools for visualization.
• Trend is towards web-based solutions for EA
visualizations.
27 Shkumbin Rrushaj
28. SEBIS survey findings
• The authors list a total of 26 different types of visualization,
such as:
1. table,
2. flowchart,
3. 3-D graphics,
4. dashboard and representation according to Business Process
Model and Notation (BPMN)…
• Particularly frequently used forms of representation are the
cluster map, matrix, timeline and the flowchart.
28 Shkumbin Rrushaj
29. SEBIS survey findings
Interestingly, there are, depending on the job profile, different
preferences:
• Bubble charts (point or pie charts) are mainly used in
communication with the IT, departmental managers and C-level
executives.
• BPMN is a common display format for business analysts.
• UML is relevant for enterprise and solution architects.
• Dashboards are aimed principally for informing C-level stakeholders.
• The Event Driven Process Chain (EPC) is often used by business
analysts.
29 Shkumbin Rrushaj
30. SEBIS survey findings
Study revealed differing update frequency patterns among different
stakeholder groups:
• Visualizations for C-level management are mostly updated on a
quarterly or monthly basis.
• In contrast, business analysts, solution architects as well as lower
and middle level managers with business focus tend to demand
for more frequent updates (e.g. on a weekly basis).
• A significant share of solutions architects even asks for daily
updates.
30 Shkumbin Rrushaj
31. SEBIS survey findings
• The survey also shows that the operation of the tools
is now easier - even less experienced users can
customize their models and sometimes visualizations.
• Nevertheless, there is a need for further
simplification for users, so that the customizing is
easier to perform.
31 Shkumbin Rrushaj
32. Conclusion
In short:
• Many EA tools, that are very friendly to use and have a
very good performance on different platforms, with many
types of visualizations
• Some visualization types are used more often than others.
The 5 most widely used visualization types are: cluster
map, matrix, graph, timeline and flow diagram.
• Differing update frequency patterns among different
stakeholder groups.
32 Shkumbin Rrushaj
33. Conclusion
It is recommended that more focus and research effort
is directed towards:
• simplification of the tools
• visual support for EA management
• to capture and visually represent the infrastructure
and the diverse connections and relationships
between all items.
33 Shkumbin Rrushaj
34. References
Shkumbin Rrushaj34
• Keim, D.,Andrienko, G., Fekete, J.D., Gorg, C., Kohlhammer, J., Melanon, G.:Visual
analytics: Definition, process and challenges. In: InformationVisualization.Volume
4950 of Lecture Notes in Computer Science. Springer Berlin / Heidelberg (2008)
154–175.
• Sabine Buckl and Christian M. Schweda. On the State-of-the-Art in Enterprise
Architecture Management Literature.Technical Report 2012
• https://wwwmatthes.in.tum.de/pages/1bcg9q4ds39aa/Publications
• Sascha Roth, Florian Matthes.Visualizing Differences of Enterprise Architecture
Models. InternationalWorkshop on Comparison andVersioning of Software Models
(CVSM 2014)
• David Naranjoa Mario Sáncheza JorgeVillalobosa. Evaluating the capabilities of
Enterprise Architecture modeling tools forVisual Analysis.Article2015
• Sascha Roth, Marin Zec, Florian Matthes. Enterprise ArchitectureVisualizationTool
Survey 2014. epubli GmbH, 2014.