Presentation is loading. Please wait.

Presentation is loading. Please wait.

Functional Requirements Emergency Coordinator App – (Web Application) Functions 1.Login or sign-up 2.Sign-up 3.Sign-up error 4.Sign-up success 5.Login.

Similar presentations


Presentation on theme: "Functional Requirements Emergency Coordinator App – (Web Application) Functions 1.Login or sign-up 2.Sign-up 3.Sign-up error 4.Sign-up success 5.Login."— Presentation transcript:

1 Functional Requirements Emergency Coordinator App – (Web Application) Functions 1.Login or sign-up 2.Sign-up 3.Sign-up error 4.Sign-up success 5.Login 6.Login 7.Login error 8.Logout 9.Forgot password 10.Reset own password - user not logged in 11.Reset own password error - user not logged in 12.Reset own password success - user not logged in 13.Reset own password - user logged in 14.Reset own password error - user logged in 15.Reset own password success - user logged in 16.Sign-up other user 17.Sign-up other user - error 18.Sign-up other user - success 19.Reset other user’s password 20.Reset other user’s password - error 21.Reset other user’s password – success 22.Start an emergency 23.Select whether emergency type is drill or live 24.Select users to include in emergency 25.Display emergency status 26.Display emergency summary 27.Emergency over – stop an emergency 28.Send SMS to user’s that haven’t responded within 5 minutes of emergency start 29.Display users that have been sent an SMS message on the emergency status page 30.Display user status 31.response to user SMS message

2 RequirementOptionality 1GeolocationKeep track of user in 15 second intervalsMandatory 2GeolocationRetrieve interval geolocation data to server every 30 secondsMandatory 3User interfaceThe transition between screens in the should be smooth i.e. “fluid”Mandatory 4User interfaceThe user should be aware that the a screen is transitioningMandatory 5SecurityUser account data must be stored on the databaseMandatory 6SecurityThe user’s password must be stored in a one way encrypted format on the databaseMandatory 7SecurityThe 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 8SecurityIf the user signs up when they first install the application, the application will remain authenticated to the user unless the user logs out. Mandatory 9SecurityThe user does not need to log on when the application receives an emergency notification (unless the device is in a logged out state) Mandatory 10SecurityThe application will not need to re-authenticate the user against the database server when an application receives an emergency notification. Mandatory 11Input validationAll user input should be validated to prevent the input over the maximum size of the field/ database column Mandatory 12Input validationAll user input should be validated to prevent the input of inappropriate charactersMandatory 13Map displayMaps must be displayed at an appropriate zoom level.Mandatory 14Map displayThe user must be able to zoom the mapMandatory 15Colour paletteTo be provided by RobMandatory 16Emergency 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 17Emergency Status pageLists users by emergency response type including the time the emergency response was requested Mandatory 18Emergency Status pageDisplay user’s location on a mapMandatory

3 RequirementOptionality 19Emergency OverEnable the Emergency co-ordinator to stop the emergencyMandatory 20MessagesDisplay emergency messagesMandatory 21MessagesEnable the emergency coordinator to create and send messages to usersMandatory 22Emergency summaryDisplay emergency status including (Ok, Need Help), Average response time, Response source (via app or SMS) Mandatory 23Emergency summaryDisplay people that did not respondMandatory 24User interfaceTBC by robMandatory 25User interfaceResponsive web designMandatory 26App deploymentApp must be deployed to AWS (Amazon Web Services)Mandatory 27Push notificationsUse AWS to send push notificationsMandatory 28SMS messagesUse AWS to send and receive SMS messagesMandatory 29DatabaseUse MySQL as databaseMandatory

4 EMERGENCY MANAGER USER MANAGERSETTINGS 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 FalworthMobile 0412 072 595Send message 22 October 201515.38 5sUser sent messageWe are running very low on water. We have only 1 day supply remaining. Reply 22 October 201515.32 42sUser requested help 22 October 201515.30 16sUser GPS location received 22 October 201515.30 14sUser received RUOK request 22 October 201515.30 11sManager sent RUOK request LOG Search…SEARCH Company logo here


Download ppt "Functional Requirements Emergency Coordinator App – (Web Application) Functions 1.Login or sign-up 2.Sign-up 3.Sign-up error 4.Sign-up success 5.Login."

Similar presentations


Ads by Google