R. Clayton (rclayton@clayton.cs.monmouth.edu)
(no date)
story 1
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.
story 2
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.
story 3
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.
story 4
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.
story 5
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.
story 6
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.
story 7
an employee with read access to time data can print a hard copy of that time
data. The data are printed on the standard time-sheet form.
story 8
employees have access to computers running windows and networked together on
the company's LAN. employees can work on time data from any networked
windows system.
story 9
employees identifiy 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.
story 10
a properly identified employee is has available a list of employee time data
to which access is allowed, as well as the date of the time data to display.
time data are uniquely identified by employee number and bi-weekly pay-period
ending date.
story 11
employees can enter their hours over the phone.
story 12
employees have read-only access to their time data once they have signed off
on them.
story 13
employees can obtain a report detailing how many hours a particular employee
has spent on a given task over a given time period.
story 14
task ids are 4 characters long. each employee has access to a list of valid
task ids, which include the following
5300
5391
53D1
53E1
FM00
SICK
VACN
HLDY
This archive was generated by hypermail 2.0b3 on Thu Aug 02 2001 - 12:45:05 EDT