CSC/E1869 GRADING AUDIT TRAIL: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
(Created page with "=='''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 crea...")
 
No edit summary
Line 16: Line 16:


===Design===
===Design===
We want to create two new models '''Review_Grade_History''' and '''Submission_Grade_History''', each will have a database contains instructor id, assignment id, student id, grade, comment, and timestamp.
We will use MVC design to create a model, a controller, and a view for both of '''Review Grade''' and '''Submission Grade'''.
 
:Model: has a database contains instructor id, assignment id, grade type, student id, grade, comment, and timestamp.
:Controller: saves a new entry into database every time a review grade or submission grade is saved
:View: displays current submission or review's grading history. An existing example of this is submission record in the system.

Revision as of 02:46, 14 November 2018

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.

Currently, there are two places need to add grading audit trail:

1. Review grade: Log in as instructor -> Manage -> Assignments -> View Review Report
2. Submission grade: Log in as instructor -> Manage -> Assignments -> View submissions

Proposed Solution

Design

We will use MVC design to create a model, a controller, and a view for both of Review Grade and Submission Grade.

Model: has a database contains instructor id, assignment id, grade type, student id, grade, comment, and timestamp.
Controller: saves a new entry into database every time a review grade or submission grade is saved
View: displays current submission or review's grading history. An existing example of this is submission record in the system.