In such cases, the activity in Phase A is concerned with verifying and understanding the documented business strategy in the Preliminary Phase or clarified as part of Phase A. The activity in Phase A is concerned Architecture Vision Document contains: Constraints are similar to principles but they have no weighting. Phase A - Architecture Vision: Objectives. discussed in Scoping the Architecture . Results focused, works tirelessly to ensure business stakeholders' concerns are met on time and defect free. understanding at this stage which stakeholders and which views need to be developed is important in setting the scope of the For the Architecture Vision it is recommended that first an overall architecture be decided upon showing how all of the various <>, <>, <>, <>, <>, <>, <>. This will involve ensuring that: The outputs of Phase A may include, but are not restricted to: The TOGAF Standard Architecture Content contains a detailed description of This template shows typical contents of an Architecture Vision and can be adapted to align with any TOGAF adaptation being implemented. This particular example illustrates some of the information subject areas that exist. Often models like that shown below are used for this View.>>, <>. Phase D: Technology Architecture. outlined in the Architecture Vision, Architecture reference materials (see the, Business principles, business goals, and business drivers (see the, Organizational Model for Enterprise Architecture (see the, Maturity assessment, gaps, and resolution approach, Roles and responsibilities for architecture team(s), Tailored architecture content (deliverables and artifacts), Populated Architecture Repository (see the, Identify stakeholders, concerns, and business requirements (see, Confirm and elaborate business goals, business drivers, and constraints (see, Assess readiness for business transformation (see, Confirm and elaborate Architecture Principles, including business principles (see, Define the Target Architecture value propositions and KPIs (see, Identify the business transformation risks and mitigation activities (see, Develop Statement of Architecture Work; secure approval (see, To identify candidate vision components and requirements to be tested as the Architecture Vision is developed, To identify candidate scope boundaries for the engagement to limit the extent of architectural investigation required, To identify stakeholder concerns, issues, and cultural factors that will shape how the architecture is presented and This scope and circulation of this view must be agreed in advance.>>, <>, <>, High-level business and technology goals that are driving this exercise and thus which this business architecture and document are meant to help achieve, Precise objectives (derived from the goals) that are driving this exercise and thus which this business architecture and document are meant to help achieve, Business or technology constraints that need to be taken into consideration as they may influence the decisions made when defining the business architecture, Other constraints that need to be taken into consideration as they may impact the delivery (e.g., timescales) of this document and thus exercise>>, High-level business and technology goals that are driving this exercise and thus which this business architecture and document are meant to help achieve>>, Precise objectives (derived from the goals) that are driving this exercise and thus which this business architecture and document are meant to help achieve>>. This section should follow the same structure as the logical target technology architecture.>>, <>, <>, <>, <>, <>. See the architecture objectives artifact template. 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. For an introduction to value streams, see the TOGAF Series Guide: Value Phase H: Architecture Change Management, 13. Once an Architecture Vision is defined and documented in the Statement of Architecture Work, it is critical to use it to build a project, at a high level. It contains detailed information about complaints and positive features of the current subject areas.>>, <>. However, it can also be used by the domains that do not produce a full (current and target) or current state business architecture but still want to know the (priority) areas on which to concentrate, and thus minimise effort. <>. Text describing the key concepts and notation used within the diagram will also need to be included so that users can easily read and understand the view.>>, <>, <>, <>, <