Atp - Artas Gtw

UNCLASSIFIED Doc N.

Iss. DRAFT

PROGRAM:

Romanian ATC System Upgrading

Acceptance Test Procedures

For

ARTAS Gateway

CDRL No. :

Program No. :

Contract Identification Code :

ISSUED BY :

SELEX Sistemi IntegratiVia Tiburtina km 12,4 - Roma

ITALY

The copyright in this document is the property of SELEX Sistemi

Integrati S.p.A. The document is supplied on the express

understanding that it is to be treated as confidential and that it may

not be copied, used or disclosed to others in whole or in part for any

purpose except as authorised in writing by SELEX Sistemi Integrati

S.p.A.

The total number of pages, included the eventual Appendixes and Annexes, is 17 pages.

UNCLASSIFIED Page 1

UNCLASSIFIEDDoc N.

Iss.

SECURITY CLASSIFICATION

The following are the military classification levels for the documents from lowest to highest.

NON CLASSIFICATO CONTROLLATO UNCLASSIFIED NC

RISERVATO RESTRICTED R

RISERVATISSIMO CONFIDENTIAL RR

SEGRETO SECRET S

SEGRETISSIMO TOP SECRET SS

Editing, issue, custody, reproduction, diffusion and disposal of Classified documents must be done in conformity to the Internal Security Rules (“Regolamento Interno di Sicurezza”).

UNCLASSIFIED Page 2

UNCLASSIFIEDDoc N.

Iss.

Validation

Preparared by:SW System Manager

..........................................................(E.PALPACELLI)

Approved by:Project Leader

..........................................................(V. CIARAFFO)

Checked by:Q.A. Manager

..........................................................(R.PETRUCCI)

Authorized by:Project Manager

..........................................................(S.ARCERI)

UNCLASSIFIED Page 3

UNCLASSIFIEDDoc N.

Iss.

REVISIONS RECORD SHEET

This sheet is a record of revisions to this document.

Issue Date Revised ParagraphsDocument

Change Note

UNCLASSIFIED Page 4

UNCLASSIFIEDDoc N.

Iss.

ABBREVIATIONS LIST

CODE DESCRIPTION

AGW ARTAS GatewayARTAS ATC Radar Tracker and ServerBYP BYPassCOM CombinedCWP Controller Working PositionDARD Direct Access Radar DataGTW GatewayMRT Multi Radar TrackingPAT Provisional Site Acceptance TestPSR Primary Surveillance RadarRDP Radar Data ProcessingRFB Radar Fall-back SubsystemSSR Secondary Surveillance RadarTC Test CaseTG Test Group

UNCLASSIFIED Page 5

UNCLASSIFIEDDoc N.

Iss.

TABLE OF CONTENTS

1. INTRODUCTION....................................................................................................................7

1.1 IDENTIFICATION.................................................................................................................71.2 SYSTEM OVERVIEW..........................................................................................................71.3 DOCUMENT OVERVIEW....................................................................................................8

2. APPLICABLE AND REFERENCED DOCUMENTS..............................................................9

3. TEST PREPARATION.........................................................................................................10

3.1 SOFTWARE PREPARATION............................................................................................10

4. TEST DESCRIPTION...........................................................................................................11

4.1 TEST GROUP 1: GENERAL REQUIREMENTS...............................................................114.1.1 TEST CASE 1: SYSTEM STATUS..................................................................................114.2 TEST GROUP 2: REDUNDANT CONFIGURATION MANAGEMENT..............................124.2.1 TEST CASE 1: REDUNDANT CONFIGURATION MANAGEMENT...............................124.2.1.1 TEST 10: ARTAS GTW NODE ROLE SWITCHING - MASTER STAND-BY.........................124.2.1.2 TEST 20: ARTAS GTW NODE ROLE SWITCHING – STAND-BY MASTER........................124.2.1.3 TEST 30: ARTAS GTW NODE ROLE SWITCHING – MASTER MASTER-ALONE...............134.2.1.4 TEST 40: ARTAS GTW NODE ROLE SWITCHING – SLAVE MASTER-ALONE..................134.2.1.5 TEST 50: ARTAS GTW NODE ROLE SWITCHING – MASTER-ALONE MASTER...............144.3 TEST GROUP 3: DATA FLOW.........................................................................................154.3.1 TEST CASE 1: INPUT AND OUTPUT DATA FLOW......................................................154.3.1.1 TEST 10: INPUT ASTERIX CAT. 062 INTERFACE.............................................................154.3.1.2 TEST 20: OUTPUT SELEX-SI LEGACY FORMAT...............................................................15

5. Appendix A – Test Environment...........................................................................................17

UNCLASSIFIED Page 6

UNCLASSIFIEDDoc N.

Iss.

1. INTRODUCTION

1.1 IDENTIFICATION

This document is the Acceptance Test Procedure (ATP) for the the ARTAS Gateway Subsystem (AGW).

1.2 SYSTEM OVERVIEW

In the SELEX ATC System, the purpose of the ARTAS GATEWAY is to interface the ARTAS System to the SELEX legacy Middleware, allowing a transparent integration so that ARTAS and RFB can operate consistently, each representing an On-Line alternative facility ("contingency") for the other. The Middleware takes care of aligning system tracks generated by ARTAS to the corresponding system tracks processed by RFB.The ARTAS GATEWAY sends radar data toward internal and external users using SELEX legacy formats and ASTERIX Cat. 062 format..

UNCLASSIFIED Page 7

UNCLASSIFIEDDoc N.

Iss.

1.3 DOCUMENT OVERVIEW

This document contains the description of the tests applicable to the ARTAS Gateway subsystem in order to verify the satisfaction of the relevant User Requirements.

This document is composed of the following chapters:

Chapter 1: IntroductionProvides the scope of the ATP document, including the title and the identification number of the Company Project, a high level description of the subsystem under test and the description of the structure of the document.

Chapter 2: Applicable and Referenced DocumentsProvides the list of all documents applicable and/or referenced in this document.

Chapter 3: Test PreparationProvides the HW and SW test preparation procedures to be executed before the start of the test procedures execution.

Chapter 4: Test DescriptionProvides the description of the test procedures.

UNCLASSIFIED Page 8

UNCLASSIFIEDDoc N.

Iss.

2. APPLICABLE AND REFERENCED DOCUMENTS

UNCLASSIFIED Page 9

UNCLASSIFIEDDoc N.

Iss.

3. TEST PREPARATION

3.1 SOFTWARE PREPARATION

The ARTAS GTW node will have LINUX OS, AEA application SW and the other CSCIs loaded on local Hard Disk.

All the needed CSCIs relevant to Middleware and Supervision SW products (e.g. CDB, XSD, etc.) have to be present on the Hard Disk before the start of the test execution.

UNCLASSIFIED Page 10

UNCLASSIFIEDDoc N.

Iss.

4. TEST DESCRIPTION

The tests will be executed using real radar data including also flight check aircraft provided by ROMATSA.

4.1 TEST GROUP 1: GENERAL REQUIREMENTS

4.1.1 TEST CASE 1: SYSTEM STATUS

Purpose: Verify the system status (RDP/RFB operative mode).

Prerequisite conditions:

1. System in RDP mode;2. Real radars connected to feed the AGW and RFB with radar data.

Test Inputs: 1. On RFB I/O Console, at a certain time (T0), perform the manual transition order to switch from RDP

to RFB operative mode.

2. On the RFB I/O Console, at a certain time T1 (T1 > T0), perform the manual transition order to switch from RFB to RDP operative mode.

3. Manual/Automatic flight plan correlations are performed;

4.Switch off the ARTAS system to simulate a failure.

Expected Test Results:

1. On the CWP, verify that before the time T0 data are received from ARTAS Gateway while after T0

data are received from RFB.

2. On the CWP, verify that before the time T1 data are received from RFB while after T1 data are received from ARTAS Gateway and during transition there is no interruption of data on the CWP or any other subsystem.

3. Verify that after ARTAS failure the system performs the transition in RFB mode.

4. Verify the RDP/RFB transition.

5. Verify the status of the nodes on the TMCS

6. Verify that there is no loss of data (including Flight Plan ) and flight plan correlations on the CWPs.

Assumptions and Constraints:

Repeat the test giving transition orders from TMCS instead of I/O console.Repeat the test simulating an ARTAS output LAN failure to verify the RDP RFB transition.


UNCLASSIFIEDDoc N.

Iss.

4.2 TEST GROUP 2: REDUNDANT CONFIGURATION MANAGEMENT

4.2.1 TEST CASE 1: REDUNDANT CONFIGURATION MANAGEMENT

4.2.1.1 Test 10: ARTAS GTW node role switching - Master Stand-by

Purpose:Verify that the Master computer change its role into Stand-by mode.

Prerequisite conditions: 1. Real radars connected to feed the AGW and RFB with radar data 2. System in RDP mode;3. ARTAS GTW node available in Master role;

Test Inputs: 1. On the ARTAS GTW I/O console of the Master node, perform the switching by means of SLV order

in the NSV window;2. On the ARTAS GTW I/O console, display the new role by means of SNI order in the NSV window;3. On the TMCS perform the switching from Master to Stand-by.

Expected Test Results:1. On the ARTAS GTW I/O console and TMCS, verify that the Master computer change its role into

Stand-by mode.2. By visual inspection on the CWP, verify that there is no loss of data and flight plan correlations.3. . Verify the results on the TMCS.

4.2.1.2 Test 20: ARTAS GTW node role switching – Stand-by Master

Purpose:Verify that the Stand-by computer change its role into Master mode.

Prerequisite conditions: 1. Real radars connected to feed the AGW and RFB with radar data;2. System in RDP mode;3. ARTAS GTW node available in Stand-by role;

Test Inputs: 1. On the ARTAS GTW I/O console of the Stand-by node, perform the MST order in the NSV window.2. On the ARTAS GTW I/O console of the Master computer, display the role by means of SNI order in

the NSV window;3. On the TMCS perform the switching from Stand-by to Master.

Expected Test Results:1. On the ARTAS GTW I/O console and TMCS, verify that the Stand-by computer change its role into

Master mode.2. By visual inspection on the CWP and all other subsystems, verify that there is no data loss.


UNCLASSIFIEDDoc N.

Iss.

4.2.1.3 Test 30: ARTAS GTW node role switching – Master Master-Alone

Purpose:Verify that the Master computer change its role into Master-Alone mode shutting down the Stand-by computer.

Prerequisite conditions: 1. Real radars connected to feed AGW and RFB with radar data;2. System in RDP mode;3. ARTAS GTW node available in Master role.

Test Inputs: 1. Turn off the Slave computer;2. On the ARTAS GTW I/O console of the Master-Alone computer, display the role by means of SNI

order in the NSV window.

Expected Test Results:1. On the ARTAS GTW I/O console and TMCS, verify that the Master computer change its role into

Master-Alone mode.2. By visual inspection on the CWP, verify that there is no data loss.

4.2.1.4 Test 40: ARTAS GTW node role switching – Slave Master-Alone

Purpose:Verify that the Slave computer change its role into Master-Alone mode shutting down the Master computer.

Prerequisite conditions: 1. System in Artas Mode;2. Real radars connected to feed AGW and RFB with radar data.

Test Inputs: 1. Turn off the Master computer.2. On the ARTAS GTW I/O console of the Master-Alone computer, display the role by means of SNI

order in the NSV window.

Expected Test Results:1. On the ARTAS GTW I/O console and TMCS, verify that the Slave computer changes its role into

Master-Alone mode.2. By visual inspection on the CWP, verify that there is no data loss.


UNCLASSIFIEDDoc N.

Iss.

4.2.1.5 Test 50: ARTAS GTW node role switching – Master-Alone Master

Purpose:This Test verifies that the Master-Alone computer change its role into Master starting up the Stand-by computer.


1. ARTAS Gateway Slave node off.

Test Inputs: 1. Start-up the Slave computer.2. On the ARTAS GTW I/O console of the Master computer, display the role by means of SNI order in

the NSV window.

Expected Test Results:1. On the ARTAS GTW I/O console and TMCS, verify that the Master-Alone computer changes its

role into Master.


UNCLASSIFIEDDoc N.

Iss.

4.3 TEST GROUP 3: DATA FLOW

4.3.1 TEST CASE 1: INPUT AND OUTPUT DATA FLOW

4.3.1.1 Test 10: Input ASTERIX Cat. 062 interface

Purpose:Verify the ARTAS Gateway input in ASTERIX Cat. 062 format.


1. System in RDP mode;2. Real radars connected to feed AGW and RFB with radar data;3. Protocol/Format analyser connected to record ARTAS GTW input.

Test Inputs: N.A.


1. By means of Protocol/Format analyser, analyse recorded data and verify that radar data acquired on ARTAS GTW input are in ASTERIX Cat. 062 format (including also flight plan related data, itemI062/390) according to the relevant ICD,

Assumptions and Constraints:N.A.

4.3.1.2 Test 20: Output SELEX-SI legacy format

Purpose:Verify the ARTAS Gateway input in ASTERIX Cat. 062 format are converted into SELEX-SI legacy format and then sent on output LAN.


1. System in RDP mode;2. Real radars connected to feed AGW and RFB with radar data;3. Protocol/Format analyser connected to record ARTAS GTW output.

Test Inputs: N.A.


UNCLASSIFIEDDoc N.

Iss.


1. By means of Protocol/Format analyser, analyse recorded data and verify that radar data acquired on ARTAS GTW outputs are converted into SELEX-SI legacy format and then sent on output LAN.

Assumptions and Constraints:N.A.


UNCLASSIFIEDDoc N.

Iss.

5. APPENDIX A – TEST ENVIRONMENT
