Transcript NCOIC Template - pair Networks, Inc.

Network Centric Operations
Industry Consortium
NCOIC Interoperability
Framework
(NIF™)
NCOIC Interoperability Framework
and
NCOIC Patterns Overview
(NIF™)
and NCOIC Patterns
Overview
August 2008
Approved for Public Release
NCOIC-NIF™ Overview
© Copyright 2008 NCOIC - All rights reserved
assists customers in obtaining
interoperable solutions
About NIF™
Customer
Goals
Missions to
Achieve Goals
NCO Initiatives
Database
Mission
Needs
Solutions to
Needs
1.
2.
3.
4.
Resulting
Services
Analysis of Alternatives
Requirements Derivation
Requirements Validation
Design Synthesis
SCOPE Model
NIF ™
NIF™
Provides enabling guidance
for net-ready solutions
-Overarching framework
- Specialized frameworks
- Pattern template
NCOIC
Interoperability
Framework
5.
6.
7.
8.
BB
NCAT ™
Building
Blocks
Net Centric
Analysis
Tool
End-to-End
Quality of
Service
Design Verification
Deployment
Support
Upgrade/Disposal
Modeling/simulation
Test/evaluation
© Copyright 2008 NCOIC - All Rights Reserved
2
assists customers in obtaining
interoperable solutions
Why Is a NIF™ Needed?
Why Is a NIF™ Needed?

Most attempts at common architectures and
common standards have failed to achieve
interoperable systems

The NIF™ is different because…
– Recommends standards plus guidance flexible enough to
be used in multiple architectures
– Derived by consensus across industry – not dictated by a
single organization
– Closer to Internet model (IETF methodology in the W3C)
than a prescriptive policy-based approach for a
department or ministry of defense
3
© Copyright 2008 NCOIC - All Rights Reserved
assists customers in obtaining
Standards Alonesolutions
are not Sufficient–Need Guidance
interoperable
Standards Alone Are Not Sufficient–Need Guidance
Performance “A”
Standard
“A”
Standard
“E”
Standard
“D”
Performance
“C”
Standard
“F”
Standard
“C”
Performance “B”
Standard
“B”
 Often the “BEST” Standard depends on the Mission
– Real-World Condition! Often no “One Size Fits All”
– Requires Guidance to select Consistent Standards
by Class of Missions: very hard to do! (but a key goal of the NIF™)
4
© Copyright 2008 NCOIC - All Rights Reserved
Guidance re: Mission
assists
customers in obtaining
interoperable solutions
Guidance re: Mission
 Usually no one Standard can be general enough to meet all
needs of all domains, as the SCOPE Model demonstrates
Cost*
QoS*
Standard “A”
attribute range
For Technology X
Transfer Rate*
Standard “B”
attribute range
For Technology X
Net
Awareness*
Security*
* Examples of SCOPE
dimensions, actual
dimensions are more
comprehensive
Different Standards
because Different
Mission Domains have
Different Needs!
Autonomy*
Power*
© Copyright 2008 NCOIC - All Rights Reserved
Service Orientation*
5
Guidance re: Level of NCO
assists
customers in obtaining
interoperable solutions
Guidance re: Level of NCO
 What is the appropriate level of NetCentricity for a given
Notional Cost (or Risk)
operational context? May impact selection of Standards!
Which is the
“Best” Standard
for this
hypothetical
operational
context?
Standard “A”
For Technology X
Standard “B”
For Technology X
This example is
time-based; many
other perspectives!
Today’s Range of
required performance
Future Range of
required performance
Notional Performance
6
© Copyright 2008 NCOIC - All Rights Reserved
Example:
Notional Intended
Span of Standard
assists
customers
in obtaining
interoperable solutions
Example: Notional Intended Span of Standard
Notional Intended Span of Standard
% A-to-B
Interoperable
SYSTEM “A” Extension:
Added Highly-Desirable
Range
SYSTEM “B” Extension:
Added Highly-Desirable
Feature
100%
Interoperable
100%
Interoperable
 “Bad” Standard, or “Bad” System Implementations?
– Real-World Condition!
– In a System-of-Systems, cannot force systems to not use
highly-desirable features when operating independently
– Requires Guidance to operate in 100% Interoperability Regions
– Can only recommend use of 100% Interoperability Regions
when Systems need to Interoperate
7
© Copyright 2008 NCOIC - All Rights Reserved
Guidance
re: Versions
assists
customers
in obtaining
interoperable solutions
Guidance re: Versions
ORIGINAL Standard v1.0
% Versions
Interoperable
UPDATED Standard v1.1
NEW Standard v2.0: “Backward Compatible”
100% all 3 versions
Interoperable
100% v1.1 & 2.0
Interoperable
V1.1 & v2.0
V1.0 & v2.0
 Is Everyone Running the Same Version of a Standard?
– Real-World Condition!
– In a System-of-Systems, cannot force Legacy systems to
update to newest standard
– Requires Guidance to operate in 100% Interoperability Regions
– Can only recommend use of 100% Interoperability Regions
when Systems need to Interoperate
8
© Copyright 2008 NCOIC - All Rights Reserved
Guidance re: Standards Interpretations
assists
customers in obtaining
interoperable solutions
Guidance re: Standards Interpretations
Interpretation “A” of Standard
%
Interoperable
Interpretation “B” of Standard
GUIDED Interpretation of Standard
Goal: 100% Interoperable
with Guided Interpretation
Inconsistent Interoperability
without Common Guidance
 Does Everyone Understand the Standard the Same Way?
– Real-World Condition! (Not necessarily a bad Standard)
– Requires Guidance to achieve goal of common understanding
• Different Languages; different Cultural backgrounds
• Same Standard applied in different Operational Domains
• Same Standard implemented by designers with different levels of
experience, different technical disciplines, different company rules
9
© Copyright 2008 NCOIC - All Rights Reserved
Interdependency
ofin
Standards
assists
customers
obtaining
interoperable solutions
Interdependency of Standards
Layers of Interoperability
Political or Business Objectives
Harmonized Strategy/Doctrines
Aligned Operations
 Standards are
Interdependent!
– Standards for a layer of
Interoperability often
People &
dependent on standards
Processes
& Applications for lower layers
Aligned Procedures
C2 Application
Standard
Knowledge/Awareness of Actions
Semantic/Information Interoperability
Data/Object Model Interoperability
Connectivity & Network Interop.
Physical Interoperability
COI
COP
KM
Information Standard Standard Standard
Services
Web Services
Pub / Sub
Standard
Network
Transport
Standard
IPv6
Standard
Radio
Standard
LAN
Standard
10
© Copyright 2008 NCOIC - All Rights Reserved
Guidance must be CLEAR and Straightforward!
assists
customers in obtaining
interoperable solutions
Guidance must be CLEAR and Straightforward!
11
© Copyright 2008 NCOIC - All Rights Reserved
The Value
of the NIF™
Approach
assists
customers
in obtaining
interoperable solutions
The Value of the NIF™ Approach
 Addresses the problems listed on prior pages
– Focus is on Net-Centric / Net-Enabled aspects
 Encourages users to use a common terminology and
approach to achieving the guidelines
– Consistent terminology and repeatable patterns of solutions
 Includes lessons learned from domain experts to keep future
users from repeating common mistakes
– Addresses root causes of interoperability failures
 Integrates guidance across critical specialties
– The “Specialized Frameworks” e.g., Information Assurance,
Services, Semantics, Mobility, etc.
 Includes guidance for verification that the standards and

guidance have been “properly” followed
Designed to support all stages of the system life cycle
– Acquisition, initial design, upgrade design, training
12
© Copyright 2008 NCOIC - All Rights Reserved
Intended
Users of the
NIF™
assists
customers
in obtaining
interoperable solutions
Intended Users of the NIF™

Oriented toward “Architects” (System, Enterprise, SoS)
as well as Design Engineers
– Useful for general industry and governments, not just NCOIC members
 How does the NIF™ help the intended users?
– Acquisition community
• Generating better Request For Proposals / Tenders
• Evaluating proposals from a common perspective
– Industry
• Expands available markets (example: the Internet)
• Points architects in the right direction for interoperability
• Establishes infrastructure that allows a company to focus on
value added enhancements rather than basic environment
13
© Copyright 2008 NCOIC - All Rights Reserved
The NIF™ Process in Four Documents
assists
customers in obtaining
interoperable solutions
The NIF™ Process in Four Documents
Requirements
Requirements
Scopeand
andProblem
ProblemStatement
Statement
NIF
NIF™™Scope
Deliverable(NSPS)
(NSPS)
Deliverable
Definesthe
theScope
Scopeofofthe
theNIF
NIF™™
• • Defines
Definesthe
theInteroperability
InteroperabilityProblem
ProblemSpace
Space
• • Defines
Definestop
toplevel
levelrequirements
requirementsfor
forinteroperability
interoperability
• • Defines
SolutionDescription
Description(NSD)
(NSD)
NIF
NIF™™Solution
Solution&&Guide
Guide
Solution
ReferenceManual
Manual(NSD-RM)
(NSD-RM)including
including
• • Reference
OverarchingInformation
Overarching
Information(meta)model
(meta)model
oriented
• • User’s
User’sGuide
Guide(NSD-UG)
(NSD-UG)with
withgeneral
generaluser
useroriented
NIF™™guidelines
guidelines&&rules
rulesfor
forarchitecting,
architecting,
NIF
includingFully
FullyDocumented
DocumentedExample
Example
including
Main
Industry
and
Customer
Interest
Approachand
andRationale
Rationale(NAR)
NIF
NIF™™Approach
(NAR)
Rationale
Rationale
Examinesalternatives
alternativesfor
foraaparticular
particularsolution
solution
• • Examines
space
space
Definescriteria
criteriafor
forinteroperability
interoperabilityand
andnet-centricity
net-centricity
• • Defines
Makesrecommendations
recommendationsfor
foraasolution
solutionset
setbased
based
• • Makes
onthe
thecriteria
criteria
on
Copyright2008
2008NCOIC
NCOIC- -All
AllRights
RightsReserved
Reserved
©©Copyright
14
The Process
in Action
assists
customers
in obtaining
interoperable solutions
The Process in Action
Operational
Subject Matter
Expert
Technical
Subject Matter
Expert
Enterprise/System
Architect
NCOIC
Customer
Operational
Analysis
NCO
Requirements
NCOIC
Focus:
Net-Centric
Interoperability
Architectural
Analysis
Overarching
Architecture
Specs
™
Integrated Project IPTs, NIF
NIF™
Teams (IPTs)
OverArching
SCOPE Model
Framework
© Copyright 2008 NCOIC - All Rights Reserved
Technical
Analysis
Technology
Guidance
IPTs, Specialized
Frameworks
15
Operational Analysis
assists
customers in obtaining
interoperable solutions
Operational Analysis
Operational SME
NCOIC
Customer
Enterprise
Context,
Organization,
Assets &
Missions
NCOIC
focus
Operation
al
Standards
Operational
Analysis
Operational
Description
SCOPE dimensions
NCO Scenarios & Use Cases
NCO Capabilities & KPPs
NCO Views and Patterns
Domain
(or Operational)
Patterns
IPTs, SCOPE
16
© Copyright 2008 NCOIC - All Rights Reserved
Architectural
Analysis
assists
customers
in obtaining
interoperable solutions
Architectural Analysis
“Generalization”
Enterprise/System
Architect
NCOIC
Customer
Operational
Description
NCOIC
focus
Architectural
Analysis
NetCentric Services, Principles,
Tenets, Architecture Patterns,
Architecture Standards and
Technology Forecasts, Risks
OverArching
Architecture
Description
Capability
Patterns
Architecture
Standards
IPTs using NIF™ OverArching Framework artifacts
17
© Copyright 2008 NCOIC - All Rights Reserved
Technical
Analysis in obtaining
assists
customers
interoperable solutions
Technical Analysis
“Specialization”
Technical SME
NCOIC
Customer
OverArching
Architecture
Description
Technical
Analysis
Technical
Description
Technical Services
Principles, Tenets
Technical Standards &
Forecasts
NCOIC
focus
Technical
Standards
IPTs and Specialized Frameworks
(SF) using NIF™+SF artifacts
© Copyright 2008 NCOIC - All Rights Reserved
Technical
Patterns
18
Framework, Process, and Patterns
assists
customers in obtaining
interoperable solutions
Framework, Process, and Patterns

The Overarching Framework contains:
– Concepts: necessary knowledge definitions, dictionaries,
ontologies, information models, etc.
– Processes: Top-down, Bottom-up, & Middle-out
– Principles: overall requirements, goals, tenets, and best
practices that foster net-centricity
– A construct for developing guidance for solving Operational and
Technical problems for a given context
 The latter is a template for NCOIC Patterns
– These Patterns are not contained in the NIF™
– Patterns are stored in an online Repository
– Patterns provide guidance for creating systems with the desired
net-centric capabilities and mitigate specific net-centric
interoperability problems
19
© Copyright 2008 NCOIC - All Rights Reserved
Basis for Patterns
assists customers in obtaining
interoperable solutions
Basis for Patterns




Christopher Alexander, Civil Engineering Architect
– Described architecture patterns for civil engineering
“Design Patterns: Elements of Reusable ObjectOriented Software”
– Book by Erich Gamma, Richard Helm, Ralph Johnson,
and John M. Vlissides (the Gang of Four)
Successful pattern stories:
– J2EE & Microsoft .NET Patterns (software)
– DIACAP-compliant Security Patterns (secure design)
Key foundation for NCOIC Patterns:
– Systems Architecture Patterns (Cloutier & Verma)
20
© Copyright 2008 NCOIC - All Rights Reserved
Characteristics
of ain
Systems
Architecture Pattern
assists
customers
obtaining
interoperable solutions
Characteristics of a Systems Architecture Pattern

A Systems Architecture Pattern is a high-level
structure, appropriate for the major components of
a system. It expresses the relationship between:
– The Context
– A Problem
– A Solution

A Systems Architecture Pattern Documents:
– Attributes
– Usage Guidance
 Patterns are time-proven in solving problems
similar in nature to the problem under
consideration
Extracted from “Applying the Concept of Patterns to Systems Architecture”
by Robert J. Cloutier and Dinesh Verma, Stevens Institute of Technology,
Systems Engineering DOI 10.1002/sys
© Copyright 2008 NCOIC - All Rights Reserved
21
NCOIC Patterns
Focus
on Net-Centric Interoperability
assists
customers
in obtaining
interoperable solutions
NCOIC Patterns Focus on Net-Centric
Interoperability


Finding a PATTERN of
Net-Centricity amongst
all of the apparent
conflict & noise
Subject Matter Experts
often independently
arrive at similar
solutions
(a painful process!)
22
© Copyright 2008 NCOIC - All Rights Reserved
Three Major Categories of NCOIC Patterns
assists
customers in obtaining
interoperable solutions
PATTERNS OF NET-CENTRIC INTEROPERABILITY
Three Major Categories of NCOIC Patterns

Operational (or Domain) Patterns
– Top level approaches to addressing domain or Customer
Capability needs
• Identifies associated Capability Patterns
• Example: Sense & Respond Logistics Total Asset Visibility
 Capability (or Composite or Application) Patterns
– One or more for each of the areas identified above
– Describe an approach to achieving a particular capability
need in the context of the domain
• Identifies associated Technical Patterns
• Example: Legacy Systems Integration

Technical Patterns
– Specific approaches to solving a given technical need
identified in the Capability Patterns
• Example: Web Services
© Copyright 2008 NCOIC - All Rights Reserved
23
Pattern Relationships
assists
customers in obtaining
interoperable solutions
Pattern Relationships
NOTIONAL
EXAMPLE
OPERATIONAL
DOMAIN “A”
NIF™ v1
Operational
Description
(OD)
OPERATIONAL
DOMAIN “B”
Composite Pattern
CAPABILITY
PATTERN 1
CAPABILITY
PATTERN 2
CAPABILITY
PATTERN 3
CAPABILITY
PATTERN 4
NIF™ v1
PFC?
TECHNICAL
PATTERN
“A”
TECHNICAL
PATTERN
“B”
TECHNICAL
PATTERN
“C”
TECHNICAL
PATTERN
“D”
*
TECHNICAL
PATTERN
“E”
NIF™ v1
Global Attribute
© Copyright 2008 NCOIC - All Rights Reserved
TECHNICAL
PATTERN
“F”
TECHNICAL
PATTERN
“G”
24
Anatomy of a NCOIC Pattern
assists
customers in obtaining
interoperable solutions
Anatomy of a NCOIC Pattern
 Captures domain knowledge from Subject Matter

Experts (SMEs)
Not just about Standards
– Includes mature solutions to a given domain problem
 Includes best standards to apply to a problem

– Goes beyond the standards to include practical guidance
as to how to implement the standards
– Guidance oriented toward obtaining consistent results
Flexible/Extensible solutions to a genre of
problems
– Not a specific recipe for a solution to a specific problem
25
© Copyright 2008 NCOIC - All Rights Reserved
Anatomy of a NCOIC Pattern (Continued)
assists
customers in obtaining
interoperable solutions
Anatomy of a NCOIC Pattern
(Continued)

An NCOIC Pattern also contains:
– Identity
– Purpose (context and applicable scenarios)
– Description
• Architectural implementation, interfaces, applicability,
known uses, maturity metrics, etc.
• Relationships to other required/associated patterns
– Verification
• Showing that the Pattern complies with NIF™
(and Specialized Framework) guidance
– Conformance
• How to verify conformance of Building Block components
to the Pattern
– Tailoring
• Guidance of how to apply/adjust to various domains
© Copyright 2008 NCOIC - All Rights Reserved
26
Relationship of the NIF™ to Other NCOIC Tools
assists
customers in obtaining
interoperable solutions
Relationship of the NIF™ to Other NCOIC Tools
Customer
Goals
Missions to
Achieve Goals
NCO Initiatives
Database
Mission
Needs
Solutions to
Needs
1.
2.
3.
4.
Resulting
Services
Analysis of Alternatives
Requirements Derivation
Requirements Validation
Design Synthesis
SCOPE Model
NIF ™
NCOIC
Interoperability
Framework
5.
6.
7.
8.
BB
NCAT ™
Building
Blocks
Net Centric
Analysis
Tool
End-to-End
Quality of
Service
Design Verification
Deployment
Support
Upgrade/Disposal
Modeling/simulation
Test/evaluation
© Copyright 2008 NCOIC - All Rights Reserved
27
Relationship of the NIF™ to Other NCOIC Activities
assists
customers in obtaining
interoperable solutions
Relationship of the NIF™ to Other NCOIC Activities

Relationship of the NIF™ to:
– NCOIC Integrated Project Teams (IPTs)
• Provides process guidance for IPT development and
update of NCOIC Patterns
– NCOIC Functional Teams (FTs)
• Provides process guidance for FT development and
update of Technical Patterns
– External Standards-setting bodies
• Potentially identifies gaps in existing Standards and
desirable enhancements to existing and new
Standards
• Note: the NCOIC is not a standards-setting body!
28
© Copyright 2008 NCOIC - All Rights Reserved
NIF™ Summary
assists customers in obtaining
interoperable solutions
NIF™ Summary
Break through the
Technical Maze
Reach the Reward of
Interoperable Systems
29
© Copyright 2008 NCOIC - All Rights Reserved
assists customers in obtaining
interoperable solutions
NCOIC Goals
NCOIC Goal
30
© Copyright 2008 NCOIC - All Rights Reserved