CSC/ECE 517 Fall 2023 - E2383. Grading Audit Trail
Introduction
Problem Statement
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. A grading audit trail must be created and the following information needs to be stored:
- 1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done.
- 2. Comments previously provided by other instructors must also be preserved.
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.
Overview of Major Changes By Previous Teams
E1934
- A new table was added to the database (grading_history), along with the corresponding model (grading_history.rb) and controller (grading_history_controller.rb).
- Whenever an instructor submits a new grade, or edits an existing grade, the grading_history_controller saves a new history entry to the database.
- Two models for specific types of histories were added: review_grading_history.rb, and submission_grading_history.rb.
- A view for displaying the grading history of a particular assignment or review was added (grading_histories/index.html.erb).
E2237
- They fixed some issues that were causing the system to crash during testing
- Altered the Grading History view
- Explained the reasoning for changes made to files using diagrams and justifications