DoD Architecture Framework Executive Seminar

1
DoD Architecture FrameworkExecutive Seminar
Maj Brian Hartt Air Force Institute of Technology
2
Topics

• Architecture Overview
• DoD Architecture Framework (DoDAF)
• Background
• Architecture ProductsAOC Example
• Relevance to Requirements and Acquisition

3
Architecture Overview
Why are we here?
4
What is an Architecture?

• The structure of components, their
  relationships, and the principles and guidelines
  governing their design and evolution over time.
  - IEEE STD 610.12 as stated in the DoD
  Architecture Framework (DoDAF)

Architecture is useful for designing
unprecedented, complex systems
5
Architecting a House

• When do you NOT need an architect?
• Simple site
• Existing design
• Existing subdivision
• When do you need an architect?
• Difficult site
• Unique design
• Oneness with the setting (i.e. integration)

• But, when do you REALLY need an architect?

6
When do you need an Architect?

• Planned community
• Integrated services
• Interoperable systems
• Efficient operations
• Complementary facilities

7
USAFs Planned Community
8
An Architecture hasMultiple Views

• Three major views (or perspectives) logically
  combine to describe an architecture
• Operational View (OV)
• Systems View (SV)
• Technical Standards View (TV)
• Views provide different perspectives on the same
  architecture

As Defined in the DoD Architectural Framework
(DoDAF)
9
Operational View (OV)

• The Citizens have the Operational View
• A Community operates as
• Place to work, shop, entertain,
• Place to raise a family
• Place to help neighbors
• Place to call home

• For the Citizens, the focus is on the ConOps
  the infrastructure is taken for granted the
  systems are expected to seamlessly interact and
  inter-operate

10
Systems View (SV)

• The Builder has the Systems View
• A Community is a system of systems
• Electrical
• Water Sewer
• Communications
• Roads
• Etc.

• For the Builder, the Communitys infrastructure
  is the main focus the various systems and
  sub-systems must be carefully speced, designed,
  and installed

11
Technical Standards View (TV)

• The Builder and the Inspector have the Technical
  View
• Homes must comply with building codes
  and standards
• National Electrical Code
• ANSI building standards
• IEEE electronics standards

• Codes, specs, and standards provide the
  foundation upon which every process and system in
  the Community is based

12
Summary of Views and Constraints

• Operational View (Citizen)
• Intended Uses and Processes
• Conceptual

• System View (Builder)
• Physical Structure
• Design Principles, Reference Models and Rules
• Logical

• Technical Standards View (Builder and Inspector)
• Building Codes / Standards
• Standardization (Components)
• Physical

13
All View (AV)

• The Architect has the All View
• The Big Picture
• Scope
• Purpose
• Intended users
• Environment
• Etc.

• The Architect must understand all the
  overarching aspects that relate to all three of
  the views

14
What is the DoDArchitecture Framework?
Framework is partitioned into three
volumes Volume I Definitions and
Guidelines Volume II Product Descriptions Volume
III Deskbook Purpose of the DoD Architecture
Framework, Version 1.0, is to Define a common
approach for developing, presenting, and
integrating of DoD architecture descriptions
15
Framework History
Evolving to a DOD instruction
2004
1997
1994
1996
16
DoD Architecture Framework -Scope

• Framework defines architecture views
• Operational
• Systems
• Technical Standards
• All View Products
• Each view is composed of sets of architecture
  information that are depicted via graphics,
  tables, or textual products

17
Architecture is Documented using Models
Source A
Function 1
Sink X
Function 2
EntityName A1 A2 A3
EntityName A1 A2 A3
Relationship
I1
A1
I2
A2
I3
A Model is worth 1000 pictures
18
DoD Framework Products(Format of Products)
OPERATIONAL (OV)
SYSTEMS (SV)
TECHNICAL (TV)
1 High-Level Operational Concept Graphic
1 Systems Interface Description
1 Technical Standards Profile
2 Systems Communications Desc.
2 Operational Node Connectivity Description
3 Systems-Systems Matrix
3 Operational Information Exchange Matrix
2 Technical Standards Forecast
4 Systems Functionality Description
4 Organizational Relationships Chart
5 Operational Activity to System Function
Traceability Matrix
5 Operational Activity Model
ALL (AV)
6 Sys Data Exchange Matrix
6a Operational Rules Model
Overview Summary
7 Sys Performance Parameters Matrix
6b Operational State Transition Description
8 Systems Evolution Description
Integrated Dictionary
6c Operational Event/Trace Description
9 Systems Technology Forecast
10a Systems Rules Model
7 Logical Data Model
10b Systems State Transition Desc.
10c Systems Event/Trace Desc.
11 Physical Data Model
DynamicModels
Static Models Graphics
Spreadsheets
Text
CADM Core Architecture Data Model
19
DoD Framework Products(Format of Products)
OPERATIONAL (OV)
SYSTEMS (SV)
TECHNICAL (TV)
1 High-Level Operational Concept Graphic
1 Systems Interface Description
1 Technical Standards Profile
2 Systems Communications Desc.
2 Operational Node Connectivity Description
3 Operational Information Exchange Matrix
5 Operational Activity Model
ALL (AV)
6 Sys Data Exchange Matrix
Overview Summary
Integrated Dictionary
DynamicModels
Static Models Graphics
Spreadsheets
Text
CADM Core Architecture Data Model
20
Architecture Example Aerospace Operations
Center (AOC)

• Why AOC?
• UnclassifiedFOUO
• Complex environment
• Background
• The AOC is the JFACCs weapon system for command
  control of air and space forces
• Closely coordinated acquisition between ESC and
  AFC2ISRC

21
DoD Framework Products(Format of Products)
OPERATIONAL (OV)
SYSTEMS (SV)
TECHNICAL (TV)
1 High-Level Operational Concept Graphic
1 Systems Interface Description
1 Technical Standards Profile
2 Systems Communications Desc.
2 Operational Node Connectivity Description
3 Operational Information Exchange Matrix
5 Operational Activity Model
ALL (AV)
6 Sys Data Exchange Matrix
Overview Summary
Integrated Dictionary
DynamicModels
Static Models Graphics
Spreadsheets
Text
CADM Core Architecture Data Model
22
AV-1 Overview and Summary
Information
Text

• Narrative description
• Overarching document guiding the architecture
  effort
• Defines scope, purpose, uses, analysis method,
  assumptions, products, context, tools and
  resources

Read First
23
AV-1 Overview and Summary
Information
Text

• Identification
• Architecture Title Aerospace Operations Center
  (AOC) Block 10 (Simplified Example)
• Architects ESC, AFC2ISR Center, and AFIT
• Purpose
• Problem Description AOCs have not previously
  been baselined units created their own AOCs
  according to various local methods and designs
  AOCs were not a standardized, integrated weapon
  system.
• Purpose AOC Block 10 sets a baseline as is
  architecture for a generic AOC this supports
  ongoing AOC efforts, including contract RFP,
  weapon system integration and test, and future
  AOC development.
• Scope This architecture depicts the evolution of
  a generic AOC and details the AOC high-level
  activities and major information exchanges.

24
AV-2 Integrated Dictionary
Text

• Glossary with definitions of terms used in the
  architecture
• Each item in the architecture should have a
  corresponding entry
• Dictionary should cross-reference all items

25
DoD Framework Products(Format of Products)
OPERATIONAL (OV)
SYSTEMS (SV)
TECHNICAL (TV)
1 High-Level Operational Concept Graphic
1 Systems Interface Description
1 Technical Standards Profile
2 Systems Communications Desc.
2 Operational Node Connectivity Description
3 Operational Information Exchange Matrix
5 Operational Activity Model
ALL (AV)
6 Sys Data Exchange Matrix
Overview Summary
Integrated Dictionary
DynamicModels
Static Models Graphics
Spreadsheets
Text
CADM Core Architecture Data Model
26
Operational ViewsDevelopment Sequence
OPERATIONAL (OV)
First
1 High-Level Operational Concept Graphic
2 Operational Node Connectivity Description
3 Operational Information Exchange Matrix
Second
5 Operational Activity Model
Third
Fourth
27
Graphics Text
OV-1 High-level Operational Concept Description

• Depicts AOC operational concept (key inputs,
  outputs, controls, and mechanisms)
• Provides text description of the ConOps
• Marketing brochure or Archi-toon

28
OV-5 Operational Activity Model
Static Models Graphics
Conduct Air Operations
Conduct Dynamic-State Operations
Conduct Steady-State Operations
Step 1 Functional Decomposition (structured
similar to WBS)
29
Static Models Graphics
OV-5 Operational Activity Model
Doctrine, ROE
ConductAir Operations
Strategic Plan
ATO
Intelligence
Operations Directions
Conduct Steady-State Operations
Steady-State Plan
Dynamic Targeting Directions
Step 2 Model the activity flow (aka IDEF0 model)
Conduct Dynamic-State Operations
Execute ATO
30
OV-2 Operational Node Connectivity Description
Static Models Graphics
Airborne Command Control (AWACS)
Tactical Reconnaissance (Predator)
Strategic Reconnaissance (Big Bird)
Operations Directions
Air Intel
Strat Intel
Tac Intel
Shooter
Dynamic Targeting Directions
Note As Is Architecture
Air Operations Center
Strategic Plan
ATO Planning Cell
ATO Execution Cell
ATO
OV-2 depicts nodes and high-level information
flow (needlines)
31
OV-3 Operational Information Exchange Matrix
Spreadsheet
32
DoD Framework Products(Format of Products)
OPERATIONAL (OV)
SYSTEMS (SV)
TECHNICAL (TV)
1 High-Level Operational Concept Graphic
1 Systems Interface Description
1 Technical Standards Profile
2 Systems Communications Desc.
2 Operational Node Connectivity Description
3 Operational Information Exchange Matrix
5 Operational Activity Model
ALL (AV)
6 Sys Data Exchange Matrix
Overview Summary
Integrated Dictionary
DynamicModels
Static Models Graphics
Spreadsheets
Text
CADM Core Architecture Data Model
33
StaticModel
SV-1 System Interface Description
34
StaticModel
SV-1 System Interface Description
Note For demonstration purposes, this chart
depicts only the AOC and AWACS systems. (Other
system nodes not shown)
35
StaticModel
SV-2 System Communication Description
Note For demonstration purposes, this chart
depicts only the AOC and AWACS systems. (Other
system nodes not shown)
36
StaticModel
SV-6 System Data Exchange Matrix
37
DoD Framework Products(Format of Products)
OPERATIONAL (OV)
SYSTEMS (SV)
TECHNICAL (TV)
1 High-Level Operational Concept Graphic
1 Systems Interface Description
1 Technical Standards Profile
2 Systems Communications Desc.
2 Operational Node Connectivity Description
3 Operational Information Exchange Matrix
5 Operational Activity Model
ALL (AV)
6 Sys Data Exchange Matrix
Overview Summary
Integrated Dictionary
DynamicModels
Static Models Graphics
Spreadsheets
Text
CADM Core Architecture Data Model
38
TV-1 Technical Standards Profile
Spreadsheets
C4ISR Domain
39
DoD Framework Products(Format of Products)
OPERATIONAL (OV)
SYSTEMS (SV)
TECHNICAL (TV)
1 High-Level Operational Concept Graphic
1 Systems Interface Description
1 Technical Standards Profile
2 Systems Communications Desc.
2 Operational Node Connectivity Description
3 Systems-Systems Matrix
3 Operational Information Exchange Matrix
2 Technical Standards Forecast
4 Systems Functionality Description
4 Organizational Relationships Chart
5 Operational Activity to System Function
Traceability Matrix
5 Operational Activity Model
ALL (AV)
6 Sys Data Exchange Matrix
6a Operational Rules Model
Overview Summary
7 Sys Performance Parameters Matrix
6b Operational State Transition Description
8 Systems Evolution Description
Integrated Dictionary
6c Operational Event/Trace Description
9 Systems Technology Forecast
10a Systems Rules Model
7 Logical Data Model
10b Systems State Transition Desc.
10c Systems Event/Trace Desc.
11 Physical Data Model
DynamicModels
Static Models Graphics
Spreadsheets
Text
CADM Core Architecture Data Model
40
Architecture Product Relationships
Integrated Architecture (as described by Joint
Staff/J8)
41
SEQUENCE OF PRODUCTS (from AMC)
AV-1
OV-1
AV-2
42
SEQUENCE OF PRODUCTS (from AMC)
AV-1
OV-1
OV-4
OV-5
OV-2
OV-3
AV-2
43
SEQUENCE OF PRODUCTS (from AMC)
AV-1
OV-1
OV-4
OV-5
OV-2
OV-3
SV-1
SV-2
TV-1
SV-5
SV-4
SV-3
AV-2
44
SEQUENCE OF PRODUCTS (from AMC)
AV-1
OV-1
OV-4
OV-6c
OV-5
OV-2
OV-6b
OV-6a
OV-3
OV-7
SV-1
SV-11
SV-6
SV-2
TV-1
TV-2
SV-5
SV-4
SV-3
AV-2
45
SEQUENCE OF PRODUCTS (from AMC)
AV-1
OV-1
OV-4
OV-6c
OV-5
OV-2
OV-6b
OV-6a
OV-3
OV-7
SV-1
SV-11
SV-6
SV-2
TV-1
TV-2
SV-10c
SV-10b
SV-5
SV-4
SV-3
SV-8
SV-9
SV-7
SV-10a
AV-2
46
DoD Framework Products
AV-1
OV-1
OV-4
OV-5
OV-2
Legend
Documents
SV-1
Models
TV-1
SV-2
SV-4
AV-2
47
Requirements and Acquisition Process
48
CJCSI 3170.01D Architecture Elements Summary
49
CJCSI 3170.01D Architecture Elements Summary
50
Architecture Capabilities
C
Capability
A1
A2
A3
Nodes
Node
OVs
Activities
A2.2
A2.1
A3.1
A1.1
A1.2
A3.2
Functions
S1.1
S1.2
S2.1
S2.2
S3.1
S3.2
SVs
Systems
Node
S1
S2



/PEs
for Acquisition, Personnel, TTP Changes,...
Financial Data
51
https//afkm.wpafb.af.milSearch for
Architecture Training CoP
Workshop (short course)
DoDAF Download Site
52
Executive Summary
Summary  In a net-centric warfighting
environment, there is a great need for
integration and interoperability in order to
achieve warfighting capabilities.  Integrated
architectures are central to the DoD approach,
and the DoD Architecture Framework is the
playbook for integrated architectures.   This
seminar will introduce the basic concepts of
architecture and explain the most common
Operational Views (OVs), System Views (SVs), and
Technical Views (TVs).  These views are required
by the three capabilities documents (ICDs, CDDs,
and CPDs) and have great relevance to the
requirements and acquisitions communities.