1 of 49
Architecting the Enterprise LimitedCopyright © 2003 TOGAF - The Continuing Story
The Open GroupArchitecture Framework
(TOGAF)
The Continuing Story
Presented by Chris Greenslade
TOGAF - The Continuing Story 2 of 49
Architecting-the-Enterprise LimitedCopyright © 2003
The questions to answerThe questions to answer
Who are we?
What principles have we adopted?
What have we achieved so far?
What is our current motivation?
What is the TOGAF Enterprise Edition?
What are our future directions?
TOGAF - The Continuing Story 3 of 49
Architecting-the-Enterprise LimitedCopyright © 2003
The questions to answerThe questions to answer
Who are we?
What principles have we adopted?
What have we achieved so far?
What is our current motivation?
What is the TOGAF Enterprise Edition?
What are our future directions?
TOGAF - The Continuing Story 4 of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Architecture ForumArchitecture Forum
The mission of the Forum’s members is to: Advance the cause of IT Architecture - in order to
Improve the quality of information systems To move IT Architecture from a cottage industry to a
profession
Original (and continuing) focus: (TOGAF) Industry consensus framework and method for IT
architecture Tool- and technology-neutral
Extended focus Architecture Tools IT Architect Certification
TOGAF - The Continuing Story 5 of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Who’s WhoWho’s Who
Director John SpencerThe Open Group
Chair Chris GreensladeFrietuna Computer Consultants (UK)
Vice Chairs Barry SmithThe MITRE Corporation (USA)
Ian McCallIBM Global Services (UK)
Vish ViswanathanCC & C Solutions (Australia)
TOGAF - The Continuing Story 6 of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Forum MembershipForum Membership
Architecting the Enterprise (UK)
BMC Software Inc. (US)
Boeing Corporation (US)
Booz Allen & Hamilton (US)
Brandeis University (US)
CC and C Solutions ((Aus)
Centre For Open Systems (Aus)
ChiSurf (Hong Kong)
Computacenter (UK)
Computas (Nor)
Computer Associates (US)
Conclusive Logic (US)
Department of Defense / DISA (US)
Department of Works and Pensions (UK)
Desktop Management Task Force (US)
Fujitsu (Japan)
Frietuna Consultants (UK)
Hewlett-Packard (US)
Hitachi (Japan)
IBM (US)
Innenministerium NordRhein-Westfalen (Ger)
Jet Propulsion Labs (US)
Lockheed Martin (US)
MEGA International (Fr)
Ministry of Defence (UK)
Mitre Corporation (US)
Monash University (Australia)
Motorola (US)
NASA Goddard Space Flight Center (US)
National Computerization Agency (Korea)
NATO C3 Agency (Bel)
NEC (Japan)
TOGAF - The Continuing Story 7 of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Forum MembershipForum Membership
NEMMCO (Australia)
NeTraverse, Inc. (US)
Nexor, Inc. (US)
Open GIS Consortium, Inc. (US)
PASS Network Consulting (Ger)
Popkin Software and Systems, Inc. (UK)
POSC (US)
Predictive Systems AG (Ger)
Primeur (Italy)
ReGIS (Japan)
QA Consulting (UK)
SCO (US)
Sun Microsystems (US)
Teamcall (Bel)
The Terasoft Group (US)
Tivoli (US)
Toyota InfoTechnology Center (Japan)
TRON Association (Japan)
University of Plymouth (UK)
University of Reading (UK)
US Army Weapon Systems Technical Working Group (WSTAWG) (US)
Veriserve Corporation (US)
Visa International (US)
Weblayers, Inc (US)
Westpac Banking Corporation (Australia)
57
TOGAF - The Continuing Story 8 of 49
Architecting-the-Enterprise LimitedCopyright © 2003
The questions to answerThe questions to answer
Who are we?
What principles have we adopted?
What have we achieved so far?
What is our current motivation?
What is the TOGAF Enterprise Edition?
What are our future directions?
TOGAF - The Continuing Story 9 of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Defining an IT ArchitectureDefining an IT Architecture
ANSI/IEEE Standard 1471-2000 Conceptually an IT Architecture is
The fundamental organization of a system, embodied in its components, their relationships
to each other and the environment,
and the principles governing its design and evolution.
Practically it is represented in Architectural Descriptions from the viewpoints of the Stakeholders
TOGAF - The Continuing Story 10
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Some more ANSI/IEEE definitionsSome more ANSI/IEEE definitions
Architect: the person, team, or organisation responsible for
systems architecture
Architecting: the activities of defining, documenting, maintaining,
improving and certifying proper implementation of an architecture.
Architectural description a collection of products to document an architecture.
TOGAF - The Continuing Story 11
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Architecture views - definitionsArchitecture views - definitions
System Stakeholder: an individual, team, or organization (or classes thereof)
with interests in, or concerns relative to, a system
View: a representation of a whole system from the perspective
of a related set of concerns
Viewpoint: (a schema of the information in a view) acts as a pattern or template from which to develop
individual views by establishing the purposes and audience for a view and the techniques for its creation and analysis
TOGAF - The Continuing Story 12
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Architecture viewArchitecture view
Description of the architecture from the viewpoint of a specific stakeholder
The main mechanism of communication between the architect and the stakeholder
Used to ensure accuracy of understanding of the current system
Used to ensure the architecture meets the need of each stakeholder
The collection of views comprises the description of the architecture
TOGAF - The Continuing Story 13
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
ArchitectureArchitecture
We are NOT talking about rocket science
We ARE talking about: Using common sense Being systematic Avoiding misunderstandings Knowing what we are doing before we start Knowing why we are doing it Learning from the best practice of others Treating the user as a partner Talking to business users in business terms Recording what, where, when, how, who and WHY Using common sense
TOGAF - The Continuing Story 14
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
The Zachman FrameworkThe Zachman Framework
EnterpriseModels
SystemsModels
TechnologyModels
DetailedRepresentations
ActualSystems
Scope
What?
Data
How?
Function
Where?
Network
Who?
People
When?
Time
Why?
Motivation
Planner’s Viewpoint
Contextual
Owner’s Viewpoint
Conceptual
Designer’s Viewpoint
Logical
Builder’s Viewpoint
Physical
Sub-contractor’s Viewpoint
Out-of-context
Functioning Enterprise
Architecture principlesBusiness principles
goals & drivers
Approved statement of architecture work Refined Business principles
goals & drivers
Business baseline version 1
Technical baseline version 1
Business architecture version 1
Technical architecture version 1
Organizationstructure
Business goalsand objectives
Business functions
Business services
Business processes Business
processes
Business roles
Correlation of organizationand function
Technical require-ments
Validated principles
Target data architectureData dissemination view
Data lifecycle view
Data lifecycle
view Data security view
Data model managem’t
view
Data model managem’t
view
Technical require-ments
Validated principles
Target application architectureCommon application services view
Applications interoperability view
Application interop.
viewApplications information view
Application information
view
Application user location view
Gap analysis results
Constraints on
technology architecture
Validated principles
Technology architecture version 0.1
Technology architecture version 0.2
Technology architecture version 0.4
Gap analysis results
Technology architecture version 0.3
TOGAF - The Continuing Story 15
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
What is an Enterprise Architecture?What is an Enterprise Architecture?
An Enterprise Architecture is the technical foundation of an effective IT strategy
It consists of four types of architecture: Business architecture Information system architectures
Data or information architecture Application architecture
Technology architecture
All these are related
TOGAF 7 Technical Edition
TOGAF 8Enterprise Edition
TOGAF - The Continuing Story 16
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Can a business succeed withouta documented business plan?
Can a business succeed withouta documented business plan?
Can IT succeed without a documented architecture?Can IT succeed without a documented architecture?
What is the desired benefit of TOGAF?What is the desired benefit of TOGAF?
Architected business information systems will have: A greater ability to respond to new demands A greater business value to the organization A greater ability to use new technology A faster, simpler and cheaper procurement process The ability to support a faster time-to-market
TOGAF - The Continuing Story 17
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
What is an Architectural Framework?What is an Architectural Framework?
Architecture design is a complex process
An architectural framework is a tool for: Designing a broad range of a architectures Assisting the evaluation of different architectures Selecting and building the right architecture for an
organization
It embodies best practice and acknowledged wisdom
It presents a set of services, standards, design concepts, components and configurations
It guides the development of specific architectures
TOGAF - The Continuing Story 18
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
What is an Architectural Framework?What is an Architectural Framework?
Use of a framework leads to: The use of common principles, assumptions and
terminology The development of information systems with better
integration and interoperability, especially with respect to issues that affect the whole enterprise
WARNING! A framework does not make architectural design an
automatic process It is a valuable aid to experienced and knowledgeable IT
Architects
TOGAF - The Continuing Story 19
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
The position of IT ArchitectsThe position of IT Architects
We know solutions to every problem? What’s your problem?
How do I know what I want, when I don’t
know what you can do for me
A rchitec tIT
TOGAF - The Continuing Story 20
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
The position of IT ArchitectsThe position of IT Architects
Business Management
Business Management
Technical ManagementTechnical
Management
System Designers & Developers
System Designers & Developers
IT Architects
IT Architects
TOGAF - The Continuing Story 21
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
The questions to answerThe questions to answer
Who are we?
What principles have we adopted?
What have we achieved so far?
What is our current motivation?
What is the TOGAF Enterprise Edition?
What are our future directions?
TOGAF - The Continuing Story 22
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
The story so farThe story so far
The direction of TOGAF’s evolution has been driven by The Open Group’s membership over a period of 8 years
An annual publication cycle 1994: Requirement statement developed
Proof of need 1995: X/Open Architectural Framework - version 1
Proof of concept 1996: TOGAF - version 2
Proof of application 1997: TOGAF - version 3
Relevance to practical architectures
TOGAF - The Continuing Story 23
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
The story so farThe story so far
1998: TOGAF - version 4 TOGAF in context - the Enterprise Continuum Web structured documentation - ease of use
1999: TOGAF - version 5 Re-organized around extended ADM Business scenarios to help define requirements Addition of ADML
2000: TOGAF - version 6 Integration of Building Block work Integration of other initiatives, US DoD, IEEE 1471,
IEEE 1003.23
TOGAF - The Continuing Story 24
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Technical Edition
Technical Edition
Current situationCurrent situation
2001: TOGAF - version 7 New sections on Architecture Patterns, Architecture
Principles, Architecture Compliance Reviews Significant additional material on Business Scenarios Comparisons of TOGAF with other frameworks Further integration of IEEE Std 1471-2000 into TOGAF Metis model of the TOGAF ADM Positioning of TOGAF relative to enterprise architecture
2002: TOGAF - Version 8Enterprise Edition
Enterprise Edition
TOGAF - The Continuing Story 25
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
TOGAF consists ofTOGAF consists of
An Architecture Development Method (ADM)
Foundation Architecture A Technical Reference Model (TRM) A Standards Information Base (SIB) Building Blocks Information Base (BBIB)
Resource Base contains advice on: Architecture views Business scenarios IT Governance Architecture patterns ADL Case studies TABB Architecture principles Architecture contracts ...
TOGAF - The Continuing Story 26
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
More about TOGAFMore about TOGAF
Business Requirements
TechnicalReference
Model (services)
Standards Information
Base (standards)
Building Block
Information Base
(future)
Architecture Development Method
Target Architectures
FoundationArchitecture
TOGAF - The Continuing Story 27
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Architecture Development MethodArchitecture Development Method
Start with a foundation architecture
Follow the phases of the ADMG
Architecturemaintenance
GArchitecturemaintenance
FImplementation
FImplementation
EMigrationoptions
EMigrationoptions
DOpportunities
& solutions
DOpportunities
& solutions
CTarget
architecture
CTarget
architecture
BBaseline
description
BBaseline
description
AInitiation &framework
AInitiation &framework
Requirements
Results inan organization-specific
architecturemore reusable building block
assets in the Enterprise Continuum
Each iteration becomes easier and has more reusable building blocks to use
TOGAF - The Continuing Story 28
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Communications Infrastructure Interface
Communication Infrastructure
Application Program Interface
Application Platform
Technical Reference ModelTechnical Reference Model
Infrastructure Applications Business Application
TOGAF - The Continuing Story 29
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Communication Infrastructure
Services and QualitiesServices and Qualities
Network Services
Operating System Services
So
ftware E
ng
ineerin
g
Secu
rity
Sys &
Net M
anag
emen
t
Tran
saction
Pro
cessing
Lo
cation
& D
irectory
User In
terface
Intern
ation
al Op
eration
s
Data In
terchan
ge
Data M
anag
emen
t
Grap
hics &
Imag
eInfrastructure Applications Business Application
Service
Qu
alities
API
CII
Ap
plicatio
n Platfo
rmS
ervices
TOGAF - The Continuing Story 30
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Standards Information Base (SIB)Standards Information Base (SIB)
A complete and up to date database of open industry standards with links to conformant products
Standards Information Base publicly available At http://www.opengroup.org/sib With user guide Search or full listing
Can be used to: Define particular services Define properties of components Be the basis of procurement procedures
Keeps the architecture up to date with the latest IT industry consensus
TOGAF - The Continuing Story 31
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Benefits of TOGAF to the architectBenefits of TOGAF to the architect
Avoids regular reinvention of the wheel
Provides a corporate memory of previous successes and failures
Ensures completeness of the design process
Provides access to accumulated best practice wisdom
Avoids communication difficulties within the team
The professional approach
“Best endeavor” legal defense - just in case
TOGAF - The Continuing Story 32
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
TOGAF - its key benefits (1)TOGAF - its key benefits (1)
Vendor-Neutral
Comprehensive process - from business requirements to applications to infrastructure
The result of 8 years of global development
Cuts up-front costs - avoids re-inventing the wheel
Refined and honed checklists at all levels - from business requirements to physical components
The Standards Information Base Maintained, current and comprehensive
Standard documented approach insures against the departure of key staff
TOGAF - The Continuing Story 33
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
TOGAF - its key benefits (2)TOGAF - its key benefits (2)
TOGAF is available today under an evaluation license http://www.opengroup.org/architecture/togaf7/index7.htm http://www.opengroup.org/architecture/togaf8/index8.htm
TOGAF is available under a free perpetual license for use within your own organization
Third-party users can buy a commercial license or can join the Architecture Forum
Any member of the Architecture Forum can participate in shaping TOGAF’s evolution
TOGAF - The Continuing Story 34
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
TOGAF - its key benefits (3)TOGAF - its key benefits (3)
TOGAF 7 is the vendor-neutral, global basis of Certification to impose standards within our profession
Architecture tools which support TOGAF 7
Training courses which instruct in TOGAF 7
Architects trained in the use of TOGAF 7
Professional services offered to support TOGAF 7
TOGAF - The Continuing Story 35
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
The questions to answerThe questions to answer
Who are we?
What principles have we adopted?
What have we achieved so far?
What is our current motivation?
What is the TOGAF Enterprise Edition?
What are our future directions?
TOGAF - The Continuing Story 36
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
What is our current motivation?What is our current motivation?
The work goes on - new knowledge, new experience, new ideas, new challenges
Changes that will influence the future take-up of IT Architecture More extended enterprises More co-operative IT operations Tighter IT budgets Global competition More frantic skills chase
Increase in litigation
Failure can be terminal
TOGAF - The Continuing Story 37
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
What is our current motivation?What is our current motivation?
Pace set by public agencies and large vendors
More enforcement of acquisition regulations Clinger-Cohen Act (US Information Technology
Management Reform Act 1996) EU Directives on the Award of Public Contracts
Contracting Authority needs procedures for ensuring: Completeness of given business requirements Vendor independent expression of needs Same information to all
TOGAF - The Continuing Story 38
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
The questions to answerThe questions to answer
Who are we?
What principles have we adopted?
What have we achieved so far?
What is our current motivation?
What is the TOGAF Enterprise Edition?
What are our future directions?
TOGAF - The Continuing Story 39
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
What is the Enterprise Edition?What is the Enterprise Edition?
An Enterprise Architecture is the technical foundation of an effective IT strategy
It consists of four types of architecture: Business architecture Information system architectures
Data or information architecture Application architecture
Technology architecture
All these are related
TOGAF 7 Technical Edition
TOGAF 8Enterprise Edition
TOGAF - The Continuing Story 40
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
The Enhanced ADMThe Enhanced ADM
RequirementsManagement
PreliminaryFramework &
Principles
PreliminaryFramework &
Principles
AArchitecture
Vision
AArchitecture
Vision
TOGAF - The Continuing Story 41
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Preliminary steps (1)Preliminary steps (1)
Getting the buy-in The most difficult stage The most important stage
Establishing the Architectural Framework Customizing, configuring and selecting options suitable
for the organization
Providing a foundation for the framework by establishing: Architecture principles – to guide all future work on all
future architectures IT Governance Architecture compliance procedures
TOGAF - The Continuing Story 42
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Preliminary steps (2)Preliminary steps (2)
Integrating the framework with existing procedures Preserving tried, trusted, or mandated procedures
Choosing the tools
Training the staff - architects and others
Creating a repository for Building Blocks (BBIB?)
Monitored pilot project Built-in leeway to allow for familiarization and fine-tuning
TOGAF - The Continuing Story 43
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
GArchitecture
ChangeManagement
GArchitecture
ChangeManagement
GImplementation
Governance
GImplementation
Governance
FMigrationPlanning
FMigrationPlanning
EOpportunites& Solutions
EOpportunites& Solutions
DTechnologyArchitecture
DTechnologyArchitecture
The Enhanced ADMThe Enhanced ADM
RequirementsManagement
CInformation
SystemArchitectures
CInformation
SystemArchitectures
CInformation
SystemArchitectures
CInformation
SystemArchitectures
PreliminaryFramework &
Principles
PreliminaryFramework &
Principles
BBusiness
Architecture
BBusiness
Architecture
AArchitecture
Vision
AArchitecture
Vision
TOGAF - The Continuing Story 44
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Application Platform
Integrated Information Infrastructure Reference Model Integrated Information Infrastructure Reference Model
Information Provider Applications
QualitiesSecurity Policy Mobility Policy
Performance SLAs Manageability Policy
Development Tools
Brokering Applications
Management Utilities
Information Consumer Applications
TOGAF - The Continuing Story 45
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Transition policyTransition policy
TOGAF 7 - frozen and retained as the version for Technology Architectures
TOGAF 8 - the first release of the Enterprise Edition Feedback needed on the ADM as applied to the
Business, Data and Application Architectures Future releases will strengthen and work harden the
Enterprise Edition until it can become a basis for Certification
TOGAF - The Continuing Story 46
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
The questions to answerThe questions to answer
Who are we?
What principles have we adopted?
What have we achieved so far?
What is our current motivation?
What is the TOGAF Enterprise Edition?
What are our future directions?
TOGAF - The Continuing Story 47
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
Knowledgeable and professional
practitioners
Knowledgeable and professional
practitioners
Support tools at all levels
A good architecture framework
The Architecture ForumThe Architecture Forum
Striving to achieve a total, practical, architectural solution
TOGAF X Enterprise
Edition
Certification of Training courses TOGAF practitioners Professional Services IT Architects
Tools Certification
TOGAF - The Continuing Story 48
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
What are our future directions?What are our future directions?
Evolution of TOGAF – Enterprise Edition Bring to maturity Establish TOGAF X Certification And possibly:
Enhance to align with OMG’s MDA Enhance to include mobility features Enhance to support Quality of Service Align with Zachman Framework Enhance to include industry TRMs
Establishment of IT Architect Certification
Develop the distributed BBIB
Promote, support, advise and get it all into use.
TOGAF - The Continuing Story 49
of 49
Architecting-the-Enterprise LimitedCopyright © 2003
The questions to answerThe questions to answer
Who are we?
What principles have we adopted?
What have we achieved so far?
What is our current motivation?
What is the TOGAF Enterprise Edition?
What are our future directions?
Any questions?
Recommended