a summary of part 1 of togaf

1. TOGAF – A SummaryIntroduction and Core Concepts

2. Where this fits in to TOGAF?

3. What is TOGAF? 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 TOGAF is developed and maintained by members of The Open Group, working with the architecture forum

4. History of TOGAF 1994 the US Department of Defense gave their Technical Architecture Framework for Information Management (TAFIM) to TOGAF for development 1995 TOGAF version 1 was released 2009 TOGAF version 9 was released

6. Architecture Planning

7. Content Framework and MetaModel

8. Capability Based Planning

9. Business Transformation Readiness

10. Architecture Repository

11. Stakeholder Management

12. Security

14. TOGAF Documentation Categorisation Core Fundamental concepts that form the essence of TOGAF Mandated Normative parts of the TOGAF specification Central top its use Would not be recognisable TOGAF if not used Recommended Pool of resources specifically referenced in TOGAF that can be used to assist practitioners Supported Not referenced in the other three categories but can provide valuable assistance

15. What is Enterprise Architecture? Architecture of an Enterprise A formal description of a system, or detailed plan of a system at component level, to guide its implementation OR The structure of components, their inter-relationships, and the guidelines governing their design and evolution over time The highest level ( typically) of description of an organisation and typically covers all missions and functions. An enterprise will often span multiple organisations “An effective enterprise architecture is critical to business survival and success and is the indispensable means to achieving competitive advantage through IT”

16. Why do we need Enterprise Architecture? 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 Good enterprise architecture helps achieve the right balance between IT efficiency and business innovation.

17. Benefits of Enterprise Architecture Create a more efficient IT Operations Lower software development, support and maintenance costs Increased portability of applications Improved interoperability and easier system and network management Improved ability to address critical enterprise-wide issues like security Easier upgrade and exchange of system components Better return on existing investment, reduced risk for future investments Reduced complexity in IT infrastructure Maximum return on investment in existing IT infrastructure Reduced risk overall in new investment, and the costs of IT ownership Faster, simpler and cheaper procurement Buying decisions are simpler, because the information governing procurement is readily available in a coherent plan The procurement process is faster

18. What is an architecture framework Foundational structure used to develop a broad range of different architectures. 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 Set of tools and common vocabulary List of recommended standards

19. Why use TOGAF as an architecture framework 300 Architecture forum members Leading vendors and service providers Neutral and Open Plays an important role “de-mystify” and “de-risk” the architecture development process

20. Core Concepts of TOGAF Enterprise Continuum The organisation structure, roles, responsibilities, skills and process required to practice Enterprise Architecture Is a view of the architecture repository that provides methods for classifying architectures and solution artifacts as they evolve Architecture Capability Architecture Development Method Architecture Continuum Solution Continuum Architecture Repository Deliverables Artifacts Stores different classes of architecture outputs at different levels of abstraction. Architecture Meta-model Building Blocks Reference Library Standards Information Base Techniques and Tools ADM provides a tested and repeatable process for delivering architectures Architecture Landscape

21. Types of architecture domains Enterprise Architecture How the business is organised to met its objectives Business Architecture IT Architecture Information Systems or Applications Architecture How the information System support the objective of the business Data Architecture Structure of the data assets Technology Architecture How the technology fits together

22. Architecture Domains : Definitions Architecture Domain: The architecture area being considered Business architecture: The business strategy, governance, and key business processes information as well as the interaction between these concepts 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 Data architecture: The structure of an organisation’s logical and physical data assets and data management resources 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