-The project is a competition between both teams, and there will be a "best team" award with some sort of prize at the end of the class.
-The age limit of enrolling students is 5 years old. Any child 6 or older will not be permitted into the day care center.
-An Immunization Record will include fields such as the Child ID, Child name, parent phone #, Immunization type, Due Date, and additional comments.
-Number of and permissions of different access levels are up to the design team. The following access levels have been suggested by the professor:
-Group 1 – Admin
-no limitations – can view, update, and delete any and all information
-Group 2 – Teacher
-can view all information, but cannot update or delete information
-Group 3 – Parent
-can view only their own account – no updates can be made
-The access levels themselves and their privelages will be hard-coded into the system - however, each time an employee is added to the system their access level will be selected by the administrator.
-Tuition will be charged monthly and at a fixed rate for all children. The cost scheme will be as follows:
-1st child - $300/month
-2nd child - $250/month
-Each additional child - $150/month
-If an incorrect login is given, the login prompt will be repeated indefinitely (there will be no lockout after a certain number of incorrect login attempts).
-For "activities" for each class, the following should be included:
-Field trip
-Book Fair
-Crazy Hat Day
-etc.
-The Class table should include the following:
-Class ID
-Class name
-Student limit (limit imposed is 20 students per class)
-Room number
-The classes should be set up as follows:
Age 0-2 – Infant class
Age 3 - Toddler class
Age 4-6 – Pre-K class
-A waiting list for full classes is OPTIONAL.
-A child must have completed a physical exam to be allowed to enroll in any class (this can be a simple yes/no prompt when enrolling a child).
-Logging the time of pickup and person picking child up is OPTIONAL.
-The following information concerning Employees should be kept:
-Employee ID
-Employee name
-Hire date
-Access level
-A tuition scheme based on the child's attendance is OPTIONAL.
-Customer accounts should NOT be deleted due to inactivity—however, inactive accounts should not show up in reports.
-Payment information should include the method of payment (Cash, Check, Credit, etc);
-The Operating System the software runs on is up to the development team.
-The status of each child (Active, Inactive, etc.) should be recorded.
-A child's information should include the child's gender, birth date, etc.
-No emails should be sent to parents unless they concern urgent billing issues (such as payments due, late payments, etc).
-Charging late fees for overdue payments is OPTIONAL.
-The system should have the capability to enroll a new employee, however recording the employees' payroll information is OPTIONAL.
- An online solution must support multiple machines accessing the system simultaneously.