CSC/E1869 GRADING AUDIT TRAIL: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
No edit summary
Line 27: Line 27:


===Expected View===
===Expected View===
Expected view for submission list
[[File:E1869-Screenshot-1.jpg]]


Expected view for review report
[[File:E1869-Screenshot-2.jpg]]
Expected view for grade record
[[File:E1869-Screenshot-3.jpg]]
===Diagram===
===Diagram===
[[File:E1869_Grading_Audit_Trails_UML.jpg]]
[[File:E1869_Grading_Audit_Trails_UML.jpg]]

Revision as of 17:36, 20 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 create a database called grading_history in the system contains elements instructor id, assignment id, grade type, 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: grading_history.rb. Has a list of attributes contains instructor id, assignment id, grade type, student id, grade, comment, and timestamp.
Controller: grading_history_controller.rb. Saves a new entry into database every time a review grade or submission grade is saved
View: index_html.erb. Displays current submission or review's grading history. An existing example of this is submission record in the system.

We also need to modified grades controller, so that every time, a grade is submitted or edited, grading_history_controller.rb will call a method to create a entry saves into database.

Expected View

Expected view for submission list


Expected view for review report


Expected view for grade record

Diagram

Files Changed

Files Added

  • app/models/grading_history.rb
This is a model for grading audit trail, containing attributes of grading history
  • app/controllers/grading_history_controller.rb
This is a controller for grading audit trail, it can add grading history into the system
  • app/views/grading_history/index_html.erb
This is a view for grading audit trail, it will display all grading histories of a submission/review

Files Modified

  • app/controller/grades_controller.rb
Add code to call methods in grading_history_controller.rb to create new grading history

Testing Plan

Functional testing:

For “Review grade”:

1.Log in as instructon

2.Navigate to Manage -> Assignments

3.Click on Review Report

A report with following details will show up: Timestamp, Instructor Id, Assignment id, Grade type, Student id, Grade, Comment

4.Every time an instructor edits or comments on the grade the report is updated with the new entry and timestamp.


For “Submission grade”:

1.Log in as instructor

2. Navigate to Manage -> Assignments

3.Click on View Submission -> History

A report with following details whill show up: Timestamp, Instructor Id, Assignment id, Grade type, Student id, Grade, Comment

4.Every time an instructor edits or comments on the grade the report is updated with the new entry and timestamp.

Reference

Expertiza

Expertiza_wiki

Expertiza Documentation

Expertiza Github