User Requirements

Requirement 4

Type: Data

Description: The application will provide a window consisting of a graph summarizing how the user has spent their time. The graph will be a bar graph displaying the amount of time the user has dedicated to each event. Each month, the graph data will refresh and the user will see a new summary.

Rationale: The graphed summary will exist to aid users in reviewing and managing their time. Throughout the month, the user can see how they have allocated their time up until that point, and decide if they wish to make any changes to their schedule. This may assist users in reaching certain goals. For example, a user may predetermine that they wish to spend a certain number of hours studying each month, and use this graph to help them reach that goal.

Criterion: With the event information from the data entry section, the application will calculate the amount of time the user has dedicated to each event over the course of any given month. It will save this information and display it in a bar graph window plotting time vs. event. The data will be ordered most to least time consuming event.



Requirement 5

Type: Functional

Description: The Time Tracker application shall notify users' cell phones of scheduled approaching events in the form of reminders.

Rationale: Should users forget, these reminders will assist them in staying on track as well as motivating them to complete their tasks.

Criterion: In the data entry window of the Time Tracker application, a "notify me" button will be available for selection. Should the user choose to select it, the application will additionally provide the user with different amounts of time from which they shall choose from. The application will send an event notification reminder to the user's cell phone this amount of time in advance of the relevant event.



Requirement 6

Type: Environmental

Description: Time Tracker shall offer a "class mode" under which the application will operate silently. This means notifications and event reminders will be muted.

Rationale: The main users of this application will frequently attend lectures, labs, tutorials, or the campus library where sound is considered a distraction. A quick mode change to silence all application notifications would efficiently prevent any potential interruptions and the application from becoming a nuisance.

Criterion: The application requires the ability to mute notifications while still delivering silent reminders to users while it is in class mode.