Section 1 - The ADM Flashcards

Question

What is the purpose of phase A - Architecture Vision

Answer 1

1. To Develop a high-level aspirational vision of the business value to be delivered. 2. Obtain approval for a statement of Architecture work

Answer 2

1. Architecture reference materials. 2. Request for Architecture work. 3. Business principles , business goals, and business drivers. 4. Organisational model for Enterprise Architecture 5. Tailored Architecture Framework 6. Populated Architecture Repository

Answer 3

1. Establish architecture project 2. Identify stakeholders, concerns, and business requirements 3. Confirm business goals, drivers and constraints 4. Evaluate capabilities 5. Assess readiness for transformation 6. Define Scope 7. Confirm architecture principles, including business principles 8. Develop architecture vision 9. define the target architecture value and KPIs 10. Identify transformation risks and mitigations activities 11. Develop statement of architecture work. Secure approval

Answer 4

1. Approved statement of Architecture work 2. Refined statements of business principles, goals and drivers 3. Architecture principles 4. Capabilities assessment 5. Tailored architecture framework

Answer 5

Matrices - stakeholder map matrix Diagrams - business model, business capability, value stream map, value chain, solution concept

Answer 6

A succinct description of the Target Architecture that describes its business value and the changes to the enterprise that will result from its successful deployment. It serves as an aspirational vision and a boundary for detailed architecture development.

Answer 7

1. To develop the Target business Architecture 2. Identify candidate Architecture Roadmap items based on gaps.

Answer 8

1. External reference materials 2. Request for Architecture work (optional) (Preliminary phase) 3. Business principles, goals, and drivers (Phase A) 4. Capabilities assessment (Phase A) 5. Communications plan (Phase A) 6. Organisation model for enterprise Architecture (Preliminary phase) 7. Tailored Architecture Framework (Preliminary phase) 8. Approved Statement of Architecture (Phase A) 9. Architecture Principles (Phase A) 10. Enterprise Continuum 11. Architecture Repository 12. Architecture vision (Phase A) 13. Draft Architecture definition document version 0.1 of all baseline and target BDAT documents (Phase A)

Answer 9

1. Select reference models, viewpoints, and tools 2. Develop baseline business architecture description 3. Develop target business architecture description 4. Perform gap analysis 5. Define candidate roadmap components 6. Resolve impact across the architecture landscape - where there are conflicting ideas 7. Conduct formal stakeholders review 8. Finalise business architecture 9. Create architecture definition document

Answer 10

1. Refined Phase A deliverables 2. Draft architecture document a) Baseline business architecture v1.0 (detailed) b) Target business architecture v1.0 (detailed) 3. Draft architecture requirements specification - gap analysis 4. Business architecture components of an architecture roadmap

Answer 11

* Catalogs Value Stream, business capabilities, * Matrices * Diagrams

Answer 12

1. Develop target information systems architectures 2. Identify candidate Architecture Roadmap items based on gaps

Answer 13

1. External reference materials 2. Request for Architecture work (optional) (Preliminary phase) 3. Capabilities assessment (Phase A) 4. Communications plan (Phase A) 5. Organisation model for enterprise Architecture (Preliminary phase) 6. Tailored Architecture Framework (Preliminary phase) 7. Approved Statement of Architecture (TOGAF chapter 20) 8. Approved statement of Architecture work (Phase A) 9. Architecture Vision (Phase A) 10. Architecture Repository 11. Draft architecture documents and draft requirements (Phase B) 12. Business related architecture roadmap (Phase B)

Answer 14

1. Select reference models, viewpoint and tools 2. Develop baseline data architecture description 3. Develop target data architecture description 4. Perform gap analysis 5. Define candidate roadmap components 6. Resolve impact across the architecture landscape 7. Data principles (TOGAF specification chapter 20) 8. Approved statement of Architecture work (Phase a) 9. Architecture vision (Phase A) 10. Architecture Repository 11. Draft architecture documents and draft requirements (Phase B) 12. Business related architecture roadmap (Phase B)

Answer 15

1. Refined Phase A deliverables 2. Draft architecture document a) Baseline business architecture v1.0 b) Target business architecture v1.0 3. Draft architecture requirements specification - gap analysis 4. Data architecture components of an architecture roadmap

Answer 16

* Catalogs Data entity / data component * Matrices Data entity / business function, Application / data * Diagrams Conceptual data, logical data, data dissemination, data security, data migration, data lifecycle

Answer 17

1. External reference materials 2. Request for Architecture work (optional) (Preliminary phase) 3. Capabilities assessment (Phase A) 4. Communications plan (Phase A) 5. Organisation model for enterprise Architecture (Preliminary phase) 6. Tailored Architecture Framework (Preliminary phase) 7. Approved Statement of Architecture (TOGAF chapter 20) 8. Approved statement of Architecture work (Phase A) 9. Architecture Vision (Phase A) 10. Architecture Repository 11. Draft architecture documents and draft requirements (Phase B) 12. Business related architecture roadmap (Phase B)

Answer 18

1. Select reference models, viewpoint and tools 2. Develop baseline data architecture description 3. Develop target data architecture description 4. Perform gap analysis 5. Define candidate roadmap components 6. Resolve impact across the architecture landscape 7. Data principles (TOGAF specification chapter 20) 8. Approved statement of Architecture work (Phase a) 9. Architecture vision (Phase A) 10. Architecture Repository 11. Draft architecture documents and draft requirements (Phase B) 12. Business related architecture roadmap (Phase B)

Answer 19

1. Refined Phase A deliverables 2. Draft architecture document a) Baseline business architecture v1.0 b) Target business architecture v1.0 3. Draft architecture requirements specification - gap analysis 4. Application architecture components of an architecture roadmap

Answer 20

* Catalogs Application, Interface * Matrices Application / organisation, role/application, application function, application interaction * Diagrams Applications communication, Application and user location, Application Use-case, Enterprise Manageability, Process/ Application, Realisation, software engineering, Application Migration, software distribution.

Answer 21

Develop the target technology architecture & Identify candidate architecture roadmaps items based on gaps.

Answer 22

1. External reference materials 2. Product information on candidate products 3. Request for Architecture work (optional) Prelim Phase) 4. Capabilities assessment (Phase A) 5. Communications plan (Phase A) 6. Organisation model for enterprise Architecture (Preliminary phase) 7. Tailored Architecture Framework (Preliminary phase) 8. Technology Principles (TOGAF Specification chapter 20) 9. Approved statement of Architecture work (Phase A) 10. Architecture Vision (Phase A) 11. Architecture Repository 12. Draft architecture documents and draft requirements (Phase B and C) 13. Business, data, and application component of an architecture roadmap (Phase B and C)

Answer 23

1. Select reference models, viewpoint and tools 2. Develop baseline technology architecture description 3. Develop target technology architecture description 4. Perform gap analysis 5. Define candidate roadmap components 6. Resolve impact across the architecture landscape 7. Conduct formal stakeholder review 8. Finalise Technology architecture 9. Create architecture definition document

Answer 24

1. Refined Phase A deliverables 2. Draft architecture document a) Baseline business architecture v1.0 b) Target business architecture v1.0 3. Draft architecture requirements specification - gap analysis 4. Technology architecture components of an architecture roadmap

Answer 25

* Catalogs Technology Standards, Technology Portfolio * Matrices Application / Technology mix * Diagrams Environments and locations, decomposition, Processing, Networked Computing/Hardware Communications Engineering

Answer 26

Generate the initial Architecture Roadmap & Identify if Transition architectures are required by defining Solution Building Blocks (SSBs) Identify if any transition architectures are required

Answer 27

1. External reference materials 2. Product information 3. Request for Architecture work (optional) Prelim Phase) 4. Capabilities assessment (Phase A) 5. Communications plan (Phase A) 6. Planning methodologies 7. Organisation model for enterprise Architecture (Preliminary phase) 8. Tailored Architecture Framework (Preliminary phase) 9. Approved statement of Architecture work (Phase A) 10. Architecture Vision (Phase A) 11. Architecture Repository 12. Draft architecture documents and draft requirements (BDAT) 13. Change requests for existing business programs and projects 14. Candidate architecture roadmap components

Answer 28

1. Determine Key corporate change attributes 2. Determine business constraints 3. Review and consolidate gap analysis from Phases B to D 4. Review consolidated requirements across business functions 5. Consolidate and reconcile interoperability requirements 6. Refine and validate dependencies 7. Confirm readiness and risk for business transformation 8. Formulate implementation and migration strategy 9. Identify transition architectures 10. Identify transition architectures 11. Create the architecture roadmap & implementation and migration plan

Answer 29

1. Refine Phase A deliverables 2. Draft architecture definition document - include baseline and target v1.0 3. Draft architecture requirement specification - include gap analysis 4. Capabilities assessments 5. Architecture roadmap, version 0.1 6. Implementation and migration plan, version 0.1

Answer 30

* Diagrams Product Contect, Benefits

Answer 31

Ensure Migration plan is aligned with enterprise approach to change & Ensure Business value and cost of work package is understood.

Answer 32

1. External reference materials 2. Request for Architecture work (optional) Prelim Phase) 3. Capabilities assessment (Phase A) 4. Communications plan (Phase A) 5. Organisation model for Enterprise Architecture (Preliminary phase) 6. Governance Model and Frameworks 7. Tailored Architecture Framework (Preliminary phase) 8. Approved statement of Architecture work (Phase A) 9. Architecture Vision (Phase A) 10. Architecture Repository 11. Draft architecture documents and draft requirements (BDAT) 12. Change requests for existing business programs and projects 13. Architecture roadmap, version 0.1 (Phase E) 14. Capability Assessment 15. Implementation and migration plan, version 0.1 (Phase E)

Answer 33

1. Confirm management framework interactions 2. Assign a business value to each work package 3. Estimate resource requirements, project timings, etc 4. Prioritise the migration projects 5. Confirm architecture roadmap and update architecture definition document 6. Generate implementation and migration plan 7. Complete the architecture development cycle, lessons learned

Answer 34

1. Implementation and Migration plan version 1.0 2. Finalised architecture definition document 3. Finalised architecture requirements 4. Finalise architecture roadmap 5. Reusable Architecture Building Blocks (ABBs) 6. Request for Architecture Work for next ADM cycle (if any) 7. Implementation of governance model 8. Change requests for architecture capability from lessons learned

Answer 35

To ensure Conformance & Perform architecture Governance

Answer 36

1. External reference materials 2. Request for Architecture work (optional) Prelim Phase) 3. Capabilities assessment (Phase A) 4. Organisation model for Enterprise Architecture (Preliminary phase) 5. Tailored Architecture Framework (Preliminary phase) 6. Approved statement of Architecture work (Phase A) 7. Architecture Vision (Phase A) 8. Architecture Repository 9. Architecture definition document and requirements (BDAT) 10. Architecture roadmap, version 1.0 (Phase F) 11. Implementation governance model 12. Architecture contract 13. Request for architecture work for next ADM cycle (phase F) 14. Implementation and migrations plan , version 1.0 (Phase F)

Answer 37

1. Confirm scope and priorities for development 2. Identify Deployment resources and skills 3. Guide Development of Solutions Deployment 4. Perform Enterprise Architecture Compliance Reviews 5. Implement Business and IT Operations 6. Perform Post-Implementation Review and Close the implementation

Answer 38

1. Architecture contract “.. joint agreements between development partners and sponsors on the deliverables, quality , and fitness for purpose of an architecture” Read Chapter 43 of the TOGAF 9.2 specification 2. Compliance assessments 3. Change requests 4. Architecture-compliant solutions deployed

Answer 39

Develop the target business architecture in line with the business goals and the vision defined in the preliminary phase

Answer 40

The standard does not recommend an order. you can do them in either order.

Answer 41

Software Engineering diagram plus others

Answer 42

The approved and signed off version.

Answer 43

1. Maintain Architecture lifecycle includes Execute architecture governance 2. Maintain Architecture Capability

Answer 44

1. External reference materials 2. Request for Architecture work (optional) Prelim Phase) 3. Organisation model for Enterprise Architecture (Preliminary phase) 4. Tailored Architecture Framework (Preliminary phase) 5. Statement of Architecture work (Phase A) 6. Architecture Vision (Phase A) 7. Architecture Repository 8. Architecture definition document and requirements (BDAT) 9. Architecture roadmap, version 1.0 (Phase F) 10. Change requests - Technology changes, business changes, lessons learned 11. Implementation governance model 12. Architecture contract (Phase G) 13. Compliance assessments (Phase G) 14. Implementation and migrations plan , version 1.0 (Phase F)

Answer 45

1. Establish value realisation model - Has the value been realised? 2. Deploy monitoring tools 3. Managing Risks 4. Provide analysis for architecture change management 5. Develop change requirements to meet performance targets 6. Manage Governance process 7. Activate the process to implement change

Answer 46

1. Architecture updates (Maintenance) 2. Change to architecture framework and principles (maintenance) 3. New request for architecture work (for major changes) 4. Statement of architecture work (update if necessary) 5. Architecture contract (update if necessary) 6. Compliance assessments (update if necessary) 7. Does a proposed change require a new ADM cycle? (or can it be done as a request as part of change management?)

Answer 47

Technically it is the Tenth Phase, but it is constant process throughout the ADM cycle. Used to monitor flow Used to handle change during any phase of the ADM process.

Answer 48

Ensure the process is sustained through all phases Manage change while the ADM cycle is in progress Provide the requirements to each ADM phase Manages “Flow” of requirements Manages the repository

Answer 49

It's a contract between the implementation team and the architecture team that the architecture work that has been defined will be implemented as defined, and that the architecture governance process will be followed for any changes.

Answer 50

To ensure that the work being delivered conforms to the architecture as it's defined.

Answer 51

Architecture Design Method is the process which an architecture is defined.

Answer 52

1. To Develop a high-level aspirational vision of the business value to be delivered. 2. Obtain approval for a statement of Architecture work

Answer 53

A difference between the baseline and target architectures. In the context of the TOGAF 10 ADM, a "gap" refers to a difference or discrepancy between the existing (baseline) architecture and the desired (target) architecture. Gap Analysis is a technique for identifying what needs to change in terms of components, processes, and other factors to move from the current state to the desired future state. "A missing software tool or application within the enterprise's IT landscape" is incorrect because, while missing tools or applications might be discovered as a result of a Gap Analysis, they do not define what a gap is. "The lack of alignment between the business and IT strategies" is a broader strategic concern that might lead to an architectural gap, but it doesn't define a gap within the context of the ADM. "An architectural decision that hasn't been approved by stakeholders" is unrelated to the concept of a gap in this context; it deals more with architectural governance and stakeholder approval.

Answer 54

Phase B In the TOGAF 10 framework, the Baseline and Target Business Architectures are developed during "Phase B: Business Architecture". This phase focuses on describing the existing business architecture (baseline) and establishing the future business architecture (target) that the organization aims to achieve. The goal is to represent organizational, functional, process, information, and other related architectures in both current and desired future states. While Phase A (Architecture Vision) sets the high-level strategic context, it is in Phase B where the detailed business architectures are defined. The other options do not specifically focus on the detailed development of business architectures.

Answer 55

A potentially re-usable component that can be combined with other building blocks to deliver architectures and solutions. In the TOGAF 10 framework, a "Building Block" represents a potentially re-usable component (whether functional, technical, or organizational) that can be combined with other building blocks to form complete architectures or solutions. "A complete solution for enterprise architecture requirements" describes a result, but not the fundamental nature of a building block. "A standalone unit that doesn't interact with other components" is incorrect as building blocks are designed to interact with others to form a complete system or solution. "The process of defining and documenting the structure, organization, and implementation of architectural components" describes the process of architecture work, not the definition of a building block. Among the choices, only "A potentially re-usable component that can be combined with other building blocks to deliver architectures and solutions" accurately captures the essence of what a building block represents within the TOGAF framework.

Answer 56

The practice of monitoring and directing architecture activities to ensure alignment with business objectives. Architecture governance in the TOGAF 10 context refers to the overarching practice of overseeing, directing, and ensuring that architectural initiatives and activities are in alignment with the organization's business objectives and strategies. It encompasses principles, practices, roles, responsibilities, and processes that ensure the effective and efficient use of architecture resources in achieving desired outcomes. "The structure and hierarchy of roles within an architectural team" is not correct because it focuses on roles, not on the overall monitoring and guiding function of governance. "The software and tools used in the architectural development process" is off the mark as it emphasizes tools rather than governance processes. "The blueprint or design of an organization's technology systems", while related to architectural work, is not governance itself but rather a product of architectural efforts.

Answer 57

Phase A In the TOGAF 10 framework, the "Draft Architecture Definition Document" is created during "Phase A: Architecture Vision". This document provides a description of the new architecture as a series of views addressing stakeholder concerns, thus capturing both the baseline (current) and target (desired) architectural states. Phase A focuses on creating the high-level vision of the capabilities and business value to be delivered as a result of the proposed enterprise architecture. The other phases further refine or implement parts of the architecture, but it is Phase A where the initial draft of the Architecture Definition Document is established.

Answer 58

Head of the IT Department Phase D of the ADM in TOGAF 10 pertains to the Technology Architecture. This phase aims to map out and define the technology infrastructure, platforms, and software necessary to support the enterprise's architecture. It entails designing the hardware, software, and network solutions to meet the application and data requirements of the organization. As a result, the Head of the IT Department would have a significant interest in the outputs of this phase, as they are responsible for overseeing the technology infrastructure, its acquisition, and its effective deployment. While the other options – Chief Marketing Officer, Head of Human Resources, and Chief Financial Officer – would have some interest in various aspects of the enterprise's architecture, they would not be as directly concerned with the technical details laid out in Phase D as the Head of the IT Department would be.

Answer 59

Phase C In the TOGAF 10 framework, "Phase C" encompasses both Data Architecture and Application Architecture. When focusing on Application Architecture, the primary objective is to establish a blueprint for the individual application systems to be deployed, the interactions between application systems, and their relationships to the core business processes of the organization. "Phase A" provides the overarching architecture vision, "Phase B" concentrates on Business Architecture, and the "Preliminary Phase" sets the groundwork for the architecture development effort. Among the provided choices, only "Phase C" specifically addresses the development and description of the Application Architecture.

Answer 60

Iteration Iteration refers to the practice of repeating certain phases or activities within the ADM to refine and detail the architecture as it evolves. In this case, organizations are taking an iterative approach to Phases B-D to gain a broader, high-level perspective before diving deeper into the specifics during the next pass. Iteration ensures that architects can adapt to changes or additional information, making the final architecture more aligned with the requirements. The other options, segmentation, diversification, and modularization, do not accurately describe the practice of revisiting phases for refinement and depth.

Answer 61

Phase C In the TOGAF 10 framework, "Phase C" is split into two parts: Data Architecture and Application Architecture. When focusing on Data Architecture, the primary objective is to define the data structures, relationships, and their specifications. This includes understanding the data assets of the organization, their relationships, and the associated data standards and principles. "Phase A" provides the overarching architecture vision, "Phase B" is dedicated to Business Architecture, and the "Preliminary Phase" prepares the organization to undertake architecture development. Among these options, only "Phase C" zeroes in on defining data architectures and its related components.

Answer 62

Artifact In the TOGAF 10 framework, an "Artifact" is an architectural work product that describes an aspect of the architecture. Artifacts represent specific pieces of information that are produced, consumed, or utilized during the architectural process. "Transition Architecture", represents a state of the architecture at a significant milestone. "Viewpoint", is the specification of the conventions for constructing and using a view. It provides the template from which a view can be developed. "Stakeholder", refers to individuals or entities that have interests in, or concerns relative to, the outcome of the architecture. Among these choices, only "Artifact" correctly identifies an architectural work product that captures and documents an aspect of the architecture.

Answer 63

Transition Architecture In the TOGAF 10 framework, "Transition Architecture" describes the architecture of a solution at an interim, architecturally significant milestone as the enterprise progresses from the Baseline Architecture to the Target Architecture. It provides a clear view and roadmap of the architectural landscape's evolution. "Baseline Architecture", describes the current state of the architecture. "Target Architecture", represents the desired or future state of the architecture. "Architecture Vision", is the high-level, aspirational view of the end architecture product. Among the given options, only the Transition Architecture captures the description of the architecture at a specific, significant point during its evolution towards the desired future state.

Answer 64

`Phase F In the TOGAF 10 framework, "Phase F" relates to Migration Planning. This phase primarily focuses on crafting detailed plans that guide the enterprise through the implementation of the Target Architecture. The Migration Plan is developed in this phase, detailing the projects, their dependencies, and timelines required to achieve the full transformation. While "Phase E" identifies opportunities and solutions for transitioning, "Phase G" deals with implementation governance, and "Phase H" is concerned with architecture change management. Among the choices, only "Phase F" emphasizes the detailed planning for the transition from the Baseline to the Target Architectures.

Answer 65

Phase A Phase A, known as "Architecture Vision" in TOGAF, is the correct answer. This phase is the initial phase of the TOGAF ADM and is specifically dedicated to creating an initial architectural vision that outlines the high-level scope, objectives, and stakeholders' concerns for the architecture project. It plays a crucial role in obtaining stakeholder buy-in and ensuring that all stakeholders have a common understanding of the architecture project's goals and objectives. Phases B, C, and D represent different phases in the TOGAF ADM, but they do not focus on the creation of the initial architecture vision and stakeholder buy-in, making them incorrect answers for this question.

Answer 66

Requirements Management Phase In the TOGAF 10 framework, the "Requirements Management Phase" acts as a central hub that governs the flow of requirements to and from the various phases of the ADM. It ensures that the architecture remains consistently aligned with business needs throughout its lifecycle. The phase manages and addresses requirements as they are identified, throughout the architecture development cycle. While other phases such as "Phase A", "Phase H", and "Phase F" have important roles in the ADM process, it is the Requirements Management Phase that is specifically dedicated to overseeing and managing requirements in a holistic manner.

Answer 67

Any collection of organizations that share a common set of goals. In the context of TOGAF 10, an "enterprise" is broadly defined as any collection of organizations that share a common set of goals. This could be a single organization or a cross-section of multiple organizations. The emphasis is on the shared objectives rather than the size or nature of the entity. "A large multinational corporation with thousands of employees" is incorrect as an enterprise does not necessarily have to be large or multinational. "A formal structure with a primary goal of producing profits for its shareholders" is overly narrow, as enterprises can have various goals beyond profit-making. "A technological infrastructure that supports business operations" misconstrues the term "enterprise" by focusing on the technological aspect rather than the collective organizational goals.

Answer 68

Phase C The "Phase C: Application Architecture" of the ADM specifically addresses the development of the Application Architecture for an organization, including the identification and articulation of key application components and their relationships. An Application Use-Case Diagram is a type of artifact that showcases how different application components interact or are used to achieve specific functions or tasks. This makes it highly relevant to Phase C, which is about defining applications and their interactions. Phase A focuses on the Architecture Vision, Phase B is dedicated to Business Architecture, and Phase D centers on Technology Architecture. Consequently, among the options provided, only Phase C would typically involve the creation of an Application Use-Case Diagram as part of its architectural artifacts.

Answer 69

A classification scheme for architecture assets. The Enterprise Continuum in TOGAF 10 provides a classification scheme for categorizing and storing architecture and solution assets. It serves as a valuable tool for developing architectures across an organization by helping architects understand where and how specific assets fit within a broader architectural context. "A repository for storing architecture artifacts" is incorrect because the Enterprise Continuum is not a repository but a classification model; the Architecture Repository is where artifacts are stored. "A lifecycle method for developing architectures" is incorrect as this describes the Architecture Development Method (ADM), not the Enterprise Continuum. "A set of predefined architecture patterns" is not entirely accurate because while the continuum does include patterns, it's not merely a set of predefined patterns; it's a broader classification scheme.

Answer 70

View In the TOGAF 10 framework, a "View" is defined as a representation of a system from the perspective of a related set of concerns. It's essentially what you see when you look at a system from a particular viewpoint. "Viewpoint", is the specification of the conventions for constructing and using a view. It defines the perspective and the concerns addressed, but is not the representation itself. "Stakeholder", refers to an individual, team, or organization (or classes thereof) with interests in, or concerns relative to, the outcome of the architecture. "Artifact", is a more general term representing a tangible output of the architectural work, which might be a document, model, or other specific form of output. Among these options, only "View" accurately captures the representation of the system based on a set of concerns.

Answer 71

Phase A In the TOGAF 10 framework, "Phase A" is titled "Architecture Vision." This phase is primarily concerned with the creation of the Statement of Architecture Work, which captures the scope, approach, and content of the architecture activities being undertaken. A crucial step within this phase is obtaining the necessary approvals to commence further work based on this statement. In contrast, the "Preliminary Phase" focuses on establishing the architecture capability, "Phase B" is about developing the business architecture, and "Phase D" deals with the technology architecture. Among the options, only "Phase A" specifically aims at obtaining approval for the Statement of Architecture Work.

Answer 72

A tailored CRM system for ABC Corp's unique processes The Architecture Continuum in TOGAF is divided into categories that range from foundational to specific. The "organization-specific" category encompasses architectures tailored to a particular organization's unique needs and context. A tailored CRM system for ABC Corp's unique processes falls under this category, as it is specifically designed for that organization's operations. In contrast, general industry best practices, generic security protocols, and standardized infrastructure components are more generic and would fit earlier in the continuum, being relevant to a broader range of organizations.

Answer 73

Providing a detailed step-by-step approach for developing an enterprise architecture. The TOGAF Architecture Development Method (ADM) serves as the core of TOGAF. Its primary objective is to provide a detailed, step-by-step approach for developing an enterprise architecture, ensuring that all aspects of the enterprise are addressed and integrated into a holistic view. "Defining a long-term IT strategy for an organization", while somewhat related, is too narrow in its focus on IT and does not encompass the breadth and depth of enterprise architecture as defined by TOGAF. "Implementing agile development processes within an organization" is incorrect because the ADM is not specifically about agile development processes; it's about the overall development of an enterprise architecture. "Designing the interface layouts for software applications" is off-topic; interface layouts for software applications are far more specific and granular than what the ADM intends to address.

Answer 74

Preliminary Phase In the TOGAF 10 framework, the "Request for Architecture Work" is an optional artifact that can be produced during the "Preliminary Phase". This request provides a justification for starting a new architecture project cycle and defines the sponsor's requirements and constraints. It might originate from the business strategy, enterprise planning, portfolio management, or another source. While other phases in the ADM process focus on defining and detailing architecture vision, business architecture, and other domains, it is the Preliminary Phase where foundational steps such as creating the “Request for Architecture Work” take place to kickstart the architecture activity.

Answer 75

Phase H In the TOGAF 10 framework, "Phase H" is named Architecture Change Management. Its main purpose is to ensure the architecture remains consistent and relevant in the face of changing business needs and environments. It manages and enhances the established architecture over time to maintain its alignment with business objectives. While the other phases have crucial roles within the ADM cycle, "Phase E" is focused on Opportunities and Solutions, "Phase F" on Migration Planning, and "Phase G" on Implementation Governance. Only "Phase H" emphasizes the continual monitoring and management of the architecture after it has been established.

Answer 76

Phase A In the TOGAF 10 framework, the "Statement of Architecture Work" is developed and approved during "Phase A: Architecture Vision". This statement details the scope, approach, and content of an architecture development activity. It serves as a reference throughout the enterprise architecture process. While the Preliminary Phase deals with the preparation and initiation of the ADM cycle, including tailoring the framework and defining principles, it is in Phase A where the Statement of Architecture Work is defined and agreed upon by stakeholders, especially the sponsors.

Answer 77

Phase G In the TOGAF 10 framework, "Phase G" is known as Implementation Governance. During this phase, the main focus is on providing architectural oversight for the implementation. This ensures that projects are carried out in compliance with the defined architecture, ensuring that any deviations are handled appropriately. "Phase E" deals with Opportunities and Solutions, "Phase F" revolves around Migration Planning, and "Phase H" tackles Architecture Change Management. Out of the given options, only "Phase G" is specifically centered on governance during the implementation of the architecture projects.

Answer 78

At least annually Architecture principles are intended to be enduring, but they should not be immutable. Regular reviews ensure they remain aligned with the organization's mission, strategy, and evolving context. While the exact frequency of review might vary based on the organization's size, culture, and industry, a common best practice is to review architecture principles at least annually. This ensures that they remain relevant in a changing business environment. "Every time a new project starts" is too frequent, making it difficult to maintain a consistent architectural vision. "Only when there is a significant change in the organization's strategy" is too infrequent, as waiting for a significant strategic change might mean missing out on other relevant changes or nuances. "Once it has been set, it should not be changed" contradicts the evolving nature of business and technology environments.

Answer 79

Phase B The "Product Lifecycle Diagram" is typically associated with the business domain, focusing on how products evolve, get developed, and retire over time. This is a key consideration in defining the business strategy and operations, making it most relevant in "Phase B: Business Architecture" of the ADM. In Phase B, the organization's business strategy, governance, organization, and key business processes are defined and analyzed. As such, a Product Lifecycle Diagram can be a useful artifact to represent part of the business process landscape and product strategy. The other options are not primarily focused on the detailed development and representation of business strategies and processes.

Answer 80

Phase B The "Product Lifecycle Diagram" is typically associated with the business domain, focusing on how products evolve, get developed, and retire over time. This is a key consideration in defining the business strategy and operations, making it most relevant in "Phase B: Business Architecture" of the ADM. In Phase B, the organization's business strategy, governance, organization, and key business processes are defined and analyzed. As such, a Product Lifecycle Diagram can be a useful artifact to represent part of the business process landscape and product strategy. The other options are not primarily focused on the detailed development and representation of business strategies and processes.

Answer 81

Target Architecture In the TOGAF 10 framework, the "Target Architecture" describes the desired or future state of the architecture that an organization aims to achieve. It contrasts with the "Baseline Architecture", which describes the current or existing state. The process of moving from the Baseline to the Target Architecture often involves identifying gaps and creating a roadmap. "Baseline Architecture", describes the current state, not the future state. The "Architecture Repository", is a storage space for architectural artifacts and not a description of the future state itself. "Architecture Landscape", provides an overview of the entire architecture environment but isn't specifically focused on the future state alone.

Answer 82

Low Interest, High Power In the stakeholder map or Power Interest Matrix, stakeholders are classified based on their level of interest (concern) and their power (influence) over the project or initiative. The CEO of the company, while not directly involved in day-to-day operations, typically holds significant power due to their position as the company's leader. However, their level of interest in the detailed, day-to-day activities may be relatively low. Therefore, the CEO would typically be categorized as "Low Interest, High Power," meaning they need to be kept satisfied and informed about key developments but may not require detailed involvement or frequent communication on operational matters. The other options do not accurately reflect the typical role of a CEO in the stakeholder map.

Answer 83

Preliminary Phase In the TOGAF 10 framework, the "Preliminary Phase" is the phase where the TOGAF Architecture Framework is customized and tailored to align with the enterprise's specific needs, capabilities, constraints, and the existing environment. It sets the foundation by establishing the architecture team, tools, principles, and governance structures that will guide subsequent phases. While "Phase A", "Phase B", and "Phase C" involve important activities related to understanding business needs, establishing architecture visions, and detailing specific architecture domains, it is the Preliminary Phase that is specifically dedicated to tailoring the framework to meet the enterprise's unique context.

Answer 84

Foundation Architectures The Architecture Continuum in TOGAF provides a progression of architecture assets that move from foundational to more specific. At the left-most end of the scale, "Foundation Architectures" provide the most generic, foundational building blocks and standards that can be used across various industries and organizations. They are the base upon which more specific architectures are built. The other options—Common Systems Architectures, Industry Architectures, and Organization-Specific Architectures—progressively move to the right, becoming more specific and tailored.

Answer 85

Phase C In the ADM, "Phase C: Application Architecture" is specifically focused on defining the applications that are necessary to support the business functions and processes, both for the current (Baseline) and the desired future (Target) states. During this phase, the Application Architecture provides a blueprint for the individual application systems to be deployed, their interactions, and their relationships to the core business processes. The other phases listed are dedicated to different facets of the enterprise architecture: Phase A addresses the Architecture Vision, Phase B focuses on Business Architecture, and Phase D is for the Technology Architecture. Hence, only Phase C is directly concerned with the development of both the Baseline and Target Application Architectures.

Answer 86

Phase E In the TOGAF 10 framework, "Phase E" pertains to the Opportunities & Solutions. During this phase, the emphasis is on identifying major implementation projects and initiatives required to transition from the current, or Baseline Architecture, to the desired, or Target Architecture. It involves evaluating and prioritizing the projects based on criteria such as return on investment, alignment with business strategy, and technical feasibility. While "Phase C" and "Phase D" are more focused on defining the Data, Application, and Technology Architectures respectively, "Phase F" proceeds with migration planning details after opportunities and solutions have been identified. Among the options provided, only "Phase E" specifically focuses on detailing opportunities and solutions for the migration.

Answer 87

Business Transformation Readiness Assessment The Business Transformation Readiness Assessment is a key ADM guideline and technique for evaluating an organization's readiness to effectively adopt significant changes, especially in the context of business transformation efforts. It helps determine whether the organization possesses the necessary capabilities, resources, and willingness to successfully implement proposed changes. While other techniques such as Capability-Based Planning, Gap Analysis, and Stakeholder Management are valuable in the ADM process, they do not specifically focus on assessing an organization's readiness for change, making BTRA the most appropriate choice for this question.

Answer 88

To define the scope of the architecture capability. The Preliminary Phase in the TOGAF ADM primarily deals with preparing and setting up the architecture capability in an organization. It defines the scope, establishes the necessary architecture principles and practices, and prepares the organization to undergo a structured and systematic architecture development process. "To develop the target architecture" is incorrect because the development of the target architecture typically occurs in later phases. "To determine technology solutions for the organization" is also inaccurate because determining technology solutions is part of translating architectural decisions and is not the primary objective of the Preliminary Phase. "To select reference models, viewpoints, and tools", while an activity in the Preliminary Phase, does not capture the overarching objective of the phase as effectively as "To define the scope of the architecture capability" does.

Answer 89

Architecture Development Method (ADM) The Architecture Development Method (ADM) is the heart of the TOGAF framework. It provides a tested and repeatable process for developing architectures. ADM is a comprehensive, step-by-step approach to guide architects through the complex process of enterprise architecture development. While the other options (Enterprise Continuum, Architecture Capability Framework, and Architecture Repository) are essential components of the TOGAF framework, none of them individually represent the core technique of TOGAF in the same way that the ADM does. The ADM integrates all these components and provides the methodology for creating and using enterprise architectures.

Answer 90

Phase B In the TOGAF 10 framework, "Phase B" is dedicated to Business Architecture. The main objective of this phase is to develop the Target Business Architecture that describes how the enterprise will operate in the future, given the desired architecture outcome. This phase looks into the organizational structure, governance, business processes, and operations of the enterprise. On the other hand, "Phase A" (Architecture Vision) sets the overall vision for the architectural endeavor, "Phase C" delves into Information Systems Architectures, and the "Preliminary Phase" prepares the organization for undertaking an architecture project. Of all these phases, only "Phase B" focuses specifically on the development of the Target Business Architecture.

Answer 91

Phase D In the TOGAF 10 framework, "Phase D" pertains to the Technology Architecture. The main objective during this phase is to design the technological infrastructure needed to support the deployment of core applications, data, and processes. It involves detailing the technology solutions and platforms, defining building blocks, and ensuring that the technology architecture is consistent and aligned with the business requirements. While "Phase A" addresses the overall architecture vision, "Phase B" delves into Business Architecture, and "Phase C" deals with Data and Application Architecture. Among the options provided, only "Phase D" specifically focuses on the Technology Architecture.

Answer 92

Architecture Contract In TOGAF 10, an "Architecture Contract" is the joint agreement between architecture practitioners and stakeholders. It is contractually specified and details the deliverables, artifacts, and responsibilities of the parties involved. Once established, the Architecture Contract is formally reviewed, agreed upon, and signed off by the stakeholders. The "Architecture Principle", provides the general rules and guidelines for architecture work but isn't a contractually binding document. The "Architecture Vision", sets the high-level direction and initial descriptions of an architecture initiative but does not serve as a contractual agreement. "Architecture Building Block (ABB)", represents a component of the architecture model, but it isn't a signed-off contract between parties.

Answer 93

1) Development of silos leads to duplication and shortsighted goals 2) Chaos - 3) Technical debt - Extra work that results from prioritising speed over quality.

Answer 94

More prone to siloed decision making

Answer 95

An enterprise-wide strategy

Answer 96

Enablement provides tools and training to support the ability of software delivery teams to output high-quality, resilient, compliant software.

Answer 97

The enterprise architecture function aims to solve complex enterprise problems across silos, and to provide standards, principles, and best practices to deliver high-quality, scalable, and secure solutions.

Answer 98

A control is a process or technical policy that provides assurance that a requirement is met in a compliant manner.

Answer 99

Friction is limited and compliance is assured.

Answer 100

Architecture best practices Architecture metrics Architecture standards

Answer 101

Incidents caused by application If you measure this, you will incentivize behaviors that mitigate the risks associated with causes of incidents, such as untested changes or single point of failures. If this metric is higher than expected, it may indicate that the application isn’t built to be scalable, resilient, and/or reliable and needs corrective action or it can adversely impact a company’s brand and reputation.

Answer 102

An effective enterprise architecture strategy must emphasize a culture of trust. It can instill mechanisms such as clarifying architecture roles, establishing standard architecture processes and engagement models that foster cooperation. Ultimately, it is the culture that will make or break an effective enterprise architecture practice.

Answer 103

Following an architecture standard or process, and using an architecture deliverable, is intrinsically part of normal software delivery processes used by the organization.

Answer 104

Describing the problem statement, business impacts, and benefits

Answer 105

No, you also need commitment that the decision will be implemented.

Answer 106

The stakeholder has an internal or external motivation to be engaged in the decision.

Answer 107

Beliefs are one of the typical inputs.

Answer 108

Many over few

Answer 109

Transparent to find Just in Time

Answer 110

Flag it or fix it

Answer 111

It puts the power of architecture knowledge into the hands of those who most need to learn that knowledge to apply it to solving problems.

Answer 112

It ensures that architecture information is effective through continuous learning and improvement.

Answer 113

Reduces support needs Promotes brand Promotes optimal usage and satisfaction

Answer 114

Create, approve, distribute, consume

Answer 115

Operational efficiency Risk Management (operational, security, data management) Innovation

Answer 116

Head of the IT Department Phase D of the ADM in TOGAF 10 pertains to the Technology Architecture. This phase aims to map out and define the technology infrastructure, platforms, and software necessary to support the enterprise's architecture. It entails designing the hardware, software, and network solutions to meet the application and data requirements of the organization. As a result, the Head of the IT Department would have a significant interest in the outputs of this phase, as they are responsible for overseeing the technology infrastructure, its acquisition, and its effective deployment. While the other options – Chief Marketing Officer, Head of Human Resources, and Chief Financial Officer – would have some interest in various aspects of the enterprise's architecture, they would not be as directly concerned with the technical details laid out in Phase D as the Head of the IT Department would be.

Answer 117

Phase B In the TOGAF 10 framework, "Phase B" is dedicated to Business Architecture. The main objective of this phase is to develop the Target Business Architecture that describes how the enterprise will operate in the future, given the desired architecture outcome. This phase looks into the organizational structure, governance, business processes, and operations of the enterprise. On the other hand, "Phase A" (Architecture Vision) sets the overall vision for the architectural endeavor, "Phase C" delves into Information Systems Architectures, and the "Preliminary Phase" prepares the organization for undertaking an architecture project. Of all these phases, only "Phase B" focuses specifically on the development of the Target Business Architecture.

Answer 118

Phase A In the TOGAF 10 framework, the "Statement of Architecture Work" is developed and approved during "Phase A: Architecture Vision". This statement details the scope, approach, and content of an architecture development activity. It serves as a reference throughout the enterprise architecture process. While the Preliminary Phase deals with the preparation and initiation of the ADM cycle, including tailoring the framework and defining principles, it is in Phase A where the Statement of Architecture Work is defined and agreed upon by stakeholders, especially the sponsors.

Answer 119

Iteration Iteration refers to the practice of repeating certain phases or activities within the ADM to refine and detail the architecture as it evolves. In this case, organizations are taking an iterative approach to Phases B-D to gain a broader, high-level perspective before diving deeper into the specifics during the next pass. Iteration ensures that architects can adapt to changes or additional information, making the final architecture more aligned with the requirements. The other options, segmentation, diversification, and modularization, do not accurately describe the practice of revisiting phases for refinement and depth.

Answer 120

Artifact In the TOGAF 10 framework, an "Artifact" is an architectural work product that describes an aspect of the architecture. Artifacts represent specific pieces of information that are produced, consumed, or utilized during the architectural process. "Transition Architecture", represents a state of the architecture at a significant milestone. "Viewpoint", is the specification of the conventions for constructing and using a view. It provides the template from which a view can be developed. "Stakeholder", refers to individuals or entities that have interests in, or concerns relative to, the outcome of the architecture. Among these choices, only "Artifact" correctly identifies an architectural work product that captures and documents an aspect of the architecture.

Answer 121

Business Transformation Readiness Assessment The Business Transformation Readiness Assessment is a key ADM guideline and technique for evaluating an organization's readiness to effectively adopt significant changes, especially in the context of business transformation efforts. It helps determine whether the organization possesses the necessary capabilities, resources, and willingness to successfully implement proposed changes. While other techniques such as Capability-Based Planning, Gap Analysis, and Stakeholder Management are valuable in the ADM process, they do not specifically focus on assessing an organization's readiness for change, making BTRA the most appropriate choice for this question.

Answer 122

Phase B The "Product Lifecycle Diagram" is typically associated with the business domain, focusing on how products evolve, get developed, and retire over time. This is a key consideration in defining the business strategy and operations, making it most relevant in "Phase B: Business Architecture" of the ADM. In Phase B, the organization's business strategy, governance, organization, and key business processes are defined and analyzed. As such, a Product Lifecycle Diagram can be a useful artifact to represent part of the business process landscape and product strategy. The other options are not primarily focused on the detailed development and representation of business strategies and processes.

Answer 123

Phase C In the TOGAF 10 framework, "Phase C" is split into two parts: Data Architecture and Application Architecture. When focusing on Data Architecture, the primary objective is to define the data structures, relationships, and their specifications. This includes understanding the data assets of the organization, their relationships, and the associated data standards and principles. "Phase A" provides the overarching architecture vision, "Phase B" is dedicated to Business Architecture, and the "Preliminary Phase" prepares the organization to undertake architecture development. Among these options, only "Phase C" zeroes in on defining data architectures and its related components.

Answer 124

Phase C In the ADM, "Phase C: Application Architecture" is specifically focused on defining the applications that are necessary to support the business functions and processes, both for the current (Baseline) and the desired future (Target) states. During this phase, the Application Architecture provides a blueprint for the individual application systems to be deployed, their interactions, and their relationships to the core business processes. The other phases listed are dedicated to different facets of the enterprise architecture: Phase A addresses the Architecture Vision, Phase B focuses on Business Architecture, and Phase D is for the Technology Architecture. Hence, only Phase C is directly concerned with the development of both the Baseline and Target Application Architectures.

Answer 125

Phase E In the TOGAF 10 framework, "Phase E" pertains to the Opportunities & Solutions. During this phase, the emphasis is on identifying major implementation projects and initiatives required to transition from the current, or Baseline Architecture, to the desired, or Target Architecture. It involves evaluating and prioritizing the projects based on criteria such as return on investment, alignment with business strategy, and technical feasibility. While "Phase C" and "Phase D" are more focused on defining the Data, Application, and Technology Architectures respectively, "Phase F" proceeds with migration planning details after opportunities and solutions have been identified. Among the options provided, only "Phase E" specifically focuses on detailing opportunities and solutions for the migration.

Answer 126

Target Architecture In the TOGAF 10 framework, the "Target Architecture" describes the desired or future state of the architecture that an organization aims to achieve. It contrasts with the "Baseline Architecture", which describes the current or existing state. The process of moving from the Baseline to the Target Architecture often involves identifying gaps and creating a roadmap. "Baseline Architecture", describes the current state, not the future state. The "Architecture Repository", is a storage space for architectural artifacts and not a description of the future state itself. "Architecture Landscape", provides an overview of the entire architecture environment but isn't specifically focused on the future state alone

Answer 127

Foundation Architectures The Architecture Continuum in TOGAF provides a progression of architecture assets that move from foundational to more specific. At the left-most end of the scale, "Foundation Architectures" provide the most generic, foundational building blocks and standards that can be used across various industries and organizations. They are the base upon which more specific architectures are built. The other options—Common Systems Architectures, Industry Architectures, and Organization-Specific Architectures—progressively move to the right, becoming more specific and tailored.

Answer 128

At least annually Architecture principles are intended to be enduring, but they should not be immutable. Regular reviews ensure they remain aligned with the organization's mission, strategy, and evolving context. While the exact frequency of review might vary based on the organization's size, culture, and industry, a common best practice is to review architecture principles at least annually. This ensures that they remain relevant in a changing business environment. "Every time a new project starts" is too frequent, making it difficult to maintain a consistent architectural vision. "Only when there is a significant change in the organization's strategy" is too infrequent, as waiting for a significant strategic change might mean missing out on other relevant changes or nuances. "Once it has been set, it should not be changed" contradicts the evolving nature of business and technology environments.

Answer 129

Phase G In the TOGAF 10 framework, "Phase G" is known as Implementation Governance. During this phase, the main focus is on providing architectural oversight for the implementation. This ensures that projects are carried out in compliance with the defined architecture, ensuring that any deviations are handled appropriately. "Phase E" deals with Opportunities and Solutions, "Phase F" revolves around Migration Planning, and "Phase H" tackles Architecture Change Management. Out of the given options, only "Phase G" is specifically centered on governance during the implementation of the architecture projects.

Answer 130

Preliminary Phase In the TOGAF 10 framework, the "Preliminary Phase" is the phase where the TOGAF Architecture Framework is customized and tailored to align with the enterprise's specific needs, capabilities, constraints, and the existing environment. It sets the foundation by establishing the architecture team, tools, principles, and governance structures that will guide subsequent phases. While "Phase A", "Phase B", and "Phase C" involve important activities related to understanding business needs, establishing architecture visions, and detailing specific architecture domains, it is the Preliminary Phase that is specifically dedicated to tailoring the framework to meet the enterprise's unique context.

Answer 131

Phase B In the TOGAF 10 framework, the Baseline and Target Business Architectures are developed during "Phase B: Business Architecture". This phase focuses on describing the existing business architecture (baseline) and establishing the future business architecture (target) that the organization aims to achieve. The goal is to represent organizational, functional, process, information, and other related architectures in both current and desired future states. While Phase A (Architecture Vision) sets the high-level strategic context, it is in Phase B where the detailed business architectures are defined. The other options do not specifically focus on the detailed development of business architectures.

Answer 132

Transition Architecture In the TOGAF 10 framework, "Transition Architecture" describes the architecture of a solution at an interim, architecturally significant milestone as the enterprise progresses from the Baseline Architecture to the Target Architecture. It provides a clear view and roadmap of the architectural landscape's evolution. "Baseline Architecture", describes the current state of the architecture. "Target Architecture", represents the desired or future state of the architecture. "Architecture Vision", is the high-level, aspirational view of the end architecture product. Among the given options, only the Transition Architecture captures the description of the architecture at a specific, significant point during its evolution towards the desired future state.

Answer 133

Phase C The "Phase C: Application Architecture" of the ADM specifically addresses the development of the Application Architecture for an organization, including the identification and articulation of key application components and their relationships. An Application Use-Case Diagram is a type of artifact that showcases how different application components interact or are used to achieve specific functions or tasks. This makes it highly relevant to Phase C, which is about defining applications and their interactions. Phase A focuses on the Architecture Vision, Phase B is dedicated to Business Architecture, and Phase D centers on Technology Architecture. Consequently, among the options provided, only Phase C would typically involve the creation of an Application Use-Case Diagram as part of its architectural artifacts.

Answer 134

To define the scope of the architecture capability. The Preliminary Phase in the TOGAF ADM primarily deals with preparing and setting up the architecture capability in an organization. It defines the scope, establishes the necessary architecture principles and practices, and prepares the organization to undergo a structured and systematic architecture development process. "To develop the target architecture" is incorrect because the development of the target architecture typically occurs in later phases. "To determine technology solutions for the organization" is also inaccurate because determining technology solutions is part of translating architectural decisions and is not the primary objective of the Preliminary Phase. "To select reference models, viewpoints, and tools", while an activity in the Preliminary Phase, does not capture the overarching objective of the phase as effectively as "To define the scope of the architecture capability" does.

Answer 135

Phase H In the TOGAF 10 framework, "Phase H" is named Architecture Change Management. Its main purpose is to ensure the architecture remains consistent and relevant in the face of changing business needs and environments. It manages and enhances the established architecture over time to maintain its alignment with business objectives. While the other phases have crucial roles within the ADM cycle, "Phase E" is focused on Opportunities and Solutions, "Phase F" on Migration Planning, and "Phase G" on Implementation Governance. Only "Phase H" emphasizes the continual monitoring and management of the architecture after it has been established.

Answer 136

Architecture Development Method (ADM) The Architecture Development Method (ADM) is the heart of the TOGAF framework. It provides a tested and repeatable process for developing architectures. ADM is a comprehensive, step-by-step approach to guide architects through the complex process of enterprise architecture development. While the other options (Enterprise Continuum, Architecture Capability Framework, and Architecture Repository) are essential components of the TOGAF framework, none of them individually represent the core technique of TOGAF in the same way that the ADM does. The ADM integrates all these components and provides the methodology for creating and using enterprise architectures.

Answer 137

Providing a detailed step-by-step approach for developing an enterprise architecture. The TOGAF Architecture Development Method (ADM) serves as the core of TOGAF. Its primary objective is to provide a detailed, step-by-step approach for developing an enterprise architecture, ensuring that all aspects of the enterprise are addressed and integrated into a holistic view. "Defining a long-term IT strategy for an organization", while somewhat related, is too narrow in its focus on IT and does not encompass the breadth and depth of enterprise architecture as defined by TOGAF. "Implementing agile development processes within an organization" is incorrect because the ADM is not specifically about agile development processes; it's about the overall development of an enterprise architecture. "Designing the interface layouts for software applications" is off-topic; interface layouts for software applications are far more specific and granular than what the ADM intends to address.

Answer 138

Preliminary Phase In the TOGAF 10 framework, the "Request for Architecture Work" is an optional artifact that can be produced during the "Preliminary Phase". This request provides a justification for starting a new architecture project cycle and defines the sponsor's requirements and constraints. It might originate from the business strategy, enterprise planning, portfolio management, or another source. While other phases in the ADM process focus on defining and detailing architecture vision, business architecture, and other domains, it is the Preliminary Phase where foundational steps such as creating the “Request for Architecture Work” take place to kickstart the architecture activity.

Answer 139

Phase C In the TOGAF 10 framework, "Phase C" encompasses both Data Architecture and Application Architecture. When focusing on Application Architecture, the primary objective is to establish a blueprint for the individual application systems to be deployed, the interactions between application systems, and their relationships to the core business processes of the organization. "Phase A" provides the overarching architecture vision, "Phase B" concentrates on Business Architecture, and the "Preliminary Phase" sets the groundwork for the architecture development effort. Among the provided choices, only "Phase C" specifically addresses the development and description of the Application Architecture.

Answer 140

Phase A In the TOGAF 10 framework, "Phase A" is titled "Architecture Vision." This phase is primarily concerned with the creation of the Statement of Architecture Work, which captures the scope, approach, and content of the architecture activities being undertaken. A crucial step within this phase is obtaining the necessary approvals to commence further work based on this statement. In contrast, the "Preliminary Phase" focuses on establishing the architecture capability, "Phase B" is about developing the business architecture, and "Phase D" deals with the technology architecture. Among the options, only "Phase A" specifically aims at obtaining approval for the Statement of Architecture Work.

Answer 141

Preliminary Phase In the TOGAF 10 framework, the "Preliminary Phase" focuses on defining the enterprise's architecture vision and strategy, which includes determining the desired architecture capability. This phase establishes how an organization's architecture capability will meet the strategic objectives of the enterprise. Phase A is more about defining the high-level strategic intent of the entire architecture development. Phase B describes the current and future state of the business environment. Phase D defines the technology infrastructure needed to support the other architecture domains. Among the provided choices, only the Preliminary Phase captures the objective of determining the desired architecture capability of the organization.

Answer 142

A classification scheme for architecture assets. The Enterprise Continuum in TOGAF 10 provides a classification scheme for categorizing and storing architecture and solution assets. It serves as a valuable tool for developing architectures across an organization by helping architects understand where and how specific assets fit within a broader architectural context. "A repository for storing architecture artifacts" is incorrect because the Enterprise Continuum is not a repository but a classification model; the Architecture Repository is where artifacts are stored. "A lifecycle method for developing architectures" is incorrect as this describes the Architecture Development Method (ADM), not the Enterprise Continuum. "A set of predefined architecture patterns" is not entirely accurate because while the continuum does include patterns, it's not merely a set of predefined patterns; it's a broader classification scheme.

Answer 143

Architecture Contract In TOGAF 10, an "Architecture Contract" is the joint agreement between architecture practitioners and stakeholders. It is contractually specified and details the deliverables, artifacts, and responsibilities of the parties involved. Once established, the Architecture Contract is formally reviewed, agreed upon, and signed off by the stakeholders. The "Architecture Principle", provides the general rules and guidelines for architecture work but isn't a contractually binding document. The "Architecture Vision", sets the high-level direction and initial descriptions of an architecture initiative but does not serve as a contractual agreement. "Architecture Building Block (ABB)", represents a component of the architecture model, but it isn't a signed-off contract between parties.

Answer 144

The practice of monitoring and directing architecture activities to ensure alignment with business objectives. Architecture governance in the TOGAF 10 context refers to the overarching practice of overseeing, directing, and ensuring that architectural initiatives and activities are in alignment with the organization's business objectives and strategies. It encompasses principles, practices, roles, responsibilities, and processes that ensure the effective and efficient use of architecture resources in achieving desired outcomes. "The structure and hierarchy of roles within an architectural team" is not correct because it focuses on roles, not on the overall monitoring and guiding function of governance. "The software and tools used in the architectural development process" is off the mark as it emphasizes tools rather than governance processes. "The blueprint or design of an organization's technology systems", while related to architectural work, is not governance itself but rather a product of architectural efforts.

Answer 145

A tailored CRM system for ABC Corp's unique processes The Architecture Continuum in TOGAF is divided into categories that range from foundational to specific. The "organization-specific" category encompasses architectures tailored to a particular organization's unique needs and context. A tailored CRM system for ABC Corp's unique processes falls under this category, as it is specifically designed for that organization's operations. In contrast, general industry best practices, generic security protocols, and standardized infrastructure components are more generic and would fit earlier in the continuum, being relevant to a broader range of organizations.

Answer 146

A potentially re-usable component that can be combined with other building blocks to deliver architectures and solutions. In the TOGAF 10 framework, a "Building Block" represents a potentially re-usable component (whether functional, technical, or organizational) that can be combined with other building blocks to form complete architectures or solutions. "A complete solution for enterprise architecture requirements" describes a result, but not the fundamental nature of a building block. "A standalone unit that doesn't interact with other components" is incorrect as building blocks are designed to interact with others to form a complete system or solution. "The process of defining and documenting the structure, organization, and implementation of architectural components" describes the process of architecture work, not the definition of a building block. Among the choices, only "A potentially re-usable component that can be combined with other building blocks to deliver architectures and solutions" accurately captures the essence of what a building block represents within the TOGAF framework.

Answer 147

View In the TOGAF 10 framework, a "View" is defined as a representation of a system from the perspective of a related set of concerns. It's essentially what you see when you look at a system from a particular viewpoint. "Viewpoint", is the specification of the conventions for constructing and using a view. It defines the perspective and the concerns addressed, but is not the representation itself. "Stakeholder", refers to an individual, team, or organization (or classes thereof) with interests in, or concerns relative to, the outcome of the architecture. "Artifact", is a more general term representing a tangible output of the architectural work, which might be a document, model, or other specific form of output. Among these options, only "View" accurately captures the representation of the system based on a set of concerns.

Answer 148

Requirements Management Phase In the TOGAF 10 framework, the "Requirements Management Phase" acts as a central hub that governs the flow of requirements to and from the various phases of the ADM. It ensures that the architecture remains consistently aligned with business needs throughout its lifecycle. The phase manages and addresses requirements as they are identified, throughout the architecture development cycle. While other phases such as "Phase A", "Phase H", and "Phase F" have important roles in the ADM process, it is the Requirements Management Phase that is specifically dedicated to overseeing and managing requirements in a holistic manner.

Answer 149

A difference between the baseline and target architectures. In the context of the TOGAF 10 ADM, a "gap" refers to a difference or discrepancy between the existing (baseline) architecture and the desired (target) architecture. Gap Analysis is a technique for identifying what needs to change in terms of components, processes, and other factors to move from the current state to the desired future state. "A missing software tool or application within the enterprise's IT landscape" is incorrect because, while missing tools or applications might be discovered as a result of a Gap Analysis, they do not define what a gap is. "The lack of alignment between the business and IT strategies" is a broader strategic concern that might lead to an architectural gap, but it doesn't define a gap within the context of the ADM. "An architectural decision that hasn't been approved by stakeholders" is unrelated to the concept of a gap in this context; it deals more with architectural governance and stakeholder approval.

Answer 150

Low Interest, High Power In the stakeholder map or Power Interest Matrix, stakeholders are classified based on their level of interest (concern) and their power (influence) over the project or initiative. The CEO of the company, while not directly involved in day-to-day operations, typically holds significant power due to their position as the company's leader. However, their level of interest in the detailed, day-to-day activities may be relatively low. Therefore, the CEO would typically be categorized as "Low Interest, High Power," meaning they need to be kept satisfied and informed about key developments but may not require detailed involvement or frequent communication on operational matters. The other options do not accurately reflect the typical role of a CEO in the stakeholder map.

Answer 151

Phase F In the TOGAF 10 framework, "Phase F" relates to Migration Planning. This phase primarily focuses on crafting detailed plans that guide the enterprise through the implementation of the Target Architecture. The Migration Plan is developed in this phase, detailing the projects, their dependencies, and timelines required to achieve the full transformation. While "Phase E" identifies opportunities and solutions for transitioning, "Phase G" deals with implementation governance, and "Phase H" is concerned with architecture change management. Among the choices, only "Phase F" emphasizes the detailed planning for the transition from the Baseline to the Target Architectures.

Answer 152

Any collection of organizations that share a common set of goals. In the context of TOGAF 10, an "enterprise" is broadly defined as any collection of organizations that share a common set of goals. This could be a single organization or a cross-section of multiple organizations. The emphasis is on the shared objectives rather than the size or nature of the entity. "A large multinational corporation with thousands of employees" is incorrect as an enterprise does not necessarily have to be large or multinational. "A formal structure with a primary goal of producing profits for its shareholders" is overly narrow, as enterprises can have various goals beyond profit-making. "A technological infrastructure that supports business operations" misconstrues the term "enterprise" by focusing on the technological aspect rather than the collective organizational goals.

Answer 153

Phase A In the TOGAF 10 framework, the "Draft Architecture Definition Document" is created during "Phase A: Architecture Vision". This document provides a description of the new architecture as a series of views addressing stakeholder concerns, thus capturing both the baseline (current) and target (desired) architectural states. Phase A focuses on creating the high-level vision of the capabilities and business value to be delivered as a result of the proposed enterprise architecture. The other phases further refine or implement parts of the architecture, but it is Phase A where the initial draft of the Architecture Definition Document is established.

Answer 154

Phase A Phase A, known as "Architecture Vision" in TOGAF, is the correct answer. This phase is the initial phase of the TOGAF ADM and is specifically dedicated to creating an initial architectural vision that outlines the high-level scope, objectives, and stakeholders' concerns for the architecture project. It plays a crucial role in obtaining stakeholder buy-in and ensuring that all stakeholders have a common understanding of the architecture project's goals and objectives. Phases B, C, and D represent different phases in the TOGAF ADM, but they do not focus on the creation of the initial architecture vision and stakeholder buy-in, making them incorrect answers for this question.

Section 1 - The ADM Flashcards

Understand the ADM cycle (187 cards)