TEST I VIDAREUTVECKLINGEN AV GRIPENS AVIONIK- OCH MARKSTÖDSYSTEM

Transcription

1 TEST I VIDAREUTVECKLINGEN AV GRIPENS AVIONIK- OCH MARKSTÖDSYSTEM Håkan Anderwall, Saab AB Jacob Gustafsson, Combitech

2 AGENDA! The Gripen weapon system an overview! Part 1: The Gripen Aircraft Computer System Scope what is done, what needs to be done, and why? Aircraft Computer System, IMA Architecture and System functions Verification and Validation methods and goals Test environments and Test architecture Automated Verification and Validation flow! Part 2: The Mission Support System (MSS) Description of the MSS system The test process, steps & content The build process Test methods and experience

3 THE GRIPEN WEAPON SYSTEM Gripen A/C Data Transfer Unit Mission Support System

4 A NEW AIRCRAFT COMPUTER SYSTEM IN GRIPEN! Why? Obsolescence issues for several equipments. Old development environment/tools, language. Software is not cost effective to maintain and add functionality in.! A new IMA architecture has been engineered More effective, allocate functions more freely among common computational resources. Focus on model based development, from models on entire aircraft and its hardware and software components and their interfaces, to design of applications and library functions. (Using Rhapsody, BridgePoint, Matlab/Simulink)! Re-implemented system functions requires re-verification/validation!

5 INTEGRATED MODULAR AVIONICS (IMA)! IMA is a shared set of flexible, reusable, and interoperable hardware and software resources that, when integrated, form a platform that provides services, designed and verified to a defined set of safety and performance requirements, to host applications performing aircraft functions.! Apart from Gripen, there are IMA systems also in Lockheed Martin F-22 and F-35, Dassault Aviation Rafale, and Airbus A350 and A380.! Guidance and certification aspects for the development of an IMA system is described in RTCA DO-297.

6 GRIPEN - ARCHITECTURE Navigation, Flight control, Communication systems etc. Flight Critical Functions IOP Flight Tactical Flight Critical Functions Critical Functions Functions IOP IOP IOP Flight Flight Displays Critical Critical Functions Functions IOP IOP IOP Head-up Display IOP Stores Functions IOP General Functions IOP Video Processing IOP Data Transfer IOP Navigation, Flight control, Communication systems etc.! Many new DCM s (Digital Computing Modules), each hosting two or more processors, using one of several new RTOSes supporting partitioning.! Re-implemented functions in (APlication Processor)! Kept interfaces to unchanged systems! A large amount of reverification/validation

7 SYSTEM FUNCTIONS, SOFTWARE LICATIONS! A set of DCM software applications and libraries performs a system function using the IMA platform.! Needs to verify all CSCIs (software components), system requirements and validate system functions. Display Partition Software Application Display_Server AGS (A661 Server) DCM Partition Software Application A Library Service (e.g. A661 Adapter) Sensor Symbolfile BIN Symbolfile BIN Actuator

8 THE OVERALL GOAL FOR VERIFICATION AND VALIDATION Stakeholder Requirements / contract Acceptance Test ~100% ref to SSS, SRS, and EqS verification results with analysis and justification Product requirements and functions Product VoV ~100% ref to SSS, SRS, and EqS verification results with analysis and justification Subsystem requirements and functions Software requirements (several levels) System integration tests Application/ Library/ Unit tests VoV Cost < 5% Aircraft Ground and Flight test ~15-20% System simulation, some automated ~10-30% Analysis ~50-70% Reuse SW and HW level verification Software 95% host/target breadboard test All tests fully automated Software 5 % Equipment test Hardware 100% Equipment vendor Code & Models Static code & model analysis Automated rules checking ~70% Manual rules checking ~30%

9 VERIFICATION METHODS - SOFTWARE! SW/SW Integration Tests Black-box verification of CSCI (Application, Library)! HW/SW Integration Tests Integration with hardware interfaces (mostly the platform CSCI:s).! Unit Tests Verification of Computer Software Units.! Analysis/Inspection Visual inspection of code or design. Static analysis of models and code where possible.

10 VERIFICATION & VALIDATION METHODS - SYSTEM! Analysis Analysis of design, specifications etc. of a systems ability to perform its intended functions.! Inspection Inspection of a system items fulfillment of required characteristics (e.g. emission, conformity to standards and regulations)! Test & Demonstration MySim SW verification (reused) Simulation (models) Flight Test / Ground Test Avionics Rig / Total System Rig! Service Experience Previous usage of subsystem/system

11 MySim! Desktop simulator for system development, and software development.! Validation of concepts.! Background mode: Automated execution of system integration test cases.

12 VERIFICATION AND VALIDATION AUTOMATION GOAL! Compile and link all tests for different test environments: MySim Automated system integration tests Solaris/Linux Host software integration and unit test, code coverage measured Target breadboard Target software integration and unit test, object code analysis Testrig with DCM Hardware/software integration test (incl. WCET)! Execute all possible tests automatically and evaluate: MySim, Host, Target breadboard Daily VoV result presentation how many test failed etc.?! Static code analysis against C/C++/Ada95 Coding Standards! Model consistency check of models against each tool Modeling Standard! Automated model code generation! DOORS checks Untested / changed requirements, traceability etc.?

13 Manual Partly automated Test environments (Applications and libraries) Automated Application/ Application integration Test in System Simulator (MySim) Application/ Platform integration Test in DCM (Rig) System Level Test in Models Quick feedback Test on Host Test on Target Processor (breadboard) CSCI Level Daily test of generated code Code coverage Automated tests enables quick regression testing! Collect evidence of the CSCIs requirements fulfillment No big surprises!

14 TEST ARCHITECTURE: BREADBOARD TEST CLUSTER! A set of breadboards for all DCM CPU architectures! Managed by a continuous integration server deploying test binaries per dedicated CPU architecture Flight Flight Critical Flight Functions Critical Functions Critical Functions Breadboard test server <<Get test result>> <<Send test binaries>> <<Send test results>> Continuous integration server Tactical Tactical Functions Tactical Functions Functions Tactical Tactical Functions Functions Displays <<Deploy and Execute>> Tactical Tactical Functions Video Functions Processing Head-up Display User network

15 AUTOMATED VERIFICATION AND VALIDATION FLOW CI server: sw test Host test report Check-out, compile, link, execute *.atr *.ctr *.log Accumulated code coverage Target test Check-out, cross compile, link target breadboard report Execute *.atr *.ctr *.log CI server: system integration test MySim test Check-out, compile, link, execute report *.log Post process report files transform transform & present xml test summary Test Page Summary CI X Pass transform *.csv import (manual) DOORS SSTD module DOORS SVC module

16 MISSION SUPPORT SYSTEM (MSS) Content! MSS and its vital role in the tactical loop! The different test steps and phases! The build & installation process! Experience from different test methods

17 MISSION SUPPORT SYSTEM (MSS) Scope of Functionality! Planning missions objectives and routes for Gripen missions! Loading planned data to the aircraft! Loading flown data from the aircraft! Analysis and replay of the flown missions! Functionality for mission simulations! The functionality is vital to achieve mission success

18 MISSION SUPPORT SYSTEM (MSS) Data loading overview Digital Maps Library data DTU-P Communication Data MMC Order, Intelligence, Weather & Reports MSS Mission Support System

19 MISSION SUPPORT SYSTEM (MSS) TACTICAL INFORMATION HANDLING Intelligence Data Mission Report Data Support Map info Libraries Planning Configuration Navigation Communication Sensors Intelligence Updates Evaluation Mission Replay including Flight path Events Cockpit Rehearsal Scenario Simulation Preparation Data Libraries Navigation data Other data Recorded Data Flight Path Events Audio/Video Mission Analysis Image Analysis 3D View Settings DTU-P MMC Cockpit panels Audio & Video

20 MISSION SUPPORT SYSTEM (MSS) Test phases (performed weekly) Sanity & integration testing Requirement tests Performed in steps throughout the development Early feedback Load on target for further testing System test Validation test System Level Automatic build of the code Early feedback Load on host for development Development tests (unit & functionality) CSCI Level

21 TEST ACTIVITIES Type of test Responsible Definition Code analysis Development team Code analysis to find initialized variables, false pointers etc. Unit test Development team Development test in parallel with the implementation Functional test Development team Functional tests of the implemented code Integration test Development team Tests in the teams to early assure correct integration between components Sanity test Common test team Short up & running test of the complete product Integration test of complete product Common test team Integration test performed weekly & every sprint (3 weeks) to assure that the integration of the complete product is correct System test Development team Contractual requirement tests with validation perspective Dry Run & Cust Demos Common test team Customer demos to present the system Validation test Common test team Final test with validation perspective

22 MISSION SUPPORT SYSTEM (MSS) Testing characteristics! The amount of automatic unit testing is increasing. Time consuming for old code as it requires much effort! Still a large amount of manual testing! Integration testing on target is tested from a user point of view. Uses several simulation tools to verify interfaces! GUI testing of the integrated product has not been successful. Tricky to develop and requires a lot of under haul during development! System & final testing is performed with a validation perspective in order to assure customer satisfaction according to contractual requirements

23 MISSION SUPPORT SYSTEM (MSS) Build overview buildscripts code repository jenkins.h.cpp svn gcc test lab installation files installations.iso.rpm.exe test results unit tests code analysis

24 MISSION SUPPORT SYSTEM (MSS) Build process & installation The build process is automatic and serves many advantages:! Enables quick response & support to developers. Host system environment is similar to the target environment! Easy to switch between customer configurations on host machines! The code is built automatically once checked in! Build results are distributed to the development teams! Several customer configurations are built over night! Unit tests are run automatically as regression tests with distributed results! Installation requires little manual effort and will be performed automatically

25 MISSION SUPPORT SYSTEM (MSS) Test methods & experience! Team organized versus functional organisation! Used to have separate teams for integration & system testing! Intended to shorten development time and increase quality! Team organisation: Resulting in many faults discovered late in the development process Somebody else tested the development teams implemented functionality Development teams relied on the test teams to find faults Unless good communication, the test teams were not fully updated on what s new! Functional organisation: The teams are responsible for a wider functional scope The testers are located in the development teams The testers know exactly which functionality that is under development Integration tests are performed earlier in the development phase Test cases are developed with a widened content

26 GRIPEN Contact Håkan Anderwall Phone: MSS Contact Jacob Gustafsson Phone:

27