PHAROS Requirements and System Engineering - Second Issue (D2.5)

By Pau Costa Foundation on

This deliverable describes the second phase of the process carried out to collect the user and system requirements for the PHAROS system so that the mentioned requirements are described in a systematic way. Moreover, the technical requirements that have been derived from the existing system requirements have been here reported. As in the previous issue of the deliverable, the definition of the functional system architecture, original planned to be included in D2.4 [1] and therefore, in this deliverable, has been moved to Deliverable 2.8 [2] (draft) and D2.9 [3] (final). The main reason relates to keeping the consistency of this document by including only system engineering related tasks within it, while grouping all the processes for defining the system architecture in the same deliverable (D2.8 [2] and D2.9 [3]). This way, duplication of the functional architecture in the two involved deliverables can be avoided. This document is the second out of four issues of the same deliverable published (First Issue already published, D2.4 [1]) and Third and Fourth Issues to be published (D2.6 and D2.7). In this issue, as it will be in the following ones, the tracking of the status and modifications of the different requirements during the different periods of time covered by each deliverable will be provided. For completeness, all modifications performed to the description of the requirements will be done by means of using change request forms, which will be included in this and the following deliverables in order to justify and document the requested modifications.

The main task contributing to this deliverable is Task 2.3: Requirements and System Engineering. In this task, the main objectives are:

•To identify and maintain the user requirements through consultations with the Advisory Board (AB) and selected additional end users

•To derive the corresponding system and technical requirements, propose an initial functional architecture and define the overall system test bed

•Maintain the requirements list by monitoring the evolution of the different technical WPs (WP 3 to WP 6) and monitor the development activities within.

•Define the overall system tests to be performed under WP 6 (System Integration, Testing and Validation)

The first workshop between members of the AB, additional local end users and members of the PHAROS consortium has been carried out in Barcelona in March 2014. It aimed at an alignment of views among the participants and led at refining the first draft of requirements (as documented in [1]). The second workshop took place again in Barcelona in October 2014, and, following the same line of actions, i.e., discussions during the workshop and further interaction by means of questionnaires distributed to the AB and end users, it offered the opportunity to further refine user and system requirements according to the received feedback. In order to clarify the relationship between the gathered user and system requirements, this issue provides a graphic interpretation of the dependencies between the consolidated user and system requirements, with the twofold goal of readily reflecting these interrelations and maintaining their traceability. As a result of the engineering process being carried out within the project, in parallel to the refinement and identification of user and system requirements, the identification of technical requirements to cope with the system requirements and provide the functionalities identified in [3] has been triggered. Although the technical requirements relative to the different system modules have been drawn up within the different technical work packages (WP 3, 4 and 5) and reported in those respective deliverables, they have been included in this present issue so to allow the documentation of any modification or addition that might be needed after the submission of the original deliverables. Therefore, the collections of technical requirements included in deliverables within WP3, 4 and 5 shall be understood as the technical 03/03/2015 requirements that triggered the specification of the different system modules, which is frozen when submitting the corresponding deliverables. The reflection of those technical requirements within this document allows for having a living collection of technical requirements which can be updated during the project lifetime and properly documented, if needed. Additionally, this approach allows gathering user, system and technical requirements in a single document, with the benefit of providing the overall perspective of the engineering approaches that have been followed during the system design. Regarding the overall system tests to be defined within this task, each system requirement includes the fit criteria to be fulfilled in order to consider the requirement satisfied by the system. In a similar way, technical requirements include also the method of verification to proof their fulfilment. This information will be used as basis to define the overall tests to be performed during system integration (WP 6) and which will be documented in the issue of this deliverable.

We acknowledge that this document uses material from the Volere Requirements Specification Template, copyright © 1995 – 2007 the Atlantic Systems Guild Limited [5].

Login or register to download this file