Integrated Architecture Development 28 Jan 2004 Brig Gen J. Maluda, USAF SIAP System Engineer Col H. Dutchyshyn, USAF Deputy SIAP SE CAPT Jeffery W. Wilson, USN Technical Director
UNCLASSIFIED SIAP system engineering . . . Getting everyone on the same sheet of music System A’s View Of The World System A’s View Of The World 303 306 3055N 01227 02547 2 observed; Only 1 real aircraft Not observed 3045N 8025W 8010W 7955W 7940W System B’s View Of The World System B’s View Of The World 306 1227 3055N 2547 303 Looks like a friendly, but it’s not 3045N 8025W 8010W 7955W 7940W 189-2 16 February, 2004
UNCLASSIFIED Joint Tactical BMC2 (today) Displays Displays Tactical Tactical BMC2 BMC2 Sensors Weapons Sensors Weapons Functionality Functionality Communication network Displays Displays Tactical Tactical BMC2 BMC2 Functionality Sensors Functionality Weapons Sensors Weapons Common functionality, implemented and maintained many ways 189-3 16 February, 2004
UNCLASSIFIED Joint Tactical BMC2 Joint Tactical BMC2 domain Data obtained from Data exchanged sources outside the among peers within Displays distributed system the distributed system Joint Tactical BMC2 Sensors Weapons System–specific Tactical BMC2 • Help is needed in identifying Service Combat and Command and controlling interface and Control System Program (e.g., system-specific Manager’s domain Tactical BMC2, sensors) 189-4 16 February, 2004
UNCLASSIFIED Joint Tactical BMC2 (future) Displays Displays Joint Tactical Joint Tactical BMC2 BMC2 Weapons Sensors Weapons Sensors System–specific System–specific Tactical BMC2 Tactical BMC2 Communication Network (and Enterprise Services) Displays Displays Joint Tactical Joint Tactical BMC2 BMC2 Weapons Weapons Sensors Sensors System–specific System–specific Tactical BMC2 Tactical BMC2 Common functionality, implemented and maintained commonly 189-5 16 February, 2004
UNCLASSIFIED Configuration Management Paper Integrated Architecture Standard(s) and Behavior Model Specification(s) (“Platform” Independent Model”) IA Repository • Gaps, overlaps, and conflicts • Unambiguous • Context-free • Described in context • Static • Dynamic • Syntax • Syntax and semantics • Strong typing Shift from static, paper artifact to dynamic behavior model Shift from static, paper artifact to dynamic behavior model 189-6 16 February, 2004
UNCLASSIFIED Integrated Architecture Behavior Model • Derived from JROC-validated requirements • Unambiguously describes dynamic system behavior in an open source model • Supports selection among alternative solutions • Delivered to program managers with verification/validation data and JDEP technical framework Idealized model of distributed system performance that shows Idealized model of distributed system performance that shows industry what “good” looks like – automates the standards industry what “good” looks like – automates the standards 189-7 16 February, 2004
UNCLASSIFIED Precepts Architecture Quality Attributes Outcomes Cornerstones • Continuous Readiness • Performance (functionality) • Reduce fratricide - Correctness • Sensor Netting • Employ weapons to - Efficiency design range • Battlespace Dominance - Completeness • Reliability • Counter existing and • Proven Lethality emerging threats - Survivability • Coordinated Weapon - Fault tolerance Employment - Openness • Scalability • Joint Command - Flexibility • Increased performance Support - Openness • Lifecycle cost avoidance • Information Assurance • Maintainability • Reduced time to field - Openness - Expandability new and modified - Testability capability • Safety • Security (Info. Assurance) - Survivability • Verifiability - Openness • Reusability and portability - Equipment and OS independence - Openness Source: IEEE-Std 1061- ISO Std 9126 MITRE Guide to Total Software Quality Control 189-8 16 February, 2004
UNCLASSIFIED Model Driven Architecture Object Oriented Analysis • Object oriented dynamic model “Platform” Integrated Independent • Characterize BMC2 behavior of Architecture Model Repository nodes in the distributed system • Precise, durable, repeatable Open Source • Subjected to rigorous consistency executable UML and conformance verification Block 1 Engineering Configuration Item Isolate functionality from specific implementation technologies allows Design for Change 189-9 16 February, 2004
UNCLASSIFIED Model Driven Architecture Machine “Platform” Implementation Testing Translation Specific Model “Platform” Integrated Independent Architecture A Reference Implementation Model Repository Block 1 Verification & Validation Engineering Targeted to High Level Architecture Run Time Infrastructure to support distributed development and test and evaluation Application Application HLA RTI HLA RTI Operating Systems Operating Systems Equipment Equipment 189-10 16 February, 2004
UNCLASSIFIED Model Driven Architecture “Platform” Implementation Testing Specific Model “Platform” Integrated “Platform” Independent Architecture Specific Implementation Testing Model Repository Model Block 1 Verification & Validation Engineering Example, targeted to specific industry standards (e.g., TAO, POSIX), based on individual system needs 189-11 16 February, 2004
UNCLASSIFIED Model Driven Architecture “Platform” Implementation Testing Specific Model “Platform” “Platform” Integrated Specific Implementation Testing Independent Architecture Model Model Repository “Platform” Specific Implementation Testing Block 1 Model Engineering Examples Examples • “Platform” independent model is inherently “open”, provides dynamic model of system behavior, and allows deferral of specific implementation technology decisions • HLA-compliant model demonstrates distributed system performance • One or more specific model(s) demonstrate distributed system performance in real system(s) 189-12 16 February, 2004
UNCLASSIFIED Verification and Validation Reference implementation “Platform” Communication Sensor(s) Weapon(s) Implementation Specific Server Model(s) “Derived from consistent and conformant HLA RTI HLA RTI HLA RTI “Platform” Independent Model Common Environment Data Reference Driver Extraction Scenario Driver Demonstrate Correctness of Distributed System Demonstrate Correctness of Distributed System 189-13 16 February, 2004
UNCLASSIFIED Implementation in tactical systems Conformance Tested “Platform” “Platform” Independent Specific Testing Model Model Machine (or manual) translation Verification and Validation by Consistent and done by System Program Managers conformant; System Program Managers; Joint built by joint (with help from joint consortium) Independent Verification and consortium Validation by JITC Being developed in collaboration w/ Industry, FFRDCs & Gov. PMs Being developed in collaboration w/ Industry, FFRDCs & Gov. PMs (e.g., Navy Open Architecture & Air Force’s E-10A/MC2A) (e.g., Navy Open Architecture & Air Force’s E-10A/MC2A) 189-14 16 February, 2004
UNCLASSIFIED Deliverables • One “Platform” Independent Model • Two or more example “Platform” Specific Model(s) - One HLA RTI-specific - At least one targeted to a specific communication environment and operating system • Reference Implementation(s) derived from “platform specific model(s) • Unit and integration test scripts and results (verification) • Validation test scripts and results • JDEP kit 189-15 16 February, 2004
UNCLASSIFIED Funding Strategies • Original Service estimates accounted for redundant development Pgm Mgt Test Design Code Int System A a b c d e f System B a b c d e f Common Total $ = System A + System B Block 0 & Block 1 • A change in business model should reduce total cost and help synchronize development Total $ = a + b + c + Ad + Bd + Ae + Be + Af + Bf New Method Pgm Mgt Int Test System A Design Code d e f a b c System B d e f Demands change in business model 189-16 16 February, 2004
UNCLASSIFIED The message • Integrated Architecture continues to be a key task force product • Integrated Architecture behavior model supports dynamic analysis and improved communication with industry • Approach changes configuration item(s) from paper specifications and standards to dynamic behavior model The Integrated Architecture provides the basis for The Integrated Architecture provides the basis for reducing development costs, reducing time required to reducing development costs, reducing time required to field new and modified capability, and increasing field new and modified capability, and increasing operational effectiveness operational effectiveness 189-17 16 February, 2004
Recommend
More recommend
