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 2-characters wide and classified as being
either premium or non-premium. the premium rate codes are the following: DB,
OT, SH, and SO. any other codes (including blank) are non-premium. (19 July
2001)
Acceptance Tests
Show that time-data can be saved to a file and recalled from a file.
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.
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, and a password.
each employee can use only their own employee number and password.
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.
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.
for a given time period and task id, generate a report listing all the employees who worked on the given task for the given period and the total amount of time each employee spent on the task during the 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 when the change was made. (18 July 2001)
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.
only the employee, the employee's bosses, and the administrator (secretary) responsible for time data can access the employee's time data. The employee and bosses always have read and write access to the data. the administrator has read access to the data until the employee has signed-off on the bi-weekly total; after the employee has signed-off, the administrator has read and write access to the time data.
employees have read-only access to their time data once they have signed off on them.
the complete set of change tags for any time datum can be made available for inspection; the initial entry of an datum is part of the change set for the datum. (18 July 2001)
to the system is maintained as a session.
the employee starts the session by entering his id and password. the employee
takes some explicit action in the system (like clicking a logout button) in
order to end the session. during the lifetime of the session, the system will
honor permitted employee actions. (19 July 2001)
Acceptance Tests
Show that the employee can end the session (log off).
Show that system functions are not accessible unless the session is active.
the user interface should present a reasonable approximation to the standard paper time sheet.
This page last modified on 11 August 2001.