DoDAF Enterprise Architecture Framework Basics

1
DoDAF Enterprise Architecture Framework Basics
2
3. Overview of the Core Products
Core products are those that are recommended
for most architectures, and/or those that have
been adopted by other frameworks
3
All Views Products Capture Information That
Applies to the Architecture Overall
Core Products
Overview and Summary Information

• Identification
• Name
• Architect
• Organizations Involved
• When Developed
• Purpose
• Analysis Needs
• Decision Support Needs
• Scope
• Views and Products Used
• Time Frames Addressed
• Context
• Mission
• Geographical
• Rules, Criteria, and Conventions Followed

Integrated Dictionary
Integrated Dictionary
At a minimum, the integrated Dictionary is a
glossary with definitions of terms used in the
given architecture description. Each labeled
graphical item in the graphical representations
should have a corresponding entry in
the Integrated Dictionary.
4
The Operational View Captures the Critical
Mission Relationships and Information Exchanges
Core Products
Operational Information Exchange Matrix
Activity Model
Operational Node Connectivity Description
High-Level Operational Concept Description
From External Node

• Information Description
• Name/Identifier
• Definition
• Media
• Size
• Units
• Information Exchange Attributes
• Frequency, Timeliness, Throughput
• Security
• Interoperability Requirements
• Information Source
• Information Destination

Information Exchange 1
Node
B
Activity 2Activity 3
Node
C
Activity 3
Activity 1 Activity 2
Node
A
To External Node
Operational nodes, activities performed at each
node, node-to-node relationships, and
information needlines
High-level graphical description of the
operational concept of interest
Operational activities performed and their
input/output relationships
Information exchanged between nodes and the
relevant attributes of the exchanges
5
A Closer Look at the Operational Node
Connectivity Description OV-2
Shows that Node C needs information of type X,
and that Node B is tasked with providing that
information.
Showing Physical Nodes
6
A Closer Look at the Operational Node
Connectivity Description OV-2 continued
Showing Logical Nodes
7
A Closer Look at the Operational Information
Exchange Matrix OV-3
There is a listing of distinct information
exchanges ...
And their attributes
For each needline ...
8
What About the Case in Which All Nodes Get All
Information - Everyone Sees Everything?

• Architectures should be built with a specific
  purpose and scope in mind (more on that later)
• Even when everyone can see everything, it is
  usually not the case that everyone needs to see
  everything for every purpose
• Needlines on the Node Connectivity Description
  show which nodes need to be connected for the
  purposes being addressed in the architecture
• The Information Exchange Matrix shows attributes
  of those exchanges that are relevant to the
  purposes being addressed in the architecture
• If in fact all nodes do need to be connected to
  all other nodes, this can be shown graphically
  in a shorthand way, but the Integrated Dictionary
  must capture each individual connection. An
  automated tool is essential for this.
• This universal connectivity can be shown also in
  the System Interface Description and System
  Communications Description (see later example)

9
The Systems View Examines Current and Postulated
IS Capabilities in Context with Mission
Operations
Core Product System Interface Description
Internodal Node-Edge-to-Node-Edge
Internodal System-to-System
Intranodal
Intrasystem

Interface 1
COMMUNICATIONS NETWORK
Interface 2
NODE B
SYSTEM
3
COMMUNICATIONS
FROM/TO OTHER
NETWORK
NODES
10
Web-based Example (All Nodes Can Get All
Information) Federal Commons System Interface
Description

Web grid indicates that all nodes can receive
all information
Color coded lines indicate which nodes need
which information
11
The Technical View Identifies the Implementation
Criteria That Govern the Given Architecture
Core Product Technical Standards Profile
Services View
Interfaces View
12
The Framework Specifies Common Architecture Data
Core Products - Operational View
Entities and Attributes
The Framework provides a description of the data
that must be captured in each architecture
product. This product data is listed in
Product Data Element Tables.
13
Example - Data Element Table for the Operational
Node Connectivity Description (Extract)
14
The Core Products Link to Each Other
HIGH-LEVEL OPERATIONALCONCEPT DESCRIPTION (OV-1)
TECHNICAL STANDARDS PROFILE (TV-1)
VALUE ADDED SUMMARY LEVEL REPRESENTATION OF
ORGANIZATIONS/ROLES, MISSION, AND CONTEXT FOR THE
ARCHITECTURE
VALUE ADDED COMPLETE LIST OF RELEVANT STANDARDS
WITH OPTIONS PARAMETERS
OPERATIONAL CONCEPTROLES MISSIONS SET SCOPE
FOR ACTIVITY MODEL
STANDARDS APPLY AT SYSTEM TO SYSTEM INTERFACES

• ACTIVITIES MAP TO OPERATIONAL NODES
• I/OS MAP TO NEEDLINES
• PERFORMERS OF ACTIVITIES, IF SHOWN ON 0V-5,
  MAP TO OPERATIONAL NODES

ACTIVITY MODEL (OV-5)
SYSTEMS INTERFACE DESCRIPTION (SV-1)
OPERATIONAL CONCEPTCONNECTIVITY
INFORMATIONEXCHANGES, IF SHOWN ON 0V-1, MAP TO
OPERATIONAL NODE CONNECTIVITYDESCRIPTION
NEEDLINES INFORMATION EXCHANGES
VALUE ADDED BUSINESS/MISSION PROCESS
RELATIONSHIPS AMONG ACTIVITIES AND OPERATIONAL
INFORMATION EXCHANGED
INFORMATION EXCHANGES ASSOCIATED WITH EACH
NEEDLINE ARE DETAILED IN OV-3
INNPUT/OUTPUT LABELS MAP TO OPERATIONAL
INFORMATIONEXCHANGES (NOT ALWAYS ONE-TO-ONE)
OPERATIONAL NODE CONNECTIVITY DESCRIPTION (OV-2)
VALUE ADDED STATEMENT OF SYSTEMS NODES, SYSTEMS,
LINKS COMPONENT INTERFACES SUMMARIZED SYSTEM
INFORMATION EXCHANGES

• OPERATIONAL NODES ARE ASSOCIATEAD WITH SYSTEMS
  AND SYSTEMS NODES
• EACH OPERATIONAL NEEDLINE MAPS TO ONE OR MORE
  SYSTEMS LINKS

OPERATIONAL INFORMATION EXCHANGE MATRIX (OV-3)
Overview and Summary Information and Integrated
Dictionary are not shown because they relate to
all other products
VALUE ADDED INDIVIDUAL INFORMATION EXCHANGES
ASSOCIATED WITH EACH NEEDLINE, PERFORMANCE
REQUIREMENTS FOR OPERATIONAL INFORMA- TION
EXCHANGES
VALUE ADDED STATEMENT OF OPERATIONAL NODES,
ACTIVITIES, AND CRITICAL INFORMATION NEEDS
(NEEDLINES SUMMARY INFORMATION EXCHANGED)
15
Some Other Important Product Linkages
OV-3 Operational Information Exchange Matrix
1
SV-1 System Interface Description
Each needline is decomposed into one or more
system interfaces ...
2
3
The individual information exchanges are
assigned to the appropriate system
interface...
And the sending and receiving systems used
to implement the interface are indicated...
Identifier/
Nature
Identifier/
Data
Data
Identifier/
of
Name of
Name of
Name of
Source
Destination
Corresponding
Transaction
Operational
Operational
System
Information
Needline
Exchange
Operational
Operational
Source
Receiving
Supported
Interface(s)
ID of
LISI Level
Node(s)
Node(s)
Supported
ID of
Protocols
System
System
Content
Size
Media
Format
(from OV-2)
Source
Where
Where
(from SV-1)
Achievable
Receiving
(from OV-3)
Used
Function
Function
System
System Is
System Is
System
(from S-4)
(from S-4)
Resident
Resident
e.g., 1-a
Needline
1
e
.g., Interface 1
e.g., 1-b
e.g., 1-c
e.g., 1-d
e
.g., Interface 2
.
e.g., 1-e
.
.
e.g., 1-f
e
.g., Interface n
Needline
2
.
.
.
Needline
n
SV-6 System Data Exchange Matrix
16
Architecture Product Linkages Provide the Audit
Trail That Relates Technology to Mission
Operations
What Information Must Be Captured?
What Performance Measures?
Audit Trail
Where Captured?
Mission Effectiveness
Mission Operations
Operational Node Connectivity Description

• Players, activities, interactions, ...
• Information exchanges
• Execution environment
• Projected risks

Operational Mission Requirements
System Attributes/Metrics

• System Requirements
• Functions/capabilities
• Information exchanges
• Performance
• Threat/security protection

• Functions supported
• Interoperability level
• Performance characteristics
• Info Assurance/IO measures

Systems Capabilities
System Interface Description

• Implementation Criteria
• Standards, Conventions
• Operating Environment

System Implementations
Technical Standards Profile
Implementation Criteria

• Applications and products
• Platform, operating system

17
4. Overview of the Supporting Products of
the DoD Architecture Framework
Supporting Products are those products, other
than the core products, that you may need to
build for your architecture
18
AV-3 Capability Maturity Profile(Not an
official part of the Framework document, but a
technique many architects are using)

• Provides a structure for enterprise-wide planning
  to
• Rationalize investment strategies
• Promote increasing capability levels
• Assure that spent address capability needs
• Move from As-Is to To-Be architectures

19
Components of the Capability Roadmap -Select the
components you need and create new ones as needed
UNCLASSIFIED
Multiple Security Level Interconnection
SECRET
SCI
Infrastructure
Process
Knowledge Management
Governance
Email/Messaging
Directory Services
Information Assurance
Information Storage Management
Collaboration
Network
Resourcing
IT Competency
Domain Applications
Subscription Delivery Services
Computing Platform
Infrastructure Management
IT Service Delivery
Administrative Applications
Search Access
20
Standard Capability Scale

Continuously optimized management, operations,
and external partnerships focused on mission
effectiveness and the agility to extract and
reassemble information from multiple domains
securely and adaptively
Increasing capabilities, availability,
reliability, and global reach
5

i
Optimizing
4
Established enterprise management and reliable
operations focused on improved customer
satisfaction, collaborative core business
processes, enterprise-wide, secure information
and applications sharing, and the timely
exploitation of enabling technologies
Structured
3
Secure multimedia collaboration within interest
groups using partially integrated networks,
limited data sharing, and interoperable
applications and services
Limited
Rudimentary, secure information exchanges
between some organizations on common intranet,
with unpredictable reliability
2
Minimal
Interactions focused on separate objectives using
organization-unique systems and databases
1
Ad-hoc
21
OV-4 Organizational Relationships Chart
22
OV-6 Operational Timing and Sequencing Products
OV-6a Operational Rules Model no graphic
OV-6bOperational State Transition Description
OV-6cOperational Event/Trace Description
23
OV-7 Logical Data Model
24
SV-2 System Communications Description
Internodal Perspective
Intranodal Perspective
25
SV-3 System-System Matrix
26
SV-4 Systems Functionality Description
27
SV-5 Operational Activity to System Function
Traceability Matrix
28
SV-6 System Data Exchange Matrix



Identifier/

Identifier/Name of
Nature of Transaction
Data Destination
Identifier/Name of
Data Source
Name of Operational
Identifier/
Operational
Corresponding
Information Exchange
System Data
Needline
Supported
System Interface(s)




Receiving
Supported

Source System
Receiving
Exchange
LISI Level
Source
Other
(from OV-2)
(from SV-1)
System Component
Size
Component
(from OV-3)
Content
Format
System Name
Achievable
Protocols
System Name
e.g., 1-a (1)
.
e.g., 1-a
.
.
e.g., 1-a (n)
1
e.g., Interface 1
Needline
e.g., 1-b
e.g., 1-c
e.g., Interface 2
e.g., 1-d
.
.
.
e.g., Interface n
2
Needline
.
.
.
Needline
n
Identifier/Name of
Identifier/Name
Identifier/Name of
Operational
Performance Attributes
Physical Environment
Threats
Identifier/
Information Assurance Attributes
of Operational
Corresponding
System Data
Information Exchange

Needline
System Interface(s)
Supported
Exchange
Supported
(from SV-1)





(from OV-3)
Political/
(from OV-2)
Criticality/
C
Sea
Throughput
Aerospace
Land
Encryption
Authentication
Other
Frequency
Timeliness
Physical
Classification
Electronic
Economic
Priority
O
.
e.g., 1-a (1)
.
.
e.g., 1-a
.
.
N
e.g., Interface 1
.
e.g., 1-a (n)
Needline
1
T
I
e.g., 1-b
N
U
e.g., 1-c
e.g., Interface 2
E
e.g., 1-d
.
D
.
.
e.g., Interface n
2
Needline
.
.
.
n
Needline
Indicates minimum recommended entries
29
SV-7 System Performance Parameters Matrix
30
SV-8 System Evolution Description
Migration Example
Evolution Example
31
SV-9 System Technology Forecast- Fragment -
32
SV-10 Systems Timing and Sequencing Products
SV-10b Systems State Transition Description
SV-10c Systems Event/Trace Description
33
SV-11 Physical Schema
34
TV-2 Standards Technology Forecast- Fragment