Attachment 0023 DoDAF V 2.02 Version Description Doc.pdf

Department of Defense Office of the Assistant Secretary of Defense (OASD) for

Network Infrastructure and Integration (NII)

Version Description Document for

The DoD Architecture Framework (DoDAF) and

DoDAF Meta Model (DM2) Version 2.02

FINAL

30 September 2010

Distribution A

Version Description Document FINAL

DoDAF / DM2 version 2.02 30 September 2010

THIS PAGE INTENTIONALLY LEFT BLANK

i

Table of Contents

1. Purpose

2. Scope

3. Summary of Improvements Made in 2.02 ii

List of Figures and Tables

Table 1. DoDAF - DM2 2.02 Change Log ................................... Error! Bookmark not defined.

DoDAF / DM2 version 2.01 1 April 2010

1. Purpose

The purpose of this document is to describe changes made to DoDAF - DM2 2.01 to create

DoDAF - DM2 2.02.

2. Scope

The DoDAF 2.02, with its accompanying meta model, the DoDAF Meta Model (DM2), was baselined in August 2010. Improvements and corrections have been collected from the DoD EA community. These were logged and tracked by the DoDAF - DM2 Work Group (WG) secretariats following the processes and procedures documented in DoDAF - DM2 Configuration

Management Plan. These were prioritized and adjudicated by the DoDAF - DM2 WG in a consensual manner though weekly DoDAF - DM2 WG meetings. WG actionees implemented the changes as per WG adjudication and reported back to the WG for WG review of the implementation. Upon technical cutoff for DoDAF - DM2 version 2.02, the status of DoDAF -

DM2 change requests was:

Action Item /

Change Request

Status

Meaning Quantity

In Ver 2.01

These were action items and change requests taken by the

DoDAF - DM2 WG since baseline and release of DoDAF -

DM2 2.0 in May 2009 and selected for implementation by the

DoDAF - DM2 WG for 2.01 and successfully implemented and included in the 2.01 baseline.

In Ver 2.02

These were action items and change requests taken by the

DoDAF - DM2 WG since baseline and release of DoDAF -

DM2 2.01 in August 2010 and selected for implementation by the DoDAF - DM2 WG for 2.02 and successfully implemented and included in the 2.02 baseline.

Consult IDEAS

Group

Theses are action items and change requests that affect the DM2 formal ontology foundation, IDEAS, and thus must be referred to the IDEAS configuration management body for resolution.

Defer

Action items and change requests that are pending prioritization by the DoDAF - DM2 WG. If prioritized for the next baseline, the WG will determine course of action and assign researchers and implementers.

Unassigned New action items and change requests that have not been presented to the WG yet.

In Progress for

Ver 2.03

Action items and change requests that have been selected by the

WG for possible 2.03 inclusion.

TOTAL 338

3. Summary of Improvements Made in 2.02

There were 29 DoDAF-DM2 Action Items / Change Requests resolved by version 2.02. These are shown in detail in the table on the following pages. The changes fall into the following categories:

a. A Reification data group and associated diagram was created because of the key role reification plays in architectural and service descriptions and in associated system engineering.

b. The adoption of the IDEAS Measure model was completed. This had been started in 2.01 but was allowed to be completed by the addition of Properties of types and individuals.

c. Triples and tuples of tuples, though syntactically allowed, were not semantically defined and so they were restructured into couples that could be specialized from semantically defined IDEAS couples.

d. Began work on fine structure for Rules, Guidance, and Agreement including supertyping how rules constrain activities and role of parties to an agreement.

e. Redefined PersonType to be a PersonRoleType.

f. Continued work with OASIS, NCOIC, and OMG SoAML to refine the Services model including removal of service channel and handling of service layers via reification. This work is still on-going.

g. Improved the structure of the relationship between measuring rules and units of measure.

There is still work to be done here.

h. There were some cases of possible redundancy in the tuples such as

ActivityPerformedByPerformer and activityPerformableUnderCondition. These were restructured.

i. The MODAF concept of Enterprise Phase was determined to be most equivalent to

DoDAF’s Capability phase, which is a state of a Capability.

j. Some cleanup of Vision and Desired Effect structure that was a major change in 2.01.

k. Minor changes, e.g., for model formality, DoDAF documentation, XSD documentation.

The definitions of the column headers are as follows:

Log Field Description

# Sequential number for DoDAF - DM2 action items and change requests assigned by the DoDAF - DM2 WG secretariat

Title Short title of action item or change request for convenient reference by WG

Description Action item or change request as submitted by submitter

Date

Submitted

Date submitted

Source Submitter individual, group, venue, etc. and organization

CI The Configuration Item to which this AI/CR applies, i.e., DoDAF, DM2.

Data Group /

Model / other

The specific part of the CI to which the AI/CR pertains.

Status In Ver 2.02, In Progress for 2.02, In Progress for 2.03, Unassigned

(new), Consult IDEAS Group, Defer, Rejected,No Action Required

Action During resolution, this is the action(s) the WG determines need to be taken. Upon satisfactory completion, this is the record of what was changed.

Actionee The individual(s) assigned to research solutions and ultimately implement the solution the WG selects.