The document discusses using enterprise architecture models to detect symptoms of misalignment between business and IT. It defines misalignment as an inaccurate mapping between enterprise architecture layers. The author proposes assessing enterprise architecture models to look for misalignment symptoms and identify incorrect relationships between architecture components. The goal is to develop a research tool that can detect misalignment symptoms through enterprise architecture assessment.

1. Analysing Enterprise Architecture Models
to Detect Misalignment Symptoms
Dóra Őri
PhD student
Corvinus University of Budapest

2. The importance of
business-IT alignment
The need for aligning business and IT
Use IT
effectively
to achieve
business
goals
The ability
of IT to
create
business
value
TÁMOP-4.2.2/B-10/1-2010-0023
Bridge the
gap
between
business
and IT
Integrate IT
to business
strategy,
mission,
goals

3. On the way to misalignment
Failures while
achieving
alignment
Different
objectives, culture,
body of knowledge
between business
and IT
Fail to adapt to
rapid changes in
technological
environment
...
TÁMOP-4.2.2/B-10/1-2010-0023
A mistake
anywhere along
the way can
appear as
misalignment

4. Explanatory misalignment
symptoms
Undefined organizational strategy and organizational goals
Undefined business process goals
Undefined security requirements over the information entities
Users managed differently in different applications
Undefined capacity and performance requirements
Lack of relation between process goals and organizational goals
Lack of data ownership
Poor IT planning and portfolio management
Multiple hierarchy or lines of reporting
Lack of data quality controls
Lack of applications interfaces
Multiple applications managing the same information
TÁMOP-4.2.2/B-10/1-2010-0023

5. Enterprise architecture-based
alignment assessment
Enterprise
architecture
assessment for
analysing the state of
business-IT
alignment in an
organisation
TÁMOP-4.2.2/B-10/1-2010-0023

6. Enterprise architecture
to capture a vision of the entire system in all its dimensions
and complexity
to coordinate the many facets that make up the
fundamental essence of an enterprise
A framework:
to provide a structure for business processes and
supportive information systems
which acts as an integrating force between aspects of
business planning, business operations and the enabling
technological infrastructure of the business
TÁMOP-4.2.2/B-10/1-2010-0023

7. …in all its dimensions and
complexity…
TÁMOP-4.2.2/B-10/1-2010-0023

8. Rephrasing misalignment
In the context of enterprise architecture
misalignment is…
…the inaccurate mapping between the different
architecture layers.
…an irregular condition that derogates the different
architecture components together with the desired fit
between them.
TÁMOP-4.2.2/B-10/1-2010-0023

9. Misalignment assessment
Assessing the
state of
alignment/
misalignment in
an organisation
Looking for
misalignment
symptoms in
enterprise
architecture
models
Identifying
inaccurate
mappings
between
architecture
layers
Enterprise architecture-based misalignment symptom detection
TÁMOP-4.2.2/B-10/1-2010-0023

10. Research questions
How can the misalignment problem be rephrased
in the context of enterprise architecture?
Can we implement a research tool to detect
misalignment symptoms in enterprise
architecture models?
Which misalignment symptoms can be detected
via enterprise architecture assessment?
TÁMOP-4.2.2/B-10/1-2010-0023

11. Summary
Enterprise
architecture
Enterprise
architecture
assessment
Misalignment
symptom
detection via
enterprise
architecture
assessment
TÁMOP-4.2.2/B-10/1-2010-0023
The need
for
businessIT
alignment
Alignment misalignment
continuum
Misalignment
symptoms

12. Assessing the
state of
alignment/
misalignment of
an organisation
Looking for
misalignment
symptoms in
enterprise
architecture
models
Identifying
inaccurate
mappings
between
architecture layer
Enterprise architecture-based misalignment symptom detection
Thank you for your attention!
Dóra Őri
PhD student
Corvinus University of Budapest
dori@informatika.uni-corvinus.hu
TÁMOP-4.2.2/B-10/1-2010-0023