Integrating TOGAF, Zachman and DoDAF Into A Common Process

Rolf Siegers Senior Principal Software Systems Engineer November 2003

Customer Success Is Our Mission

Topics

Definitions Why Architecture? Building Blocks of an Architecture Process Unifying the Standards Summary

Definitions
Architecture
The fundamental organization of a system embodied in its components, their relationships to
each other and to the environment, and the principles guiding its design and evolution. (IEEE 1471-2000)

Architecture Framework
A resource that guides the development or description of an architecture

Business Architecture
A perspective of the overall architecture reflecting enterprise mission, strategies, goals,
business drivers, business processes, information flows, and the supporting organizational structure

Technical Architecture
Perspectives of the overall architecture reflecting the enterprises data, applications and
technical components

Enterprise Architecture
A blueprint (set of models) that depicts how various business and technical elements work
together as a whole

Enterprise
e E
: the highest level of a system or system of systems : a Department or Agency of the government

Why Architecture?

Customer Success Is Our Mission

Why Architecture?

Government Customer Expectations Industry Competition Academia Our Future

Why Architecture? Government: Background

The US Government has clearly established their direction and expectation
for how complex systems of the future will be developed and integrated through architecture.

Spans all Departments and Agencies Not the tech or process trend du jour this is traceable back over a decade
Department of Defense Architecture Framework Federal Enterprise Architecture Service Component &
Technical Reference Models Federal Enterprise Architecture Business Reference Model Federal/DoD Enterprise Architecture Certification Institute Federal Enterprise Architecture Program Management Office Treasury Enterprise Architecture Framework Federal Enterprise Architecture Framework C4ISR Architecture Framework Establishment of CIO Council by Executive Order 13011 Congressional acts (GPRA 1993; FASA 1994; ITMRA 1996) Defense Science studies of early 1990s 2003 2003 2002 2002 2001 2000 1999 1996, 1997 1996

Why Architecture? Government: Sound Bites

OMB: Business cases must relate to enterprise architectures for 2005;
Government Computer News; 5/22/03 Agencies should include with their business case submissions a copy of their
architecture framework and an explanation of how it relates to the federal blueprintmore than 2,000 agency officials have attended seminars the office conducts on how to prepare business cases.

Get down to business with an architecture; Government Computer News; 4/7/03

The message from the Office of Management and Budget to agency managers is loud and
clear: No enterprise architecture, no funding.

DoD lays out enterprise architecture plans; Government Computer News; 4/4/03
the grid will be a globally connected, single information system with an enterprise
architecture called the Net-Centric Enterprise Service[SAIC] last month received a $50 million, five-year contract from the Office of the Joint Chiefs of Staff to plan and develop the grid.

Architecture due diligence; Federal Computer Week; 3/31/03

Agency spending on enterprise architectures is expected to increase to more than $1
billion this year according to OMB

Feds work on melding architectures; Federal Computer Week; 2/10/03

The Defense framework is probably the farthest removed from the FEA, but developers of
the framework have checked, and if components are collecting the data needed to meet DOD architecture requirements, the data should also qualify for the FEA reference models, [Mitre] said.
[Note: Article titles above are hyperlinks]

Why Architecture? Government: Sound Bites

OMB looks to extend architecture to DOD, intelligence;
Government Computer News; 9/13/02 The Office of Management and Budget is beginning to figure out how to integrate the
federal enterprise architecture with the Defense Department and intelligence agencies systems.

If you only read one article on the importance of this topic, please read Information Week, Nov 11 2002 One Nation, Under I.T.
http://www.informationweek.com/shared/printableArticle.jhtml?articleID=6504197

Piecing The Puzzle Together: Whats Needed In An Architecting Process?

Architecting Method Architectural Products Product Formats Architecture Validation Collaboration

METHOD C O L L A B O R A T I O N

PRODUCTS

FORMATS VALIDATION

Building Blocks

Architecting Method Architectural Products Product Formats Architecture Validation Collaboration

The Open Group Architecture Framework (TOGAF) Version 8.0 Enterprise Edition Architecture Development Method (ADM)

Building Blocks (contd)

Applicable View All Views All Views Framework Product AV-1 AV-2 OV-1 OV-2 Framework Product Name Overview and Summary Information Integrated Dictionary High-Level Operational Concept Graphic Operational Node Connectivity Description Operational Information Exchange Matrix Organizational Relationships Chart Operational Activity Model General Description Scope, purpose, intended users, environment depicted, analytical findings Data repository with definitions of all terms used in all products High-level graphical/ textual description of operational concept Operational nodes, operational activities performed at each node, connectivity and information exchange needlines between nodes Information exchanged between nodes and the relevant attributes of that exchange Organizational, role, or other relationships among organizations Operational Activities, relationships among activities, inputs and outputs. Overlays can show cost, performing nodes, or other pertinent information One of the three products used to describe operational activity sequence and timing - identifies business rules that constrain operation One of three products used to describe operational activity sequence and timing - identifies business process responses to events One of three products used to describe operational activity sequence and timing - traces actions in a scenario or sequence of events and specifies timing of events Documentation of the data requirements and structural business process rules of the Operational View. Identification of systems and system components and their interconnections, within and between nodes Systems nodes and their related communications lay-downs Relationships among systems in a given architecture; can be designed to show relationships of interest, e.g., system-type interfaces, planned vs. existing interfaces, etc. Functions performed by systems and the information flow among system functions
Mapping of systems back to operational capabilities or of system functions back to operational activities Provides details of systems data being exchanged between systems Performance characteristics of each system(s) hardware and software elements, for the appropriate timeframe(s) Planned incremental steps toward migrating a suite of systems to a more efficient suite, or toward evolving a current system to a future implementation Emerging technologies and software/hardware products that are expected to be available in a given set of timeframes, and that will affect future development of the architecture One of three products used to describe systems activity sequence and timingConstraints that are imposed on systems functionality due to some aspect of systems design or implementation One of three products used to describe systems activity sequence and timingResponses of a system to events One of three products used to describe systems activity sequence and timing -- System-specific refinements of critical sequences of events and the timing of these events Physical implementation of the information of the Logical Data Model, e.g., message formats, file structures, physical schema Extraction of standards that apply to the given architecture Description of emerging standards that are expected to apply to the given architecture, within an appropriate set of timeframes

Architecting Method Architectural Products Product Formats Architecture Validation Collaboration

Operational Operational

Operational Operational Operational

OV-3 OV-4 OV-5

Operational

OV-6a

Operational Rules Model

Operational

OV-6b

Operational State Transition Description Operational Event-Trace Description Logical Data Model Systems Interface Description Systems Communications Description Systems-Systems Matrix

Operational

OV-6c

Operational Systems Systems Systems

OV-7 SV-1 SV-2 SV-3

Systems
Systems

SV-4
SV-5

Systems Functionality Description

Operational Activity to Systems Function Traceability Matrix Systems Data Exchange Matrix Systems Performance Parameters Matrix Systems Evolution Description Systems Technology Forecast Systems Rules Model

Systems Systems Systems

SV-6 SV-7 SV-8

Systems

SV-9

Systems

SV-10a

Systems Systems

SV-10b SV-10c

Systems State Transition Description Systems Event-Trace Description Physical Schema Technical Standards Profile Technical Standards Forecast

Systems Technical

SV-11 TV-1 TV-2

The Department of Defense Architecture Framework (DoDAF) Final Draft Version 1.0

Technical

Building Blocks (contd)

Architecting Method Architectural Products
Supplementing the DoDAF Product Formats Architecture Validation Collaboration

The Zachman Framework For Enterprise Architecture

Building Blocks (contd)

DoDAF, Final Draft Version 1.0

Architecting Method Architectural Products Product Formats Architecture Validation Collaboration

DoDAF Templates Unified Modeling Language (UML) Integrated Computer-Aided

Manufacturing (ICAM) DEFinition (IDEF)

Building Blocks (contd)

Architecting Method Architectural Products Product Formats Architecture Validation Collaboration
Software Engineering Institute

Software Engineering Institutes

Architecture Tradeoff Analysis MethodSM Quality Attribute Assessment Techniques (e.g., Colored Petri Nets)
University of Aarhus CS Department

Building Blocks (contd)

Architecting Method Architectural Products Product Formats Architecture Validation Collaboration

REAP: A Unification of Standards

Raytheon Enterprise Architecture Process (REAP)
Applicable View All Views All Views Framework Product AV-1 AV-2 Framework Product Name Overview and Summary Information Integrated Dictionary High-Level Operational Concept Graphic Operational Node Connectivity Description Operational Information Exchange Matrix Organizational Relationships Chart Operational Activity Model General Description Scope, purpose, intended users, environment depicted, analytical findings Data repository with definitions of all terms used in all products High-level graphical/ textual description of operational concept Operational nodes, operational activities performed at each node, connectivity and information exchange needlines between nodes Information exchanged between nodes and the relevant attributes of that exchange Organizational, role, or other relationships among organizations Operational Activities, relationships among activities, inputs and outputs. Overlays can show cost, performing nodes, or other pertinent information One of the three products used to describe operational activity sequence and timing - identifies business rules that constrain operation One of three products used to describe operational activity sequence and timing - identifies business process responses to events One of three products used to describe operational activity sequence and timing - traces actions in a scenario or sequence of events and specifies timing of events Documentation of the data requirements and structural business process rules of the Operational View.

I Enterprise Understanding II Architecture Planning III Business Architecting IV Technical Architecting V Architecture Validation
Operational Operational OV-1 OV-2 Operational Operational Operational OV-3 OV-4 OV-5 Operational OV-6a Operational OV-6b Operational OV-6c Operational Systems Systems Systems OV-7 SV-1 SV-2 SV-3 Systems
Systems

Operational Rules Model

Operational State Transition Description Operational Event-Trace Description Logical Data Model Systems Interface Description Systems Communications Description Systems-Systems Matrix

Activity I

Identification of systems and system components and their interconnections, within and between nodes

Enterprise Understanding

Systems nodes and their related communications lay-downs Relationships among systems in a given architecture; can be designed to show relationships of interest, e.g., system-type interfaces, planned vs. existing interfaces, etc. Functions performed by systems and the information flow among system functions
Mapping of systems back to operational capabilities or of system functions back to operational activities Provides details of systems data being exchanged between systems

SV-4
SV-5

Systems Functionality Description

Operational Activity to Systems Function Traceability Matrix

Systems Systems Systems

SV-6 SV-7 SV-8

Activity V
Architecture Validation
Systems Evolution Description Systems Technology Forecast

Systems Data Exchange Matrix Systems Performance Parameters Matrix

Performance characteristics of each system(s) hardware and software elements, for the appropriate timeframe(s)

Planned incremental steps toward migrating a suite of systems to a more efficient suite, or toward evolving a current system to a future implementation Emerging technologies and software/hardware products that are expected to be available in a given set of timeframes, and that will affect future development of the architecture

Systems

SV-9

Five Activities of Architecture Process

Inter-Activity Iteration Intra-Activity Iteration

Activity II
Architecture Planning

Systems

SV-10a

Systems Rules Model

One of three products used to describe systems activity sequence and timingConstraints that are imposed on systems functionality due to some aspect of systems design or implementation One of three products used to describe systems activity sequence and timingResponses of a system to events

Systems Systems

SV-10b SV-10c

Systems State Transition Description Systems Event-Trace Description Physical Schema Technical Standards Profile Technical Standards Forecast

One of three products used to describe systems activity sequence and timing -- System-specific refinements of critical sequences of events and the timing of these events

Systems Technical Technical

SV-11 TV-1 TV-2

Physical implementation of the information of the Logical Data Model, e.g., message formats, file structures, physical schema Extraction of standards that apply to the given architecture Description of emerging standards that are expected to apply to the given architecture, within an appropriate set of timeframes

Activity IV
Technical Architecting
Software Engineering Institute

Activity III
Business Architecting

Activity I: Enterprise Understanding

Goals
Set context for architecture and
architecting activities Common understanding with customer on the [E/e]nterprise, the architecting initiative, and the problem space

Subprocesses

Customer-focused architecting Requirements analysis Operational/Business analysis Quality attribute analysis

TOGAF Relationship
ADM: Phase A
Activity I
Enterprise Understanding

Inputs
Customer vision, needs, &
requirements documents Domain expertise Industry & government standards

Outputs
DoDAF AV-1, Overview & Summary
Information DoDAF AV-2, Integrated Data Dictionary DoDAF OV-1, High Level Operational Concept Graphic DoDAF TV-1, Technical Standards Profile

Activity II: Architecture Planning

Goal
Establish a plan for the upcoming
architecting activities, the goals of the architecture and the architectural outputs

Subprocesses
Identify stakeholders Define architecture principles Identify architectural products, formats and
the supporting Zachman cells Define product relationships / dependencies Define schedule Select tool(s) Plan concordance, configuration & consolidation of architectural products Form/train Architecture Team

TOGAF Relationship
ADM: Preliminary Phase, Phase A
Activity II
Architecture Planning

Inputs
Customer vision, needs, &
requirements documents DoDAF AV-1, AV-2, OV-1, TV-1 Quality attribute-based requirements

Outputs
Architecture principles Architecture schedule Enhanced DoDAF AV-1, Overview &
Summary Information Architecture engineering environment

Activity III: Business Architecting

Goal
Model the customers view

Subprocesses
Collect Zachman Framework primitives
for Row 2 Produce mapping matrices as needed Model Business/Mission Scenarios

TOGAF Relationship
ADM: Phase B

Activity III
Business Architecting

Inputs
Customer vision, needs, &

Outputs
Business/Mission Scenarios within
DoDAF OV-5, Operational Activity Model Catalogued information from Zachman Framework Row 2 Cells

requirements documents Domain expertise Architecture principles DoDAF AV-1, AV-2, OV-1 Architecture engineering environment

Activity IV: Technical Architecting

Goal
Produce the remaining architectural
descriptions of the enterprise from a variety of views

Subprocesses

Develop/mature the defined DoDAF view

products Develop the defined additional architectural products Ensure concordance between architectural products Iteratively evolve an executable model

TOGAF Relationship
ADM: Phases C, D

Activity IV
Technical Architecting

Inputs
Business Architecture Customer vision, needs, &
requirements documents Domain expertise Architecture principles DoDAF AV-1, AV-2, OV-1, OV-5, TV-1 (and its referenced standards)

Outputs
Architecture Baseline Package Executable model

Activity V: Architecture Validation

Goal
Ensure the architecture is ready
to be implemented

Subprocesses
Architecture checklist ATAMSM Quality attribute assessments

Activity V
Architecture Validation

Inputs
Architecture Baseline Package Executable model

Outputs
Completed architecture checklist Simulation results SEIs Architecture Tradeoff
Analysis Method results Validated architecture
SM

Other Analysis Efforts

Enterprise Architecting Tools Object Management Groups Model-Driven Architecture UML 2.0 for Systems Engineering OMBs Federal Enterprise Architecture Reference Models CMMI and IEEE-1471 Mappings Standardized supplemental views Agile Modeling Open Systems Architectures Certification Programs

Summary
There are established industry and government standards to help
us address enterprise-wide architectural alignment between customer mission, strategic goals, business rules, data, application systems, organization, and technology.

No one standard or framework addresses all the aspects of the

architecting process. Unification is necessary to complete the picture.

Questions?

Rolf Siegers Raytheon Intelligence and Information Systems Garland, Texas [email protected] 972.205.5169

Customer Success Is Our Mission

Reference Links
The Open Group Architecture Framework, Version 8.0
http://www.opengroup.org/architecture/togaf8/index8.htm C4ISR Architecture Framework, Version 2.0 http://www.defenselink.mil/nii/org/cio/i3/AWG_Digital_Library/index.htm Department of Defense Architecture Framework, Version 1.0 (intermittent drafts appears on Mitres web site; final draft is currently
out, but no formal release statement has been issued yet)

Zachman Framework for Enterprise Architecture

http://www.zifa.com http://www.zachmaninternational.com Software Engineering Institutes Architecture Evaluations http://www.sei.cmu.edu/ata/ata_eval.html