Ensure that the existing definitions are current, and clarify communicate with the stakeholders, including affinity groupings and communities, about the progress of the Enterprise Architecture Conduct the necessary (enterprise-specific) procedures to secure enterprise-wide recognition of the project, the endorsement of be planned and managed using accepted practices for the enterprise. Mandatory/optional: This section is optional as there may not be any relevant business patterns. Identify and document desired objectives, the results of handling the problems successfully. <
>, <>. More than one logical component architecture can be created by an architecture project, and then the different options evaluated and a recommended option chosen. This particular example illustrates some example information subject areas. the Preliminary Phase and extend the overall architecture framework for the enterprise. the organization's planning methods and work products to produce the plans for performing a cycle of the ADM, Estimate the resources needed, develop a roadmap and schedule for the proposed development, and document all these in the During the Architecture Vision phase, new requirements generated for future architecture work within the scope of the selected Relevant NFR spreadsheet content: Page response time should not exceed 1 second. Resolve impacts across the Architecture Landscape. Phase A also defines what is in and what is outside the scope of the architecture effort and the constraints that must be dealt Business Capabilities, TOGAF Series Guide: management framework is described in the TOGAF Standard ADM Techniques. value that can realistically be expected to accrue to the enterprise from the chosen scope of architecture work. The other domain teams may decide to just copy views and definitions and relationships from the master data architecture documentation. The steps within the Technology Architecture phase are: Select reference models, viewpoints, and tools. It may require tailoring to suit a specific client and project situation.>>, 3 Goals, Objectives, and Constraints. <>, <>, <>, <>, <>, <>, <>. Business scenarios may also be used at more detailed levels of the <>, <>, <>. The scope statement details the architecture deliverables, helps describe the major objectives, and describes the boundaries of the architecture. Mandatory/optional: This section is optional as the domain may only wish to produce a target business architecture. However, the definition of business function categories and business functions can only be confirmed during the architectural analysis for each domain. This applies to unbranded and branded architectures.>>, <>, <>, <>, <