Steven Spewak methodology for EA

Explore The Enterprise Architecture Toolkit

Steven Spewak's Enterprise Architecture Planning (EAP) is a set of methods for planning the development of information, applications, and technology architectures (the recommended approach being to develop them in that order), and for aligning the three types of architecture with respect to each other. The goal is to ensure that such architectures form the blueprints for sound, implementable systems that solve real business problems.

The overall EAP methodology involves the following "steps":

Planning Initiation: Defining scope, objectives, roles and responsibilities, and deciding which methodology to use, who should be involved, and what toolset to use. This leads to producing a workplan for the Enterprise Architecture Planning activity and securing management commitment to go through all of the following phases.

Principles: Developing the core principles to support the effective governance of information and technology. These principles form the basis for making architectural decisions, accepting the results, and managing the migration. They are based on industry best practice and the enterprise’s purpose, vision and values, and are implemented through policies, procedures, and standards.

Business Modeling: Modeling the current business activities and the information used, and identifying business process improvement opportunities.

Current Systems & Technology: Defining what is in place today for application systems and supporting technology platforms. This is a summary-level inventory of application systems, data, and technology platforms to provide a baseline for long-range migration plans.

Data Architecture: Developing the data architecture, including defining the major business activities and data objects needed to support the business.

Applications Architecture: Defining the major kinds of applications needed to manage the data and support the business functions.

Technology Architecture: Defines the platforms needed to provide a technological infrastructure for the applications that manage the data and support the business functions.

Implementation/Migration Plans: Defines the sequence for implementing applications, a schedule for implementation, a cost/benefit analysis, and a clear step-by-step path for migration. Executive-level recommendations are made for implementing the plan, and a plan is developed for the transition period after following the Enterprise Architecture Planning activity.

Planning Conclusion: Final report and presentation of the results to management.

The EAP methodology thus positions the four types of "architecture" in the sequence: Business Architecture, Data Architecture, Applications Architecture, and IT (or Technology) Architecture as the recommended sequence.

Enterprise Architecture Toolkit: the definitive resource for Enterprise Architecture projects