greenslade_togaf2_THE OPEN GROUP ARCHITECTURE FRAMEWORK

THE OPEN GROUP ARCHITECTURE
FRAMEWORK

1. Architecting the Enterprise Limited
Copyright © 2003
1of 49TOGAF -The Continuing Story
The Open Group
Architecture Framework
(TOGAF)
The Continuing Story
Presented by Chris Greenslade
[email protected]

2. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story2of 49
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?

3. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story3of 49
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?

4. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story4of 49
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

5. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story5of 49
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)

6. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story6of 49
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)

7. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story7of 49
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

8. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story8of 49
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?

9. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story9of 49
Defining 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

10. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story10of 49
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.

11. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story11of 49
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

12. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story12of 49
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

13. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story13of 49
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
Using common sense

14. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story14of 49
The Zachman Framework
Enterprise
Models
Systems
Models
Technology
Models
Detailed
Representations
Actual
Systems
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 principles
Business
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
Organization
structure
Business
goals
and
objectives
Business
functions
Business
services
Business
processes Business
processes
Business
roles
Correlation of organization
and function
Technical
require-
ments
Validated
principles
Target data architecture
Data dissemination view
Data lifecycle view
Data
lifecycle
viewData security view
Data model
managem’t
view
Data model
managem’t
view
Technical
require-
ments
Validated
principles
Target application architecture
Common 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

15. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story15of 49
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 8
Enterprise Edition

16. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story16of 49
Can a business succeed without
a documented business plan?
Can IT succeed without a documented architecture?
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

17. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story17of 49
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

18. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story18of 49
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

19. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story19of 49
The 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 meA
rchitect
IT

20. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story20of 49
The position of IT Architects
Business
Management
Technical
Management
System
Designers &
Developers
IT
Architects

21. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story21of 49
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?

22. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story22of 49
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

23. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story23of 49
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 1003.23

24. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story24of 49
Current 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 8

25. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story25of 49
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...

26. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story26of 49
More about TOGAF
Business Requirements
Technical
Reference
Model
(services)
Standards
Information
Base
(standards)
Building
Block
Information
Base
(future)
Architecture Development Method
Target Architectures
Foundation
Architecture

27. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story27of 49
Architecture Development Method
Start with a foundation
architecture
Follow the phases of the ADM
G
Architecture
maintenance
F
Implementation
E
Migration
options
D
Opportunities
& solutions
C
Target
architecture
B
Baseline
description
A
Initiation &
framework
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

28. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story28of 49
Communications Infrastructure Interface
Communication Infrastructure
Application Program Interface
Application Platform
Technical Reference Model
Infrastructure Applications Business Application

29. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story29of 49
Communication Infrastructure
Services and Qualities
Network Services
Operating System Services
Software Engineering
Security
Sys & Net ManagementTransaction Processing
Location & Directory
User Interface
International Operations
Data InterchangeData ManagementGraphics & Image
Infrastructure Applications Business Application
Service Qualities
API
CII
Application
Platform
Services

30. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story30of 49
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

31. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story31of 49
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

32. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story32of 49
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

33. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story33of 49
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

34. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story34of 49
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

35. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story35of 49
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?

36. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story36of 49
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

37. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story37of 49
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

38. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story38of 49
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?

39. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story39of 49
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 8
Enterprise Edition

40. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story40of 49
The Enhanced ADM
Requirements
Management
Preliminary
Framework &
Principles
A
Architecture
Vision

41. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story41of 49
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

42. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story42of 49
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

43. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story43of 49
G
Architecture
Change
Management
G
Implementation
Governance
F
Migration
Planning
E
Opportunites
& Solutions
D
Technology
Architecture
The Enhanced ADM
Requirements
Management
C
Information
System
Architectures
C
Information
System
Architectures
Preliminary
Framework &
Principles
B
Business
Architecture
A
Architecture
Vision

44. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story44of 49
Application Platform
Integrated Information Infrastructure
Reference Model
Information Provider Applications
Qualities
Security Policy Mobility Policy
Performance SLAs Manageability Policy
Development
Tools
Brokering
Applications
Management
Utilities
Information Consumer Applications

45. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story45of 49
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

46. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story46of 49
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?

47. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story47of 49
Knowledgeable
and professional
practitioners
Support tools at
all levels
A good
architecture
framework
The 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

48. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story48of 49
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.

49. Architecting-the-Enterprise Limited
Copyright © 2003
TOGAF -The Continuing Story49of 49
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?