What is TOGAF?<br />The Open Group Architecture Framework is a framework – a detailed method and a set of supporting tools – for developing an enterprise architecture for use within that organisation<br />TOGAF is developed and maintained by members of The Open Group, working with the architecture forum<br />
History of TOGAF<br />1994 the US Department of Defense gave their Technical Architecture Framework for Information Management (TAFIM) to TOGAF for development<br />1995 TOGAF version 1 was released<br />2009 TOGAF version 9 was released <br />
What was new in TOGAF 9<br />Design objectives<br />Evolution not revolution<br />No change to the top level processes<br />Interoperability between TOGAF 8 and 9<br />Stronger links to business<br />Strategic Planning<br />Deployment decisions<br />Easier to use<br />A More formal meta-model<br />More guidelines and techniques<br />Improved structure<br /><ul><li>New sections
SOA</li></li></ul><li>Components of TOGAF 9<br />High level introduction and key concepts, definition of terms and release notes<br />Introduction and Core Concepts ( Part 1)<br />TOGAF ADM <br />and <br />Content Framework<br />Architecture Development Method (Part 2)<br />Core of TOGAF, a step by step guide to developing enterprise architecture<br />ADM Guidelines and Techniques<br />(Part 3)<br />Collections of Guidelines and Techniques to apply with using ADM<br />Architecture Content Framework<br />(Part 4)<br />Structured Meta-model for architectural artifacts. Re-useable architecture building blocks<br />TOGAF Enterprise <br />Continuum & Tools<br />Enterprise Continuum and Tools (Part 5)<br />Taxonomies and tools to categorise and store outputs<br />TOGAF Reference Models ( Part 6)<br />Two reference models that can be applied to EA<br />TOGAF Capability <br />Framework<br />Architecture Capability Framework<br />(Part 7)<br />How to establish and operate EA with an Organisation<br />
TOGAF Documentation Categorisation<br />Core<br />Fundamental concepts that form the essence of TOGAF<br />Mandated<br />Normative parts of the TOGAF specification<br />Central top its use<br />Would not be recognisable TOGAF if not used<br />Recommended<br />Pool of resources specifically referenced in TOGAF that can be used to assist practitioners<br />Supported<br />Not referenced in the other three categories but can provide valuable assistance<br />
What is Enterprise Architecture?<br />Architecture of an Enterprise<br />A formal description of a system, or detailed plan of a system at component level, to guide its implementation<br />OR<br />The structure of components, their inter-relationships, and the guidelines governing their design and evolution over time<br />The highest level ( typically) of description of an organisation and typically covers all missions and functions. An enterprise will often span multiple organisations<br />“An effective enterprise architecture is critical to business survival and success and is the indispensable means to achieving competitive advantage through IT”<br />
Why do we need Enterprise Architecture?<br />Optimise the often fragmented legacy of processes (both manual and automated) into an integrated environment that is responsive to change and supportive of the delivery of the business strategy<br />Good enterprise architecture helps achieve the right balance between IT efficiency and business innovation.<br />
Benefits of Enterprise Architecture<br />Create a more efficient IT Operations<br />Lower software development, support and maintenance costs<br />Increased portability of applications<br />Improved interoperability and easier system and network management<br />Improved ability to address critical enterprise-wide issues like security<br />Easier upgrade and exchange of system components<br />Better return on existing investment, reduced risk for future investments<br />Reduced complexity in IT infrastructure<br />Maximum return on investment in existing IT infrastructure<br />Reduced risk overall in new investment, and the costs of IT ownership<br />Faster, simpler and cheaper procurement<br />Buying decisions are simpler, because the information governing procurement is readily available in a coherent plan<br />The procurement process is faster<br />
What is an architecture framework<br />Foundational structure used to develop a broad range of different architectures. <br />Provides a method to help design a target state of the enterprise in terms of building blocks, and to show how the building blocks fit together<br />Set of tools and common vocabulary<br />List of recommended standards<br />
Why use TOGAF as an architecture framework<br />300 Architecture forum members<br />Leading vendors and service providers<br />Neutral and Open<br />Plays an important role “de-mystify” and “de-risk” the architecture development process<br />
Core Concepts of TOGAF<br />Enterprise Continuum<br />The organisation structure, roles, responsibilities, skills and process required to practice Enterprise Architecture<br />Is a view of the architecture repository that provides methods for classifying architectures and solution artifacts as they evolve <br />Architecture Capability <br />Architecture Development Method<br />Architecture Continuum<br />Solution Continuum<br />Architecture Repository <br />Deliverables<br />Artifacts<br />Stores different classes of architecture outputs at different levels of abstraction.<br />Architecture Meta-model<br />Building <br />Blocks<br />Reference Library<br />Standards Information Base<br />Techniques <br />and Tools<br />ADM provides a tested and repeatable process for delivering architectures<br />Architecture Landscape<br />
Types of architecture domains<br />Enterprise <br />Architecture<br />How the business <br />is organised to met<br />its objectives<br />Business Architecture<br />IT Architecture<br />Information Systems or <br />Applications Architecture <br />How the information<br />System support the objective of the business<br />Data Architecture <br />Structure of the data assets<br />Technology Architecture<br />How the technology <br />fits together<br />
Architecture Domains : Definitions<br />Architecture Domain: The architecture area being considered<br />Business architecture: The business strategy, governance, and key business processes information as well as the interaction between these concepts<br />Application architecture: A description of the major logical groups of capabilities that manage the data objects necessary to process the data and support the business<br />Data architecture: The structure of an organisation’s logical and physical data assets and data management resources<br />Technology architecture : The Logical software and hardware capabilities that are required to support deployment of business, data and application services, includes middleware, networks, communications etc<br />
A particular slide catching your eye?
Clipping is a handy way to collect important slides you want to go back to later.