Preliminary Phase

1. Preliminary Phase

2. Preliminary Phase - Objectives • Determine the Architecture Capability desired by the organization: • Identify and scope the elements of the enterprise organizations • Identify frameworks, methods, and processes • Establish a Capability Maturity target • Establish the Architecture Capability: • Define and establish the Organizational Model for Enterprise Architecture • Define and establish the detailed processes and resources for architecture governance • Select and implement tools that support the Architecture Capability • Define the Architecture Principles

3. Preliminary Phase - Approach • Defining the enterprise • Identifying key drivers and elements in the organizational context • Defining the requirements for architecture work • Defining the Architecture principles that will inform any architecture work • Defining the framework to be used • Evaluating the enterprise architecture maturity

4. Preliminary Phase – Main Inputs • Togaf • Other architecture frameworks • Business strategy, IT strategy • Business principles, business goals, and business drivers • Governance and legal frameworks, including architecture governance strategy, when pre-existing • Partnership and contract agreements

5. Preliminary Phase – Steps Scope the impacted Enterprise Organizations Confirm Governance and Frameworks Define and Establish Enterprise Architecture Team and Organization Identify Architecture Principles Tailor TOGAF and, if any, Other Selected Architecture Framework(s) Implement Architecture Tools

6. Step 1: Scope the impacted Enterprise Organizations • Identify core enterprise (units) • Identify soft enterprise (units) • Identify extended enterprise (units) • Identify communities involved (enterprises) - stakeholders • Identify governance involved

7. Step 2: Confirm Governance and Frameworks • Existing governance and support models of an organization will need to change to support the newly adopted architecture framework. • Sponsors and stakeholders for architecture will need to be consulted on potential impacts that could occur. • Upon completion of this step, the architecture touch-points and likely impacts should be understood and agreed by relevant stakeholders.

8. Step 3: Define and Establish Enterprise Architecture Team and Organization • Determine existing enterprise and business capability • Identify gaps in existing work areas • Define requests for change to existing business programs and projects: • Determine constraints on enterprise architecture work • Review and agree with sponsors and board • Assess budget requirements

9. Step 4: Identify Architecture Principles • Principle 1: Primacy of Principles • Statement: These principles of information management apply to all organizations within the enterprise. • Rationale: The only way we can provide a consistent and measurable level of quality information to decision-makers is if all organizations abide by the principles.

10. Step 4: Identify Architecture Principles • Principle 2: Maximize Benefit to the Enterprise • Statement: Information management decisions are made to provide maximum benefit to the enterprise as a whole. • Rationale:This principle embodies "service above self". Decisions made from an enterprise-wide perspective have greater long-term value than decisions made from any particular organizational perspective.

11. Step 4: Identify Architecture Principles • Principle 3: Common Use Applications • Statement: Development of applications used across the enterprise is preferred over the development of similar or duplicative applications which are only provided to a particular organization. • Rationale: Duplicative capability is expensive and proliferates conflicting data.

12. Step 4: Identify Architecture Principles • Principle 4: Data is Shared • Statement: Users have access to the data necessary to perform their duties; therefore, data is shared across enterprise functions and organizations. • Rationale: Timely access to accurate data is essential to improving the quality and efficiency of enterprise decision-making. It is less costly to maintain timely, accurate data in a single application, and then share it, than it is to maintain duplicative data in multiple applications

13. Step 5: Tailor TOGAF and, if any, Other Selected Architecture Framework(s) • Terminology Tailoring: produce an agreed terminology set for description of architectural content. • Process Tailoring: remove tasks that are already carried out elsewhere in the organization, align the ADM processes to external process frameworks and touch-points.

14. Step 6: Implement Architecture Tools • With an understanding of the desired approach to architecture, it is possible to select appropriate architecture tools to underpin the architecture function.

15. Preliminary Phase – Outputs • Organizational Model for Enterprise Architecture • Tailored Architecture Framework including architecture principles • Initial Architecture Repository • Restatement of business principles, goals, and drivers • Request for Architecture Work  • Architecture Governance Framework

16. Phase A: Architecture Vision

17. Phase A : Architecture Vision – Objectives • Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed enterprise architecture • Obtain approval for a Statement of Architecture Work that defines a program of works to develop and deploy the architecture outlined in the Architecture Vision

18. Phase A : Architecture Vision – Approach • Phase A defines what is in and what is outside the scope of the architecture effort and the constraints that must be dealt with. • Create the architecture vision document • Clarifying and agreeing the purpose of architecture • Demonstrating how it will be achieved • A first-cut, high-level description of the Baseline and Target Architectures • The business scenarios technique can be used to develop the architecture vision

19. Phase A : Architecture Vision – Approach Business scenarios are an appropriate and useful technique to discover and document business requirements, and to articulate an Architecture Vision that responds to those requirements.

20. Phase A : Architecture Vision – Inputs • Request for Architecture Work • Business principles, goals, and drivers • Organizational Model for Enterprise Architecture • Tailored Architecture Framework including architecture principles • Populated Architecture Repository

21. Phase A : Architecture Vision – Steps Establishthe Architecture Project Identify Stakeholders, Concerns, and Business Requirements Confirm business goals, drivers, and constraints Evaluate business capabilities Assess readiness for business transformation Define Scope

22. Phase A : Architecture Vision – Steps 7. Confirm and Elaborate Architecture Principles, including Business Principles 8. Develop Architecture Vision 9. Define the Target Architecture Value Proposal 10. Identify the Business Transformation Risks and Mitigation Activities 11. Develop Statement of Architecture Work; Secure Approval

23. Step 1: Establish the Architecture Project • Conduct the necessary procedures to secure recognition of the project, the endorsement of corporate management. • Include references to other management frameworks in use within the enterprise, explaining how this project relates to those frameworks.

24. Step 2:Identify Stakeholders, Concerns, and Business Requirements Here we must identify: • Stakeholder concerns, issues, and cultural factors • The concerns and viewpoints that are relevant to this project • The stakeholders that are involved with the project • The key roles and responsibilities within the project

25. Step 3: Confirm business goals, drivers, and constraints • Identify the business goals and strategic drivers of the organization. • If these have already been defined elsewhere within the enterprise, ensure that the existing definitions are current, and clarify any areas of ambiguity. • Define the constraints that must be dealt with, (time, schedule, resources, etc.).

26. Step 4: Evaluate Business Capabilities • Understand the capabilities and desires of the enterprise at an appropriate level of abstraction • Consideration of the gap between the baseline and target capability of the enterprise is critical. • The results of the assessment are documented in a Capability Assessment

27. Step 5: Assess readiness for business transformation • This assessment is based upon the determination and analysis/rating of a series of readiness factors • These results are then used to shape the scope of the architecture, to identify activities required within the architecture project, and to identify risk areas to be addressed.

28. Step 6: Define Scope Define: • what is inside and what is outside the scope of the Baseline Architecture and Target Architecture efforts • The level of detail required • The specific architecture domains to be covered (business, data, application, technology) • Schedule project milestones • Assets created in previous iterations of the ADM cycle within the enterprise • Existing reference frameworks, systems models, and so on.

29. Step 7: Confirm and Elaborate Architecture Principles, including Business Principles • Ensure that the existing definitions are current, and clarify any areas of ambiguity. • If principles do not exist , go back to the body responsible for architecture governance and together define the principles • Secure their endorsement by management.

30. Step 8: Develop Architecture Vision • Informal techniques are often used e.g. a simple solution concept diagram that illustrates the main components of the solution and its advantages • Business scenarios are an appropriate and useful technique to discover and document business requirements, • This step generates the first, very high-level definitions of the baseline and target environments, from a business, information systems, and technology perspective. • This should be stored in the Architecture Repository,

31. Step 9: Define the Target Architecture Value Proposal • Produce the value proposition for each of the stakeholder groupings • Assess and define the procurement requirements • Assess the business risk • Incorporate the output in the Statement of Architecture Work

32. Step 10: Identify the Business Transformation Risks and Mitigation Activities • Identify the risks associated with the Architecture Vision and assess the initial level of risk (e.g., catastrophic, critical, marginal, or negligible) and the potential frequency associated with it. • Assign a mitigation strategy for each risk. • Risk mitigation activities should be considered for inclusion within the Statement of Architecture Work.

33. Step 11: Develop Statement of Architecture Work; Secure Approval • Identify new work products that will need to be changed and the impact of change on other work products • Provide direction on which existing work products, including building blocks, will need to be changed • Estimate the resources needed, develop a roadmap and schedule for the proposed development, and document all these in the Statement of Architecture Work • Develop the specific enterprise architecture Communications Plan • Gain sponsor's sign-off to proceed

34. Phase A : Architecture Vision – Outputs • Approved Statement of Architecture Work • Project description and scope • Overview of architecture vision • Project plan and schedule • Refined statements of business goals, principles, and drivers. • Architecture principles including business principles

35. Phase A : Architecture Vision – Outputs • Capability Assessment • Tailored Architecture Framework Architecture Vision • Architecture Vision • Draft Architecture Definition Document, • Communications Plan

36. Phase B: Business Architecture

37. Phase B : Business Architecture - Objectives Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals, respond to the strategic drivers set out in the Architecture Vision, and addresses the Request for Architecture Work and stakeholder concerns Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Business Architectures

38. Phase B : Business Architecture - Approach • A knowledge of the Business Architecture is a prerequisite for architecture work in any other domain (Data, Application, Technology) • and is therefore the first architecture activity that needs to be undertaken • The Business strategy defines what to achieve • Business Architecture describes how to achieve it • This phase is often required to demonstrate business value of subsequent work to stakeholders

39. Phase B : Business Architecture - Approach • Scope depends on existing strategy and planning • If there is no existing strategy or planning: • Identify any existing architecture definitions, then verify and update • New process definitions may require detailed work • In both cases, use business scenarios to identify key business objectives and processes

40. Phase B : Business Architecture - Inputs • Request for Architecture Work • Refined statements of Business principles, goals, and drivers • Capability Assessment • Organizational Model for Enterprise Architecture • Tailored Architecture Framework

41. Phase B : Business Architecture - Inputs • Approved Statement of Architecture Work • Architecture principles • Architecture Repository  • Architecture Vision • Draft Architecture Definition Document

42. Phase B : Business Architecture - Steps • Select Reference Models, Viewpoints, and Tools • Develop Baseline Business Architecture Description • Develop Target Business Architecture Description • Perform Gap Analysis • Define Candidate Roadmap Components

43. Phase B : Business Architecture - Steps 6. Resolve Impacts Across the Architecture Landscape 7. Conduct Formal Stakeholder Review 8. Finalize the Business Architecture 9. Create Architecture Definition Document

44. Step 1: Select Reference Models, Viewpoints, and Tools • Select relevant Business Architecture resources from the Architecture Repository • Select relevant Business Architecture viewpoints that will enable the architect to demonstrate how the stakeholder concerns are being addressed • Identify appropriate tools and techniques to be used for capture, modeling, and analysis with the viewpoins.

45. Step 1: Select Reference Models, Viewpoints, and Tools • Identify Required Catalogs of Business Building Blocks • Identify Required Matrices • Matrices show the core relationships between related model entities. •  Identify Required Diagrams • Diagrams present the businessArchitecture information from a set of different viewpoints •  Identify Types of Requirement to be Collected • identify requirements that should be met by the architecture

47. Step 2: Develop Baseline Business Architecture Description • Must be complete, but without unnecessary details • If possible, identify the relevant Business Architecture building blocks, drawing on the Architecture Repository • If not, develop a new architecture description: • use the models identified within Step 1 as a guideline

48. Step 3: Develop Target Business Architecture Description • If possible, identify the relevant Business Architecture building blocks, drawing on the Architecture Repository • If not, develop a new architecture description: • use the models identified within Step 1 as a guideline

49. Step 4: Perform Gap Analysis • Highlight the services and/or functions between the Baseline Architecture and the Target Architecture that have been omitted, or yet to be developed

50. Gap Analysis Example