Practice Free OGEA-10B Exam Online Questions
Question #1
Which of the following does the TOGAF standard describe as a package of functionality defined to meet business needs across an organization?
- A . An application
- B . A deliverable
- C . A solution architecture
- D . A building block
Correct Answer: D
Question #2
What component of the Architecture Repository represents architecture requirements agreed with the Architecture Board?
- A . Reference Library
- B . Architecture Capability
- C . Architecture Requirements Repository
- D . Governance Log
Correct Answer: C
C
Explanation
The Architecture Requirements Repository stores all the requirements that are output of the architecture development cycle, as well as the requirements that are input to the architecture development cycle1.
The Architecture Requirements Repository includes the following types of requirements1:
• Stakeholder Requirements: These are the high-level requirements and expectations of the stakeholders, derived from the business drivers, goals, and objectives. They are captured and refined in the Architecture Vision phase and the Requirements Management phase.
• Architecture Requirements: These are the detailed requirements that specify what the architecture must do or deliver to meet the stakeholder requirements. They are derived and refined in the Business, Information Systems, and Technology Architecture phases.
• Implementation and Migration Requirements: These are the detailed requirements that specify what the implementation and migration projects must do or deliver to realize the architecture. They are derived and refined in the Opportunities and Solutions and Migration Planning phases.
The Architecture Requirements Repository is used to manage the architecture requirements throughout the architecture lifecycle, ensuring their traceability, consistency, and compliance1. The Architecture Board is the authority that reviews and approves the architecture requirements, as well as the architecture deliverables and artifacts, as part of the architecture governance process2.
References: 1: Architecture Requirements Repository 2: Architecture Board
C
Explanation
The Architecture Requirements Repository stores all the requirements that are output of the architecture development cycle, as well as the requirements that are input to the architecture development cycle1.
The Architecture Requirements Repository includes the following types of requirements1:
• Stakeholder Requirements: These are the high-level requirements and expectations of the stakeholders, derived from the business drivers, goals, and objectives. They are captured and refined in the Architecture Vision phase and the Requirements Management phase.
• Architecture Requirements: These are the detailed requirements that specify what the architecture must do or deliver to meet the stakeholder requirements. They are derived and refined in the Business, Information Systems, and Technology Architecture phases.
• Implementation and Migration Requirements: These are the detailed requirements that specify what the implementation and migration projects must do or deliver to realize the architecture. They are derived and refined in the Opportunities and Solutions and Migration Planning phases.
The Architecture Requirements Repository is used to manage the architecture requirements throughout the architecture lifecycle, ensuring their traceability, consistency, and compliance1. The Architecture Board is the authority that reviews and approves the architecture requirements, as well as the architecture deliverables and artifacts, as part of the architecture governance process2.
References: 1: Architecture Requirements Repository 2: Architecture Board
Question #3
Which phase of the ADM has the purpose to develop an Enterprise Architecture Capability?
- A . Phase G
- B . Preliminary Phase
- C . Phase A
- D . Phase B
Correct Answer: B
B
Explanation
According to the TOGAF Standard, 10th Edition, the Preliminary Phase of the Architecture Development Method (ADM) has the purpose to develop an Enterprise Architecture Capability 1. An Enterprise Architecture Capability is the ability of the organization to perform the activities and tasks related to Enterprise Architecture, such as defining the scope, principles, vision, governance, and stakeholders of the architecture. The Preliminary Phase also establishes the architecture framework, the architecture repository, the architecture tools, and the architecture team 1. The other options are not correct, as they have different purposes in the ADM. Phase G: Implementation Governance has the purpose to ensure that the implementation projects conform to the target architecture 2. Phase A: Architecture Vision has the purpose to define the scope, stakeholders, business drivers, and objectives of the architecture project 3. Phase B: Business Architecture has the purpose to describe the baseline and target business architecture, and to identify the gaps between them.
References: 1: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 6: Preliminary Phase. 2: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 18: Phase G: Implementation Governance. 3: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 12: Phase A: Architecture Vision.: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 13: Phase B: Business Architecture.
B
Explanation
According to the TOGAF Standard, 10th Edition, the Preliminary Phase of the Architecture Development Method (ADM) has the purpose to develop an Enterprise Architecture Capability 1. An Enterprise Architecture Capability is the ability of the organization to perform the activities and tasks related to Enterprise Architecture, such as defining the scope, principles, vision, governance, and stakeholders of the architecture. The Preliminary Phase also establishes the architecture framework, the architecture repository, the architecture tools, and the architecture team 1. The other options are not correct, as they have different purposes in the ADM. Phase G: Implementation Governance has the purpose to ensure that the implementation projects conform to the target architecture 2. Phase A: Architecture Vision has the purpose to define the scope, stakeholders, business drivers, and objectives of the architecture project 3. Phase B: Business Architecture has the purpose to describe the baseline and target business architecture, and to identify the gaps between them.
References: 1: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 6: Preliminary Phase. 2: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 18: Phase G: Implementation Governance. 3: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 12: Phase A: Architecture Vision.: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 13: Phase B: Business Architecture.
Question #4
Complete the sentence A set of architecture principles that cover every situation perceived meets the recommended criteria of_______________
- A . consistency
- B . robustness
- C . stability
- D . completeness
Correct Answer: D
D
Explanation
A set of architecture principles that cover every situation perceived meets the recommended criteria of completeness. Completeness is one of the six criteria that should be applied when developing or assessing architecture principles. Completeness means that there are no gaps or overlaps in the coverage of principles across all relevant aspects of the enterprise’s architecture.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.7 Architecture Principles.
D
Explanation
A set of architecture principles that cover every situation perceived meets the recommended criteria of completeness. Completeness is one of the six criteria that should be applied when developing or assessing architecture principles. Completeness means that there are no gaps or overlaps in the coverage of principles across all relevant aspects of the enterprise’s architecture.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.7 Architecture Principles.
Question #5
Which of the following describes the practice by which the enterprise architecture is managed and controlled at an enterprise-wide level?
- A . Corporate governance
- B . Architecture governance
- C . IT governance
- D . Technology governance
Correct Answer: B
B
Explanation
According to the TOGAF Standard, 10th Edition, architecture governance is “the practice by which enterprise architectures and other architectures are managed and controlled at an enterprise-wide level” 1. Architecture governance ensures that the architecture development and implementation are aligned with the strategic objectives, principles, standards, and requirements of the enterprise, and that they deliver the expected value and outcomes. Architecture governance also involves establishing and maintaining the architecture framework, repository, board, contracts, and compliance reviews 1. The other options are not correct, as they are not the term used by the TOGAF Standard to describe the practice by which the enterprise architecture is managed and controlled at an enterprise-wide level. Corporate governance is “the system by which an organization is directed and controlled” 2, and it covers aspects such as leadership, strategy, performance, accountability, and ethics. IT governance is “the system by which the current and future use of IT is directed and controlled” 2, and it covers aspects such as IT strategy, policies, standards, and services. Technology governance is “the system by which the technology decisions and investments are directed and controlled” 3, and it covers aspects such as technology selection, acquisition, deployment, and maintenance.
References: 1: TOGAF Standard, 10th Edition, Part VI: Architecture Governance, Chapter 44: Introduction. 2: TOGAF Standard, 10th Edition, Part I: Introduction, Chapter 3: Definitions. 3: TOGAF Series Guide: Using the TOGAF Framework to Define and Govern Service-Oriented Architectures, Part II: Using the TOGAF Framework to Define and Govern Service-Oriented Architectures, Chapter 5: Technology Governance.
B
Explanation
According to the TOGAF Standard, 10th Edition, architecture governance is “the practice by which enterprise architectures and other architectures are managed and controlled at an enterprise-wide level” 1. Architecture governance ensures that the architecture development and implementation are aligned with the strategic objectives, principles, standards, and requirements of the enterprise, and that they deliver the expected value and outcomes. Architecture governance also involves establishing and maintaining the architecture framework, repository, board, contracts, and compliance reviews 1. The other options are not correct, as they are not the term used by the TOGAF Standard to describe the practice by which the enterprise architecture is managed and controlled at an enterprise-wide level. Corporate governance is “the system by which an organization is directed and controlled” 2, and it covers aspects such as leadership, strategy, performance, accountability, and ethics. IT governance is “the system by which the current and future use of IT is directed and controlled” 2, and it covers aspects such as IT strategy, policies, standards, and services. Technology governance is “the system by which the technology decisions and investments are directed and controlled” 3, and it covers aspects such as technology selection, acquisition, deployment, and maintenance.
References: 1: TOGAF Standard, 10th Edition, Part VI: Architecture Governance, Chapter 44: Introduction. 2: TOGAF Standard, 10th Edition, Part I: Introduction, Chapter 3: Definitions. 3: TOGAF Series Guide: Using the TOGAF Framework to Define and Govern Service-Oriented Architectures, Part II: Using the TOGAF Framework to Define and Govern Service-Oriented Architectures, Chapter 5: Technology Governance.
Question #6
What is defined as the effect of uncertainty on objectives?
- A . Vulnerability
- B . Risk
- C . Continuity
- D . Threat
Correct Answer: B
B
Explanation
Risk is defined as the effect of uncertainty on objectives, according to the ISO 31000 standard, which provides principles and guidelines for risk management1 Risk can be positive or negative, depending on whether the uncertainty affects the achievement or the failure of the objectives. Risk can also be expressed in terms of likelihood and impact, which indicate the probability and the consequence of the risk occurrence. Risk management is the coordinated activities to direct and control an organization with regard to risk. Risk management is an integral part of the TOGAF standard, as it helps to identify, assess, and treat the risks that may affect the architecture development and implementation2
References: 1: ISO 31000:2018, Risk management ― Guidelines, Clause 3.1 2: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 32: Risk Management
B
Explanation
Risk is defined as the effect of uncertainty on objectives, according to the ISO 31000 standard, which provides principles and guidelines for risk management1 Risk can be positive or negative, depending on whether the uncertainty affects the achievement or the failure of the objectives. Risk can also be expressed in terms of likelihood and impact, which indicate the probability and the consequence of the risk occurrence. Risk management is the coordinated activities to direct and control an organization with regard to risk. Risk management is an integral part of the TOGAF standard, as it helps to identify, assess, and treat the risks that may affect the architecture development and implementation2
References: 1: ISO 31000:2018, Risk management ― Guidelines, Clause 3.1 2: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 32: Risk Management
Question #6
What is defined as the effect of uncertainty on objectives?
- A . Vulnerability
- B . Risk
- C . Continuity
- D . Threat
Correct Answer: B
B
Explanation
Risk is defined as the effect of uncertainty on objectives, according to the ISO 31000 standard, which provides principles and guidelines for risk management1 Risk can be positive or negative, depending on whether the uncertainty affects the achievement or the failure of the objectives. Risk can also be expressed in terms of likelihood and impact, which indicate the probability and the consequence of the risk occurrence. Risk management is the coordinated activities to direct and control an organization with regard to risk. Risk management is an integral part of the TOGAF standard, as it helps to identify, assess, and treat the risks that may affect the architecture development and implementation2
References: 1: ISO 31000:2018, Risk management ― Guidelines, Clause 3.1 2: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 32: Risk Management
B
Explanation
Risk is defined as the effect of uncertainty on objectives, according to the ISO 31000 standard, which provides principles and guidelines for risk management1 Risk can be positive or negative, depending on whether the uncertainty affects the achievement or the failure of the objectives. Risk can also be expressed in terms of likelihood and impact, which indicate the probability and the consequence of the risk occurrence. Risk management is the coordinated activities to direct and control an organization with regard to risk. Risk management is an integral part of the TOGAF standard, as it helps to identify, assess, and treat the risks that may affect the architecture development and implementation2
References: 1: ISO 31000:2018, Risk management ― Guidelines, Clause 3.1 2: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 32: Risk Management
Question #8
Please read this scenario prior to answering the question
Your role is that of a senior architect, reporting to the Chief Enterprise Architect, at a medium-sized company with 400 employees. The nature of the business is such that the data and the information stored on the company systems is their major asset and is highly confidential.
The company employees travel extensively for work and must communicate over public infrastructure using message encryption, VPNs, and other standard safeguards. The company has invested in cybersecurity awareness training for all its staff. However, it is recognized that even with good education as well as system security, there is a dependency on third-parly suppliers of infrastructure and software.
The company uses the TOGAF standard as the method and guiding framework for its Enterprise Architecture (EA) practice. The CTO is the sponsor of the activity.
The Chief Security Officer (CSO) has noted an increase in ransomware (malicious software used in ransom demands) attacks on companies with a similar profile. The CSO recognizes that no matter how much is spent on education, and support, it is likely just a matter of time before the company suffers a significant attack that could completely lock them out of their information assets.
A risk assessment has been done and the company has sought cyber insurance that includes ransomware coverage. The quotation for this insurance is hugely expensive. The CTO has recently read a survey that stated that one in four organizations paying ransoms were still unable to recover their data, while nearly as many were able to recover the data without paying a ransom. The CTO has concluded that taking out cyber insurance in case they need to pay a ransom is not an option.
Refer to the scenario
You have been asked to describe the steps you would take to improve the resilience of the current architecture?
Based on the TOGAF standard which of the following is the best answer?
- A . You would determine business continuity requirements, and undertake a gap analysis of the current Enterprise Architecture. You would make recommendations for change requirements to address the situation and create a change request. You would manage a meeting of the Architecture Board to assess and approve the change request. Once approved you would produce a new Request for Architecture Work to activate an ADM cycle to carry out a project to define the change.
- B . You would monitor for technology changes from your existing suppliers that could improve resilience. You would prepare and run a disaster recovery planning exercise for a ransomware attack and analyze the performance of the current Enterprise Architecture. Using the findings, you would prepare a gap analysis of the current Enterprise Architecture. You would prepare change requests to address identified gaps. You would add the changes implemented to the Architecture Repository.
- C . You would ensure that the company has in place up-to-date processes for managing change to the current Enterprise Architecture. Based on the scope of the concerns raised you recommend that this be managed at the infrastructure level. Changes should be made to the baseline description of the Technology Architecture. The changes should be approved by the Architecture Board and implemented by change management techniques.
- D . You would request an Architecture Compliance Review with the scope to examine the company’s resilience to ransomware attacks. You would identify the departments involved and have them nominate representatives. You would then tailor checklists to address the requirement for increased resilience. You would circulate to the nominated representatives for them to complete. You would then review the completed checklists, identifying and resolving issues. You would then determine and present your recommendations.
Correct Answer: A
A
Explanation
Business continuity is the ability of an organization to maintain essential functions during and after a disaster or disruption. Business continuity requirements are the specifications and criteria that define the acceptable level of performance and availability of the business processes and services in the event of a disaster or disruption. A gap analysis is a technique that compares the current state of the architecture with the desired state, and identifies the gaps or differences that need to be addressed. A change request is a formal proposal for an amendment to some product or system, such as the architecture. A Request for Architecture Work is a document that describes the scope, approach, and expected outcomes of an architecture project123
The best answer is A, because it describes the steps that would improve the resilience of the current architecture, which is the ability to withstand and recover from a ransomware attack or any other disruption.
The steps are:
– Determine the business continuity requirements, which specify the minimum acceptable level of performance and availability of the business processes and services in case of a ransomware attack. This would involve identifying the critical business functions, the recovery time objectives, the recovery point objectives, and the dependencies and resources needed for recovery.
– Undertake a gap analysis of the current Enterprise Architecture, which compares the current state of the architecture with the desired state based on the business continuity requirements. This would involve assessing the strengths and weaknesses of the current architecture, the risks and opportunities for improvement, and the gaps or differences that need to be addressed.
– Make recommendations for change requirements to address the situation and create a change request. This would involve proposing solutions and alternatives to close the gaps, enhance the resilience, and mitigate the risks of the current architecture. The change request would document the rationale, scope, impact, and benefits of the proposed changes, and seek approval from the relevant stakeholders.
– Manage a meeting of the Architecture Board to assess and approve the change request. The Architecture Board is a governance body that oversees the architecture work and ensures compliance with the architecture principles, standards, and goals. The meeting would involve presenting the change request, discussing the pros and cons, resolving any issues or conflicts, and obtaining the approval or rejection of the change request.
– Once approved, produce a new Request for Architecture Work to activate an ADM cycle to carry out a project to define the change. The Request for Architecture Work would describe the scope, approach, and expected outcomes of the architecture project that would implement the approved change request. The Request for Architecture Work would initiate a new cycle of the Architecture Development Method (ADM), which is the core process of the TOGAF standard that guides the development and management of the enterprise architecture.
References: 1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 33:
Business Scenarios 2: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 30: Gap Analysis 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 31: Architecture Change Management: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 7: Request for Architecture Work: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 34: Business Transformation Readiness Assessment: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 30: Gap Analysis: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 31: Architecture Change Management: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 50: Architecture Governance: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 7: Request for Architecture Work
A
Explanation
Business continuity is the ability of an organization to maintain essential functions during and after a disaster or disruption. Business continuity requirements are the specifications and criteria that define the acceptable level of performance and availability of the business processes and services in the event of a disaster or disruption. A gap analysis is a technique that compares the current state of the architecture with the desired state, and identifies the gaps or differences that need to be addressed. A change request is a formal proposal for an amendment to some product or system, such as the architecture. A Request for Architecture Work is a document that describes the scope, approach, and expected outcomes of an architecture project123
The best answer is A, because it describes the steps that would improve the resilience of the current architecture, which is the ability to withstand and recover from a ransomware attack or any other disruption.
The steps are:
– Determine the business continuity requirements, which specify the minimum acceptable level of performance and availability of the business processes and services in case of a ransomware attack. This would involve identifying the critical business functions, the recovery time objectives, the recovery point objectives, and the dependencies and resources needed for recovery.
– Undertake a gap analysis of the current Enterprise Architecture, which compares the current state of the architecture with the desired state based on the business continuity requirements. This would involve assessing the strengths and weaknesses of the current architecture, the risks and opportunities for improvement, and the gaps or differences that need to be addressed.
– Make recommendations for change requirements to address the situation and create a change request. This would involve proposing solutions and alternatives to close the gaps, enhance the resilience, and mitigate the risks of the current architecture. The change request would document the rationale, scope, impact, and benefits of the proposed changes, and seek approval from the relevant stakeholders.
– Manage a meeting of the Architecture Board to assess and approve the change request. The Architecture Board is a governance body that oversees the architecture work and ensures compliance with the architecture principles, standards, and goals. The meeting would involve presenting the change request, discussing the pros and cons, resolving any issues or conflicts, and obtaining the approval or rejection of the change request.
– Once approved, produce a new Request for Architecture Work to activate an ADM cycle to carry out a project to define the change. The Request for Architecture Work would describe the scope, approach, and expected outcomes of the architecture project that would implement the approved change request. The Request for Architecture Work would initiate a new cycle of the Architecture Development Method (ADM), which is the core process of the TOGAF standard that guides the development and management of the enterprise architecture.
References: 1: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 33:
Business Scenarios 2: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 30: Gap Analysis 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 31: Architecture Change Management: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 7: Request for Architecture Work: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 34: Business Transformation Readiness Assessment: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 30: Gap Analysis: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 31: Architecture Change Management: The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 50: Architecture Governance: The TOGAF Standard, Version 9.2, Part II: Architecture Development Method (ADM), Chapter 7: Request for Architecture Work
Question #9
What does the TOGAF ADM recommend for use in developing an Architecture Vision document?
- A . Requirements Management
- B . Architecture Principles
- C . Gap Analysis
- D . Business Scenarios
Correct Answer: D
D
Explanation
Business scenarios are a technique recommended by the TOGAF ADM for use in developing an Architecture Vision document12. Business scenarios are a means of capturing the business requirements and drivers, the processes and actors involved, and the desired outcomes and measures of success34. Business scenarios help to create a common vision and understanding among the stakeholders, and to identify and validate the architecture requirements . Business scenarios also provide a basis for analyzing the impact and value of the proposed architecture.
References:
• The TOGAF Standard, Version 9.2 – Phase A: Architecture Vision – The Open Group
• TOGAF® Standard ― Introduction – Phase A: Architecture Vision
• The TOGAF Standard, Version 9.2 – Definitions – The Open Group
• Business Scenarios – The Open Group
• [The TOGAF Standard, Version 9.2 – Architecture Requirements Specification – The Open Group]
• [The TOGAF Standard, Version 9.2 – Architecture Vision – The Open Group]
• [The TOGAF Standard, Version 9.2 – Business Transformation Readiness Assessment – The Open Group]
D
Explanation
Business scenarios are a technique recommended by the TOGAF ADM for use in developing an Architecture Vision document12. Business scenarios are a means of capturing the business requirements and drivers, the processes and actors involved, and the desired outcomes and measures of success34. Business scenarios help to create a common vision and understanding among the stakeholders, and to identify and validate the architecture requirements . Business scenarios also provide a basis for analyzing the impact and value of the proposed architecture.
References:
• The TOGAF Standard, Version 9.2 – Phase A: Architecture Vision – The Open Group
• TOGAF® Standard ― Introduction – Phase A: Architecture Vision
• The TOGAF Standard, Version 9.2 – Definitions – The Open Group
• Business Scenarios – The Open Group
• [The TOGAF Standard, Version 9.2 – Architecture Requirements Specification – The Open Group]
• [The TOGAF Standard, Version 9.2 – Architecture Vision – The Open Group]
• [The TOGAF Standard, Version 9.2 – Business Transformation Readiness Assessment – The Open Group]
Question #10
Complete the following sentence:
Presenting different_________and_________to stakeholders helps architects to extract hidden agendas
principles and requirements that could impact the final Target Architecture
- A . Alternatives Trade-offs
- B . Solutions Applications
- C . Architecture Views Architecture Viewpoints
- D . Business Scenarios Business Models
Correct Answer: C
C
Explanation
According to the TOGAF Standard, an architecture view is a representation of a system from the perspective of a related set of concerns1. An architecture viewpoint is a specification of the conventions for a particular kind of architecture view1. Presenting different architecture views and architecture viewpoints to stakeholders helps architects to extract hidden agendas, principles, and requirements that could impact the final target architecture. This is because different stakeholders may have different concerns and interests in the system, and by showing them how the system addresses their concerns from different perspectives, the architects can elicit more feedback and validation from them2. For example, a business stakeholder may be interested in the business architecture view, which focuses on the business processes, functions, and capabilities of the system3. A security stakeholder may be interested in the enterprise security view, which addresses the security aspects of the system, such as confidentiality, integrity, and availability3. By presenting these views to the respective stakeholders, the architects can ensure that the system meets their expectations and needs, and also identify any potential issues or gaps that may affect the target architecture.
References: 1: The TOGAF Standard, Version 9.2 – Architectural Artifacts – The Open Group1; 2: Understanding TOGAF Views and Viewpoints in Enterprise Architecture2; 3: Developing Architecture Views – The Open Group4
C
Explanation
According to the TOGAF Standard, an architecture view is a representation of a system from the perspective of a related set of concerns1. An architecture viewpoint is a specification of the conventions for a particular kind of architecture view1. Presenting different architecture views and architecture viewpoints to stakeholders helps architects to extract hidden agendas, principles, and requirements that could impact the final target architecture. This is because different stakeholders may have different concerns and interests in the system, and by showing them how the system addresses their concerns from different perspectives, the architects can elicit more feedback and validation from them2. For example, a business stakeholder may be interested in the business architecture view, which focuses on the business processes, functions, and capabilities of the system3. A security stakeholder may be interested in the enterprise security view, which addresses the security aspects of the system, such as confidentiality, integrity, and availability3. By presenting these views to the respective stakeholders, the architects can ensure that the system meets their expectations and needs, and also identify any potential issues or gaps that may affect the target architecture.
References: 1: The TOGAF Standard, Version 9.2 – Architectural Artifacts – The Open Group1; 2: Understanding TOGAF Views and Viewpoints in Enterprise Architecture2; 3: Developing Architecture Views – The Open Group4