EXECUTIVE SUMMARY:
The FLYSAFE Project is concerned with the development of a prototype Next Generation Integrated Surveillance System (“NG-ISS”).  The Traffic functionality of the NG-ISS groups several subsystems with response-times ranging from immediate reaction (safety net functions such as ACAS), through tactical alerting systems (e.g. airport surface movement alerting) to inputs for strategic decision and planning aids.  
This document, the “Specification of Functional Requirements for Evaluation” for the Traffic segment of the NG-ISS:

• Provides a short review of the inputs used for the work,
• Defines the functional and performance requirements for the full scope of Traffic functionality to be developed during the FLYSAFE project. Please note that the design of Traffic Functions is embodied in the NG-ISS UML Model in the form of Use Cases, Sequence Diagrams and Interface Definitions. UML design information presented in D3.1.2 version A has been removed from this Version B to prevent possible confusion with the UML Model.  Other aspects of the Traffic Functions (such as interface definitions) have been aligned with the specifications used in the Traffic Part Task Evaluations.
• Identifies the complete set of Traffic interfaces, in terms of:
• External Traffic interfaces (i.e. interfaces between Traffic functions and other parts of the NG-ISS or the operating environment)
• Intra-Traffic interfaces (i.e. interfaces between functions within the Traffic segment), and
• Internal function interfaces (i.e. interfaces within the function being described), which forms part of the function design description.
• Describes the set of test harnesses necessary to prepare the Traffic functions for the man-in-the-loop Traffic Part Task Evaluations (PTE) to be undertaken at the Technical University of Darmstadt (TUD).

This document is the second in a series of reports designed to record the development of new Traffic functionality and the re-use of existing technology within the NG-ISS Traffic segment and is based on the required Traffic segment behaviours identified in FLYSAFE report D 3.1.1 “Specification of Operational Situations, Goals and Behaviours”.  
Subsequent reports will document the detailed Traffic functionality design, testing and evaluation.
 
For further information please contact:
Mr. Alexander Halstead: Alexander.Halstead@baesystems.com