The DoDAF Development Team Supporting OASD(NII) Architecture Directorate John V. Tieso [email protected] A Preview of DoDAF V2.0 This document contains.

The DoDAF Development TeamSupporting OASD(NII) Architecture Directorate

John V. [email protected]

A Preview of DoDAF V2.0

This document contains pre-decisional materials that has been authorized for use in limited public presentations by the Director, OASD(NII), Architecture Directorate. This

information is otherwise intended solely for the use and information of the client to whom it is addressed.

2Filename/RPS Number

Table Of Contents

DoDAF v2.0 – Where are we Now?

What are we doing with this version?

Organization

Perspectives

Meta Model Groups

Views

Models

3Filename/RPS Number

DoDAF v2.0 is emerging from the Development Cycle

Spirals I - III

– Volume 1 & 2 Reviewed and comments adjudicated

– Updated Draft out o/a 10 Dec

Spiral IV

– Physical Exchange Specification Draft, 29 Dec

– Community review and comment, 24 Jan – 4 Feb

– Adjudicate comments, 5 Feb – 26 Feb

– Send to DCIO for Approval

4Filename/RPS Number

This version is a major change from previous versions

Data-centric vs. product-centric

Wider range of example models (New name for old ‘products’)

“Fit-for-Purpose” Development Guidance

Better linkage to major departmental programs (e.g. JCIDS, DAS, PfM, SE, etc.) and the Federal Enterprise Architecture Framework

Integrated Data Model (Conceptual, Logical, and Physical Exchange Specification)

Backward compatibility with DoDAF 1.0, and DoDAF 1.5

Extended capability to support international and coalition partners

5Filename/RPS Number

DoDAF Version 2 has an entirely new Organization Structure

Three Volumes:

– Volume 1 – For Managers & Leaders

– Volume 2 – For Architects

– Volume 3 – For Data Engineers and Toolset Vendors

DoDAF Journal – On online reference in Wiki format to share information

The Defense Architecture Registry System (DARS) – Register Architectures here for sharing through Federation

The Defense Metadata Registry – For registration/discovery of reusable data

6Filename/RPS Number

DoDAF Metamodel Groups

7Filename/RPS Number

DoDAF Metamodel Groups

Performer

Resource Flow

Data & Information

Doctrine

Training/Skill/ Education

Capability

Services

Project

Goals

Rules

Measures

Location

Activity

8Filename/RPS Number

Metadata Groups to …….

Vie

ws

Mo

del

s

Co

re

Pro

cess

es

Metamodel Data Groups

AV, CV, DIV, OV, PV, DI, SeV,

StdV, SvcV, SysV

AV, CV, DIV, OV, PV, SeV, StdV, SvcV, SysV

J CIDS, DAS, PPBE, System Engineering, Operations, Portfolio Management (IT and

Capability)

Capability CV, PV, SysV, SvcV 

SysV-5, SysV-8, SvcV-5, SvcV-8, CV-1, CV-2, CV-3, CV-4, CV-5, CV-6, CV-

7, PV-3 J , D, P, S, O, C

Services

CV, StdV, SysV 

SysV-1, SysV-2, SysV-3, SysV-4, SysV-5, SysV-8, SvcV-1, SvcV-2, SvcV-3, SvcV-4, SvcV-5, SvcV-8,

StdV-1, StdV-2, CV-7 P, S

Project AV, CV, PV, SvcV, SysV,  

AV-1, SysV-8, SysV-9, SvcV-8, SvcV-9, StdV-1, StdV-2, PV-1, PV-2, PV-

3, CV-3, CV-5 D, P, S

Goals  CV, PV CV-1, PV-2 J , D, P, O, C

Rules OV, StdV,

SvcV, SysV

OV-6a, SysV-1, SysV-2, SysV-4, SysV-6, SysV-

10a, SvcV-1, SvcV-2, SvcV-4, SvcV-6, SvcV-

10a, StdV-1, StdV-2 J , D, S, O

9Filename/RPS Number

DoDAF 2.0 has an extensive set of Views

All V

iewO

verarchin

g asp

ects of arch

itecture co

ntext th

at relate to all view

s

Data an

d In

form

ation

Vie

wA

rticulate th

e data relatio

nsh

ips an

d alig

nm

ent stru

ctures in

the

architectu

re con

tent

Stan

dard

s View

Articu

late app

licable O

peratio

nal, B

usin

ess, Tech

nical, an

d In

du

stry p

olicy, stan

dard

s, gu

idan

ce, con

straints, an

d fo

recasts

Services ViewArticulate the performers,

activities, services, and their exchanges providing for, or supporting, DoD functions

9

Systems View

Articulate the legacy systems, their composition,

interconnectivity, and context providing for, or

supporting, DoD functions

System Engineering ViewArticulate activities to design and implement solution based

on operational and capability requirements

Operational ViewArticulate operational scenarios, processes, activities &

requirements

Pro

ject V

iewD

escribes th

e relation

ship

s betw

een o

peratio

nal an

d

capab

ility requ

iremen

ts and

the vario

us p

rojects b

eing

im

plem

ented

; Details d

epen

den

cies betw

een cap

ability

man

agem

ent an

d th

e Defen

se Acq

uisitio

n S

ystem p

rocess.

Capability ViewArticulate the capability requirement, delivery timing, and deployed capability

10Filename/RPS Number

Data &

Information

View

OV-7

Services

View

SV-11

All “Service”

Versions of

SV Products

Systems

View

All “Systems” Versions of SV Products

DoDAF V1.5

Capability

View

Project

View

System

Engineering

View

Standards

View

Operational

View

Rest of OVs

All TVs

All

ViewAll AVs

DoDAF V2.0

NewUpdated Moved

DoDAF Metamodel (DM2)

Fit ForPurpose

PresentationDashboards Graphical

DepictionsReference

ModelsFusion

ProductsCompositeProducts

11Filename/RPS Number

Questions?

12Filename/RPS Number

Backup Slides

13Filename/RPS Number

Organization of Volume 1Section 1: Introduction

Section 2: DoDAF and Journal Overview

Section 3: Enterprise Architecture

Section 4: Scoping Architecture to be “fit for purpose”

Section 5: Customer Requirements

Section 6: Methodologies

Section 7: Architecture Presentations

Section 8: DoDAF Metamodel

Section 9: Architecture Planning

Section 10: Architecture Based Analytics

Section 11: Configuration Management of the DoD Architecture Framework

Section 12: Relationships to Other Frameworks

14Filename/RPS Number

Organization of Volume 2

Section 1: Introduction to this Volume, including ‘What’s New” and “How-to”.

Section 2: Meta Model Data Groups

Section 3: ”Views” of DoDAF 2.0.

Appendix A: Acronyms

Appendix B: Glossary

Appendix C: DoDAF Meta Model

Appendix D: DoDAF Meta Model Data Dictionary

Appendix E: References

Appendix F: DoDAF V2.0 Presentation Development

15Filename/RPS Number

Operational Models

Model Description

OV-1: High Level Operational Concept Graphic

High-level graphical/textual description of operational concept

OV-2: Operational Connectivity Description

Operational connectivity and information exchange needlines

OV-3: Operational Information Exchange Matrix

Information exchanged and the relevant attributes of that exchange

OV-4: Organizational Relationships Chart

Organizational, role, or other relationships amongOrganizations

OV-5: Operational Activity Model

Capabilities, operational activities, relationships among activities, inputs, and outputs; overlays can show cost, performers or other pertinent information

OV-6a: Operational Rules ModelOne of three models used to describe operational activity - identifies business rules that constrain operation

OV-6b: State Transition Description

One of three models used to describe operational activity - identifies business process responses to events

OV-6c: Event-Trace DescriptionOne of three models used to describe operational activity - traces actions in a scenario or sequence of events

16Filename/RPS Number

Capability Models

Model Description

CV-1: VisionOverall vision for transformational endeavors,

provides a strategic context for the capabilities described, and provides a high-level scope.

CV-2: Capability TaxonomyA hierarchy of capabilities, specifies all the

capabilities that are referenced throughout one or more architectures.

CV-3: Capability PhasingPlanned achievement of capability at different points

in time or during specific periods of time.

CV-4: Capability Dependencies

Dependencies between planned capabilities and defines logical groupings of capabilities.

CV-5: Capability to Organizational Development Mapping

The fulfillment of capability requirements, shows the planned capability deployment and interconnection for a particular Capability Phase.

CV-6: Capability to Operational Activities Mapping

Mapping between the capabilities required and the operational activities that those capabilities support.

CV-7: Capability to Services Mapping

Mapping between capabilities and the services that these capabilities enable.

17Filename/RPS Number

Project Models

Models Descriptions

PV-1: Project Portfolio Relationships

Organizational structures needed to manage a portfolio of projects and shows dependency relationships between the organizations and projects.

PV-2: Project TimelinesA timeline perspective on programs or projects, with

the key milestones and interdependencies

PV-3: Project to Capability Mapping

Mapping of programs and projects to capabilities to show how the specific projects and program elements help to achieve a capability

18Filename/RPS Number

Service Models

Models Descriptions

SvcV-1 Services Interface DescriptionIdentification of services and service items and

their interconnections

SvcV-2 Services Communications Description

Services and service items and their related communications laydowns

SvcV-3a Systems-Services MatrixSvcV-3b Services-Services Matrix

Relationships among services in a given architecture; can be designed to show relationships of interest, e.g., service-type interfaces, planned vs. existing interfaces, etc.

SvcV-4 Services Functionality Description Functions performed by services and the service

data flows among service functions

SvcV-5 Operational Activity to Services Traceability Matrix

Mapping of services back to operational activities

SvcV-6 Services Data Exchange MatrixProvides details of system or service data

elements being exchanged between services and the attributes of that exchange

SvcV-7 Services Performance Parameters Matrix

Performance characteristics of Services View elements for the appropriate time frame(s)

19Filename/RPS Number

Service Models (Cont.)

Models Descriptions

SvcV-8 Services Evolution Description

Planned incremental steps toward migrating a suite of systems to a more efficient suite, or toward evolving a current services to a future implementation.

SvcV-9 Services Technology Forecast

Emerging technologies and software/hardware products that are expected to be available in a given set of time frames and that will affect future development of the architecture

SvcV-10a Services Rules Model

One of three models used to describe service functionality - identifies constraints that are imposed on systems functionality due to some aspect of systems design or implementation

SvcV-10b Services State Transition Description

One of three models used to describe service functionality - identifies responses of a services to events

SvcV-10c Services Event-Trace Description

One of three models used to describe service functionality - identifies service-specific refinements of critical sequences of events described in the Operational Model

20Filename/RPS Number

System Models

Models Descriptions

SysV-1 Systems Interface DescriptionIdentification of systems and system items and their

interconnections

SysV-2 Systems Communications Description

Systems and system items and their related communications laydowns

SysV-3 Systems-Systems Matrix

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.

SysV-4a Systems Functionality Description

Functions performed by systems and the system data flows among system functions

SysV-5a Operational Activity to Systems Function Traceability Matrix

Mapping of system functions back to operational activities

SysV-5b Operational Activity to Systems Traceability Matrix

Mapping of systems back to capabilities or operational activities

SysV-6 Systems Data Exchange Matrix

Provides details of system data elements being exchanged between systems and the attributes of that exchange

21Filename/RPS Number

System Models (Cont.)

Models Descriptions

SysV-7 Systems Performance Parameters Matrix

Performance characteristics of Systems Model elements for the appropriate time frame(s)

SysV-8 Systems Evolution DescriptionPlanned incremental steps toward migrating a suite of

systems to a more efficient suite, or toward evolving a current system to a future implementation.

SysV-9 Systems Technology Forecast

Emerging technologies and software/hardware products that are expected to be available in a given set of time frames and that will affect future development of the architecture

SysV-10a Systems Rules Model

One of three models used to describe system functionality—identifies constraints that are imposed on systems functionality due to some aspect of systems design or implementation

SysV-10b Systems State Transition Description

One of three models used to describe system functionality—identifies responses of a system to events

SysV-10c Systems Event-Trace Description

One of three models used to describe system functionality—identifies system-specific refinements of critical sequences of events described in the Operational View

22Filename/RPS Number

Standards Models

Models Descriptions

Standards View-1 Standards Profile (StdV-1)

Listing of standards that apply to solution elements in a given architecture

Standards View-2 Standards Forecast (StdV-2)

Description of emerging standards and potential impact on current solution elements, within a set of time frames

23Filename/RPS Number

Data and Information Models

Models Descriptions

DIV-1:Conceptual Data ModelRequired High level data concepts and their

relationships

DIV-2: Logical Data ModelDocumentation of the data requirements andstructural business process rules

DIV-3: Physical Data ModelPhysical implementation of the Logical Data Model

entities, e.g., message formats, file structures, physical schema

24Filename/RPS Number

All View Models

Models Descriptions

AV-1 Overview and Summary Information

Describes a Project's Visions, Goals, Objectives, Plans, Activities, Events, Conditions, Measures, Effects (Outcomes), and produced objects.

AV-2 Integrated DictionaryArchitecture data repository with definitions of all termsused throughout the architecture data and

presentations.

25Filename/RPS Number

Speaker’s BioJohn Tieso

Booz Allen Hamilton

John Tieso has had a long and distinguished record of achievement in assisting clients to effect desired change and improvement in their organizations. Prior to retirement from the Federal Government in 1997, Mr. Tieso was Deputy Director, Functional Process Improvement in the Office of the Deputy Assistant Secretary of Defense (Command, Control, Communications, and Intelligence) and was a principal in the development of the methodology and techniques for C4ISR Architecture. He was an active member of the teams that created the DoD Architecture Framework, Version 1.0, and subsequently served as the Configuration Control manager for changes to that document. He has been an active member of the DoDAF 2.0 revisions, and is the principal author for Volume I, the Decision-makers volume.

Mr. Tieso is well known for his efforts toward defining Business Process Reengineering (BPR), and was the project manager for development of the first BPR Practitioner’s Program within the DoD community.

Since retirement, Mr. Tieso has been Vice President and Director, Process Innovation at the D. Appleton Company in Fairfax VA., a principal engineer at Silver Bullet Solutions Inc., in Arlington, VA., and is now employed with Booz Allen Hamilton in support of the office of the Assistant Secretary of Defense (Network Information and Integration).

Mr. Tieso was honored by the IT community as a member of the Federal 100 Class of 1995, and has received a Life Achievement Award from the Industry Advisory Council for his work on Business Reengineering. He has also received awards from the Smithsonian Institution, The Computerworld Awards Program, Government Computer News, the Information Technology Association of America, and a number of other national and international groups.

John Tieso’s most recent work, Avoiding False Mirrors: Some Thoughts on Process Management Change in Innovative Organizations is in publication for release on November 1st, 2008.