1

UML Profile for DoDAF/MODAF

Information SessionCo-Hosted by:

DoD CIO/Architecture & Interoperability and SAF/Enterprise Architecting and

Warfighting Integration Decision Support Division

16 May 2007Brian WilczynskiArchitecture & Interoperability Directorate

Office of the DoD CIO

2

Core Architecture Data Model

All View

Syste

ms/S

ervic

esView

Technical Standards View

Operational View

Beyond DoDAF 1.5

https://dars1.army.mil

3

Major Changes in DoDAF 1.5:

Incorporated Net-Centric Content

Changed Systems View to Systems/Services View

Re-Packaged 3 Volume Set

– Integrated CADM

– Added Journal

4

DoDAF v2.0 Potential Topics

Operational Node

Relationship to NCOW RM

Relationship to FEAStrategic Goals

Alignment to JCIDS/JROC

Information Assurance/Security

Service Specification Template

Net-Centricity

Service Oriented Architecture

Net-Centric Examples

Architecture Tiers

Service Interfaces

Authoritative Sources

BPMN

Capability related concepts

Measurement concepts

SA and OO

Other FrameworksOther Frameworks

Service Description FrameworkService Description Framework

Scoping Workshop in June 2007

UPDM

ABM/ASM

Program vs. Enterprise Architecture Content

5

DoDAF1.5

BaselineConcept

Map

Analysis ofExternal

RequirementsInitial Input

For DoDAF 2.0InputFor

Derive

DAS ProcessJCIDS ProcessPfM ProcessExternal ReportingPPBE ProcessIRB Processes

DoDAF2.0

AnalysisOf

Frameworks

MODAFTOGAF

NAF

Initial Requirements Set For

2.0Concept

Map

Re-validate Through

Finalized Requirements For

LeadsTo

2.0Model

AnalysisBaseline

For

ASM BTAUPDM CADM

2.0Conceptual

DataModel

Derive

2.0Physical

DataModel

2.0Logical

DataModel

Derive

Derive

DoDAF v2.0 Planned Approach

6

Summary Our approach to architecture must be as agile as the

processes and technology we describe Use DoDAF 1.5 requirements as baseline for DoDAF 2.0 The Core Architecture Data Model (CADM) will be derived

from DoDAF 2.0 requirements– Structure and content may change– The name is the same

Establish standards so that architecture data is net-centric DoDAF v2.0 must address evolving information

requirements of the Department using both top-down and bottom-up approaches