Rajendra Akerkar, Therese Friberg, Christoph Amelunxen
This document gives an updated description of the “requirements engineering methodology” applied in EmerGent. The document also presents second version of 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 a scenario 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. Three 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 has been adopted in the EmerGent project.
- To update/refine and prioritise requirements for the development of the subsystems in WP4, WP5 and WP6.
In order to achieve this purpose the following tasks have been carried out since D3.4:
- We have updated the general methodology for the requirements engineering (RE) process that has been adopted in the EmerGent project (Section 3).
- We have refined two scenarios describing a series of events resulting from flooding. We have also added a new scenario on use of social media in riots (Section 5).
- Furthermore we have refined 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 prioritised the requirements (Section 7, 8).