Introduction NAME 24 Sep 2009 Mr. Michael Wayson Enterprise Architecture & Standards Directorate Office of the DoD Deputy Chief Information Officer (703)

Introduction

NAME24 Sep 2009

Mr. Michael Wayson

Enterprise Architecture & Standards Directorate

Office of the DoD Deputy Chief Information Officer

(703) 607-0482 [email protected]

DoDAF Definition

DoDAF V2.0 is the overarching, comprehensive framework and conceptual model enabling the development of architectures to facilitate DoD managers at all levels to make key decisions more effectively through organized information sharing across Department, Joint Capability Areas (JCAs), Component, and Program boundaries.

DoDAF V2.0 Goals

Support the Department’s core processes:1. Capabilities Integration and Development (JCIDS)2. Planning, Programming, Budgeting, and Execution

(PPBE)3. Acquisition System (DAS)4. Systems Engineering (SE)5. Operations Planning6. Capabilities Portfolio Management (CPM)

Establish guidance for architecture content as a function of purpose – “fit for purpose”

Increase utility and effectiveness of architectures via a rigorous data model – the DoDAF Meta Model (DM2) -- so the architectures can be integrated, analyzed, and evaluated to mathematical precision.

DoDAF V2.0What has been delivered?

DoDAF V2.0 (http://www.defenselink.mil/cio-nii/policy/eas.shtml)– Volume 1 – Manager’s Guide

Guidance for Development, Use, and Management of Architectures

– Volume 2 – Architect’s Guide Describes construction of Architectures, the

DODAF Meta-model, Data Exchange Requirements, and Development of the Architectural Models in technical detail

– Volume 3 – Developer’s Guide Introduces the DoDAF Meta-Model Physical

Exchange Specification

DKO DoDAF Journal

What has been delivered in the DKO DoDAF Journal (https://www.us.army.mil/suite/page/454707)– Models, Evaluation, Process– Other Information (

https://www.us.army.mil/suite/folder/17204298) Meta-Model Data Dictionary (Zip File) Physical Exchange Specification XSDs (Zip file) DoDAF Product Development Questionnaire Analysis

Report (Capability and Project View examples and others are here)

The DKO-S DoDAF Homepage is www.us.army.smil.mil/suite/page/9964.

Need a sponsored account if not Military or DoD Civilian

DoDAF V2.0 Promulgation Memo

Version 2.0 is the prescribed framework for all Department architectures and represents a substantial shift in approach. – Don’t redo current architecture

Architectures shall comply with Version 2.0 in their next major release.– Update only in the next release– Does not prevent early adoption of DoDAF

V2.0

Value of DoDAF V2.0

DoDAF V2.0 provides an overarching set of architecture concepts, guidance, best practices, and methods to enable and facilitate architecture development.

Fit-for-Purpose describes an architecture that is appropriately focused and directly support customer needs or improve the overall process undergoing change. The models provide choices, based upon the decision-maker needs.

Adoption of DoDAF V2.0 benefits the decision-maker and the architect with the freedom of presenting the architectural data in the terms for the decision-makers.

Facilitates development of architectural descriptions under Service-Oriented Architecture (SOA)-related techniques and tools

Adheres to the DoD Acquisition Life Cycle methodologies contained in the DoD Acquisition Guide

Can be used in conjunction with Lean Six Sigma and other Process Improvement methods

DoDAF V2.0 Focus

The DoDAF Meta-model (DM2) supports the architecture content of the DoD Core Processes

The relationships captured in DM2 supports qualitative and quantitative analysis

By being able to relate architectural descriptions, with a common architecture vocabulary, better analysis across architectural description can be performed

Focus: architecture DATA, not Products

Results: Better ANALYSIS and

Decisions.

Data allows better analytical results for the decision makers.

Shift from Product-Centric to Data-Centric Focus Prior versions of DoDAF and earlier C4ISR versions of

the Architecture Framework have emphasized reusable and interoperable data organized into ‘products’ (e.g., graphical representations or documents)

DoDAF V2.0 emphasizes focus on data, and relationships among and between data rather than the presentations of products– Emphasizes on utilizing architectural data to support

analysis and decision-making,– Greatly expands the types of graphical

representations that can be used to support decision-making activities.

– Supports innovative and flexible presentation of the architectural data in a meaningful, useful, and understandable manner

DoDAF 2.0 focuses architecture development to ‘Fit for Purpose’ DoDAF 2.0 introduces ‘Fit-for-Purpose’ architecture as

one that is appropriately focused on supporting the stated objectives

‘Fit-for-Purpose’ architectures– Respond to the stated goals and objectives of a

process owner– Are useful in the decision-making process– Respond to internal and external stakeholder

concerns ‘Fit-for-Purpose’ enables the architect to focus on

collecting data and creating views that are necessary for the decision-maker’s requirements, and focusing the architecture to align to the decision-maker’s needs

Data-Centric: Original DoDAF Views have been expanded to better organize information, and reflect data that practitioners actually use

Modified Viewpoints The original DoDAF Systems View has been separated into a Systems

Viewpoint (SV) and a Service Viewpoint (SvcV) to accommodate extension to both systems and software/services engineering practice

All the models of data (Conceptual, Logical, and Physical) have been moved into the Data & Information Viewpoint (DIV)

The Operational Viewpoint (OV) now describes rules and constraints for any function (business, intelligence, warfighting, etc)

Technical View (TV) has been updated to the Standards Viewpoint (StdV) to describe business, commercial, and doctrinal standards in addition to technical standards

The All Viewpoint (AV) is essentially the same.

New Viewpoints Capability Viewpoint (CV) focuses on Capability data in support of

Capability development and to standardize the capture of capability data Project Viewpoint (PV) focuses on the Portfolio Management/CPM

information to explicitly tie architecture data to project efforts

DoDAF Evolution To Support “Fit For Purpose” Architecture

(Published in 2003)

(Published in 2007)

DoDAF 1.5• Addresses Net-Centricity • Volume III is CADM & Architecture Data Strategy• Addresses Architecture Federation• Baseline for DoDAF 2.0• Shifted away from DoDAF mandating a set of products

DoDAFDoDAF

2.02.0

DoDAF 2.0• Cover Enterprise and Program Architecture• Emphasize Data versus Products• Tailored Presentation• AV-1 to capture federation metadata• Quality Support to Decision Processes• FEA & Allied/Coalition Support• Journal - Errata & Interim Releases

DoDAF 1.0• CADM Separate• Baseline For DoDAF 1.5• Removed Essential & Supporting Designations• Expanded audience to all of DoD

Data &

Information

Viewpoint

OV-7

Services

Viewpoint

SV-11

All “Service”

Versions of

SV Products

Systems

Viewpoint

All “Systems” Versions of SV Products

DoDAF V1.5

Capability

Viewpoint

Project

Viewpoint

Standards

Viewpoint

Operational

Viewpoint

Rest of OVs

All TVs

All

ViewpointAll AVs

DoDAF V2.0

NewUpdated Moved

DoDAF Metamodel (DM2)

Fit ForPurpose

PresentationDashboards Graphical

DepictionsReference

ModelsFusion

ProductsCompositeProducts

Perspectives: Viewpoints That Fit-the-Purpose

Architecture viewpoints are composed of data that has been organized to facilitate understanding.

All V

iewp

oin

tO

ve

rarc

hin

g a

sp

ec

ts o

f arc

hite

ctu

re c

on

tex

t tha

t rela

te to

all

mo

de

ls

Data an

d In

form

ation

View

po

int

Artic

ula

te th

e d

ata

rela

tion

sh

ips

an

d a

lign

me

nt s

truc

ture

s in

th

e a

rch

itec

ture

co

nte

nt

Stan

dard

s View

po

int

Artic

ula

te a

pp

lica

ble

Op

era

tion

al, B

us

ine

ss

, Te

ch

nic

al, a

nd

In

du

stry

po

licy

, sta

nd

ard

s, g

uid

an

ce

, co

ns

train

ts, a

nd

fo

rec

as

ts

Systems Viewpoint

Articulate the legacy systems or independent systems, their composition,

interconnectivity, and context providing for, or supporting, DoD functions

Services Viewpoint

Articulate the performers, activities, services, and their exchanges providing

for, or supporting, DoD functions

Operational Viewpoint

Articulate operational scenarios, processes, activities & requirements

Capability Viewpoint Articulate the capability requirement,

delivery timing, and deployed capability

Pro

ject View

po

int

De

sc

ribe

s th

e re

latio

ns

hip

s b

etw

ee

n o

pe

ratio

na

l an

d c

ap

ab

ility

req

uire

me

nts

an

d th

e v

ario

us

pro

jec

ts b

ein

g im

ple

me

nte

d;

De

tails

de

pe

nd

en

cie

s b

etw

ee

n c

ap

ab

ility m

an

ag

em

en

t an

d th

e

De

fen

se

Ac

qu

isitio

n S

ys

tem

pro

ce

ss

.

DoDAF V2.0

The logo indicates the change with DoDAF V2.0. With authoritative data, using a vocabulary for architects, a development method, and desired presentations, an architectural description can be ‘Fit-for-Purpose’ for the Decision-makers.

“Fit for Purpose” Architecture Descriptions

Models

Based on models and authoritative information (data), the architectural description can support desired presentations for multiple purposes.

DoDAF V2.0 Focus: Terms

DoDAF V1.5 DoDAF V2.0

Architecture Architectural Description

Architecture data Architectural data

Product Model (a template for collecting data)

Product View (a model with data for an architecture)

View Viewpoint

Models are templates for organizing and displaying data in DoDAF 2.0

– Previous versions of DoDAF referred to these as ‘Products’

– An example of a Model is an OV-2, OV-5, SV-1, CV-5 Views are the result of collecting and populating Models with data and then presenting it

– Views are a Model populated with specific data

– An example of a view is a MOC OV-2, MDA OV-6c, NAVFAC SV-1 Viewpoints are a collection of models/views

– Previous versions of DoDAF just referred to these as ‘Views’

– Examples include: All Viewpoint (AV), Operational Viewpoints (OV), Capability Viewpoint (CV) The collection of information, specifically Views and/or Viewpoints, used to document the

architecture is referred to as an Architectural Description

– Previous versions of DoDAF referred to these as just an ‘Architecture’

Alignment with ISO 42010 and 15407

DoDAF V2.0 Focus: Architecture Models + Data = Architectural Description

Fit-for-Purpose (FFP)

Architecture

ModelsArchitectural Description

Fit-for-Purpose describes an architecture that is appropriately focused and directly support customer needs or improve the overall process undergoing change. The models provide choices, based upon the decision-maker needs.

Architecture

Data + Metadata

Things

Individuals

Types or classes of individuals or things

Operational Model

Example

Methodology: DoDAF V2.0 Six-Step Architecture Development Process

Determine theintended use of the architecture

Determine theintended use of the architecture

1

Determinescope of

architecture

Determinescope of

architecture

2Determine data

required tosupport

architecturedevelopment

Determine datarequired to

supportarchitecturedevelopment

3Collect, organize,

correlate, andstore architecture

data

Collect, organize,correlate, and

store architecturedata

4Conduct

analyses insupport of

architectureobjectives

Conductanalyses insupport of

architectureobjectives

5Document

Results IAWDecision-Maker

needs

DocumentResults IAW

Decision-Makerneeds

6

Provide list of data needed and use

cases

Provide list of data needed and use

cases

3.1

Model toDM2 Concept

List

Model toDM2 Concept

List

Review list of architecture dataand determine if it meets the use

cases

Review list of architecture dataand determine if it meets the use

cases

3.2

DM2 ConceptualData Model &

Logical Data Model

DM2 ConceptualData Model &

Logical Data Model

Assist with the Architect’s

data collectionprocesses

Assist with the Architect’s

data collectionprocesses

4.1

List of architecture

data

List of architecture

data

PotentialCollectionMethods

PotentialCollectionMethods

SelectedCollectionMethods

SelectedCollectionMethods

Verify the datacollected meetsthe use cases

Verify the datacollected meetsthe use cases

5.1

ExampleUses

ExampleUses

Fit-for-PurposeUse

Fit-for-PurposeUse

Determine howdata needs to be

presented

Determine howdata needs to be

presented

6.1

LegacyProducts

LegacyProducts User

Requirements

UserRequirements Example

Presentations

ExamplePresentations

Fit-for-PurposePresentations

Fit-for-PurposePresentations

Detailed Steps forDecision-Maker

With the updated process, DoDAF V2.0 describes Roles and Responsibilities for the Decision-maker throughout the architecture development effort.

Capture and express Architectural Descriptions in a common, understood language for the exchange of architecture information

Data: DoDAF Meta-Model (DM2) Purposes:

– The vocabulary for description and discourse about DoDAF models (formerly “products”) and core process usage

– Specification for federated data exchange between: architecture development and analysis tools architecture databases other authoritative data sources

– Support discovery and understandability tenants of NCDS:

Discovery DM2 categories of information Understandability thru precise semantics augmented

with linguistic traceability

Data may be activity data, system or service data, or network data, or any of a number of data categories that contain appropriate data.

Data: Types of Data in DoDAF V2.0 (known as Conceptual Data)

Performers

Resource Flows

Information and Data

Training, Skill, Education

Capabilities

Services

Projects

Goals

Rules

Measures

Locations

Activities

The DoDAF Meta-model Improvements

High-level conceptual model developed with easily understood terms and descriptions

Semantically correct without broken or obscure associations and relationships

Only that data related to architecture development in Departmental core processes

Extensible and Scalable to support “Fit-for-Purpose” developments

Small and compact versus large, cumbersome, and difficult to read

DoDAF V2.0 Conformance

The data in an architectural description is defined according to the DoDAF Meta-model (DM2) concepts, associations, and attributes.– The information captured in an architecture tool is consistent

with the DM2 concepts, association, and attributes.– Architectural data should be stored in a recognized

commercial architecture tool that conforms to industry standards.

– Tools, preferably data-driven, can be used for the PRESENTATION of architectural data, but it must be based on DATA.

The architecture data is capable of transfer in accordance with the UPDM and PES

DoDAF Meta-model (DM2) and Unified Profile for DoDAF and MODAF (UPDM)

DoDAF Meta-model (DM2)/Physical Exchange Specification (PES) – A data model that defines conceptual, logical, and physical views of the information requirements for DoD architectures.– A language for the DoD architect– A model for ALL tool vendors– An exchange schema for interoperability

Unified Profile for DoDAF and MODAF (UPDM) 1.0 – An Object Management Group specification for UML tool vendors to follow for consistent representations/exchanges of DoDAF V1.5/MODAF V1.2 architectures.– A specification from which UML/SYSML tool vendors can

implement UPDM 2.0 – A new effort by the Object Management Group to

update UPDM for DoDAF V2.0 and MODAF V1.3.

DISR and MDR

DoD Information Technology Standards and Profile Registry (DISR) – Registry of standards for the Department; UPDM is in DISR because it is a standard developed by a Voluntary Consensus Standards body.

DoD Metadata Registry (MDR) – A registry of data models, vocabularies, and schemas to support COI collaboration

DoDAF V2.0 Summary DoDAF V2.0 provides an overarching set of architecture

concepts, guidance, best practices, and methods to enable and facilitate architecture development.

It is all about the decision-makers and the data! Fit-for-Purpose describes an architecture that is appropriately

focused and directly support customer needs or improve the overall process undergoing change. The models provide choices, based upon the decision-maker needs.

Adoption of DoDAF V2.0 benefits the decision-maker and the architect with the freedom of presenting the architectural data in the terms for the decision-makers.

DoDAF V2.0 is available at:– http://www.defenselink.mil/cio-nii/policy/eas.shtml– https://www.us.army.mil/suite/page/454707

The DKO-S DoDAF Homepage is www.us.army.smil.mil/suite/page/9964.