Date : 1 May 2007
Page : 1 /
EUROCONTROL EXPERIMENTAL CENTRE
Brétigny-sur-Orge, FRANCE
eCockpit
Technical Document
eDEP / eCockpit Integration Project Software Test Plan
Document Ref:eCockpit-XX-v0.11
Issue date: 1 May 2007
The information contained in this document is the property of the EUROCONTROL Agency and no part should be reproduced in any form without the Agency’s permission.
The views expressed herein do not necessarily reflect the official views or policy of the Agency.
Document Change LogRelease / Author / Date of the release / Description of the release / Modifications (sections affected and relevant information)
0.1 / Graffica / Initial Draft
0.2 / Graffica / WP2.2 Update / Test cases added to Section 5.2
0.3 / Graffica / WP2.2 Update / Updated following comments from EEC.
0.4 / Graffica / 01/10/04 / WP2.2 Update / Update test case specifications following CTS development.
0.5 / Graffica / 18/10/04 / WP2.4 Update / Added Section 5.3
0.6 / Graffica / 09/12/04 / WP2.5 and WP2.3 Update. / Added Sections 5.4 and 5.5
0.7 / Graffica / 08/02/05 / UDP Forwarding / Added section 5.5.5.
0.8 / Graffica / 11/02/05 / Added test for WP2.3. / Updated section 5.5.3
0.9 / Graffica / 21/10/05 / Added test for PWP/ECockpit / Added Section 5.6
0.10 / Graffica / 25/1/2007 / Added tests for Cat-21 messages. / Sections 5.3 and 5.5.
0.11 / Graffica / 2/2/2007 / Added tests for AVT ADSB validation trials. / Section 5.7
Acceptance and Reviewing Procedures
Name (s) / Date of acceptance/ review / Date of approval
Darren Smith
Mike Vere
Document distribution
to/cc / Name / Role
to / Tim Cooper / Graffica Technical Lead
to / Darren Smith / EEC Point of Contact for eCockpit
to / Leo van der Hoorn / AVT Project Manager
Table of contents
1.Introduction......
1.1Purpose......
1.2Document structure......
1.3Associated documentation......
2.project overview......
2.1Background......
2.2Development Process......
2.3Software & Software Testing......
2.4Project Milestones......
3.Process reviews......
3.1Testing and Review Processes......
3.1.1Design Reviews......
3.1.2Code Reviews......
3.1.3Unit Testing......
3.1.4Integration Testing......
3.1.5System Testing......
3.2Review Schedule......
3.2.1SSP3 – WP2.1 eCockpit / eDEP Integration......
3.2.2SSP4 – WP2.2 Live Air System......
3.2.3SSP6 – WP2.4 Pseudo Live AIR/GRD......
3.2.4SSP7 – WP2.5 CDTI Modifications......
3.2.5SSP5 – WP2.3 Simulated Air/Ground......
3.2.6WP 7.1 – ADS-B Validation Trials......
4.Test Design Specification......
4.1SSP3 – WP2.1 eCockpit / eDEP Integration......
4.2SSP4 – WP2.2 Live Air System......
4.3SSP6 – WP2.4 Pseudo Live AIR/GRD......
4.4SSP7 – WP2.5 CDTI Modifications......
4.5SSP5 – WP2.3 Simulated Air/Ground......
4.6WP7.1 – ADS-B Validation Trials......
5.Test Case Specification......
5.1SSP3 – WP2.1 eCockpit / eDEP Integration......
5.1.1eDEP Time Service Integration......
5.1.2eDEP IFPL Integration......
5.1.3eDEP Airspace Integration......
5.2SSP4 – WP2.2 Live Air System......
5.2.1ADS-B Communication......
5.2.2ADS-B in eCockpit......
5.2.3TIS-B Communication (Cat62)......
5.2.4TIS-B in eCockpit......
5.2.5ADS-B and TIS-B Messages......
5.3SSP6 – WP2.4 Pseudo Live AIR/GRD......
5.3.1ARTAS Proxy Server......
5.3.2IAS......
5.3.3Flight Plan with ICAO 24-Bit Address......
5.4SSP7 – WP2.5 CDTI Modifications......
5.4.1CTS_CDTI_10 ND Plug-in framework......
5.4.2CTS_CDTI_20 Behaviour of ND plug-in components......
5.4.3CTS_CDTI_30 Behaviour of Navaids ND plugin......
5.4.4CTS_CDTI_40 Behaviour of Surrounding Aircraft ND plugin......
5.4.5CTS_CDTI_50 ND Traffic symbol and Data tag......
5.4.6CTS_CDTI_60 ND Static data block......
5.5SSP5 – WP2.3 Simulated Air/Ground......
5.5.1ADS-B Communication......
5.5.2TIS-B Communication......
5.5.3eCockpit......
5.5.4CWP......
5.5.5UDP Forwarding to External Clients......
5.6ECockpit / PWP Coexistence......
5.6.1ECockpit / PWP Coexistence......
5.7ADS-B Validation Trials HMI......
5.7.1CWP......
1.Introduction
1.1Purpose
This document describes the test strategy and specification for WP2 of the contract TRS B164/2003 (see [Ref 1] and [Ref 2]), and WP7.1 ADS-B Validation Trials (see [Ref 9]). It compliments and extends those developed in the eDEP Acceptance Plan Document (see [Ref 3]).
The test strategy specified will be applied to the eDEP/eCockpit software to ensure the software meets the requirements for the integrated eDEP/eCockpit system specified in TRS B164/2003 and the eDEP/eCockpit software requirements (see [Ref 4]). The test specification is based around and extends the test cases specified in the validation test document used with the initial development of the eCockpit software (see [Ref 5]).
Additional tests are added to this document for eDEP/ARTAS integration, in particular the requirements for the use of eDEP in ADS-B Validation trials (CRISTAL MED).
Further test cases will be added to this document as work packages are commenced.
1.2Document structure
The document has the following structure:
- Section 2 provides an overview of the eDEP/eCockpit Integration project.
- Section 3 describes the testing and review processes that shall be applied for each milestone.
- Section 4 details the test specification for each milestone.
- Section 5 details the test cases to be applied for each milestone.
1.3Associated documentation
Title / Reference / Filename / Author / Date[Ref 1] / TRS B164 / 2003 / TRS_Phase_eDEP_SSP_v1.0.doc / D.Smith / 15/11/03
[Ref 2] / TRS B164 / 2003 Annex / TRS ANNEX eDEP SSP Demonstrator_v1.0.doc / D.Smith / 14/11/03
[Ref 3] / eDEP Acceptance Test Plan / eDEP_AcceptanceTestPlan.doc / R.Aynsworth / 26/11/02
[Ref 4] / eDEP/eCockpit Integration Project System Software Requirements / srd.doc / M.Vere / 02/04/04
[Ref 5] / eCockpit Validation Tests / eCockpit_VTD.doc / P.Hafeneder et. al. / 18/05/04
[Ref 6] / eDEP/eCockpit Integration Project Detailed Design Document. / eCockpit_DDD.doc / T.Cooper
[Ref 7] / eDEP Component Test Script / eDEP_ComponentTestScripts.doc / D.Smith / 14/05/04
[Ref 8] / eDEP/eCockpit Integration Component Test Script / ECockpit_CTS.doc / T.Cooper
[Ref 9] / Edep future task for the use of eDEP in ADS-B Validation Trials (CRISTAL MED),
Ref: TEC/eDEP/A34PT-50/WPE7.1 / TRS A34PT-2005_FutureTask_WP.7.1_AVT_Annex_v1.0.doc / L. Van der Hoorn / 30/8/2006
[Ref 10] / AVT CTSD / AVT_CTSD.doc / D. Kirkwood / 8/12/2006
2.project overview
2.1Background
The original eCockpit software is a stand-alone application providing a cockpit display for an aircraft. The eDEP/eCockpit integration project shall incorporate the original eCockpit software into the eDEP application and component structure and provide a connection to the ARTAS and SMART systems for communication of ADS-B and TIS-B messages.
2.2Development Process
The eDEP/eCockpit software integration development process consists of an iterative approach, adding functionality to the system in discrete steps. At each step, testing will be performed to ensure the functionality of the system is maintained and new functionality is adequately tested.
2.3Software & Software Testing
The eDEP/eCockpit integrated software is 100% Java built upon the JDK 1.4 SDK, the eDEP software library and the ILog JViews graphics library.
The software shall be tested throughout development and for each milestone using the test processes and strategy outlined in section 3.
2.4Project Milestones
The eDEP/eCockpit integration project WP2 consists of a number of milestones, each adding discreet functionality to the system:
Due date / Work Package ID and Name / Deliverable ID and Description25/06/04 / WP2.1 / Deliverable SSP3 : eCockpit / eDEP Integration
eDEP/eCockpit integrated application using eDEP flight, airspace and initial flight plan services provided by eDEP. Restructured code following design patterns for application and entity management demonstrated in the GSDK and ATC software.
23/08/04 / WP2.2 / Deliverable SSP4 : Live Air System
eDEP/eCockpit integrated application using ADS-B and TISB services through eDEP UDP connections to SMART / ARTAS.
14/10/04 / WP2.4 / Deliverable SSP6 : Pseudo Live AIR/GRD
Modification to IAS to support Cat32 messages.
19/11/04 / WP2.5 / Deliverable SSP7 : CDTI Modifications
eDEP/eCockpit integrated application with CDTI Plug-In framework and update of CDTI graphical displays with new functionality.
10/12/04 / WP2.3 / Deliverable SSP5 : Simulated Air/Ground
Modifications to the PM and IAS servers to use ADS-B and TIS-B messages respectively.
Table 1 – WP2 Milestones
The CRISTAL MED project WP7.1 consists of two milestones:
Due date / Work Package ID and Name / Deliverable ID and DescriptionEnd 2006 / WP7.1_1 / Delivery 1: eDEP capable of processing Asterix CAT 21.
Early 2007 / WP7.1_2 / Delivery 2: eDEP capable of handling multiple input streams.
3.Process reviews
This section details the processes that will be used in order to ensure the integrated software meets the software requirements for the project.
3.1Testing and Review Processes
The following sections outline the review processes and testing methods that will be applied to the eDEP/eCockpit integration project and software.
3.1.1Design Reviews
The software requirements for WP2 are documented in the eDEP/eCockpit Integration projects Software Requirements Document (see [Ref 4]). The requirements for WP7.1are documented in the ADS-B Validation Trials work plan (see [Ref 9]). The software architecture and the software design will be documented in the eDEP/eCockpit Integration Project Architecture Design Document and the eCockpit Software Design Document (see [Ref 6]) respectively. Test cases are specified in the eCockpit Validation Test Document (see [Ref 5]) for the original eCockpit system functionality.
The documentation will be maintained throughout the course of the projects.
The design reviews will ensure that:
- The interfaces and their data flows are sufficient to achieve the software requirements.
- The software requirements can be allocated to a given architectural element.
- Test use cases exercise the expected system behaviour.
3.1.2Code Reviews
During the development process, Graffica will conduct code reviews to ensure the software coding and comment standards are applied. These reviews will ensure that the software conforms to the standard eDEP/GSDK design patterns.
3.1.3Unit Testing
Software modules will not undergo formal unit testing, neither will complete coverage be demonstrated, as this will not be cost effective. Creation or replacement of eCockpit modules with eDEP code will be tested through informal partial integration tests within the stable environment of the GSDK toolkit throughout development. The original eCockpit system validation tests (see [Ref 5]) will be used to ensure the HMI interface is correct and that the system maintains its functionality.
3.1.4Integration Testing
Given the project timescales and budget, complete and exhaustive integration testing is not feasible. Integration testing will follow a “black box” strategy, with testing driven from scenario files and ADS-B and TIS-B message feeds from their respective services. The eCockpit cockpit and ASD will be used to evaluate the expected results from the scenario and message feeds against the observed display.
A large part of the integration phase will involve verifying the interface between the eCockpit simulator and the eDEP ATC systems connection to the ARTAS and SMART servers. This will require the transfer of ADS-B and TIS-B messages between eCockpit and the relevant ARTAS or SMART server via eDEP services.
For the eDEP/ARTAS integration, recorded data files and a recording file replayer is supplied by AVT and shall be used to simulate the live connection between eDEP and ARTAS.
3.1.5System Testing
The integrated eDEP/eCockpit system will be tested before each delivery using the eDEP component test scripts (see [Ref 7]) and eDEP/eCockpit integration component test scripts (see [Ref 8]) relevant for the changes made in the preceding work package.
The component tests for the eDEP/ARTAS integration are documented in the AVT CTSD (See [Ref 10]). This document shall be extended for the ADS-B Validation Trials WP7.1, to include tests for multiple streams of Asterix data and its display on the eDEP CWP.
3.2Review Schedule
The following sections detail the review processes that will be applied for each delivery.
3.2.1SSP3 – WP2.1 eCockpit / eDEP Integration
The eCockpit validation tests (see [Ref 5]) will be executed to ensure that the integrated software maintains the original eCockpit functionality after the integration with eDEP services and replacement of entity structures. Code reviews will be performed.
3.2.2SSP4 – WP2.2 Live Air System
The eCockpit validation tests (see [Ref 5]) will be executed to ensure that the integrated software maintains the original eCockpit functionality. The eDEP/eCockpit integration component test scripts will be executed to test the system’s use of messages made available through connection to eDEP ADS-B / TIS-B proxy services. Code reviews will be performed. Integration testing will be performed to evaluate the connection to the SMART system, both through simulated connection at the Graffica offices and through on-site connection at EEC.
3.2.3SSP6 – WP2.4 Pseudo Live AIR/GRD
The eCockpit validation tests (see [Ref 5]) will be executed to ensure that the integrated software maintains the original eCockpit functionality. The eDEP/eCockpit integration component test scripts will be executed to test the eDEP IAS component correctly produces Cat 32 messages, to correlate eDEP/eCockpit flights with those in the ARTAS/SMART system. Code reviews will be performed. Integration testing will be performed to evaluate the connection to the SMART system, both through simulated connection at the Graffica offices and through on-site connection at EEC.
3.2.4SSP7 – WP2.5 CDTI Modifications
The eCockpit validation tests (see [Ref 5]) will be executed to ensure that the integrated software maintains the original eCockpit functionality. The eDEP/eCockpit integration component test scripts will be executed to evaluate the new display features and ensure they are shown correctly. Code reviews will be performed.
3.2.5SSP5 – WP2.3 Simulated Air/Ground
The eCockpit validation tests (see [Ref 5]) will be executed to ensure that the integrated software maintains the original eCockpit functionality. The eDEP/eCockpit integration component test scripts will be executed to test that the PM and IAS services are correctly integrated with the ADS-B and TIS-B services respectively. Code reviews will be performed. Integration testing shall initially take place at the Graffica offices, followed by integration and acceptance tests on-site at EEC.
3.2.6WP 7.1 – ADS-B Validation Trials
The AVT CTSD shall be executed to ensure that the software maintains the original functionality. These tests will cover the IAS, eCockpit, PM generation of Cat-21 and the ARTAS proxy server. New tests are added for the receipt of Cat-21 messages and for the requirements specified in the work plan (see [Ref 9]). Code reviews will be performed. Integration testing shall initially take place at the Graffica offices, followed by integration and acceptance tests on-site at EEC.
4.Test Design Specification
The following sections provide an outline of areas that require testing for each delivery. Section 5 details of the test cases to be applied based on the specifications below.
4.1SSP3 – WP2.1 eCockpit / eDEP Integration
The test procedures for SSP3 – eCockpit / eDEP Integration will cover the following topics:
Look and Feel
- Verify the graphical display and interaction of the eCockpit display has remained the same throughout the eDEP integration.
eDEP Integration
- Verify that the airspace, initial flight plan and time are being driven through eDEP services.
- Verify that the eCockpit entity model has been replaced with the eDEP structures and patterns.
4.2SSP4 – WP2.2 Live Air System
The test procedures for SSP4 – Live Air will cover the following topics:
ASTERIX Messages
- Verify that Cat 21, 244, 32 and 62 message objects are available and correctly formatted.
Proxy Servers
- Verify that the ADS-B proxy server connects to the SMART ADS-B service.
- Verify that the TIS-B proxy server connects to the SMART TIS-B service.
- Verify that eCockpit receives and process ADS-B and TIS-B messages.
4.3SSP6 – WP2.4 Pseudo Live AIR/GRD
The test procedures for SSP6 – Pseudo Live Air will cover the following topics:
IAS Modifications
- Verify that the IAS Service correctly produces Cat32 messages.
- Verify that the IAS Service correctly uses Cat62 messages.
4.4SSP7 – WP2.5 CDTI Modifications
The test procedures for SSP7 – CDTI Modifications will cover the following topics:
CDTI Enhancements
- Verify that the CDTI supports a Plug-In framework.
- Verify that range rings are correctly displayed.
- Verify that the altitude filter works.
- Verify that the traffic symbol and data tags are correctly displayed.
- Verify that the static data block is correctly shown.
4.5SSP5 – WP2.3 Simulated Air/Ground
The test procedures for SSP5 – Simulated Air/Ground will cover the following topics:
ADS-B Messages
- Verify that the PM server correctly supports the use of ADS-B messages.
TIS-B Messages
- Verify that the IAS server correctly supports the use of TIS-B messages.
4.6WP7.1 – ADS-B Validation Trials
The test procedures for WP7.1 will cover the following topics:
- Verify that the ARTAS proxy server can correctly decode Asterix Cat 21 v0.23 messages.
- Verify that the ARTAS proxy server can receive and distribute state vectors for multiple streams of messages.
- Verify that the ARTAS proxy server can filter message streams by geographical region.
- Verify that the ARTAS proxy server can correlate messages on a per-stream basis.
- Verify that the ARTAS proxy server can stale-out tracks on a per-stream basis after a configurable amount of time.
- Verifiy that IAS can receive state vectors for multiple streams of data consisting of both Cat-21 and Cat-62.
- Verify that the CWP can display multiple streams of data, that these streams can be toggled on and off the display and that where a track is correlated, the flightplan can be displayed.
5.Test Case Specification
The following sections detail the test cases that will be applied for each milestone.
The test cases for each work package shall be determined at the start of that package.
5.1SSP3 – WP2.1 eCockpit / eDEP Integration
The original eCockpit validation test cases (see [Ref 5]) shall be performed. At this stage no other aircraft will be visible as feeds for ADS-B and TIS-B messages are implemented in future work packages.
5.1.1eDEP Time Service Integration
Test Case ID / SSP_TS_10Objective / The integrated system uses the eDEP time service for simulation time control.
Test Items / eCockpit Display
Input Specifications / Use the time control panel to test the time controls. Namely.
1)start the timer
2)accelerate the time rate
3)freeze / unfreeze the timer
4)stop the timer
Output Specifications / The eCockpit application time is controlled through the eDEP time control panel.
Test Criterion / Visual check for running the cockpit display and time control panel.
Environment
Test Dependencies / ---
5.1.2eDEP IFPL Integration
Test Case ID / SSP_FI_10Objective / The integrated system receives IFPL information from the eDEP IFPL server.
Test Items / eCockpit application, PVT.
Input Specifications / A scenario file with a flight is loaded in the PVT and the flight plan observed. eCockpit is loaded and run using the scenario file, observe the route shown in eCockpit for the flight.
Output Specifications / The flight plan for the eCockpit display matches the flight plan in the PVT.
Test Criterion / Visual checks.
Environment
Test Dependencies / ---
5.1.3eDEP Airspace Integration