NCOIC Interoperability Framework (NIF ) and NCOIC Patterns Overview

Transcription

1 Network Centric Operations Industry Consortium NCOIC Interoperability Framework (NIF ) NCOIC Interoperability Framework (NIF ) and NCOIC Patterns Overview and NCOIC Patterns Overview August 2008 Approved for Public Release NCOIC-NIF Overview Copyright 2008 NCOIC - All rights reserved

2 About NIF Customer Goals Missions to Achieve Goals Mission Needs Solutions to Needs Resulting Services NCO Initiatives Database SCOPE Model NIF Provides enabling guidance for net-ready solutions -Overarching framework - Specialized frameworks - Pattern template Modeling/simulation NIF 1. Analysis of Alternatives 2. Requirements Derivation 3. Requirements Validation 4. Design Synthesis BB 5. Design Verification 6. Deployment 7. Support 8. Upgrade/Disposal NCAT NCOIC Building Net Centric Interoperability Blocks Analysis Framework Tool End-to-End Quality of Service Copyright 2008 NCOIC - All Rights Reserved Test/evaluation 2

3 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

4 Standards Alone are not Sufficient Need Guidance Standards Alone Are Not Sufficient Need Guidance Performance A Performance C Standard D Standard A Standard C Standard B Standard E Standard F Often the BEST Standard depends on the Mission Real-World Condition! Often no One Size Fits All Performance B Requires Guidance to select Consistent Standards by Class of Missions: very hard to do! (but a key goal of the NIF ) 4

5 Guidance re: Mission 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* Transfer Rate* Standard A attribute range For Technology X Standard B attribute range For Technology X Net Awareness* Different Standards because Different Mission Domains have Different Needs! Security* * Examples of SCOPE dimensions, actual dimensions are more comprehensive Autonomy* Power* Service Orientation* 5

6 Notional Cost (or Risk) Guidance re: Level of NCO Guidance re: Level of NCO What is the appropriate level of NetCentricity for a given operational context? May impact selection of Standards! Which is the Best Standard for this hypothetical operational context? This example is time-based; many other perspectives! Standard A For Technology X Standard B For Technology X Today s Range of required performance Future Range of required performance Notional Performance Copyright 2008 NCOIC - All Rights Reserved 6

7 % A-to-B Interoperable Copyright 2008 NCOIC - All Rights Reserved assists Example: customers Notional Intended in obtaining Span of Standard Example: Notional Intended Span of Standard Notional Intended Span of Standard SYSTEM A Extension: Added Highly-Desirable Range 100% Interoperable 100% Interoperable SYSTEM B Extension: Added Highly-Desirable Feature 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

8 % Versions Interoperable Copyright 2008 NCOIC - All Rights Reserved assists Guidance customers re: Versions in obtaining Guidance re: Versions ORIGINAL Standard v1.0 UPDATED Standard v1.1 NEW Standard v2.0: Backward Compatible 100% all 3 versions Interoperable 100% v1.1 & 2.0 Interoperable V1.0 & v2.0 V1.1 & 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

9 % Interoperable Copyright 2008 NCOIC - All Rights Reserved Guidance re: Standards Interpretations Guidance re: Standards Interpretations Interpretation A of Standard 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

10 Layers of Interoperability Copyright 2008 NCOIC - All Rights Reserved assists Interdependency customers of in Standards obtaining Interdependency of Standards Political or Business Objectives Harmonized Strategy/Doctrines Aligned Operations Aligned Procedures Knowledge/Awareness of Actions Semantic/Information Interoperability Data/Object Model Interoperability Connectivity & Network Interop. Physical Interoperability People & Processes & Applications Information Services Network Transport Standards are Interdependent! Standards for a layer of Interoperability often dependent on standards for lower layers COI Standard C2 Application Standard Web Services Standard Radio Standard COP Standard IPv6 Standard KM Standard Pub / Sub Standard LAN Standard 10

11 Guidance must be CLEAR and Straightforward! Guidance must be CLEAR and Straightforward! 11

12 assists The Value customers of the NIF in obtaining Approach 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

13 assists Intended customers Users of the in obtaining NIF 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

14 Copyright 2008 NCOIC - - All All Rights Reserved The NIF Process in Four Documents The NIF Process in Four Documents Requirements Solution & Guide NIF Scope and Problem Statement Deliverable (NSPS) Defines the Scope of of the NIF Defines the Interoperability Problem Space Defines top level requirements for interoperability NIF Solution Description (NSD) Reference Manual (NSD-RM) including Overarching Information (meta)model User s Guide (NSD-UG) with general user oriented NIF guidelines & rules for architecting, including Fully Documented Example Main Industry and Customer Interest Rationale NIF Approach and Rationale (NAR) Examines alternatives for a a particular solution space Defines criteria for interoperability and net-centricity Makes recommendations for a a solution set based on on the criteria 14

15 assists The Process customers in Action in obtaining The Process in Action Operational Subject Matter Expert Enterprise/System Architect Technical Subject Matter Expert NCOIC Customer Operational Analysis Architectural Analysis Technical Analysis NCOIC Focus: Net-Centric Interoperability NCO Requirements Integrated Project Teams (IPTs) SCOPE Model Overarching Architecture Specs IPTs, NIF OverArching Framework Technology Guidance IPTs, Specialized Frameworks 15

16 Operational Analysis Operational Analysis Operational SME NCOIC Customer NCOIC focus Enterprise Context, Organization, Assets & Missions Operation al Standards IPTs, SCOPE Operational Analysis SCOPE dimensions NCO Scenarios & Use Cases NCO Capabilities & KPPs NCO Views and Patterns Copyright 2008 NCOIC - All Rights Reserved Operational Description Domain (or Operational) Patterns 16

17 assists Architectural customers Analysis in obtaining Architectural Analysis Enterprise/System Architect Generalization NCOIC Customer NCOIC focus Operational Description Architecture Standards Architectural Analysis NetCentric Services, Principles, Tenets, Architecture Patterns, Architecture Standards and Technology Forecasts, Risks OverArching Architecture Description Capability Patterns IPTs using NIF OverArching Framework artifacts 17

18 assists Technical customers Analysis in obtaining Technical Analysis Technical SME Specialization NCOIC Customer NCOIC focus OverArching Architecture Description Technical Standards Technical Analysis Technical Services Principles, Tenets Technical Standards & Forecasts IPTs and Specialized Frameworks (SF) using NIF +SF artifacts Copyright 2008 NCOIC - All Rights Reserved Technical Description Technical Patterns 18

19 Framework, Process, and Patterns 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

20 Basis for Patterns Basis for Patterns Christopher Alexander, Civil Engineering Architect Described architecture patterns for civil engineering Design Patterns: Elements of Reusable Object- Oriented 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

21 assists Characteristics customers of a in Systems obtaining Architecture Pattern 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 /sys Copyright 2008 NCOIC - All Rights Reserved 21

22 assists NCOIC Patterns customers Focus in obtaining on Net-Centric Interoperability 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

23 PATTERNS OF NET-CENTRIC INTEROPERABILITY Three Major Categories of NCOIC Patterns 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

24 Pattern Relationships Pattern Relationships NOTIONAL EXAMPLE OPERATIONAL DOMAIN A OPERATIONAL DOMAIN B NIF v1 Operational Description (OD) 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 TECHNICAL PATTERN F TECHNICAL PATTERN G NIF v1 Global Attribute 24

25 Anatomy of a NCOIC Pattern 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

26 Anatomy of a NCOIC Pattern (Continued) 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

27 Relationship of the NIF to Other NCOIC Tools Relationship of the NIF to Other NCOIC Tools Customer Goals Missions to Achieve Goals Mission Needs Solutions to Needs Resulting Services SCOPE Model NCO Initiatives Database NIF 1. Analysis of Alternatives 2. Requirements Derivation 3. Requirements Validation 4. Design Synthesis NCOIC Interoperability Framework BB Building Blocks NCAT Net Centric Analysis Tool End-to-End Quality of Service Modeling/simulation 5. Design Verification 6. Deployment 7. Support 8. Upgrade/Disposal Test/evaluation 27

28 Relationship of the NIF to Other NCOIC Activities 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

29 NIF Summary NIF Summary Break through the Technical Maze Reach the Reward of Interoperable Systems 29

30 NCOIC Goals NCOIC Goal 30