1 / 9

ECTL 13-110856-A Support to the Automated Safety Data Monitoring Indicator project

ECTL 13-110856-A Support to the Automated Safety Data Monitoring Indicator project. Details. Objective: support the development of an Automated Data Processing Tool. Firm part (1 st October-31 st December) +Optional part (1 st Jan-31 st March)

alodie
Download Presentation

ECTL 13-110856-A Support to the Automated Safety Data Monitoring Indicator project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ECTL 13-110856-A Support to the Automated Safety Data Monitoring Indicator project

  2. Details • Objective: support the development of an Automated Data • Processing Tool. • Firm part (1st October-31st December) +Optional part (1st Jan-31st March) • Due date: 30th September, 15:00 (Brussels time) • Online submission

  3. Context

  4. Firm part • T1. Prototype a look and feel generator provide an advanced "look and feel" of the automated data processing tool. The tool shall allow an iterative process of design and review to be conducted with the EUROCONTROL project team, and for the design to be evolved in accordance with EUROCONTROL requirements, meaning that it shall be capable of integrating further performance indicators. As a minimum the tool shall demonstrate how automatically generated data can be displayed, filtered, processed and interacted with. At this time, the automatically generated data is expected to be as detailed in section 1.3 above, but this may be expanded as the project progresses. • T2. Develop user requirements (URD) for tool specification Following the production of the Interface Demonstrator - which will be non functional - it will be used to derive a detailed specification of functional and non functional requirements describing user actions and outputs. The URD will consider as a starting point the prototype tool. The technical specification shall be written in such a way that it may be used to develop a fully defined system interface should it be required.

  5. Optional part (I) • T3. Develop the system requirements (SRD) for the tool Based on the user requirements document and the interface demonstrated a detailed requirements specification will be produced. The specification will describe in detail the process and technical "functions" the tool is expected to deliver. The specification will make it clear how for the safety performance indicators data can be processed and displayed in accordance with the User requirements specification. The specification will also make it clear how future automated indicators shall be integrated into the tool. A list of potential indicators for display will be provided. • T4. Tool development (including documentation/manuals) Based on the URD and the SRD, the tool shall be developed to accept, process, analyse and display, to start with, separation minima infringements and runway incursions data, and any other indicator data identified and agreed with EUROCONTROL. The tool will be managed in accordance with software development best practice, and is expected to function on generic windows platforms and not require specialist software to run.

  6. Optional Part (II) • T5. Updated version of the Tool and documentation This task is twofold: • First, building upon the results of a pilot study conducted by EUROCONTROL during which the tool developed in T4 will undergo validation testing to ensure that it is sufficiently robust for operational use, an updated version of the tool will be developed. • Secondly, the software documentation (product documentation related to Users and System) will be produced to satisfy the following requirements: · how to use and administer the Tool · program source code · how further evolution of the Tool has been taken into account in its design Bidders shall give hints on ways of writing effective documents.

  7. Deliverables table (I)

  8. Deliverables (II)

  9. Required skills & evaluation

More Related