Assessment system created using the Django web framework

I divided the Assessment System app into two pages.

The front-end page first asks the user to choose a semester, followed by a class followed by a student who is enrolled in that class. After the user completes the rubric for the student, the user is taken back to the class page so the user can continue filling out rubrics for the course. All rubrics must be completed in full before the user is allowed to submit.

Based upon how the class is setup from the admin page, certain users (e.g. teachers) are only allowed to see certain classes. This restriction ensures that users are not filling out rubrics for which they are not associated.

Accessing the /assessment/ page requires a login for the application

The application's data page gives the user three viewing options. The first option allows the user to choose a student and then choose the course for which a professor or teacher has completed a rubric. The second option allows the user to choose a semester and then choose class associated with that semester. The class page will show aggregated rubric data and will show how many data points the aggregated rubric data represents. Access to the data view requires an administrative account.

The third viewing option gives the user the ability to see which standards are associated with which rubric row. If the user would like to see scores for the row, they will have to choose a semester and a standard. However, if the user wants to see which rows in which rubrics are associated with which standards, they will need to choose the link "See what rubrics use what standards".

The admin page, accessible by administrative user only, allows the user to create different models based upon the needs of the user. The different models are below:

A model that represents a single entity of a class. The class creation requires a unique identification number (i.e. crn), a subject, a course number (maximum four characters), a section number and a teacher associated with the course.

A model that allows the user to associate an assignment with each class. The assignment must link to the assignment name and the edclass name. The assignment can also have a keyrubric associated with it.

An intermediate model that represents a particular students enrollment in a class and semester. If the rubric needs to be edited after submission, you will need to disable rubric completed and resubmit the rubric.

The rubric model allows the user to create a rubric to be used for each course. The rubric model consists of rows where the user can edit the name of the row and add descriptive text for each row/column intersection. The user must enable the "Template" box to allow the rubric to be used in a course. The template box differentiate's the blank rubric from a student's completed rubric (both based on the same model). Rubric rows cannot be edited after creation; however, rows can be added to rubrics after rubric creation.

This model houses metadata about each completed rubric. Each RubricData object is associated with an enrollment object and assignment object. The RubricData object can also be linked to a completed rubric and boolean value which tells the system where the student in the associated enrollment has completed the assignment or not.

A model that represents a particular semester.

A model that represents a student instance. The student model includes a first name, last name and a student identification number (i.e. Lnumber). Student instances can be deleted or edited, but this is highly discouraged.

A model that represents standards associated with rubric rows. The user can choose more than one standard per row or they can choose none.