Togaf: Open Group Architecture Framework PDF

TOGAF The Open Group Architecture Framework TOGAF The Open Group Architecture Framework (TOGAF) is a framework a detailed method and a set of supporting tools for developing an enterprise architecture. -It may be used freely by any organization wishing to develop an enterprise architecture f...

TOGAF The Open Group Architecture Framework TOGAF The Open Group Architecture Framework (TOGAF) is a framework a detailed method and a set of supporting tools for developing an enterprise architecture. -It may be used freely by any organization wishing to develop an enterprise architecture for use within that organization Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html TOGAF is....  The Open Group Architecture Forum ◼ Architecture Framework (TOGAF) ◼ Architecture Tools  TOGAF is freely available for internal use of organizations 3 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html Difference with other frameworks  Other Frameworks list deliverables but do not say ‘how’  TOGAF can be used in companion with other frameworks to deliver their deliverables  TOGAF is a framework by itself, it can be used by its own to prepare its own deliverables , too! 4 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html architecture domains does TOGAF cover?  TOGAF 8.1 : ◼ Technology Architecture ◼ Application Architecture ◼ Data Architecture ◼ Business Architecture  TOGAF 7 only covered Technology Architecture 5 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html TOGAF components  ADM (Architecture Development Method)  Enterprise Continuum  Resource Base 6 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html  TOGAF Components ADM (Architecture Development Method) Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html ADM (Architecture Development Method) 8 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html Key points about ADM  ADM might need adoption due to : ◼ The enterprise ‘s circumstances ◼ To be integrated with another framework  ADM is iterative, over the whole process, between phases, and within phases.  For each iteration of ADM decide about: ◼ The scope ◼ What needs to be leveraged in the organization's Enterprise Continuum 9 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html About scoping  It has to be done for every architectural activity  We have to scope because of limitations in time, human resource and finance  Scoping dimensions: ◼ Horizontal scope (enterprise scope) ◼ Architecture domains ◼ Vertical scope (level of detail)  Scoping decision made must create value to the enterprise 10 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html ADM Phases  A-H phases  For each phase, TOGAF 8.1 has defined : ◼ Objectives ◼ Approach ◼ Inputs ◼ Steps ◼ Outputs 11 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html ADM preliminary phase  Make sure all who should be involved are committed  Define architecture principles and assumptions  List the people performing it and their locations and responsibilities  Define framework and methodology  Define procedures for evaluation 12 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html ADM Phase A: Architecture Vision  validate the business principles, business goals, and strategic business drivers of the organization  define the scope of, and to identify and prioritize the components of the current architecture effort  define the relevant stakeholders, and their concerns and objectives.  define the key business requirements to be addressed in this architecture effort, and the constraints that must be dealt with  secure formal approval to proceed 13 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html ADM Phase B : Business Architecture  describe the current baseline business architecture (using modeling tools such as UML)  develop a target Business Architecture, describing the product and/or service strategy, and the organizational, functional, process, information, and geographic aspects of the business environment, based on the business principles, business goals, and strategic drivers.  analyze the gaps between the baseline and target Business Architectures 14 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html ADM Phase C :Information System Architecture  develop target architectures covering either or both (depending on project scope) of the Data and Application Systems domains.  Data: define the major types and sources of data necessary to support the business – define data entities – no database design  Applications: define the major kinds of application system necessary to process the data and support the business – described as logical groups of capabilities– without reference to particular technologies – stable and relatively unchanging over time, whereas the technology used to implement them will change over time 15 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html ADM Phase D : Technology Architecture  develop a technology architecture that will form the basis of the following implementation work  As part of this Phase, the architecture team will need to consider what relevant technology architecture resources are available in the Architecture Continuum like TOGAF Technical Reference Model (TRM) 16 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html ADM Phase E : Opportunities and Solutions  evaluate and select among the implementation options identified in the development of the various target architectures (for example, build vs. buy vs. reuse options)  identify the strategic parameters for change, and the top-level work packages or projects to be undertaken in moving from the current environment to the target  generate an overall implementation and migration strategy 17 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html ADM Phase F : Migration Planning  to sort the various implementation projects into priority order  Generate a detailed implementation plan 18 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html ADM Phase G : Implementation Governance  formulate recommendations for each implementation project  perform appropriate governance functions while the system is being implemented and deployed  ensure conformance with the defined architecture 19 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html ADM Phase H : Architecture Change Management  provide for the continual monitoring of such things as new developments in technology and changes in the business environment, and for determining whether to formally initiate a new architecture evolution cycle 20 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html ADM Architecture Requirements Management  not a static set of requirements, but a dynamic process whereby requirements for enterprise architecture and subsequent changes to those requirements are identified, stored, and fed into and out of the relevant ADM phases.  Changes such as changing market conditions, new legislation, etc. 21 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html  Enterprise Continuum  A repository of reusable building blocks  ADM both uses (ready building blocks) from and adds (organization-specific building blocks) to it  Contains : ◼ Work in progress ◼ Previous work done in this organization ◼ Reference models and patterns  Sample content: ◼ In the development of a Technology Architecture, this may be TOGAF's own Foundation Architecture. ◼ In the development of a business architecture, it may be a reference model for e-Commerce taken from the industry at large. 22 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html Enterprise Continuum  TOGAF views the world of enterprise architecture as a continuum of architectures, ranging from highly generic to highly specific. Enterprise Continuum Read details about the components in this picture, here. 24 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html Enterprise Continuum  specifies a progression for developing architectures and solutions using architecture building blocks and solution building blocks in a continuous, iterative fashion.  A building block is simply a grouping of functionality defined to meet business needs. An architecture building block is described with a general level of detail. Solution building blocks reflect real products or specific custom developments.  The TOGAF ADM guides you through the left-to-right progression from the general architectures and solutions (on the left), to organization-specific ones (on the right).  The relationship between the Architecture Continuum and the Solutions Continuum is one of guidance, direction, and support. You build an architecture by navigating the two continuums, from left to right, top to bottom, so that you are specifying architecture building blocks at each stage, and then the solution building blocks that implement them, and continuing rightward, building upon the solution and adding increasing detail. 25 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html About the Enterprise Continuum components  A Foundation Architecture consists of architecture building blocks and corresponding standards that support a complete computing environment. TOGAF's pre-supplied Foundation Architecture consists of the Technical Reference Model and Standards Information Base.  A Common System Architecture is complete in terms of a particular problem domain, but incomplete in terms of the overall information system functionality. Examples of Common Systems Architectures are a Network Architecture, or a Security Architecture. A System Solution is an implementation of a Common System Architecture comprising a set of products and services.  Industry Architectures include pre-built, off-the-shelf architectures that have been developed for particular vertical industries. These often include pre-built data models and business processes. An Industry Solution is an implementation of an Industry Architecture. 26 Reference-http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap01.html