Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2017/E1798 Role-based Reviewing

2017-11-15T16:28:05Z

Amehta8:

== Problem Statement ==
In various agile methodologies, such as Scrum, different team members take on different duties, such as architect, designer, tester and implementer. Currently, there is no functionality that enables this. The purpose of this project is to assign different duties to team members of an assignment. While reviewing too, there will be different rubrics for evaluating the contribution of members with different roles.

== Solution Plan ==
=== Task Description ===
1. A table 'duties' will be created. It will contain all the duties assigned in one assignment. 
2. While creating or editing an assignment, there will be a checkbox in the 'Review Strategies' tab, which will specify whether the assignment is a role-based assignment. 
3. If the checkbox is checked, different duties can be added to the assignment through the UI. 
4. When an assignment is a role-based assignment, the student should be able to assign duties to himself through the 'Your Team' page. In case the assignment does not allow multiple team members to take on the same duty, the student cannot pick a duty that has been picked by another member. 
5. While reviewing, there will be different rubrics associated with different duties, which can be created through the 'Questionnaires' tab on the homepage. 
6. When a particular teammate is being reviewed, the system should present the correct rubric based on the duty of the teammate. 

=== Proposed Database Changes ===
A new table called 'duties' will be created with the following structure - 
'''duty_name''' (varchar) - Name of the duty 
'''multiple_duty''' (boolean) - If multiple team members can have the same duty in one assignment, this field will be '''true'''. Otherwise, it should be '''false'''. 

The existing table 'assignments' will be modified to include the following fields - 
'''duty_flag''' (boolean) - If the assignment is role-based, this field will be '''true'''. Otherwise, it should be '''false'''. 

The existing table 'teams_users' will be modified to include the following fields - 
'''duty_id''' (varchar) - If the duty_flag is checked, this field will give the duty assigned to a team member for the assignment.

=== Proposed File Changes ===
''Controllers'' -

'''assignments_controller.rb''' - This is the controller that handles the actions performed by view in _review_stategy.html.erb.

New function 'save_duty' to be created - This will save the duties assigned to an assignment.

Existing function 'edit' to be modified - This function will save whether the assignment is role-based.

'''student_teams_controller.rb''' - The controller function for 'view' will be modified to show the duty and also select a duty for a team member so that review rubrics can be done based on that role.

New functions 'assign_duty' and 'select_duty' will be defined so that a team member can select a duty and save it.

''Views'' -

'''assignments/edit/_review_stategy.html.erb''' - This is view file that has the 'Review Strategy' form for a new or modified assignment. This view will have a checkbox that will specify whether the assignment is role-based.

'''assignments/edit/_rubrics.html.erb''' - This view file for the 'Rubrics' tab will specify the reviewing rubric that is applicable to each role.

'''student_teams/view.html.erb''' - This view shows the team members and their email id's. we can review them from here. If the assignment is a duty based one, then duties will be visible along side the existing fields. If the duties are not selected yet, then a set duties drop down will be visible.

=== UI Description ===

'''The new changes will be as follows in the UI - '''

The team would add the duties as -

[[File:Duty_team.png]]

The Instructor would mark the assignment where team members will have duties or not -

[[File:Assignmnet_duties.png]]

The Rubrics will added based on the role and a new text field will be added to do that -

[[File:Captureapo.png]]

== Use Case Diagram ==

[[File:UseCaseDiagram1.jpg]]

'''Actors''' - Instructor and Student

'''1. Instructor''' 

Preconditions -
* Assume assignment to be a role-based assignment 
* Reviewing rubrics for different duties have been created through the 'Questionnaires' tab.

Sequence of steps -
* Log into Expertiza 
* While creating an assignment, add duties that team members can take on through the 'Review Strategies' tab 
* On the 'Rubrics' tab, choose the pre-created reviewing rubrics for different duties 
* Finish creating the assignment

'''2. Student'''

Preconditions -
* Student is already a part of a team
* The assignment that the student is working on is a role-based assignment

Sequence of steps -
* Log into Expertiza 
* On 'Your Team' page, choose a duty to take on from a list of available duties (If multiple_duty is not enabled for a particular duty, the duty will be assigned to first member who chooses it, and will be disabled for the others) 
* On 'Your Team' page, click 'Review' link for a particular team member 
* Review the team mate based on the rubric loaded for his duty 

== Class Diagram ==

[[File:ClassDiagram.jpg]]

* The table 'duties' will contain the name of the duty and whether multiple team members can choose the same duty.
* Assignments will either be role-based or not, depending on the value of the duty flag. 
* The 'save_duty' and 'edit' functions in the AssignmentsController will allow saving the duties assigned to an assignment and saving whether the assignment is role-based. 
* The 'assign_duty' and 'select_duty' functions in StudentTeamsController be defined so that a team member can select a duty and save it. 

==Test Plan==
* For the instructor

1. While creating a new assignment, new checkbox will be available to make it a role-based assignment

2. If the checkbox is checked then the instructor will be able to add roles which will be applicable for the assignment

3. A role can be repeated among team members based on the role stored in the database.

4. New rubrics for a particular role can be added under Questionnaires tab for specific review questions based on role of a team member

* For the student in team

1. Once a student is in a team for the assignment with roles, they can pick up roles.

2. If a role does not allow multiple members, it will not be visible to other members to choose if chosen already.

2.1. A new view will open for selecting roles which are available.

2.2. The student can select an available role.

2.3. Once a role is selected by a member, it will not be visible for selection.

3. If a role allows multiple selection, multiple team members will be able to select a role.

4. When a peer review begins, the rubrics will be related to that particular role.

5. The members will review each member based on the role the member played for the assignment.

For assignments without roles, the peer reviews will be as per the current functionality with generalized review rubrics for all and not role based.

File:Captureapo.png

2017-11-08T02:42:20Z

Amehta8:

CSC/ECE 517 Fall 2017/E1798 Role-based Reviewing

2017-11-08T02:42:00Z

Amehta8: /* UI Description */

== Problem Statement ==
In various agile methodologies, such as Scrum, different team members take on different duties, such as architect, designer, tester and implementer. The purpose of this project is to assign different duties to team members of an assignment. While reviewing too, there will be different rubrics for evaluating the contribution of members with different roles.

== Solution Plan ==
=== Task Description ===
1. A table 'duties' will be created. It will contain all the duties assigned in one assignment. 
2. While creating or editing an assignment, there will be a checkbox in the 'Review Strategies' tab, which will specify whether the assignment is a role-based assignment. 
3. If the checkbox is checked, different duties can be added to the assignment through the UI. 
4. When an assignment is a role-based assignment, the student should be able to assign duties to himself through the 'Your Team' page of the team member. 
5. While reviewing, there will be different rubrics associated with different duties, which can be created through the 'Questionnaires' tab on the homepage. 
6. When a particular teammate is being reviewed, the system should present the correct rubric based on the duty of the teammate. 

=== Proposed Database Changes ===
A new table called 'duties' will be created with the following structure - 
'''assignment_number''' (numeric) - the assignment number that will have the duty, this will be the id field of table assignments (foreign key) 
'''duty_name''' (varchar) - duty assigned to that assignment number. 

The existing table 'assignments' will be modified to include the following fields - 
'''duty_flag''' (boolean) - If the assignment is role-based, this field will be '''true'''. Otherwise, it should be '''false'''. 
'''multiple_duty''' (boolean) - If multiple team members can have the same duty in one assignment, this field will be '''true'''. Otherwise, it should be '''false'''. 

The existing table 'teams_users' will be modified to include the following fields - 
'''duty_id''' (varchar) - If the duty_flag is checked, this field will give the duty assigned to a team member for the assignment.

=== Proposed File Changes ===
''Controllers'' -

'''assignments_controller.rb''' - This is the controller that handles the actions performed by view in _review_stategy.html.erb.
New function 'saveDuty' to be created - This will save the duties assigned to an assignment.

Existing function 'edit' to be modified - This function will save whether the assignment is role-based and whether multiple team members can have the same duties.

'''student_teams_controller.rb''' - The controller function for 'view' will be modified to show the duty and also select a duty for a team member so that review rubrics can be done based on that role.
New functions 'assignDuty' and 'selectDuty' will be defined so that a team member can select a duty and save it.

''Views'' -

'''assignments/edit/_review_stategy.html.erb''' - This is view file that has the 'Review Strategy' form for a new or modified assignment. This view will have a checkbox that will specify whether the assignment is role-based.

'''assignments/edit/_rubrics.html.erb''' - This view file for the 'Rubrics' tab will specify the reviewing rubric that is applicable to each role.

'''student_teams/view.html.erb''' - This view shows the team members and their email id's. we can review them from here. If the assignment is a duty based one, then duties will be visible along side the existing fields. If the duties are not selected yet, then a set duties drop down will be visible.

=== UI Description ===

'''The new changes will be as follows in the UI - '''

The team would add the duties as -

[[File:Duty_team.png]]

The Instructor would mark the assignment where team members will have duties or not -

[[File:Assignmnet_duties.png]]

The Rubrics will added based on the role and a new text field will be added to do that -

[[File:Captureapo.png]]

== Use Case ==

CSC/ECE 517 Fall 2017/E1798 Role-based Reviewing

2017-11-08T02:41:16Z

Amehta8: /* UI Description */

CSC/ECE 517 Fall 2017/E1798 Role-based Reviewing

2017-11-08T02:20:36Z

Amehta8:

File:Assignmnet duties.png

2017-11-08T02:18:47Z

Amehta8: uploaded a new version of "File:Assignmnet duties.png"

File:Duty team.png

2017-11-08T02:17:53Z

Amehta8: uploaded a new version of "File:Duty team.png"

CSC/ECE 517 Fall 2017/E1798 Role-based Reviewing

2017-11-08T02:10:18Z

Amehta8:

== Problem Statement ==
In various agile methodologies, such as Scrum, different team members take on different duties, such as architect, designer, tester and implementer. The purpose of this project is to assign different duties to team members of an assignment. While reviewing too, there will be different rubrics for evaluating the contribution of members with different roles.

== Solution Plan ==
=== Task Description ===
1. A table 'duties' will be created. It will contain all the duties assigned in one assignment. 
2. While creating or editing an assignment, there will be a checkbox in the 'Review Strategies' tab, which will specify whether the assignment is a role-based assignment. 
3. If the checkbox is checked, different duties can be added to the assignment through the UI. 
4. When an assignment is a role-based assignment, the student should be able to assign duties to himself through the 'Your Team' page of the team member. 
5. While reviewing, there will be different rubrics associated with different duties, which can be created through the 'Questionnaires' tab on the homepage. 
6. When a particular teammate is being reviewed, the system should present the correct rubric based on the duty of the teammate. 

=== Proposed Database Changes ===
A new table called 'duties' will be created with the following structure - 
'''assignment_number''' (numeric) - the assignment number that will have the duty, this will be the id field of table assignments (foreign key) 
'''duty_name''' (varchar) - duty assigned to that assignment number. 

The existing table 'assignments' will be modified to include the following fields - 
'''duty_flag''' (boolean) - If the assignment is role-based, this field will be '''true'''. Otherwise, it should be '''false'''. 
'''multiple_duty''' (boolean) - If multiple team members can have the same duty in one assignment, this field will be '''true'''. Otherwise, it should be '''false'''. 

The existing table 'teams_users' will be modified to include the following fields - 
'''duty_id''' (varchar) - If the duty_flag is checked, this field will give the duty assigned to a team member for the assignment.

=== Proposed File Changes ===
''Controllers'' -

'''assignments_controller.rb''' - This is the controller that handles the actions performed by view in _review_stategy.html.erb.
New function 'saveDuty' to be created - This will save the duties assigned to an assignment.

Existing function 'edit' to be modified - This function will save whether the assignment is role-based and whether multiple team members can have the same duties.

'''student_teams_controller.rb''' - The controller function for 'view' will be modified to show the duty and also select a duty for a team member so that review rubrics can be done based on that role.
New functions 'assignDuty' and 'selectDuty' will be defined so that a team member can select a duty and save it.

''Views'' -

'''assignments/edit/_review_stategy.html.erb''' - This is view file that has the 'Review Strategy' form for a new or modified assignment. This view will have a checkbox that will specify whether the assignment is role-based.

'''assignments/edit/_rubrics.html.erb''' - This view file for the 'Rubrics' tab will specify the reviewing rubric that is applicable to each role.

'''student_teams/view.html.erb''' - This view shows the team members and their email id's. we can review them from here. If the assignment is a duty based one, then duties will be visible along side the existing fields. If the duties are not selected yet, then a set duties drop down will be visible.

=== UI Description ===

'''The new changes will be as follows in the UI - '''
The team would add the duties as -

[[File:Duty_team.png]]

The Instructor would mark the assignment where team members will have duties or not -
[[File:Assignmnet_duties.png]]

== Use Case ==

File:Assignmnet duties.png

2017-11-08T02:04:42Z

Amehta8: uploaded a new version of "File:Assignmnet duties.png"

File:Duty team.png

2017-11-08T02:04:04Z

Amehta8: uploaded a new version of "File:Duty team.png"

File:Assignmnet duties.png

2017-11-08T02:00:46Z

Amehta8:

CSC/ECE 517 Fall 2017/E1798 Role-based Reviewing

2017-11-08T01:54:14Z

Amehta8:

== Problem Statement ==
In various agile methodologies, such as Scrum, different team members take on different duties, such as architect, designer, tester and implementer. The purpose of this project is to assign different duties to team members of an assignment. While reviewing too, there will be different rubrics for evaluating the contribution of members with different roles.

== Solution Plan ==
=== Task Description ===
1. A table 'duties' will be created. It will contain all the duties assigned in one assignment. 
2. While creating or editing an assignment, there will be a checkbox in the 'Review Strategies' tab, which will specify whether the assignment is a role-based assignment. 
3. If the checkbox is checked, different duties can be added to the assignment through the UI. 
4. When an assignment is a role-based assignment, the student should be able to assign duties to himself through the 'Your Team' page of the team member. 
5. While reviewing, there will be different rubrics associated with different duties, which can be created through the 'Questionnaires' tab on the homepage. 
6. When a particular teammate is being reviewed, the system should present the correct rubric based on the duty of the teammate. 

=== Proposed Database Changes ===
A new table called 'duties' will be created with the following structure - 
'''assignment_number''' (numeric) - the assignment number that will have the duty, this will be the id field of table assignments (foreign key) 
'''duty_name''' (varchar) - duty assigned to that assignment number. 

The existing table 'assignments' will be modified to include the following fields - 
'''duty_flag''' (boolean) - If the assignment is role-based, this field will be '''true'''. Otherwise, it should be '''false'''. 
'''multiple_duty''' (boolean) - If multiple team members can have the same duty in one assignment, this field will be '''true'''. Otherwise, it should be '''false'''. 

The existing table 'teams_users' will be modified to include the following fields - 
'''duty_id''' (varchar) - If the duty_flag is checked, this field will give the duty assigned to a team member for the assignment.

=== Proposed File Changes ===
''Controllers'' -

'''assignments_controller.rb''' - This is the controller that handles the actions performed by view in _review_stategy.html.erb.
New function 'saveDuty' to be created - This will save the duties assigned to an assignment.

Existing function 'edit' to be modified - This function will save whether the assignment is role-based and whether multiple team members can have the same duties.

'''student_teams_controller.rb''' - The controller function for 'view' will be modified to show the duty and also select a duty for a team member so that review rubrics can be done based on that role.
New functions 'assignDuty' and 'selectDuty' will be defined so that a team member can select a duty and save it.

''Views'' -

'''assignments/edit/_review_stategy.html.erb''' - This is view file that has the 'Review Strategy' form for a new or modified assignment. This view will have a checkbox that will specify whether the assignment is role-based.

'''assignments/edit/_rubrics.html.erb''' - This view file for the 'Rubrics' tab will specify the reviewing rubric that is applicable to each role.

'''student_teams/view.html.erb''' - This view shows the team members and their email id's. we can review them from here. If the assignment is a duty based one, then duties will be visible along side the existing fields. If the duties are not selected yet, then a set duties drop down will be visible.

=== UI Description ===

'''The new changes will be as follows in the UI - '''

[[File:Duty_team.png]]

[[File:Assignmnet_duties.png]]

== Use Case ==

File:Duty team.png

2017-11-08T01:50:46Z

Amehta8:

CSC/ECE 517 Fall 2017/E1798 Role-based Reviewing

2017-11-08T01:50:09Z

Amehta8:

== Problem Statement ==
In various agile methodologies, such as Scrum, different team members take on different duties, such as architect, designer, tester and implementer. The purpose of this project is to assign different duties to team members of an assignment. While reviewing too, there will be different rubrics for evaluating the contribution of members with different roles.

== Solution Plan ==
=== Task Description ===
1. A table 'duties' will be created. It will contain all the duties assigned in one assignment. 
2. While creating or editing an assignment, there will be a checkbox in the 'Review Strategies' tab, which will specify whether the assignment is a role-based assignment. 
3. If the checkbox is checked, different duties can be added to the assignment through the UI. 
4. When an assignment is a role-based assignment, the student should be able to assign duties to himself through the 'Your Team' page of the team member. 
5. While reviewing, there will be different rubrics associated with different duties, which can be created through the 'Questionnaires' tab on the homepage. 
6. When a particular teammate is being reviewed, the system should present the correct rubric based on the duty of the teammate. 

=== Proposed Database Changes ===
A new table called 'duties' will be created with the following structure - 
'''assignment_number''' (numeric) - the assignment number that will have the duty, this will be the id field of table assignments (foreign key) 
'''duty_name''' (varchar) - duty assigned to that assignment number. 

The existing table 'assignments' will be modified to include the following fields - 
'''duty_flag''' (boolean) - If the assignment is role-based, this field will be '''true'''. Otherwise, it should be '''false'''. 
'''multiple_duty''' (boolean) - If multiple team members can have the same duty in one assignment, this field will be '''true'''. Otherwise, it should be '''false'''. 

The existing table 'teams_users' will be modified to include the following fields - 
'''duty_id''' (varchar) - If the duty_flag is checked, this field will give the duty assigned to a team member for the assignment.

=== Proposed File Changes ===
''Controllers'' -

'''assignments_controller.rb''' - This is the controller that handles the actions performed by view in _review_stategy.html.erb.
New function 'saveDuty' to be created - This will save the duties assigned to an assignment.

Existing function 'edit' to be modified - This function will save whether the assignment is role-based and whether multiple team members can have the same duties.

'''student_teams_controller.rb''' - The controller function for 'view' will be modified to show the duty and also select a duty for a team member so that review rubrics can be done based on that role.
New functions 'assignDuty' and 'selectDuty' will be defined so that a team member can select a duty and save it.

''Views'' -

'''assignments/edit/_review_stategy.html.erb''' - This is view file that has the 'Review Strategy' form for a new or modified assignment. This view will have a checkbox that will specify whether the assignment is role-based.

'''assignments/edit/_rubrics.html.erb''' - This view file for the 'Rubrics' tab will specify the reviewing rubric that is applicable to each role.

'''student_teams/view.html.erb''' - This view shows the team members and their email id's. we can review them from here. If the assignment is a duty based one, then duties will be visible along side the existing fields. If the duties are not selected yet, then a set duties drop down will be visible.

=== UI Description ===

'''The new changes will be as follows in the UI - '''

[[File:Duty_team.png]]

[[File:Assignmnet_duties]]

== Use Case ==

File:Select.png

2017-11-08T01:46:53Z

Amehta8:

CSC/ECE 517 Fall 2017/E1798 Role-based Reviewing

2017-11-08T01:06:08Z

Amehta8:

CSC/ECE 517 Fall 2017/E1798 Role-based Reviewing

2017-11-08T00:46:32Z

Amehta8:

== Problem Statement ==
In various agile methodologies, such as Scrum, different team members take on different duties, such as architect, designer, tester and implementer. The purpose of this project is to assign different duties to team members of an assignment. While reviewing too, there will be different rubrics for evaluating the contribution of members with different roles.

== Solution Plan ==
=== Task Description ===
1. A table 'duties' will be created. It will contain all the duties assigned in one assignment. 
2. While creating or editing an assignment, there will be a checkbox in the 'Review Strategies' tab, which will specify whether the assignment is a role-based assignment. 
3. If the checkbox is checked, different duties can be added to the assignment through the UI. 
4. When an assignment is a role-based assignment, the student should be able to assign duties to himself through the 'Your Team' page of the team member. 
5. While reviewing, there will be different rubrics associated with different duties, which can be created through the 'Questionnaires' tab on the homepage. 
6. When a particular teammate is being reviewed, the system should present the correct rubric based on the duty of the teammate. 

=== Proposed Database Changes ===
A new table called 'duties' will be created with the following structure - 
'''assignment_number''' (numeric) - the assignment number that will have the duty, this will be the id field of table assignments (foreign key) 
'''duty_name''' (varchar) - duty assigned to that assignment number. 

The existing table 'assignments' will be modified to include the following fields - 
'''duty_flag''' (boolean) - If the assignment is role-based, this field will be '''true'''. Otherwise, it should be '''false'''. 
'''multiple_duty''' (boolean) - If multiple team members can have the same duty in one assignment, this field will be '''true'''. Otherwise, it should be '''false'''. 

The existing table 'teams_users' will be modified to include the following fields - 
'''duty_id''' (varchar) - If the duty_flag is checked, this field will give the duty assigned to a team member for the assignment.

=== Proposed File Changes ===
'''1. assignments/edit/_review_stategy.html.erb''' - This is view file that has the 'Review Strategy' form for a new or modified assignment. This view will have a checkbox that will specify whether the assignment is role-based.

'''2. assignments_controller.rb''' - This is the controller that handles the actions performed by view in _review_stategy.html.erb.

New function 'saveDuty' to be created - This will save the duties assigned to an assignment.

Existing function 'edit' to be modified - This function will save whether the assignment is role-based and whether multiple team members can have the same duties.

'''3. assignments/edit/_rubrics.html.erb''' - This view file for the 'Rubrics' tab will specify the reviewing rubric that is applicable to each role.

'''4.student_teams/view.html.erb''' - This view shows the team members and their email id's. we can review them from here. If the assignment is a duty based one, then duties will be visible along side the existing fields. If the duties are not selected yet, then a set duties drop down will be visible.

'''5.student_teams_controller.rb''' - The controller function for 'view' will be modified to show the duty and also select a duty for a team member so that review rubrics can be done based on that role.

=== UI Description ===

== Use Case ==

CSC/ECE 517 Fall 2017

2017-10-27T06:53:03Z

Amehta8:

'''Writing Assignment 2'''
*[[CSC/ECE 517 Fall 2017/E1779. Fix teammate advertisements and requests to join a team]]
*[[CSC/ECE_517_Fall_2017/E1773 Investigate and Fix Expertiza Production Version Runtime Exceptions.rb]]
*[[CSC/ECE_517_Fall_2017/E1774 Metareview fixes and improvements.rb]]
*[[CSC/ECE_517_Fall_2017/E1788 OSS project Maroon Heatmap fixes]]
*[[CSC/ECE 517 Fall 2017/E1781 Topic Management]]
*[[CSC/ECE_517_Fall_2017/E1745_Refactor_response_controller.rb]]
*[[CSC/ECE_517_Fall_2017/E1752 Refactor assignments controller]]
*[[CSC/ECE_517_Fall_2017/E1776_Enhance_Imports]]
*[[CSC/ECE_517_Fall_2017/E1756 TLD Refactor response.rb]]
*[[CSC/ECE_517_Fall_2017/E1772_Refactor reputation_web_service_controller.rb]]
*[[CSC/ECE_517_Fall_2017/M1754_Mutation Testing on Servo]]
*[[CSC/ECE_517_Fall_2017/E1753 OSS project bidding tests]]
*[[CSC/ECE_517_Fall_2017/E1766_Test team functionality]]
*[[CSC/ECE_517_Fall_2017/E1787_OSS project Bronze Score calculations]]
*[[CSC/ECE_517_Fall_2017/E1763 Fix Staggered-Deadline Assignments]]
*[[CSC/ECE 517 Fall 2017/E1757 Introduce a Student View for instructors]]

CSC/ECE 517 Fall 2017/E1757 Introduce a Student View for instructors

2017-10-27T06:48:32Z

Amehta8:

This wiki page documents the changes made as a part of E1757 which allows users with instructor role to view Expertiza as a student.

== Introduction ==
=== Background ===
In Expertiza, instructors can act as students, but they do so by using different pull-down menus. This is potentially confusing, especially for Assignments, which appear both in the admin and student menus.

An '''instructor''' sees the following menus across the top (if his/her window is wide enough; otherwise, the menus show up when the menu icon is clicked on):

''Home Manage Survey Deployments Assignments Course Evaluation Profile Contact Us''

A '''student''' sees these menus:

''Home Assignments Course Evaluations Profile Contact Us''

On the instructor’s Manage menu, one of the options is “Assignments”. Having Assignments appear in two places in the menu is potentially confusing. Manage > Assignments allows the instructor to edit and create assignments. The Assignments menu that both students and instructors see allows them to participate in assignments.

Hence, to avoid confusion, a new view is introduced.

=== Problem statement ===
To create a ''Student View'' that would make the instructor view the system the way (s)he would view it if they were a student. Once the instructor is in student view, the menu items are same as a student would view, so to come back as the instructor, a button should be visible to the instructor that would exit the ''Student View'' and take the instructor back to his/her home page.

=== Team ===
# Amit Kanwar
# Apoorva Mehta
# Gaurav Joshi

'''Mentor''' - Ed Gehringer

== Development ==
=== student_view_controller.rb ===
A new controller is created ''app/controllers/student_view_controller.rb'' to handle the new student view functionality, which ''sets'' and instructor to student view and ''reverts'' the view back to instructor.

<pre>
@@ -0,0 +1,21 @@
class StudentViewController < ApplicationController
def action_allowed?
case params[:action]
when 'set'
true
when 'revert'
true
end
end

def set
session[:student_view] = true
redirect_back
end

def revert
session.delete(:student_view)
redirect_back
end

end
</pre>

=== role_instructor.yml ===

A new view is created for the instructor in ''config/role_instructor.yml'' which will show the view under the Manage menu item. The view id is 25.

<pre>
51: &25 !ruby/object:Menu::Node
content_page_id:
controller_action_id: 15
id: 51
label: Student View
name: student_view
parent:
parent_id: 37
site_controller_id: 35
url: "/student_view/set"

</pre>

=== _navigation.html.erb ===

A new session variable (:student_view) will be used to check if an instructor is in student view or not and will be used to exit the Student view, code changes in ''app/views/shared/_navigation.html.erb''

<pre>
<% if session.key?(:student_view) %>
<%= form_for :student_view, url: '/student_view/revert', html: {id: 'instructor-form'} do |f| %>
<button type="button" class="btn btn-primary" id="instructor-button">Revert to Instructor View</button>
<% end %>
<% end %>
</pre>

<pre>
jQuery("#instructor-button").click(function(event) {
jQuery("#instructor-form").submit()
});
</pre>

=== _suckerfish.html.erb ===

The different menu items are shown for particular roles, we check the new session variable to show or hide the various menu items accordingly for the instructor in ''app/views/menu_items/_suckerfish.html.erb''

<pre>
student_view = session.key?(:student_view) ? ([1, 26, 27, 2, 14].include? item_id) ? true : false : false
instructor_view = !session.key?(:student_view) ? ([1, 37, 35, 30, 27, 2, 13, 38, 44, 45, 33, 50, 51, 36, 14].include? item_id) ? true: false : false
if !student_view and !instructor_view then
conditional = false
if session[:user].role.name == "Instructor" then
if !student_view and !instructor_view then
conditional = false
else
conditional = true
end
</pre>

=== routes.rb ===

The new controller methods are added in ''config/routes.rb''

<pre>
post '/student_view/set', to: 'student_view#set'
post '/student_view/revert', to: 'student_view#revert'
</pre>

== Testing ==

The user needs to log-in as instructor to view the developed functionality, this won't be visible for other user roles-

1. Go to Manage > Student View

2. Instructor views Expertiza as a student.

3. A revert button appears at the top right corner, to exit the Student view.

4. Clicking the button takes you back to the instructor view.

== External Links ==
# link for forked repository [[https://github.com/Aminoid/expertiza/commits/master]]

CSC/ECE 517 Fall 2017/E1757 Introduce a Student View for instructors

2017-10-27T06:46:00Z

Amehta8:

This wiki page is for the description of changes made under E1757 OSS assignment for Fall 2017, CSC/ECE 517. This changes made allow users with instructor role to view Expertiza as a student.

== Introduction ==
=== Background ===
In Expertiza, instructors can act as students, but they do so by using different pull-down menus. This is potentially confusing, especially for Assignments, which appear both in the admin and student menus.

An '''instructor''' sees the following menus across the top (if his/her window is wide enough; otherwise, the menus show up when the menu icon is clicked on):

''Home Manage Survey Deployments Assignments Course Evaluation Profile Contact Us''

A '''student''' sees these menus:

''Home Assignments Course Evaluations Profile Contact Us''

On the instructor’s Manage menu, one of the options is “Assignments”. Having Assignments appear in two places in the menu is potentially confusing. Manage > Assignments allows the instructor to edit and create assignments. The Assignments menu that both students and instructors see allows them to participate in assignments.

Hence, to avoid confusion, a new view is introduced.

=== Problem statement ===
To create a ''Student View'' that would make the instructor view the system the way (s)he would view it if they were a student. Once the instructor is in student view, the menu items are same as a student would view, so to come back as the instructor, a button should be visible to the instructor that would exit the ''Student View'' and take the instructor back to his/her home page.

=== Team ===
# Amit Kanwar
# Apoorva Mehta
# Gaurav Joshi

'''Mentor''' - Ed Gehringer

== Development ==
=== student_view_controller.rb ===
A new controller is created ''app/controllers/student_view_controller.rb'' to handle the new student view functionality, which ''sets'' and instructor to student view and ''reverts'' the view back to instructor.

<pre>
@@ -0,0 +1,21 @@
class StudentViewController < ApplicationController
def action_allowed?
case params[:action]
when 'set'
true
when 'revert'
true
end
end

def set
session[:student_view] = true
redirect_back
end

def revert
session.delete(:student_view)
redirect_back
end

end
</pre>

=== role_instructor.yml ===

A new view is created for the instructor in ''config/role_instructor.yml'' which will show the view under the Manage menu item. The view id is 25.

<pre>
51: &25 !ruby/object:Menu::Node
content_page_id:
controller_action_id: 15
id: 51
label: Student View
name: student_view
parent:
parent_id: 37
site_controller_id: 35
url: "/student_view/set"

</pre>

=== _navigation.html.erb ===

A new session variable (:student_view) will be used to check if an instructor is in student view or not and will be used to exit the Student view, code changes in ''app/views/shared/_navigation.html.erb''

<pre>
<% if session.key?(:student_view) %>
<%= form_for :student_view, url: '/student_view/revert', html: {id: 'instructor-form'} do |f| %>
<button type="button" class="btn btn-primary" id="instructor-button">Revert to Instructor View</button>
<% end %>
<% end %>
</pre>

<pre>
jQuery("#instructor-button").click(function(event) {
jQuery("#instructor-form").submit()
});
</pre>

=== _suckerfish.html.erb ===

The different menu items are shown for particular roles, we check the new session variable to show or hide the various menu items accordingly for the instructor in ''app/views/menu_items/_suckerfish.html.erb''

<pre>
student_view = session.key?(:student_view) ? ([1, 26, 27, 2, 14].include? item_id) ? true : false : false
instructor_view = !session.key?(:student_view) ? ([1, 37, 35, 30, 27, 2, 13, 38, 44, 45, 33, 50, 51, 36, 14].include? item_id) ? true: false : false
if !student_view and !instructor_view then
conditional = false
if session[:user].role.name == "Instructor" then
if !student_view and !instructor_view then
conditional = false
else
conditional = true
end
</pre>

=== routes.rb ===

The new controller methods are added in ''config/routes.rb''

<pre>
post '/student_view/set', to: 'student_view#set'
post '/student_view/revert', to: 'student_view#revert'
</pre>

== Testing ==

The user needs to log-in as instructor to view the developed functionality, this won't be visible for other user roles-

1. Go to Manage > Student View

2. Instructor views Expertiza as a student.

3. A revert button appears at the top right corner, to exit the Student view.

4. Clicking the button takes you back to the instructor view.

== External Links ==
# link for forked repository [[https://github.com/Aminoid/expertiza/commits/master]]

CSC/ECE 517 Fall 2017/E1757 Introduce a Student View for instructors

2017-10-27T06:41:38Z

Amehta8:

== Introduction ==
=== Background ===
In Expertiza, instructors can act as students, but they do so by using different pull-down menus. This is potentially confusing, especially for Assignments, which appear both in the admin and student menus.

An '''instructor''' sees the following menus across the top (if his/her window is wide enough; otherwise, the menus show up when the menu icon is clicked on):

''Home Manage Survey Deployments Assignments Course Evaluation Profile Contact Us''

A '''student''' sees these menus:

''Home Assignments Course Evaluations Profile Contact Us''

On the instructor’s Manage menu, one of the options is “Assignments”. Having Assignments appear in two places in the menu is potentially confusing. Manage > Assignments allows the instructor to edit and create assignments. The Assignments menu that both students and instructors see allows them to participate in assignments.

Hence, to avoid confusion, a new view is introduced.

=== Problem statement ===
To create a ''Student View'' that would make the instructor view the system the way (s)he would view it if they were a student. Once the instructor is in student view, the menu items are same as a student would view, so to come back as the instructor, a button should be visible to the instructor that would exit the ''Student View'' and take the instructor back to his/her home page.

=== Team ===
# Amit Kanwar
# Apoorva Mehta
# Gaurav Joshi

'''Mentor''' - Ed Gehringer

== Development ==
=== student_view_controller.rb ===
A new controller is created ''app/controllers/student_view_controller.rb'' to handle the new student view functionality, which ''sets'' and instructor to student view and ''reverts'' the view back to instructor.

<pre>
@@ -0,0 +1,21 @@
class StudentViewController < ApplicationController
def action_allowed?
case params[:action]
when 'set'
true
when 'revert'
true
end
end

def set
session[:student_view] = true
redirect_back
end

def revert
session.delete(:student_view)
redirect_back
end

end
</pre>

=== role_instructor.yml ===

A new view is created for the instructor in ''config/role_instructor.yml'' which will show the view under the Manage menu item. The view id is 25.

<pre>
51: &25 !ruby/object:Menu::Node
content_page_id:
controller_action_id: 15
id: 51
label: Student View
name: student_view
parent:
parent_id: 37
site_controller_id: 35
url: "/student_view/set"

</pre>

=== _navigation.html.erb ===

A new session variable (:student_view) will be used to check if an instructor is in student view or not and will be used to exit the Student view, code changes in ''app/views/shared/_navigation.html.erb''

<pre>
<% if session.key?(:student_view) %>
<%= form_for :student_view, url: '/student_view/revert', html: {id: 'instructor-form'} do |f| %>
<button type="button" class="btn btn-primary" id="instructor-button">Revert to Instructor View</button>
<% end %>
<% end %>
</pre>

<pre>
jQuery("#instructor-button").click(function(event) {
jQuery("#instructor-form").submit()
});
</pre>

=== _suckerfish.html.erb ===

The different menu items are shown for particular roles, we check the new session variable to show or hide the various menu items accordingly for the instructor in ''app/views/menu_items/_suckerfish.html.erb''

<pre>
student_view = session.key?(:student_view) ? ([1, 26, 27, 2, 14].include? item_id) ? true : false : false
instructor_view = !session.key?(:student_view) ? ([1, 37, 35, 30, 27, 2, 13, 38, 44, 45, 33, 50, 51, 36, 14].include? item_id) ? true: false : false
if !student_view and !instructor_view then
conditional = false
if session[:user].role.name == "Instructor" then
if !student_view and !instructor_view then
conditional = false
else
conditional = true
end
</pre>

=== routes.rb ===

The new controller methods are added in ''config/routes.rb''

<pre>
post '/student_view/set', to: 'student_view#set'
post '/student_view/revert', to: 'student_view#revert'
</pre>

== Testing ==

The user needs to log-in as instructor to view the developed functionality, this won't be visible for other user roles-

1. Go to Manage > Student View

2. Instructor views Expertiza as a student.

3. A revert button appears at the top right corner, to exit the Student view.

4. Clicking the button takes you back to the instructor view.

== External Links ==
# link for forked repository [[https://github.com/Aminoid/expertiza/commits/master]]

CSC/ECE 517 Fall 2017/E1757 Introduce a Student View for instructors

2017-10-27T06:38:09Z

Amehta8:

== Introduction ==
=== Background ===
In Expertiza, instructors can act as students, but they do so by using different pull-down menus. This is potentially confusing, especially for Assignments, which appear both in the admin and student menus.

An '''instructor''' sees the following menus across the top (if his/her window is wide enough; otherwise, the menus show up when the menu icon is clicked on):

''Home Manage Survey Deployments Assignments Course Evaluation Profile Contact Us''

A '''student''' sees these menus:

''Home Assignments Course Evaluations Profile Contact Us''

On the instructor’s Manage menu, one of the options is “Assignments”. Having Assignments appear in two places in the menu is potentially confusing. Manage > Assignments allows the instructor to edit and create assignments. The Assignments menu that both students and instructors see allows them to participate in assignments.

Hence, to avoid confusion, a new view is introduced.

=== Problem statement ===
To create a ''Student View'' that would make the instructor view the system the way (s)he would view it if they were a student. Once the instructor is in student view, the menu items are same as a student would view, so to come back as the instructor, a button should be visible to the instructor that would exit the ''Student View'' and take the instructor back to his/her home page.

=== Team ===
# Amit Kanwar
# Apoorva Mehta
# Gaurav Joshi

'''Mentor''' - Ed Gehringer

----

== Development ==
=== student_view_controller.rb ===
A new controller is created ''app/controllers/student_view_controller.rb'' to handle the new student view functionality, which ''sets'' and instructor to student view and ''reverts'' the view back to instructor.

<pre>
@@ -0,0 +1,21 @@
class StudentViewController < ApplicationController
def action_allowed?
case params[:action]
when 'set'
true
when 'revert'
true
end
end

def set
session[:student_view] = true
redirect_back
end

def revert
session.delete(:student_view)
redirect_back
end

end
</pre>

=== role_instructor.yml ===

A new view is created for the instructor in ''config/role_instructor.yml'' which will show the view under the Manage menu item. The view id is 25.

<pre>
51: &25 !ruby/object:Menu::Node
content_page_id:
controller_action_id: 15
id: 51
label: Student View
name: student_view
parent:
parent_id: 37
site_controller_id: 35
url: "/student_view/set"

</pre>

=== _navigation.html.erb ===

A new session variable (:student_view) will be used to check if an instructor is in student view or not and will be used to exit the Student view, code changes in ''app/views/shared/_navigation.html.erb''

<pre>
<% if session.key?(:student_view) %>
<%= form_for :student_view, url: '/student_view/revert', html: {id: 'instructor-form'} do |f| %>
<button type="button" class="btn btn-primary" id="instructor-button">Revert to Instructor View</button>
<% end %>
<% end %>
</pre>

<pre>
jQuery("#instructor-button").click(function(event) {
jQuery("#instructor-form").submit()
});
</pre>

=== _suckerfish.html.erb ===

The different menu items are shown for particular roles, we check the new session variable to show or hide the various menu items accordingly for the instructor in ''app/views/menu_items/_suckerfish.html.erb''

<pre>
student_view = session.key?(:student_view) ? ([1, 26, 27, 2, 14].include? item_id) ? true : false : false
instructor_view = !session.key?(:student_view) ? ([1, 37, 35, 30, 27, 2, 13, 38, 44, 45, 33, 50, 51, 36, 14].include? item_id) ? true: false : false
if !student_view and !instructor_view then
conditional = false
if session[:user].role.name == "Instructor" then
if !student_view and !instructor_view then
conditional = false
else
conditional = true
end
</pre>

=== routes.rb ===

The new controller methods are added in ''config/routes.rb''

<pre>
post '/student_view/set', to: 'student_view#set'
post '/student_view/revert', to: 'student_view#revert'
</pre>

== Testing ==

The user needs to log-in as instructor to view the developed functionality, this won't be visible for other user roles-

1. Go to Manage > Student View

2. Instructor views Expertiza as a student.

3. A revert button appears at the top right corner, to exit the Student view.

4. Clicking the button takes you back to the instructor view.

== External Links ==
# link for forked repository [[https://github.com/Aminoid/expertiza/commits/master]]

CSC/ECE 517 Fall 2017/E1757 Introduce a Student View for instructors

2017-10-27T06:37:35Z

Amehta8: This wiki page is for the description of changes made under E1757 OSS assignment for Fall 2017, CSC/ECE 517. The changes made allow instructors to view Expertiza as a student.

== Introduction ==
=== Background ===
In Expertiza, instructors can act as students, but they do so by using different pull-down menus. This is potentially confusing, especially for Assignments, which appear both in the admin and student menus.

An '''instructor''' sees the following menus across the top (if his/her window is wide enough; otherwise, the menus show up when the menu icon is clicked on):

''Home Manage Survey Deployments Assignments Course Evaluation Profile Contact Us''

A '''student''' sees these menus:

''Home Assignments Course Evaluations Profile Contact Us''

On the instructor’s Manage menu, one of the options is “Assignments”. Having Assignments appear in two places in the menu is potentially confusing. Manage > Assignments allows the instructor to edit and create assignments. The Assignments menu that both students and instructors see allows them to participate in assignments.

Hence, to avoid confusion, a new view is introduced.

=== Problem statement ===
To create a ''Student View'' that would make the instructor view the system the way (s)he would view it if they were a student. Once the instructor is in student view, the menu items are same as a student would view, so to come back as the instructor, a button should be visible to the instructor that would exit the ''Student View'' and take the instructor back to his/her home page.

=== Team ===
# Amit Kanwar

# Apoorva Mehta

# Gaurav Joshi

'''Mentor''' - Ed Gehringer

----

== Development ==
=== student_view_controller.rb ===
A new controller is created ''app/controllers/student_view_controller.rb'' to handle the new student view functionality, which ''sets'' and instructor to student view and ''reverts'' the view back to instructor.

<pre>
@@ -0,0 +1,21 @@
class StudentViewController < ApplicationController
def action_allowed?
case params[:action]
when 'set'
true
when 'revert'
true
end
end

def set
session[:student_view] = true
redirect_back
end

def revert
session.delete(:student_view)
redirect_back
end

end
</pre>

=== role_instructor.yml ===

A new view is created for the instructor in ''config/role_instructor.yml'' which will show the view under the Manage menu item. The view id is 25.

<pre>
51: &25 !ruby/object:Menu::Node
content_page_id:
controller_action_id: 15
id: 51
label: Student View
name: student_view
parent:
parent_id: 37
site_controller_id: 35
url: "/student_view/set"

</pre>

=== _navigation.html.erb ===

A new session variable (:student_view) will be used to check if an instructor is in student view or not and will be used to exit the Student view, code changes in ''app/views/shared/_navigation.html.erb''

<pre>
<% if session.key?(:student_view) %>
<%= form_for :student_view, url: '/student_view/revert', html: {id: 'instructor-form'} do |f| %>
<button type="button" class="btn btn-primary" id="instructor-button">Revert to Instructor View</button>
<% end %>
<% end %>
</pre>

<pre>
jQuery("#instructor-button").click(function(event) {
jQuery("#instructor-form").submit()
});
</pre>

=== _suckerfish.html.erb ===

The different menu items are shown for particular roles, we check the new session variable to show or hide the various menu items accordingly for the instructor in ''app/views/menu_items/_suckerfish.html.erb''

<pre>
student_view = session.key?(:student_view) ? ([1, 26, 27, 2, 14].include? item_id) ? true : false : false
instructor_view = !session.key?(:student_view) ? ([1, 37, 35, 30, 27, 2, 13, 38, 44, 45, 33, 50, 51, 36, 14].include? item_id) ? true: false : false
if !student_view and !instructor_view then
conditional = false
if session[:user].role.name == "Instructor" then
if !student_view and !instructor_view then
conditional = false
else
conditional = true
end
</pre>

=== routes.rb ===

The new controller methods are added in ''config/routes.rb''

<pre>
post '/student_view/set', to: 'student_view#set'
post '/student_view/revert', to: 'student_view#revert'
</pre>

== Testing ==

The user needs to log-in as instructor to view the developed functionality, this won't be visible for other user roles-

1. Go to Manage > Student View

2. Instructor views Expertiza as a student.

3. A revert button appears at the top right corner, to exit the Student view.

4. Clicking the button takes you back to the instructor view.

== External Links ==
# link for forked repository [[https://github.com/Aminoid/expertiza/commits/master]]