<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.expertiza.ncsu.edu/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Ghou3</id>
	<title>Expertiza_Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.expertiza.ncsu.edu/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Ghou3"/>
	<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Special:Contributions/Ghou3"/>
	<updated>2026-07-17T22:34:20Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.41.0</generator>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142872</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142872"/>
		<updated>2021-12-20T21:52:36Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* 1. grades_controller.rb */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Code changes ===&lt;br /&gt;
====1. \app\controllers\grades_controller.rb====&lt;br /&gt;
Add create submission record function&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
GradingHistory.create(instructor_id: session[:user].id,&lt;br /&gt;
  assignment_id: participant.assignment.id,&lt;br /&gt;
  grading_type: &amp;quot;Submission&amp;quot;,&lt;br /&gt;
  grade_receiver_id: @team.id,&lt;br /&gt;
  grade: @team.grade_for_submission,&lt;br /&gt;
  comment: @team.comment_for_submission)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====2. \app\controllers\grading_histories_controller.rb====&lt;br /&gt;
Create grading_histories_controller.rb&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
class GradingHistoriesController &amp;lt; ApplicationController&lt;br /&gt;
    before_action :set_grading_history, only: %i[show]&lt;br /&gt;
  &lt;br /&gt;
    def action_allowed?&lt;br /&gt;
      return true if ['Super-Administrator', 'Administrator'].include? current_role_name&lt;br /&gt;
      check_type(params[:grade_type])&lt;br /&gt;
      if @assignment.instructor_id == current_user.id&lt;br /&gt;
        true&lt;br /&gt;
      elsif TaMapping.exists?(ta_id: current_user.id, course_id: @assignment.course_id) &amp;amp;&amp;amp;&lt;br /&gt;
          (TaMapping.where(course_id: @assignment.course_id).include? TaMapping.where(ta_id: current_user.id, course_id: @assignment.course_id).first)&lt;br /&gt;
        true&lt;br /&gt;
      elsif @assignment.course_id &amp;amp;&amp;amp; Course.find(@assignment.course_id).instructor_id == current_user.id&lt;br /&gt;
        true&lt;br /&gt;
      end&lt;br /&gt;
    end&lt;br /&gt;
  &lt;br /&gt;
  &lt;br /&gt;
    def check_type(type)&lt;br /&gt;
      if type.eql? &amp;quot;Submission&amp;quot;&lt;br /&gt;
        assignment_team = AssignmentTeam.find(params[:grade_receiver_id])&lt;br /&gt;
        @assignment = Assignment.find(assignment_team.parent_id)&lt;br /&gt;
      end&lt;br /&gt;
      if type.eql? &amp;quot;Review&amp;quot;&lt;br /&gt;
        participant_id = params[:participant_id]&lt;br /&gt;
        grade_receiver = AssignmentParticipant.find(participant_id)&lt;br /&gt;
        @assignment = Assignment.find(grade_receiver.parent_id)&lt;br /&gt;
      end&lt;br /&gt;
    end&lt;br /&gt;
  &lt;br /&gt;
    def index&lt;br /&gt;
      @grading_histories = GradingHistory.where(grade_receiver_id: params[:grade_receiver_id], grading_type: params[:grade_type]).reverse_order&lt;br /&gt;
    end&lt;br /&gt;
  end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====3. \app\controllers\review_mapping_controller.rb====&lt;br /&gt;
Add create review record function&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
GradingHistory.create(instructor_id: session[:user].id,&lt;br /&gt;
  assignment_id: params[:assignment_id],&lt;br /&gt;
  grading_type: &amp;quot;Review&amp;quot;,&lt;br /&gt;
  grade_receiver_id: Participant.find(params[:participant_id]).user_id,&lt;br /&gt;
  grade: params[:grade_for_reviewer],&lt;br /&gt;
  comment: params[:comment_for_reviewer])&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====4. \app\helpers\grading_histories_helper.rb====&lt;br /&gt;
Create grading_histories_helper.rb&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
module GradingHistoriesHelper&lt;br /&gt;
end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====5. \app\models\grading_history.rb====&lt;br /&gt;
Create grading_history.rb&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
class GradingHistory &amp;lt; ActiveRecord::Base&lt;br /&gt;
  attr_protected&lt;br /&gt;
    belongs_to :instructor, inverse_of: :instructor_id&lt;br /&gt;
    belongs_to :assignment, inverse_of: :assignment_id&lt;br /&gt;
end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====6. \app\models\review_grading_history.rb====&lt;br /&gt;
Create review_grading_history.rb&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
class ReviewGradingHistory &amp;lt; GradingHistory&lt;br /&gt;
  attr_protected&lt;br /&gt;
    belongs_to :grade_receiver, class_name: 'Participant', inverse_of: :grade_receiver_id&lt;br /&gt;
end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====7. \app\models\submission_grading_history.rb====&lt;br /&gt;
Create submission_grading_history.rb&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
class SubmissionGradingHistory &amp;lt; GradingHistory&lt;br /&gt;
  attr_protected&lt;br /&gt;
    belongs_to :grade_receiver, class_name: 'Team', inverse_of: :grade_receiver_id&lt;br /&gt;
end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====8. \app\views\assignments\list_submissions.html.erb====&lt;br /&gt;
Add &amp;quot;Grading History&amp;quot; link to submissions page&lt;br /&gt;
====9. \app\views\grading_histories\index.html.erb====&lt;br /&gt;
Create grading histories index page&lt;br /&gt;
====10. \app\views\reports\_review_report.html.erb====&lt;br /&gt;
Add &amp;quot;Grading History&amp;quot; link to review report page&lt;br /&gt;
====11. \config\routes.rb====&lt;br /&gt;
Configure the routes&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
resources :grading_histories, only: [:index]&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
====12. \app\views\assignments\list_submissions.html.erb====&lt;br /&gt;
Create table grading_histories&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
class CreateGradingHistories &amp;lt; ActiveRecord::Migration&lt;br /&gt;
  def change&lt;br /&gt;
    create_table :grading_histories do |t|&lt;br /&gt;
       t.integer :instructor_id&lt;br /&gt;
       t.integer :assignment_id&lt;br /&gt;
       t.string  :grading_type&lt;br /&gt;
       t.integer :grade_receiver_id&lt;br /&gt;
       t.integer :grade&lt;br /&gt;
       t.text :comment&lt;br /&gt;
       t.timestamps null: false&lt;br /&gt;
     end&lt;br /&gt;
  end&lt;br /&gt;
end&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
To start the test, we need to log in as instructor or TA first. These accounts should have access to the assignment. For example: we can use '''intructor6/password''' or '''teaching_assistant8631/password''';&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1: Grading histories of submissions ====&lt;br /&gt;
Step 1. Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_view_submisson.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 2. The instructor/TA can assign grades to a team by clicking 'Assign Grade' in the 'Team name' column:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_submisson1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 3. The instructor/TA can view the grading audit trail by clicking 'Grading History' in the 'History' column, here is the record page:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_submisson2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==== Scenario 2: Grading histories of reviews ====&lt;br /&gt;
Step 1. Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Reports&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_view_report.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 2. Select 'Review Report' then click 'View', here is the Review Report page. The instructor/TA can assign grades to a review by inputing 'Grade' and 'Comment' then clicking 'Save' button:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_report1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 3. The instructor/TA can view the grading audit trail by clicking 'Grading History' as Step 2 figure shows, here is the record page:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_report2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2164 Pull Request]&lt;br /&gt;
#[https://www.youtube.com/watch?v=ad4wF6--5dQ Test1]&lt;br /&gt;
#[https://youtu.be/8PWD5gNQFog Test2]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142871</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142871"/>
		<updated>2021-12-20T21:19:54Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Code changes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Code changes ===&lt;br /&gt;
====1. grades_controller.rb====&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
GradingHistory.create(instructor_id: session[:user].id,&lt;br /&gt;
  assignment_id: participant.assignment.id,&lt;br /&gt;
  grading_type: &amp;quot;Submission&amp;quot;,&lt;br /&gt;
  grade_receiver_id: @team.id,&lt;br /&gt;
  grade: @team.grade_for_submission,&lt;br /&gt;
  comment: @team.comment_for_submission)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
To start the test, we need to log in as instructor or TA first. These accounts should have access to the assignment. For example: we can use '''intructor6/password''' or '''teaching_assistant8631/password''';&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1: Grading histories of submissions ====&lt;br /&gt;
Step 1. Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_view_submisson.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 2. The instructor/TA can assign grades to a team by clicking 'Assign Grade' in the 'Team name' column:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_submisson1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 3. The instructor/TA can view the grading audit trail by clicking 'Grading History' in the 'History' column, here is the record page:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_submisson2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==== Scenario 2: Grading histories of reviews ====&lt;br /&gt;
Step 1. Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Reports&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_view_report.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 2. Select 'Review Report' then click 'View', here is the Review Report page. The instructor/TA can assign grades to a review by inputing 'Grade' and 'Comment' then clicking 'Save' button:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_report1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 3. The instructor/TA can view the grading audit trail by clicking 'Grading History' as Step 2 figure shows, here is the record page:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_report2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2164 Pull Request]&lt;br /&gt;
#[https://www.youtube.com/watch?v=ad4wF6--5dQ Test1]&lt;br /&gt;
#[https://youtu.be/8PWD5gNQFog Test2]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142870</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142870"/>
		<updated>2021-12-20T21:19:38Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Code changes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Code changes ===&lt;br /&gt;
1. grades_controller.rb&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
GradingHistory.create(instructor_id: session[:user].id,&lt;br /&gt;
  assignment_id: participant.assignment.id,&lt;br /&gt;
  grading_type: &amp;quot;Submission&amp;quot;,&lt;br /&gt;
  grade_receiver_id: @team.id,&lt;br /&gt;
  grade: @team.grade_for_submission,&lt;br /&gt;
  comment: @team.comment_for_submission)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
To start the test, we need to log in as instructor or TA first. These accounts should have access to the assignment. For example: we can use '''intructor6/password''' or '''teaching_assistant8631/password''';&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1: Grading histories of submissions ====&lt;br /&gt;
Step 1. Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_view_submisson.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 2. The instructor/TA can assign grades to a team by clicking 'Assign Grade' in the 'Team name' column:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_submisson1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 3. The instructor/TA can view the grading audit trail by clicking 'Grading History' in the 'History' column, here is the record page:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_submisson2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==== Scenario 2: Grading histories of reviews ====&lt;br /&gt;
Step 1. Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Reports&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_view_report.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 2. Select 'Review Report' then click 'View', here is the Review Report page. The instructor/TA can assign grades to a review by inputing 'Grade' and 'Comment' then clicking 'Save' button:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_report1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 3. The instructor/TA can view the grading audit trail by clicking 'Grading History' as Step 2 figure shows, here is the record page:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_report2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2164 Pull Request]&lt;br /&gt;
#[https://www.youtube.com/watch?v=ad4wF6--5dQ Test1]&lt;br /&gt;
#[https://youtu.be/8PWD5gNQFog Test2]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142869</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142869"/>
		<updated>2021-12-20T21:18:18Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Code changes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Code changes ===&lt;br /&gt;
1. grades_controller.rb&lt;br /&gt;
      GradingHistory.create(instructor_id: session[:user].id,&lt;br /&gt;
        assignment_id: participant.assignment.id,&lt;br /&gt;
        grading_type: &amp;quot;Submission&amp;quot;,&lt;br /&gt;
        grade_receiver_id: @team.id,&lt;br /&gt;
        grade: @team.grade_for_submission,&lt;br /&gt;
        comment: @team.comment_for_submission)&lt;br /&gt;
&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
To start the test, we need to log in as instructor or TA first. These accounts should have access to the assignment. For example: we can use '''intructor6/password''' or '''teaching_assistant8631/password''';&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1: Grading histories of submissions ====&lt;br /&gt;
Step 1. Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_view_submisson.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 2. The instructor/TA can assign grades to a team by clicking 'Assign Grade' in the 'Team name' column:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_submisson1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 3. The instructor/TA can view the grading audit trail by clicking 'Grading History' in the 'History' column, here is the record page:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_submisson2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==== Scenario 2: Grading histories of reviews ====&lt;br /&gt;
Step 1. Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Reports&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_view_report.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 2. Select 'Review Report' then click 'View', here is the Review Report page. The instructor/TA can assign grades to a review by inputing 'Grade' and 'Comment' then clicking 'Save' button:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_report1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 3. The instructor/TA can view the grading audit trail by clicking 'Grading History' as Step 2 figure shows, here is the record page:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_report2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2164 Pull Request]&lt;br /&gt;
#[https://www.youtube.com/watch?v=ad4wF6--5dQ Test1]&lt;br /&gt;
#[https://youtu.be/8PWD5gNQFog Test2]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142721</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142721"/>
		<updated>2021-12-05T02:43:38Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Code changes ===&lt;br /&gt;
&lt;br /&gt;
  # code changes will be added here&lt;br /&gt;
&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
To start the test, we need to log in as instructor or TA first. These accounts should have access to the assignment. For example: we can use '''intructor6/password''' or '''teaching_assistant8631/password''';&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1: Grading histories of submissions ====&lt;br /&gt;
Step 1. Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_view_submisson.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 2. The instructor/TA can assign grades to a team by clicking 'Assign Grade' in the 'Team name' column:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_submisson1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 3. The instructor/TA can view the grading audit trail by clicking 'Grading History' in the 'History' column, here is the record page:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_submisson2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==== Scenario 2: Grading histories of reviews ====&lt;br /&gt;
Step 1. Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Reports&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_view_report.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 2. Select 'Review Report' then click 'View', here is the Review Report page. The instructor/TA can assign grades to a review by inputing 'Grade' and 'Comment' then clicking 'Save' button:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_report1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 3. The instructor/TA can view the grading audit trail by clicking 'Grading History' as Step 2 figure shows, here is the record page:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_report2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2164 Pull Request]&lt;br /&gt;
#[https://www.youtube.com/watch?v=ad4wF6--5dQ Test1]&lt;br /&gt;
#[https://youtu.be/8PWD5gNQFog Test2]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142172</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142172"/>
		<updated>2021-11-30T01:25:45Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Manual UI Tests */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
To start the test, we need to log in as instructor or TA first. These accounts should have access to the assignment. For example: we can use '''intructor6/password''' or '''teaching_assistant8631/password''';&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1: Grading histories of submissions ====&lt;br /&gt;
Step 1. Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_view_submisson.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 2. The instructor/TA can assign grades to a team by clicking 'Assign Grade' in the 'Team name' column:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_submisson1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 3. The instructor/TA can view the grading audit trail by clicking 'Grading History' in the 'History' column, here is the record page:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_submisson2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==== Scenario 2: Grading histories of reviews ====&lt;br /&gt;
Step 1. Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Reports&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_view_report.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 2. Select 'Review Report' then click 'View', here is the Review Report page. The instructor/TA can assign grades to a review by inputing 'Grade' and 'Comment' then clicking 'Save' button:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_report1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 3. The instructor/TA can view the grading audit trail by clicking 'Grading History' as Step 2 figure shows, here is the record page:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_grading_history_report2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142150</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142150"/>
		<updated>2021-11-30T01:08:42Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Manual UI Tests */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
To start the test, we need to log in as instructor or TA first. These accounts should have access to the assignment. For example: we can use '''intructor6/password''' or '''teaching_assistant8631/password''';&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1: Grading histories of reviews ====&lt;br /&gt;
Step 1. Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_view_submisson.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 2. &lt;br /&gt;
&lt;br /&gt;
==== Scenario 2: Grading histories of submissions ====&lt;br /&gt;
Step 1. Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Reports&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_view_report.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 2.&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142148</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142148"/>
		<updated>2021-11-30T01:07:44Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Manual UI Tests */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
To start the test, we need to log in as instructor or TA first. These accounts should have access to the assignment. For example: we can use '''intructor6/password''' or '''teaching_assistant8631/password''';&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1: Grading histories of reviews ====&lt;br /&gt;
Step 1. Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_view_submisson.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Step 2. &lt;br /&gt;
&lt;br /&gt;
==== Scenario 2: Grading histories of submissions ====&lt;br /&gt;
Step 1. Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Reports&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_view_report.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Step 2.&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142147</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142147"/>
		<updated>2021-11-30T01:07:05Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Manual UI Tests */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
To start the test, we need to log in as instructor or TA first. These accounts should have access to the assignment. For example: we can use '''intructor6/password''' or '''teaching_assistant8631/password''';&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1: Grading histories of reviews ====&lt;br /&gt;
Step 1. Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
[[File:E2158_view_submisson.png|1100px]]&lt;br /&gt;
&lt;br /&gt;
Step 2. &lt;br /&gt;
&lt;br /&gt;
==== Scenario 2: Grading histories of submissions ====&lt;br /&gt;
Step 1. Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Reports&lt;br /&gt;
[[File:E2158_view_report.png|1100px]]&lt;br /&gt;
&lt;br /&gt;
Step 2.&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142143</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142143"/>
		<updated>2021-11-30T01:03:40Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Manual UI Tests */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
To start the test, we need to log in as instructor or TA first. These accounts should have access to the assignment. For example: we can use '''intructor6/password''' or '''teaching_assistant8631/password''';&lt;br /&gt;
&lt;br /&gt;
1. Review grade: Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Reports&lt;br /&gt;
&lt;br /&gt;
2. Submission grade: Log in as instructor/TA -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1: Grading histories of submissions ====&lt;br /&gt;
    Step 1.&lt;br /&gt;
    Step 2.&lt;br /&gt;
&lt;br /&gt;
==== Scenario 2: Grading histories of reviews ====&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:E2158_view_submisson.png&amp;diff=142134</id>
		<title>File:E2158 view submisson.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:E2158_view_submisson.png&amp;diff=142134"/>
		<updated>2021-11-30T00:57:29Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:E2158_view_report.png&amp;diff=142133</id>
		<title>File:E2158 view report.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:E2158_view_report.png&amp;diff=142133"/>
		<updated>2021-11-30T00:57:18Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:E2158_grading_history_submisson2.png&amp;diff=142131</id>
		<title>File:E2158 grading history submisson2.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:E2158_grading_history_submisson2.png&amp;diff=142131"/>
		<updated>2021-11-30T00:57:08Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:E2158_grading_history_submisson1.png&amp;diff=142129</id>
		<title>File:E2158 grading history submisson1.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:E2158_grading_history_submisson1.png&amp;diff=142129"/>
		<updated>2021-11-30T00:56:53Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:E2158_grading_history_report2.png&amp;diff=142128</id>
		<title>File:E2158 grading history report2.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:E2158_grading_history_report2.png&amp;diff=142128"/>
		<updated>2021-11-30T00:56:43Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:E2158_grading_history_report1.png&amp;diff=142127</id>
		<title>File:E2158 grading history report1.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:E2158_grading_history_report1.png&amp;diff=142127"/>
		<updated>2021-11-30T00:56:28Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142126</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142126"/>
		<updated>2021-11-30T00:56:06Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Scenario 2 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
The new features of recording and showing the history of grades and comments of reviews and submissions will be manually tested after we finished the implementation of those functions.&lt;br /&gt;
&lt;br /&gt;
Since we are stilling working on the project, the screenshots and some edge test cases will be added when our code is finished.&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1: Grading histories of submissions ====&lt;br /&gt;
    Step 1. Log in with a instructor's or TA's account which has access to the assignment, in this example we use '''intructor6/password''';&lt;br /&gt;
    Step 2.&lt;br /&gt;
&lt;br /&gt;
==== Scenario 2: Grading histories of reviews ====&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142117</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142117"/>
		<updated>2021-11-30T00:54:18Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Scenario 1: Grading histories of submissions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
The new features of recording and showing the history of grades and comments of reviews and submissions will be manually tested after we finished the implementation of those functions.&lt;br /&gt;
&lt;br /&gt;
Since we are stilling working on the project, the screenshots and some edge test cases will be added when our code is finished.&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1: Grading histories of submissions ====&lt;br /&gt;
    Step 1. Log in with a instructor's or TA's account which has access to the assignment, in this example we use '''intructor6/password''';&lt;br /&gt;
    Step 2.&lt;br /&gt;
&lt;br /&gt;
==== Scenario 2 ====&lt;br /&gt;
An assignment and 3 teams will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. For each team: 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. For each team: 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142115</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=142115"/>
		<updated>2021-11-30T00:53:54Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Scenario 1 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
The new features of recording and showing the history of grades and comments of reviews and submissions will be manually tested after we finished the implementation of those functions.&lt;br /&gt;
&lt;br /&gt;
Since we are stilling working on the project, the screenshots and some edge test cases will be added when our code is finished.&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1: Grading histories of submissions ====&lt;br /&gt;
    Step 1. Log in with a instructor's or TA's account which has access to the assignment, in this example we use **intructor6/password**;&lt;br /&gt;
    Step 2.&lt;br /&gt;
&lt;br /&gt;
==== Scenario 2 ====&lt;br /&gt;
An assignment and 3 teams will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. For each team: 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. For each team: 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141592</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141592"/>
		<updated>2021-11-10T17:41:33Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Expected View */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
The new features of recording and showing the history of grades and comments of reviews and submissions will be manually tested after we finished the implementation of those functions.&lt;br /&gt;
&lt;br /&gt;
Since we are stilling working on the project, the screenshots and some edge test cases will be added when our code is finished.&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1 ====&lt;br /&gt;
An assignment and a team will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
==== Scenario 2 ====&lt;br /&gt;
An assignment and 3 teams will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. For each team: 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. For each team: 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141591</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141591"/>
		<updated>2021-11-10T17:41:22Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Expected View */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1200px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
The new features of recording and showing the history of grades and comments of reviews and submissions will be manually tested after we finished the implementation of those functions.&lt;br /&gt;
&lt;br /&gt;
Since we are stilling working on the project, the screenshots and some edge test cases will be added when our code is finished.&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1 ====&lt;br /&gt;
An assignment and a team will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
==== Scenario 2 ====&lt;br /&gt;
An assignment and 3 teams will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. For each team: 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. For each team: 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:E2158_Proposed_Solution_3.png&amp;diff=141590</id>
		<title>File:E2158 Proposed Solution 3.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:E2158_Proposed_Solution_3.png&amp;diff=141590"/>
		<updated>2021-11-10T17:40:32Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: Ghou3 uploaded a new version of File:E2158 Proposed Solution 3.png&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141567</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141567"/>
		<updated>2021-11-09T20:39:52Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Expected View */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
The new features of recording and showing the history of grades and comments of reviews and submissions will be manually tested after we finished the implementation of those functions.&lt;br /&gt;
&lt;br /&gt;
Since we are stilling working on the project, the screenshots and some edge test cases will be added when our code is finished.&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1 ====&lt;br /&gt;
An assignment and a team will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
==== Scenario 2 ====&lt;br /&gt;
An assignment and 3 teams will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. For each team: 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. For each team: 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141566</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141566"/>
		<updated>2021-11-09T20:39:19Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Expected View */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px]]&lt;br /&gt;
&amp;lt;/br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px]]&lt;br /&gt;
&amp;lt;/br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px]]&lt;br /&gt;
&amp;lt;/br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
The new features of recording and showing the history of grades and comments of reviews and submissions will be manually tested after we finished the implementation of those functions.&lt;br /&gt;
&lt;br /&gt;
Since we are stilling working on the project, the screenshots and some edge test cases will be added when our code is finished.&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1 ====&lt;br /&gt;
An assignment and a team will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
==== Scenario 2 ====&lt;br /&gt;
An assignment and 3 teams will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. For each team: 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. For each team: 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141565</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141565"/>
		<updated>2021-11-09T20:37:24Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Manual UI Tests */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px|center]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
The new features of recording and showing the history of grades and comments of reviews and submissions will be manually tested after we finished the implementation of those functions.&lt;br /&gt;
&lt;br /&gt;
Since we are stilling working on the project, the screenshots and some edge test cases will be added when our code is finished.&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1 ====&lt;br /&gt;
An assignment and a team will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
==== Scenario 2 ====&lt;br /&gt;
An assignment and 3 teams will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. For each team: 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. For each team: 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141564</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141564"/>
		<updated>2021-11-09T20:37:02Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Manual UI Tests */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px|center]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
The new features of recording and showing the history of grades and comments of reviews and submissions will be manually tested after we finished the implementation of those functions.&lt;br /&gt;
Since we are stilling working on the project, the screenshots and some edge test cases will be added when our code is finished.&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1 ====&lt;br /&gt;
An assignment and a team will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
==== Scenario 2 ====&lt;br /&gt;
An assignment and 3 teams will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. For each team: 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. For each team: 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141563</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141563"/>
		<updated>2021-11-09T20:25:27Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Scenario 2 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px|center]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
The new features of recording and showing the history of grades and comments of reviews and submissions will be manually tested after we finished the implementation of those functions.&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1 ====&lt;br /&gt;
An assignment and a team will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
==== Scenario 2 ====&lt;br /&gt;
An assignment and 3 teams will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. For each team: 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. For each team: 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
    ...&lt;br /&gt;
&lt;br /&gt;
Since We are stilling working on the project, the screenshots and some edge test cases will be added when our code is finished.&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141562</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141562"/>
		<updated>2021-11-09T20:23:06Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Scenerio 1 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px|center]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
The new features of recording and showing the history of grades and comments of reviews and submissions will be manually tested after we finished the implementation of those functions.&lt;br /&gt;
&lt;br /&gt;
==== Scenario 1 ====&lt;br /&gt;
An assignment and a team will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
==== Scenario 2 ====&lt;br /&gt;
An assignment and 3 teams will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. For each team: 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. For each team: 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
    ...&lt;br /&gt;
&lt;br /&gt;
We will generate some edge cases to test the robustness of our work.&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141561</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141561"/>
		<updated>2021-11-09T20:22:15Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Manual UI Tests */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px|center]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
The new features of recording and showing the history of grades and comments of reviews and submissions will be manually tested after we finished the implementation of those functions.&lt;br /&gt;
&lt;br /&gt;
==== Scenerio 1 ====&lt;br /&gt;
An assignment and a team will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
:2. An assignment and 3 teams will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. For each team: 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. For each team: 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
    ...&lt;br /&gt;
&lt;br /&gt;
We will generate some edge cases to test the robustness of our work.&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141560</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=141560"/>
		<updated>2021-11-09T20:20:33Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Important Links */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
[https://expertiza.csc.ncsu.edu/index.php/E1934_-_Grading_Audit_Trail Previous Wiki Page]&lt;br /&gt;
&lt;br /&gt;
[https://youtu.be/yyxX_kRYxLc Screencast]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Review ===&lt;br /&gt;
&lt;br /&gt;
:1. '''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in the current implementation; &lt;br /&gt;
:2. But for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment, and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
:1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
:2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
:3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
:4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
:5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
:6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px|center]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Reviews ===&lt;br /&gt;
&lt;br /&gt;
In this part, we will modify the current view of review page, to add the link &amp;quot;history&amp;quot; to a proper place as the expected design picture shows.&lt;br /&gt;
&lt;br /&gt;
The related table from databases is [https://expertiza.csc.ncsu.edu/index.php/Review_scores review_scores]. The ER table of review_scores is shown as below.&lt;br /&gt;
&lt;br /&gt;
[[File:Review scores imported.png]]&lt;br /&gt;
==== Review History Flow====&lt;br /&gt;
[[File:reviewhistory.png]]&lt;br /&gt;
&lt;br /&gt;
=== History of Comment and Grade for Submissions===&lt;br /&gt;
&lt;br /&gt;
In Expertiza, we find the fields related to grade and comment are located in the model '''team''', which is only able to be overwritten. Since there is no table to store the history of the comment and score given by instructors and TAs, we need to do:&lt;br /&gt;
&lt;br /&gt;
:1. Review the related implementation of previous work in order to evaluate and understand the process of adding new models.&lt;br /&gt;
&lt;br /&gt;
:2. Implement the related Model, View and Controller:&lt;br /&gt;
&lt;br /&gt;
:* Model: grading_history.rb &lt;br /&gt;
&lt;br /&gt;
:* Controller:  grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
:* View: related pages.&lt;br /&gt;
&lt;br /&gt;
Because in Expertiza the team ID will be generated for each given assignment, so the original design of grade / comment of team's submission are the field belongs to '''team'''. So our model uses the foreign key to only the team but not the related assignments or submissions.&lt;br /&gt;
&lt;br /&gt;
The expected class of grading history could be shown as:&lt;br /&gt;
&lt;br /&gt;
[[File:GradingHistory.png]]&lt;br /&gt;
&lt;br /&gt;
==== Team History Flow====&lt;br /&gt;
[[File:teamhistory.png]]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests ===&lt;br /&gt;
==== For History of the Grade of Reviews ====&lt;br /&gt;
The history of the grade and comments are related to this controller app/controllers/review_mapping_controller.rb and this view app/views/reports/_review_report.html.erb. &lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/controllers/review_mapping_controller_spec.rb&lt;br /&gt;
&lt;br /&gt;
==== For History of the Grade of Team Submissions ====&lt;br /&gt;
The history of the grade and comments are related to the new model grading_history.rb and the new controller grading_history_controller.rb.&lt;br /&gt;
&lt;br /&gt;
So the related RSpec tests are planned to be executed:&lt;br /&gt;
&lt;br /&gt;
    spec/models/grading_history.rb&lt;br /&gt;
    spec/controllers/grading_history_controller.rb&lt;br /&gt;
&lt;br /&gt;
For the feature part, test if the grading history and instructor can be shown in chronological order:&lt;br /&gt;
&lt;br /&gt;
    spec/features/grade_histories_spec.rb&lt;br /&gt;
    spec/features/helpers/grade_histories_helper.rb&lt;br /&gt;
&lt;br /&gt;
=== Manual UI Tests ===&lt;br /&gt;
The new features of recording and showing the history of grades and comments of reviews and submissions will be manually tested after we finished the implementation of those functions.&lt;br /&gt;
&lt;br /&gt;
:1. An assignment and a team will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
:2. An assignment and 3 teams will be generated, and at most 3 instructors / TAs will give grades for these situations:&lt;br /&gt;
    1. For each team: 1 submission, 1 review, 1 grade and comment for submission, 1 grade and comment for review.&lt;br /&gt;
    2. For each team: 1 submission, 2 review, 2 grade and comment for submission from different graders, 2 grade and comment for review from different graders.&lt;br /&gt;
    ...&lt;br /&gt;
&lt;br /&gt;
We will generate some edge cases to test the robustness of our work.&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git Repo]&lt;br /&gt;
#[https://github.com/expertiza/expertiza/pull/2130 Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140820</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140820"/>
		<updated>2021-11-04T01:49:52Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Overview */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
&lt;br /&gt;
'''Review grade''' part in the previous implementation served well, we only need to fix some UI issues in current implementation; but for '''Submission grade''' part, we need to add a table in order to save submission history including the instructor id, assignment id, student id, grade, comment and timestamp.&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below the in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px|center]]&lt;br /&gt;
&lt;br /&gt;
=== Review Grade ===&lt;br /&gt;
1.....&lt;br /&gt;
&lt;br /&gt;
2.....&lt;br /&gt;
&lt;br /&gt;
3.....&lt;br /&gt;
&lt;br /&gt;
=== Submission Grade ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# add history table&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests === &lt;br /&gt;
=== Manual UI Testing ===&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/pulls Pull Request (not created yet)]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140808</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140808"/>
		<updated>2021-11-04T01:45:32Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Overview */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
&lt;br /&gt;
The previous implementation&lt;br /&gt;
&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below the in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px|center]]&lt;br /&gt;
&lt;br /&gt;
=== Review Grade ===&lt;br /&gt;
1.....&lt;br /&gt;
&lt;br /&gt;
2.....&lt;br /&gt;
&lt;br /&gt;
3.....&lt;br /&gt;
&lt;br /&gt;
=== Submission Grade ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# add history table&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests === &lt;br /&gt;
=== Manual UI Testing ===&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/pulls Pull Request (not created yet)]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140806</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140806"/>
		<updated>2021-11-04T01:44:46Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Issues */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
=== Issues with Previous Work ===&lt;br /&gt;
1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below the in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px|center]]&lt;br /&gt;
&lt;br /&gt;
=== Review Grade ===&lt;br /&gt;
1.....&lt;br /&gt;
&lt;br /&gt;
2.....&lt;br /&gt;
&lt;br /&gt;
3.....&lt;br /&gt;
&lt;br /&gt;
=== Submission Grade ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# add history table&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests === &lt;br /&gt;
=== Manual UI Testing ===&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/pulls Pull Request (not created yet)]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140803</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140803"/>
		<updated>2021-11-04T01:43:34Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Expected View */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
=== Issues ===&lt;br /&gt;
1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below the in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1100px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1100px|center]]&lt;br /&gt;
&lt;br /&gt;
=== Review Grade ===&lt;br /&gt;
1.....&lt;br /&gt;
&lt;br /&gt;
2.....&lt;br /&gt;
&lt;br /&gt;
3.....&lt;br /&gt;
&lt;br /&gt;
=== Submission Grade ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# add history table&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests === &lt;br /&gt;
=== Manual UI Testing ===&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/pulls Pull Request (not created yet)]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:E2158_Proposed_Solution_3.png&amp;diff=140801</id>
		<title>File:E2158 Proposed Solution 3.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:E2158_Proposed_Solution_3.png&amp;diff=140801"/>
		<updated>2021-11-04T01:42:50Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: Ghou3 uploaded a new version of File:E2158 Proposed Solution 3.png&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140798</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140798"/>
		<updated>2021-11-04T01:40:47Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Expected View */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
=== Issues ===&lt;br /&gt;
1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below the in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1200px|center]]&lt;br /&gt;
&lt;br /&gt;
=== Review Grade ===&lt;br /&gt;
1.....&lt;br /&gt;
&lt;br /&gt;
2.....&lt;br /&gt;
&lt;br /&gt;
3.....&lt;br /&gt;
&lt;br /&gt;
=== Submission Grade ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# add history table&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests === &lt;br /&gt;
=== Manual UI Testing ===&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/pulls Pull Request (not created yet)]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140796</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140796"/>
		<updated>2021-11-04T01:39:19Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Proposed Solution */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
=== Issues ===&lt;br /&gt;
1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below the in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|800px]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|800px]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|800px]]&lt;br /&gt;
&lt;br /&gt;
=== Review Grade ===&lt;br /&gt;
1.....&lt;br /&gt;
&lt;br /&gt;
2.....&lt;br /&gt;
&lt;br /&gt;
3.....&lt;br /&gt;
&lt;br /&gt;
=== Submission Grade ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# add history table&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests === &lt;br /&gt;
=== Manual UI Testing ===&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/pulls Pull Request (not created yet)]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:E2158_Proposed_Solution_3.png&amp;diff=140789</id>
		<title>File:E2158 Proposed Solution 3.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:E2158_Proposed_Solution_3.png&amp;diff=140789"/>
		<updated>2021-11-04T01:35:16Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: Ghou3 uploaded a new version of File:E2158 Proposed Solution 3.png&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140709</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140709"/>
		<updated>2021-11-03T22:38:45Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Important Links */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
=== Issues ===&lt;br /&gt;
1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below the in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1200px|center]]&lt;br /&gt;
=== Review Grade ===&lt;br /&gt;
1.....&lt;br /&gt;
&lt;br /&gt;
2.....&lt;br /&gt;
&lt;br /&gt;
3.....&lt;br /&gt;
&lt;br /&gt;
=== Submission Grade ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# add history table&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests === &lt;br /&gt;
=== Manual UI Testing ===&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/pulls Pull Request (not created yet)]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140708</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140708"/>
		<updated>2021-11-03T22:38:38Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Important Links */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
=== Issues ===&lt;br /&gt;
1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below the in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1200px|center]]&lt;br /&gt;
=== Review Grade ===&lt;br /&gt;
1.....&lt;br /&gt;
&lt;br /&gt;
2.....&lt;br /&gt;
&lt;br /&gt;
3.....&lt;br /&gt;
&lt;br /&gt;
=== Submission Grade ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# add history table&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests === &lt;br /&gt;
=== Manual UI Testing ===&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/pulls Pull Request(not created yet)]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140707</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140707"/>
		<updated>2021-11-03T22:38:02Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Important Links */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
=== Issues ===&lt;br /&gt;
1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below the in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1200px|center]]&lt;br /&gt;
=== Review Grade ===&lt;br /&gt;
1.....&lt;br /&gt;
&lt;br /&gt;
2.....&lt;br /&gt;
&lt;br /&gt;
3.....&lt;br /&gt;
&lt;br /&gt;
=== Submission Grade ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# add history table&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests === &lt;br /&gt;
=== Manual UI Testing ===&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/pulls Pull Request]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140705</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140705"/>
		<updated>2021-11-03T22:32:51Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Submission Grade */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
=== Issues ===&lt;br /&gt;
1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below the in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1200px|center]]&lt;br /&gt;
=== Review Grade ===&lt;br /&gt;
1.....&lt;br /&gt;
&lt;br /&gt;
2.....&lt;br /&gt;
&lt;br /&gt;
3.....&lt;br /&gt;
&lt;br /&gt;
=== Submission Grade ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# add history table&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests === &lt;br /&gt;
=== Manual UI Testing ===&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140704</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140704"/>
		<updated>2021-11-03T22:32:22Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Submission Grade */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
=== Issues ===&lt;br /&gt;
1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below the in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1200px|center]]&lt;br /&gt;
=== Review Grade ===&lt;br /&gt;
1.....&lt;br /&gt;
&lt;br /&gt;
2.....&lt;br /&gt;
&lt;br /&gt;
3.....&lt;br /&gt;
&lt;br /&gt;
=== Submission Grade ===&lt;br /&gt;
&lt;br /&gt;
[add history table]&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests === &lt;br /&gt;
=== Manual UI Testing ===&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140703</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140703"/>
		<updated>2021-11-03T22:32:14Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Submission Grade */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
=== Issues ===&lt;br /&gt;
1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below the in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1200px|center]]&lt;br /&gt;
=== Review Grade ===&lt;br /&gt;
1.....&lt;br /&gt;
&lt;br /&gt;
2.....&lt;br /&gt;
&lt;br /&gt;
3.....&lt;br /&gt;
&lt;br /&gt;
=== Submission Grade ===&lt;br /&gt;
&lt;br /&gt;
## add history table&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests === &lt;br /&gt;
=== Manual UI Testing ===&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140702</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140702"/>
		<updated>2021-11-03T22:32:04Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Submission Grade */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
=== Issues ===&lt;br /&gt;
1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below the in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1200px|center]]&lt;br /&gt;
=== Review Grade ===&lt;br /&gt;
1.....&lt;br /&gt;
&lt;br /&gt;
2.....&lt;br /&gt;
&lt;br /&gt;
3.....&lt;br /&gt;
&lt;br /&gt;
=== Submission Grade ===&lt;br /&gt;
&lt;br /&gt;
add history table&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests === &lt;br /&gt;
=== Manual UI Testing ===&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140701</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140701"/>
		<updated>2021-11-03T22:31:51Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Submission Grade */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
=== Issues ===&lt;br /&gt;
1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below the in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1200px|center]]&lt;br /&gt;
=== Review Grade ===&lt;br /&gt;
1.....&lt;br /&gt;
&lt;br /&gt;
2.....&lt;br /&gt;
&lt;br /&gt;
3.....&lt;br /&gt;
&lt;br /&gt;
=== Submission Grade ===&lt;br /&gt;
&lt;br /&gt;
# add history table&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests === &lt;br /&gt;
=== Manual UI Testing ===&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140700</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140700"/>
		<updated>2021-11-03T22:31:36Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Review Grade */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
=== Issues ===&lt;br /&gt;
1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below the in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1200px|center]]&lt;br /&gt;
=== Review Grade ===&lt;br /&gt;
1.....&lt;br /&gt;
&lt;br /&gt;
2.....&lt;br /&gt;
&lt;br /&gt;
3.....&lt;br /&gt;
&lt;br /&gt;
=== Submission Grade ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# add history table&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests === &lt;br /&gt;
=== Manual UI Testing ===&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140699</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140699"/>
		<updated>2021-11-03T22:31:28Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Review Grade */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
=== Issues ===&lt;br /&gt;
1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below the in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1200px|center]]&lt;br /&gt;
=== Review Grade ===&lt;br /&gt;
1.....&lt;br /&gt;
2.....&lt;br /&gt;
3.....&lt;br /&gt;
&lt;br /&gt;
=== Submission Grade ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# add history table&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests === &lt;br /&gt;
=== Manual UI Testing ===&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140698</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140698"/>
		<updated>2021-11-03T22:30:12Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Expected View */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
=== Issues ===&lt;br /&gt;
1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below the in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
=== Expected View ===&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1200px|center]]&lt;br /&gt;
=== Review Grade ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Submission Grade ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# add history table&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests === &lt;br /&gt;
=== Manual UI Testing ===&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140696</id>
		<title>CSC/ECE 517 Fall 2021 - E2158. Grading audit trail</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2158._Grading_audit_trail&amp;diff=140696"/>
		<updated>2021-11-03T22:29:57Z</updated>

		<summary type="html">&lt;p&gt;Ghou3: /* Proposed Solution */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Problem Definition ==&lt;br /&gt;
After an instructor gave a grade to an assignment, there is no way to track who gave the grade. Any instructor can assign/edit a grade freely. There is no way of tracking who did it.&lt;br /&gt;
&lt;br /&gt;
A grading audit trail must be created and the following information needs to be stored: &lt;br /&gt;
:1. When a grade is assigned by an instructor, there needs to be an indication of who did it and when it was done. &lt;br /&gt;
:2. Comments previously provided by other instructors must also be preserved.&lt;br /&gt;
&lt;br /&gt;
This information needs to be stored every time an instructor edits a grade/comment and clicks the save button.&lt;br /&gt;
&lt;br /&gt;
Currently, there are two places need to add grading audit trail: &lt;br /&gt;
:1. '''Review grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Review Report&lt;br /&gt;
:2. '''Submission grade''': Log in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View submissions&lt;br /&gt;
&lt;br /&gt;
The grading audit trail can probably be implemented as the submission records history on Expertiza.&lt;br /&gt;
The required page can be reached by logging in as instructor -&amp;gt; Manage -&amp;gt; Assignments -&amp;gt; View Submissions -&amp;gt; History&lt;br /&gt;
&lt;br /&gt;
At the minimum, a grading log entry must include the '''instructor id''', '''assignment id''', '''student id''', '''grade''', '''comment''' and '''timestamp'''.&lt;br /&gt;
&lt;br /&gt;
== Previous Implementation ==&lt;br /&gt;
=== Overview ===&lt;br /&gt;
=== Issues ===&lt;br /&gt;
1. For review grades, the “Grading History” link must not be in a separate column. It should be in smaller text below the in the “Save” button.&lt;br /&gt;
&lt;br /&gt;
2. In the view grading record page, remove the receiver column and add it to the title.&lt;br /&gt;
&lt;br /&gt;
3. Restrict the column width on the grading record page.&lt;br /&gt;
&lt;br /&gt;
4. Add comments on list_submissions.html.erb to indicate that the alignment was changed to fix code climate issues.&lt;br /&gt;
&lt;br /&gt;
5. Revert changes made to list_review_mapping.html.erb.&lt;br /&gt;
 &lt;br /&gt;
6. Remove the review_report-html.erb file.&lt;br /&gt;
&lt;br /&gt;
== Proposed Solution ==&lt;br /&gt;
== Expected View ==&lt;br /&gt;
[[File:E2158_Proposed_Solution_1.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_2.png|1200px|center]]&lt;br /&gt;
[[File:E2158_Proposed_Solution_3.png|1200px|center]]&lt;br /&gt;
=== Review Grade ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Submission Grade ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# add history table&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Testing Plan ==&lt;br /&gt;
=== Rspec Unit Tests === &lt;br /&gt;
=== Manual UI Testing ===&lt;br /&gt;
&lt;br /&gt;
== Important Links ==&lt;br /&gt;
#[https://github.com/duliwencynthia/expertiza/tree/beta Git path]&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
'''Mentor:''' Xiao, Kai (yxiao28)&lt;br /&gt;
&lt;br /&gt;
Yao, Kaiyong (kyao)&lt;br /&gt;
&lt;br /&gt;
Hou, Guanyu (ghou3)&lt;br /&gt;
&lt;br /&gt;
Du, Haoze (hdu5)&lt;br /&gt;
&lt;br /&gt;
Du, Liwen (ldu2)&lt;/div&gt;</summary>
		<author><name>Ghou3</name></author>
	</entry>
</feed>