Deliverable D2.2 FDFTO User Requirements Specification

This document constitutes deliverable D2.2 “User-Requirements” of EU-Rail Flagship Area 5 project FP5 TRANS4M-R. The project aims to boost innovation for the European rail freight sector, concretely by developing, validating, and demonstrating FP5- TRANS4M-R technical enablers. The reports results from task 2.4: Functional requirements.

The primary objective of this document is to provide the functional User-Requirements that are needed to perform the processes described in deliverable D2.1 “Preliminary Operational Procedures”. These requirements form the foundation for innovation development across WP3-WP12.

To derive the functional requirements from the operational procedures in chapter 6 – Elaboration of Requirements a methodology was developed that ensures the completeness and allows iterations including other WPs and expert groups. Polarion is the tool that is used within FP5 for requirements management in general. Therefore, all User-Requirements are created, developed, evaluated, and approved within this tool. Moreover, experts from various WPs were involved and decisions would be documented transparently and fully traceable. The developed methodology enables system and subsystem requirements that are to be developed in other WPs at different timelines to link to the User-Requirements and form relations.

The scope and delimitations of this document are stated in chapter 7 – General Assumptions & Premises. As the base of the elaborated User-Requirements are the Operational Procedures in D2.1, the restrictions stated there are also valid for this document. Within D2.1 the target Operational Procedures are used as reference to derive the User-Requirements from them.

In addition, further influencing factors were identified in chapter 8 which require the definition of further User-Requirements by other WPs or expert groups. These must be taken into account in a future overall consideration of the functional requirements of the FDFT system. Beyond the task description, non-functional User-Requirements and requirements resulting from other influencing factors are partly included in this deliverable when indicated without claim of completeness.

The results are to be found as User-Requirements and User-Features that are hierarchically and thematically related to each other. Items resulting from the operational procedures are divided into cluster that describe the following topics: System in General, DAC System, Power System, Data System and Brake System. They can be found in chapter 9 – User-Requirements.

The results represent the current state of discussions within FP5 TRANS4M-R based on the Target Operational Procedures. The currently elaborated User-Requirements state a work in progress that still needs to be consolidated and verified within the evaluation and verification/validation process in  Polarion. Due to continuous development within the requirements management process in Polarion, future releases of D2.1, or other developments within the project it is intended that these requirements are subject to possible changes in further development and will most likely be adapted in the future. Consequently, this document will then be updated and updated versions will be published.