D3.4 User Requirements, Version 1


Rajendra Akerkar, Therese Friberg, Alexis Gizikis


This document gives a description of the “requirements engineering methodology” applied in EmerGent. The document also presents first version of conceptual, technical, visual and user requirements for including social media in the emergency management for both ES and citizens.
The requirements for a system are the descriptions of what the system should do—the services that it provides and the constraints on its operation. Requirements engineering is one of the earliest phases of software development and has the maximum impact on the product in the long run. Hence properly collected requirements have great influence on the design phase software development.
The EmerGent requirements engineering process is based on use case driven approach, involving both EmerGent end-users and technology providers who are part of the consortium as well as End user Advisory Board (EAB) members. Two scenarios form the basis for the identification and development of use cases and requirements. This process has culminated in a number of specific requirements that can be used as the basis of the software development process.

Purpose of the document

The aim of this document is as follows:

  •  To present methodology for requirements engineering to be adopted in the EmerGent project.
  • To collect requirements for the development of the components in WP4, WP5 and WP6.

In order to achieve this purpose the following tasks have been performed:

  • We have prepared the general methodology for the requirements engineering (RE) process that has been adopted in the EmerGent project (Section 3).
  • We have defined two scenarios describing a series of events resulting from flooding to current and possible uses of social media (Section 5).
  • Furthermore we have illustrated eight use cases to identify the requirements for the development of the components in WP4, WP5 and WP6 (Task 6.1 and 6.3) (Section 6).
  • Finally we have described the requirements prioritisation approach as well as the initial list of the requirements (Section 7, 8).