© 2014 IBM Corporation

Technique for Generating DoDAF2 OV-03 and SV-06 Matrix Reports using Project Specific Measurements, Resources and Resource Flows

Chuck FarisSenior Enterprise Architecture SpecialistIBM Rational Unleash the Labscfaris@us.ibm.com

© 2014 IBM Corporation

Why This Technique is Useful in DoDAF2

Provides a flexible workflow supporting the creation and use of custom measurements and attributes needed to describe the Resources in Resource Flows reported on in OV-03 Operational Resource Flow Matrix, SV-06 System Resource Flow Matrix and other reports

Supports user creation of OV-05b/SV-04 and auto-generation of Exchanges (OV-06c/SV-10c), Need Lines (OV-02) and System Resource Flows (SV-01 and SV-02)

Contains a mechanism for creation and maintenance of needed measurements and attributes without metamodel changes

Supports the creation and reuse of DoDAF2 Resources and subtypes (data, information, materiel, system, etc.) containing the Measurement Instances and Attributes

Supports the creation and assignment of Resources to Resource Flows (ActivityResourceOverlap, System Data Flow, Service Data Flow)

– Other definition types containing a Resource property can have Resources assigned but they will not be included in OV-03 and SV-06 reports

Generates OV-03 and SV-06 reports based on your Measurements, Resources and Resource Flows in prescribed structure

Measurement Types : Boolean, Date, Fixed-List, Numeric or Text and their Unit Of Measure

– Fixed-List collects the list elements and provides a drop-down list of elements

Also used in FEAF2 and can be used in other frameworks

2

© 2014 IBM Corporation

Generated System Architect Report Generator sample OV-03 Operational Resource Flow Matrix based on custom Measurements used in Resources in Resource Flows and generated Need Lines – Same for SV-06

OV-03 Operational Resource Flow Matrix and SV-06 System Resource Flow Matrix

3

© 2014 IBM Corporation

Structure Used in OV-03 and SV-06 Report Generation

Resource Flow (High Level)•Need Line•System Resource Flow

Exchange•Operational Exchange•System Exchange

Resource Flow (Low Level)•ActivityResourceOverlap•System Data Flow

Resource subtype structure•Resource

•Information•Data•Architectural Description•Domain Information

•Materiel•Performer

•System•Service•Service Interface•Person•Organization•Interface (Port)

Activity subtype structure•Activity

•System Function•Service Function

Role

Performer

Role

Performer Resource Flow (High Level)

Generate

Build

OV-02/SV-01

OV-06c/SV-10c

OV-03/SV-06

Activity &Performer

Activity &Performer

Exchange

Resource Flow (Low Level)

OV-05b/SV-04

Resources

Measurement Instances

Measurement Sets and Types

© 2014 IBM Corporation5

Workflow – Measurement Creation to Report Generation

Create the needed Measurement Sets, Types and Values

Create the Resources that will flow in the Resource Flows (any DoDAF2 Resource subtype: Data, Information and Materiel are a few of the subtypes)

Assign Resources to Low Level Resource Flows

– Low Level Resource Flows are: ActivityResourceOverlaps, System Data Flows and Service Data Flow

Create and Assign Measurement Instances to the Resources in Low Level Resource Flows to include in OV-03 and SV-06

– Top-down by working in a Resource and creating Measurement Instances as needed

– Bottom-up by creating the Measurement Instances, then using them in Resources

Using System Architect DoDAF2 Utilities under the Tools menu, Generate Operational Exchanges and Need Lines or System Exchanges and System Resource Flows or Service Resource Flows from low level Resource Flows

Rename generated Resource Flows, Exchanges and Roles if needed

Using System Architect Report Generator, Generate OV-03 Operational Resource Flow Matrix or SV-06 System Resource Flow Matrix

Steps can be done in many sequences – for example after generating an OV-03 report add other Resources to Resource Flows or other Measurement Instances to Resources and rerun the OV-03

© 2014 IBM Corporation6

Creating Measurement Sets and Measurement Types

Used in creation of Measurement Instances

Measurement Sets contain collections of Measurement Types

Measurement Types contain collections of Measurement Values when Measurement Type is “Fixed List”

Measurement Types also containOne Unit of MeasureOne Value Type

© 2014 IBM Corporation7

Creating a Measurement Instance

Select Measurement Set

Select Measurement Type based on restricted list

Value Type completed from Measurement Type

Select Value from fixed list or fill in the Value depending on Value Type

Report Value populated on OK

© 2014 IBM Corporation8

Using Measurement Instances in a Resource in a Resource Flow

DoDAF2 Resources including all Resource subtypes (data, information, material, person, etc.) can contain Measurement Instances and can be assigned to Resource Flows

Open or create a Resource that will be assigned to a Resource Flow.

Add the Measurement Instances you need to the Resource. Measurement Instances can be created in their containers, top-down, or they can be reused.

Assign the Resource to an ActivityResourceOverlap System Data Flow or Service Data Flow

Note: Measurements are also enabled in in other DoDAF2 and FEAF2 definitions

© 2014 IBM Corporation9

Generating High Level Views from Low Level

Auto Generation from low level to high level (ActivityResourceOverlap to Need Line for example) supports tracability and drill-down access to Low Level Resource Flows, their Resources and their Measurement Instances

Create Low Level View such as OV-05b BPMN Operational Activity Model populated with Sequence/Message Flows (DoDAF2 ActivityResourceOverlap)

Generate Operational Exchanges and Need Lines using the DoDAF2 Utilities (Tools > DoDAF2 Utilities)

Refresh the diagram and the generated Need Lines become visible

Open one of the Need Lines and drill down through Operational Exchange, ActivityResourceOverlap and Resource to see Measurements

Generate OV-03 Operational Resource Flow Matrix

© 2014 IBM Corporation

Measurement Instance – Technical View

Measurement Instance contains:

One Measurement Set

One Measurement Type restricted based on selected Measurement Set

One Value Type and One Unit of Measure (UOM) based on Measurement Type

For “Fixed List” Value Type, Value is restricted based on selected Measurement Type

For Value Types Boolean, Date, Numeric or Text Value Type, the Value is not read only and is user entered

Technical Changes to version 11.4.3.2

Removed GUID key from Measurement Instance to support top-down creation

Added Report Value property to Measurement Instance to support single property for Report Generator use

Added macro to update Report Value property including top-down creation and change to Measurement Instance

Added OV-03 and SV-06 reports based on this technique

© 2014 IBM Corporation11

Measurement Instance Use in Other Frameworks

Measurement Instance use is preset in DoDAF2 and FEAF2

To use Measurement Instances in a framework other than DoDAF2 and FEAF2, add the following to any definition type in the USRPROPS.TXT file:

PROPERTY "Measurement Instances"{ EDIT ListOf "Measurement Instance" …..}

– The property name must be “Measurement Instances” to populate the Report Value property from the type specific values

– The referenced definition type must be “Measurement Instance” to access the correct definition type and its supporting definition types.

Enable Measurement Sets on the advanced page of the System Architect Configuration dialog

Use the Report Value property for reports since it will contain each Measurement Instance’s value regardless of its Value Type

© 2014 IBM Corporation12

Thank You!

© 2014 IBM Corporation

Measurement Instance Properties

Measurement Relationships

NameMeasurement

Set

Fixed List Value

MeasurementType

Unit ofMeasure

Measurement Value--Rank

Measurement Type--Unit Of Measure--Value Type

MeasurementSet

ONEOF

LISTOF

LISTOF

Value Type• Date• Text• Numeric• Boolean• Fixed List

ReportValue

Boolean Value

Numeric Value

Text ValueText Value

Date Value

ONEOF

ONEOF