Enterprise Architecture Phases
EA is mainly about defining a target architecture, and planning how to establish it. In order to get there, there
are a number of phases you need to go through. You also need to execute these iteratively, because you need
to adapt to internal or external changes, and you want your models to always give a realistic
view of the organization's processes, information, services, applications and technology.
Each phase uses the wheel of architecture perspectives, described to the left, to guide the scenario-based analysis.
quality criteria definition
Defining what characterizes "good" architecture. F.ex. with respect to data quality, level of process automation,
separation of concerns, standardization etc. The criteria are based on business and IT goals.
Describing today's architecture, f.ex. which processes constitutes the business, which information flows currently through
the processes, how is data mastered across the application landscape, how are typical integration scenarios solved etc.
The as-is architecture is then evaluated against the quality criteria.
The business strategy, the IT strategy, the quality criteria and an the evaluation of the as-is architecture, all give
input to a vision of which architecture may bring the enterprise closer to its goals. The definition of architecture
principles for business, information, application, integration, service, security and technology architecture set the
direction for the next phases.
The target enterprise architecture iteratively focus on the best candidates for improvement, within business processes,
how applications are used across the business, how information is shared and how the processes, information and services
are supported by technology. Different scenarios, combining the various architecture perspectives, are evaluated, and
the phase ends up in a consolidated target architecture.
The target architecture is evaluated against the same criteria as the as-is architecture was. This is the basis for
evaluating the business impacts from the changes implied by the target architecture.
This is about defining the tasks required to get from the as-is state to the target state, and which stable transition
states the organization can reach on its way to an established target architecture.
A complete and realistic set of tasks/projects, like establishing service oriented architecture, establishing platforms, acquiring applications,
improving business processes and improving the masterdata manaagement. These tasks/projects will lead the enterprise
through a set of transition architectures, all the way to the target architecture.
Improve the routines, organizational structures, processes and frameworks for the coming phases of EA evolution.