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

• 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

Findings: Results, Recommendations• Tools and File Formats

Overview and Summary Information

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 shouldhave a corresponding entry in theIntegrated Dictionary.

Integrated

Dictionary

Core Products

4

The Operational View Captures the Critical Mission Relationships and Information Exchanges

Core Products

OPE

RA

TIO

NA

LIN

FOR

MA

TIO

NE

LE

ME

NT

DE

SCR

IPT

ION

ME

DIA

SIZ

EU

NIT

S

NA

ME

/ID

EN

TIF

IER

DE

FIN

ITIO

ND

IGIT

AL

,V

OIC

E,

TE

XT

,IM

AG

E,

ET

C.

RA

NG

EL

IMIT

S

FEE

T,

LIT

ER

S,IN

CH

ES,

ET

C.

OPE

RA

TIO

NA

LE

LE

ME

NT

&A

CT

IVIT

Y

OPE

RA

TIO

NA

LE

LE

ME

NT

&A

CT

IVIT

Y

IDE

NT

IFIE

RO

FPR

OD

UC

ING

OE

PRO

DU

CIN

GA

CT

IVIT

Y

IDE

NT

IFIE

RO

FC

ON

SUM

ING

OE

CO

NSU

MIN

GA

CT

IVIT

Y

INF

OR

MA

TIO

NS

OU

RC

E

INF

OR

MA

TIO

NS

OU

RC

EIN

FO

RM

AT

ION

DE

STIN

AT

ION

INF

OR

MA

TIO

ND

EST

INA

TIO

N

FRE

QU

EN

CY

,T

IME

LIN

ESS

,T

HR

OU

GH

PUT

SEC

UR

ITY

INT

ER

OPE

R-

AB

ILIT

YR

EQ

UIR

EM

EN

TS

INF

OR

MA

TIO

N

EX

CH

AN

GE

AT

TR

IBU

TE

S

INF

OR

MA

TIO

N

EX

CH

AN

GE

AT

TR

IBU

TE

S

INF

OR

MA

TIO

ND

ESC

RIP

TIO

N

INF

OR

MA

TIO

ND

ESC

RIP

TIO

NNodeA

NodeB

Activity 1 Activity 2

NodeC

Activity 3

Activity 2Activity 3

•Information Description•Name/Identifier•Definition•Media•Size•Units

•Information Exchange Attributes

•Frequency, Timeliness, Throughput•Security•Interoperability Requirements

•Information Source•Information Destination

Information Exchange 1

High-Level Operational

Concept Description

Operational Node Connectivity

Description

Operational Information

Exchange Matrix

High-level graphicaldescription of the operational concept of interest

Operational nodes, activities performed ateach node, node-to-node relationships, and information needlines

Information exchanged between nodes and the relevant attributes of the exchanges

To External

Node

STATEVECTOR

From External

Node

Activity Model

Activity 1

Activity 2

Activity 3

Operational activities performed and their input/output relationships

5

A Closer Look at the Operational Node Connectivity Description OV-2

NodeA

NodeB

Performs: Activity 1 Activity 2

NodeC

Performs:Activity 3

Performs:Activity 2Activity 3

To External Destination,

including Allies’,Coalition Partners’

Nodes

From ExternalSource,

including Allies’,Coalition Partners’

Nodes

Needline 1Information Type X

Needline 2Information Type Y

Needline 3Information Type W

Needline 4Information Type Z

Showing Physical Nodes

Shows that Node C needs information of type X, and that

Node B is tasked with providing that information.

6

LogicalNode

Type A(e.g., C2 Node)

LogicalNode

Type B(e.g., Logistics

Node)

Logical Node Type C

(e.g., IntelligenceNode)

To External Destination,

including Allies’, Coalition Partners’ nodes

From ExternalSource,

including Allies’, Coalition Partners’ nodes

Needline 1Information Type X

Needline 2Information Type Y

Needline 3Information Type W

Needline 4Information Type Z

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

And their attributes

PerformanceAttributes

InformationAssuranceAttributes

PhysicalEnvironment

Frequency Timeliness Throughput

Threats

Physical(includesweather,terrain)

Electronic(jamming,

hackers, etc.)Aerospace SeaLand

Political/Economic

SecurityClassification

(& Declassification/Restrictions, if app.)

Priorityor

Criticality

IntegrityChecks

Required

AssuredAuthorization

to Send/Receive

1

2

n

e.g., 1-a 1-n

e.g., 2-a

2-n...

...

...

Identifier/Name of

Operational Needline

Supported(from OV-2)

CONT INUED

Identifier/Name of

InformationExchange

Remarks/Other

... ... ......... ... ...... ... ... ...

... ... ...

... ... ...... ... ... ... ... ...... ...... ... ... ...

Natureof

Transaction

InformationSource

InformationDestination

Description(Content)

Size MediaCollaborative

(Y/N)?

LISI Level

Required

ID ofProducing Node

(facility orlogicalnode)

ID ofReceiving Node

(facility orlogicalnode)

ID/name of Producing

Activity

Identifier/Name of

Operational Needline

Supported(from OV-2)

Identifier/Name of

InformationExchange

1

2

n

e.g., 1-a

1-n

e.g., 2-a 2-n...

...

...

Mission/Scenario

Language(For Multi-

NationalOperations)

Units

... ... ... ... ... ......... ... ... ... ... ...

... ... ... ...... ... ... ... ...... ... ... ... ...

Purpose/Triggering

Event

ID/name ofReceivingActivity

* *

* *

*

** * *

* * *

* Indicates minimum required entries

* *

*

For each needline ...There is a listing of distinct information exchanges ...

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

InternodalSystem-to-System

Intranodal Intrasystem

Core Product: System Interface Description

The Systems View Examines Current and Postulated IS Capabilities in Context with Mission Operations

NODE A

NODE B

NODE C

SYSTEM2

SYSTEM1

SYSTEM1

SYSTEM3

SYSTEM4

EXTE

RN

AL

CO

NN

ECTI

ON

SYSTEM1

COMMS Interface S1 A/S1 B

COMMS Interfa

ce S2 A/S1 B

SYSTEM2

CO

MM

S In

terf

ace

S1C

/S3 B

SAT

CO

M I

nter

face

S4 C

/S3 B

One-way SATCOM Interface S2

A /S1C

InternodalNode-Edge-to-Node-Edge

SAT

CO

M I

nter

face

NODE A

NODE B

NODE C

SYSTEM2

SYSTEM1

SYSTEM1

SYSTEM3

SYSTEM4

EXTERNAL

CONNECTI

ON

SYSTEM1

COMMS Interface 1

COMMS Interface 2

SYSTEM2

CO

MM

S In

terf

ace

3

One-way SATCOM Interface

NODES

COMMUNICATIONSNETWORK

FROM/TO OTHER

SYSTEM1

SYSTEM3

SYSTEM

2

NODE BCO

MM

UN

ICA

TIO

NS

NE

TW

OR

KF

RO

M/T

O O

TH

ER

NO

DE

S

Interface 1

Interface 2

SYSTEM 1

Component 1 Component 2

Component 4 Component 3

Component 5

FROM/TOOTHER

SYSTEMS

FROM/TOOTHER

SYSTEMS

10

Web-based Example (All Nodes Can Get All Information): Federal Commons System Interface Description

INTERNET

HI-TECH APPLICANT/GRANTEE

TYPE NODE

FIREWALLE

DATASERVER

E

LABSYSTEMS

RESEARCHDEPARTMENT

SYSTEMS

FINANCIALAPPLICATIONS

SERVER E

E-MAILSERVER

E

OASYSTEMS E

DATASERVER

D

FIREWALLD

OASYSTEMS

D

FINANCIALAPPLICATIONS

SERVER D

E-MAILSERVER

D

HI-TECHGRANTING

AGENCY TYPE NODE

FEDERAL COMMONSWEB NODE

httpSERVER A

DATASERVER

A

FIREWALLA

USERADMINISTRATION

SERVER A

REGISTRATIONSERVER A

S/W APPLICATIONSERVER A

FEDERAL COMMONS

SECONDARY NODE

DATASERVER

B

FIREWALLB

INTERNETCONNECTION E

VPN A

EDI VPN

INTERNETCONNECTION A

INTERNETCONNECTION D

S/W APPLICATIONSERVER D

LINKS THAT SUPPORT NEEDLINES 1 & 4

LINKS THAT SUPPORTNEEDLINES 2 & 3

LINKS THAT SUPPORTNEEDLINES 5 & 6

E-MAILSERVER

A

“Web” grid indicates that all nodes can receive all information

Color coded lines indicate which nodesneed which information

11

The Technical View Identifies the Implementation Criteria That Govern the Given Architecture

Core Product: Technical Standards ProfileApplication Software

SERVICE AREA SERVICE STANDARDSupport Applications Web Applications Internet Explorer Version 4.X or better

Netscape Version 3.X or betterApplication Platform

SERVICE AREA SERVICE STANDARDData Interchange Document

InterchangeXML 1.0, W3C Recommendation, 10February 1998, Rec-xml-19980210(Extensible Markup Language)HTML 4.0 Specification, W3CRecommendation revised 24-apr-1998,Rec-html40-19980424 (HypertextMarkup Language)

Communications World Wide WebServices

IETF RFC-2616 Hypertext TransferProtocol – HTTP/1.1, June 1999

Electronic Mail IETF Standard 10/RFC-821/RFC-1869/RFC-1870 Simple Mail TransferProtocol (SMTP) Service Extensions,November 1995IETF Standard 11/RFC-822/RFC-1049Standard for the Format of ARPAInternet Text Messages, 13 August 1982IETF RFCs 2045-2049 MultipurposeInternet Mail Extensions (MIME),November 1996

Transport Services IETF Standard 7/RFC-793 TransmissionControl Protocol, September 1981IETF Standard 6/RFC-791/RFC-950/RFC-919/RFC-922/RFC-792/RFC-1112 Internet Protocol, September 1981

DistributedComputing

Object Services Common Object Request BrokerArchitecture (CORBA) Version 2.3Object Management Group (OMG)document formal/98-12-01, June 1999(Proposed)

Security Authentication FIPS-PUB 112 Password Usage, 30 May1985

Application SoftwareMISSION AREA APPLICATIONS

SERVICEAREA

SERVICE STANDARD

All WebApplications

Interface 4D: (Application to Web Server)Common Gateway Interface (CGI) 1.1, NCSASoftware Development

Application SoftwareSUPPORT APPLICATIONS

SERVICEAREA

SERVICE STANDARD

CommunicationsApplications

WebApplications

Component: Internet Explorer Version 4.X orbetterComponent: Netscape Version 3.X or betterInterface 4L: HTML 4.0 Specification, W3CRecommendation revised 24-apr-1998, Rec-html40-19980424 (Hypertext Markup Language)

PersonalMessaging

Interface 4D: (E-Mail Client to E-Mail Server)IETF Standard 10/RFC-821/RFC-1869/RFC-1870 Simple Mail Transfer Protocol (SMTP)Service Extensions, November 1995Interface 4D: (E-Mail Server to E-Mail Client)Internet Mail Access Protocol (IMAP)

Application PlatformSYSTEM SUPPORT SERVICES (XOS)

SERVICEAREA

SERVICE STANDARD

Communications World WideWeb Services[Web Server]

Interface 3L: IETF RFC-2616 Hypertext TransferProtocol – HTTP/1.1, June 1999

Electronic Mail[E-Mail Server]

Interface 3L: IETF Standard 10/RFC-821/RFC-1869/RFC-1870 Simple Mail Transfer Protocol(SMTP) Service Extensions, November 1995Interface 3L: IETF Standard 11/RFC-822/RFC-1049 Standard for the Format of ARPA InternetText Messages, 13 August 1982Interface 3L: IETF RFCs 2045-2049Multipurpose Internet Mail Extensions (MIME),November 1996

OPERATING SYSTEM SERVICESSERVICE

AREASERVICE STANDARD

Operating System KernelOperations

Interface 3L: IETF Standard 7/RFC-793Transmission Control Protocol, September 1981Interface 3L: IETF Standard 6/RFC-791/RFC-950/RFC-919/RFC-922/RFC-792/RFC-1112Internet Protocol, September 1981Services View

Interfaces View

12

The Framework Specifies Common Architecture Data

Core Product - Technical View

Entities and AttributesCore Product - Systems View

Entities and AttributesCore Products - Operational View

Entities and Attributes

The Framework provides a description of the data that must becaptured 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)Entities, Attributes, & Relationships Example Values/Explanation

Graphical Box Types Operational Node*

Name* Name or label of node box on diagramDescription* Text description of mission or role being

performed by the nodeLocation Actual location or generic location type

Graphical Arrow Types Needline*

Identifier* Unique identifier of the needline (may be anumber)

Descriptive Name* Descriptive name for the needline, usuallyassociated with the type(s) of informationassociated with the needline

Description* Text description of needline“From” Operational Node* Name of node box that is the source of the

node connector on the diagram“To” Operational Node* Name of the node box that is the

destination of the node connector on thediagram.

14

The Core Products Link to Each Other HIGH-LEVEL OPERATIONALCONCEPT DESCRIPTION

(OV-1)

VALUE ADDED: SUMMARY LEVEL REPRESENTATION OF ORGANIZATIONS/ROLES, MISSION, AND CONTEXT FOR THE ARCHITECTURE

OPERATIONAL CONCEPTROLES & MISSIONS SET SCOPE FOR ACTIVITY MODEL

OPERATIONAL INFORMATION EXCHANGE MATRIX (OV-3)

VALUE ADDED: INDIVIDUAL INFORMATION EXCHANGES

ASSOCIATED WITH EACH NEEDLINE, PERFORMANCE REQUIREMENTS FOR OPERATIONAL INFORMA-

TION EXCHANGES

OPERATIONAL NODE CONNECTIVITY DESCRIPTION (OV-2)

VALUE ADDED: STATEMENT OF OPERATIONAL NODES, ACTIVITIES, AND CRITICAL INFORMATION NEEDS

(NEEDLINES & SUMMARY INFORMATION EXCHANGED)

• OPERATIONAL NODES ARE ASSOCIATEAD WITH SYSTEMS AND SYSTEMS NODES

• EACH OPERATIONAL NEEDLINE MAPS TO ONE OR MORE SYSTEMS LINKS

SYSTEMS INTERFACE DESCRIPTION(SV-1)

VALUE ADDED: STATEMENT OF SYSTEMS NODES, SYSTEMS, LINKS & COMPONENT INTERFACES; SUMMARIZED SYSTEM INFORMATION EXCHANGES

STANDARDS APPLY ATSYSTEM TO SYSTEM INTERFACES

TECHNICAL STANDARDS PROFILE(TV-1)

VALUE ADDED: COMPLETE LIST OF RELEVANT STANDARDS WITH OPTIONS & PARAMETERS

INFORMATION EXCHANGES ASSOCIATED WITH EACH NEEDLINE ARE DETAILED IN OV-3

STATEVECTOR

NodeA

NodeB

Performs: Activity 1 Activity 2

NodeC

Performs:Activity 3

Performs:Activity 2Activity 3

High-LevelDescription of NeedlineCollective summary ofinformation exchanged, including:• Needline identifier/name• Critical attributes for the given architecture’s purpose, such as timeliness, bandwidth, media, etc., • Statement of Minimum, Mean, and Maximum requirements for critical attributes

To External Destination,

including Allies’,Coalition Partners’

Nodes

From ExternalSource,

including Allies’,Coalition Partners’

Nodes

• ACTIVITIES MAP TO OPERATIONAL NODES

• I/OS MAP TO NEEDLINES• PERFORMERS OF ACTIVITIES,

IF SHOWN ON 0V-5, MAP TO OPERATIONAL NODES

VALUE ADDED: BUSINESS/MISSION PROCESS & RELATIONSHIPS AMONG ACTIVITIES AND OPERATIONAL INFORMATION EXCHANGED

A1

A2

A3

ACTIVITY MODEL (OV-5)

SATCOM Interface

NODE A

NODE B

NODE C

SYSTEM

2

SYSTEM1

SYSTEM1

SYSTEM3

SYSTEM

4

EXTERNALCONNECTION

SYSTEM1

COMMS Interfa

ce

COMM

S Inter

face

SYSTEM

2

COMMS Interface

One-way SATCOM Interface

Natureof

Transaction

InformationSource

InformationDestination

Description(Content)

SizeMedia

Collabo-rative

or One-Way?

LISI LevelReq’d

SenderOPFAC

(or functionalnode, as

appropriate)

RecipientOPFAC

(or functionalnode, as

appropriate)

Sender Performing

Activity(e.g.,

UJTL ID)

RecipientPerforming

Activity(e.g.,

UJTL ID)

Purpose/Triggering

Event

Identifier/Name of

Operational Needline

Supported(from OV-2)

IERInformation

Element(Identifier/Name of

InformationExchange)

1

2

n

e.g., 1-a 1-n

e.g., 2-a 2-n...

...

...

SenderOwning

Organization/Unit

Recipient Owning

Organization/Unit

Scenarioor

Mission

Language(For Multi-

NationalOperations)

Units

... ... ... ... ... ... ... ... ... ... ... ... ... ... ...... ... ... ... ... ... ... ... ...... ... ... ... ... ... ...

OPERATIONAL CONCEPTCONNECTIVITY & INFORMATIONEXCHANGES, IF SHOWN ON 0V-1, MAP TO OPERATIONAL NODE CONNECTIVITYDESCRIPTION NEEDLINES & INFORMATION EXCHANGES

INNPUT/OUTPUT LABELS MAP TO OPERATIONAL INFORMATIONEXCHANGES (NOT ALWAYS ONE-TO-ONE)

SERVICE AREA SERVICE STANDARDSupport Applications Web Applications Internet Explorer Version 4.X or better

Netscape Version 3.X or betterData Management Business Data

StandardsData Universal Numbering System (DUNS)

ZIP Code DirectoryCongressional District IdentifierISO 3166: ISO 3166-1 (1Ocober 1997) and ISO 3166-2 (15 December 1998) (Codesfor the Representation of Names of Countries and Their Subdivisions)U.S. State Codes and Territory CodesCatalogue for Federal Domestic Assistance ProgramElectronic Grants Data Elements

Data Interchange DocumentInterchange

XML 1.0, W3C Recommendation, 10 February 1998, Rec-xml-19980210 (ExtensibleMarkup Language)HTML 4.0 Specification, W3C Recommendation revised 24-apr-1998, Rec-html40-19980424 (Hypertext Markup Language)ANSI ASC X12 (Electronic Data Interchange)

Communications World Wide WebServices

IETF RFC-2616 Hypertext Transfer Protocol – HTTP/1.1, June 1999

Electronic Mail IETF Standard 10/RFC-821/RFC-1869/RFC-1870 Simple Mail Transfer Protocol(SMTP) Service Extensions, November 1995IETF Standard 11/RFC-822/RFC-1049 Standard for the Format of ARPA InternetText Messages, 13 August 1982IETF RFCs 2045-2049 Multipurpose Internet Mail Extensions (MIME), November1996

Overview and Summary Information and Integrated Dictionary are not shown because they relate to allother products

15

Some Other Important Product Linkages

…And the sending and receiving systems used to implement the interface are indicated...

OV-3 Operational InformationExchange Matrix

DATA SYSTEM

EXCHANGE MATRIX

ATTRIBUTES

NODE A

NODE B

NODE C

SYSTEM

2

SYSTEM1

SYSTEM

1

SYSTEM3

SYSTEM

4

EXTERNALCONNECTION

SYSTEM1

COMMS Interfa

ce S1 A/S1 B

COMM

S Inter

face S

2 A/S1 B

SYSTEM

2

COMMS Interface S1C/S3B

COMMS Interface S4C/S3B

One-way COMMS Interface S2

A /S1C

SV-1 System InterfaceDescription

SV-6 System Data Exchange Matrix

Natureof

Transaction

DataSource

DataDestination

ContentSize MediaFormat LISI LevelAchievable

ID ofSource System

ID ofReceiving

System

SourceSystem

Function(from S-4)

ReceivingSystem

Function(from S-4)

OperationalNode(s)Where

System IsResident

OperationalNode(s)Where

System IsResident

ProtocolsUsed

Identifier/Name of

Operational Needline

Supported(from OV-2)

Identifier/Name of

OperationalInformationExchangeSupported

(from OV-3)

e.g., 1-ae.g., 1-b

e.g., 1-c

Identifier/Name of

CorrespondingSystem

Interface(s)(from SV-1)

e.g., Interface 1

e.g., Interface 2...

e .g., Interface n

Needline 1

Needline 2

Needline n

...

e.g., 1-de.g., 1-e

e.g., 1-f

1

3

Natureof

Transaction

InformationSource

InformationDestination

Description(Content)

SizeMedia

Collabo-rative

(Y/N)? LISI LevelReq’d

ID ofProducing Node

(facility orlogicalnode)

ID ofReceiving Node

(facility orlogicalnode)

Name of Producing

Activity

Identifier/Name of

Operational Needline

Supported(from OV-2)

Identifier/Name of

InformationExchange

1

2

n

e.g., 1-a 1-n

e.g., 2-a 2-n...

...

...

OwningOrganization

of Producing

Node

OwningOrganization

of Receiving

Node

Mission/Scenario

Language(For Multi-

NationalOperations)

Units

... ... ... ... ... ... ... ... ... ... ... ... ... ... ...... ... ... ... ... ... ... ... ...... ... ... ... ... ... ...

Purpose/Triggering

Event

Name ofReceivingActivity

…The individual information exchanges are assigned to the appropriate system interface...

2

Each needline is decomposedinto one or more system interfaces ...

16

What Information Must Be Captured?

Implementation Criteria

• Standards, Conventions• Operating Environment

What Performance Measures?

Where Captured? Audit Trail

TARGETS KILLED

SAUDI ARABIA PFP

SITES DETECTED

IRAQ

TIMELY INTERDICTION

BOLIVIA PIT RAID

COUNTERDRUG

COUNTER-PROLIFERATION SUPPORT TO

MILITARY OPS

Mission Effectiveness

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

• Applications and products• Platform, operating system

Ope

rati

onal

Mis

sion

R

equ

irem

ents

Sys

tem

sC

apab

ilit

ies

Impl

emen

tati

onC

rite

ria

OPERATIONS

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

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

Operational Node Connectivity

Description

Technical Standards

Profile

System Interface Description

SYSTEMS

TECHNICAL

Mission Operations

System Attributes/Metrics

System Implementations

Architecture Product Linkages Provide the “Audit Trail” That Relates Technology to Mission

Operations

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)Investment Portfolio

Related Programs

i

i

Policy & Technology Enablers

Limited

4

Managed 5

Managed 5

Optimized

i

Component Capability Levels5

43Component Definition

1

1

2Ad-hoc

1

2Ad-hoc

Minimal

3

Components

IT ServiceDelivery

IT ServiceDelivery

Email/Messaging

Email/Messaging

CollaborationTools

CollaborationTools

Directory Services

Directory Services

IntelligenceApplicationsIntelligenceApplications

Search & Access

Facilitators

Search & Access

FacilitatorsAdministrative

ApplicationsAdministrative

Applications

INFOSECINFOSEC

Computing Platform

Computing Platform

Enterprise InfrastructureManagement

Enterprise InfrastructureManagement

ResourcingResourcing

GovernanceGovernance

NetworkNetwork

Subscription &Delivery Services

Subscription &Delivery Services

InformationStorage &

Management

InformationStorage &

Management

IT Competency

IT Competency

2

4Process InfrastructureKnowledge Management

54

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

SCISECRET

UNCLASSIFIED

ITCompetency

ITCompetency

Email/MessagingEmail/Messaging

CollaborationCollaboration

Directory Services

Directory Services

DomainApplications

DomainApplications

Search & AccessSearch & AccessAdministrativeApplications

AdministrativeApplications

InformationAssurance

InformationAssurance

Computing Platform

Computing Platform

InfrastructureManagement

InfrastructureManagement

InfrastructureKnowledge ManagementKnowledge Management

ResourcingResourcing

GovernanceGovernance

NetworkNetwork

Subscription & Delivery Services

Subscription & Delivery Services

InformationStorage &

Management

InformationStorage &

Management

IT Service Delivery

IT Service Delivery

Multiple Security Level

Interconnection

ProcessProcess

Components of the Capability Roadmap -Select the components you need and create new ones as needed

20

1

2

Interactions focused on separate objectives using organization-unique systems and databasesAd-hoc

Rudimentary, secure information exchanges between some organizations on commonintranet, with unpredictable reliabilityMinimal

3

Limited

Secure multimedia collaboration within interest groups using partially integrated networks, limited data sharing, and interoperable applications and services

4

Structured

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

5

Optimizing

i

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 globalreach

Standard Capability Scale

21

OV-4 Organizational Relationships Chart

Top-LevelOrganization

CommandRelationship

Second-LevelOrganization

Second-LevelOrganization

Third-LevelOrganization

Third-LevelOrganization

Coordination orOther SpecifiedRelationship

OV-6 Operational Timing and Sequencing Products

SUBSTATE1

SUBSTATE2

SUBSTATE3

SUBSTATE4

EVENT 3

EVENT 4

EVENT 1

EVENT 2

OV-6bOperational State Transition Description

OV-6a Operational Rules Model: no graphic

OV-6cOperational Event/Trace Description

EVENTS/TIME

NODESNODE 1 NODE 2 NODE 3

EVENT 1

EVENT 2

EVENT 3

EVENT 4 EVENT 5

EVENT 6

EVENT 7 EVENT 8

time 1

time 2

time 3

time 3'

{formula relatingtime 3 to time 3'}

time n

{formula relatingtime 1 to time 2}

23

OV-7 Logical Data Model

EntityName

Relationship

Attributes • .....• .....• .....

24

SV-2 System Communications Description

Intranodal Perspective

Internodal Perspective

NODE A

NODE B

NODE CEXTERNAL CONNECTION

(OUTSIDE THENODES OF INTEREST)

COMMUNICATIONSPATHS, AND NETWORKS

DETAILS OF COMMSINTERFACE 1

NODE A

Local Area Net

System1

System2

System3

System4

System5

EXTERNALCONNECTION(OUTSIDE THENODES OF INTEREST)

CONNECTIONTO NODE B

CONNECTIONTO NODE B

CONNECTIONTO NODE C

Two-WayCommunicationsPaths

One-WayCommuni -cationsPath

25

SV-3 System-System Matrix

SYSTEM1

SYSTEM2

SYSTEM3

SYSTEM4

SYSTEM5

SYSTEM6

SYSTEM7

SYSTEM8

SYSTEM9

SYSTEM10

SYSTEM 1

SYSTEM 2SYSTEM 3SYSTEM 4

SYSTEM 5

SYSTEM 6SYSTEM 7

SYSTEM 10

SYSTEM 8

SYSTEM 9

26

SV-4 Systems Functionality Description

System Function

1

DATAREPOSITORY

DATAFLOW 1

DATAFLOW 2

DATAFLOW 3

DATAFLOW 4

DATAFLOW 5

DATAFLOW 6

DATAFLOW 7

DATAFLOW 8

DATAFLOW 9

DATAFLOW 10

EXTERNALSOURCE

1

EXTERNALSOURCE

2

EXTERNALSINK

1

EXTERNALSINK

2

System Function

3

System Function

4

System Function

2

27

SV-5 Operational Activity to System Function Traceability Matrix

1

1.1

1.1.1

1.1.1.1

1.1.1.2

1.1.1.3

1.1.2

1.1.2.1

1.1.2.2

1.1.2.3

1.1.3

1.1.3.1

1.1.3.2

1.1.3.3

1.1.3.4

3.11

3.11

.3

3.12

3.12

.1

3.12

.2

3.12

.3

3.13

3.14

3.14

.1

3.14

.2

3.14

.3

3.14

.4

3.15

3.16

3.17

3.17

.1System Functions

....

Operational Activities

X

XX

X

X

X

XX

X

X

X

X

XX

X

28

SV-6 System Data Exchange Matrix

Nature of Transaction Data Source Data Destination

Content Size FormatLISI Level Achievable

Source System Name

Receiving System Name

Source System Component

Receiving System Component

Other Protocols

Identifier/Name ofOperational

Needline Supported (from OV-2)

Identifier/Name of Operational

Information Exchange Supported

(from OV-3)

e.g., 1-a

e.g., 1-b

Identifier/Name ofCorrespondingSystem Interface(s)

(from SV-1)

e.g., Interface 1

e.g., Interface 2...

e.g., Interface n

Needline 1

Needline 2

Needline n

...

e.g., 1-c

e.g., 1-d

Identifier/System Data

Exchange

e.g., 1-a (1)e.g., 1-a (n)

...

Performance Attributes Information Assurance Attributes Physical Environment

Frequency Timeliness Throughput

Threats

Physical Electronic Aerospace SeaLandPolitical/EconomicClassification

Criticality/Priority

Encryption AuthenticationOther

...

Identifier/Name of

Operational

Information Exchange Supported

(from OV-3)

e.g., 1-a

e.g., 1-b

e.g., Interface 1

e.g., Interface 2...e.g., Interface n

Needline 1

Needline 2

Needline n...

e.g., 1-ce.g., 1-d

e.g., 1-a (1)

Identifier/System Data

Exchange

e.g., 1-a (n)...

Identifier/Name of Operational

Needline Supported

(from OV-2)

Identifier/Name ofCorresponding System Interface(s)

(from SV-1)

* * * ** * * * *

* * * * *

* Indicates minimum recommended entries

CONTINUED

29

SV-7 System Performance Parameters Matrix

Hardware Element 1

Maintainability

Availability

System Initialization Time Data Transfer Rate

Program Restart Time

S/W Element 1 / H/W Element 1 Data Capacity (e.g., throughput or # of input types) Automatic Processing Responses (by input type, # processed/unit time) Operator Interaction Response Times (by type)

Effectiveness Availability Mean Time Between S/W Failures Organic Training

S/W Element 2 / H/W Element 1

System Name Time0 (Baseline) Time1 Timen (Objective)

Performance Thresholds/Measures

Hardware Element 2

30

SV-8 System Evolution Description

XIDB

IDB-II

Mainframe IDB

NEWSYSTEM

SUITE

DIA JMIIS

MIIPS

CONSTANT WEB

Collateral XIDB

PORTSMARS (HATS)

CSIDS

SDB

STANS

FORT/FORTRIS

RAILS

MIDB C&P Capability

ACOM Amphibious DBMILFAC

ACOM TMMC&P Data Server

EOB-S

6/95 3/96 6/96 12/96 6/97 9/97

v 1.0 v

1.1v 1.2

v 2.0

LEGACYMAINFRAMESYSTEM

FEDERATEDDISTRIBUTEDSYSTEM

CLIENT/SERVERPLATFORMS, LAN, &MIDDLEWARE INSTALLED

SEGMENT 1 APPLICATIONS& UNIQUE DATA CONVERTEDTO CLIENT/SERVER

SEGMENT 2 APPLICATIONS& UNIQUE DATA CONVERTEDTO CLIENT/SERVER

SEGMENT 3 APPLICATIONS,& UNIQUE DATA CONVERTEDTO CLIENT/SERVER

COMMON DATA CONVERTEDTO SHARED DATA SERVER

NEW FUNCTION 1 &UNIQUE DATA IMPLEMENTEDON CLIENT SERVER (& INTEGRATED WITH COMMON DATA ON MAINFRAME)

NEW FUNCTION 2 &UNIQUE DATA IMPLEMENTEDON CLIENT SERVER (& INTEGRATED WITH COMMON DATA ON MAINFRAME)

V1.0

V1.1

V1.2

V1.3

V1.4

V2.0

+6 MO. +12 MO. +18 MO. +24 MO. +36 MO. +48 MO. +60 MO.Migration Example

Evolution Example

31

SV-9 System Technology Forecast- Fragment -

TECHNOLOGY FORECASTSTRMTECHNOLOGYCATEGORY

SHORT TERM(0-6 Months)

MID TERM(6-12 Months)

LONG TERM(12-18 Months)

Application SoftwareSupportApplications

Microsoft Office2000 available (forWindows 2000)

Microsoft Office2000 stable enoughfor full scaleimplementation

Microsoft Officeavailable for LinuxE-mail on wirelessPDAs commonplace

Application PlatformUser InterfaceServices

Spoken interfacesupport available

Spoken user interfacebecomes the standarduser interface

Data Management Oracle 9i availableMySQL (OpenSource DBMS)available

Operating System Next MS Windowsdesktop upgradeexpectedNext Red Hat Linuxmajor releaseexpected

Next MS Windowsserver upgrade expected

PhysicalEnvironment

Intel IA-64 becomesstandard processor fordesktopsInitial use of quantumcomputing technologies

32

SV-10 Systems Timing and Sequencing Products

SUBSTATE1

SUBSTATE2

SUBSTATE3

SUBSTATE4

EVENT 3

EVENT 4

EVENT 1

EVENT 2

COMPLEX TRANSITIONS(SYNCHRONIZATION OF CONTROL )

SV-10a Systems Rules Model: no graphic

SV-10b Systems State Transition Description

EVENTS/TIME

NODESNODE 1 NODE 2 NODE 3

EVENT 1

EVENT 2

EVENT 3

EVENT 4 EVENT 5

EVENT 6

EVENT 7 EVENT 8

time 1

time 2

time 3

time 3'

{formula relatingtime 3 to time 3'}

time n

{formula relatingtime 1 to time 2}

SV-10c Systems Event/Trace Description

33

SV-11 Physical Schema

PHYSICALDATAMODEL

OPTIONS

MESSAGE FORMAT

• STANDARDS REFERENCE• MESSAGE TYPE(S)• MESSAGE FIELDS WITH REPRESENTATIONS• MAP FROM LDM TO MESSAGE FIELDS

FILE STRUCTURE

• STANDARDS REFERENCE• RECORD AND FILE DESCRIPTIONS• MAP FROM LIM TO RECORD FIELDS

PHYSICAL SCHEMA

• DDL OR ERA NOTATION (WITH SUFFICIENT DETAIL TO GENERATE THE SCHEMA)

• MAP FROM LDM TO PDM WITH RATIONALE

OTHER OPTIONS

AND/OR

•••

34

TV-2 Standards Technology Forecast- Fragment

STANDARDS FORECASTSTRMCATEGORY SHORT TERM

(0-6 Months)

MID TERM

(6-12 Months)

LONG TERM

(12-18 Months)Application PlatformData InterchangeDocumentInterchange

Security MarkingDTD – in CAPCOcoordination(proposed ICstandard)

Mapping Geography DTD 2.0– accepted by GISConsortium

Commercialproducts that use thestandard becomeavailable

Geospatial XSD – incoordination OpenGIS

Geospatial XSD –accepted by OpenGIS

CommunicationsElectronic Mail

IETF RFC2060Internet MailAccess Protocol(IMAP) – accepted,replaces de factostandard

World Wide WebServices

IETF - RFC???Common GatewayInterface (CGI) 1.2– becomes proposedstandard

IETF – RFC???Common GatewayInterface (CGI) 1.2– accepted, replacesCGI 1.1, the defacto standardIETF – RFC 2818HTTP Over TLS –accepted, replacesRFC 2616