Sei sulla pagina 1di 22

1

MODULE 2:
Results of Enterprise
Architecting
(Enterprise Architecture
Framework)

ITS 580
Aim of Topic
2

 We have discussed
 the needs for EA.
 EA as a means to meet these needs.
 the tangible and intangible products of
enterprise architecting.

#
Enterprise Architecture
3

 An enterprise architecture
A formal description of an enterprise, or a detailed
plan of the enterprise at component level to guide its
implementation.
 The structure of components, their inter-relationships,
and the principles and guidelines governing their
design and evolution over time.

#
Enterprise Architecture is
about understanding all of
the different components
that go to make
up the enterprise and how
those components inter-
relate.

4
Enterprise architecture is a complete expression of the
enterprise; a master plan which “acts as a collaboration
force” between aspects of business planning such as
goals, visions, strategies and governance principles;
aspects of business operations such as business terms,
organization structures, processes and data; aspects of
automation such as information systems and databases;
and aspects of enabling technological infrastructure of the
business such as computers, operating systems and
networks.

IFEAD is an independent research and information exchange organization working on the future state of Enterprise
Architecture.

5
Criteria for Choices of Results
6
Quality
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.

#
In such choices, we can also profit
from an insight how the possible
results interrelate, as described in
architecture frameworks .

7
 Enterprise architecture frameworks provide:
a means to order architecture results;
 a means to guard the completeness of the
architecture results, both in terms of scoping
and level of detail;
 insight into the interrelationships of architecture
results, enabling the traceability of decisions and
their impact.

8
9 Enterprise Architecture Framework
Introduction : provides clear insight into the
relationships in an organization.
Introduction
10

 The foundational elements of an EA program are


the analysis and documentation framework (EA
framework), and the implementation methodology
(EA methodology).
 The EA framework defines what the EA program
will document.
 The EA methodology defines how that
documentation will be developed and used.

#
EA Program
Foundational Elements

Analysis and Implementation


Documentation Methodology
Framework
EA Framework: What EA Methodology: How

The EA framework defines the scope of the architecture


by defining what parts of the enterprise are included in
the EA.
11
Impact of Using a Framework
12

Use of a
framework
leads to: The use of common principles,
assumptions and terminology.

The development of information


systems with better integration and
interoperability, especially with
respect to issues that affect the
whole enterprise.

#
13 Enterprise Architecture Framework
EA Framework
14

 Zachman
 TOGAF
 FEAF
 Oracle

(https://msdn.microsoft.com/en-us/library/bb466232.aspx :Roger Sessions))

#
Dimensions of Architecture
15
Framework
 Opt’land distinguish three classes of dimensions:
1. Dimensions pertaining to the subject of a view.
 concerned with the subjects of the cells.
2. Dimensions dealing with the purpose of views.
 refers to the communicative goal of the result, the intended
audience and the process context.
3. Dimensions concerned with the form of views.
 refers to the communication style and languages used.

#
Subject Dimensions
16

 Enterprise frameworks concerned with the subjects


of the cells in the framework:
 Range

 Construction abstraction
 Implementation abstraction

 Enterprise system types

 Aspects of dynamic systems

 System qualities

 Interrogatives

#
Purpose Dimensions
17

 Refer to the communicative goal of the result, the


intended audience and the process context:
 Goal of the result
 Audience

 Transformation stage

 Planning horizon

#
Form Dimensions
18

 Form of an enterprise architecture result refers to


the communication style and languages used. The
actual form of a result should be inline with its
intended purpose and audience.
 Intangible results, 3 dimensions:
 Level of understanding
 Level of agreement

 Level of commitment

#
Form dimensions
19

 Eg of tangible form graphical model/view, textual


model/view or combination.
 2 dimensions:
 Level of detail
 Level of precision

#
Conclusion
20

 EA frameworks, such as TOGAF etc are associated with EA


products. Frameworks are not products of EA processes but
can be seen as containers for EA products. Frameworks state
when and why products should be created and how they relate
to each other (The Open Group 2003). A good example is
the Zachman framework (Zachman 1987), which says very
little about the products in each cell but explains the meaning
of the cells containing them. This makes frameworks
fundamentally different in nature from an EA product.

#
Conclusion
21

 EA framework is one of the foundational elements of an EA program


and implementation methodology. Explorations of some of the
frameworks illustrate the range of frameworks in enterprise
architecture context and the possible dimensions these frameworks
may occupy.
 The EA framework establishes the scope of the EA documentation
effort, and relates the areas of the architecture together.
 Common characteristics of most EA frameworks are that they
address multiple, often hierarchical views of the enterprise and
technology to distinguish high-level views that are of value to
executives and planners from the more detailed views that are of
value to line managers and support staff.

#
References
22

 Pereira, C.M. and Sousa, P. 2004. A Method to Define an Enterprise


Architecture using the Zachman Framework, 2004 ACM Symposium on
Applied Computing, Nicosia, Cyprus
 Op ’t Land, M . Proper, E. Waage, M. Cloo, J. and Steghuis, C. 2009.
Enterprise Architecture: Creating Value by Informed Governance, Springer-
Verlag, Berlin Heidelberg

Potrebbero piacerti anche