1. Presented By: Katie, Jake, Janet, Marcellous, and Junaid

3. Requirements and Testing for Project

4. Requirement: All employees will have unique user ID and password for web access –Each user would have a login to get access to see or edit the timesheets Test: –Testing the user login access Using each individual user ID and password to see if he/she can login correctly –Using some invalid user ID and password to test if they can login

5. Requirements: The program would have supper (root) accounts, which are the administrators –To modify root account’s information can only be done by the administrator –Modify root account’s schedule can only be done by administrator –Root account can perform all the function that manager can perform

6. Requirements: The manager user can enter and edit hours on the timesheets –The managers will have access to change the timesheets for both manager and employee users –If the employees want to change their schedule they may call managers to change the schedule –The managers cannot modify past schedule –Schedule modification can only be used at least a day before –The managers and employees both can view the timesheets of all employees

7. Requirements: The employees can only read the hour schedule, no access to change the timesheets –The employees can only view schedules –They also can see all the schedules of other employees –If employees want to make changes on their schedules they must request to their managers to change it for them ahead of time

8. Requirements: The managers can add, delete, and modify users –The managers can add users when the company hires new people and delete the users when a person no longer with the company The managers assign user IDs and passwords for new employees

9. Tests: Testing for the different access ability for the different user types –Use all IDs and passwords to see if the users can all see the whole schedule from both the website and cell phones –Use root account ID and password to see if the administrator have the correct ability to change the timesheets and add & delete users –Use the employees’ user IDs and passwords to test if the employees can access and change timesheets or add & delete users –Testing the managers’ IDs and passwords and see if the managers have the correct ability to change timesheets as well as add & delete users

10. Requirements: Pattern for information of creating new users –User Id and password should be at least 4 characters or numbers to maximum 12 characters or numbers – Type of user and overtime must to be clarified –First and last name should be at least 1 character –Birthday has to be in range of 1900 to current, and it should be existing date –Email address should be at least 1 character follows “@” with at least 1 character after then “.” follows at least 1 character –Phone number should be (xxx) xxx-xxxx, you can put either space or not after the brackets Test: –Testing the pattern for the information form Check if any information with incorrect pattern would generate error message

11. Requirements: Accounts’ condition –New employees can modify their information after their first time login with assigned ID and password –After the new user created it will store this and following weeks’ date for the time table –Time table will always store current and next week’s date never stores previous weeks Tests: –Testing format of time table and new account Testing if the time table of current and next weeks’ date would create after the new user being added Testing if the time table will delete the pass week time table and update it to current and next weeks’ date Testing if the new user can modify he/she information after first login with assigned ID and password

12. Requirements: Website has to be user-friendly –The website should be easy to view and clearly understandable for users Test: –Check the project on computers and cell phones Access the project on several main computers to see if it looks nice on the screen Access the project on several cell phones to see if it looks easy to use

13. Requirements: The modification of the timesheets can only be done on main computers not on cell phones –The managers can only change the timesheet on their office computers –They won’t be able to change the timesheet with their cell phones Test: –Testing if the managers can change the timesheets on cell phones Testing managers’ user IDs and passwords on cell phones access to make sure that they can’t change schedules on cell phones They can only view the schedules

14. Requirements: The change of timesheet should follow the labor law in the state of employment –All employees who are under 16 should follow the Illinois labor laws –All employees should have at least one day off in a week –Most employees (except the type of employees in the law exception specified) should not work over 40 hours per week unless the company will pay them overtime pay on the hours over 40 hours Test: –Testing the schedules’ changing limitation on main computers Managers can only change schedule at least a day before Managers can only add hours to the employee, who is overtime pay type, when he/she has less 40 hours per pay week, otherwise, the managers would be notified that the company needs to pay the employee with overtime pay Managers cannot assign the employee any shift on the day the employee had been scheduled off after every Sunday of the week Managers can only schedule for the employees under 16 years of age 3 hours at school days during 7:00 am ~ 7:00 pm period and 8 hours during 7:00 am ~ 9:00 pm at June 1st to August 31st.

15. Requirements: Training is necessary for all users to use –Teach users the knowledge of using internet –Training all users how to use IDs and passwords to access the timesheet –Training managers how to modify timesheets and add or delete users Test: –Teach some users outside of our group to use the project Train some outside users to use the project to see if they can use the project well Testing if the training is well organized for users to understand

16. Requirements: Employees can have one shift per day –All employee should only have one shift on each day –There’s no overnight shift applied in this program Test: –Testing for adding shift Each employee can only work one shift on each day There’s not overnight schedule allowed If the employee is scheduled on the day, the manager would unable to add another schedule to the same employee for the same day

17. Overview Requirements The program would have supper (root) accounts, which are the administrators All employees will have unique user ID and password for web access The manager users can enter and edit hours on timesheets The employee can only read the hours schedule Managers can add and delete users Modification of the timesheets can only be done on main computer not on cell phones Website has to be user-friendly The change of timesheet should follow the labor law in the state of employment The training is necessary for all users to use this program Employees can have one shift per day Accounts’ condition Pattern for information of creating new users Testing Testing of the user login access Testing for different access ability for the different type of user Testing if the managers can change the timesheets on their cell phones Testing if the managers can change the timesheet on office computers Check the project on office computers and cell phones Testing the schedules’ changing limitation on main computers Teach some users outside our group to use the project Testing for make sure that one shift can be add when employees have schedule Testing format of time table and new account Testing the pattern for the information form