ATP-PHASE2 After Remarq

UNCLASSIFIED
Doc N.
E401-02-1014ATP
Iss.
01.00
PROGRAM: ROMANIAN ATC SYSTEM UPGRADING
Acceptance Test Procedure

for
Romanian ATC System Upgrading PHASE 2-3
Contract Identification Code :
ISSUED BY :
SELEX Sistemi Integrati
Via 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 40 pages.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 1
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
SECURITY CLASSIFICATION
The following are the security classification levels for the documents.
NON CLASSIFICATO
NON CLASSIFICATO CONTROLLATO
RISERVATO
RISERVATISSIMO
SEGRETO
SEGRETISSIMO
UNCLASSIFIED
UNCLASSIFIED CONTROLLED
RESTRICTED
CONFIDENTIAL
SECRET
TOP SECRET
This document shall be used only by the intended recipients.

Editing, issue, custody, reproduction, diffusion and disposal of documents shall be performed in
compliance with the provisions of document BAM E 01.
If lost and found, the document, shall be addressed, in a closed envelope, with the indication of
the name and address of the sender, to:
Valter CIARAFFO
SELEX S.I. S.p.A.
Ufficio Sicurezza Aziendale
Via Tiburtina Km. 12,400
00131 Roma
ITALIA
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 2
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
Validation
Prepared by
Approved by :
Project Leader
.........................................................
.
(Gianfrancesco Ranieri)
.........................................................
.
(Valter CIARAFFO)
QA Approval:
Head of BUSC QA
.........................................................
.
(Renzo PETRUCCI)
Authorized by:
Project Manager
.........................................................
.
(Sergio ARCERI)
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
05/11/2010
Page 3
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
REVISIONS RECORD SHEET

This sheet is the record of revisions to this document.
Issue
Date
Revised Paragraphs
01.00
Draft
21/07/2009
05/11/2010
First issue
4.1.1.1,5.2.2,5.2.3,Add Requir. List
Document
Change Note
NA
LIST OF ABBREVIATIONS
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 4
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
ABBR.
ACC
ACT
AOR
APP
ATC
ATM
COP
DCL
DEC
DEP
EST
EXE
FDE
FIR
FPP
FPPS
IFR
LAM
MIL
OLDI
OPS
PLN
RFL
SCL
TKO
TOC
TOF
TWR
VFR
VSP
WKC
293113915.doc
Mod. Normal.dot
DESCRIPTION
Area Control Centre
ACTivate message
Area Of Responsibility
APProach control
Air Traffic Control
Air Traffic Management
Coordination Point
Departure CLearance
track DECorrelation
DEParture list
ESTimate
EXEcutive function
Flight Data Entry
Flight Information Region
Flight Progress Process
Flight data Pre-Processing System
Instrumental Flight Rule
Logical Acknowledge Message
MILitary
On Line Data Interchange
OPerational Site
PLaNning function
Requested Flight Level
SeCtor List
TaKeOff
Transfer Of Control
Transfer of Control Free
control ToWeR
Visual Flight Rule
Variable System Parameter
WaKeup
UNCLASSIFIED
Page 5
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
TABLE OF CONTENTS
1.
INTRODUCTION..................................................................................................................8
1.1 IDENTIFICATION.............................................................................................................................8
1.2 DOCUMENT OVERVIEW................................................................................................................8
2.
APPLICABLE AND REFERENCED DOCUMENTS........................................................9
3.
TEST PREPARATION.........................................................................................................10
3.1 HARDWARE PREPARATION........................................................................................................10
4.
TEST DESCRIPTIONS.......................................................................................................12
4.1 TEST GROUP 1.: AREA OF INTEREST MANAGEMENT...........................................................12

4.1.1
TEST CASE 1.: AREA OF INTEREST MANAGEMENT.........................................................................12
4.1.1.1
4.1.1.2
TEST 1.0 Application of the AoI/AoR concept in Environmental data management .....................................................12
TEST 2.0 Reference COP configuration.........................................................................................................................12
4.2 TEST GROUP 2.: TRAJECTORY PREDICTION AND DATA DISTRIBUTION WITHIN THE
AOI 13
4.2.1
TEST CASE 1.: APPLICATION OF THE AOI/AOR CONCEPT TO ROUTE EXTRACTION...............13
4.2.1.1
4.2.1.2
4.2.1.3
4.2.1.4
4.2.1.5
4.2.1.6
4.2.1.7
4.2.1.8
4.2.1.9
4.2.1.10
4.2.1.11
4.2.1.12
TEST 1.0 Trajectory calculation in AoI/AoR.................................................................................................................13

TEST 2.0 Dynamic OUT COP calculation with DCT....................................................................................................14
TEST 3.0 Dynamic OUT COP for departing Traffic ......................................................................................................14
TEST 4.0 Dynamic OUT COP MONA calculation for departing Traffic .......................................................................15
TEST 5.0 Next FIR changing calculation for departing Traffic and MAC transmission. ................................................16
TEST 6.0 Dynamic INB COP reception without route and without associated SFPL....................................................17
TEST 7.0 Dynamic OUT COP for Landing Traffic ........................................................................................................18
TEST 8.0 Dynamic INB COP for received OLDI messages without route.....................................................................19
TEST 9.0 AoI-Departure Aerodrome.............................................................................................................................19
TEST 10.0 AoI- Arrival Aerodrome.............................................................................................................................20
TEST 11.0 Flight procedural status for an inbound flight .............................................................................................20
TEST 12.0 Flight procedural status for an outbound flight ...........................................................................................21
4.3 TEST GROUP 3.: QNH RECEPTION OVER TCP/IP.....................................................................22

4.3.1.1
4.3.1.2
4.3.2
4.3.3
TEST 1.0 FDP connection to ROMAWOS for reception of QNH over TCP/IP ............................................................22
TEST 2.0 FDP disconnection from ROMAWOS...........................................................................................................22
TEST 3.0 QNH CONNECTION CONFIGURATION................................................................................23

QNH CONNECTION ACTIVATION.........................................................................................................23
4.3.3.1
TEST 4.0 Open connection at ROMAWOS start-up......................................................................................................23
4.3.4
4.3.5
4.3.6
4.3.7
4.3.8
4.3.9
4.3.10
TEST 5.0 CLOSE CONNECTION AT ROMAWOS SHUTDOWN..........................................................24

TEST 6.0 OPEN CONNECTION AT LFDP START-UP............................................................................24
TEST 7.0 CLOSE CONNECTION AT LFDP SHUT-DOWN....................................................................25
TEST 7.0 CLOSE CONNECTION AT TIME-OUT ELAPSING...............................................................25
TEST 8.0 QNH MESSAGES HANDLING...............................................................................................25
TEST 9.0 QNH MESSAGES FORMAT QNH RANGE.........................................................................26
TEST 10.0 QNH HANDLING FOR TMA CONTROLLING MORE THAN 1 AIRPORT.......................26
5.
TEST GROUP 4: CWP TRACKS PRESENTATION.......................................................27
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 6
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
5.1.1
5.1.1.1
TEST CASE 1.: CWP TRACKS PRESENTATION....................................................................................27

TEST 1.0 Maximum number of tracks presentation.......................................................................................................27
5.2 TEST GROUP 4 : TCA MAPS MANAGEMENT............................................................................27

5.2.1
5.2.1.1
5.2.1.2
5.2.1.3
5.2.1.4
5.2.2
5.2.2.1
5.2.2.2
5.2.2.3
5.2.3
5.2.3.1
5.2.3.2
5.2.3.3
TEST CASE 2.: DAIW AREAS MANAGEMENT....................................................................................27

TEST 1.0 DAIW Mask...................................................................................................................................................27
TEST 2.0 DAIW Area Updating....................................................................................................................................28
TEST 3.0 DAIW Area Updating....................................................................................................................................28
TEST 4.0 DAIW Area Conflict detection.......................................................................................................................28
SAFETY NET MAPS HANDLING BY MAP GENERATOR TOOL........................................................29

TEST 5.0 MSAW Maps Management............................................................................................................................29
TEST 6.0 STCA Maps Management..............................................................................................................................29
TEST 7.0 DAIW Maps Management.............................................................................................................................30
SAFETY NET MAPS HANDLING BY SAFETY NET FUNCTION........................................................30

TEST 8.0 MSAW Maps Management............................................................................................................................30
TEST 9.0 STCA Maps Management..............................................................................................................................30
TEST 10.0 DAIW Maps Management...........................................................................................................................31
5.3 INTERFACE EDITOR SYSTEM.....................................................................................................31

5.3.1
5.3.1.1
5.3.1.2
5.3.1.3
5.3.1.4
5.3.1.5
5.3.2
5.3.2.1
5.3.2.2
5.3.2.3
5.3.2.4
5.3.3
5.3.3.1
5.3.3.2
5.3.3.3
5.3.3.4
5.3.3.5
5.3.3.6
5.3.4
5.3.4.1
5.3.4.2
5.3.4.3
5.3.4.4
TEST CASE 3.: GSL TOOL........................................................................................................................31

TEST 1.0: Modify a color..............................................................................................................................................31
TEST 2.0: Create a Background colour..........................................................................................................................32
TEST 3.0: Create a Normal colour.................................................................................................................................32
TEST 4.0: Modify a font................................................................................................................................................33
TEST 5.0: modify a symbol...........................................................................................................................................33
TEST CASE 4.: CONTACT TOOL.............................................................................................................34

TEST 1.0: Modify the color resource of the speed vector..............................................................................................34
TEST 2.0: Modify label fields position..........................................................................................................................34
TEST 3.0: Add a label field............................................................................................................................................35
TEST 4.0: Modify leader line.........................................................................................................................................35
TEST CASE 5.: WIDGET TOOL................................................................................................................36

TEST 1.0: Modify SDA interface dimension..................................................................................................................36
TEST 2.0: Modify position window...............................................................................................................................36
TEST 3.0: Modify fields position...................................................................................................................................37
TEST 4.0: Modify fields dimension...............................................................................................................................37
TEST 5.0: Modify the effect associated to any button....................................................................................................37
TEST 6.0: Modify the text.............................................................................................................................................38
TEST CASE 6.: TABULAR TOOL.............................................................................................................38

TEST 1.0 Modify the background color of a flight list...................................................................................................38
TEST 2.0 Modify the text attributes (font, colour, style) of a flight list field ..................................................................39
TEST 3.0 Modify sorting criteria...................................................................................................................................39
TEST 4.0 Modify field position of a table......................................................................................................................40
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 7
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
1.
1.1
INTRODUCTION
IDENTIFICATION
This document is the Acceptance Test Procedure (ATP) for the Acceptance Test (FAT and SAT)
of the Local and Integrated tests for ROMANIAN ATC SYSTEM UPGRADING Phase 2-3
(E401).
1.2
DOCUMENT OVERVIEW
This document contains the description of the tests applicable to the Local ATC centre of Bucharest or
Arad or Constanta and for Integrated test for the three centre in order to verify the satisfaction of the
relevant SSS for phase 2-3 and ICD for QNH reception over TCP/IP
This document is composed of the following chapters:
Chapter 1: Introduction
Provides 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 Documents
Provides the list of all documents applicable and/or referenced in this document.
Chapter 3: Test Preparation
Provides the HW and SW test preparation procedures to be executed before the start of the test
procedures execution.
Chapter 4: Test Description
Provides the description of the test procedures.
Paragraph 4.1
TEST GROUP 1.: AREA OF INTEREST MANAGEMENT
Paragraph 4.2
TEST GROUP 2.: TRAJECTORY PREDICTION AND
DISTRIBUTION WITHIN THE AOI
Paragraph 4.3
TEST GROUP 3: QNH RECEPTION OVER TCP/IP
Paragraph 4.4
TEST GROUP 4: MAPS MANAGEMENT
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
DATA
Page 8
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
2.
APPLICABLE AND REFERENCED DOCUMENTS
[1]
E401-02-1002SWCD- A Date 15/09/2008 (draft A).
[2]
EE1100008304ATP05 REV E Integrated Tests
[3]
EE110008301ATP01 REV M CWP
[4]
E184-02-2395ATP REV D Flight Coordination Lfpds
[5]
EE100017801ATP01 REV B MTCD
[6]
EE110008303ATP01 REV F CMS
[7]
EE100008309ATP01 REV G RPB/TCA
[8]
EE100008304ATP01 REV G LFDPS/FPPS
[9]
Romania ATM Upgrade Technical Proposal TP2007-34 Rev.1
[10]
ES010006105SSS_revA: PROGRAM: Romania Upgrade - Phase 2 System Specification for

Flight Data Processing, Safety Nets and Operational Display
[11]
EE100021101ICD rev A: Interface Control Document for QNH messages management over
TCP/IP
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 9
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
3.
3.1
TEST PREPARATION
HARDWARE PREPARATION
The following hardware is necessary to perform the test session for the integrated tests:
Test Bed BLOCK DIAGRAM for Integrated Tests
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 10
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
The following hardware is necessary to perform the test session for the Local ATC tests:
Test Bed BLOCK DIAGRAM for Local ATC Tests
Bucharest or Arad or Constanta
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 11
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
4.
4.1
TEST DESCRIPTIONS
TEST GROUP 1: AREA OF INTEREST MANAGEMENT
4.1.1 TEST CASE 2:
AREA OF INTEREST MANAGEMENT
This Test Case verifies area of Interest management

4.1.1.1 TEST 30
Application of the AoI/AoR concept in Environmental data management
Purpose:
Verify that in the environment database (geographical data section) it is possible to distinguish between
Sectors internal to the AoR or Sectors internal to the AoI but external to the AoR.
Prerequisite conditions:
a. Geography database available

b. FDA [5] available
Test Inputs:
From "Geography" Menu select Sectors.

Expected Test Results:
The list of all the sectors stored in the Geography database is displayed.
Assumptions and constraints
Each Sector (both AoI Type and AoR Type) shall be defined as a composition of Airspace Zones.
Each AoI Type Sector shall be defined as a portion of the external Adjacent (or Subjacent) ATS Unit
airspace.
Points shall be basically characterised as follows:
a. Internal, if internal to the AoI (and with attributes, e.g. crossing, system, etc.);
b. External, if external to the AoI.
4.1.1.2 TEST 40
Reference COP configuration
Purpose:
Configure a COP, for each defined OLDI remote ATS unit, as reference coordination point for calculated
dynamic COP referencing (range and bearing) in OLDI messages.
a. Geography database available

b. FDA [5] available
Test Inputs:
1.From "Geography" Menu select COP.

2. Select the preferred cop (if existing, else create another one with add button) and press update button
to configure the COP marked as reference.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 12
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
3. Select the AoI sector to be referenced by the selected COP.

Expected Test Results :
The COP is saved and marked as reference

The reference COP shall be linked to one AoI sector.
4.2 TEST GROUP 5: TRAJECTORY

DISTRIBUTION WITHIN THE AOI
4.2.1 TEST CASE 6:
EXTRACTION
PREDICTION
AND
DATA
APPLICATION OF THE AOI/AOR CONCEPT TO ROUTE
This Test Case verifies Application of the AoI/AoR Concept To Route Extraction
4.2.1.1 TEST 70
Trajectory calculation in AoI/AoR
Purpose:
The route extraction function shall deliver to the trajectory calculation function the sequence of AoI and
AoR route points relevant to referred flights (2D Profile).
a. FDA [5] available

b. FDP available
Test Inputs :
Inserting a flight that follow a sequence of AoI and AoR route points, then open the FPL extended data
window.
Expected Test Results :
The list of all route points (AoI and AoR), time estimates and levels in trajectory is displayed.
The following type of routes shall be allowed:
a. Route point sequences composed only of AoR points.
b. Route point sequences composed both of AoR and AoI points, with more than one segment
contained in AoR.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 13
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
4.2.1.2 TEST 80 Dynamic OUT COP calculation with DCT

Purpose:
Verify that the 4D-Profile Calculation determine the points (and the associated flight conditions) resulting
from the intersections of the estimated flight path with the AoR boundaries, also for direct route segments
("DCT") from AoR to AoI, resulting in dynamic COP calculation and OLDI message formatting.
Prerequisite Conditions:
- FDP and CWP are in operative state
- Track simulator is running(SIMUL) or live traffic if available at the time
- OLDI simulator is running
- A reference OUT COP has been defined between TMA AoR and Upper AoI
Test Inputs:
- Overfly SFPL in live status
- Change the route with relevant order with a DCT from AoR internal point to AOI point.
- Wait the ABI message is sent to the next FIR
- Coordinate the flight and wait the ACT transmission
- The Trajectory calculation is performed
- The AoR boundary point is calculated
- The ETO for AoR boundary point is calculated
- The Dynamic outbound COP calculation is performed
- The dynamic COP is expressed in Estimated data field of the sent ABI and ACT messages as
range and bearing from the reference COP (the COP which is configured as reference for that
AoI sector).
Assumptions and Constraints:
N.A.
4.2.1.3 TEST 90 Dynamic OUT COP for departing Traffic
Purpose:
from the intersections of the estimated flight path with the AoR boundaries, for Departing Traffic that
exits from AoR on vertical boundary (e.g. from Constanta TMA to Bucarest ACC) on dynamic COP .
- Track simulator is running (SIMUL) or live traffic if available at the time
- TMA (Constanta) and ACC (BUcarest) are connected.
- ACT and REV are configured with Route Field.
Test Inputs:
a) Departing SFPL in pending status with RFL greater that upper AoR Limit.
b) Issue a Departure Clearance.
c) Wait for take-off
d) Issue an RCR clearance changing the route and vertical crossing point.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 14
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED

In TMA (CK):
a) The Trajectory calculation is performed and the AoR boundary point is calculated
b) A PAC message is transmitted containing the crossing point in estimate data expressed as
range and bearing from reference COP. The Dynamic COP information is displayed in flight
data page on FDE and CWP and on FHI and Sector List on CWP of TMA. The Crossing
point is presented on DPT.
c) An ACT message is transmitted containing the crossing point in estimate data expressed as
range and bearing from reference COP. The Dynamic OUT COP information is displayed in
flight data page on FDE and CWP and on FHI and Sector List on CWP of TMA. The
Crossing point is presented on DPT.
d) The trajectory is recalculated and a REV message is transmitted containing the new crossing
point in estimate data expressed as new range and new bearing from reference COP. The
Dynamic OUT COP information is displayed in flight data page on FDE and CWP and on
FHI and Sector List on CWP of TMA. The Crossing point is presented on DPT.
In ACC (OP):
b) A PAC message is received and the SFPL is updated and put in pending status. The Dynamic
COP information is displayed in flight data page on FDE and CWP. The Crossing point is
presented on DPT.
c) An ACT message is received and the SFPL updated and put in active status, correlation is
achieved. The Dynamic INB COP information is displayed in flight data page on FDE and
CWP and on FHI and Sector List on CWP of ACC. The Crossing point is presented on DPT.
d) A REV message is received and SFPL is updated. The Dynamic INB COP information is
displayed in flight data page on FDE and CWP and on FHI and Sector List on CWP of
TMA. The Crossing point is presented on DPT. If the new trajectory involves another ACC
sector as first in trajectory the SFPL is distributed according to the new sector sequence.
N.A.
4.2.1.4 TEST 100 Dynamic OUT COP MONA calculation for departing Traffic
Purpose:
Verify that the 4D-Profile Calculation automatically triggered by Monitoring AID determine the Dynamic
Point calculation and Revision message triggering.
- Track simulator is running (SIMUL)
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 15
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
Test Inputs:
d) Wait for firs automatic report with actual level lower than expected .
In TMA (CK):
d) The trajectory is recalculated and a REV message is transmitted containing the new crossing
FHI and Sector List on CWP of TMA. The Crossing point is presented on DPT.
In ACC (OP):
presented on DPT.
c) An ACT message is received and the SFPL updated and put in active status and correlation is
d) A REV message is received and SFPL is updated. The Dynamic INB COP information is
N.A.
4.2.1.5 TEST 110 Next FIR changing calculation for departing Traffic and MAC transmission.
Purpose:
Verify that the FDP transmits ACT and MAC message considering the next FIR for departing traffic.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 16
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
Track simulator is running (SIMUL)

TMA (Constanta) and ACC (BUcarest) are connected.
OLDI simulator between CK and SF is working, and between SF and OP
A reference OUT COP has been defined between TMA AoR and Upper AoI
ACT and REV are configured with Route Field.
Test Inputs:
d) Change the trajectory (automatically or manually with XFL) in order to change the exit level
and send the SFPL to NEW Next FIR (SF) .
In TMA (CK):
d) The trajectory is recalculated and a MAC message is transmitted to ACC and an ACT
message is transmitted to SF.
In ACC (OP):
presented on DPT.
c) An ACT message is received and the SFPL updated and put in active status and correlation is
d) A MAC message is received and a MAC is sent to SF.
N.A.
4.2.1.6 TEST 120 Dynamic INB COP reception without route and without associated SFPL
Purpose:
Verify that the FDP insert a flight considering received Dynamic COP and predefined OUTDF/Arrival
RWY point if there is no route in the received message and no eligible existing SFPL to be updated.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 17
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
- A reference INB COP has been defined
- NO SFPL exists in DB with same callsign of received message
Test Inputs:
a) Receive an OLDI message (ABI, or PAC or ACT) with Inbound point expressed as range
and bearing from reference COP.
In TMA (CK):
a) An SFPL is inserted with the following trajectory:
i. Received dynamic COP DCT OUTDF if the ADES contained in Message is NOT
Internal.
ii. Received dynamic COP DCT arrival runway if the ADES contained in Message
is Internal.
N.A.
4.2.1.7 TEST 130 Dynamic OUT COP for Landing Traffic

Purpose:
from the intersections of the estimated flight path with the AoR boundaries, for Landing Traffic that exits
from AoR on vertical boundary (e.g. from Bucarest ACC to Constanta TMA) on dynamic COP .
- Track simulator is running (SIMUL) or live traffic if available at the time
- A reference OUT COP has been defined between ACC AoR and Lower AoI
Exiting SFPL in Live status landing in Lower TMA (AoI) to Constanta exiting over a
static COP..
Test Inputs:
a) Issue a COO/XFL towards TMA..
b) Issue an RCR clearance going direct to arrival (AoI) runway..
In ACC (OP):
a) An ACT message is transmitted containing the static COP in estimate data.
b) The trajectory is recalculated and a REV message is transmitted containing the crossing
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 18
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
FHI and Sector List on CWP of ACC. The Crossing point is presented on DPT.
In TMA (CK):
a) An ACT message is received and the SFPL updated and put in active status, correlation is
achieved.
b) A REV message is received and SFPL is updated. The Dynamic INB COP information is
N.A.
4.2.1.8 TEST 140 Dynamic INB COP for received OLDI messages without route
Purpose:
Verify that the FDP updates a flight considering received Dynamic COP and existing SFPL route if they
are found to be consistent.
- A reference INB COP has been defined
- An SFPL exists in DB with same callsign of received message
Test Inputs:
Receive an OLDI message (ABI, or PAC or ACT) with Inbound point expressed as range and
bearing from reference COP and without route field.
An SFPL is found in DB to be associated and is updated considering the dynamic COP
information and message content .
4.2.1.9 TEST 150
AoI-Departure Aerodrome
Purpose:
Verify that for a flight departing from an aerodrome inside the AoI the FDPS automatically uses the
departure runway defined to be in use at the moment of SFPL creation.
- FDP and CWP [6] are in operative state
- Define an Aerodrome within the AoI and the runway in use for DEP in runway management
list
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 19
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
Test Inputs:
- Insert an Inbound SFPL with the ADEP configured as AoI.
- The FDP performs the trajectory calculation starting from runway elevation.
- Check in the FLDA the route extracted in particular the ADEP and the runway associated (as
defined in runway management list)
N.A.
4.2.1.10TEST 160
AoI- Arrival Aerodrome
Purpose:
Verify that for a flight arriving to an aerodrome inside the AoI, the FDPS shall automatically use the
arrival runway defined to be in use at the moment of SFPL creation.
- Define an Aerodrome within the AoI and the runway in use for ARR in runway management
list
Test Inputs:
- Insert an outbound SFPL with the ADES configured as AoI .
- The FDP performs the trajectory calculation
- Check in the FLDA the route extracted in particular the ADES and the runway associated (as
defined in runway management list)
N.A.
4.2.1.11TEST 170
Flight procedural status for an inbound flight
Purpose:
Verify the transition from active in live state for an inbound flight upon a manual or automatic report.
a. FDP in operative state
b. FDA available
c. MONA in operative state
d. Track simulator is running(SIMUL) or live traffic if available at the time
e. Inbound AoR SFPL in live state (SFPL_INBOUND)
Test Inputs:
a. Report manually the first AoR point (CWP , FDA) for selected SFPL
a. SFPL status is switched from active to live
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 20
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED

Repeat the test wait the automatic report of the first AoR point.
4.2.1.12TEST 180
Flight procedural status for an outbound flight
Purpose:
Verify the transition from live in terminated state for an outbound flight upon a manual or automatic
report.
a. FDP in operative state
b. FDA available
c. MONA in operative state
d. Track simulator is running(SIMUL) or live traffic if available at the time
e. Outbound AoR SFPL in live state (SFPL_OUTBOUND)
Test Inputs:
a. Report the last AoR point for selected SFPL
a. SFPL status is switched from live to terminated
b. Check the SFPL in the terminated flight list
Repeat the test with MONA and wait the automatic report of the last AoR point.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 21
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
4.3
TEST GROUP 19: QNH RECEPTION OVER TCP/IP
The system configuration for testing the QNH Connection and Management Function is the following:
- 2 LFDP Servers configured master/stand-by;
- at least 1 Client (FDE) for the LFDP servers;
- at least 2 CWPs configured as different TMA sectors,
- A PC running ROMATSA QNH routing software (ROMAWOS).
4.3.1.1 TEST 200
FDP connection to ROMAWOS for reception of QNH over TCP/IP
Purpose:
Verify the FDP connection to ROMAWOS for reception of QNH over TCP/IP.
a. FDP in idle state
b. FDA available
c. Connection via LAN to ROMAWOS server is available.
d. The configuration of connection parameters is ready (port number, IP address, time out parameters)
Test Inputs:
Put the FDP in operative state
The connection with the ROMAWOS is established and the QNH is received each VSP time.
The QNH updated value shall be presented only on TMA consoles
For ACC consoles, in QNH field, it shall be used TL=50 and NO computation is performed regarding
the QNH update.
4.3.1.2 TEST 210
FDP disconnection from ROMAWOS
Purpose:
Verify the FDP disconnection to ROMAWOS in case of no reception of QNH.
FDP in idle state
FDA available
Connection via LAN to ROMAWOS server is established.
QNH is received each VSP time.
Tr timer is configured to be greater than QNH VSP time.
Test Inputs:
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 22
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
From ROMAWOS no QNH is received for Tr seconds.

The FDP performs disconnection from ROMAWOS
4.3.2 TEST 3.0 QNH CONNECTION CONFIGURATION

Purpose: verify that LFDPS is able to manage all the configuration parameters needed to establish a
TCP/IP connection with the QNH routing software (ROMAWOS). For each connection it shall be
possible to configure the following parameters:
name of the connection (Aerodrome ICAO identifier: 4 ASCII characters) ;
one or two IP address;
one port number (remote port if FDP role is client, local port if FDP role is server);
one Tr time-out parameter for reception (in seconds);
the FDP role in the connections: client or server.
Pre-test Activities:
Verify the parameters in .Server.ini. Any parameter change will require an

IDLE/OPERATIVE transition for the relevant LFDP servers.
Activation: open a remote terminal session or a local terminal session on LFDP server. Modify the
parameters regarding the tested QNH connection. Perform an
IDLE/OPERATIVE transition.
Result:
Verify that the new parameters are applied and verify that the connection is working
properly.
4.3.3
QNH CONNECTION ACTIVATION
4.3.3.1 TEST 4.0 Open connection at ROMAWOS start-up
Purpose:
verify that every time ROMATSA ROMAWOS software starts-up and LFDP is on, the
connection between them shall arise automatically.
Pre-Test Activities:
the connection between ROMAWOS and LFDP shall be CLOSED. LFDP

should be operative
Activation: activate the ROMAWOS software and start the connection.

Result:
the connection between ROMAWOS and LFDP shall be ON. On the ROMAWOS client as
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 23
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
well as on the LFDP Client, the status of the connection with LFDP shall be
ON.
4.3.4 TEST 5.0 CLOSE CONNECTION AT ROMAWOS SHUTDOWN
Purpose:
verify that every time ROMATSA ROMAWOS is shut-down the connection with LFDP
shall be closed.
the connection between LFDP and ROMAWOS shall be opened.
Activation: close the connection on the ROMAWOS software.

Result:
on ROMAWOS Client the status of connection with LFDP shall be displayed as CLOSED.
On LFDP client the status of connection to ROMAWOS shall be displayed as
CLOSED.
The current QNH is displayed in dedicated blinking color on CWP
4.3.5 TEST 6.0 OPEN CONNECTION AT LFDP START-UP
Purpose:
verify that every time the LFDP starts-up and the ROMAWOS software is on, the connection
between them shall arise automatically.
the connection between ROMAWOS and LFDP shall be CLOSED. The LFDP
shall run in Idle mode. Activate the ROMAWOS software.
Activation: activate the LFDP in Operative mode. Start the connection on ROMAWOS software.
Result:
on the ROMAWOS client the status of the connection with LFDP shall be displayed as ON.
On the LFDP client the status of the connection with the ROMAWOS shall be
displayed as ON.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 24
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
4.3.6 TEST 7.0 CLOSE CONNECTION AT LFDP SHUT-DOWN
Purpose:
verify that every time the LFDP is shut-down even if the connection with ROMAWOS was
previously on, the connection between them shall be closed.
Activation: On LFDP terminal insert AFS SHT order.

Result:
the connection between ROMAWOS and LFDP shall be CLOSED. On the ROMAWOS
client the status of the connection with the LFDP shall be displayed CLOSED.
On the LFDP client the status of the connection with the ROMAWOS shall be
displayed CLOSED.
4.3.7 TEST 7.0 CLOSE CONNECTION AT TIME-OUT ELAPSING
Purpose:
verify that every time the no QNH message is received within Tr time-out the connection is
closed..
Activation: no QNH message is received for Tr seconds.

Result:
connection is closed
4.3.8 TEST 8.0 QNH MESSAGES HANDLING
Purpose:
verify that LFDP is able to extract the QNH information from the messages received from
ROMAWOS Software according the format described in QNH ICD.
Activation: On ROMAWOS client change the QNH value in the relevant field and send the new
message.
Result:
The extracted information shall be used to feed the system with actual QNH value for QNH
presentation and TL calculation.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 25
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
4.3.9 TEST 9.0 QNH MESSAGES FORMAT QNH RANGE

Purpose:
verify that the FDP shall reject without any further processing the message if the QNH value
is outside the defined QNH Range.
Activation: On ROMAWOS client change the QNH to a value below or above the minimum and
maximum values defined in the QNH range. Send the new message.
Result:
the message shall be rejected and the QNH value shall not be applied.
4.3.10 TEST 10.0 QNH HANDLING FOR TMA CONTROLLING MORE THAN 1
AIRPORT
Purpose:
verify that the QNH value used for TMA sectors will be the lowest received value among the
existing values referred to the relevant TMA airports (e.g. for Cluj the lowest
between LRSB, LRTM and LRCL)
Activation: On ROMAWOS client send on the same connection 2 or 3 different QNH values for
different airports.
Result:
the message shall be processed and the lowest value will be applied at the relevant TMA
sector.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 26
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
5.
TEST GROUP 4: CWP TRACKS PRESENTATION

5.1.1
TEST CASE 22:
CWP TRACKS PRESENTATION
This Test Case verifies the maximum number of tracks displayable on CWP.
5.1.1.1 TEST 230
Maximum number of tracks presentation
Purpose: Verify the capability to visualize up to 512 tracks on the Radar screen
Prerequisite Conditions: Track simulator is running (SIMUL) and 512 tracks have been generated.
Test Inputs: By track generator (SIMUL) set the squawk Indent for the first track and the last track.
The two tracks, having the code showed by the track generator, are shown with the squawk oversymbol.
Assumptions and Constraints: N.A.
5.2
TEST GROUP 4 : TCA MAPS MANAGEMENT

5.2.1
TEST CASE 24:
DAIW AREAS MANAGEMENT
This Test Case verifies the Military Areas Activation order from Supervisor position.
5.2.1.1 TEST 250
DAIW Mask
Purpose: Verify to visualize capability to activate 128 DAIW areas

Prerequisite Conditions: In the System 128 DAIW Maps have been defined and loaded.
Test Inputs: the supervisor requires the presentation of mask for DAIW areas activation.
The DAIW Map Activation mask contains 128 buttons, one for each defined area.
Each button reports the information related to:
The name of the Map;
the minimum level associated to the relevant area;
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 27
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
the maximum level associated to the relevant area.

5.2.1.2 TEST 260
DAIW Area Updating
Purpose: Verify the capability to change the upper level of the DAIW map
Prerequisite Conditions: In the System the DAIW Maps have been defined.
Test Inputs: the supervisor requires the presentation of mask for DAIW maps activation and for a
selected area changes the upper level.
The upper level on the button related to the selected Map is updated.
5.2.1.3 TEST 270
DAIW Area Updating
Purpose: Verify the capability to change the activate a DAIW Map

Prerequisite Conditions: In the System the DAIW Maps have been defined.
Test Inputs: the supervisor requires the presentation of mask for DAIW areas activation and activates the
selected area.
As soon as the Supervisor activates the area, the relevant area is activated and displayed on all the CWPs.
5.2.1.4 TEST 280
DAIW Area Conflict detection
Purpose: Verify the capability to detect the infringement with 128 DAIW areas
Prerequisite Conditions: In the System the DAIW Maps have been defined, the item-map 128 of the
DAIW Map file has been activated.
Test Inputs: By means of Track Generator (SIMUL) drives a track in order to infringe the item-map 128.
The alarm related the infringement of the relevant area is arisen and shown on the display.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 28
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
5.2.2
SAFETY NET MAPS HANDLING BY MAP GENERATOR TOOL
This Test Case verifies the capability to handle 512 MSAW areas, 512 STCA Areas and 128 DAIW Areas
by Map Generator.
5.2.2.1 TEST 290
MSAW Maps Management
Purpose: Verify the extensions of the maximum number of MSAW map to 512
Prerequisite Conditions: Map Editor Tool has been launched.
.
Test Inputs: In the XMG Start Up Panel select with left mouse button an existing application on the
Display List Field, then click on the Open button.
On the top side of the screen select, in the Maps pull down menu, the MSAW item, then
Version and then in the Version Choice box and press OK.
In the MSAW CMD frame click on the MSAW button under the REGION label and the
MSAW area panel appears.
Insert in the number field of the mask any value from 0 to 511;
Expected Test Results: the order is accepted and the drawing session starts..
5.2.2.2 TEST 300
STCA Maps Management
Purpose: Verify the extension of the maximum number of STCA map to 512
On the top side of the screen select, in the Maps pull down menu, the STCA item, then
Version and then in the Version Choice box select OK.
Click the stca button under the REGION section of the STCA CMD frame and the STCA
Region panel appears.
Expected Test Results: the order is accepted and the drawing session starts.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 29
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
5.2.2.3 TEST 310
DAIW Maps Management
Purpose: Verify the extension of the maximum number of DAIW map to 128
On the top side of the screen select, in the Maps pull down menu, the DAIW item, then
Version and in the Version Choice box and press OK.
In the DAIW CMD frame click on the daiw button under the REGION label and the
DAIW area panel appears.
Expected Test Results: the order is accepted and the drawing session starts..
5.2.3
SAFETY NET MAPS HANDLING BY SAFETY NET FUNCTION
This Test Case verifies the capability to handle 512MSAW areas, 512STCA Areas and 128 DAIW Areas
by Safety Net function.
5.2.3.1 TEST 320
MSAW Maps Management
Purpose: Verify the capability of the Safety Net function to handle up to 512 MSAW Maps
Prerequisite Conditions: 512MSAW Maps have been created and loaded by the Safety Net Function.
Test Inputs: Using Track Generator (SIMUL) drive:
A track infringing the MSAW Map n0;
A track infringing the MSAW Map n 254;
A track infringing the MSAW Map n 511;
Expected Test Results: The alarms for the three tracks are arisen
5.2.3.2 TEST 330
STCA Maps Management
Purpose: Verify the capability of the Safety Net function to handle up to 512STCA Maps
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 30
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
Prerequisite Conditions: 512STCA Maps have been created and loaded by the Safety Net Function.
Test Inputs: Using Track Generator (SIMUL) drive:
A track infringing the STCA Map n0;
A track infringing the STCA Map n 128;
A track infringing the STCA Map n 511.
5.2.3.3 TEST 340 DAIW Maps Management
Purpose: Verify the capability of the Safety Net function to handle up to 128 DAIW Maps
Prerequisite Conditions: 128 DAIW Maps have been created and loaded by the Safety Net Function.
The Supervisor has enabled the DAIW Maps related to the Maps n0, n64, n127.
Test Inputs: Test Inputs: Using Track Generator (SIMUL) drive:
A track infringing the DAIW Map n0;
A track infringing the DAIW Map n 64;
A track infringing the DAIW Map n 127.
5.3
INTERFACE EDITOR SYSTEM

5.3.1
TEST CASE 35:
GSL TOOL
5.3.1.1 TEST 1.0: Modify a color

Purpose: To edit a colour category by means of GSL Tool.
Prerequisite conditions: GSL Tool has been launched.
A colour category has been previously defined.
Test Inputs:
On the GSL Main Menu Bar select Edit and then the item Colors.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 31
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
On the appeared "Color Selection" window choose the desired colour category,
select it and click Ok.
On the appeared "Properties Editor" window click the button near to the
"Value" field.
On the appeared "IES Color Editor" window change the desired color
components values and click Apply.
On the "Properties Editor" window, appeared again, change the desired color
properties and click Ok.
Expected Test Results: The colour category has been modified.
5.3.1.2 TEST 2.0: Create a Background colour
Purpose: To create a Background colour category by means of GSL Tool.
Test Inputs:
On the GSL Main Menu Bar select Create, then the item Color, then the item
Background.
On the appeared "IES Prompt_popup" enter the new color name and click Ok.
On the appeared "Properties Editor" window enter color properties and click
Ok.
Expected Test Results: The new Background colour category has been created.
Assumptions and Constraints: In case of the creation of a new GSL file, the number of
memorized file must be less the maximum number definable.
5.3.1.3 TEST 3.0: Create a Normal colour
Purpose: To create a Normal colour category by means of GSL Tool.
Test Inputs:
On the GSL Main Menu Bar select Create, then the item Color, then the item
Normal.
On the appeared "IES Prompt_popup" enter the new color name and click Ok.
On the appeared "Properties Editor" window enter color properties and click
Ok.
Expected Test Results: The new Normal colour category has been created.
Assumptions and Constraints: In case of the creation of a new GSL file, the number of
memorized file must be less the maximum number definable.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 32
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
5.3.1.4 TEST 4.0: Modify a font

Purpose: To edit a font category by means of GSL Tool.
A font category has been previously defined.
Test Inputs:
On the GSL Main Menu Bar select Edit and then the item Fonts.
On the appeared "Font Selection" window choose the desired font category,
select it and click Ok.
On the appeared "Properties Editor" window click the button >> near to the
"Font Type" field.
On the appeared " Font Server Selection " box change the font family, type and
size. Then click Ok.
On the "Properties Editor" window, appeared again, change Grid Width and
Height Width fields value and click Apply or Ok.
Expected Test Results: The font category has been modified.
5.3.1.5 TEST 5.0: modify a symbol
Purpose: To modify a symbol or a font used by CWP application by means of GSL tool.
A file in X Consortium standard Bitmap Description Format (BDF) has been previously created
and at least one symbol has been previously defined inside.
Test Inputs:
On the GSL Main Menu Bar select Tools, then the item FontEditor.
On the appeared "Font Shower" window select File menu and then the item
load.
Select a font file by using the provided file selection box.
On the "Font Shower" window select a single character with the mouse left
button, then click with the mouse centre button.
On the appeared Bitmap Editor window modify the symbol, then select File
menu and click on the item Save.
On the "Font Shower" window select File menu and click on the item Save.
Expected Test Results: The symbol has been modified.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 33
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
5.3.2
TEST CASE 36:
CONTACT TOOL
5.3.2.1 TEST 1.0: Modify the color resource of the speed vector
Purpose: To modify the color resource of the speed vector.
Prerequisite conditions: Contact Tool has been launched.
The PENDING class and PENDING template have been created.
Test Inputs:
Click with the right mouse button on PENDING (template) node, child of
PENDING (class) node.
Select the View Structure item in the pop-up menu.
Move the mouse pointer over the structural tree then click with the right mouse
button on SPEED_VECT_FLD (field vector) node.
Select the item Properties Editor from the appeared pop-up menu.
From the selected Properties Editor window, press the selection button next to
the color field.
On the appeared Color Selection window select the color resource and click
Ok.
On the appeared Properties Editor window click Ok.
Expected Test Results: The color resource assigned to the speed vector has been modified.
5.3.2.2 TEST 2.0: Modify label fields position

Purpose: To modify a label field position.
Test Inputs:
button on FLD_MODECODE (field text) node, child of the "label (Label)"
node. Select the item Properties Editor from the appeared pop-up menu.
From the selected Properties Editor window, click on the selection button next
to position field, modify the text of the position resource (row; coloumn
format) to "C#13; R#3", then click Ok.
On the Properties Editor window click Ok.
Expected Test Results: The selected text field position has been modified according to the new
entered values.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 34
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
5.3.2.3 TEST 3.0: Add a label field

Purpose: To add a label field.
Test Inputs:
button on label (label) node. Select the item Add Field from the appeared popup menu.
Enter the new field name FLD_FREE_TEXT through the appeared IES New
Object window, then click Ok.
button on FLD_FREE_TEXT (field text) node, child of the "label (Label)"
node. Select the item Properties Editor from the appeared pop-up menu.
From the selected Properties Editor window, press the button next to the
visible field and select True, then click on the selection button next to
position field, enter "C#0; R#3", then click Ok.
Click Okfrom the Properties Editor window.
Expected Test Results: The label field has been added. It is visible on the preview window.
.
5.3.2.4 TEST 4.0:
Modify leader line
Purpose: To modify leader line.

Test Inputs:
button on leader (leader) node, child of the "label (Label)" node. Select the item
Properties Editor from the appeared pop-up menu.
From the selected Properties Editor window, press the second button next to the
min_leader_lenght field and select the new value, then click Ok.
Click Okfrom the Properties Editor window.
Expected Test Results: The leader line has been modified.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 35
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
5.3.3
TEST CASE 37:
WIDGET TOOL
5.3.3.1 TEST 1.0: Modify SDA interface dimension

Purpose: To modify the dimension of SDA interface.
Prerequisite conditions: Widget Tool has been launched.
SDA interface has been previously defined.
Test Inputs:
On the Widget Main Menu Bar select File and then the item Load.
On the appeared " Widget Selection" window select SDA and click Ok.
Move the mouse pointer over the structural tree, then click with the right mouse
button on the "SDA (TopLevelShell) node, the top node of the tree structure
representation.
Select from the appeared pop-up menu the item Properties Editor. On the
appeared Properties Editor window click the button next to the "dimensions"
field. Modify the text of the geometry resource in "650*SCALE_WIDTH *2,
SDA_HEIGHT*SCALE_ HEIGHT *2", then press Ok.
On the "Properties Editor" window click Ok.
Expected Test Results: The SDA interface dimensions have been modified.
5.3.3.2 TEST 2.0: Modify position window

Purpose: To modify SDA interface default position.
SDA interface has been previously defined.
Test Inputs:
On the appeared " Widget Selection" window select SDA and click Ok.
Move the mouse pointer over the structural tree, then click with the right mouse
button on the "SDA (TopLevelShell) node, the top node of the tree structure
representation.
Select from the appeared pop-up menu the item Properties Editor. On the
appeared Properties Editor click the first button next to the position field, change
values (e.g. from 11,1700 to 11,11) and click Ok.
On the Properties Editor window click Ok.
Expected Test Results: SDA interface default position has been changed.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 36
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
5.3.3.3 TEST 3.0:
Modify fields position
Purpose: To modify the position of a field in the LDA Window.

The LDA has been previously defined.
Test Inputs:
On the appeared " Widget Selection" window select LDA and click Ok.
Move the mouse pointer on the button1 that has to be moved and then click with
the right mouse button.
Select Proprieties Editor, select the button next to the field geometry, change
LDA_C_button1columnnumber into LDA_C_button1newcolumnnumber. Click
Ok. Click Ok.
Select
the
button2
already
displayed
in
the
position
LDA_C_button1newcolumnnumber, LDA_R_button1rownumber. Click with the
right mouse button and select Proprieties Editor. Select the button next to the field
geometry,
change
LDA_C_button2columnnumber
into
LDA_C_button1columnnumber. Click Ok. Then Click Ok.
Expected Test Results: The positions of the relevant buttons are inverted.
5.3.3.4 TEST 4.0:
Modify fields dimension
Purpose: To modify the dimension of SRP Window.

The LDA has been previously defined.
Test Inputs:
Continue the previous test.
Move the mouse pointer on the button whose dimensions have to be changed and
then click with the right mouse button.
Select Proprieties Editor, select the button next to the field geometry, change
LDA_BTN_WIDTH into LDA_BTN_WIDTH+4. Change LDA_BTN_HEIGHT
into LDA_BTN_ HEIGHT+2. Click Ok. Click Ok
Expected Test Results: The dimensions of the selected button are updated.
5.3.3.5 TEST 5.0:
Modify the effect associated to any button
Purpose: To modify the effect associated to any button of the SLDA Window.
The SLDA has been previously defined.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 37
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
Test Inputs:
On the appeared " Widget Selection" window select SLDA and click Ok.
Move the mouse pointer on a SLDA button (i.e. EBC Button) and click with the
right mouse button.
Select from the appeared pop-up menu Properties Editor.
On the Proprieties Editor window select the first button, i.e. 3dots on the right
of the input box for valueChangedCallback, insert the new function1 in the Edit
window and then click Ok.
Expected Test Results: The new function is associated to the selected button of the SLDA
Window..
5.3.3.6 TEST 6.0:
Modify the text
Purpose: Modify the text displayed on a button in the RB_Menu.

The RB_Menu has been previously defined.
Test Inputs:
On the appeared " Widget Selection" window select RB_Menu and click Ok.
Move the mouse pointer on the Button item of the structure tree and click with
Select from the appeared pop-up menu Proprieties Editor.
On the Proprieties Editor window select the first button on the right of the input
box for labelString, insert the new string in the Edit window and then click
Ok. Then click Ok.
Expected Test Results: The new string is visualized on the relevant button.
5.3.4
TEST CASE 38:
TABULAR TOOL
5.3.4.1 TEST 1.0 Modify the background color of a flight list

Purpose: Modify the background colour of the Departure List
The functions that can be used are those listed in the window accessible through menu Help/Reference on the main
menu bar, by clicking on the item Grp.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 38
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
Prerequisite conditions: Tabular Tool has been launched.

The Departure List has been previously defined.
Test Inputs:
On the Tabular Main Menu Bar select File and then the item Load.
On the appeared "Component Selection" window select dep and click Ok.
Move the mouse pointer on the TABLE item of the structure tree and click with
On the Proprieties Editor window select the button on the right of the cont
background color item, in the edit Window input the new color identifier 1 and
then click Ok.
On the Proprieties Editor window select Apply.
Expected Test Results: The background colour of the List is set.
5.3.4.2 TEST 2.0 Modify the text attributes (font, colour, style) of a flight list field
Purpose: Modify the Text attributes of the Departure List field.
Test Inputs:
Move the mouse pointer on an Entry Text Field item of the structure tree (or on
the relevant field on the list presentation) and click with the right mouse button.
On the Proprieties Editor window select the button on the right of the
attribute_name item, in the attribute selection Window select the new attribute
(font, color, style) for the field presentation and then click Ok.
Expected Test Results: The relevant field attribute in the Departure List is updated.
5.3.4.3 TEST 3.0 Modify sorting criteria
Purpose: Modify the sorting Criteria of the Flight items in the Departure List.
Test Inputs:
1
The new colour will be chosen from the defined Background Colour.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 39
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
Move the mouse pointer on the <Table> item of the structure tree and click with
On the Proprieties Editor window select the button on the right of action item,
and in the Edit Action Window reference the "sort_template" identifier and then
click Ok.
Expected Test Results: The sorting Criteria of the Departure List items is set
5.3.4.4 TEST 4.0 Modify field position of a table
Purpose: Modify a field position in the Departure List field.
Test Inputs:
Move the mouse pointer on a Text Field item of the structure tree, child of
HEADER_GRID (Grid), (or on the relevant field on the list presentation) and
click with the right mouse button.
On the Proprieties Editor window modify the text of the position_x resource
(expressed as column number in the father grid) and then click Ok.
Move the mouse pointer on a Entry Text Field item of the structure tree, child of
Entry_GRID (Grid), (or on the relevant field on the list presentation) and click
with the right mouse button.
On the Proprieties Editor window modify the text of the position_x resource
(expressed as column number in the father grid) and then click Ok.
Expected Test Results: The relevant field position in the Departure List is updated.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 40
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
REQ_1.0
If the Local ATS Units AoI is defined, it shall be

possible to calculate Dynamic COPs for all the flights
entering or leaving the ATS Units AoR on routes
(either ATS routes or direct route segments) not
containing static COPs.
4.2.1Test Case 6:
Application of the
AoI/AoR Concept
To
Route
Extraction
REQ_2.0
The calculated Dynamic COP shall be the point of

boundary crossing expressed as a bearing and
distance from a bilaterally agreed point both for
entering and for exiting flights.
REQ_3.0
For flights coordinated on Dynamic COPs,

downstream ATS Unit shall be calculated by
system. The messages to be transmitted and
rules for the transmission shall be based on
remote ATS Unit configuration features.
4.2.1Test Case 6:
Application of the
AoI/AoR Concept
To
Route
Extraction
4.2.1Test Case 6:
Application of the
AoI/AoR Concept
To
Route
Extraction
REQ_4.0
The system shall also provide the dynamic Change

Sector Point calculation.
REQ_5.0
All Change Sector Point shall be defined as

reference for internal coordination and the dynamic
Change Sector Point shall be calculated according
to Dynamic COPs.
REQ_6.0
The dynamic Change Sector Point shall be

displayed on the HMI as follows: magnetic direction
(i.e.: NW, SW) range (2 digits) point (3 characters).
Example: NW15BUK
REQ_7.0
The Area of Interest (AoI) shall be defined as the

composition of the existing AoI sectors defined in the
FDP geographical database.
REQ_8.0
All AoI geographical elements shall be defined in the

FDP Geographical Database.
REQ_9.0
The AoI shall be larger or equal to the AoR.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
the
the
the
the
4.2.1Test Case 6:
Application of the
AoI/AoR Concept
To
Route
Extraction
4.2.1Test Case 6:
Application of the
AoI/AoR Concept
To
Route
Extraction
4.2.1Test Case 6:
Application of the
AoI/AoR Concept
To
Route
Extraction
4.1Test Group 1:
area of Interest
management
4.1Test Group 1:
area of Interest
management
4.1Test Group 1:
area of Interest
management
Page 41

ATP-PHASE2 After Remarq

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ATP-PHASE2 After Remarq

Uploaded by

Copyright:

Available Formats

UNCLASSIFIED

PROGRAM: ROMANIAN ATC SYSTEM UPGRADING

Acceptance Test Procedure

Contract Identification Code :

The copyright in this document is the property of SELEX Sistemi

This document shall be used only by the intended recipients.

REVISIONS RECORD SHEET

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

3.1 HARDWARE PREPARATION........................................................................................................10

4.1 TEST GROUP 1.: AREA OF INTEREST MANAGEMENT...........................................................12

TEST CASE 1.: AREA OF INTEREST MANAGEMENT.........................................................................12

TEST CASE 1.: APPLICATION OF THE AOI/AOR CONCEPT TO ROUTE EXTRACTION...............13

TEST 1.0 Trajectory calculation in AoI/AoR.................................................................................................................13

4.3 TEST GROUP 3.: QNH RECEPTION OVER TCP/IP.....................................................................22

TEST 3.0 QNH CONNECTION CONFIGURATION................................................................................23

TEST 4.0 Open connection at ROMAWOS start-up......................................................................................................23

TEST 5.0 CLOSE CONNECTION AT ROMAWOS SHUTDOWN..........................................................24

TEST GROUP 4: CWP TRACKS PRESENTATION.......................................................27

TEST CASE 1.: CWP TRACKS PRESENTATION....................................................................................27

5.2 TEST GROUP 4 : TCA MAPS MANAGEMENT............................................................................27

TEST CASE 2.: DAIW AREAS MANAGEMENT....................................................................................27

SAFETY NET MAPS HANDLING BY MAP GENERATOR TOOL........................................................29

SAFETY NET MAPS HANDLING BY SAFETY NET FUNCTION........................................................30

5.3 INTERFACE EDITOR SYSTEM.....................................................................................................31

TEST CASE 3.: GSL TOOL........................................................................................................................31

TEST CASE 4.: CONTACT TOOL.............................................................................................................34

TEST CASE 5.: WIDGET TOOL................................................................................................................36

TEST CASE 6.: TABULAR TOOL.............................................................................................................38

APPLICABLE AND REFERENCED DOCUMENTS

E401-02-1002SWCD- A Date 15/09/2008 (draft A).

EE1100008304ATP05 REV E Integrated Tests

EE110008301ATP01 REV M CWP

E184-02-2395ATP REV D Flight Coordination Lfpds

EE100017801ATP01 REV B MTCD

EE110008303ATP01 REV F CMS

EE100008309ATP01 REV G RPB/TCA

EE100008304ATP01 REV G LFDPS/FPPS

Romania ATM Upgrade Technical Proposal TP2007-34 Rev.1

ES010006105SSS_revA: PROGRAM: Romania Upgrade - Phase 2 System Specification for

4.1.1 TEST CASE 2:

AREA OF INTEREST MANAGEMENT

This Test Case verifies area of Interest management

Application of the AoI/AoR concept in Environmental data management

a. Geography database available

From "Geography" Menu select Sectors.

Reference COP configuration

a. Geography database available

1.From "Geography" Menu select COP.

3. Select the AoI sector to be referenced by the selected COP.

The COP is saved and marked as reference

Assumptions and constraints

4.2 TEST GROUP 5: TRAJECTORY

APPLICATION OF THE AOI/AOR CONCEPT TO ROUTE

Trajectory calculation in AoI/AoR

a. FDA [5] available

4.2.1.2 TEST 80 Dynamic OUT COP calculation with DCT

Expected Test Results:

Track simulator is running (SIMUL)

4.2.1.7 TEST 130 Dynamic OUT COP for Landing Traffic

4.2.1.9 TEST 150

AoI- Arrival Aerodrome

Flight procedural status for an inbound flight

Assumptions and Constraints:

Flight procedural status for an outbound flight