CSC/E1869 GRADING AUDIT TRAIL: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
No edit summary
 
(29 intermediate revisions by 4 users not shown)
Line 7: Line 7:
:2. Comments previously provided by other instructors must also be preserved.
: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.
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:  
Currently, there are two places need to add grading audit trail:  
Line 16: Line 16:


===Design===
===Design===
We will create a database called grading_history in the system contains elements of 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'''.
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.
:Model: grading_history.rb. Has a list of attributes 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
:Controller: grading_history_controller.rb. Saves a new entry into the 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.
:View: index_html.erb. Displays current submission or review's grading history. An existing example of this is a submission record in the system.


=='''Files Changed'''==
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 an entry saves into the database.


===Files Added===
===Expected View===
*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===
==== The list submission page with the new "grade history" option====
* app/controller/grades_controller.rb
[[Image: E1869-Screenshot-1.jpg|50]]
'''Add code to call methods in grading_history_controller.rb to create new grading history'''
 
==== The review report page with the new "grade history" option====
[[File:E1869-Screenshot-2.jpg]]
 
==== Grade history for a given team====
[[File:E1869-Screenshot-3.jpg]]
 
===Diagram===
[[File:E1869_Grading_Audit_Trails_UML.jpg]]


=='''Testing Plan'''==
=='''Testing Plan'''==
Line 40: Line 44:
Functional testing:
Functional testing:


For “Review grade”:
1. Test if SubmissionGradeHistory.create is being called when a submission grade is changed.
  spec/controllers/grades_controller_spec.rb https://bit.ly/2EpJaGS
1.Log in as instructon
 
2. Test if ReviewGradeHistory.create is being called when a submission grade is changed.
  spec/controllers/review_mapping_controller_spec.rb https://bit.ly/2LjM4OF
 
3. Test if GradeHistory.where is being called when grading history button is clicked.
  spec/controllers/grading_histories_controller_test.rb https://bit.ly/2PFLknz
 
=='''Actual Implementation'''==
===Actual View===
== The list submission page with the new "grade history" option==
[[File:E1869-Actual-1.JPG]]
 
 
 
== The Review Report page with the new "grade history" option==
[[File:E1869-Actual-3.png]]
 
 
 
== Grade history page for a given team(submission grade history)==
[[File:E1869-Actual-2.JPG]]
 
 
== Grade history for a given student(review grade history)==
[[File:E1869-Actual-4.png]]
 
===Code Changes===
 
==Files Modified==
*app/controllers/grades_controller.rb https://bit.ly/2Cg9WzR
'''
    Creates a Grading History Record for every Submission grade edited by the instructor for a Team.
'''
 
*app/controllers/review_mapping_controller.rb https://bit.ly/2QywzZc
'''
 
    Creates a Grading History Record for every Review grade edited by the instructor for a Student.
'''


2.Navigate to Manage -> Assignments
* app/views/assignments/list_submissions.html.erb https://bit.ly/2UHNRkO
'''
3.Click on Review Report
    Add code to support view changes for Grade Record
'''


A report with following details will show up:
* app/views/review_mapping/_review_report.html.erb https://bit.ly/2GfTqUj
Timestamp, Instructor Id, Assignment id, Grade type, Student id, Grade, Comment
'''
    Add code to support view changes for Grade Record
'''


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


*app/controllers/grading_histories_controller.rb https://bit.ly/2RY5xa6
'''
    Calls the grading history view after validaing Submission and Review Type.


For “Submission grade”:
'''


1.Log in as instructor
*app/models/grading_history.rb https://bit.ly/2PHKNRY
'''
    Model for Grading History.
'''


2. Navigate to Manage -> Assignments
*app/models/review_grading_history.rb https://bit.ly/2SPNR0e
'''
    Model containing specifics of Review Grading History. Inherits Grading History.
'''


3.Click on View Submission -> History
*app/models/submission_grading_history.rb https://bit.ly/2S5EI3J
'''
    Model containing specifics of Submission Grading History. Inherits Grading History.
'''


A report with following details whill show up:
*app/views/grading_history/index_html.erb https://bit.ly/2rDiZF1
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.
'''
    This is a view for grading audit trail, it will display all grading histories of a submission/review
'''


=='''Reference'''==
=='''Reference'''==

Latest revision as of 17:30, 16 December 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 of 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 the 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 a 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 an entry saves into the database.

Expected View

The list submission page with the new "grade history" option

50

The review report page with the new "grade history" option

Grade history for a given team

Diagram

Testing Plan

Functional testing:

1. Test if SubmissionGradeHistory.create is being called when a submission grade is changed. 

  spec/controllers/grades_controller_spec.rb https://bit.ly/2EpJaGS

2. Test if ReviewGradeHistory.create is being called when a submission grade is changed. 

  spec/controllers/review_mapping_controller_spec.rb https://bit.ly/2LjM4OF

3. Test if GradeHistory.where is being called when grading history button is clicked. 

  spec/controllers/grading_histories_controller_test.rb https://bit.ly/2PFLknz

Actual Implementation

Actual View

The list submission page with the new "grade history" option


The Review Report page with the new "grade history" option


Grade history page for a given team(submission grade history)


Grade history for a given student(review grade history)

Code Changes

Files Modified

    Creates a Grading History Record for every Submission grade edited by the instructor for a Team. 


    Creates a Grading History Record for every Review grade edited by the instructor for a Student.


    Add code to support view changes for Grade Record


    Add code to support view changes for Grade Record

Files Added

    Calls the grading history view after validaing Submission and Review Type.


    Model for Grading History.


    Model containing specifics of Review Grading History. Inherits Grading History.


    Model containing specifics of Submission Grading History. Inherits Grading History.


    This is a view for grading audit trail, it will display all grading histories of a submission/review

Reference

Expertiza

Expertiza_wiki

Expertiza Documentation

Expertiza Github

Retrieved from "https://wiki.expertiza.ncsu.edu/index.php?title=CSC/E1869_GRADING_AUDIT_TRAIL&oldid=121545"