Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2016 E1683 Team-based reviewing

2016-12-01T22:59:56Z

Xding3: /* Design */

== Purpose ==
In Expertiza, students can review others’ work. However, currently all reviews are done by individuals, regardless of whether the assignment is assigned as individuals or teams. In team assignments, when the team member reviews an assignment, his/her review is independent from his/her teammates’ reviews.

To encourage students to discuss together and review carefully, it is sometimes reasonable for students to submit their reviews as a team. And apparently, team-based reviewing can reduce the workload of each student.

In a word, the main purpose of this project is to achieve the function of team-based reviewing and ensure that Expertiza works well with the change.

[[File:Purpose.png]]

== Design ==
Based on the design documents, the basic project design is proposed below.

=== Database Design ===
In Expertiza, we have ''ResponseMap'', which is the object that records who reviews whom. In ''ResponseMap'', there are two attributes: ''reviewer_id'' and ''reviewee_id''. The ''reviewee_id'' is the ID of the ''Team'', which indicates which team is being reviewed. And the ''reviewer_id'' is the ID of ''Participant'', which specifies a user who is participating in this assignment.

[[File:data_design_1.png]]

To achieve function of team-based reviewing, a boolean field ''reviewer_is_team'' needs to be added to ''ResponseMap'' to determines whether the reviewer is a ''AssignmentParticipant'' or an ''AssignmentTeam''. If ''reviewer_is_team'' is true, then the ''reviewer_id'' would refer to a record in the teams table, not a record in the participants table.

[[File:data_design_2.png]]

And a field ''reviewer_is_team'' is also need to be added to the assignments table as well to indicate the review of assignment is an individual-based reviewing or team-based reviewing.

[[File:data_design_3.png]]

=== Interface Design ===
Several parts of the system need to work regardless of whether the reviewer is an individual or a team, like “View my scores” and “Alternative view”. The scores are given as team if the reviewing type is team-based.
expertiza/app/controllers/grades_controller:
def view_my_score
+ Give all team members the same score
end
For an ''Instructor'' to specify whether the reviewing is team-based or individual-based, we are intended to provide a dropdown on the ''Review Strategy'' tab of assignment creation.
expertiza/app/views/assignments/edit_html_erb:
+ Add a select tag to let instructor choose the reviewing type

expertiza/app/controllers/assignments_controller:
def edit
+ Accept the value from view and assign it to assignment
end

We set a lock in editing review, so that other team member cannot start to edit a review at the same time that one team member is editing it. The error message is considered to be displayed by ''flash[:alert]''.
expertiza/app/controllers/responses_controller:
def edit
+ Set a lock allowing only one student editing review at the same time
end

=== Test Design ===
RSpec is a testing framework for Rails, and is a Behavioral-Driven Development tool. It is a domain specific language(DSL). All the tests can be executed by rspec spec command, or can also be executed individually using the command "rspec spec/models/assignment_team_spec.rb. We intend to write unit tests using RSpec for all the methods which we modified/created. We intend to write unit tests using RSpec for all the methods which we modified/created. And also the basic test case is proposed for UI test.

{| class="wikitable"
!Test Name !!Prerequisites !!Test Procedure !!Expected Results

|-
|Edit reviewing type of assignments
|1. User is an Instructor 2. At leaset one assignments can be edited
|1. Log into Expertiza 2. Edit assignments 3. Change reviewing type under Review Strategy
|The reviewing type is changed (in database)

|-
|Edit reviews at the same time
|1. Two users at the same team as Students 2. At least one assignments can be reviewed
|1. Two users log into Expertiza. 2. One start editing review and the other try submitting at the same time
|An alert message will be displayed

|-
|View scores
|1. Two users at the same team as Students 2. At least one assignments is graded
|1. Two users log into Expertiza. 2. Click "your score" under one assignment page
|The page works well and the score is the same

|}

CSC/ECE 517 Fall 2016 E1683 Team-based reviewing

2016-11-15T04:19:42Z

Xding3: /* Design */

== Purpose ==
In Expertiza, students can review others’ work. However, currently all reviews are done by individuals, regardless of whether the assignment is assigned as individuals or teams. In team assignments, when the team member reviews an assignment, his/her review is independent from his/her teammates’ reviews.

To encourage students to discuss together and review carefully, it is sometimes reasonable for students to submit their reviews as a team. And apparently, team-based reviewing can reduce the workload of each student.

In a word, the main purpose of this project is to achieve the function of team-based reviewing and ensure that Expertiza works well with the change.

[[File:Purpose.png]]

== Design ==
Based on the design documents, the basic project design is proposed below.

=== Data Design ===
In Expertiza, we have ''ResponseMap'', which is the object that records who reviews whom. In ''ResponseMap'', there are two attributes: ''reviewer_id'' and ''reviewee_id''. The ''reviewee_id'' is the ID of the ''Team'', which indicates which team is being reviewed. And the ''reviewer_id'' is the ID of ''Participant'', which specifies a user who is participating in this assignment.

To achieve function of team-based reviewing, a boolean field ''reviewer_is_team'' needs to be added to ''ResponseMap'' to determines whether the reviewer is a ''AssignmentParticipant'' or an ''AssignmentTeam''. If ''reviewer_is_team'' is true, then the ''reviewer_id'' would refer to a record in the teams table, not a record in the participants table.

And a field ''reviewer_is_team'' is also need to be added to the assignments table as well to indicate the review of assignment is an individual-based reviewing or team-based reviewing.

=== Interface Design ===
Several parts of the system need to work regardless of whether the reviewer is an individual or a team, like “View my scores” and “Alternative view”.

For an ''Instructor'' to specify whether the reviewing is team-based or individual-based, we are intended to provide a dropdown on the ''Review Strategy'' tab of assignment creation.

We set a lock in editing review, so that other team member cannot start to edit a review at the same time that one team member is editing it. The error message is considered to be displayed by “flash[:alert]”.

=== Test Design ===
RSpec is a testing framework for Rails, and is a Behavioral-Driven Development tool. It is a domain specific language(DSL). All the tests can be executed by rspec spec command, or can also be executed individually using the command "rspec spec/models/assignment_team_spec.rb. We intend to write unit tests using RSpec for all the methods which we modified/created. We intend to write unit tests using RSpec for all the methods which we modified/created.

== Test Plan ==
=== RSpec ===
RSpec is a testing framework for Rails, and is a Behavioral-Driven Development tool. It is a domain specific language(DSL). All the tests can be executed by rspec spec command, or can also be executed individually using the command "rspec spec/models/assignment_team_spec.rb. We intend to write unit tests using RSpec for all the methods which we modified/created. We intend to write unit tests using RSpec for all the methods which we modified/created.

CSC/ECE 517 Fall 2016 E1683 Team-based reviewing

2016-11-15T00:44:22Z

Xding3: /* Project Design */

CSC/ECE 517 Fall 2016 E1683 Team-based reviewing

2016-11-15T00:43:39Z

Xding3: /* Project Purpose */

File:Purpose.png

2016-11-15T00:39:22Z

Xding3: uploaded a new version of "File:Purpose.png": Shrink the picture to display

CSC/ECE 517 Fall 2016 E1683 Team-based reviewing

2016-11-15T00:35:16Z

Xding3: /* Project Purpose */

== Project Purpose ==
In Expertiza, students can review others’ work. However, currently all reviews are done by individuals, regardless of whether the assignment is assigned as individuals or teams. In team assignments, when the team member reviews an assignment, his/her review is independent from his/her teammates’ reviews.

To encourage students to discuss together and review carefully, it is sometimes reasonable for students to submit their reviews as a team. And apparently, team-based reviewing can reduce the workload of each student.

In a word, the main purpose of our project is to achieve the function of team-based reviewing and ensure that Expertiza works well with the change.

[[File:Purpose.png]]

== Project Design ==
Based on the design documents, the basic project design is proposed below.

=== Model ===
In Expertiza, we have ''ResponseMap'', which is the object that records who reviews whom. In ''ResponseMap'', there are two attributes: ''reviewer_id'' and ''reviewee_id''. The ''reviewee_id'' is the ID of the ''AssignmentTeam'' , which indicates which team is being reviewed. The ''reviewer_id'' is a ''Participant'', which specifies a User who is participating in this assignment.

To achieve function of team-based reviewing, a boolean field ''reviewer_is_team'' needs to be added to ''ResponseMap'' to determines whether the reviewer is a ''AssignmentParticipant'' or an ''AssignmentTeam''. If ''reviewer_is_team'' is true, then the ''reviewer_id'' would refer to a record in the teams table, not a record in the participants table.

And a field ''reviewer_is_team'' is also need to be added to the assignments table as well to indicate the review of assignment is an individual-based reviewing or team-based reviewing.

===Controller===
The method sending a message to the reviewer should be implemented appropriately in both ''Participant'' and ''AssignmentTeam''.
=== View ===
Several parts of the system need to work regardless of whether the reviewer is an individual or a team, like “View my scores” and “Alternative view”.

For an ''Instructor'' to specify whether the reviewing is team-based or individual-based, we are intended to provide a dropdown on the ''Review Strategy'' tab of assignment creation.

We set a lock in editing review, so that other team member cannot start to edit a review at the same time that one team member is editing it.

== Test Plan ==
=== RSpec ===
RSpec is a testing framework for Rails, and is a Behavioral-Driven Development tool. It is a domain specific language(DSL). All the tests can be executed by rspec spec command, or can also be executed individually using the command "rspec spec/models/assignment_team_spec.rb. We intend to write unit tests using RSpec for all the methods which we modified/created. We intend to write unit tests using RSpec for all the methods which we modified/created.

File:Purpose.png

2016-11-15T00:33:52Z

Xding3:

CSC/ECE 517 Fall 2016 E1683 Team-based reviewing

2016-11-15T00:32:31Z

Xding3:

== Project Purpose ==
In Expertiza, students can review others’ work. However, currently all reviews are done by individuals, regardless of whether the assignment is assigned as individuals or teams. In team assignments, when the team member reviews an assignment, his/her review is independent from his/her teammates’ reviews.

To encourage students to discuss together and review carefully, it is sometimes reasonable for students to submit their reviews as a team. And apparently, team-based reviewing can reduce the workload of each student.

In a word, the main purpose of our project is to achieve the function of team-based reviewing and ensure that Expertiza works well with the change.
[[File:C:\Users\Ding\Desktop\Picture1.png]]

== Project Design ==
Based on the design documents, the basic project design is proposed below.

=== Model ===
In Expertiza, we have ''ResponseMap'', which is the object that records who reviews whom. In ''ResponseMap'', there are two attributes: ''reviewer_id'' and ''reviewee_id''. The ''reviewee_id'' is the ID of the ''AssignmentTeam'' , which indicates which team is being reviewed. The ''reviewer_id'' is a ''Participant'', which specifies a User who is participating in this assignment.

To achieve function of team-based reviewing, a boolean field ''reviewer_is_team'' needs to be added to ''ResponseMap'' to determines whether the reviewer is a ''AssignmentParticipant'' or an ''AssignmentTeam''. If ''reviewer_is_team'' is true, then the ''reviewer_id'' would refer to a record in the teams table, not a record in the participants table.

And a field ''reviewer_is_team'' is also need to be added to the assignments table as well to indicate the review of assignment is an individual-based reviewing or team-based reviewing.

===Controller===
The method sending a message to the reviewer should be implemented appropriately in both ''Participant'' and ''AssignmentTeam''.
=== View ===
Several parts of the system need to work regardless of whether the reviewer is an individual or a team, like “View my scores” and “Alternative view”.

For an ''Instructor'' to specify whether the reviewing is team-based or individual-based, we are intended to provide a dropdown on the ''Review Strategy'' tab of assignment creation.

We set a lock in editing review, so that other team member cannot start to edit a review at the same time that one team member is editing it.

== Test Plan ==
=== RSpec ===
RSpec is a testing framework for Rails, and is a Behavioral-Driven Development tool. It is a domain specific language(DSL). All the tests can be executed by rspec spec command, or can also be executed individually using the command "rspec spec/models/assignment_team_spec.rb. We intend to write unit tests using RSpec for all the methods which we modified/created. We intend to write unit tests using RSpec for all the methods which we modified/created.

CSC/ECE 517 Fall 2016 E1683 Team-based reviewing

2016-11-11T23:28:19Z

Xding3:

== Project Purpose ==
At present, all reviews in Expertiza are done by individuals, regardless of whether the assignment is assigned as individuals or teams. In team assignments, when the team member reviews an assignment, his/her review is independent from his/her teammates’ reviews. To encourage students to discuss together and review carefully, it is sometimes reasonable for students to submit their reviews as a team. The main purpose of our project is to achieve the function of team-based reviewing and ensure the other functions in Expertiza works well with the change.

== Project Design ==
Based on the design documents, the basic project design is proposed below.

=== Model ===
In Expertiza, we have ''ResponseMap'', which is the object that records who reviews whom. In ''ResponseMap'', there are two attributes: ''reviewer_id'' and ''reviewee_id''. The ''reviewee_id'' is the ID of the ''AssignmentTeam'' , which indicates which team is being reviewed. The ''reviewer_id'' is a ''Participant'', which specifies a User who is participating in this assignment.

To achieve function of team-based reviewing, a boolean field ''reviewer_is_team'' needs to be added to ''ResponseMap'' to determines whether the reviewer is a ''AssignmentParticipant'' or an ''AssignmentTeam''. If ''reviewer_is_team'' is true, then the ''reviewer_id'' would refer to a record in the teams table, not a record in the participants table.

And a field ''reviewer_is_team'' is also need to be added to the assignments table as well to indicate the review of assignment is an individual-based reviewing or team-based reviewing.

===Controller===
The method sending a message to the reviewer should be implemented appropriately in both ''Participant'' and ''AssignmentTeam''.
=== View ===
Several parts of the system need to work regardless of whether the reviewer is an individual or a team, like “View my scores” and “Alternative view”.

For an ''Instructor'' to specify whether the reviewing is team-based or individual-based, we are intended to provide a dropdown on the ''Review Strategy'' tab of assignment creation.

We set a lock in editing review, so that other team member cannot start to edit a review at the same time that one team member is editing it.

== Test Plan ==
=== RSpec ===
RSpec is a testing framework for Rails, and is a Behavioral-Driven Development tool. It is a domain specific language(DSL). All the tests can be executed by rspec spec command, or can also be executed individually using the command "rspec spec/models/assignment_team_spec.rb. We intend to write unit tests using RSpec for all the methods which we modified/created. We intend to write unit tests using RSpec for all the methods which we modified/created.

User:Xding3

2016-11-11T23:21:25Z

Xding3: moved User:Xding3 to CSC/ECE 517 Fall 2016 E1683 Team-based reviewing

#REDIRECT [[CSC/ECE 517 Fall 2016 E1683 Team-based reviewing]]

CSC/ECE 517 Fall 2016 E1683 Team-based reviewing

2016-11-11T23:21:25Z

Xding3: moved User:Xding3 to CSC/ECE 517 Fall 2016 E1683 Team-based reviewing

== Project Purpose ==
At present, all reviews in Expertiza are done by individuals, regardless of whether the assignment is assigned as individuals or teams. In team assignments, when the team member reviews an assignment, his/her review is independent from his/her teammates’ reviews. To encourage students to discuss together and review carefully, it is sometimes reasonable for students to submit their reviews as a team.

== Project Design ==
Based on the design documents, the basic project design is proposed below.
=== Model ===
In Expertiza, we have ResponseMap, which is the object that records who reviews whom. In ResponseMap, there are two attributes: reviewer_id and reviewee_id. The reviewee_id is the ID of the AssignmentTeam that is being reviewed. The reviewer_id is a Participant, which specifies a User who is participating in this assignment.

To achieve function of team-based review, a boolean field reviewer_is_team needs to be added to ResponseMap to determines whether the reviewer is a AssignmentParticipant or an AssignmentTeam. If reviewer_is_team is true, then the reviewer_id would refer to a record in the teams table, not a record in the participants table.

And a field reviewer_is_team is also need to be added to the assignments table as well to indicate the assignment is an individual-based review or team-based review.

===Controller===
The method sending a message to the reviewer should be implemented appropriately in both Participant and AssignmentTeam.
=== View ===
Several parts of the system need to work regardless of whether the reviewer is an individual or a team, like “View my scores” and “Alternative view”.

For an Instructor to specify whether the view is team-based or individual-based, we are intended to provide a dropdown on the Review Strategy tab of assignment creation.

Set a lock, so that a second team member cannot start to edit a review at the same time that another team member is editing it.

== Test Plan ==
=== RSpec ===
RSpec is a testing framework for Rails, and is a Behavioral-Driven Development tool. It is a domain specific language(DSL). All the tests can be executed by rspec spec command, or can also be executed individually using the command "rspec spec/models/assignment_team_spec.rb. We intend to write unit tests using RSpec for all the methods which we modified/created. We intend to write unit tests using RSpec for all the methods which we modified/created.

CSC/ECE 517 Fall 2016 E1683 Team-based reviewing

2016-11-11T23:12:56Z

Xding3: /* View */

== Project Purpose ==
At present, all reviews in Expertiza are done by individuals, regardless of whether the assignment is assigned as individuals or teams. In team assignments, when the team member reviews an assignment, his/her review is independent from his/her teammates’ reviews. To encourage students to discuss together and review carefully, it is sometimes reasonable for students to submit their reviews as a team.

== Project Design ==
Based on the design documents, the basic project design is proposed below.
=== Model ===
In Expertiza, we have ResponseMap, which is the object that records who reviews whom. In ResponseMap, there are two attributes: reviewer_id and reviewee_id. The reviewee_id is the ID of the AssignmentTeam that is being reviewed. The reviewer_id is a Participant, which specifies a User who is participating in this assignment.

To achieve function of team-based review, a boolean field reviewer_is_team needs to be added to ResponseMap to determines whether the reviewer is a AssignmentParticipant or an AssignmentTeam. If reviewer_is_team is true, then the reviewer_id would refer to a record in the teams table, not a record in the participants table.

And a field reviewer_is_team is also need to be added to the assignments table as well to indicate the assignment is an individual-based review or team-based review.

===Controller===
The method sending a message to the reviewer should be implemented appropriately in both Participant and AssignmentTeam.
=== View ===
Several parts of the system need to work regardless of whether the reviewer is an individual or a team, like “View my scores” and “Alternative view”.

For an Instructor to specify whether the view is team-based or individual-based, we are intended to provide a dropdown on the Review Strategy tab of assignment creation.

Set a lock, so that a second team member cannot start to edit a review at the same time that another team member is editing it.

== Test Plan ==
=== RSpec ===
RSpec is a testing framework for Rails, and is a Behavioral-Driven Development tool. It is a domain specific language(DSL). All the tests can be executed by rspec spec command, or can also be executed individually using the command "rspec spec/models/assignment_team_spec.rb. We intend to write unit tests using RSpec for all the methods which we modified/created. We intend to write unit tests using RSpec for all the methods which we modified/created.

CSC/ECE 517 Fall 2016 E1683 Team-based reviewing

2016-11-11T23:12:45Z

Xding3: /* Model */

== Project Purpose ==
At present, all reviews in Expertiza are done by individuals, regardless of whether the assignment is assigned as individuals or teams. In team assignments, when the team member reviews an assignment, his/her review is independent from his/her teammates’ reviews. To encourage students to discuss together and review carefully, it is sometimes reasonable for students to submit their reviews as a team.

== Project Design ==
Based on the design documents, the basic project design is proposed below.
=== Model ===
In Expertiza, we have ResponseMap, which is the object that records who reviews whom. In ResponseMap, there are two attributes: reviewer_id and reviewee_id. The reviewee_id is the ID of the AssignmentTeam that is being reviewed. The reviewer_id is a Participant, which specifies a User who is participating in this assignment.

To achieve function of team-based review, a boolean field reviewer_is_team needs to be added to ResponseMap to determines whether the reviewer is a AssignmentParticipant or an AssignmentTeam. If reviewer_is_team is true, then the reviewer_id would refer to a record in the teams table, not a record in the participants table.

And a field reviewer_is_team is also need to be added to the assignments table as well to indicate the assignment is an individual-based review or team-based review.

===Controller===
The method sending a message to the reviewer should be implemented appropriately in both Participant and AssignmentTeam.
=== View ===
Several parts of the system need to work regardless of whether the reviewer is an individual or a team, like “View my scores” and “Alternative view”.
For an Instructor to specify whether the view is team-based or individual-based, we are intended to provide a dropdown on the Review Strategy tab of assignment creation.
Set a lock, so that a second team member cannot start to edit a review at the same time that another team member is editing it.

== Test Plan ==
=== RSpec ===
RSpec is a testing framework for Rails, and is a Behavioral-Driven Development tool. It is a domain specific language(DSL). All the tests can be executed by rspec spec command, or can also be executed individually using the command "rspec spec/models/assignment_team_spec.rb. We intend to write unit tests using RSpec for all the methods which we modified/created. We intend to write unit tests using RSpec for all the methods which we modified/created.

CSC/ECE 517 Fall 2016 E1683 Team-based reviewing

2016-11-11T23:12:10Z

Xding3: /* Project Purpose */

== Project Purpose ==
At present, all reviews in Expertiza are done by individuals, regardless of whether the assignment is assigned as individuals or teams. In team assignments, when the team member reviews an assignment, his/her review is independent from his/her teammates’ reviews. To encourage students to discuss together and review carefully, it is sometimes reasonable for students to submit their reviews as a team.

== Project Design ==
Based on the design documents, the basic project design is proposed below.
=== Model ===
In Expertiza, we have ResponseMap, which is the object that records who reviews whom. In ResponseMap, there are two attributes: reviewer_id and reviewee_id. The reviewee_id is the ID of the AssignmentTeam that is being reviewed. The reviewer_id is a Participant, which specifies a User who is participating in this assignment.
To achieve function of team-based review, a boolean field reviewer_is_team needs to be added to ResponseMap to determines whether the reviewer is a AssignmentParticipant or an AssignmentTeam. If reviewer_is_team is true, then the reviewer_id would refer to a record in the teams table, not a record in the participants table.
And a field reviewer_is_team is also need to be added to the assignments table as well to indicate the assignment is an individual-based review or team-based review.
===Controller===
The method sending a message to the reviewer should be implemented appropriately in both Participant and AssignmentTeam.
=== View ===
Several parts of the system need to work regardless of whether the reviewer is an individual or a team, like “View my scores” and “Alternative view”.
For an Instructor to specify whether the view is team-based or individual-based, we are intended to provide a dropdown on the Review Strategy tab of assignment creation.
Set a lock, so that a second team member cannot start to edit a review at the same time that another team member is editing it.

== Test Plan ==
=== RSpec ===
RSpec is a testing framework for Rails, and is a Behavioral-Driven Development tool. It is a domain specific language(DSL). All the tests can be executed by rspec spec command, or can also be executed individually using the command "rspec spec/models/assignment_team_spec.rb. We intend to write unit tests using RSpec for all the methods which we modified/created. We intend to write unit tests using RSpec for all the methods which we modified/created.

CSC/ECE 517 Fall 2016 E1683 Team-based reviewing

2016-11-11T23:11:54Z

Xding3: Created page with "== Project Purpose == At present, all reviews in Expertiza are done by individuals, regardless of whether the assignment is assigned as individuals or teams. In team assignment..."

== Project Purpose ==
At present, all reviews in Expertiza are done by individuals, regardless of whether the assignment is assigned as individuals or teams. In team assignments, when the team member reviews an assignment, his/her review is independent from his/her teammates’ reviews. To encourage students to discuss together and review carefully, it is sometimes reasonable for students to submit their reviews as a team.

== Project Design ==
Based on the design documents, the basic project design is proposed below.
=== Model ===
In Expertiza, we have ResponseMap, which is the object that records who reviews whom. In ResponseMap, there are two attributes: reviewer_id and reviewee_id. The reviewee_id is the ID of the AssignmentTeam that is being reviewed. The reviewer_id is a Participant, which specifies a User who is participating in this assignment.
To achieve function of team-based review, a boolean field reviewer_is_team needs to be added to ResponseMap to determines whether the reviewer is a AssignmentParticipant or an AssignmentTeam. If reviewer_is_team is true, then the reviewer_id would refer to a record in the teams table, not a record in the participants table.
And a field reviewer_is_team is also need to be added to the assignments table as well to indicate the assignment is an individual-based review or team-based review.
===Controller===
The method sending a message to the reviewer should be implemented appropriately in both Participant and AssignmentTeam.
=== View ===
Several parts of the system need to work regardless of whether the reviewer is an individual or a team, like “View my scores” and “Alternative view”.
For an Instructor to specify whether the view is team-based or individual-based, we are intended to provide a dropdown on the Review Strategy tab of assignment creation.
Set a lock, so that a second team member cannot start to edit a review at the same time that another team member is editing it.

== Test Plan ==
=== RSpec ===
RSpec is a testing framework for Rails, and is a Behavioral-Driven Development tool. It is a domain specific language(DSL). All the tests can be executed by rspec spec command, or can also be executed individually using the command "rspec spec/models/assignment_team_spec.rb. We intend to write unit tests using RSpec for all the methods which we modified/created. We intend to write unit tests using RSpec for all the methods which we modified/created.

CSC/ECE 517 Fall 2016/E1662. UI issues/fixes

2016-11-10T04:10:53Z

Xding3: /* How was this Issue Fixed? */

= UI Issues/Fixes =

=== Background ===
Expertiza is an open source web application developed by students and faculty members of North Carolina State University. This portal is being used by both faculty members and students in order to carry out assignments. Typically following is the workflow of the system:
* Faculty member adds students to a particular course. He also adds an assignment for the class.
* Assignment has a specific deadline, review period and final submission.
* Faculty members upload list of topics for the assignment.
* Students have to bid for the topic or they can suggest their own topic.
* At the end of the bidding process, students get a specific topic for the assignment.
* Students can form the teams by sending out invitations to other students.
* Students start working on the assignment and submit the assignment work before the initial submission date.
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.
* Students are graded on the basis of their work and reviews.

=== Objective ===
The main objective this project is to fix the issues in the current system. The current system has following issues:

* Historically courses were created without providing Institution ID. Since data warehouse is now storing Institution ID for a particular course, this application should do support this function.
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank "Actions" column on the signup sheet still appears. It would be better if the column did not appear.
* Currently when admin/instructor tries to delete an assignment, there is no alert/confirmation shown. This is risky. We need to add a confirmation step to avoid losing data.

=== Issues ===
==== Issue#702 ====
===== How was this Issue Fixed? =====
Capturing Institution ID

Institution and Course has One-to-Many relationship where in one institution may have many courses associated with it. In current system while creating new course user does not have to choose which institution the course belongs to. Hence we need to fix this issue. Following basic changes are required in order to fix this issue.

* Ensure that relationship exists between Course and Institution model classes.
<pre>
# Establishing relationship between Course and Institution
class Institution < ActiveRecord::Base
has_many :courses, dependent: :destroy
end

class Course < ActiveRecord::Base
belongs_to :institution, class_name: 'Institution', foreign_key: 'instituition_id'
end
</pre>

* In ''app/views/course/_course.html.erb'', add a drop-down list so that user can select institution from the available options.
<pre>

<label for="course_instituition_id">Institution</label> 
<%= select_tag 'institution', options_from_collection_for_select(Institution.all,:id,:name) %>
</pre>

* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.
* Once we receive all the data in controller Institution ID should be saved in course table. Thus in ''app/controllers/course_controller.rb'', add arguments to the Create method.

<pre>
@course = Course.new(name: params[:course][:name], directory_path: params[:course][:directory_path], info: params[:course][:info], private: params[:course][:private], institutions_id: params[:institution])
</pre>

===== How to Test this fix? =====
* User should login to expertiza using Instructor's credentials.
* Go to Manage Courses and click on New Course button so as to open form for it.
* Fill up the form. you can see new field added as Institution Name. This is a drop down list which has list of Institutions.
* User has to select one of these institutions. If user tries to go ahead without selecting this then he will get an alert flash saying this is a required field.
* Once an institution is selected user can click on Create button to submit the form (with other fields completed).
* Institution ID would be saved in database record against this particular entry of course in Course table. User can verify this by accessing Course table in the database.

==== Issue#316 ====
===== How was this Issue Fixed? =====
When student open sign up sheet for the Finished projects, he should not be able to take any actions for that assignment and hence Actions column should be hidden to him. For fixing this bug, we had to make following changes into ''app/views/sign_up_sheet/_table_header.html.erb''.

<pre>
<% if @assignment.current_stage_name != "Finished" %>
<th width="10%">Actions</th>
<th width="5%">Advertisement(s)</th>
<% else %>
<th width="15%">Advertisement(s)</th>
<% end %>
</pre>

===== How to Test this fix? =====
* Login to expertiza using student credentials
* Go to assignment tab and look for the assignments which have current stage as "Finished"
* Go to that assignment and open sign-up sheet.
* You should not be able to see column Activities, which means the work is successful.

==== Issue#295 ====
===== How was this Issue Fixed? =====
When instructor clicks on delete button to delete assignment, It gets deleted without confirming it. System should ask for confirmation whether to go ahead with deletion or not. To post a confirmation to users, we used the flash method to put the message on the screen. When user is going to delete an assignment, he will firstly use the ''delete'' action in ''assignment'' model with parameter ''force=nil''. Thus in ''app/models/assignment.rb'', we added an condition in the beginning of the method to check whether it is the first attempt to delete the assignment. If it is, an exception will be raised.
<pre>
if(force.nil?)
raise "The delete action cannot be revoked."
end
</pre>

The exception will be caught in the assignment controller. Then corresponding messages are passed by flash method to be shown on the page.

<pre>
begin
@assignment_form = AssignmentForm.create_form_object(params[:id])
@user = session[:user]
id = @user.get_instructor
if id != @assignment_form.assignment.instructor_id
raise "You are not authorized to delete this assignment."
else
@assignment_form.delete(params[:force])
flash[:success] = "The assignment was successfully deleted."
end
rescue
error = $ERROR_INFO

url_accept = url_for action: 'delete', id: params[:id], force: 0
url_deny = list_tree_display_index_path

url_yes = url_for action: 'delete', id: params[:id], force: 1
url_no = list_tree_display_index_path

if(error.to_s == "The delete action cannot be revoked.")
flash[:error] = error.to_s + " Are you sure? <a href='#{url_accept}'>Yes</a> | <a href='#{url_deny}'>No</a> "
else
flash[:error] = error.to_s + " Delete this assignment anyway? <a href='#{url_yes}'>Yes</a> | <a href='#{url_no}'>No</a> "
end
end

</pre>

===== How to Test this fix? =====
* Login to Expertiza as an Instructor.
* Go to manage assignment page.
* Try deleting an assignment by clicking on an image from the activities column.
* When delete button is clicked, system should ask for confirmation message whether you really want to delete or not.
* If you select yes then that assignment should be deleted. Otherwise if selected no then that assignment should not be deleted.

== References ==
1. https://github.com/expertiza/expertiza - Github link for original repository

2. https://github.com/psabhyan/expertiza.git - Github Repository code for the updated code

CSC/ECE 517 Fall 2016/E1662. UI issues/fixes

2016-11-10T04:06:02Z

Xding3: /* How was this Issue Fixed? */

= UI Issues/Fixes =

=== Background ===
Expertiza is an open source web application developed by students and faculty members of North Carolina State University. This portal is being used by both faculty members and students in order to carry out assignments. Typically following is the workflow of the system:
* Faculty member adds students to a particular course. He also adds an assignment for the class.
* Assignment has a specific deadline, review period and final submission.
* Faculty members upload list of topics for the assignment.
* Students have to bid for the topic or they can suggest their own topic.
* At the end of the bidding process, students get a specific topic for the assignment.
* Students can form the teams by sending out invitations to other students.
* Students start working on the assignment and submit the assignment work before the initial submission date.
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.
* Students are graded on the basis of their work and reviews.

=== Objective ===
The main objective this project is to fix the issues in the current system. The current system has following issues:

* Historically courses were created without providing Institution ID. Since data warehouse is now storing Institution ID for a particular course, this application should do support this function.
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank "Actions" column on the signup sheet still appears. It would be better if the column did not appear.
* Currently when admin/instructor tries to delete an assignment, there is no alert/confirmation shown. This is risky. We need to add a confirmation step to avoid losing data.

=== Issues ===
==== Issue#702 ====
===== How was this Issue Fixed? =====
Capturing Institution ID

Institution and Course has One-to-Many relationship where in one institution may have many courses associated with it. In current system while creating new course user does not have to choose which institution the course belongs to. Hence we need to fix this issue. Following basic changes are required in order to fix this issue.

* Ensure that relationship exists between Course and Institution model classes.
<pre>
# Establishing relationship between Course and Institution
class Institution < ActiveRecord::Base
has_many :courses, dependent: :destroy
end

class Course < ActiveRecord::Base
belongs_to :institution, class_name: 'Institution', foreign_key: 'instituition_id'
end
</pre>

* In ''app/views/course/_course.html.erb'', add a drop-down list so that user can select institution from the available options.
<pre>

<label for="course_instituition_id">Institution</label> 
<%= select_tag 'institution', options_from_collection_for_select(Institution.all,:id,:name) %>
</pre>

* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.
* Once we receive all the data in controller Institution ID should be saved in course table. Thus in ''app/controllers/course_controller.rb'', add arguments to the Create method.

<pre>
@course = Course.new(name: params[:course][:name], directory_path: params[:course][:directory_path], info: params[:course][:info], private: params[:course][:private], institutions_id: params[:institution])
</pre>

===== How to Test this fix? =====
* User should login to expertiza using Instructor's credentials.
* Go to Manage Courses and click on New Course button so as to open form for it.
* Fill up the form. you can see new field added as Institution Name. This is a drop down list which has list of Institutions.
* User has to select one of these institutions. If user tries to go ahead without selecting this then he will get an alert flash saying this is a required field.
* Once an institution is selected user can click on Create button to submit the form (with other fields completed).
* Institution ID would be saved in database record against this particular entry of course in Course table. User can verify this by accessing Course table in the database.

==== Issue#316 ====
===== How was this Issue Fixed? =====
When student open sign up sheet for the Finished projects, he should not be able to take any actions for that assignment and hence Actions column should be hidden to him. For fixing this bug, we had to make following changes into ''app/views/sign_up_sheet/_table_header.html.erb''.

<pre>
<% if @assignment.current_stage_name != "Finished" %>
<th width="10%">Actions</th>
<th width="5%">Advertisement(s)</th>
<% else %>
<th width="15%">Advertisement(s)</th>
<% end %>
</pre>

===== How to Test this fix? =====
* Login to expertiza using student credentials
* Go to assignment tab and look for the assignments which have current stage as "Finished"
* Go to that assignment and open sign-up sheet.
* You should not be able to see column Activities, which means the work is successful.

==== Issue#295 ====
===== How was this Issue Fixed? =====
When instructor clicks on delete button to delete assignment, It gets deleted without confirming it. System should ask for confirmation whether to go ahead with deletion or not. To post a confirmation to users, we used the flash method to put the message on the screen. When the user is going to delete an assignment, he will firstly use the ''delete'' action of ''assignment'' controller with parameter ''force=nil''. Thus in ''app/models/assignment.rb'', we added an condition to check whether it is the first attempt to delete the assignment. If it is, an exception will be raised.
<pre>
if(force.nil?)
raise "The delete action cannot be revoked."
end
</pre>

The exception will be caught in the assignment controller. Corresponding messages are passed by flash method to the page.

<pre>
begin
@assignment_form = AssignmentForm.create_form_object(params[:id])
@user = session[:user]
id = @user.get_instructor
if id != @assignment_form.assignment.instructor_id
raise "You are not authorized to delete this assignment."
else
@assignment_form.delete(params[:force])
flash[:success] = "The assignment was successfully deleted."
end
rescue
error = $ERROR_INFO

url_accept = url_for action: 'delete', id: params[:id], force: 0
url_deny = list_tree_display_index_path

url_yes = url_for action: 'delete', id: params[:id], force: 1
url_no = list_tree_display_index_path

if(error.to_s == "The delete action cannot be revoked.")
flash[:error] = error.to_s + " Are you sure? <a href='#{url_accept}'>Yes</a> | <a href='#{url_deny}'>No</a> "
else
flash[:error] = error.to_s + " Delete this assignment anyway? <a href='#{url_yes}'>Yes</a> | <a href='#{url_no}'>No</a> "
end

</pre>

===== How to Test this fix? =====
* Login to Expertiza as an Instructor.
* Go to manage assignment page.
* Try deleting an assignment by clicking on an image from the activities column.
* When delete button is clicked, system should ask for confirmation message whether you really want to delete or not.
* If you select yes then that assignment should be deleted. Otherwise if selected no then that assignment should not be deleted.

== References ==
1. https://github.com/expertiza/expertiza - Github link for original repository

2. https://github.com/psabhyan/expertiza.git - Github Repository code for the updated code

CSC/ECE 517 Fall 2016/E1662. UI issues/fixes

2016-11-10T04:00:18Z

Xding3: /* How was this Issue Fixed? */

= UI Issues/Fixes =

=== Background ===
Expertiza is an open source web application developed by students and faculty members of North Carolina State University. This portal is being used by both faculty members and students in order to carry out assignments. Typically following is the workflow of the system:
* Faculty member adds students to a particular course. He also adds an assignment for the class.
* Assignment has a specific deadline, review period and final submission.
* Faculty members upload list of topics for the assignment.
* Students have to bid for the topic or they can suggest their own topic.
* At the end of the bidding process, students get a specific topic for the assignment.
* Students can form the teams by sending out invitations to other students.
* Students start working on the assignment and submit the assignment work before the initial submission date.
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.
* Students are graded on the basis of their work and reviews.

=== Objective ===
The main objective this project is to fix the issues in the current system. The current system has following issues:

* Historically courses were created without providing Institution ID. Since data warehouse is now storing Institution ID for a particular course, this application should do support this function.
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank "Actions" column on the signup sheet still appears. It would be better if the column did not appear.
* Currently when admin/instructor tries to delete an assignment, there is no alert/confirmation shown. This is risky. We need to add a confirmation step to avoid losing data.

=== Issues ===
==== Issue#702 ====
===== How was this Issue Fixed? =====
Capturing Institution ID

Institution and Course has One-to-Many relationship where in one institution may have many courses associated with it. In current system while creating new course user does not have to choose which institution the course belongs to. Hence we need to fix this issue. Following basic changes are required in order to fix this issue.

* Ensure that relationship exists between Course and Institution model classes.
<pre>
# Establishing relationship between Course and Institution
class Institution < ActiveRecord::Base
has_many :courses, dependent: :destroy
end

class Course < ActiveRecord::Base
belongs_to :institution, class_name: 'Institution', foreign_key: 'instituition_id'
end
</pre>

* In ''app/views/course/_course.html.erb'', add a drop-down list so that user can select institution from the available options.
<pre>

<label for="course_instituition_id">Institution</label> 
<%= select_tag 'institution', options_from_collection_for_select(Institution.all,:id,:name) %>
</pre>

* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.
* Once we receive all the data in controller Institution ID should be saved in course table. Thus in ''app/controllers/course_controller.rb'', add arguments to the Create method.

<pre>
@course = Course.new(name: params[:course][:name], directory_path: params[:course][:directory_path], info: params[:course][:info], private: params[:course][:private], institutions_id: params[:institution])
</pre>

===== How to Test this fix? =====
* User should login to expertiza using Instructor's credentials.
* Go to Manage Courses and click on New Course button so as to open form for it.
* Fill up the form. you can see new field added as Institution Name. This is a drop down list which has list of Institutions.
* User has to select one of these institutions. If user tries to go ahead without selecting this then he will get an alert flash saying this is a required field.
* Once an institution is selected user can click on Create button to submit the form (with other fields completed).
* Institution ID would be saved in database record against this particular entry of course in Course table. User can verify this by accessing Course table in the database.

==== Issue#316 ====
===== How was this Issue Fixed? =====
When student open sign up sheet for the Finished projects, he should not be able to take any actions for that assignment and hence Actions column should be hidden to him. For fixing this bug, we had to make following changes into ''app/views/sign_up_sheet/_table_header.html.erb''.

<pre>
<% if @assignment.current_stage_name != "Finished" %>
<th width="10%">Actions</th>
<th width="5%">Advertisement(s)</th>
<% else %>
<th width="15%">Advertisement(s)</th>
<% end %>
</pre>

===== How to Test this fix? =====
* Login to expertiza using student credentials
* Go to assignment tab and look for the assignments which have current stage as "Finished"
* Go to that assignment and open sign-up sheet.
* You should not be able to see column Activities, which means the work is successful.

==== Issue#295 ====
===== How was this Issue Fixed? =====
When instructor clicks on delete button to delete assignment, It gets deleted without confirming it. System should ask for confirmation whether to go ahead with deletion or not. To post a confirmation to users, we used the flash method to put the message on the screen. When the user is going to delete an assignment, he will firstly use the ''delete'' action of ''assignment'' controller with parameter ''force=nil''. Thus in ''app/models/assignment.rb'', we added an condition to check whether it is the first attempt to delete the assignment. If it is, an exception will be raised.
<pre>
if(force.nil?)
raise "The delete action cannot be revoked."
end

===== How to Test this fix? =====
* Login to Expertiza as an Instructor.
* Go to manage assignment page.
* Try deleting an assignment by clicking on an image from the activities column.
* When delete button is clicked, system should ask for confirmation message whether you really want to delete or not.
* If you select yes then that assignment should be deleted. Otherwise if selected no then that assignment should not be deleted.

== References ==
1. https://github.com/expertiza/expertiza - Github link for original repository

2. https://github.com/psabhyan/expertiza.git - Github Repository code for the updated code

CSC/ECE 517 Fall 2016/E1662. UI issues/fixes

2016-11-10T03:39:44Z

Xding3: /* How to Test this fix? */

= UI Issues/Fixes =

=== Background ===
Expertiza is an open source web application developed by students and faculty members of North Carolina State University. This portal is being used by both faculty members and students in order to carry out assignments. Typically following is the workflow of the system:
* Faculty member adds students to a particular course. He also adds an assignment for the class.
* Assignment has a specific deadline, review period and final submission.
* Faculty members upload list of topics for the assignment.
* Students have to bid for the topic or they can suggest their own topic.
* At the end of the bidding process, students get a specific topic for the assignment.
* Students can form the teams by sending out invitations to other students.
* Students start working on the assignment and submit the assignment work before the initial submission date.
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.
* Students are graded on the basis of their work and reviews.

=== Objective ===
The main objective this project is to fix the issues in the current system. The current system has following issues:

* Historically courses were created without providing Institution ID. Since data warehouse is now storing Institution ID for a particular course, this application should do support this function.
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank "Actions" column on the signup sheet still appears. It would be better if the column did not appear.
* Currently when admin/instructor tries to delete an assignment, there is no alert/confirmation shown. This is risky. We need to add a confirmation step to avoid losing data.

=== Issues ===
==== Issue#702 ====
===== How was this Issue Fixed? =====
Capturing Institution ID

Institution and Course has One-to-Many relationship where in one institution may have many courses associated with it. In current system while creating new course user does not have to choose which institution the course belongs to. Hence we need to fix this issue. Following basic changes are required in order to fix this issue.

* Ensure that relationship exists between Course and Institution model classes.
<pre>
# Establishing relationship between Course and Institution
class Institution < ActiveRecord::Base
has_many :courses, dependent: :destroy
end

class Course < ActiveRecord::Base
belongs_to :institution, class_name: 'Institution', foreign_key: 'instituition_id'
end
</pre>

* In ''app/views/course/_course.html.erb'', add a drop-down list so that user can select institution from the available options.
<pre>

<label for="course_instituition_id">Institution</label> 
<%= select_tag 'institution', options_from_collection_for_select(Institution.all,:id,:name) %>
</pre>

* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.
* Once we receive all the data in controller Institution ID should be saved in course table. Thus in ''app/controllers/course_controller.rb'', add arguments to the Create method.

<pre>
@course = Course.new(name: params[:course][:name], directory_path: params[:course][:directory_path], info: params[:course][:info], private: params[:course][:private], institutions_id: params[:institution])
</pre>

===== How to Test this fix? =====
* User should login to expertiza using Instructor's credentials.
* Go to Manage Courses and click on New Course button so as to open form for it.
* Fill up the form. you can see new field added as Institution Name. This is a drop down list which has list of Institutions.
* User has to select one of these institutions. If user tries to go ahead without selecting this then he will get an alert flash saying this is a required field.
* Once an institution is selected user can click on Create button to submit the form (with other fields completed).
* Institution ID would be saved in database record against this particular entry of course in Course table. User can verify this by accessing Course table in the database.

==== Issue#316 ====
===== How was this Issue Fixed? =====
When student open sign up sheet for the Finished projects, he should not be able to take any actions for that assignment and hence Actions column should be hidden to him. For fixing this bug, we had to make following changes into ''app/views/sign_up_sheet/_table_header.html.erb''.

<pre>
<% if @assignment.current_stage_name != "Finished" %>
<th width="10%">Actions</th>
<th width="5%">Advertisement(s)</th>
<% else %>
<th width="15%">Advertisement(s)</th>
<% end %>
</pre>

===== How to Test this fix? =====
* Login to expertiza using student credentials
* Go to assignment tab and look for the assignments which have current stage as "Finished"
* Go to that assignment and open sign-up sheet.
* You should not be able to see column Activities, which means the work is successful.

==== Issue#295 ====
===== How was this Issue Fixed? =====
When instructor clicks on delete button to delete courses/assignment, It gets deleted without confirming it. System should ask for confirmation whether to go ahead with deletion or not. We had to make following changes in _shared_action.html.erb
<pre>
<%= link_to image_tag('/assets/tree_view/delete-icon-24.png', :title => 'Delete ' + model.downcase),
{ :controller => controller, :action=>'delete', :id => node.node_object_id , :data => {:confirm => 'Are you sure you want to delete?'}},
{ :title => 'Delete ' + model.downcase } %>
</pre>

===== How to Test this fix? =====
* Login to Expertiza as an Instructor.
* Go to manage assignment page.
* Try deleting an assignment by clicking on an image from the activities column.
* When delete button is clicked, system should ask for confirmation message whether you really want to delete or not.
* If you select yes then that assignment should be deleted. Otherwise if selected no then that assignment should not be deleted.

== References ==
1. https://github.com/expertiza/expertiza - Github link for original repository

2. https://github.com/psabhyan/expertiza.git - Github Repository code for the updated code

CSC/ECE 517 Fall 2016/E1662. UI issues/fixes

2016-11-10T03:38:54Z

Xding3: /* How was this Issue Fixed? */

= UI Issues/Fixes =

=== Background ===
Expertiza is an open source web application developed by students and faculty members of North Carolina State University. This portal is being used by both faculty members and students in order to carry out assignments. Typically following is the workflow of the system:
* Faculty member adds students to a particular course. He also adds an assignment for the class.
* Assignment has a specific deadline, review period and final submission.
* Faculty members upload list of topics for the assignment.
* Students have to bid for the topic or they can suggest their own topic.
* At the end of the bidding process, students get a specific topic for the assignment.
* Students can form the teams by sending out invitations to other students.
* Students start working on the assignment and submit the assignment work before the initial submission date.
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.
* Students are graded on the basis of their work and reviews.

=== Objective ===
The main objective this project is to fix the issues in the current system. The current system has following issues:

* Historically courses were created without providing Institution ID. Since data warehouse is now storing Institution ID for a particular course, this application should do support this function.
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank "Actions" column on the signup sheet still appears. It would be better if the column did not appear.
* Currently when admin/instructor tries to delete an assignment, there is no alert/confirmation shown. This is risky. We need to add a confirmation step to avoid losing data.

=== Issues ===
==== Issue#702 ====
===== How was this Issue Fixed? =====
Capturing Institution ID

Institution and Course has One-to-Many relationship where in one institution may have many courses associated with it. In current system while creating new course user does not have to choose which institution the course belongs to. Hence we need to fix this issue. Following basic changes are required in order to fix this issue.

* Ensure that relationship exists between Course and Institution model classes.
<pre>
# Establishing relationship between Course and Institution
class Institution < ActiveRecord::Base
has_many :courses, dependent: :destroy
end

class Course < ActiveRecord::Base
belongs_to :institution, class_name: 'Institution', foreign_key: 'instituition_id'
end
</pre>

* In ''app/views/course/_course.html.erb'', add a drop-down list so that user can select institution from the available options.
<pre>

<label for="course_instituition_id">Institution</label> 
<%= select_tag 'institution', options_from_collection_for_select(Institution.all,:id,:name) %>
</pre>

* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.
* Once we receive all the data in controller Institution ID should be saved in course table. Thus in ''app/controllers/course_controller.rb'', add arguments to the Create method.

<pre>
@course = Course.new(name: params[:course][:name], directory_path: params[:course][:directory_path], info: params[:course][:info], private: params[:course][:private], institutions_id: params[:institution])
</pre>

===== How to Test this fix? =====
* User should login to expertiza using Instructor's credentials.
* Go to Manage Courses and click on New Course button so as to open form for it.
* Fill up the form. you can see new field added as Institution Name. This is a drop down list which has list of Institutions.
* User has to select one of these institutions. If user tries to go ahead without selecting this then he will get an alert flash saying this is a required field.
* Once an institution is selected user can click on Create button to submit the form (with other fields completed).
* Institution ID would be saved in database record against this particular entry of course in Course table. User can verify this by accessing Course table in the database.

==== Issue#316 ====
===== How was this Issue Fixed? =====
When student open sign up sheet for the Finished projects, he should not be able to take any actions for that assignment and hence Actions column should be hidden to him. For fixing this bug, we had to make following changes into ''app/views/sign_up_sheet/_table_header.html.erb''.

<pre>
<% if @assignment.current_stage_name != "Finished" %>
<th width="10%">Actions</th>
<th width="5%">Advertisement(s)</th>
<% else %>
<th width="15%">Advertisement(s)</th>
<% end %>
</pre>

===== How to Test this fix? =====
* Login to expertiza using student credentials
* Go to assignment tab
* Look for the assignments which have current stage as "Finished"
* Go to that assignment and open sign-up sheet.
* You should not be able to see column Activities. If you don't see this column then the test is successful.

==== Issue#295 ====
===== How was this Issue Fixed? =====
When instructor clicks on delete button to delete courses/assignment, It gets deleted without confirming it. System should ask for confirmation whether to go ahead with deletion or not. We had to make following changes in _shared_action.html.erb
<pre>
<%= link_to image_tag('/assets/tree_view/delete-icon-24.png', :title => 'Delete ' + model.downcase),
{ :controller => controller, :action=>'delete', :id => node.node_object_id , :data => {:confirm => 'Are you sure you want to delete?'}},
{ :title => 'Delete ' + model.downcase } %>
</pre>

===== How to Test this fix? =====
* Login to Expertiza as an Instructor.
* Go to manage assignment page.
* Try deleting an assignment by clicking on an image from the activities column.
* When delete button is clicked, system should ask for confirmation message whether you really want to delete or not.
* If you select yes then that assignment should be deleted. Otherwise if selected no then that assignment should not be deleted.

== References ==
1. https://github.com/expertiza/expertiza - Github link for original repository

2. https://github.com/psabhyan/expertiza.git - Github Repository code for the updated code

CSC/ECE 517 Fall 2016/E1662. UI issues/fixes

2016-11-10T03:34:14Z

Xding3: /* How to Test this fix? */

= UI Issues/Fixes =

=== Background ===
Expertiza is an open source web application developed by students and faculty members of North Carolina State University. This portal is being used by both faculty members and students in order to carry out assignments. Typically following is the workflow of the system:
* Faculty member adds students to a particular course. He also adds an assignment for the class.
* Assignment has a specific deadline, review period and final submission.
* Faculty members upload list of topics for the assignment.
* Students have to bid for the topic or they can suggest their own topic.
* At the end of the bidding process, students get a specific topic for the assignment.
* Students can form the teams by sending out invitations to other students.
* Students start working on the assignment and submit the assignment work before the initial submission date.
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.
* Students are graded on the basis of their work and reviews.

=== Objective ===
The main objective this project is to fix the issues in the current system. The current system has following issues:

* Historically courses were created without providing Institution ID. Since data warehouse is now storing Institution ID for a particular course, this application should do support this function.
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank "Actions" column on the signup sheet still appears. It would be better if the column did not appear.
* Currently when admin/instructor tries to delete an assignment, there is no alert/confirmation shown. This is risky. We need to add a confirmation step to avoid losing data.

=== Issues ===
==== Issue#702 ====
===== How was this Issue Fixed? =====
Capturing Institution ID

Institution and Course has One-to-Many relationship where in one institution may have many courses associated with it. In current system while creating new course user does not have to choose which institution the course belongs to. Hence we need to fix this issue. Following basic changes are required in order to fix this issue.

* Ensure that relationship exists between Course and Institution model classes.
<pre>
# Establishing relationship between Course and Institution
class Institution < ActiveRecord::Base
has_many :courses, dependent: :destroy
end

class Course < ActiveRecord::Base
belongs_to :institution, class_name: 'Institution', foreign_key: 'instituition_id'
end
</pre>

* In ''app/views/course/_course.html.erb'', add a drop-down list so that user can select institution from the available options.
<pre>

<label for="course_instituition_id">Institution</label> 
<%= select_tag 'institution', options_from_collection_for_select(Institution.all,:id,:name) %>
</pre>

* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.
* Once we receive all the data in controller Institution ID should be saved in course table. Thus in ''app/controllers/course_controller.rb'', add arguments to the Create method.

<pre>
@course = Course.new(name: params[:course][:name], directory_path: params[:course][:directory_path], info: params[:course][:info], private: params[:course][:private], institutions_id: params[:institution])
</pre>

===== How to Test this fix? =====
* User should login to expertiza using Instructor's credentials.
* Go to Manage Courses and click on New Course button so as to open form for it.
* Fill up the form. you can see new field added as Institution Name. This is a drop down list which has list of Institutions.
* User has to select one of these institutions. If user tries to go ahead without selecting this then he will get an alert flash saying this is a required field.
* Once an institution is selected user can click on Create button to submit the form (with other fields completed).
* Institution ID would be saved in database record against this particular entry of course in Course table. User can verify this by accessing Course table in the database.

==== Issue#316 ====
===== How was this Issue Fixed? =====
When student open sign up sheet for the Finished projects, he should not be able to take any actions for that assignment and hence Actions column should be hidden to him. For fixing this bug, we had to make following changes into sign_up_sheet/_table_line.html.erb.
<pre>
<%if !@assignment.get_current_stage.eql?"Finished"%>
<td align="center">
<%= render :partial => '/sign_up_sheet/actions',
:locals => {:i=>i,:topic=>topic, :is_suggested_topic=>is_suggested_topic ||= false} %>
</td>
<%end%>
</pre>

===== How to Test this fix? =====
* Login to expertiza using student credentials
* Go to assignment tab
* Look for the assignments which have current stage as "Finished"
* Go to that assignment and open sign-up sheet.
* You should not be able to see column Activities. If you don't see this column then the test is successful.

==== Issue#295 ====
===== How was this Issue Fixed? =====
When instructor clicks on delete button to delete courses/assignment, It gets deleted without confirming it. System should ask for confirmation whether to go ahead with deletion or not. We had to make following changes in _shared_action.html.erb
<pre>
<%= link_to image_tag('/assets/tree_view/delete-icon-24.png', :title => 'Delete ' + model.downcase),
{ :controller => controller, :action=>'delete', :id => node.node_object_id , :data => {:confirm => 'Are you sure you want to delete?'}},
{ :title => 'Delete ' + model.downcase } %>
</pre>

===== How to Test this fix? =====
* Login to Expertiza as an Instructor.
* Go to manage assignment page.
* Try deleting an assignment by clicking on an image from the activities column.
* When delete button is clicked, system should ask for confirmation message whether you really want to delete or not.
* If you select yes then that assignment should be deleted. Otherwise if selected no then that assignment should not be deleted.

== References ==
1. https://github.com/expertiza/expertiza - Github link for original repository

2. https://github.com/psabhyan/expertiza.git - Github Repository code for the updated code

CSC/ECE 517 Fall 2016/E1662. UI issues/fixes

2016-11-10T03:33:57Z

Xding3: /* How to Test this fix? */

= UI Issues/Fixes =

=== Background ===
Expertiza is an open source web application developed by students and faculty members of North Carolina State University. This portal is being used by both faculty members and students in order to carry out assignments. Typically following is the workflow of the system:
* Faculty member adds students to a particular course. He also adds an assignment for the class.
* Assignment has a specific deadline, review period and final submission.
* Faculty members upload list of topics for the assignment.
* Students have to bid for the topic or they can suggest their own topic.
* At the end of the bidding process, students get a specific topic for the assignment.
* Students can form the teams by sending out invitations to other students.
* Students start working on the assignment and submit the assignment work before the initial submission date.
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.
* Students are graded on the basis of their work and reviews.

=== Objective ===
The main objective this project is to fix the issues in the current system. The current system has following issues:

* Historically courses were created without providing Institution ID. Since data warehouse is now storing Institution ID for a particular course, this application should do support this function.
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank "Actions" column on the signup sheet still appears. It would be better if the column did not appear.
* Currently when admin/instructor tries to delete an assignment, there is no alert/confirmation shown. This is risky. We need to add a confirmation step to avoid losing data.

=== Issues ===
==== Issue#702 ====
===== How was this Issue Fixed? =====
Capturing Institution ID

Institution and Course has One-to-Many relationship where in one institution may have many courses associated with it. In current system while creating new course user does not have to choose which institution the course belongs to. Hence we need to fix this issue. Following basic changes are required in order to fix this issue.

* Ensure that relationship exists between Course and Institution model classes.
<pre>
# Establishing relationship between Course and Institution
class Institution < ActiveRecord::Base
has_many :courses, dependent: :destroy
end

class Course < ActiveRecord::Base
belongs_to :institution, class_name: 'Institution', foreign_key: 'instituition_id'
end
</pre>

* In ''app/views/course/_course.html.erb'', add a drop-down list so that user can select institution from the available options.
<pre>

<label for="course_instituition_id">Institution</label> 
<%= select_tag 'institution', options_from_collection_for_select(Institution.all,:id,:name) %>
</pre>

* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.
* Once we receive all the data in controller Institution ID should be saved in course table. Thus in ''app/controllers/course_controller.rb'', add arguments to the Create method.

<pre>
@course = Course.new(name: params[:course][:name], directory_path: params[:course][:directory_path], info: params[:course][:info], private: params[:course][:private], institutions_id: params[:institution])
</pre>

===== How to Test this fix? =====
* User should login to expertiza using Instructor's credentials.
* Go to Manage Courses and click on New Course button so as to open form for it.
* Fill up the form. you can see new field added as Institution Name. This is a drop down list which has list of Institutions.
* User has to select one of these institutions. If user tries to go ahead without selecting this then he will get an alert flash saying this is a required field.
* Once an institution is selected user can click on Create button to submit the form (with other fields completed).
* Institution Id would be saved in database record against this particular entry of course in Course table. User can verify this by accessing Course table in the database.

==== Issue#316 ====
===== How was this Issue Fixed? =====
When student open sign up sheet for the Finished projects, he should not be able to take any actions for that assignment and hence Actions column should be hidden to him. For fixing this bug, we had to make following changes into sign_up_sheet/_table_line.html.erb.
<pre>
<%if !@assignment.get_current_stage.eql?"Finished"%>
<td align="center">
<%= render :partial => '/sign_up_sheet/actions',
:locals => {:i=>i,:topic=>topic, :is_suggested_topic=>is_suggested_topic ||= false} %>
</td>
<%end%>
</pre>

===== How to Test this fix? =====
* Login to expertiza using student credentials
* Go to assignment tab
* Look for the assignments which have current stage as "Finished"
* Go to that assignment and open sign-up sheet.
* You should not be able to see column Activities. If you don't see this column then the test is successful.

==== Issue#295 ====
===== How was this Issue Fixed? =====
When instructor clicks on delete button to delete courses/assignment, It gets deleted without confirming it. System should ask for confirmation whether to go ahead with deletion or not. We had to make following changes in _shared_action.html.erb
<pre>
<%= link_to image_tag('/assets/tree_view/delete-icon-24.png', :title => 'Delete ' + model.downcase),
{ :controller => controller, :action=>'delete', :id => node.node_object_id , :data => {:confirm => 'Are you sure you want to delete?'}},
{ :title => 'Delete ' + model.downcase } %>
</pre>

===== How to Test this fix? =====
* Login to Expertiza as an Instructor.
* Go to manage assignment page.
* Try deleting an assignment by clicking on an image from the activities column.
* When delete button is clicked, system should ask for confirmation message whether you really want to delete or not.
* If you select yes then that assignment should be deleted. Otherwise if selected no then that assignment should not be deleted.

== References ==
1. https://github.com/expertiza/expertiza - Github link for original repository

2. https://github.com/psabhyan/expertiza.git - Github Repository code for the updated code

CSC/ECE 517 Fall 2016/E1662. UI issues/fixes

2016-11-10T03:32:14Z

Xding3: /* How was this Issue Fixed? */

= UI Issues/Fixes =

=== Background ===
Expertiza is an open source web application developed by students and faculty members of North Carolina State University. This portal is being used by both faculty members and students in order to carry out assignments. Typically following is the workflow of the system:
* Faculty member adds students to a particular course. He also adds an assignment for the class.
* Assignment has a specific deadline, review period and final submission.
* Faculty members upload list of topics for the assignment.
* Students have to bid for the topic or they can suggest their own topic.
* At the end of the bidding process, students get a specific topic for the assignment.
* Students can form the teams by sending out invitations to other students.
* Students start working on the assignment and submit the assignment work before the initial submission date.
* Every student then gets to review work submitted by at least one team. Student submit their feedback in the review.
* Students then make the necessary changes as suggested by reviewer and submit the assignment before the final submission date.
* Students are graded on the basis of their work and reviews.

=== Objective ===
The main objective this project is to fix the issues in the current system. The current system has following issues:

* Historically courses were created without providing Institution ID. Since data warehouse is now storing Institution ID for a particular course, this application should do support this function.
* If an assignment is completed, no one can sign up for topics or drop topics. Yet a completely blank "Actions" column on the signup sheet still appears. It would be better if the column did not appear.
* Currently when admin/instructor tries to delete an assignment, there is no alert/confirmation shown. This is risky. We need to add a confirmation step to avoid losing data.

=== Issues ===
==== Issue#702 ====
===== How was this Issue Fixed? =====
Capturing Institution ID

Institution and Course has One-to-Many relationship where in one institution may have many courses associated with it. In current system while creating new course user does not have to choose which institution the course belongs to. Hence we need to fix this issue. Following basic changes are required in order to fix this issue.

* Ensure that relationship exists between Course and Institution model classes.
<pre>
# Establishing relationship between Course and Institution
class Institution < ActiveRecord::Base
has_many :courses, dependent: :destroy
end

class Course < ActiveRecord::Base
belongs_to :institution, class_name: 'Institution', foreign_key: 'instituition_id'
end
</pre>

* In ''app/views/course/_course.html.erb'', add a drop-down list so that user can select institution from the available options.
<pre>

<label for="course_instituition_id">Institution</label> 
<%= select_tag 'institution', options_from_collection_for_select(Institution.all,:id,:name) %>
</pre>

* Ensure that the id for the selected institution is sent as a parameter along with other parameters back to controller.
* Once we receive all the data in controller Institution ID should be saved in course table. Thus in ''app/controllers/course_controller.rb'', add arguments to the Create method.

<pre>
@course = Course.new(name: params[:course][:name], directory_path: params[:course][:directory_path], info: params[:course][:info], private: params[:course][:private], institutions_id: params[:institution])
</pre>

===== How to Test this fix? =====
* User should login to expertiza using Instructor's credentials.
* Go to Manage Courses
* Click on New Course button so as to open form for it.
* Fill up the form. you can see new field added as Institution Name. This is a drop down list which has list of Institutions.
* User has to select one of these institutions. If user tries to go ahead without selecting this then he will get an alert flash saying this is a required field.
* Once an institution is selected user can click on Create button to submit the form.
* Institution Id would be saved in database record against this particular entry of course in Course table. User can verify this by accessing Course table in the database.
==== Issue#316 ====
===== How was this Issue Fixed? =====
When student open sign up sheet for the Finished projects, he should not be able to take any actions for that assignment and hence Actions column should be hidden to him. For fixing this bug, we had to make following changes into sign_up_sheet/_table_line.html.erb.
<pre>
<%if !@assignment.get_current_stage.eql?"Finished"%>
<td align="center">
<%= render :partial => '/sign_up_sheet/actions',
:locals => {:i=>i,:topic=>topic, :is_suggested_topic=>is_suggested_topic ||= false} %>
</td>
<%end%>
</pre>

===== How to Test this fix? =====
* Login to expertiza using student credentials
* Go to assignment tab
* Look for the assignments which have current stage as "Finished"
* Go to that assignment and open sign-up sheet.
* You should not be able to see column Activities. If you don't see this column then the test is successful.

==== Issue#295 ====
===== How was this Issue Fixed? =====
When instructor clicks on delete button to delete courses/assignment, It gets deleted without confirming it. System should ask for confirmation whether to go ahead with deletion or not. We had to make following changes in _shared_action.html.erb
<pre>
<%= link_to image_tag('/assets/tree_view/delete-icon-24.png', :title => 'Delete ' + model.downcase),
{ :controller => controller, :action=>'delete', :id => node.node_object_id , :data => {:confirm => 'Are you sure you want to delete?'}},
{ :title => 'Delete ' + model.downcase } %>
</pre>

===== How to Test this fix? =====
* Login to Expertiza as an Instructor.
* Go to manage assignment page.
* Try deleting an assignment by clicking on an image from the activities column.
* When delete button is clicked, system should ask for confirmation message whether you really want to delete or not.
* If you select yes then that assignment should be deleted. Otherwise if selected no then that assignment should not be deleted.

== References ==
1. https://github.com/expertiza/expertiza - Github link for original repository

2. https://github.com/psabhyan/expertiza.git - Github Repository code for the updated code