Table 3 Example output of the requirements elicitation process of informal scenario-based requirements

From: Robust requirements gathering for ontologies in smart water systems

Requirement group Requirement sub-group Elicitation question Behaviour and feedback scenario
Functional requirements Functionality What will the system do? See use case diagram and scenario description
Are there several modes of operation? Idle mode, where the system checks for significant water usage and recommends changes if needed. Active mode, where the application is operated by users for evaluating behaviours and neighbourhood data
Data What should the format of the input and output data be? The format of input data will be dependant on the data sources and the sensors used, while the output data should be intuitive and accurate to the end-users
Users Who will use the system? Primarily end-users and possibly water utility staff
Quality requirements Performance Are there constraints on execution speed, response time, or throughput? Viewing pertinent data should be performed immediately. The response time for evaluating a set of behaviours should be very quick while giving the recommended changes of behaviours could be within minutes
Usability How easy should it be for a user to understand and use the system? Very simple. Menus should be intuitively structured with the functionalities introduced to the users