enterprise architecture - dodaf

© 2006 Vitech Corporation. All rights reserved.

Enterprise Architecture -

DoDAF

Capturing a DODAF Architecture in CORE

Clifford Levine

Vitech Corporation


Presentation Objectives

• Demonstrate how to implement MBSE

methodology to build a DoDAF Architecture

using CORE®

• Solve a sample problem while at the same time,

generate a complete set of DoDAF views

• Provide you the knowledge and skills to take

back to your team and organization

12/2008 DoDAF- 2


Presentation Outline

– Using Model-based systems engineering

concepts

– The CORE® Environment

– Introduction to Tactical Image Management

System example

– Capturing the Architecture

– Generating DoDAF Views

– Summary and review

12/2008 DoDAF- 3

© 2006 Vitech Corporation. All rights reserved.12/2008 DoDAF- 4

Model Base Systems Engineering


Model Base Systems Engineering

12/2008 DoDAF- 5

Problem

Definition

Behavioral

Analysis

Architecture

Synthesis

Integrated, Consistent Analysis: Complete Specifications, Project Documentation, Queries & Models

Source

MaterialDoDAF

Views


Why MBSE?

• Convergent

• Model-based

• Concurrent engineering

• Layered, hierarchical solution

• Central engineering repository

– Incorporating system definition language

• With graphical control constructs

• Executable, dynamic validation of system logic

• Context free

• Automated artifact generation

12/2008 DoDAF- 6


CORE Environment


CORE System Definition Language

12/2008 DoDAF- 8

CORE

Language

English

Equivalent

CORE Example

Element Noun • Operational Node Brigade Level

• Operational Activity Receive Orders

• Component Troop Carrier

Relationship Verb • Operational Activity are allocated to

Operational Node

Attribute Adjective • Description

• Number

Attribute of

Relationship

Adverb Resource consumed by Function

• Amount

Structure N/A • Viewed as Enhanced FFBD or FFBD

SDL is an Extended Natural Language in ERA Format


A Partial ERA Example

12/2008 DoDAF- 9

•Description

•Number

•Structure

Operational Node

comprised of

(member of)

comprised of

(member of)

performs

(allocated to)

performs

(allocated to)

Implemented by

(implements)

Implemented by

(implements)

•Description

•Number

•Structure

Operational Activity

•Description

•Number

•Structure

Component

•Description

•Number

•Structure

Function

•Description

•Number

Architecture

Operational Elements System Domain


CORE Project Explorer

12/2008 DoDAF- 10


Tactical Image Management

Architecture


TIM Context View

12/2008 DoDAF- 12

Description:

The Tactical Image Management Architecture

is composed of both an operational element

and an image management system which

supports the architecture.


Operational Behavior

12/2008 DoDAF- 13

This diagram

becomes an

OV-6


Data to be Collected

12/2008 DoDAF- 14


DoDAF Views


OV-3 Operational Information

Exchange Matrix

• Description:

– Information exchanged between nodes and the

relevant attributes of that exchange

• CORE Implementation

– Outputs the information exchange requirements for

the OperationalNodes that comprise the user selected

Architecture or OperationalNode. Optionally outputs

an Elements Definitions Table.

12/2008 DoDAF- 16


Operational Information Exchange

Matrix (OV-3)

12/2008 DoDAF- 17


Operational Information Exchange

Matrix (OV-3)


SV-1 System Interface Diagram

• Description

– Identification of systems nodes, systems, system

items, services, and service items and their

interconnections, within and between nodes

• CORE Implementation

– Outputs a Physical Block Diagram for the user

selected Component or a user selected ExternalFile

for the Component.

12/2008 DoDAF- 19


System Interface Diagram (SV-1)

12/2008 DoDAF- 20


Summary


Impleting DoDAF in CORE

12/2008 DoDAF- 22

• Extended the underlying systems engineering design

language to embrace operational architecture

development

• Apply the MBSE approach to integrated operational and

system architectures

– DoDAF views are by-products architecture development

– Integrated architecture data and views are always synchronized

• Ability to identify critical decision elements that are part

of the architecture and be able to ‘tune’ them for decision

support


Benefits of Integrated Repository

12/2008 DoDAF- 23

Viewgraph Engineering Model-Based SE

Independent drawings Consistent views

Static diagrams Executable behavior[1]

Data storage Linked repository

Stored views Dynamic view generation

Ad hoc process (inconsistent

results)

Repeatable process (consistent

results)

Manual change propagation across

all affected products (by the system

engineer)

Automatic change propagation

across all current and future

products (by the engineering

environment)

[1] Executable behavior eliminates structural or dynamic inconsistencies from the requirements.


Summation

• A way to produce architecture view artifacts (OV,

SV, and TV’s) that meet the wants and desires

of the DoD customer

• A way to deliver System and Architecture views

to users, stakeholders, and customers that

support each of their analytical tasks

• A way to produce Integrated Architectures

• A way to produce ‘Executable Architectures’

• A methodology to do the above

12/2008 DoDAF- 24

enterprise architecture - dodaf

Education

rights reserved

dodaf architecture

architecture

dodaf

implements

member

allocated