Skip to main content
. 2015 May 3;14:18. doi: 10.1186/s12942-015-0010-z

Table 1.

General detection of a hot zone

Actor’s actions System’s answers
1.- This use case starts when thenotification service obtains users’geoposition.
2.- The notification service requestsinformation from the server withusers’ geoposition and the hotzones closest to them.
3.- It determines if users are near ahot zone, using distances that havebeen configured previously.
4.- It notifies users of the hot zonethrough the notifications bar.
5.- Users select thenotification.
6.- The system opens a windowusing mapview, in which it shows the various hot zones including their radius.
7.- Users can select arisk presented in themapview and obtaininformation about it(available when theapplication is usedfor infectious diseasesprevention).
Alternative flow: 3.- The notification service did notfind a hot zone near users’geoposition, therefore the system checks again after X amount of time has passed or Y meters have beentraveled.

This table presents an extension of the General detection of a geographic use case, in a conversational format, which emphasizes the interaction between the actors and the system.