As specified by the client

Must have

ID	Requirements	Priority
1	The application can monitor all Field Engineers's 'stress levels' (based primarily on heart rate)	Must have
2	The ability to read the vitals of the worker every minute (heart rate, skin temperature)	Must have
3	The ability for field engineers to send and respond to alerts from the head office	Must have
4	A Panic/Emergency feature which allows field engineers to raise an alarm manually or automatically with a 'panic button'	Must have

ID	Requirements	Priority
1	Reads location of lone worker when requested (to comply with company's regulations and worker's rights	Should have
2	A profile for each worker displaying their name, email, weight, height, and date of birth	Should have
3	The ability to send a certain message to the head office	Should have
4	The ability to receive a certain message from the head office	Should have

ID	Requirements	Priority
1	Create a desktop applicaiton that works with the microsoft band and has the same (possibly more) functionality as the existing application	Could have
2	Port the application onto iOS, Android, and Windows 10 devices to increase the user base of the application	Could have
3	Update the application to be compatible with Microsoft Band 2 (and hence, make use of the added sensors which increases funcitonality of the applicaiton)	Could have

ID	Use Case	Primary Actor	Secondary Actor
1	PanicButton	LoneWorker	Head Office
2	RecieveAlert	LoneWorker	Head Office

Use Case: PanicButton
ID: UC1
Brief Description: The LoneWorker wants to report an emergency to the Head Office.
Primary Actor: LoneWorker
Secondary Actor: Head Office
Pre-conidtion: The LoneWorker must be out on the field
Main Flow:
1. The use case starts when the LoneWorker selects the 'alert' section on the Band
2. The LoneWorker selects the type of emergency
3. The Head Office will recieve a notification of the emergency and act accordingly.
Post-condition: Emergency notification is removed.
Alternative Flow: None

Use Case: ReceiveAlert
ID: UC2
Brief Description: The Head Office has sent an alert to the LoneWorker.
Primary Actor: LoneWorker
Secondary Actor: Head Office
Pre-conidtion: The LoneWorker must be logged in
Main Flow:
1. The use case starts when the LoneWorker recieves an alert notification
2. The LoneWorker selects the notification and views the message recieved from the head office.
3. The LoneWorker will act accordingly.
Post-condition: Alert notification is removed.
Alternative Flow: None