an employee assigns a task and a code to each half-hour
worked. tasks are selected from a fixed set of tasks; codes are selected from a
fixed set of codes. each code is classified as being either premium or
non-premium. the premium rate codes are any 2-character code (such as DB, EO,
OT, SH, and SO); any other codes are non-premium.
Acceptance Tests
Show that time-data with an invalid employee-id or hours is rejected.
Show that time-data can be saved to a file and recalled from a file.
for each day worked, the employee sums the amount of time assigned to each task-code pair. task-code pairs having no time assigned to them for a particular day are ignored for that day. the set of task-time sums is known as the daily totals. the daily totals must be computed no later than 24 hours after the day to which they apply.
follow-on version deleted
a daily total must have eight non-premium hours; a daily total not having exactly eight non-premium hours is incorrect. a daily total of more than 24 hours is incorrect. incorrect time data should be highlighted to indicate potential problems. the presence of incorrect time data should not hinder other operations on the time data.
employees identify themselves before they can access time
data; the identification remains valid for the remainder of the session. each
employee has an employee number, which is a five digit number. each employee
can use only their own employee number.
Acceptance Tests
Show that a person with a valid employee id but invalid password cannot login
Show that a person with a valid employee id and valid password can login.
Show that a new employee cannot login until the new id and password are added to the password database; show that the new employee can login once the new id and password have been added to the password database.
every two weeks employee sums the daily totals produced over the previous two weeks to produce a bi-weekly total. the bi-weekly total is one number; the task-time associations in the daily totals are ignored when producing the bi-weekly total. the employee computing the bi-weekly total must sign-off on it to indicate the daily and bi-weekly totals are complete and correct. The bi-weekly total must be computed no later than the morning of the next business day after the last day in the bi-weekly period.
employees can obtain a report detailing how many hours a particular employee has spent on a given task over a given time period.
whenever an employee's time data is changed, the change is tagged with the old data, the name of the person making the change, and the date and time of the change. the complete set of change tags for any time datum can be made available for inspection; the initial entry of an datum is be part of the change set for the datum.
This page last modified on 18 July 2001.