Integrating TOGAF, Zachman and DoDAF Into A Common Process

1
Integrating TOGAF, Zachman and DoDAF Into A
Common Process

• Rolf Siegers
• Senior Principal Software Systems Engineer
• November 2003

2
Topics

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

3
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 the highest level of a system or system of
  systems
• E a Department or Agency of the government

4
Why Architecture?
5
Why Architecture?

• Government

• Customer Expectations

• Industry

• Competition

• Academia

• Our Future

6
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
  integratedthrough 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
  2003
• Federal Enterprise Architecture Service Component
  2003 Technical Reference Models
• Federal Enterprise Architecture Business
  Reference Model 2002
• Federal/DoD Enterprise Architecture Certification
  Institute 2002
• Federal Enterprise Architecture Program
  Management Office 2001
• Treasury Enterprise Architecture Framework 2000
• Federal Enterprise Architecture Framework 1999
• C4ISR Architecture Framework 1996, 1997
• Establishment of CIO Council by Executive Order
  13011 1996
• Congressional acts (GPRA 1993 FASA 1994 ITMRA
  1996)
• Defense Science studies of early 1990s

7
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
  ServiceSAIC 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

8
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/printableAr
  ticle.jhtml?articleID6504197

9
Piecing The Puzzle TogetherWhats Needed In An
Architecting Process?

• Architecting Method

• Architectural Products

• Product Formats

• Architecture Validation

• Collaboration

10
Building Blocks

• Architecting Method
• Architectural Products
• Product Formats
• Architecture Validation
• Collaboration

The Open Group Architecture Framework
(TOGAF)Version 8.0Enterprise EditionArchitectur
e Development Method (ADM)
11
Building Blocks (contd)

• Architecting Method
• Architectural Products
• Product Formats
• Architecture Validation
• Collaboration

The Department of Defense Architecture Framework
(DoDAF)Final Draft Version 1.0
12
Building Blocks (contd)

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

The Zachman Framework ForEnterprise Architecture
13
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)

14
Building Blocks (contd)

• Architecting Method
• Architectural Products
• Product Formats
• Architecture Validation
• Collaboration

• Software Engineering Institutes Architecture
  Tradeoff Analysis MethodSM
• Quality Attribute Assessment Techniques (e.g.,
  Colored Petri Nets)

15
Building Blocks (contd)

• Architecting Method
• Architectural Products
• Product Formats
• Architecture Validation
• Collaboration

16
REAP A Unification of Standards

• Raytheon Enterprise Architecture Process (REAP)
• I Enterprise Understanding
• II Architecture Planning
• III Business Architecting
• IV Technical Architecting
• V Architecture Validation

17
Activity I Enterprise Understanding

• Goals
• Set context for architecture and architecting
  activities
• Common understanding with customer on the
  E/enterprise, the architecting initiative, and
  the problem space
• TOGAF Relationship
• ADM Phase A

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

• 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

18
Activity II Architecture Planning

• 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

• Goal
• Establish a plan for the upcoming architecting
  activities, the goals of the architecture and the
  architectural outputs
• TOGAF Relationship
• ADM Preliminary Phase, Phase A

• 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

19
Activity III Business Architecting

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

• Goal
• Model the customers view
• TOGAF Relationship
• ADM Phase B

• Inputs
• Customer vision, needs, requirements documents
• Domain expertise
• Architecture principles
• DoDAF AV-1, AV-2, OV-1
• Architecture engineering environment

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

20
Activity IV Technical Architecting

• Subprocesses
• Develop/mature the defined DoDAF view products
• Develop the defined additional architectural
  products
• Ensure concordance between architectural products
• Iteratively evolve an executable model

• Goal
• Produce the remaining architectural descriptions
  of the enterprise from a variety of views
• TOGAF Relationship
• ADM Phases C, D

• 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

21
Activity V Architecture Validation

• Goal
• Ensure the architecture is ready to be
  implemented

• Subprocesses
• Architecture checklist
• ATAMSM
• Quality attribute assessments

• Inputs
• Architecture Baseline Package
• Executable model

• Outputs
• Completed architecture checklist
• Simulation results
• SEIs Architecture Tradeoff Analysis MethodSM
  results
• Validated architecture

22
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

23
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.

24
Questions?

• Rolf Siegers
• Raytheon Intelligence and Information
  SystemsGarland, Texas
• rolf_siegers_at_raytheon.com
• 972.205.5169

25
Reference Links

• The Open Group Architecture Framework, Version
  8.0
• http//www.opengroup.org/architecture/togaf8/index
  8.htm
• C4ISR Architecture Framework, Version 2.0
• http//www.defenselink.mil/nii/org/cio/i3/AWG_Digi
  tal_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