What are the four dimensions used to scope an architecture?
A. Business Data Application Technology
B. Strategy Segment Capability Budget
C. Breadth Depth Time Period Architecture Domains
D. Strategy Portfolio Project Solution Delivery
Explanation:
The four dimensions used to scope an architecture are Breadth, Depth, Time Period, and Architecture Domains1, p. 8.
Breadth refers to the extent of the enterprise covered by the architecture, which can range from a specific business unit to the entire organization1, p. 8.
Depth refers to the level of detail and completeness of the architecture, which can vary depending on the purpose, scope, and stakeholders of the architecture1, p. 8.
Time Period refers to the temporal aspects of the architecture, such as the current state, the target state, and the transition plan1, p. 8.
Architecture Domains refers to the classification of the architecture into four domains: Business, Data, Application, and Technology1, p. 8.
These four dimensions help define the scope and boundaries of the architecture and ensure that it meets the needs and expectations of the stakeholders.
References:
1: The Open Group (2018). The TOGAF® Standard, Version 9.2. 1
When considering the scope of an architecture, what dimension considers to what level of detail the architecting effort should go?
A. Project
B. Breadth
C. Depth
D. Architecture Domains
Explanation:
The scope of an architecture is the extent and level of detail of the architecture work. The scope of an architecture can be defined along four dimensions: project, breadth, depth, and architecture domains. The project dimension considers the boundaries and objectives of the architecture project, such as the time frame, budget, resources, and deliverables. The breadth dimension considers the coverage and completeness of the architecture across the enterprise, such as the organizational units, business functions, processes, and locations. The depth dimension considers the level of detail and specificity of the architecture, such as the granularity, abstraction, and precision of the architectural elements and relationships. The architecture domains dimension considers the aspects or segments of the architecture, such as the business, data, application, and technology domains.
Therefore, the depth dimension is the one that considers to what level of detail the architecting effort should go.
References: : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 25: Architecture Scope : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 25.2: Scope Dimensions : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 25.2.1: Project, Breadth, Depth, and Architecture Domains
Which of the following supports the need to govern Enterprise Architecture?
A. The Architecture Project mandates the governance of the target architecture
B. The TOGAF standard cannot be used without executive governance
C. Best practice governance enables the organization to control value realization
D. The Stakeholders preferences may go beyond the architecture project scope and needs control
Explanation:
This statement best supports the need to govern Enterprise Architecture. Best practice governance enables the organization to control value realization by ensuring that architectures are aligned with the enterprise’s strategy and objectives, meet the quality and performance requirements, and deliver the expected benefits and outcomes. The Architecture Project does not mandate the governance of the target architecture, but rather follows the governance framework established by the enterprise. The TOGAF standard can be used without executive governance, but it is recommended that executive sponsorship and support are obtained for successful architecture development and transition. The Stakeholders preferences may go beyond the architecture project scope and need control, but this is not the primary reason for governing Enterprise Architecture.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.6 Architecture Governance.
Which one of the following classes of information within the Architecture Repository would typically contain a list of the applications in use within the enterprise?
A. Reference Library
B. Architecture Metamodel
C. Architecture Landscape
D. Governance Log
Explanation:
The Architecture Landscape is a class of information within the Architecture Repository that shows an architectural view of the building blocks that are in use within the organization today (the Baseline Architecture), as well as those that are planned for the future (the Target Architecture). The Architecture Landscape typically contains a list of the applications in use within the enterprise, along with their relationships and dependencies, as well as other relevant architectural information. The Architecture Landscape helps to identify opportunities for re-use, consolidation, or retirement of existing applications, as well as gaps or overlaps in the current or future architecture.
References: : The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 34: Architecture Landscape : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 47: Architecture Repository
Which of the following is a responsibility of an Architecture Board?
A. Conducting assessments of the maturity level of architecture discipline within the organization
B. Allocating resources for architecture projects
C. Creating the Statement of Architecture Work
D. Establishing targets for re-use of components
Explanation:
Page 4 out of 19 Pages |
Previous |