System Engineering Tools for Interoperability Testing p y g Use of Advanced System Engineering Techniques For System of Systems Test Environment F. C. Alvidrez MTSI MTSI - Edwards AFB Ed ards AFB
Topics • Background, Introduction & Acknowledgements • Why are we here? – Transformation & the Growth of NetCentric Warfare – Growth of NetCentric Warfare – System of Systems Engineering • SE Approach to Testing – Phases – Tools • Interoperability Test Requirements (an example) – Integrated Architectures – NR-KPPs – DISA & JITC • Summary
Background & Introduction • Some Acknowledgements Some Acknowledgements – DAU – DISA (Def Info Sys Agcy) ( y g y) – DoDAF Working Group – OMG – INCOSE SD – MagicDraw • Some Caveats S C t – Not an official USAF or USG presentation – All Material is available on line through DAU, DISA, All Material is available on line through DAU DISA and other public DoD Sources
The Warfighters Perspective Interoperability V I R I O R I A B T U C S I M M V V A A R R I I If you are not interoperable, you areÉ Not on the net N Not contributing ib i Not benefiting Not part of the information age information age Not part of the Source: USN War College NetCentric Warfare Presentation
How did we get here? • Moore’s Law • Metcalf’s Law • The Fall of the Berlin Wall • 9-11 & GWOT • Katrina
What Our Leaders Say • “The National Defense Strategy clearly states how we gy y will operate in the future – we will be net-centric. Our job is to deliver the critical enabling capability to conduct network-centric operations.” p • “Defense transformation hinges on the recognition that information is our greatest source of power. We can leverage information to allow decision makers at all leverage information to allow decision makers at all levels to make better decisions faster and sooner.” — John G Grimes Assistant Secretary of Defense for John G. Grimes, Assistant Secretary of Defense for Networks and Information Integration, and DoD CIO, March 2006
What is the Problem? • Not doing well as a community (acquisition) – 95 Major Program exceeded the original budgets by$295B and 95 Major Program exceeded the original budgets by$295B and were delivered almost 2 years late on avg.* – Biggest shortfalls – lack of knowledge in technology maturity (risk management) design stability (requirements) and production management), design stability (requirements) and production maturity. – Getting worse, “It’s taking longer and costing more.” • New paradigm of System Engineering thought: N di f S t E i i th ht – Interoperability / System of Systems Engineering – NetCentric Enterprise • Just a better way of thinking – Model Based System Engineering – Thinking out of the box and using better tools Thinking out of the box and using better tools * Source: Washington Post April 1, 2008, GAO Article
Thought for the day “Any intelligent fool can make things bigger and more complex... things bigger and more complex... It takes a touch of genius --- and a lot of courage to move in the opposite direction.” pp G id Guidance for SoS SE’s? f S S SE’ ?
Interoperability Concept OV-1 O Source: DARPA J-UCAS 2004
DoD Architecture Framework Purpose & Scope • Provide guidance on describing architectures architectures – Warfighting Operations – Business Operations & Processes • Provides guidance, rules & product descriptions for developing and presenting “Integrated” architectures Integrated architectures • Defines three views – Operational View Operational View – System View – Technical Standards
Type of Problems for Test • Interoperability - Systems work at the Interoperability Systems work at the subsystem level but do not work when in an operational environment • Integration problems with legacy systems - Systems work but interfere with legacy systems such as IFF, TACAN or Defensive Avionics • Lack of NetCentric & Interoperability Test expertise for early Test Planning - i f l T Pl i
Why DoDAF and Interoperability Test? • Increasing NetCentric upgrades and modifications since g pg 9/11 (actually starting after Iraq 1) • Link-16, FAB-T, B-1B FIDL, B-52 CONECT, B-2A EHF, etc., t • Requirement to shorten the “Kill Chain” and to increase Situational Awareness Situational Awareness • Interoperability is about Integrated Architectures • DoDAF is the language of Integrated Architectures in DoD • DoDAF Integrated Architectures is the blueprint for Interoperability Test Requirements Interoperability Test Requirements
The Linkages Between Views Source: DoDAF Ver. 1
Analyzing DoDAF Products and Relationships 2 AVs 2 AVs 9 OVs 9 OVs 16 SVs 16 SVs 16 SVs 16 SVs 2 TVs 2 TVs
When to Start the Process
Interoperability Governance
Timeline for Planning Integrated Interoperability Architectures Tests in Place in Place
Timing and Interoperability Full Interoperability DoDAF Integrated Architectures Demonstration (JITC Certification) Initial SE Requirements Critical Test Planning
Critical DoDAF Products for Interoperability Test SV-1 SV-6 TV-1 OV-5 OV-1 SV 2 SV-2 OV-2 OV-3 CONOPS
Example OV-1 OV-1 O Source: DARPA J-UCAS 2004
Example OV-2
Summary • Interoperability modifications and upgrades are increasing • Interoperability is System of Systems Engineering • Interoperability Testing has special considerations (other nodes and players) (other nodes and players) • “New Think” needed – get out of the box completely • DoDAF Architectures are required in all phases of Interoperability Testing (TES - TEMP - Flight Test Plan - JTIC Certification) • Recommendation – Concerted effort by the SE Community of Practice to re-think it’s role in the new Interoperable paradigm new Interoperable paradigm
Important References • DAU NR-KPPs Web Course (CLM 029) DAU NR KPPs Web Course (CLM 029) • DAU Fundamentals of Test & Evaluation Web Course (TST 102) ( ) • DISA / JITC • (http://www disa mil/index html) / (http://www.disa.mil/index.html) / (http://jitc.fhu.disa.mil/jitc_dri/jitc.html) • DARS – DoD Architecture Repository S o c tectu e epos to y System (https://dars1.army.mil/IER/welcome.jsp) • GAO Report on Major Acquisitions 2008
Recommend
More recommend
