Manage Enterprise Architecture

Purpose:

Establish a common architecture consisting of business process, information, data, application and technology architecture layers for effectively and efficiently realizing enterprise and IT strategies by creating key models and practices that describe the baseline and target architectures. Define requirements for taxonomy, standards, guidelines, procedures, templates and tools, and provide a linkage for these components. Improve alignment, increase agility, improve quality of information and generate potential cost savings through initiatives such as re-use of building block components.

Objective:

Represent the different building blocks that make up the enterprise and their inter-relationships as well as the principles guiding their design and evolution over time, enabling a standard, responsive and efficient delivery of operational and strategic objectives.

Description:

<?>

Inputs:

• Guiding principles for Enterprise Architecture
• Strategic Road Map
• Enterprise Operational Guidelines
• Definition of Organizational Structure and Functions
• Defined Operational placement of IT Function
• Evaluation of options for IT Organization
• Data Classification Guidelines
• Proposed Enterprise Architecture Changes

Outputs:

• Define Scope of Architecture
• Architecture Principles
• Architecture Concept Business Case and Value Proposition
• Baseline Domain Descriptions and Architecture Definition
• Process Architecture Model
• Information Architecture Model
• High-level Implementation and Migration Strategy
• Transition Architectures
• Resource Requirements
• Implementation Phase Descriptions
• Architecture Governance Requirements
• Solution Development Guidance

Controls:

• Enterprise Strategy
• Enterprise Drivers

Task Instructions:

Develop the Enterprise Architecture Vision

1. 1. Identify the key stakeholders and their concerns/objectives, and define the key enterprise requirements to be addressed as well as the architecture views to be developed to satisfy the various stakeholder requirements.
   2. Identify the enterprise goals and strategic drivers of the enterprise and define the constraints that must be dealt with, including enterprisewide constraints and project-specific constraints (time, schedule, resources, etc.).
   3. Align architecture objectives with strategic programme priorities.
   4. Understand the capabilities and desires of the business, then identify options to realise those capabilities.
   5. Assess the enterprise’s readiness for change.
   6. Define what is inside and what is outside the scope of the baseline architecture and target architecture efforts, understanding that the baseline and target need not be described at the same level of detail.
   7. Confirm and elaborate architecture principles, including enterprise principles. Ensure that any existing definitions are current and clarify any areas of ambiguity.
   8. Understand the current enterprise strategic goals and objectives and work with the strategic planning process to ensure that IT-related enterprise architecture opportunities are leveraged in the development of the strategic plan.
   9. Based on stakeholder concerns, business capability requirements, scope, constraints and principles, create the architecture vision: a high-level view of the baseline and target architectures.
   10. Define the target architecture value propositions, goals and metrics.
   11. Identify the enterprise change risk associated with the architecture vision, assess the initial level of risk (e.g., critical, marginal or negligible) and develop a mitigation strategy for each significant risk.
   12. Develop an enterprise architecture concept business case, outline plans and statement of architecture work, and secure approval to initiate a project aligned and integrated with enterprise strategy.

Define Reference Architecture

1. 1. Maintain an architecture repository containing standards, reusable components, modeling artifacts, relationships, dependencies, and views to enable uniformity of architectural organization and maintenance.
   2. Select reference viewpoints from the architecture repository that will enable the architect to demonstrate how stakeholder concerns are being addressed in the architecture.
   3. For each viewpoint, select the models needed to support the specific view required, using selected tools or methods and the appropriate level of decomposition.
   4. Develop baseline architectural domain descriptions, using the scope and level of detail necessary to support the target architecture and, to the extent possible, identifying relevant architecture building blocks from the architecture repository.
   5. Maintain a process architecture model as part of the baseline and target domain descriptions. Standardize the descriptions and documentation of processes. Define the roles and responsibilities of the process decision-makers, process owner, process users, process team, and any other process stakeholders who should be involved.
   6. Maintain an information architecture model as part of the baseline and target domain descriptions, consistent with the enterprise’s strategy to enable optimal use of information for decision making. Maintain an enterprise data dictionary that promotes a common understanding and a classification scheme that includes details about data ownership, the definition of appropriate security levels, and data retention and destruction requirements.
   7. Verify the architecture models for internal consistency and accuracy and perform a gap analysis between the baseline and target. Prioritize gaps and define new or modified components that must be developed for the target architecture. Resolve potential impacts such as incompatibilities, inconsistencies, or conflicts within the envisioned architecture.
   8. Conduct a formal stakeholder review by checking the proposed architecture against the original motivation for the architecture project and the statement of architecture work.
   9. Finalize business, information, data, applications, and technology domain architectures, and create an architecture definition document.

Select Opportunities and Solutions

1. 1. Determine and confirm key enterprise change attributes, including the enterprise culture and how this will impact enterprise architecture implementation, as well as the enterprise transition capabilities.

   2. Identify any enterprise drivers that would constrain the sequence of implementation, including a review of the enterprise and line of business strategy and business plans, and consideration of the current enterprise architecture maturity.

   3. Review and consolidate the gap analysis results between the baseline and target architectures and assess their implications with respect to potential solutions/opportunities, interdependencies, and alignment with current IT-enabled programs.

   4. Assess the requirements, gaps, solutions, and factors to identify a minimal set of functional requirements whose integration into work packages would lead to a more efficient and effective implementation of the target architecture.

   5. Reconcile the consolidated requirements with potential solutions.

   6. Refine the initial dependencies, ensuring that any constraints on the implementation and migration plans are identified, and consolidate them into a dependency analysis report.

   7. Confirm the enterprise readiness for and the risk associated with enterprise transformation.

   8. Formulate a high-level implementation and migration strategy that will guide the target architecture implementation and structure the transition architectures in alignment with enterprise strategic objectives and time scales.

   9. Identify and group major work packages into a coherent set of programs and projects, respecting the enterprise strategic implementation direction and approach.

   10. Develop a series of transition architectures as necessary where the scope of change required to realize the target architecture requires an incremental approach.

Define Architecture Implementation

1. 1. Establish what the implementation and migration plan should include as part of the program and project planning and ensure that it is aligned with the requirements of applicable decision-makers.
   2. Confirm transition architecture increments and phases and update the architecture definition document.
   3. Define architecture implementation governance requirements.

Provide Enterprise Architecture Services

1. 1. Confirm scope and priorities and provide guidance for solution development and deployment.

   2. Manage the portfolio of enterprise architecture services to ensure alignment with strategic objectives and solution development.
   3. Manage enterprise architecture requirements and support with architectural principles, models and building blocks.
   4. Identify and align enterprise architecture priorities to value drivers. Define and collect value metrics and measure and communicate enterprise architecture value.
   5. Establish a technology forum to provide architectural guidelines, advice on projects and guidance on the selection of technology. Measure compliance with these standards and guidelines, including compliance with external requirements and their business relevance.