1. The Open Group Architecture Framework (TOGAF)
TOGAF - The Continuing Story
The Open Group Architecture Framework (TOGAF)
The Continuing Story
Presented by Chris Greenslade
TOGAF - The Continuing Story
of 49
TA P12
Version /03

2. The questions to answer
TOGAF - The Continuing Story
The 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
of 49
TA P12
Version /03

3. The questions to answer
TOGAF - The Continuing Story
The 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
of 49
TA P12
Version /03

4. TOGAF - The Continuing Story
Architecture 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
of 49
TA P12
Version /03

5. TOGAF - The Continuing Story
Who’s Who
Director John Spencer The Open Group
Chair Chris Greenslade
Frietuna Computer Consultants (UK)
Vice Chairs Barry Smith
The MITRE Corporation (USA)
Ian McCall
IBM Global Services (UK)
Vish Viswanathan
CC & C Solutions (Australia)
TOGAF - The Continuing Story
of 49
TA P12
Version /03

6. TOGAF - The Continuing Story
Forum 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
of 49
TA P12
Version /03

7. TOGAF - The Continuing Story
Forum 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
of 49
TA P12
Version /03

8. The questions to answer
TOGAF - The Continuing Story
The 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
of 49
TA P12
Version /03

9. Defining an IT Architecture
TOGAF - The Continuing Story
Defining an IT Architecture
ANSI/IEEE Standard
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
of 49
TA P12
Version /03

10. Some more ANSI/IEEE definitions
TOGAF - The Continuing Story
Some 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
of 49
TA P12
Version /03

11. Architecture views - definitions
TOGAF - The Continuing Story
Architecture 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
of 49
TA P12
Version /03

12. TOGAF - The Continuing Story
Architecture 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
of 49
TA P12
Version /03

13. TOGAF - The Continuing Story
Architecture
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
TOGAF - The Continuing Story
of 49
TA P12
Version /03

14. TOGAF - The Continuing Story
The Zachman Framework
What?
Data
How?
Function
Where?
Network
Who?
People
When?
Time
Why?
Motivation
Planner’s Viewpoint
Contextual
Validated principles
Validated principles
Approved statement of architecture work
Architecture principles
Business functions
Validated principles
Correlation of organization
and function
Organization
structure
Business goals
and objectives
Business roles
Refined Business principles goals & drivers
Business principles goals & drivers
Scope
Owner’s Viewpoint
Conceptual
Target data architecture
Data model managem’t
view
Business architecture version 1
Gap analysis results
Business baseline version 1
Business services
Business processes
Enterprise
Models
Designer’s Viewpoint
Logical
Technology architecture version 0.2
Technology architecture version 0.3
Data security view
Target application architecture
Common application services view
Applications interoperability view
Application interop. view
Applications information view
Application information view
Data lifecycle view
Data dissemination view
Technical baseline version 1
Technical architecture version 1
Application user location view
Technical require-ments
Constraints on technology architecture
Technical require-ments
Systems
Models
Builder’s Viewpoint
Physical
Technology architecture version 0.4
Gap analysis results
Technology architecture version 0.1
Technology
Models
Sub-contractor’s Viewpoint
Out-of-context
Detailed
Representations
Functioning Enterprise
Actual
Systems
TOGAF - The Continuing Story
of 49
TA P12
Version /03

15. What is an Enterprise Architecture?
TOGAF - The Continuing Story
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 8 Enterprise Edition
TOGAF 7 Technical Edition
TOGAF - The Continuing Story
of 49
TA P12
Version /03

16. What is the desired benefit of TOGAF?
TOGAF - The Continuing Story
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
Can a business succeed without
a documented business plan?
Can IT succeed without a documented architecture?
TOGAF - The Continuing Story
of 49
TA P12
Version /03

17. What is an Architectural Framework?
TOGAF - The Continuing Story
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
of 49
TA P12
Version /03

18. What is an Architectural Framework?
TOGAF - The Continuing Story
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
of 49
TA P12
Version /03

19. The position of IT Architects
TOGAF - The Continuing Story
The position of IT Architects
How do I know what I want, when I don’t know what you can do for me
We know solutions to every problem? What’s your problem?
TOGAF - The Continuing Story
of 49
TA P12
Version /03

20. The position of IT Architects
TOGAF - The Continuing Story
The position of IT Architects
Technical Management
Business Management
IT Architects
System Designers & Developers
TOGAF - The Continuing Story
of 49
TA P12
Version /03

21. The questions to answer
TOGAF - The Continuing Story
The 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
of 49
TA P12
Version /03

22. TOGAF - The Continuing Story
The 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
of 49
TA P12
Version /03

23. TOGAF - The Continuing Story
The 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
TOGAF - The Continuing Story
of 49
TA P12
Version /03

24. TOGAF - The Continuing Story
Current situation
Technical Edition
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 into TOGAF
Metis model of the TOGAF ADM
Positioning of TOGAF relative to enterprise architecture
2002: TOGAF - Version 8
Enterprise Edition
TOGAF - The Continuing Story
of 49
TA P12
Version /03

25. TOGAF - The Continuing Story
TOGAF 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
of 49
TA P12
Version /03

26. TOGAF - The Continuing Story
More about TOGAF
Foundation Architecture
Target Architectures
Architecture Development Method
Technical Reference Model (services)
Standards Information Base (standards)
Building Block Information Base (future)
Business Requirements
TOGAF - The Continuing Story
of 49
TA P12
Version /03

27. Architecture Development Method
TOGAF - The Continuing Story
Architecture Development Method
Start with a foundation architecture
Follow the phases of the ADM
A Initiation & framework
G Architecture maintenance
B Baseline description
Requirements
Results in
an organization-specific architecture
more reusable building block assets in the Enterprise Continuum
Each iteration becomes easier and has more reusable building blocks to use
C Target architecture
F Implementation D
Opportunities
& solutions
E Migration options
TOGAF - The Continuing Story
of 49
TA P12
Version /03

28. Technical Reference Model
TOGAF - The Continuing Story
Technical Reference Model
Infrastructure Applications
Business Application
Application Program Interface
Application Platform
Communications Infrastructure Interface
Communication Infrastructure
TOGAF - The Continuing Story
of 49
TA P12
Version /03

29. Services and Qualities
TOGAF - The Continuing Story
Services and Qualities
Infrastructure Applications
Business Application
API
CII
Application Platform Services
Software Engineering
Security
Sys & Net Management
Transaction Processing
Location & Directory
User Interface
International Operations
Data Interchange
Data Management
Graphics & Image
Service Qualities
Operating System Services
Network Services
Communication Infrastructure
TOGAF - The Continuing Story
of 49
TA P12
Version /03

30. Standards Information Base (SIB)
TOGAF - The Continuing Story
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
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
of 49
TA P12
Version /03

31. Benefits of TOGAF to the architect
TOGAF - The Continuing Story
Benefits 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
of 49
TA P12
Version /03

32. TOGAF - its key benefits (1)
TOGAF - The Continuing Story
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
of 49
TA P12
Version /03

33. TOGAF - its key benefits (2)
TOGAF - The Continuing Story
TOGAF - its key benefits (2)
TOGAF is available today under an evaluation license
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
of 49
TA P12
Version /03

34. TOGAF - its key benefits (3)
TOGAF - The Continuing Story
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
of 49
TA P12
Version /03

35. The questions to answer
TOGAF - The Continuing Story
The 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
of 49
TA P12
Version /03

36. What is our current motivation?
TOGAF - The Continuing Story
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
of 49
TA P12
Version /03

37. What is our current motivation?
TOGAF - The Continuing Story
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
of 49
TA P12
Version /03

38. The questions to answer
TOGAF - The Continuing Story
The 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
of 49
TA P12
Version /03

39. What is the Enterprise Edition?
TOGAF - The Continuing Story
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 8 Enterprise Edition
TOGAF 7 Technical Edition
TOGAF - The Continuing Story
of 49
TA P12
Version /03

40. TOGAF - The Continuing Story
The Enhanced ADM
Preliminary
Framework &
Principles
A Architecture
Vision
Requirements
Management
TOGAF - The Continuing Story
of 49
TA P12
Version /03

41. TOGAF - The Continuing Story
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
of 49
TA P12
Version /03

42. TOGAF - The Continuing Story
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
of 49
TA P12
Version /03

43. TOGAF - The Continuing Story
The Enhanced ADM
Preliminary
Framework &
Principles
A Architecture
Vision
G Architecture Change
Management
B Business
Architecture
C Information
System
Architectures
G Implementation
Governance
Requirements
Management D
Technology
Architecture
F Migration
Planning
E Opportunites
& Solutions
TOGAF - The Continuing Story
of 49
TA P12
Version /03

44. Integrated Information Infrastructure Reference Model
TOGAF - The Continuing Story
Integrated Information Infrastructure Reference Model
Security Policy
Qualities
Mobility Policy
Application Platform
Information Consumer Applications
Development Tools
Brokering Applications
Management Utilities
Information Provider Applications
Performance SLAs
Manageability Policy
TOGAF - The Continuing Story
of 49
TA P12
Version /03

45. TOGAF - The Continuing Story
Transition 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
of 49
TA P12
Version /03

46. The questions to answer
TOGAF - The Continuing Story
The 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
of 49
TA P12
Version /03

47. The Architecture Forum
TOGAF - The Continuing Story
The Architecture Forum
Striving to achieve a total, practical, architectural solution
Certification of
Training courses
TOGAF practitioners
Professional Services
IT Architects
TOGAF X Enterprise Edition
A good architecture framework
Tools Certification
Knowledgeable and professional practitioners
Support tools at all levels
TOGAF - The Continuing Story
of 49
TA P12
Version /03

48. What are our future directions?
TOGAF - The Continuing Story
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
of 49
TA P12
Version /03

49. The questions to answer
TOGAF - The Continuing Story
The 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?
TOGAF - The Continuing Story
of 49
TA P12
Version /03