Use cases

Use case 1:
Stakeholder description:
 * 1) The User: Manage tasks, connect with other people with similar tasks
 * 2) Existing calender services(Google Calendar): Utilize our calendersystem, so their calender data can be spread out to more platforms.

Actors: Precondition:
 * 1) User
 * 2) Administrator

The user has basic knowledge of computer and has been introduced to the calendar system. Is near a calendar device at the time. He has synchronized his existing calendar system with our system, so it becomes cross platform.

Postcondition (succes scenario):

The user gets notified about the statement by the system on whatever operating system (car, refrigerator, television) he is near at the time, or a predefined amount of time before, the appointment is. OR, if he is not near, get notifed as soon as he is near one.

Main-success-scenario:


 * 1) User opens the calender system on whatever platform he wishes (phone, car-computer, computer).
 * 2) The system presents a graphical presentation of the current month, and the appointments, that the user has already made.
 * 3) The user finds the date on which he wishes to make an appointment.
 * 4) He opens the Create Appointment menu for the day, and types in the information and time.
 * 5) He saves the appointment and exits the program.
 * 6) At the time for the appointment the user is near a device with the calendar system installed on.
 * 7) The system notifies him about the appointment.
 * 8) The user closes the notification.

Main-alternate-scenario:


 * 1) User opens the calendar system.
 * 2) Through the graphical presentation he finds the date, where he wishes to make an appointment.
 * 3) He opens Create Appointment and makes the apoointment.
 * 4) He exits the program.
 * 5) At the time for the appointment the user NOT is near a device with the calendar system installed on.
 * 6) The system will try to notify him, but he is not there.
 * 7) When the user is near a device again, the system will notify him, that an appointment has occured(when and where).
 * 8) The user closes the application.

Stakeholder description:
Refer to stakeholders in use case 1.

Actor:
Administrator/User.

Precondition:
The user has created tasks enough for the system ot create and maintain a list of featured tasks (see glossary for definition). The user wants to edit some characteristic of a featured task. For example: The user have been training regularly, but have now switched gym and want to update the featured tasks for training with the new location.

Postcondition:
The user have succesfully updated the featured task and the system will now propose the updated version of the task instead of the old one. This eliminates the need for the user to "build up" a new featured task by adding it many times.

Main-success-scenario:

 * 1) The user opens the calendar system.
 * 2) The user enters the edit featured tasks functionality
 * 3) The user edits the task he wish to update.
 * 4) The user confirms the decisions made and closes the program.