Unclassified/Pre-decisional/FOUO DRAFT
DoD Architecture
Framework Application
DoD CIO Architecture and Interoperability Directorate
Briefing to JTSO Director
May 2013
DISTRIBUTION STATEMENT D: Distribution authorized to DoD and DoD contractors only. Critical Technology (4/10/2007). Other U.S. requests shall be referred to the DoD CIO,
Architecture and Interoperability Directorate
WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C. Sec. 2751 Et. Seq.) or Executive Order 12470. Violations of
these export laws are subject to severe criminal penalties.
DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.
Unclassified/Pre-decisional/FOUO DRAFT
Unclassified/Pre-decisional/FOUO DRAFT
Agenda
•
Why DoDAF?
•
•
•
DoDAF Basics
Re-cap brief on IDT architecture development
Reification, allocation, and traceability across the
development levels
Summary from a JIE perspective
•
25 Feb 2013
Unclassified/Pre-decisional/FOUO DRAFT
2
Unclassified/Pre-decisional/FOUO DRAFT
Why DoDAF?
• Tbs – standarization across Components,
enterprise analytics, reuse of data across
core processes, line-of-sight from rqmts to
implementations to resourcing
Unclassified/Pre-decisional/FOUO DRAFT
Unclassified/Pre-decisional/FOUO DRAFT
DoDAF Basics
• Tbs from plenaries, NATO briefs,
capability tutorial, etc.
Unclassified/Pre-decisional/FOUO DRAFT
Unclassified/Pre-decisional/FOUO DRAFT
Re-cap Feb 2013 DoD CIO A&I brief on
IDT architecture development
Unclassified/Pre-decisional/FOUO DRAFT
Unclassified/Pre-decisional/FOUO DRAFT
SoS Functional Allocation Theory
SoS Spec
Function 1
Function 2
Function 3
Black lines = ideal
+ Orange = reality
System 1
FoS 1A
FoS 1B
FoS 1C
System 2
FoS 2A
FoS 2B
FoS 2C
System 3
Black lines = ideal
FoS 3A + Orange = reality
FoS 3B
FoS 3C
Orange is sometimes inevitable but should be avoided otherwise
25 Feb 2013
Unclassified/Pre-decisional/FOUO DRAFT
6
Unclassified/Pre-decisional/FOUO DRAFT
As Applied to JIE “Spec Tree”
Requirements
documents*
* See notes for list
JIE ICD
IDEAL
JIE EA
Corrections and
improvements
IDT Tech Archs
Component
System/Service Specs
for RFPs, working
capital fund taskers,
etc.
25 Feb 2013
Joint &
Service
Doctrine, TTP,
training, etc.
Test and
compliance
plans and
procedures
Unclassified/Pre-decisional/FOUO DRAFT
7
Unclassified/Pre-decisional/FOUO DRAFT
Focus at each tier
Requirements
documents
System
SoS
SoS Elements
FoS of SoS
Elements
25 Feb 2013
Component
System/Service Specs
for RFPs, working
capital fund taskers,
etc.
End-state
objectives are
paramount
JIE ICD
JIE EA+RA’s
In SoSE,
interfaces and
common
components are
paramount
IDT Tech Archs
Joint &
Service
Doctrine, TTP,
training, etc.
Test and
compliance
plans and
procedures
Unclassified/Pre-decisional/FOUO DRAFT
Adherence to the
the SoS element
specifications is
paramount
8
Unclassified/Pre-decisional/FOUO DRAFT
Aligned JIE Spec Tree
1. The ICD X EA layer is
collapsed and mappings
no longer exist
2. Many-to-manys
(orange lines) from EA Op
Acts to RAs to IDT no
longer exist
3. EA X RA Op Acts
mapping no longer
exists
4. EA/RA X IDT Op Acts
mapping no longer
exists
25 Feb 2013
JIE EA
(JIE ICD Arch is a subset)
Op Act 1
Op Act 2
Op Act 3
JIE RA x
JIE RA y
JIE RA z
IDT TA 1
FoS 1A
FoS 1B
FoS 1C
IDT TA 2
FoS 2A
FoS 2B
FoS 2C
Unclassified/Pre-decisional/FOUO DRAFT
IDT TA 3
FoS 3A
FoS 3B
FoS 3C
Only
orange
lines left
are those
due to
legacy
9
Unclassified/Pre-decisional/FOUO DRAFT
Recommended Streamlining
ICD
1. JIE ICD to JIE EA
JIE RA
CV-2/6
CV-2/6
Hierarchy
Desired Effects
Desired Effects Metrics
Tasks
Task Metrics
Conditions
Condition Metrics
OV-4
OV-4
OV-2
OV-2
OV-5a
OV-5a
CV-1
CV-3
CV-4
Should be equal
Should be equal, the orgs involved in
the operation of the JIE
Should be equal, interaction between
the orgs identified in OV-4
Should be equal, activities to operate
the JIE
All CV-1 data is contained in CV-2/6
Should match IMS
Should match IMS
2. JIE EA Op Acts one-to-one with RAs which are
one-to-one IDTs
3. RA Op Acts = JIE EA Op Acts for their branch
4. IDT System Functions respond to RA Op Acts
25 Feb 2013
Unclassified/Pre-decisional/FOUO DRAFT
10
Unclassified/Pre-decisional/FOUO DRAFT
Notional Interface Matrix
SSA
NNT
CDC
SSA
CDC status relevant to
Security protocols across
SSA. SSA msgs to alter
netw orks
CDC ops
NNT
Netw ork status and CDC
config and resource
requests. CDC netw ork
status.
EOC
OOB
UC
IdAM
SSA alterts and status to SSA status and alerts
SSA alerts and state
SSA controls on UC ops.
operators. SSA
necessitating OOB aciton.
change orders. IdAM
UC status.
configuration cmds.
OOB actions.
status
CDC
EOC
OOB
UC
IdAM
In other words, it can be done at the SoS (EA/RA) level
25 Feb 2013
Unclassified/Pre-decisional/FOUO DRAFT
11
Unclassified/Pre-decisional/FOUO DRAFT
CDC
EOC
OOB
x
x
x
x
x
Monitor the JIE
x
x
x
x
x
2.1.1
Monitor the JIE Security
x
2.1.2
Monitor the JIE Performance
x
x
x
2.1.3
Monitor Operational Events
2.1.4
Monitor Equipment Health & Status
x
x
2.1.5
Monitor Communications Links and Networks
x
1
2
2.1
2.2
2.2.1
2.2.14 PARK
x
x
Manage JIE Operations
Manage NetOps
x
Provide Services Infrastructure
x
x
2.2.2
Detect/Diagnose Issues
x
2.2.3
Perform System Administration
x
2.2.4
Perform Configuration Management
x
2.2.5
Manage Workforce
2.2.6
Manage Enterprise Services
x
2.2.7
Perform Centralized Data Management
x
x
x
Manage JIE Performance and Effectiveness
x
2.3.1
Manage IE Performance
x
2.3.2
Manage JIE Effectiveness
x
2.4
Operate Service Desk
x
2.4.1
Collect and Track Incidents/Events
x
2.4.2
Evaluate Incidents/Events
x
2.4.3
Assign Incidents/Events
x
2.4.4
Resolve Incidents/Events
x
2.4.5
Report Resolution
x
2.3
IdAM
NNT
Provide JIE Infrastructure & Services
Manage and Operate the JIE
JIE EA_Name
JIE EA_ID
UC
SSA
Functional Allocation EA to IDTs
In other words, it can be done at the SoS (EA/RA) level but
may need to go below tier 3 in some cases
25 Feb 2013
Unclassified/Pre-decisional/FOUO DRAFT
12
Unclassified/Pre-decisional/FOUO DRAFT
IDT Arch Scoping: DoDAF “Fit for
Purpose”
SSA
NNT
CV
OV
* In DoDAF 2,
operators are
part of the
system or
service
SV/SvcV-1/2
CDC
EOC
Components of SSA and
their interfaces
SV-5a
SV/SvcV-5b
SV/SvcV-6 Data interfaces
Network laydowns,
interfaces, associated
standards
Facility laydowns and
layouts, interfaces
Componentry and
interfaces
Functions perfomed by
operators and network
interconnection systems,
leverage JCSFL Internal
functional flows of NNT.
Functions performed by
operators at the CDC
covered by EOC.
Functions performed by
OOB functions and
operators and systems and
functional flow, leverage
services in managing the
JCSFL.
EOC, leverage JCSFL
Data interfaces
Metrics associated with
NNT
Metrics associated with
CDC
Rules for operators and
systems/services
Rules for operators and
systems/services
Same as EOC
State transition logic for
SSA
Threads for different use
cases of SSA. Could be
SV/SvcV-10c
integrated with SV/SvcV10b.
StdV-1 Detail from RA
DIV-1, 2, & 3
Network, interfaces,
components
Components, interfaces
Components, interfaces
Functional architecture of
UC SFs and functional flow,
IdAFM services and
leverage JCSFL
systems, leverage JCSFL
Traceability of SFs to RA activities
Data interfaces
StdV-2
IdAM
Traceability of Systems and Services to RA activities
Metrics associated with
SV/SvcV-7
SSA
SV/SvcV-10b
UC
None needed. Done in RA's. (In DoDAF 2, SV/SvcV includes operators.)
Functional architecture
SV/SvcV-4 (SFs and functional flows)
of SSA. Use JCSFL.
SV/SvcV-10a
OOB
None needed, done in RA's. Just need to show traceabilities.
e.g., for failovers, COOP.
Coord / reuse from EOC
Threads for different use
cases of NNT
Data interfaces
Metrics associated with
EOC operators and
systems/services
To become p/o doctrine,
TTP, etc.
State transition logic for
EOC
Threads for different use
Use cases could be
cases of EOC. Could be
integrated with 10b. Coord
integrated with SV/SvcV/ reuse from EOC.
10b.
Data interfaces
Metrics associated with
OOB (e.g., survivability)
OOB rules
For different threat
scenarios, state transition
and logic. Coord / reuse
from EOC.
. Coord / reuse from
EOC.Use cases / thread
possibly integrated with
10b. Coord / reuse from
EOC.
Network standards related
to SV/SvcV-1/2, 4, 10a, and Detail from RA
OOB standards
10c.
Not needed for Inc 1 or future increments unless change anticipated.
Data interfaces
Data interfaces
Metrics associated with
Metrics associated with UC,
IdAM, e.g., %error,
e.g., QoS
timeliness
Detail from RA
Detail from RA
IdAM logic
Use cases for UC services
IdAM use case sequences;
could be integrated with
10b
Detail from RA
Detail from RA
As needed for SoS
As needed for SoS
As needed for SoS
As needed for SoS
As needed for SoS
As needed for SoS
As needed for SoS
interface specification and interface specification and interface specification and interface specification and interface specification and interface specification and interface specification and
for functional architecture. for functional architecture. for functional architecture. for functional architecture. for functional architecture. for functional architecture. for functional architecture.
If standards suffice, point If standards suffice, point If standards suffice, point If standards suffice, point If standards suffice, point If standards suffice, point If standards suffice, point
to specific StdVs.
to specific StdVs.
to specific StdVs.
to specific StdVs.
to specific StdVs.
to specific StdVs.
to specific StdVs.
Fit-for-purpose (FFP) architecture tailored to the focus of the IDT
25 Feb 2013
Unclassified/Pre-decisional/FOUO DRAFT
13
Unclassified/Pre-decisional/FOUO DRAFT
Next Steps
25 Feb 2013
IDT Arch
Scoping
Shared
Architecture
Data
RA/IDT
Boundaries
Next Steps:
Align ICD and EA
Align EA and RAs
Functional allocation EA to IDTs
Reload allocated EA into IDT tool
/ DB
Functional IDT interfaces /
boundaries EA level
IDT Interfaces / boundaries
refinement
CV metrics EA level
CV X SV/SvcV metrics IDT level
Master vignettes (OV-6bc) EA
level
Master cross-IDT vignettes (SVSvcV-10bc)
Master AV-2 EA level
Master AV-2 IDT level
Streamlined
Spec Tree
Risk Mitigator
x
x
Who
EA team / J6
EA team
EA team
x
x
IDT
High
x
EA team
High
x
IDTs
Low
EA team
IDT team
High
Med
x
EA team
Med
x
IDTs
Med
x
x
EA team
IDTs
Med
Med
x
x
x
x
Unclassified/Pre-decisional/FOUO DRAFT
Priority
Med
Low
High
14
Unclassified/Pre-decisional/FOUO DRAFT
Reification, allocation, and traceability
across the development levels
Unclassified/Pre-decisional/FOUO DRAFT
Unclassified/Pre-decisional/FOUO DRAFT
Reification
• By extension
(specialization) or
decomposition
Artifact11
Artifact12
Artifact13
Artifact 1
Artifact 2
Artifact 3
Artifact 4
x
x
x
x
x
x
Artifact D
Artifact C
Artifact B
Artifact1
Artifact A
DM2
supersubtype or
whole-part
• By mapping or
allocation
x
DM2
overlap
Reification in DoDAF is formally superSubtype, wholePart,
or ovelap
25 Feb 2013
16
Unclassified/Pre-decisional/FOUO DRAFT
Unclassified/Pre-decisional/FOUO DRAFT
Reification of Activities
“Work, not specific to a single organization, weapon system or individual that
transforms inputs (Resources) into outputs (Resources) or changes their state.”
•
•
•
•
In architectures, Activities are
structures (see diagram to
right)
Hence, to reify them means
to reify the structure
For example, in an OV-5a,
“Activity-1.1 reifies Activity-1”,
means it reifies Activity-1’s
structure:
–
–
–
–
–
–
Activity-1
consumedResources-A1.i
producedResources-A1.j
Rules-A1.k
Performers-A1.l
Measures-A1.m
–
–
–
superSubtype,
wholePart, or
overlap
Where “reify” means:
Unclassified/Pre-decisional/FOUO DRAFT
Unclassified/Pre-decisional/FOUO DRAFT
Reification of Capabilities
“The ability to achieve a Desired Effect under specified [performance] standards and
conditions through combinations of ways and means [rules, activities, and resources] to
perform a set of activities.”
•
•
•
•
In architectures, Capabilities
are structures (see diagram to
right)
Hence, to reify them means
to reify the structure
For example, in an CV-2,
“Capability-1.1 reifies
Capability-1” means it reifies
the Capability-1 structure:
–
–
–
–
–
–
Capability-1
desiredEffects-C1.i
Tasks-C1.j
Rules-C1.k
Conditions-C1.l
Measures-C1.m
–
–
–
superSubtype,
wholePart, or
overlap
Where “reify” means:
Unclassified/Pre-decisional/FOUO DRAFT
Unclassified/Pre-decisional/FOUO DRAFT
Reification of Resource Flow
“The behavioral and structural representation of the interactions between activities (which
are performed by performers) that is both temporal and results in the flow or exchange of
things such as information, data, materiel, and performers...”
•
•
For example, in an SV-1,
each element of a reified
resource flow must be a
reification of elements from
ordinate resource flows
More complex reiying across
allocation levels (e.g.,
OVSV) because of typical
many-many allocations
–
–
Some flows get rolled-up
New ones get created
Unclassified/Pre-decisional/FOUO DRAFT
Unclassified/Pre-decisional/FOUO DRAFT
The Reification can be in the
form of different types of artifacts
Capability desiredEffect measure 1
Capability desiredEffect measure 11
Capability desiredEffect measure 111
Capability desiredEffect measure 2
Capability desiredEffect measure 21
Capability desiredEffect measure 211
Performer
measure a
e.g., CV-x Data
Performer
measure a
Performer
measure a
e.g., SV/SvcV-7 Data
x
x
X
x
x
X
x
x
X
x
x
X
The mapping is at
the leaf level but
some mapping to
the “parents” is
implied
This is the traditional MOE to MOP relationship
Unclassified/Pre-decisional/FOUO DRAFT
The Reification (and hence traceability)
span from requirements to implementation
X
CV-x
X
X
Activity-b11
Activity-b1
Activity-b
Activity-a11
Notional example
SvcV-4
Organization-i
Organization-i1
Organization-i11
Organization-j
Organization-j1
Organization-j11
System-x1
System-x1
System-x11
System-y
System-y1
System-y11
SV-1
SvcV-3
Service-b1
Service-b11
OV-2/4/3/5
Service-b
Service-a
SvcV-5
Service-a11
ServiceFunction-x1
ServiceFunction-x1
ServiceFunction-x11
ServiceFunction-y
ServiceFunction-y1
ServiceFunction-y11
Service-a1
Activity-a1
SvcV-7
Activity-a
Capability-1
Capability-11
Capability-111
Capability-2
Capability-21
Capability-211
Notionally, for JIE, the upper pieces tend to flow
from the ICD & EA through the RA’s to the SA’s
and eventual implementations
ICD/ EA
X
X
RAs
Notional example
SAs
Activity-b11
Activity-b1
Activity-b
Activity-a11
Activity-a1
X
Activity-a
Capability-1
Capability-11
Capability-111
Capability-2
Capability-21
Capability-211
Component
implementations
Organization-i
Organization-i1
Organization-i11
Organization-j
Organization-j1
Organization-j11
Service-b11
Service-b1
Service-b
Service-a11
Service-a1
Service-a
ServiceFunction-x1
ServiceFunction-x1
ServiceFunction-x11
ServiceFunction-y
ServiceFunction-y1
ServiceFunction-y11
System-x1
System-x1
System-x11
System-y
System-y1
System-y11
This is similar to the “yellow brick road” diagram but applied to the
JIE at the enterprise level rather than each reification level
Unclassified/Pre-decisional/FOUO DRAFT
Capabilities Reification Traceability
Criteria
• superSubtype reification: Capability11 reifies
Capabilitiy1 iff:
Task i11  Capability11 ,
WPT
Task 1  Capability1 
j
desiredEffect i11  Capability11 ,
WPT
Task 11  Task 1j 
i
WPT
desiredEffect 1  Capability1 
j
WPT
WPT
• wholePart reificaiton:
desiredEffect 11  desiredEffect 1 
i
j
WPT
measureOfDesiredEffect 11  measureOfDesiredEffect 1
i
j
– Proper wholePart:
– Improper wholePart:
Condition ix11  Task i11 ,
WPT
Condition 1
jy
 Task 1j 
WPT
Condition 11  Condition 1jy
ix
WPT
• typeInstance:
• overlap:
Unclassified/Pre-decisional/FOUO DRAFT
Unclassified/Pre-decisional/FOUO DRAFT
Questions?
25 Feb 2013
Unclassified/Pre-decisional/FOUO DRAFT
24
Unclassified/Pre-decisional/FOUO DRAFT
Current Situation
CV-1
CV-2
CV-6
CV-7
OV-2
OV-3
OV-4
OV-5a
OV-5b
OV-6a
OV-6b
OV-6c
SV-1
SV-2
SV-3
SV-4
SV-6
SV-7
SV-10a
SV-10b
SV-10c
SvcV-1
SvcV-2
SvcV-3a
SvcV-3b
SvcV-4
SvcV-6
SvcV-7
SvcV-10a
SvcV-10b
SvcV-10c
StdV-1
StdV-2
DIV-1
DIV-2
DIV-3
IDT Architectural Artifact POA&M*
SSA
NNT
CDC
EOC
OOB
UC
IdAM
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
143 DoDAF views total across IDTs
* Source: EXCOM Brief
25 Feb 2013
Above is simplification of 
Unclassified/Pre-decisional/FOUO DRAFT
25
Unclassified/Pre-decisional/FOUO DRAFT
Risks
• Large number of views (143) to be developed in a “Stove
Pipe”
• Possible redundant artifacts in views
– Views may become inconsistent
• Configuration management of artifacts becomes intractable
• No integration between IDTs
25 Feb 2013
Unclassified/Pre-decisional/FOUO DRAFT
26
Unclassified/Pre-decisional/FOUO DRAFT
JIE Spec Tree As-is
JIE ICD Inc. 1 Arch
ICD Op Act 1
ICD Op Act 2
ICD Op Act 3
JIEEA
Op Act xu
Op Act 1
Op Act 2
Op Act 3
JIE RA x
JIE RA y
JIE RA z
Op Act xv
IDT TA 1
FoS 1A
FoS 1B
FoS 1C
Op Act xw
Op Act yu
Op Act yv
Op Act yw
IDT TA 2
FoS 2A
FoS 2B
FoS 2C
Op Act zu
Op Act zv
Op Act zw
IDT TA 3
FoS 3A
FoS 3B
FoS 3C
A related problem is “building from” views (reports) rather than the whole
model (data)
25 Feb 2013
Unclassified/Pre-decisional/FOUO DRAFT
27
Unclassified/Pre-decisional/FOUO DRAFT
Risk Mitigation # 2: RA/IDT Boundaries
RAD
CV-1/6
x
CV-2
IEA 2.0
UC RA
9 capabilities defined
narratively
partial based on
narratives
Narrative, not structured
IdAM
JIE EA
JIE ICD
117 capabilities defined
narratively
5 capabilities defined
narratively with JCA UJTL
tasks cross ref'd
Narrative, not structured 5 capabilities cross-ref'd
to 3 JCAs
Narrative, not structured
51 capabilities aligned to
the 56 services
OV-2
OV-3
OV-4
x
OV-5
x
OV-6a
x
OV-6b
OV-6c
x
SV/SvcV-1/2
x
SvcV-1 for 56 services
SV/SvcV-4
x
SvcV-4 hierarchy only
SV/SvcV-10c
StdV-1
CDC RA
Narrative, not structured
CV-3
CV-4
CV-5
CV-7
SV-5a
SV/SvcV-5b
SV/SvcV-6
SV/SvcV-7
SV/SvcV-10a
SV/SvcV-10b
JCSFL
partial, 51 capabilities
defined narratively
3 types of org interaction in progress
x
for the operation of the
UC
5a only, 307 activities
defined for the operation
of the IE
103 rules defined related
to the operation of the IE
5a only
many
x
~55 rules defined
x
High-level with ~flows
and activities
4 service areas identified
9 services defined
x
in progress
84 orgs identified
5a only; ~600 activites
defined
5a only; ~600 activites
defined
SV-4 hierarchy only; ~
TBD Net-Centric SFs
x
x
x
x
~100 standards identified
x
x
~25 standards identified
StdV-2
DIV-1
DIV-2
DIV-3
At the SoS (EA/RA) level, the interfaces have not been defined sufficiently
25 Feb 2013
Unclassified/Pre-decisional/FOUO DRAFT
28
Unclassified/Pre-decisional/FOUO DRAFT
3.1.1
Conduct Computer Network Defense
x
3.1.2
Provide Information Assurance
x
3.1.3
Manage Threats, Risks, and Vulnerabilities
x
3.1.4
Protect Network Boundaries
x
3.1.5
Manage Mission Assurance
3.2
x
x
x
x
x
x
x
x
x
x
x
x
x
x
3.2.1
Manage Identity Attributes
3.2.2
Provide Authentication Services
3.2.3
Establish Access Policy Mechanisms
x
3.2.4
Provide Authorization Services
x
3.2.5
Provide Federation
x
x
x
x
Enable Cross Domain Security
x
3.3.1
Identify Domains
x
3.3.2
Determine Domain Security
x
3.3.3
Implement Cross Domain Solution
x
3.3.4
Evaluate CDS Effectiveness
x
Protect Data, Metadata and Devices
x
x
3.4.1
Protect All Devices Connected to the Network
x
x
3.4.2
Protect Data and Metadata
x
3.3
3.4
x
Use the JIE
x
Locate and Use Information, Applications and Services
x
4.1.1
Execute Enterprise Search & Discovery
x
4.1.2
Perform Data Tagging & Exchange
x
Share Information, Applications & Services
x
4.2.1
Publish Information, Applications & Services
x
4.2.2
Collaborate
4
4.1
4.2
x
x
4.3.1
Identify JIE Training Requirements
x
4.3.2
Develop JIE Training Plans
x
4.3.3
Evaluate JIE Training Performance
x
4.3.4
Execute JIE Training
x
5
x
x
Train for JIE Proficiency
4.3
25 Feb 2013
Perform IdAM
IdAM
x
UC
x
x
OOB
x
3
3.1
EOC
NNT
Protect and Secure the JIE
Defend the Enterprise Network
JIE EA_Name
JIE EA_ID
CDC
SSA
Cont’d
Oversee & Govern the JIE
Unclassified/Pre-decisional/FOUO DRAFT
29
Unclassified/Pre-decisional/FOUO DRAFT
FFP
Workflow
Examples
25 Feb 2013
Unclassified/Pre-decisional/FOUO DRAFT
30
Unclassified/Pre-decisional/FOUO DRAFT
Risk Mitigation #4: Shared Architecture Data
• Shared use cases / scenarios / vignettes*
– EOC might lead many
• Master AV-2 from ICD to IDTs and across all
rocks, RAs, and IDTs
– Probably federated CM
* SV/SvcV-10bc flow
down’s from EA OV-6bc’s
25 Feb 2013
Unclassified/Pre-decisional/FOUO DRAFT
31
Unclassified/Pre-decisional/FOUO DRAFT
Proposed
Plan
Current
Plan
CV-1
CV-2
CV-6
CV-7
OV-2
OV-3
OV-4
OV-5a
OV-5b
OV-6a
OV-6b
OV-6c
SV-1
SV-2
SV-3
SV-4
SV-6
SV-7
SV-10a
SV-10b
SV-10c
SvcV-1
SvcV-2
SvcV-3a
SvcV-3b
SvcV-4
SvcV-6
SvcV-7
SvcV-10a
SvcV-10b
SvcV-10c
StdV-1
StdV-2
DIV-1
DIV-2
DIV-3
Expected Results
SSA
NNT
CDC
EOC
OOB
UC
IdAM
SSA
NNT
CDC
EOC
OOB
UC
IdAM
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
X
X
x
x
X
X
X
x
X
X
X
x
x
X
x
X
x
x
x
x
x
x
X
x
x
x
x
x
X
X
x
x
x
X
X
X
x
X
X
x
x
x
X
X
x
x
x
x
x
x
X
X
x
x
x
x
x
x
x
x
X
X
x
x
x
x
x
X
x
x
x
X
x
x
x
x
x
X
X
x
From 143 DoDAF views total across IDTs to 81 with:
– Boundaries defined
– Metrics defined
25 Feb 2013
Unclassified/Pre-decisional/FOUO DRAFT
32
Unclassified/Pre-decisional/FOUO DRAFT
Expected Results/Benefits
• Can reduce DoDAF views substantially and produce a higher
quality and more usable product
– From 143 DoDAF views total across IDTs to 81 with:
• Boundaries defined
• Metrics defined
• Redundant artifacts in views reduced through tailoring
– Improve consistency
• Configuration management of models (data) rather than
views (reports)
• Boundaries between IDTs definitized
• Align and simplify the tiers from EA to RA to IDT
• Build from models and data, not views
• Practice SoSE and use DoDAF to establish boundaries
• Tailor IDT Technical Architecture scope to fit-for-purpose
• Shared vignettes and master AV-2
25 Feb 2013
Unclassified/Pre-decisional/FOUO DRAFT
33