TOGAF provides the methods and tools for assisting in the acceptance, production, use, and maintenance of an enterprise architecture. Requests for Architecture Work can be created as an output of the Preliminary Phase, a result of approved architecture Change Requests, or terms of reference for architecture work originating from migration planning. In these circumstances, a Change Request may be submitted in order to kick-start a further cycle of architecture work. TOGAF® 9 Template Artifacts and Deliverables, Set 2 Templates provided by The Open Group Adoption Strategies Working Group to accompany W102 and W103 This is an example set of templates for the TOGAF 9 standard. What standards and reference models need to be considered? (see 32.2.7 Architecture Roadmap), Architecture Vision (see 32.2.4 Architecture Principles), Architecture Repository See Part V, 37. Typical contents of a Tailored Architecture Framework are: 32.2.6 Architecture Requirements Specification, 32.2.9 Business Principles, Business Goals, and Business Drivers, 32.2.14 Implementation and Migration Plan, 32.2.16 Organizational Model for Enterprise Architecture, A system of continuous monitoring to check integrity, changes, decision-making, and audit of all What architectural assets (see 32.2.19 Solution Building Blocks), Statement of Architecture Work work. Typical contents of an Architecture Vision are: Business principles, business goals, and business drivers provide context for architecture work, by describing the may nevertheless have significant implications for the way that architecture is developed. Within organizations that have established architecture functions, there is likely to be a governance framework already in place, but specific processes, organizations, roles, responsibilities, and measures may need to be defined on a project-by-project basis. form a major component of an implementation contract or contract for more detailed Architecture Definition. integration with management frameworks, customization of terminology, development of presentational styles, selection, See Part III, 20. See Part V, 41. start of an architecture development cycle. Phase D (Technology Architecture) describes the development of a Technology Architecture for an architecture project. Requests for Architecture Work typically include: Throughout the ADM, new information is collected relating to an architecture. Business Capability Assessment, including: Baseline state assessment of the performance level of each capability, Future state aspiration for the performance level of each capability, Baseline state assessment of how each capability is realized, Future state aspiration for how each capability should be realized, Assessment of likely impacts to the business organization resulting from the successful deployment of the Target Early agreement on the outcome enables the architects to focus on the This chapter defines the deliverables that will typically be consumed and produced across the TOGAF ADM cycle. configuration, and deployment of architecture tools, etc. groups at what time and in what location, Software services and middleware checklist. The Architecture Definition Document is a companion to the Architecture Requirements Specification, with a Effective communication In these Architecture are identified as intermediate steps. The license is free to any organization wishing to use the TOGAF standard entirely for internal purposes (for example, to develop an information system architecture for use within that organization). This tailoring will include integration with project and process management frameworks, customization of terminology, development of presentational styles, selection, configuration, and deployment of architecture tools, etc. Typical contents of an Organizational Model for enterprise architecture are: This is a document that is sent from the sponsoring organization to the architecture organization to trigger the start of an architecture development cycle. summary version of the full Architecture Definition. Architecture, Baseline and target maturity level of change process, Baseline and target maturity level of operational processes, Baseline capability and capacity assessment, Assessment of the likely impacts to the IT organization resulting from the successful deployment of the Target Many factors that lie outside the consideration of architecture discipline may nevertheless have significant implications for the way that architecture is developed. Typical contents of a Compliance Assessment are: The Implementation and Migration Plan provides a schedule of the projects that will realize the Target Project and portfolio breakdown of implementation: Allocation of work packages to project and portfolio, May include impact on existing portfolio, program, and projects, Benefits of migration, determined (including mapping to business requirements), Governance checkpoints and success/failure criteria, Maturity assessment, gaps, and resolution approach, Roles and responsibilities for architecture team(s), Budget information, financial constraints, External constraints, business constraints, Current architecture/IT system description, Description of resources available to developing organization, Architecture project request and background, Architecture project description and scope, Roles, responsibilities, and deliverables, Tailored architecture content (deliverables and artifacts). Firstly, it is necessary to tailor the TOGAF model for integration into the enterprise. Development of a Communications Plan for architecture allows for this communication to be carried out within a planned and managed likely to be a governance framework already in place, but specific processes, organizations, roles, responsibilities, and measures Identification of mechanisms that will be used to communicate with stakeholders and allow access to architecture information, such as meetings, newsletters, repositories, etc. In these circumstances, a Change Request may be submitted in order to kick-start a further cycle of architecture (see 32.2.11 Change Request), Communications Plan The Statement of Architecture Work defines the scope and approach that will be used to complete an architecture development cycle. (see 32.2.21 Tailored Architecture Framework). Architecture documentation and models from the enterprise's Architecture Repository; see Part IV, 37. Typical contents of a Communications Plan are: Once an architecture has been defined, it is necessary to govern that architecture through implementation to ensure that the original Architecture Vision is appropriately realized and that any implementation learnings are fed back into the architecture process.