Purposes for Enterprise Architecture

  1. Enterprise Architecture to Support Strategy: Deliver Enterprise Architecture to provide an end-to-end Target Architecture, and develop roadmaps of change over a three to ten-year period.

    An architecture for this purpose will typically span many change programs or portfolios. In this context, architecture is used to identify change initiatives and supporting portfolio and programs. Set terms of reference, identify synergies, and govern the execution of strategy via portfolio and programs.

  2. Enterprise Architecture to Support Portfolio: Deliver Enterprise Architecture to support cross-functional, multi-phase, and multi-project change initiatives.

    An architecture for this purpose will typically span a single portfolio. In this context, architecture is used to identify projects, and set their terms of reference, align their approaches, identify synergies, and govern their execution of projects

  3. Enterprise Architecture to Support Project: Deliver Enterprise Architecture to support the enterprise's project delivery method.

    An architecture for this purpose will typically span a single project. In this context, the architecture is used to clarify the purpose and value of the project, identify requirements to address synergy and future dependency, assure compliance with architectural governance, and to support integration and alignment between projects.

  4. Enterprise Architecture to Support Solution Delivery: Deliver Enterprise Architecture that is used to support the solution deployment.

    An architecture for this purpose will typically be a single project or a significant part of it. In this context, the architecture is used to define how the change will be designed and delivered, identify constraints, controls, and Architecture Requirements to the design, and, finally, act as a governance framework for change