Which of the following best describes purpose of the Business Scenarios?
Answer(s): B
Business scenarios are a technique for capturing, clarifying, and communicating the functional and non-functional requirements of a system. Business scenarios describe the business environment, the actors involved, the desired outcomes, and the processes or rules that govern the behavior of the system. Business scenarios are useful for ensuring that the architecture addresses the real needs and concerns of the stakeholders, and for validating and testing the architecture against expected situations. Business scenarios are developed in Phase A: Architecture Vision of the ADM cycle, and refined and updated throughout the other phases3
3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 26: Business Scenarios : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18: Phase A: Architecture Vision
Consider the following statements:1. Each contracted party is required to act responsibly to the organization and its stakeholders.2. All decisions taken, processes used, and their implementation will not be allowed to create unfair advantage to any one particular party.3. Digital Transformation and operations will be more effective and efficient.4. Strategic decision-making by C-Level executives and business leaders will be more effective.Which statements highlight the value and necessity for Architecture Governance to be adopted within organizations?
Answer(s): A
Architecture governance is the practice of ensuring compliance with the enterprise architecture and its principles, standards, and goals. Architecture governance provides the means to establish, monitor, and control the architecture development and implementation processes, and to resolve any issues or conflicts that may arise. Architecture governance also ensures that all stakeholders are represented and involved in the decision-making process, and that their interests and concerns are balanced and aligned. Statements 1 and 2 highlight the value and necessity for architecture governance to be adopted within organizations, as they emphasize the importance of responsibility, accountability, fairness, and transparency in the architectural activities. Statements 3 and 4 are more related to the benefits and outcomes of having a good enterprise architecture, rather than the governance aspect.The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 50: Architecture Governance : The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 29: Architecture Governance
Consider the image showing basic architectural concepts.What are items A and B?
The image shows a diagram that illustrates the basic concepts of architecture description as defined by the ISO/IEC/IEEE 42010:2011 standard1, which is also adopted by the TOGAF standard2.According to the ISO/IEC/IEEE 42010:2011 standard, an architecture description is a work product used to express an architecture, and it consists of one or more architecture views1.An architecture view is a representation of a system from the perspective of a related set of concerns, and it conforms to an architecture viewpoint1.An architecture viewpoint is a specification of the conventions for constructing and using an architecture view to address specific stakeholder concerns1.Therefore, the correct answer is option A, which identifies the items labeled as “A” and “B” in the image as an architecture viewpoint and an architecture view, respectively.
1: ISO/IEC/IEEE 42010:2011 - Systems and software engineering — Architecture description12: TOGAF Standard, Version 9.2 - Part IV: Architecture Content Framework - 31. Architectural Artifacts2
Which ADM phase focuses on defining the problem to be solved, identifying the stakeholders, their concerns, and requirements?
Answer(s): D
Phase A: Architecture Vision is the first phase of the Architecture Development Method (ADM) cycle, which is the core of the TOGAF standard. The main purpose of this phase is to define the scope and approach of the architecture development, and to create the Architecture Vision, which is a high-level description of the desired outcomes and benefits of the proposed architecture. To achieve this purpose, this phase focuses on defining the problem to be solved, identifying the stakeholders, their concerns, and requirements, and establishing the business goals and drivers that motivate the architecture work. This phase also involves obtaining the approval and commitment of the sponsors and other key stakeholders, and initiating the Architecture Governance process.The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 5: Introduction to the ADM : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18: Phase A: Architecture Vision : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18.3: Inputs : The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 18.4: Steps
When considering the scope of an architecture, what dimension is about the extent of the enterprise?
Comprehensive and Detailed ExplanationWhen defining the scope of an architecture, TOGAF identifies four dimensions that need to be considered:Breadth – This dimension addresses the extent of the enterprise that will be impacted by the architecture. It answers the question: How much of the enterprise is covered? For example, does the scope include the entire enterprise, a business unit, a division, or just a single organizational function?Depth – This refers to the level of detail to be covered. For instance, will the architecture describe high-level capabilities, or will it go into detailed system design?Time Period – This defines the planning horizon of the architecture. It could be short-term (tactical), medium-term, or long-term (strategic).Architecture Domains – This refers to which domains are covered: Business, Data, Application, and Technology. The scope may include all or just a subset of these domains.Project Scope (sometimes discussed separately) – Focuses on which specific programs, portfolios, or projects will be impacted.Among these, the dimension that specifically relates to the extent of the enterprise is Breadth.Why the other options are incorrectA . Architecture Domains: Refers to the domains covered (Business, Data, Application, Technology), not the extent of the enterprise.B . Depth: Refers to the level of detail, not the enterprise extent.C . Project: Refers to the program or initiative focus, not enterprise coverage.ReferenceThe Open Group, TOGAF® Standard, Version 9.2, Part II: ADM — Preliminary Phase (scope considerations).The Open Group, TOGAF® 9 Certified Study Guide — discussion of the dimensions of architecture scope (Breadth, Depth, Time Period, Architecture Domains).
Post your Comments and Discuss The Open Group OGEA-101 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the OGEA-101 content, but please register or login to continue.