Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia

Introduction to the Architecture Development Method (ADM) Key Points Explained What is the ADM cycle? What are the typical sets of steps within a phase? What is the versioning convention used for deliverables? What is the purpose of the supporting guidelines and techniques? What is the difference between guidelines and techniques? What are the key points of the ADM cycle? Why would I need to adapt the ADM to my enterprise? Why does the ADM process need to be governed? What are the major information areas covered by a governance repository? What are the reasons for scoping the architecture activity for my organization? What are the possible dimensions for limiting the scope?

The Architecture Development Cycle

ADM Phases and Objectives

Key Points of the ADM Cycle The TOGAF ADM is iterative. New decisions have to be taken at each iteration: 1. Enterprise coverage 2. Level of detail 3. Time period 4. Architecture asset re-use: — Previous ADM iterations — Other frameworks, system models, industry models,... Decisions taken should be based on competence and/or resource availability, and the value accruing to the enterprise. The ADM does not recommend the scope of activity; this has to be determined by the organization itself. The choice of scope is critical to the success of the architecting effort. The main guideline is to focus on what creates value to the enterprise, and to select horizontal and vertical scope, and project schedules, accordingly. This exercise will be repeated, and future iterations will build on what is being created in the current effort, adding greater width and depth. Where necessary, use of the ADM should be tailored to meet the needs of the organization. This means that some phases may be omitted, modified, or even additional procedures added.

Scoping the Architecture Activity for your Organization

How to Adapt the ADM to your Enterprise There are a number of reasons for wanting to tailor the ADM to the circumstances of an individual enterprise. Some of the reasons are outlined as follows: 1. An important consideration is that the order of the phases in the ADM is to some extent dependent on the maturity of the architecture discipline within the enterprise concerned. For example, if the business case for doing architecture is not well recognized, then creating an Architecture Vision is essential; and a detailed Business Architecture needs to come next to define the business case for the remaining architecture work, and secure the active participation of key stakeholders in that work. 2. The order of phases may also be defined by the business and architecture principles of an enterprise. For example, the business principles may dictate that the enterprise be prepared to adjust its business processes to meet the needs of a packaged solution, so that it can be implemented quickly to enable fast response to market changes. In such a case, the Business Architecture (or at least the completion of it) may well follow completion of the Information Systems Architecture. 3. An enterprise may wish to use or tailor the ADM in conjunction with another enterprise architecture framework that has a defined set of deliverables specific to a particular vertical sector: Government, Defense, e-Business, Telecommunications, etc.

4. The ADM is one of many corporate processes that make up the corporate governance model for an enterprise. The ADM is complementary to, and supportive of, other standard program management processes. The enterprise will tailor the ADM to reflect the relationships with, and dependencies on, the other management processes. 5. The ADM is being mandated for use by a prime or lead contractor in an outsourcing situation, and needs to be tailored to achieve a suitable compromise between the contractor’s existing practices and the contracting enterprise’s requirements. 6. The enterprise is a small-to-medium enterprise, and wishes to use a “cut-down” version of the ADM that is more attuned to the reduced level of resources and system complexity typical of such an environment. 7. The enterprise is very large and complex, comprising many separate but interlinked “enterprises” within an overall collaborative business framework, and the architecture method needs to be adapted to recognize this. Such enterprises usually cannot be treated successfully as a single entity and a more federated approach is required. The ADM process can also be adapted to deal with a number of different use scenarios, including different process styles (e.g., the use of iteration) and also specific specialist architectures (such as security).

The Need for Architecture Governance The major information areas managed by a governance repository should contain the following types of information: Reference Data (collateral from the organization’s own repositories/Enterprise Continuum, including external data; e.g., COBIT, ITIL): Used for guidance and instruction during project implementation. This includes the details of information outlined above. The reference data includes a description of the governance procedures themselves. Process Status: A record of all information regarding the state of any governance processes; examples of this include outstanding compliance requests, dispensation requests, and compliance assessment investigations. Audit Information: A record of all completed governance process actions. This is used to support: — Key decisions and responsible personnel for any architecture project that has been sanctioned by the governance process — A reference for future architectural and supporting process developments, guidance, and precedence

Integrating the Architecture Domains for your Organization There is a need to integrate the architecture domains identified by the phases of the ADM. This can be done by using an “enterprise framework” such as the TOGAF Architecture Content Framework to position the various domains and artifacts, or by using a meta-architecture framework (i.e., principles, models, and standards) to allow interoperability, migration, and conformance between federated architectures. The purpose of this meta-architecture framework is to: Allow the architect to understand how components fit into the framework Derive the architectural models that focus on enterprise-level capabilities Define the conformance standards that enable the integration of components for maximum leverage and re-use

The ADM - Summary It defines a recommended sequence for the various phases and steps involved in developing an architecture. It is an iterative method. A number of inputs and outputs are recommended for each phase. It draws on other parts of TOGAF for assets and processes. The ADM can be used with other deliverables from other frameworks. The ADM does not recommend a scope; this has to be determined by the organization itself. The choice of scope is critical to the success of the architecting effort. The main guideline is to focus on what creates value to the enterprise, and to select horizontal and vertical scope, and project schedules, accordingly. This exercise will be repeated, and future iterations will build on what is being created in the current effort, adding greater width and depth. Where necessary, use of the ADM should be tailored to meet the needs of the organization. This means that some phases may be omitted, modified, or even additional procedures added.

Test Yourself Questions Q1: Complete the sentence: Phase H ___________________ A. Prepares the organization for successful TOGAF architecture projects B. Develops Baseline and Target Architectures and analyzes the gaps C. Prepares and issues Architecture Contracts D. Ensures that the architecture responds to the needs of the enterprise E. All of these Q2: Which of the following is typically the final step in development of the Business Architecture in Phase B? A. Conduct formal stakeholder review B. Create Architecture Definition Document C. Perform gap analysis D. Select reference models, viewpoints, and tools Q3: Which one of the following does not complete the sentence: When executing the ADM, the architect is not only developing a snapshot of the enterprise, but is also populating the __________________ A. Architecture Repository B. Architecture Capability Framework C. Enterprise Continuum D. Foundation Architecture

Recommended Reading Foundation Study Guide of TOGAF Version - 9 Chapter - 05 ( Complete ) Provided as a.pdf document