 |
Enterprise Architecture Overview - To
remain competitive, organizations must
be able to anticipate and respond to
market changes, modifying products and
services in increasingly shorter cycle
times.
To support this demand for quick changes,
the enterprise must become more agile
from a Business, an Application and
a Technology perspective.
In all levels of the organization, to
face Change, management must make more
informed spending decisions faster and
with a higher probability of success
and all that combined with increased
complexity and budget constraints.
|
|
|
| To succeed they need three things: |
To
know the “enterprise legacy”
When
we deal with complex things, change
starts with their description. Builders
would not undertake the construction
of a building without
its architecture documented in various
blueprints, defining the structure
of the components, their interrelationships,
and the principles and guidelines governing
their design.
Are Business and Information
System Building so simple they don’t
need such help? Don’t we need
to develop an architecture of the enterprise? |
To
align IT with Business Goals, corporate
and regulatory requirements.
The organization
must evolve in the right way at the
first time. Business strategic goals
and regulatory requirements must drive
the changes in the organization and
the IT System to maximize business return
across all investments and project.
Business and IT decisions must not be
made in isolation. |
To
know the dependencies between processes
and systems
Due to
its complexity, it can be hard to know
the business impacts of changing IT.
Similarly, it is difficult to know how
IT should react to change in Business.
Getting such decisions wrong can prove
costly. |
|
Enterprise Architecture is a way to facilitate
theses three cornerstones. Indeed, it represents
a snapshot of where the organization is today,
where it wants to go in the future and the
roadmap to reach it. EA is a blueprint driven
by the strategic goals of the enterprise to
support the Business. |
| |
| An
enterprise Architecture defines: |
| |
 |
A set of components
(People, Processes, Application, Server,
Information…) describing the Business,
Application and Technology Architectures. |
| |
|
A series of diagrams
that illustrates how the whole organization
is structured and how all of these components
interrelate |
|
| |
| Framework
and Enterprise Architecture |
|
Enterprise
Architecture generates a lot of objects to
manage like components (People, Processes,
Application, Server, Information…) and
models.
We need a library, a table of classification
to facilitate access to relevant models. A
framework is such a tool. It is used to break
down and categorize the various parts of the
architecture.
The most well known of these is the Zachman
Framework |
| |
| Framework
example: |
| |
|
Zachman Framework
for Enterprise Architecture |
| |
|
TOGAF - The Open
Group Architecture Framework |
| |
|
DoDAF - US Department
of Defense Architecture Framework (C4ISR) |
| |
|
FEAF - US Federal
Enterprise Architecture Framework |
|
| |
 |
Discover
the solutions of the major actors
of the Enterprise Architecture
domain. They provide proven solutions
to control your corporate assets,
including human and IT resources,
and increase your ability to drive
change. |
|
|
| |
| |
