Introduction To TOGAF 9.1
Introduction to Enterprise Architecture Framework And TOGAF Konakanchi Srinivasa Rao
What is an EnterpriseWhat is an ArchitectureWhat is Enterprise ArchitectureWhy Enterprise ArchitectureWhat is an Architecture FrameworkTop Architecture FrameworksTOGAF...
AgendaA collection of organizations that share a common set of goals Government agency Part of a corporation CorporationLarge corporations may comprise multiple enterprisesextended enterprise including partners, suppliers and customersWhat is an Enterprise?
Example for Enterprise: P&G
P&G Global Brands
An Architecture is the fundamental organization of something, embodied in: its components, their relationships to each other and the environment its design and evolution.What is an Architecture?
The organizing logic for business processes and IT infrastructure reflecting the integration and standardization requirements of the firms operating model
A conceptual blueprint that defines the structure and operation of an organization. The intent of an enterprise architecture is to determine how an organization can most effectively achieve its current and futureWhat is Enterprise Architecture?
Example for Enterprise ArchitectureEnterprise Architecture: The analysis and documentation of an enterprise in its current and future states from a strategy, business, and technology perspective.
Capabilitiesof the CurrentEnterpriseCapabilitiesof the FutureEnterpriseEmerging Technologies(IT Support Team)New Business Priorities(Management Team)New Direction & Goals(Leadership Team)StrategicTacticalOperatingScenariosProgramPlansAS-IS to TO-BE ArchitectureEffective management and exploitation of information through IT is key to business successGood information management = competitive advantageCurrent IT systems do not really meet the needs of business Broken, duplicated Poorly understood Not responsive to change
Investment in Information Technology Focussed on system maintenance Tactical developments rather than a strategic planWhy Enterprise Architecture?A conceptual structure used to develop, implement and sustain an Enterprise Architecture
It should describe a method for designing target state of the Enterprise in terms of a set of building blocks, and for showing how the building blocks fit together
It should contain a set of tools and provide a common vocabulary
It should also include a list of recommended standards and compliant products that can be used to implement the building blocksWhat is an Architecture Framework?The Zachman Framework
The Open Group Architecture Framework(TOGAF)
Federal Enterprise Architecture(FEA)
Gartner
Top Architecture FrameworksEvery enterprise has an IT architectureSomeare designedand somejust happen14Directly address the needs of the enterpriseReact to change at the rate dictated by the enterprises marketsBe understood and supported by senior managementClearly define the structure of the existing systemProvide a roadmap and migration strategy for future purchases / developmentsReduce the number and complexity of the interfaces between components, improving the ease of:Application portabilityComponent upgradeComponent exchangeComponent development and maintenanceA good IT architecture will:15Greater ability to respond to new demandsGreater business value from IT operationsGreater ability to introduce new technologyFaster, simpler and cheaper procurementFaster time-to-marketDo you have a plan?Can a business succeed withouta documented business plan?Can I.T. succeed without a documented architecture?16There are many successful IT architectures in useCan you benefit from that accumulation of knowledge?Can you examine in detail the IT architecture of another organization?Do you have to reinvent the wheel?What reference material is available? The TOGAF is going to answers for all your questions.But where do you start?17A customer initiative:Formal user requirement developed 1994Main themes:A single, unifying Architectural Framework for the IT industryA framework for developing architectures to meet specific business needsTOGAF Origins and Motivations18 A framework - there was dialog prior to agreement on the requirement - ultimate need was architecture, but recognition that consensus architecture not feasible - so requirement was for a framework within which individual architectures could be developed to suit specific business needs. More than any other program, customers feel ownership Driver was requirement developed 2H94 by X/Open User Council, subsequently endorsed by OSF customers post merger (1H96) Problem: Building real (=multi-vendor, heterogeneous) open systems too complex and costly - need help, else alternative is single-vendor solutions (=> standards conformance irrelevant, market leader dominates)Two main aspects to solution: A single, unifying framework - gives help in designing open systems architectures and procuring products that meet the open design Need to understand The Open Group's role in large picture - how individual product standards, technologies, projects, etc.. relate to / help solve the overall problemMore than 100,000 downloadsOver 16,000 certified practitionersMore than 220 corporate members of The Open Group Architecture ForumOver 55,000 TOGAF series books shippedAssociation of Enterprise Architects membership at more that 20,000 TOGAF Momentum
Industry consensusTechnology- and tool-neutral8 years continuous developmentProven in practicePublicly available
TOGAF Today1994: RequirementProof of Need1995: TOGAF Version 1Proof of Concept1996: TOGAF Version 2Proof of Application1997: TOGAF Version 3Relevance to practical architectures (Building Blocks)1998: TOGAF Version 4TOGAF in Context - the Enterprise Continuum1999: TOGAF Version 5Business Scenarios - architecture requirements2000: TOGAF Version 6Architecture views / IEEE 1471 US DoD work (C4ISR Framework, C2STA)2001: TOGAF Version 72003: TOGAF Version 82009: TOGAF Version 92011: TOGAF Version 9.1TOGAF Development History21Brief review of development to date: 2H94 requirement - demonstrated real need 1995 - hand-picked group of customer & vendor experts (Architecture Task Force) first version of Framework published Dec 95, as X/Open A/F deficiencies, but demonstrated proof of concept many had doubted feasibility of a consensus arch f/w 1996 - Arch Task Force continued, embraced work of OSF community second version published as TOGAF, builds on XAF, integrates arch. work of OSF community => stable, robust f/w case studies of TOGAF used in significant projects for design and procurement of open system solution vendor commitments to develop mappings to TOGAF from own product architectures NCR / OCCA there already, IBM / Open Blueprint committed, discussions ongoing with other vendors Next logical progression - build critical mass greater relevance to specific architectural implementations address key deficienciesTOGAF 9.1 was released in December 2011It is the first maintenance update to TOGAF 9 It is an upwards-compatible evolution from TOGAF 9, addressing usage feedback and comments raisedIt addresses over 400 comments received Contains over 450 changes
TOGAF 9.1The TOGAF 9.1-Body knowledge
The Architecture Development Method
ADM Iterative viewArchitecture Development MethodFoundation ArchitectureResource BaseTOGAF Structure and ComponentsBuilding Blocks Information Base
(architecture building blocks - future)Standards Information Base
(standards)Technical Reference Model
(services taxonomy)Architecture Development MethodResource BaseTarget ArchitecturesTOGAF FoundationArchitecture26The Architecture Continuum
Overview of TOGAF exam
Q&AThanks
