Lynx D1.2 Technical requirements analysis report

The impact of requirements gathering and specification in the development of software systems as in the case of the Lynx project cannot be overemphasized. Generally, software requirements are grouped under functional and technical (non-functional) requirements. The former specify the individual actions that a system or component must accomplish whereas the latter define the quality attributes that a system shall fulfill.

In this document, we focus our attention on the gathering and specification of the technical requirements of the Lynx system. The document also describes the methodologies and models used in the gathering and specification of these requirements.

The methods we used to gather the technical requirements include the analysis of the documentation presented in D1.1 and D4.1, the technical analysis of similar existing systems (e.g. MULTISENSOR), some interviews conducted with other partners and a survey to gather specific QoS requirements.

The model we adopted for the requirement specification is based on a set of rules: unambiguity, completeness, ranking, consistency and verifiability. All the requirements must comply with these rules.

From the requirements that have been collected, we were able to deduce some key qualities that the design of the Lynx platform shall comply with: the system shall be scalable, flexible, interoperable, the reliability of the data must be guaranteed, the resources of the platform (data and services) shall be accessible only to authorized clients and the architecture shall comply with REST architectural style.