Professional Documents
Culture Documents
Doc N.
E401-02-1014ATP
Iss.
01.00
ISSUED BY :
SELEX Sistemi Integrati
Via Tiburtina km 12,4 - Roma
ITALY
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
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
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.
3.
TEST PREPARATION.........................................................................................................10
4.
TEST DESCRIPTIONS.......................................................................................................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
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
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
4.3.3.1
4.3.4
4.3.5
4.3.6
4.3.7
4.3.8
4.3.9
4.3.10
5.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 6
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
5.1.1
5.1.1.1
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
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
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.
[1]
[2]
[3]
[4]
[5]
[6]
[7]
[8]
[9]
[10]
[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
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:
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
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.
Prerequisite conditions:
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 12
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
PREDICTION
AND
DATA
This Test Case verifies Application of the AoI/AoR Concept To Route Extraction
4.2.1.1 TEST 70
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).
Prerequisite conditions:
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.
Assumptions and constraints
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
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 14
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 15
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
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) Wait for firs automatic report with actual level lower than expected .
Expected Test Results:
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):
a) The Trajectory calculation is performed and the AoR boundary point is calculated
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 and 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.
Assumptions and Constraints:
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.
Prerequisite Conditions:
- FDP and CWP are in operative state
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 16
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
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) Change the trajectory (automatically or manually with XFL) in order to change the exit level
and send the SFPL to NEW Next FIR (SF) .
Expected Test Results:
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 MAC message is transmitted to ACC and an ACT
message is transmitted to SF.
In ACC (OP):
a) The Trajectory calculation is performed and the AoR boundary point is calculated
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 and 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 MAC message is received and a MAC is sent to SF.
Assumptions and Constraints:
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
Prerequisite Conditions:
- FDP and CWP are in operative state
- 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.
Expected Test Results:
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.
Assumptions and Constraints:
N.A.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 18
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
Dynamic OUT 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.
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
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.
Assumptions and Constraints:
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.
Prerequisite Conditions:
- FDP and CWP are in operative state
- 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.
Expected Test Results:
An SFPL is found in DB to be associated and is updated considering the dynamic COP
information and message content .
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.
Prerequisite Conditions:
- 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.
Expected Test Results:
- 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)
Assumptions and Constraints:
N.A.
4.2.1.10TEST 160
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.
Prerequisite Conditions:
- FDP and CWP are in operative state
- 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 .
Expected Test Results:
- 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)
Assumptions and Constraints:
N.A.
4.2.1.11TEST 170
Purpose:
Verify the transition from active in live state for an inbound flight upon a manual or automatic report.
Prerequisite Conditions:
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
Expected Test Results:
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
Purpose:
Verify the transition from live in terminated state for an outbound flight upon a manual or automatic
report.
Prerequisite Conditions:
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
Expected Test Results:
a. SFPL status is switched from live to terminated
b. Check the SFPL in the terminated flight list
Assumptions and Constraints:
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
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
Purpose:
Verify the FDP connection to ROMAWOS for reception of QNH over TCP/IP.
Prerequisite Conditions:
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
Expected Test Results:
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
Assumptions and Constraints:
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
Purpose:
Verify the FDP disconnection to ROMAWOS in case of no reception of QNH.
Prerequisite Conditions:
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
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
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 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.
Purpose:
verify that every time ROMATSA ROMAWOS is shut-down the connection with LFDP
shall be closed.
Pre-Test Activities:
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
Purpose:
verify that every time the LFDP starts-up and the ROMAWOS software is on, the connection
between them shall arise automatically.
Pre-Test Activities:
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
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.
Pre-Test Activities:
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.
Purpose:
verify that every time the no QNH message is received within Tr time-out the connection is
closed..
Pre-Test Activities:
connection is closed
The current QNH is displayed in dedicated blinking color on CWP
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.
Pre-Test Activities:
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
verify that the FDP shall reject without any further processing the message if the QNH value
is outside the defined QNH Range.
Pre-Test Activities:
the connection between LFDP and ROMAWOS shall be opened.
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.
The current QNH is displayed in dedicated blinking color on CWP
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)
Pre-Test Activities:
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.
This Test Case verifies the maximum number of tracks displayable on CWP.
5.1.1.1 TEST 230
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.
Expected Test Results:
The two tracks, having the code showed by the track generator, are shown with the squawk oversymbol.
Assumptions and Constraints: N.A.
5.2
This Test Case verifies the Military Areas Activation order from Supervisor position.
5.2.1.1 TEST 250
DAIW Mask
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 27
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
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.
Expected Test Results:
The upper level on the button related to the selected Map is updated.
Assumptions and Constraints: N.A.
5.2.1.3 TEST 270
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.
Expected Test Results:
The alarm related the infringement of the relevant area is arisen and shown on the display.
Assumptions and Constraints: N.A.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 28
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
5.2.2
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
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..
Assumptions and Constraints: N.A.
Purpose: Verify the extension of the maximum number of STCA 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 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.
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.
Assumptions and Constraints: N.A.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 29
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
Purpose: Verify the extension of the maximum number of DAIW map to 128
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 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.
Insert in the number field of the mask any value from 0 to 127;
Expected Test Results: the order is accepted and the drawing session starts..
Assumptions and Constraints: N.A.
5.2.3
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
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:
Expected Test Results: The alarms for the three tracks are arisen
Assumptions and Constraints: N.A.
5.2.3.2 TEST 330
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:
Expected Test Results: The alarms for the three tracks are arisen
Assumptions and Constraints: N.A.
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:
Expected Test Results: The alarms for the three tracks are arisen
Assumptions and Constraints: N.A.
5.3
GSL TOOL
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.
Prerequisite conditions: GSL Tool has been launched.
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.
Prerequisite conditions: GSL Tool has been launched.
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
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 33
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
5.3.2
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.
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 34
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 35
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
5.3.3
WIDGET TOOL
293113915.doc
Mod. Normal.dot
UNCLASSIFIED
Page 36
Doc N.
E401-02-1014ATP
Iss.
01.00
UNCLASSIFIED
Purpose: To modify the effect associated to any button of the SLDA Window.
Prerequisite conditions: Widget Tool has been launched.
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 Widget Main Menu Bar select File and then the item Load.
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.4
TABULAR TOOL
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
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.
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 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.
Select from the appeared pop-up menu Proprieties Editor.
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.
On the Proprieties Editor window select Apply.
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.
Prerequisite conditions: Tabular Tool has been launched.
The Departure List has been previously defined.
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
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
the right mouse button.
Select from the appeared pop-up menu Proprieties Editor.
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.
On the Proprieties Editor window select Apply.
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.
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 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.
Select from the appeared pop-up menu Proprieties Editor.
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.
Select from the appeared pop-up menu Proprieties Editor.
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
4.2.1Test Case 6:
Application of the
AoI/AoR Concept
To
Route
Extraction
REQ_2.0
REQ_3.0
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
REQ_5.0
REQ_6.0
REQ_7.0
REQ_8.0
REQ_9.0
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