Where an ABB from the baseline architecture is missing in the target architecture, each must be reviewed. clarify any areas of ambiguity. Governance, TOGAF Series Guide: The diagram below provides an example view of the baseline data architecture at the logical level which consists of logical data entities and the relationships between them. The reader should readily discern the answer to: How does this affect me? It is important not to oversimplify, trivialize, or judge the merit of the impact. enterprise to develop and consume the architecture. <>, <>, <>. This section should follow the same structure as the logical target technology architecture.>>, <>, <>, <>, <>. Stakeholders who need to review the business architecture and this document, Stakeholders who need to approve the business architecture and this document, Decision-making stakeholders in terms of governance and management such as scope confirmation, issue escalation, and issue resolution (if not already defined elsewhere; for example, in a project initiation document (PID)), Concerns of these stakeholders with regards to the business architecture or this exercise, Issues of these stakeholders with regards to the business architecture or this exercise>>, The priority of the capabilities in a list>>, Any other relevant business architecture documentation, Context around any such relevant business architecture documentation; e.g., validity, ownership, purpose, Any assumptions regarding the business architecture documentation, Relevant views (diagrams) illustrating the business functions in scope for the current business architecture, Description of the business function view(s), Definitions for the business functions (in table format) in scope for the current business architecture, Relevant views (diagrams) illustrating the organization structure and units in scope for the current business architecture, Description of the organization structure and units view(s), Definitions for the organization structure and units (in table format) in scope for the current business architecture, Relevant views (diagrams) at the conceptual level illustrating the conceptual business services and their contracts (interactions) in scope for the current business architecture, Description of the conceptual- level view(s) in order to understand the architectural decisions that have been taken and resulting key messages for the stakeholders, Definitions for the conceptual business services (in table format) in scope for the current business architecture, Characteristics of the conceptual business services (in table format) in scope for the current business architecture, Descriptions of the contracts (interactions) between the conceptual business services (in table format) in scope for the current business architecture, If required, characteristics of the contracts (interactions) between the business services (in table format) in scope for the current business architecture, Relevant views (diagrams) at the logical level illustrating the business processes in scope for the current business architecture, Description of the logical level view(s) in order to understand the architectural decisions that have been taken and resulting key messages for the stakeholders, Definitions for the business processes (in table format) in scope for the current business architecture, Any relationships between the business function categories, business functions, business service categories, and business services that are in scope for the current business architecture, Any assumptions that have been used to define the current business architecture>>, Human (system) roles in the baseline architecture, Computer (system) roles in the baseline architecture>>, Human (system) actors in scope for the baseline architecture, Computer (system) actors in scope for baseline architecture, Any other system actor oriented requirements in scope for the target architecture>>, Human actors in scope for the target architecture>>, Computer actors and roles in scope for target architecture>>, Any other actor-oriented requirements in scope for the target architecture>>, Relevant views (diagrams) at the planning level illustrating the information subject areas in scope for the baseline data architecture, as well as the relationships between them, Description of the planning-level view(s) for the baseline data architecture in order to understand the architectural decisions that have been taken and resulting key messages for the stakeholders, Definitions for the information subject areas (in table format) in scope for the baseline data architecture, Descriptions of the relationships and cardinality (if relevant) between the information subject areas (in table format) in scope for the baseline data architecture, Relevant views (diagrams) at the conceptual level illustrating the business objects in scope for the baseline data architecture, as well as the relationships between them; these medium-level business objects will have been derived from the high-level information subject areas, Description of the conceptual-level view(s) for the baseline data architecture in order to understand the architectural decisions that have been taken and resulting key messages for the stakeholders, Definitions for the business objects (in table format) in scope for the baseline data architecture, Descriptions of the relationships and cardinality (if relevant) between the business objects (in table format) in scope for the baseline data architecture, Relevant views (diagrams) at the logical level illustrating the logical data entities in scope for the baseline data architecture, as well as the relationships between them. TOGAF ADM Guide-Through 4. They make the arguments and decisions more explicit and traceable, so they are a guide in decision- making and an aid for structuring services. Additional services can be identified by considering how the main services, when implemented, will be instantiated, started up, shut down, configured, monitored, and how faults will be diagnosed, users maintained, new business configuration items added (e.g., products) and so on. Content). When the exercise is complete, anything under Eliminated or New is a gap, which should either be explained as correctly eliminated, or marked as to be addressed by reinstating or developing/procuring the function. The TOGAF Library is maintained under the governance of The Open Group Architecture Forum. E-ISSN : 2540 - 8984 JIPI (Jurnal Ilmiah Penelitian dan Pembelajaran Informatika) Volume 07, Nomor 04, Desember 2022 : 1251 - 1262 1254 Fig. >. the Architecture Vision. Transformation Risks and Mitigation Activities, 3.3.11 Develop Statement of Architecture These views will illustrate the business processes in the baseline business architecture. These use within that organization). It describes the Communications Plan for your project. <