Which of the following statements about architecture partitioning are correct*?
1 Partitions are used to simplify the management of the Enterprise Architecture
2 Partitions are equivalent to architecture levels
3 Partitions enable different teams to work on different element of the architecture at the same time.
4 Partitions reflect the organization's structure
Statements 1 and 3 about architecture partitioning are correct. Architecture partitioning is the technique of dividing an architecture into smaller and more manageable parts that can be developed, maintained, and governed independently. Partitions are used to simplify the management of the Enterprise Architecture and to enable different teams to work on different elements of the architecture at the same time. Partitions are not equivalent to architecture levels, which are different degrees of abstraction or detail in an architecture. Partitions do not necessarily reflect the organization's structure, which may change over time or differ from the architecture's scope and boundaries. Reference: The TOGAF Standard | The Open Group Website, Section 2.5 Architecture Partitioning.
Which of the following are interests important to the stakeholders in a system?
Concerns are interests important to the stakeholders in a system. They are used to identify and classify the system's stakeholders and to guide the selection of viewpoints for the architecture description. Reference: The TOGAF Standard | The Open Group Website, Section 3.2.1 Architecture Viewpoints
What component of the Architecture Repository represents architecture requirements agreed with the Architecture Board?
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.
Which of the following is a responsibility of an Architecture Board?
Providing the basis for all decision-making with regard to the architectures
Consistency between sub-architectures
Establishing targets for re-use of components
Flexibility of the Enterprise Architecture: To meet changing business needs To leverage new technologies
Enforcement of Architecture Compliance
Improving the maturity level of architecture discipline within the organization
Ensuring that the discipline of architecture-based development is adopted
Supporting a visible escalation capability for out-of-bounds decisions
1: Architecture Board - The Open Group3
2: TOGAF Standard, Version 9.2 - Part VI: Architecture Governance Framework - Architecture Board
Please read this scenario prior to answering the question
Your role is that of a consultant to the Lead Enterprise Architect to an international supplier of
engineering services and automated manufacturing systems. It has three manufacturing plants
where it assembles both standard and customized products for industrial production
automation. Each of these plants has been operating its own planning and production
scheduling systems, as well as applications and control systems that drive the automated
production line.
The Enterprise Architecture department has been operating for several years and has mature,
well-developed architecture governance and development processes that are based on the
TOGAF Standard. The CIO sponsors the Enterprise Architecture.
During a recent management meeting, a senior Vice-President highlighted an interview where
a competitor company's CIO is reported as saying that their production efficiency had been
improved by replacing multiple planning and scheduling systems with a common Enterprise
Resource Planning (ERP) system located in a central data center. Some discussion followed,
with the CIO responding that the situations are not comparable, and the current architecture is
already optimized.
In response, the Architecture Board approved a Request for Architecture Work covering the
investigations to determine if such an architecture transformation would lead to improvements
in efficiency. You have been assigned to support the architecture team working on this project.
A well-known concern of the plant managers is about the security and reliability of driving their
planning and production scheduling from a remote centralized system. Any chosen system
would also need to support the current supply chain network consisting of local partners at
each of the plants.
Refer to the scenario
You have been asked to explain how you will initiate the architecture project.
Based on the TOGAF Standard, which of the following is the best answer?
The best answer is C. You would hold a series of interviews at each of the manufacturing plants using the business scenarios technique. This will allow you to understand the systems and integrations with local partners. You would use stakeholder analysis to identify key players in the engagement, and to understand their concerns. You will then identify and document the key high-level stakeholder requirements for the architecture. You will then generate high level definitions of the baseline and target architectures.
Establish the architecture project
Identify stakeholders, concerns, and business requirements
Confirm and elaborate business goals, business drivers, and constraints
Evaluate business capabilities
Assess readiness for business transformation
Define scope
Confirm and elaborate Architecture Principles, including business principles
Develop Architecture Vision
Define the Target Architecture value propositions and KPIs
Identify the business transformation risks and mitigation activities
Secure stakeholder and sponsor approval
The other answers are not the best approach for architecture development, because:
Answer A focuses on researching vendor literature and conducting briefings with vendors, which is not the best way to understand the business needs and the current situation of the enterprise. Answer A also defines a preliminary Architecture Vision without involving the stakeholders or validating the requirements, which may lead to misalignment and lack of consensus.
Answer B conducts a pilot project that will enable vendors to demonstrate potential solutions, which is premature and costly at this stage of the architecture project. Answer B also does not address the stakeholder concerns or the current systems and integrations, which may result in gaps and risks. Answer B also develops the requirements after the pilot project, which may not reflect the actual business needs and goals.
Answer D develops baseline and target architectures for each of the manufacturing plants, which may not consider the enterprise-wide perspective and the potential benefits of a common ERP system. Answer D also does not involve the stakeholders or address their concerns, which may result in resistance and conflict. Answer D also does not define the business case or the performance metrics, which are essential for demonstrating the value and feasibility of the architecture.
