1

MODULE 2:
Results of Enterprise
Architecting
(Quality of Results)

ITS 580
 Aim of Topic
2

 Previously we have discussed

 the needs for EA.
 EA as a means to meet these needs.

 This lecture focus on the process

results of enterprise architecting.

#
3 Quality of Results
Introduction
 EA Results
4

 The EA development process creates

products that are used in the EA
deployment process.
 2 types of EA products:

Tangible
Intangible

#
 Enterprise Architecting :
5

 These tangible results are not limited to

 principles,
 models,

 views

 intermediate results used to develop the enterprise

architecture and
 the evaluation of alternative solutions/directions.

#
 Enterprise Architecting :
6

 Some of the non-tangible results:

 shared understanding,
 shared agreement, and
 commitment amongst stakeholders.

#
 Criteria for Results Quality
7

Enterprise architecture can produce a large variety of tangible and

intangible results. What criteria on product quality are needed
to make the choices of:
which results should be delivered?
what levels of details are required?
What are the form of the results?

o …depends on
 the stakeholders and their concerns, and

 the decisions that should be taken based on these results.

#
 When Is Good Good Enough?
8

 A lot of resources, such as money, time, emotional

energy, and intellectual energy are invested into the
creation of enterprise architecture results. This raises
the question of whether these resources are spent
well.
 Dothe results meet the needs?
 What is the quality of the results?

 What is the return on modeling effort (RoME)?

#
 Approach to Understanding Uses of
9
Architecture Results
 Previously the class take the position that the
enterprise architecture products depends on the
stakeholders and their concerns.
 Hence it is logical, in considering the quality of
enterprise architecture products, we take the
position that the stakeholders, their concerns, as well
as their information, insight and/or steering
requirements as a starting point.

#
 Who Are The
Stakeholders Of The
Architecture
Results?

10
 Uses of Architecture Results
11

1. Top-level management—Is the intended

transformation still justified given the (expected)
improvements in relation to the (expected) costs of
the transformation? How can we ensure our
policies are followed in the development and
operation of processes and systems? What is the
impact of decisions (on personnel, finance, IT, etc.)?
2. Middle-level management—The current situation
with regard to the computerized support of a
business process.
#
 Uses of Architecture Results
12

3. End user—The potential impact of a new system

on the activities of a prospective user.
4. System administrators—The potential impact of
a new system on the work of the system
administrators that are to maintain the new system.
5. Operational manager—What new technologies
do we need to prepare for? Is there a need to
adapt maintenance processes? What is the impact
of changes to existing applications? How secure
are my systems?
#
 Uses of Architecture Results
13

6. Architect—The requirements of a specific

stakeholder with regard to the desired situation.
What are the consequences for the maintainability
of a system with respect to corrective, preventive,
and adaptive maintenance?
7. Project manager—What are the relevant domains
and their relations, what is the dependence of
business processes on the applications to be built?
What is their expected performance?

#
 Uses of Architecture Results
14

8. System developer—What are the modifications with

respect to the current situation that need to be
performed? In the ArchiMate project [78], three
purposes for models and views have been identified:
 Designing—supporting architects and designers in the
design process from initial sketches to detailed design.
 Deciding—supporting decision makers in the process of
decision making by offering an insight into the
issues/impacts they need to decide upon.
 Informing—supporting the informing of any stakeholder
about the enterprise architecture and its impact on the
future enterprise. #
 Uses of Architecture Results
15

 Architecture results have become part of formal contracts

governing outsourcing and/or procurement [42].
Developments such as outsourcing stress the purpose of
architecture results for contracting reasons. 4 types of goals
for which architecture results may be created:
1. Specifying—making explicit the requirements, principles
or designs pertaining to the enterprise, ranging from initial
sketches to detailed specifications, including their
justification in terms of earlier made decisions.

#
 Uses of Architecture Results
16

2. Deciding—supporting decision makers in the process of

decision making by offering an insight into the
issues/questions, as well as their consequences and
possible justifications, they need to decide upon.
3. Informing—supporting the informing of any stakeholder
about the enterprise architecture and its impact on the
future enterprise, possibly including their justification.
4. Contracting—providing a formal statement of the
architectural requirements of enterprise/system
components to be realized/worked-out by a supplier.

#
 Conclusion
17

 “Enterprises are constantly subjected to internal and

external changes. One way to deal with these
changes is to be integrated and agile. Enterprises
can use Enterprise Architecture as a way to achieve
integration and agility in a coherent and consistent
way, through EA products created by the EA
development process. Therefore, the quality of an EA
product is its ability to aid integration and agility in
a coherent and consistent way.”

#
18
 Reference
19

 Op’t Land et al. (2009). Enterprise Architecture :

creating value by informed governance. Springer-
Verlag Berlin Heidelberg