- Srini Katragadda, 9/12/17

ABC holding company timesheet Requirements

Brief description:
ABC holding company needs a portal based solution for their employees to log their
time that they have worked on for auditing purposes. The high level requirements discussed
so far are mentioned below with the assumptions.

The timesheet application will have two(2) roles.

1) Employee:
a. Employee will login to the timesheet portal with credentials that needs to be validated
against an active directory setup.
a. Questions: Does the client want the timesheet application be available via
internet or do they have an intranet (vpn)?
b. We need credentials, to login into the AD server, and also a service account/
application credentials to use during validation of employee.

b. Once Employee logs in, a page displays with a layout which shows the dates of the
current week ( Mon thru Fri ) as 5 rows
c. Each date row will have adjacent columns, Date, Client, Tasks, Desc, and Hours
a. The Clients and Tasks will be populated from DB tables Clients & Tasks
b. The current day/date row will be available for entering data, i.e. pick client, task
from drop downs, enter Description, and hours.
c. Description field validation ?? If employee doesnot enter any description, just
enter a space in the DB field, as it cannot be null.
d. The hours field will be validated to make sure the hours are:
1. Not Null
2. Not zero
3. Not more than 24 hours
d. A provision will be provided next to the Date (ex: a “+” OR a check box) to insert a
new row for that date, into which the employee can enter data.
Note: The properties of the columns of this row will same as 1.c, and the total
hours for that date cannot be more than 24 hours.
Question: How many additional rows can be inserted, say upto 5 for 5 tasks ??
e. When an employee will login to the timesheet 1st time during the middle of the
week, should we let them enter data for any of the rest of the dates in that week?
a. Should we let them enter time for previous dates in that week?
b. Should the columns of those previous date rows be greyed out ?
c. Should employee be able to enter future dates hours ?
f. When an employee will login a 2nd or 3rd .. time during the week, we will populate any
data already entered for previous dates of that week.
a. Should we let them edit previous dates hours?
 b. If they have not entered hours on consecutive dates, say they entered hours on
Monday, and did not login on Tuesday, then when they login on Wednesday
should we let them enter hours for Tuesday?
g. Each time employee inputs hours, there will be a “Total” hours column at the bottom
of the hours, which will show the total hours.
a. Should the Total hours reach 37.5 anytime during the middle of the week, should
we prompt the user that the minimum requirement has reached?
h. Should employee have the ability to:
a. edit any timesheet using an edit button ? If so, is it for the hours of that week
only ?OR can they pick which week timesheet they can edit.
b. View a previous week (posted) timesheet AND cannot edit it ?
c. Request to enter hours for a future week.
i. Should the employee have the ability to view a previous
j. Once employee selects “submit” button, message will appear to display the hours IF
total hours less than 37.5
k. We will give two options:
a. “Continue to submit” (this will post hours even if they are less than 37.5) and
page will close, so they will be logged out to “Login” page.
b. “Cancel submit” will let user edit hours as per criteria we decide in previous
steps. And let user submit hours again, process repeats.
c. If we do not logout, and employee selects Submit button, we will have to validate
if they already entered and as if they want to overwrite etc..

2) Admin
a. Should we have a separate admin login page ?
b. What is the criteria for Authenticating Admin ?
c. Who is an admin, how do we identify:
d. Is it by predefined user-id’s
1. If so should we have a separate column in employees tables for
admin/employee role
b. When Admin will login, we will display a dropdown of employees.
c. Admin will pick an employee and select view hours botton,
d. This will display any hours employee entered.
e. Should we give them an option to view by employee and for certain dates ?
f. Should we have print option OR export option ?
We will have an exit/logout button.

Additional questions:
- Which browsers can use, and versions?? We may know this based on how they access the
application ( internet or intranet (vpn..)). If its onl one browser, its easier, if not we will have
some more work.

High-level tasks completed so far:

- Created login page (dummy account)
- Created landing page with below tasks:
o Auto population of dates of the current week
 o Auto population of Clients from DB tables into dropdown
o Auto population of Tasks from DB tables into dropdown
o Null value catch for Description, and Hours fields
o Added Submit button which:
 Totals hours for the week
 Prompts about hours if less than 37.5
 Insert values into transactions DB table
- Configured IIS
- Published page to IIS

Issues encountered:
- Remote Login issues
- Created new account
- DB tables unavailable
- Data not available / incomplete
- IIS not completely configured