Project Marking Requirements

Your project will be marked in class in the last week of the term. As Dale is away Elise will be taking all the classes except the Wednesday 3-5 class, this is staffed by a senior student but he cannot mark your work.

Please install all files on kate (make sure your database tables are populated with the required data). Also you must be backing up every session in your gitlab repository

Read the presentation Project.pptx this will be continually updated as requirements are tweaked.

Your site must provide (at a minimum) the following functionality:

1. Record the completed checkpoint for an individual student
2. Record data for the three tools (the students may skip all or one of the questions)
3. Show the completed labs for a given student (currently we ask for student id number)

4. Set up the database tables starting with the attached spreadsheet
5. Insert a new student not in the original spreadsheet
6. Delete a student
7. Staff registration form: create new administrators
8. User login (multiple staff user site)
9. Tabular view of all students and what labs they have completed.
10. Scatter graphs for each tool: Interest vs Difficulty, Plan vs Familiarity, Satisfaction vs Improvement by lab number for all students (each dot is a student)
11. Scatter graphs (3) as above but for an individual over all labs
12. Line graphs (6) for an individual student, for a particular scale, (x axis contains the lab number 1-25)
13. Class average response over all labs per scale descriptor (6)

For testing and setup purposes you are required to have the following two files. createTables this is where you create all the tables. showTables this is for testing purposes you must show all fields and all records in all tables.

Hard code a staff user: login name dale password minttimtams

This gives me access to your site to check your progress.

1. List any functionality you intend to provide additional to that listed above
2. List or sketch (just little boxes will do – just give each one a name so you can refer to it below) the individual screens you will provide in your site. Make sure that you have the necessary screens for all of the functionality required.
3. In the table below, list all the screens you are building, as named above. For each screen, give the name of the file which will produce the html for that screen. Name the controller file that includes these screens.
4. List any additional utility files (i.e. files that don’t actually produce any screens, but just perform work). Examples are your dbConnect include file and any function libraries. For each listed file, briefly describe its purpose.
5. In the table below, list each functional element you are going to provide that requires user input. For each function listed, name the screen(s) the user will see when providing that input. For each screen, list all the input controls on the screen (don’t forget the submit buttons) with their type, name and value properties as they will appear in the generated tag.
6. In the table below, list each functional element you are going to provide that requires user input. For each function listed, write out the mySQL query or queries that you will perform to support the functionality. Refer to the database tables described in your design document. Check that the controls you listed in Table 5 will enable you to perform all the queries listed here.
7. List any additional queries you will perform on your database that are not directly tied to the processing of user input. For each query, briefly describe its purpose.
8. For each file you described in parts 3 and 4 above, list the data variables that will be stored in and/or retrieved from the $_SESSION array.
9. For each file you described in parts 3 and 4 above, list all the data validation that you will perform. For each data element, give its local variable name, the name of the file which produces the html for the associated input control, the name of the data element in $_POST (i.e. its associative index in the $_POST array) and the type of validation to be performed. Give the php statement you will use to validate it or a description
10. Sketch your database model