카테고리 The Open Group

According to the TOGAF Standard, an enterprise is defined as any collection of organizations that has a common set of goals and/or a single bottom line1. The examples given in the question are all types of enterprises that can be the subject of enterprise architecture1.
In the context of TOGAF, the term ‘enterprise’ encompasses more than just a single organization. It refers to any collection of organizations that has a common set of goals. This can include, as described in the statements provided, entire corporations or their divisions, government agencies or departments, as well as business partnerships such as consortia or supply chains. TOGAF uses the term ‘enterprise’ to define the full scope of the entity that is the subject of planning, design, implementation, and operation of an Enterprise Architecture.

The development of Business Architecture Descriptions is always iterative because it involves constant refinement and validation of the architecture models and views based on stakeholder feedback and changing requirements. Therefore, any Architecture Description that was created in Phase A may need to be updated in Phase B as new information or insights emerge. Phase B does not require that all Architecture Descriptions be updated, only those that are relevant and necessary for the Business Architecture. Phase B is an ADM Architecture Development phase, but that does not explain why Architecture Descriptions need to be updated. A new value stream may or may not require updating existing Architecture Descriptions depending on its scope and impact.

In the TOGAF ADM (Architecture Development Method), Phase B is the Business Architecture phase.
During this phase, the information map, which represents the relationships and flow of information within the business, is linked to other business blueprints. This linkage is crucial to ensure that the business architecture is aligned with the data and information needs of the organization, providing a foundation for the development of subsequent architecture domains (Data, Application, and Technology Architectures).

Phase E Explanation of Correct answer: In Phase E (Opportunities and Solutions) of the TOGAF Explanation:ADM, the information map is linked to other business blueprints such as the Business Capability Map, the Value Stream Map, and the Business Process Model Phase E Explanation of Correct answer: In Phase E (Opportunities and Solutions) of the TOGAF Explanation:ADM, the information map is linked to other business blueprints such as the Business Capability Map, the Value Stream Map, and the Business Process Model2. This helps to identify and prioritize opportunities for business improvement and transformation2.
In the TOGAF Architecture Development Method (ADM), the information map is linked to other business blueprints during Phase B, Business Architecture. This phase involves the development of a business architecture to support an agreed Architecture Vision. It is during this phase that the information architecture is developed in detail, which involves mapping the information to the business, hence linking the information map to other business blueprints.

The development of Business Architecture Descriptions is always iterative because it involves constant refinement and validation of the architecture models and views based on stakeholder feedback and changing requirements. Therefore, any Architecture Description that was created in Phase A may need to be updated in Phase B as new information or insights emerge. Phase B does not require that all Architecture Descriptions be updated, only those that are relevant and necessary for the Business Architecture. Phase B is an ADM Architecture Development phase, but that does not explain why Architecture Descriptions need to be updated. A new value stream may or may not require updating existing Architecture Descriptions depending on its scope and impact.
In TOGAF’s ADM, the development of architecture is an iterative process. During Phase A, initial business capability maps and value streams are created to establish the Architecture Vision. However, as stakeholders provide more detailed inputs and requirements are refined, it is necessary to update the Architecture Descriptions. This is an iterative process that continues into Phase B, Business Architecture, where these descriptions are further developed and refined.

The provided representation of a business model appears to be a variant of the Business Model Canvas, which is a strategic management template for developing new or documenting existing business models. It is a visual chart with elements describing a firm’s value proposition, infrastructure, customers, and finances. The model assists firms in aligning their activities by illustrating potential trade-offs. Since none of the options precisely match the Business Model Canvas and the Four Box Framework is conceptually closest to the Business Model Canvas, option B is the best available answer, albeit not a perfect match.

According to the TOGAF Series Guide: Business Capabilities, after documenting all of the business capabilities, the next step is to organize them in a logical manner1. This can be done by using techniques such as layering, sorting, mapping, and leveling1. These techniques can help to classify, group, and align capabilities into categories for a deeper understanding of how they support the business goals and objectives1. Organizing the business capabilities can also help to identify dependencies, gaps, overlaps, or redundancies among them1.

One of the reasons that supports the need to govern Enterprise Architecture is that best practice governance enables the organization to control value realization6. Value realization is the process of ensuring that the expected benefits from implementing an Enterprise Architecture are achieved and sustained over time6. Best practice governance provides a framework and mechanisms for monitoring and evaluating the performance and outcomes of Enterprise Architecture initiatives, as well as ensuring alignment with strategic objectives and stakeholder expectations.

이 예에 표시된 기법을 히트 매핑이라고 합니다. 비즈니스 역량 맵에 성숙도, 효율성, 성과, 각 역량의 비즈니스에 대한 가치 또는 비용 기여도 등 다양한 관점을 표시하는 데 사용할 수 있는 기법입니다2. 다양한 속성에 따라 비즈니스 역량 맵에서 각 역량의 색상이 결정됩니다. 히트 매핑은 비즈니스 아키텍처의 강점, 약점, 기회 및 위협을 식별하는 데 도움이 될 수 있습니다.

Value networks are primarily concerned with identifying the participants involved in creating and delivering value. They focus on the interactions between different stakeholders, including customers, suppliers, partners, and internal departments. This approach helps in understanding how value is exchanged and co-created across the network, highlighting the roles and relationships that contribute to the overall value delivery.

The TOGAF standard covers the development of four architecture domains: Business, Data, Technology, and Application. The Application Architecture domain defines the applications required to process the data and support the business functions.
The TOGAF standard describes the development of four architecture domains, which are considered its pillars.
These are Business, Data, Technology, and Application. The Application Architecture domain provides a blueprint for the individual application systems to be deployed, their interactions, and their relationships to the core business processes of the organization.

가치 흐름 매핑(VSM)은 다양한 이해관계자를 위해 가치를 창출, 포착, 전달하는 조직의 효율성을 평가하는 데 사용되는 강력한 도구입니다. 여기에는 가치 창출의 전체 프로세스를 처음부터 끝까지 매핑하고, 관련된 각 단계를 식별하고, 각 단계에서 가치가 어떻게 추가되는지 분석하는 작업이 포함됩니다.
VSM은 병목 현상, 비효율성, 개선 기회를 파악하여 궁극적으로 가치 전달 프로세스를 최적화하여 이해관계자의 요구 사항을 더 잘 충족하는 것을 목표로 합니다.

TOGAF 비즈니스 역량 가이드 V2에 따르면 비즈니스 역량은 "조직이 핵심 기능을 수행하기 위해 필요한 역량, 자료 및 전문 지식의 표현 또는 표현"5으로 정의됩니다. 비즈니스 역량은 역할, 정보, 프로세스 및 기술의 네 가지 요소로 분해할 수 있습니다5. 주어진 예에서 A는 역할을, C는 정보를 나타냅니다.
In the context provided in the image, ‘A’ refers to the roles involved in the recruitment management process, which in this case is the ‘User: Recruiter’ and the ‘Stakeholders: Manager, Candidate Employee’. ‘C’ refers to the information or data aspects of the process, which includes ‘Candidate/Applicant Details’, ‘Position Descriptions’, ‘Recruitment Agency Data’, and ‘Industry Standard Role Definitions’. Thus, ‘A’ corresponds to ‘Roles’ and ‘C’ to ‘Information’.

Business scenarios are most prominently used in Phase A (Architecture Vision) of the TOGAF ADM. In this phase, they help in discovering and documenting business requirements by providing detailed and realistic descriptions of business situations. Business scenarios help in identifying the key business drivers, goals, and challenges, ensuring that the architecture development is aligned with the actual needs of the business.

Phase A of the TOGAF ADM (Architecture Development Method), also known as the Architecture Vision phase, focuses on defining the problem to be solved, identifying stakeholders, their concerns, and requirements. Here’s a detailed explanation:
Phase A: Architecture Vision:
Objective: The primary objective of Phase A is to establish a high-level vision of the architecture project, including defining the scope and identifying key stakeholders and their concerns.
Problem Definition: This phase involves clearly defining the business problem or opportunity that the architecture project seeks to address. This sets the stage for all subsequent architecture work.
Stakeholder Identification:
Identification and Analysis: Stakeholders are identified and their concerns and requirements are gathered.
This includes business leaders, IT leaders, end-users, and other relevant parties.
Understanding Needs: Understanding the needs and expectations of stakeholders is crucial for ensuring that the architecture aligns with business objectives and addresses key concerns.
Requirements Gathering:
High-Level Requirements: In Phase A, high-level requirements are identified and documented. These requirements guide the development of the architecture vision and provide a basis for more detailed requirements in later phases.
Requirements Management: A requirements management process is established to ensure that stakeholder needs are continuously captured, analyzed, and addressed throughout the architecture development process.
TOGAF References:
Deliverables: Key deliverables of Phase A include the Architecture Vision document, stakeholder map, and high-level requirements.
ADM Guidelines: TOGAF provides guidelines and techniques for conducting Phase A, including methods for stakeholder analysis, problem definition, and developing the architecture vision.
In summary, Phase A of the TOGAF ADM focuses on defining the problem to be solved, identifying stakeholders, understanding their concerns and requirements, and developing a high-level architecture vision that aligns with business objectives.