Functional RequirementsEmergency Coordinator App – (Web Application)Functions

1. Login or sign-up2. Sign-up3. Sign-up error4. Sign-up success5. Login6. Login7. Login error8. Logout9. Forgot password10. Reset own password - user not logged in11. Reset own password error - user not logged in12. Reset own password success - user not logged

in13. Reset own password - user logged in14. Reset own password error - user logged in15. Reset own password success - user logged in16. Sign-up other user17. Sign-up other user - error18. Sign-up other user - success19. Reset other user’s password20. Reset other user’s password - error21. Reset other user’s password – success22. Start an emergency23. Select whether emergency type is drill or live24. Select users to include in emergency25. Display emergency status26. Display emergency summary27. Emergency over – stop an emergency28. Send SMS to user’s that haven’t responded

within 5 minutes of emergency start29. Display users that have been sent an SMS

message on the emergency status page30. Display user status31. response to user SMS message

Requirement Optionality

1 Geolocation Keep track of user in 15 second intervals Mandatory

2 Geolocation Retrieve interval geolocation data to server every 30 seconds Mandatory

3 User interface The transition between screens in the should be smooth i.e. “fluid” Mandatory

4 User interface The user should be aware that the a screen is transitioning Mandatory

5 Security User account data must be stored on the database Mandatory

6 Security The user’s password must be stored in a one way encrypted format on the database Mandatory

7 Security The user only needs to log on once when they first signup to the application. The application will remain authenticated to the user unless the user logs out.

Mandatory

8 Security If the user signs up when they first install the application, the application will remain authenticated to the user unless the user logs out.

Mandatory

9 Security The user does not need to log on when the application receives an emergency notification (unless the device is in a logged out state)

Mandatory

10 Security The application will not need to re-authenticate the user against the database server when an application receives an emergency notification.

Mandatory

11 Input validation All user input should be validated to prevent the input over the maximum size of the field/ database column

Mandatory

12 Input validation All user input should be validated to prevent the input of inappropriate characters Mandatory

13 Map display Maps must be displayed at an appropriate zoom level. Mandatory

14 Map display The user must be able to zoom the map Mandatory

15 Colour palette To be provided by Rob Mandatory

16 Emergency Status page

This icon displays and flashes in the app header when an emergency is in progress. The icon doesn’t display when there is no emergency in progress or the emergency is over

Mandatory

17 Emergency Status page Lists users by emergency response type including the time the emergency response was requested

Mandatory

18 Emergency Status page Display user’s location on a map Mandatory

Requirement Optionality

19 Emergency Over Enable the Emergency co-ordinator to stop the emergency Mandatory

20 Messages Display emergency messages Mandatory

21 Messages Enable the emergency coordinator to create and send messages to users Mandatory

22 Emergency summary Display emergency status including (Ok, Need Help), Average response time, Response source (via app or SMS)

Mandatory

23 Emergency summary Display people that did not respond Mandatory

24 User interface TBC by rob Mandatory

25 User interface Responsive web design Mandatory

26 App deployment App must be deployed to AWS (Amazon Web Services) Mandatory

27 Push notifications Use AWS to send push notifications Mandatory

28 SMS messages Use AWS to send and receive SMS messages Mandatory

29 Database Use MySQL as database Mandatory

EMERGENCYMANAGER

USERMANAGER SETTINGS

SELECT EMERGENCY

NEW EMERGENCY

USER STATUS

NEED HELP

Rachel Falworth

Jose Fargo

Jim Ferris

OK

NO RESPONSE

ALL USERS

Rachel Falworth

Jose Fargo

Jim Ferris

Rachel Falworth Mobile 0412 072 595 Send message

22 October 2015 15.38 5s User sent message We are running very low on water. We have only 1 day supply remaining.

Reply

22 October 2015 15.32 42s User requested help

22 October 2015 15.30 16s User GPS location received

22 October 2015 15.30 14s User received RUOK request

22 October 2015 15.30 11s Manager sent RUOK request

LOG

Search… SEARCH

Company logo here