REQUIREMENT ANALYSIS

General requirements of the app

As a user , I want:

• A default notification on arrival to the destination.
• The notification should be sent to the peers chosen by the users.
• The followers have the liberty to unfollow based on circumstances.

Home screen

As a user, I want to be able to create a new tracking which will include:

1. Choosing peers who want to be intimated about the arrival.
   • The choosing of peers should be possible through a contact search
   • Provision of choosing people present in the phone’s contacts
2. As a user, I want to be able to set the time so that the app is intimated about the time of arrival. The time can be set in two ways
   • Set a time manually that is by entering the estimated time of arrival
   • Set a delay that is a particular number of hours or minutes of delay to determine the arrival time.
3. As a user , I want a GPS setting so that the destination of arrival is provided. Two options are available :
   • Location can be set using Maps
   • The address of the destination can be entered.
4. As a user I also want a manage tracking option where I can include:
   • SOS button
   • ABORT button
   • Stagnant Location option

SOS button

As a user , I want an SOS button so as to acknowledge an emergency situation that may occur

• In case of emergency either a default message or a message with explanation with the location co-ordinates has to be sent to the peers.
• Long press the button for 2-3 seconds
• If there is sufficient time , a message along with a photo can also be sent.

ABORT button

As a user , I want an ABORT button so that peers can be intimated about an area without network

• A free message along with a reason could be sent if there is a place without network.

STAGNANT LOCATION

As a user, I want an option which will detect the “no movement” condition for a certain duration

• When peers send a message regarding the “NO MOVEMENT” condition,a notification has to be sent to the followers.

How did your team analyse requirements?

• Effective communication among team members
• Iterative process of gathering the requirements from time-time
• Re-structuring and updating the requirements

How did your team specify requirements? How did you map requirements to user stories/use case?

• Paying heed to the details as defined by the customer
• Organising the requirements based on the necessity
• Tabulating the requirements in order
• Following the basic protocols while creating the User Stories and Use Case Diagrams.

WRONG ASSUMPTIONS

• We assumed that the follower does not require the app. Our customer later clarified this wrong assumption
• We also thought that the user should either accept or decline a request which would be sent after the app installation. But later clarified that there will be no request of any kind.
• Another false idea we had was that the time will be set by default. It later became clear to us that the time can be set manually by the user too.

Future work

• Check for any missing requirements and validate them
• Start the system design
• Effectively map the requirements to system design