1. DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. Joint Common Architecture Demonstration Lessons Learned – Sikorsky/Boeing Perspective Presented by: Scott Wigginton Bill Kinahan US Army AATD Sikorsky Aircraft

2. DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. Introduction 2 Problem Complexity of avionics software increasing exponentially 70% of new aircraft development cost is software Key Initiatives Future Airborne Capability Environment (FACE TM ) Consortium Joint Common Architecture (JCA) Reference Architecture Model Based Engineering JCA Demonstration Objectives Exercise FACE standard, guidance and tools Validate JCA concept Reduce risk for follow-on efforts Approach Procure single software component from multiple vendors Integrate on two undisclosed Operating Environments (OEs) Limit interaction between developer & integrator

3. DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. JCA Demonstration 3 Developer Scope Data Correlation and Fusion Manager (DCFM) component –FACE Unit of Portability (UoP) Reusable Verification Component (RVC) Utilize FACE tools for development Submit verification evidence for FACE Conformance Solicitation Model-driven acquisition approach –Interface specified as a data model and interaction diagrams –Minimal set of functional requirements –Utilized draft FACE Contract Guide Sikorsky/Boeing selected for Technology Investment Agreement Processes, tools, and lessons learned were more important than component performance

4. DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. Technical Approach 4 Data Correlation and Fusion Manager –Functionality from existing Cohesion software product –Software interface layer that conforms to FACE Standard Reusable Verification Component developed as FACE UoP Primary development on Linux with ARINC-653 Simulator –Also ported to three additional supplier provided OEs Formation Flight UoP for timing

5. DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. Cohesion product design to be portable Interface layer adapted to Transport Service API and data model Minor content issues with data model required correction Behavioral was insufficiently specified in interaction diagrams Other minor changes due to reduced API set in Safety profile Data Correlation and Fusion Manager 5

6. DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. Reuse of Existing Software Adapted to FACE profile APIs Adapted to FACE Data Model –Supplied DCFM data model didn’t fully exploit Cohesion capability Portability and Reuse across Systems Clearly demonstrated ability to port to other operating environments Integrated on three additional OEs with different transport services DCFM and RVC UoPs unchanged Transport services implementations were environment specific Substitution of One UoP for Another Sikorsky/Boeing did not attempt to swap DCFM UoP with alternative Challenges exist with current limitations to model-based approach to interface specification –FACE Data Model does not currently support behavioral interactions –Doesn’t reveal architectural problems (e.g. can other components modify the list of correlated tracks) 6 Software Reuse

7. DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. Candidate FACE Tools FACE IDL Compiler used to generated header files from DCFM data model FACE Conformance Test Suite used to generate test results FACE Modeling Tools used to generate data model for Formation Flight UoP Contracts Officer exercised the FACE Library Portal for registration Verification Activities Iterative and incremental process to interact with Verification Authority (VA) –Preliminary evidence – Source code, documentation, test results –Initial – Addressed VA comments, inspection based verification steps –Final – Resolution of open items, Final conformance statement and verification matrix Conformance was not achieved due to Army provided data model Known issues due to timing of the Shared Data Model release Recommended improvements to process and clarification of requirements Dispute over allowance of exception handlers in Safety profile 7 Additional Activities

8. DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. System Model Created DCFM UoP Data Model RVC UoP Data Model Connectivity between RVC and DCFM ports RVC Data Model based on DCFM Message definitions are the same Adds entities specific to testing FACE Ecosystem Tools used to auto-generate data types and transport services implementation Test Cases Modeled in AnyCASE Test cases specified as series of steps –Set, Verify, Log, etc. Created instances of entities to be modified/examined by test case steps Provided mechanism to trace test cases to requirements 8 Reusable Verification Component

9. DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. Key elements of the RVC architecture Entity instances to hold current state of test environment Test cases embodied in sets of C++ objects Application specific versions of I/O and simulation functions. Periodic loop providing primary execution structure High percentage of RVC code automatically generated from test case model. 9 The architecture of the RVC is itself reusable! This same approach can be used in testing any FACE portable component Reusable Verification Component

10. DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. 10 Test Case Meta-Model Range of step types Essential Automated Testing Behavior Application Specific Automated Testing Behavior Reusable Verification Component

11. DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. System Integration 11 ARINC-653 Emulator –Compiler issues –Verified initial operation using RVC Integration –Minor issues encountered Compiler issues Ecosystem TSS TSS parameters Lack of FACE conformant RTOS –Process improved by using FACE tools Test –Functional tests on emulator via RVC RVC on target OEs desired –System level tests passed on both OEs Demonstration –Utilized common scenario –Successfully demonstrated on both OEs –Successfully demonstrated component replacement on both OEs Operating Environment 1 -PowerPC ® 7447 dual processors -WindRiver ® VxWorks ® 653 2.3.0.1 -1GB RAM, 64 GB Storage Operating Environment 2 –Intel ® Xeon ® dual-core processor –LynuxWorks ® LynxOS ® -178 2.3 –1GB RAM, 4GB Storage

12. DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. Model-driven acquisition approach showed potential benefits –FACE tools demonstrated potential for modeled interfaces –Data model described composition of entities and their properties –Gaps remain for fully defining components (behavior, arch) –Model may constrain existing software functionality FACE Data Model is maturing FACE Standard provided independence from underlying platform and transport paradigm to enable portability to multiple disparate OEs RVC as FACE UoP was effective FACE Transport latencies were insignificant (~5 µs) Engage FACE VA early Conclusions 12 Quality of the lessons learned highlighted importance of maturing FACE standard and JCA concept through representative acquisition processes

13. DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. ACRONYMS 13 ACRONYMDEFINITION AATDArmy Aviation Test Directorate APIApplication Programming Interface AMRDEC Aviation and Missile Research Development Engineering Center ATWAll Terrain Warning APR39DRadar Warning Receiver BAABroad Agency Announcement BFTBlue Force Tracker CTSConformance Test Suite DCFMData Correlation and Fusion Manager EGIEmbedded GPS INS FACEFuture Airborne Capability Environment GPSGlobal Positioning Satellite IDKIntegrators Development Kit INSInertial Navigation System IOInput Output ITKIntegrators Toolkit JCAJoint Common Architecture JMRJoint Multi Role MMPMulticore Mission Processor ACRONYMDEFINITION OEOperating Environment PSSS Platform Specific Services Segment RTOSReal Time Operating System RDECOM Research Development and Engineering Command RVCReusable Verification Component SASituational Awareness SADMSA Data Manager SDKSoftware Development Kit SILSystem Integration Laboratory SWSoftware TSTransport Services TSSTransport Services Segment UoPUnit of Portability VAVerification Authority