Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-26T01:15:51Z

Sniu:

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features that will be added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This view file displays various statistics related to review scores obtained by the student in different assignments.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/models/student_task.rb app/models/student_task.rb]'''

The file contains all the methods related to students and the assignments objects.

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page "http://expertiza.ncsu.edu/student_task/list" (Need log in to see). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the '''app/views/grades/_teammate_reviews.html.erb''' file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value 'k', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is not less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Readme==
===Instructions to run Expertiza===
'''To see the new functionality for student:'''
Login to the Expertiza application using any student account like ‘user5403’, then select assignment.
*The student should be able to see all the teammates he has teamed with in specific courses on the left panel.
*To see the teammate review, select “your score” in one assignment, there is one column named “teammate review” showing the teammate review you got from your teammates for this assignment.

'''To see the new functionality for instructor:'''
Login to Expertiza as an instructor using username “user6”.
*To see the fixed dashboard, click on the "360 assessment dashboard" action of some particular course.
*To see the review and metareview scores for each student in one course, click on the "View aggregated team mate and metareviews" action of that particular course.

==Functionality achieved after Modification==

===Adding the teammates details to the Student page===

The number of students that have teamed up with the current user would be seen in the "Assignments" page as shown in the figure below.

[[File:Assignments_page.jpg]]

The new section (circled) in the left pane of the above page indicates the number of teams people the current user has teamed up with in each course and their names. In this case, the current user has 1 teammate in the CSC/ECE 506 class, namely "5409, Student".

===Fixing the Assessment 360 dashboard in the Instructor's page===

The instructor can look at the overview of the course by clicking on the "360 assessment dashboard" action of the particular course. The following image shows the Dashboard page.

[[File:Assessment360_dashboard.jpg]]

This page summarizes the details such as the Grade distribution and Review progress for each of the assignments.

===Fixing the Aggregated Metareviews Page for the Instructor's===

Similarly, the instructor can look at the review and metareview scores for each student by clicking on the "View aggregated team mate and metareviews" action of the particular course. The following image shows the resulting page.

[[File:metareviews1.jpg]]

Along with the aggregate scores for each student, this page also shows the class averages for each assignment as shown in the image below.

[[File:metareviews2.jpg]]

==Potential performance issues==
Testing will be carried out to verify the desired functionality.
Since a view of aggregation of teammates and reviews are added and the information of teammates are shown on two pages: the course page and the assignment page. There may exist duplication of method calls, which will increase the overall loading time.

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-26T01:15:19Z

Sniu: /* Instructions to run Expertiza */

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-26T01:15:03Z

Sniu: /* Instructions to run Expertiza */

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features that will be added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This view file displays various statistics related to review scores obtained by the student in different assignments.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/models/student_task.rb app/models/student_task.rb]'''

The file contains all the methods related to students and the assignments objects.

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page "http://expertiza.ncsu.edu/student_task/list" (Need log in to see). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the '''app/views/grades/_teammate_reviews.html.erb''' file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value 'k', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is not less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Readme==
===Instructions to run Expertiza===
'''To see the new functionality for student:'''
Login to the Expertiza application using any student account like ‘user5403’, then select assignment.
**The student should be able to see all the teammates he has teamed with in specific courses on the left panel.
**To see the teammate review, select “your score” in one assignment, there is one column named “teammate review” showing the teammate review you got from your teammates for this assignment.

'''To see the new functionality for instructor:'''
Login to Expertiza as an instructor using username “user6”.
*To see the fixed dashboard, click on the "360 assessment dashboard" action of some particular course.
*To see the review and metareview scores for each student in one course, click on the "View aggregated team mate and metareviews" action of that particular course.

==Functionality achieved after Modification==

===Adding the teammates details to the Student page===

The number of students that have teamed up with the current user would be seen in the "Assignments" page as shown in the figure below.

[[File:Assignments_page.jpg]]

The new section (circled) in the left pane of the above page indicates the number of teams people the current user has teamed up with in each course and their names. In this case, the current user has 1 teammate in the CSC/ECE 506 class, namely "5409, Student".

===Fixing the Assessment 360 dashboard in the Instructor's page===

The instructor can look at the overview of the course by clicking on the "360 assessment dashboard" action of the particular course. The following image shows the Dashboard page.

[[File:Assessment360_dashboard.jpg]]

This page summarizes the details such as the Grade distribution and Review progress for each of the assignments.

===Fixing the Aggregated Metareviews Page for the Instructor's===

Similarly, the instructor can look at the review and metareview scores for each student by clicking on the "View aggregated team mate and metareviews" action of the particular course. The following image shows the resulting page.

[[File:metareviews1.jpg]]

Along with the aggregate scores for each student, this page also shows the class averages for each assignment as shown in the image below.

[[File:metareviews2.jpg]]

==Potential performance issues==
Testing will be carried out to verify the desired functionality.
Since a view of aggregation of teammates and reviews are added and the information of teammates are shown on two pages: the course page and the assignment page. There may exist duplication of method calls, which will increase the overall loading time.

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-26T00:35:48Z

Sniu:

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features that will be added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This view file displays various statistics related to review scores obtained by the student in different assignments.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/models/student_task.rb app/models/student_task.rb]'''

The file contains all the methods related to students and the assignments objects.

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page "http://expertiza.ncsu.edu/student_task/list" (Need log in to see). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the '''app/views/grades/_teammate_reviews.html.erb''' file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value 'k', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is not less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Readme==
===Instructions to run Expertiza===
*To see the new functionality for student:
Login to the Expertiza application using any student account like ‘user5403’,
then select assignment, the student should be able to see all the teammates he has teamed with in specific courses on the left panel. To see the teammate review, select “your score” in one assignment, there is one column named “teammate review” showing the teammate review you got from your teammates for this assignment.

*To see the new functionality for instructor:
Login to Expertiza as an instructor using username “user6”,

==Functionality achieved after Modification==

===Adding the teammates details to the Student page===

The number of students that have teamed up with the current user would be seen in the "Assignments" page as shown in the figure below.

[[File:Assignments_page.jpg]]

The new section (circled) in the left pane of the above page indicates the number of teams people the current user has teamed up with in each course and their names. In this case, the current user has 1 teammate in the CSC/ECE 506 class, namely "5409, Student".

===Fixing the Assessment 360 dashboard in the Instructor's page===

The instructor can look at the overview of the course by clicking on the "360 assessment dashboard" action of the particular course. The following image shows the Dashboard page.

[[File:Assessment360_dashboard.jpg]]

This page summarizes the details such as the Grade distribution and Review progress for each of the assignments.

===Fixing the Aggregated Metareviews Page for the Instructor's===

Similarly, the instructor can look at the review and metareview scores for each student by clicking on the "View aggregated team mate and metareviews" action of the particular course. The following image shows the resulting page.

[[File:metareviews1.jpg]]

Along with the aggregate scores for each student, this page also shows the class averages for each assignment as shown in the image below.

[[File:metareviews2.jpg]]

==Potential performance issues==
Testing will be carried out to verify the desired functionality.
Since a view of aggregation of teammates and reviews are added and the information of teammates are shown on two pages: the course page and the assignment page. There may exist duplication of method calls, which will increase the overall loading time.

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-24T01:18:10Z

Sniu:

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features that will be added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This view file displays various statistics related to review scores obtained by the student in different assignments.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/models/student_task.rb app/models/student_task.rb]'''

The file contains all the methods related to students and the assignments objects.

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page "http://expertiza.ncsu.edu/student_task/list" (Need log in to see). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the '''app/views/grades/_teammate_reviews.html.erb''' file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value 'k', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is not less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Functionality achieved after Modification==
===README===
'''To view the change, log in as an existing instructor or student.'''

==Potential performance issues==
Testing will be carried out to verify the desired functionality.
Since a view of aggregation of teammates and reviews are added and the information of teammates are shown on two pages: the course page and the assignment page. There may exist duplication of method calls, which will increase the overall loading time.

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-24T01:17:45Z

Sniu:

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features that will be added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This view file displays various statistics related to review scores obtained by the student in different assignments.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/models/student_task.rb app/models/student_task.rb]'''

The file contains all the methods related to students and the assignments objects.

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page "http://expertiza.ncsu.edu/student_task/list" (Need log in to see). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the '''app/views/grades/_teammate_reviews.html.erb''' file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value 'k', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is not less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Functionality achieved after Modification==
===README===
'''To view, log in as an existing instructor or student.'''

==Potential performance issues==
Testing will be carried out to verify the desired functionality.
Since a view of aggregation of teammates and reviews are added and the information of teammates are shown on two pages: the course page and the assignment page. There may exist duplication of method calls, which will increase the overall loading time.

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-24T01:17:00Z

Sniu: /* Functionality achieved after Modification */

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features that will be added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This view file displays various statistics related to review scores obtained by the student in different assignments.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/models/student_task.rb app/models/student_task.rb]'''

The file contains all the methods related to students and the assignments objects.

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page "http://expertiza.ncsu.edu/student_task/list" (Need log in to see). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the '''app/views/grades/_teammate_reviews.html.erb''' file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value 'k', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is not less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Functionality achieved after Modification==

==Potential performance issues==
Testing will be carried out to verify the desired functionality.
Since a view of aggregation of teammates and reviews are added and the information of teammates are shown on two pages: the course page and the assignment page. There may exist duplication of method calls, which will increase the overall loading time.

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-24T01:14:50Z

Sniu: /* New functionality after Modification */

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features that will be added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This view file displays various statistics related to review scores obtained by the student in different assignments.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/models/student_task.rb app/models/student_task.rb]'''

The file contains all the methods related to students and the assignments objects.

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page "http://expertiza.ncsu.edu/student_task/list" (Need log in to see). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the '''app/views/grades/_teammate_reviews.html.erb''' file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value 'k', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is not less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Functionality achieved after Modification==
'''To view, log in as an existing instructor or student.'''

==Potential performance issues==
Testing will be carried out to verify the desired functionality.
Since a view of aggregation of teammates and reviews are added and the information of teammates are shown on two pages: the course page and the assignment page. There may exist duplication of method calls, which will increase the overall loading time.

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-24T01:14:22Z

Sniu: /* New functionality after Modification */

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features that will be added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This view file displays various statistics related to review scores obtained by the student in different assignments.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/models/student_task.rb app/models/student_task.rb]'''

The file contains all the methods related to students and the assignments objects.

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page "http://expertiza.ncsu.edu/student_task/list" (Need log in to see). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the '''app/views/grades/_teammate_reviews.html.erb''' file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value 'k', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is not less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==New functionality after Modification==
'''To view, log in as an existing instructor or student.'''

==Potential performance issues==
Testing will be carried out to verify the desired functionality.
Since a view of aggregation of teammates and reviews are added and the information of teammates are shown on two pages: the course page and the assignment page. There may exist duplication of method calls, which will increase the overall loading time.

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-24T01:13:46Z

Sniu:

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features that will be added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This view file displays various statistics related to review scores obtained by the student in different assignments.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/models/student_task.rb app/models/student_task.rb]'''

The file contains all the methods related to students and the assignments objects.

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page "http://expertiza.ncsu.edu/student_task/list" (Need log in to see). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the '''app/views/grades/_teammate_reviews.html.erb''' file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value 'k', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is not less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==New functionality after Modification==
***To view, log in as an existing instructor or student.***

==Potential performance issues==
Testing will be carried out to verify the desired functionality.
Since a view of aggregation of teammates and reviews are added and the information of teammates are shown on two pages: the course page and the assignment page. There may exist duplication of method calls, which will increase the overall loading time.

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-24T01:02:48Z

Sniu: /* Documentation */

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features that will be added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This view file displays various statistics related to review scores obtained by the student in different assignments.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/models/student_task.rb app/models/student_task.rb]'''

The file contains all the methods related to students and the assignments objects.

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page "http://expertiza.ncsu.edu/student_task/list" (Need log in to see). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the '''app/views/grades/_teammate_reviews.html.erb''' file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value 'k', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is not less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Potential performance issues==
Testing will be carried out to verify the desired functionality.
Since a view of aggregation of teammates and reviews are added and the information of teammates are shown on two pages: the course page and the assignment page. There may exist duplication of method calls, which will increase the overall loading time.

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-01T00:46:31Z

Sniu: /* Potential performance issues */

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features that will be added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This view file displays various statistics related to review scores obtained by the student in different assignments.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assignments_controller.rb app/controllers/assignments_controller.rb]'''

The assignments controller contains the new, create, edit, update, delete and various other useful functions pertaining to the assignment objects.

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page "http://expertiza.ncsu.edu/student_task/list" (Need log in to see). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the '''app/views/grades/_teammate_reviews.html.erb''' file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value 'k', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is not less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Potential performance issues==
Testing will be carried out to verify the desired functionality.
Since a view of aggregation of teammates and reviews are added and the information of teammates are shown on two pages: the course page and the assignment page. There may exist duplication of method calls, which will increase the overall loading time.

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-01T00:45:47Z

Sniu: /* Use Cases */

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features that will be added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This view file displays various statistics related to review scores obtained by the student in different assignments.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assignments_controller.rb app/controllers/assignments_controller.rb]'''

The assignments controller contains the new, create, edit, update, delete and various other useful functions pertaining to the assignment objects.

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page "http://expertiza.ncsu.edu/student_task/list" (Need log in to see). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the '''app/views/grades/_teammate_reviews.html.erb''' file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value 'k', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is not less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Potential performance issues==
Testing will be carried out to verify the desired functionality.
A view of aggregation of teammates and reviews are added.The information of teammates are shown on two pages: the course page and the assignment page. There may exist duplication of method calls, which will increase the overall loading time.

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-01T00:45:23Z

Sniu: /* Use Cases */

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features that will be added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This view file displays various statistics related to review scores obtained by the student in different assignments.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assignments_controller.rb app/controllers/assignments_controller.rb]'''

The assignments controller contains the new, create, edit, update, delete and various other useful functions pertaining to the assignment objects.

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page http://expertiza.ncsu.edu/student_task/list(Need log in to see). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the '''app/views/grades/_teammate_reviews.html.erb''' file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value 'k', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is not less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Potential performance issues==
Testing will be carried out to verify the desired functionality.
A view of aggregation of teammates and reviews are added.The information of teammates are shown on two pages: the course page and the assignment page. There may exist duplication of method calls, which will increase the overall loading time.

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-01T00:44:15Z

Sniu: /* Use Cases */

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features that will be added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This view file displays various statistics related to review scores obtained by the student in different assignments.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assignments_controller.rb app/controllers/assignments_controller.rb]'''

The assignments controller contains the new, create, edit, update, delete and various other useful functions pertaining to the assignment objects.

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page (http://expertiza.ncsu.edu/student_task/list). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the '''app/views/grades/_teammate_reviews.html.erb''' file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value 'k', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is not less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Potential performance issues==
Testing will be carried out to verify the desired functionality.
A view of aggregation of teammates and reviews are added.The information of teammates are shown on two pages: the course page and the assignment page. There may exist duplication of method calls, which will increase the overall loading time.

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-01T00:42:59Z

Sniu: /* Scope */

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features that will be added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This view file displays various statistics related to review scores obtained by the student in different assignments.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assignments_controller.rb app/controllers/assignments_controller.rb]'''

The assignments controller contains the new, create, edit, update, delete and various other useful functions pertaining to the assignment objects.

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page (http://expertiza.ncsu.edu/student_task/list). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the app/views/grades/_teammate_reviews.html.erb file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value 'k', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is not less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Potential performance issues==
Testing will be carried out to verify the desired functionality.
A view of aggregation of teammates and reviews are added.The information of teammates are shown on two pages: the course page and the assignment page. There may exist duplication of method calls, which will increase the overall loading time.

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-01T00:40:46Z

Sniu:

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This view file displays various statistics related to review scores obtained by the student in different assignments.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assignments_controller.rb app/controllers/assignments_controller.rb]'''

The assignments controller contains the new, create, edit, update, delete and various other useful functions pertaining to the assignment objects.

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page (http://expertiza.ncsu.edu/student_task/list). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the app/views/grades/_teammate_reviews.html.erb file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value 'k', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is not less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Potential performance issues==
Testing will be carried out to verify the desired functionality.
A view of aggregation of teammates and reviews are added.The information of teammates are shown on two pages: the course page and the assignment page. There may exist duplication of method calls, which will increase the overall loading time.

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-01T00:32:29Z

Sniu: /* Use Cases */

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This file is respondable for, from insturctor’s view, showing all the students’s info enrolled in one course and the review scores they got from their teammates.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assignments_controller.rb app/controllers/assignments_controller.rb]'''

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page (http://expertiza.ncsu.edu/student_task/list). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the app/views/grades/_teammate_reviews.html.erb file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value 'k', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is not less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Testing Requirements==
Testing will be carried out to verify the desired functionality.
For example:
A student have a new teammate in one of the course’s assignment. Then this student should be able to see this teammate on the teammates page for this course, not just on the teammates page for this assignment.
If this new teammate gave him a new review score based on his contribution to their teamwork, this student should be able to see the review score if the number of reviews given for this assignment is higher than k, which is preassigned by the instructor for this assignment. The review access condition is shown in the figure above.

==Conclusion==

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-01T00:31:32Z

Sniu: /* Use Cases */

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This file is respondable for, from insturctor’s view, showing all the students’s info enrolled in one course and the review scores they got from their teammates.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assignments_controller.rb app/controllers/assignments_controller.rb]'''

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page (http://expertiza.ncsu.edu/student_task/list). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the app/views/grades/_teammate_reviews.html.erb file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value 'k', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Testing Requirements==
Testing will be carried out to verify the desired functionality.
For example:
A student have a new teammate in one of the course’s assignment. Then this student should be able to see this teammate on the teammates page for this course, not just on the teammates page for this assignment.
If this new teammate gave him a new review score based on his contribution to their teamwork, this student should be able to see the review score if the number of reviews given for this assignment is higher than k, which is preassigned by the instructor for this assignment. The review access condition is shown in the figure above.

==Conclusion==

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-01T00:30:30Z

Sniu:

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This file is respondable for, from insturctor’s view, showing all the students’s info enrolled in one course and the review scores they got from their teammates.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assignments_controller.rb app/controllers/assignments_controller.rb]'''

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page (http://expertiza.ncsu.edu/student_task/list). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the app/views/grades/_teammate_reviews.html.erb file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value''', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Testing Requirements==
Testing will be carried out to verify the desired functionality.
For example:
A student have a new teammate in one of the course’s assignment. Then this student should be able to see this teammate on the teammates page for this course, not just on the teammates page for this assignment.
If this new teammate gave him a new review score based on his contribution to their teamwork, this student should be able to see the review score if the number of reviews given for this assignment is higher than k, which is preassigned by the instructor for this assignment. The review access condition is shown in the figure above.

==Conclusion==

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-01T00:29:15Z

Sniu: /* Problem statements */

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

==Problem statements==
The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/student_task_controller.rb app/controllers/student_task_controller.rb]'''
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/student_task/list.html.erb app/views/student_task/list.html.erb]'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/views/assessment360/all_students_all_reviews.html.erb app/views/assessment360/all_students_all_reviews.html.erb]'''

This file is respondable for, from insturctor’s view, showing all the students’s info enrolled in one course and the review scores they got from their teammates.

*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assignments_controller.rb app/controllers/assignments_controller.rb]'''

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page (http://expertiza.ncsu.edu/student_task/list). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the app/views/grades/_teammate_reviews.html.erb file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value''', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Testing Requirements==
Testing will be carried out to verify the desired functionality.
For example:
A student have a new teammate in one of the course’s assignment. Then this student should be able to see this teammate on the teammates page for this course, not just on the teammates page for this assignment.
If this new teammate gave him a new review score based on his contribution to their teamwork, this student should be able to see the review score if the number of reviews given for this assignment is higher than k, which is preassigned by the instructor for this assignment. The review access condition is shown in the figure above.

==Conclusion==

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-01T00:26:25Z

Sniu: /* Problem statements */

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

==Problem statements==
The following section discusses briefly about each file that has would be modified in the course of this project.
*'''[https://github.com/expertiza/expertiza/blob/rails4/app/controllers/assessment360_controller.rb app/controllers/assessment360_controller.rb]'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''app/controllers/student_task_controller.rb'''
*'''app/views/student_task/list.html.erb'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''app/views/assessment360/all_students_all_reviews.html.erb'''

This file is respondable for, from insturctor’s view, showing all the students’s info enrolled in one course and the review scores they got from their teammates.

*'''app/controllers/assignments_controller.rb'''

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page (http://expertiza.ncsu.edu/student_task/list). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the app/views/grades/_teammate_reviews.html.erb file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value''', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Testing Requirements==
Testing will be carried out to verify the desired functionality.
For example:
A student have a new teammate in one of the course’s assignment. Then this student should be able to see this teammate on the teammates page for this course, not just on the teammates page for this assignment.
If this new teammate gave him a new review score based on his contribution to their teamwork, this student should be able to see the review score if the number of reviews given for this assignment is higher than k, which is preassigned by the instructor for this assignment. The review access condition is shown in the figure above.

==Conclusion==

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-01T00:24:26Z

Sniu: /* Problem statements */

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

==Problem statements==
The following section discusses briefly about each file that has would be modified in the course of this project.
*'''app/controllers/assessment360_controller.rb'''

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*'''app/controllers/student_task_controller.rb'''
*'''app/views/student_task/list.html.erb'''

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*'''app/views/assessment360/all_students_all_reviews.html.erb'''

This file is respondable for, from insturctor’s view, showing all the students’s info enrolled in one course and the review scores they got from their teammates.

*'''app/controllers/assignments_controller.rb'''

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page (http://expertiza.ncsu.edu/student_task/list). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the app/views/grades/_teammate_reviews.html.erb file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value''', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Testing Requirements==
Testing will be carried out to verify the desired functionality.
For example:
A student have a new teammate in one of the course’s assignment. Then this student should be able to see this teammate on the teammates page for this course, not just on the teammates page for this assignment.
If this new teammate gave him a new review score based on his contribution to their teamwork, this student should be able to see the review score if the number of reviews given for this assignment is higher than k, which is preassigned by the instructor for this assignment. The review access condition is shown in the figure above.

==Conclusion==

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-01T00:21:40Z

Sniu: /* Problem statements */

Expertiza - Teaming information and analytics 
__TOC__

==Overview==
===Introduction To Expertiza===
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (Original version)]</ref>

===Motivation===
Expertiza is a large project developed as a combined effort of students and faculty using the Ruby on Rails framework. The main advantage of using Expertiza, in an educational environment, is for the instructor to introduce peer reviewing among the students. Expertiza allows the instructor to create and customize assignments, create a list of topics the students can sign up for, have students work on teams and then review each other's assignments at the end. Expertiza supports submission of almost any document type, including the URLs and wiki pages.
Currently the teaming information is only accessible from specific assignment. Sometimes a course may require a student to work with at least, for example 5 other students. To check teaming information for a course, It would be helpful for a student to have a way in Expertiza to see how many other students (s)he has teamed with during a course, and who those students are. An instructor might also want to see this information for grading purposes. Similarly, instructors and students want to see scores that teammates have given them for contributions to their team projects.

===Scope===
New features added to the system will

*Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.
*Allow students to see the review score that teammates have given them for contributions to their team projects.
*Allow the instructor to be able to see the teaming information of all the students.
*Prevent students from seeing individual review scores when the number of team members who reviewed the student is < k, where k should be settable by the instructor when editing an assignment.

==Documentation==
All the documentation for the Expertiza system can be found in the following links:
[https://github.com/expertiza/expertiza Expertiza on Github]
[http://wikis.lib.ncsu.edu/index.php/Expertiza Wiki documentation for Expertiza]

==Problem statements==
The following section discusses briefly about each file that has would be modified in the course of this project.
*app/controllers/assessment360_controller.rb

This file implements methods to represent various scores obtained by the student in each individual assignment and all assignments together in various pictorial formats such as Pie Charts and Bar Charts.

*app/controllers/student_task_controller.rb
*app/views/student_task/list.html.erb

These files handle all the assignments related functions. These include showing all the assignments of all the courses, and displaying details about each assignment such as deadlines, team details, submission links, links to review others’ work, scores etc.

*app/views/assessment360/all_students_all_reviews.html.erb

This file is respondable for, from insturctor’s view, showing all the students’s info enrolled in one course and the review scores they got from their teammates.

*app/controllers/assignments_controller.rb

==Use Cases==

* '''Use Case 1: Allow a student to see how many other students (s)he has teamed with during a course, and who those students are.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

In order to achieve this, we plan to add a link, say “Teammates” in the “Assignments” page (http://expertiza.ncsu.edu/student_task/list). Clicking on the Teammates link leads to a page consisting of all the courses the student is enrolled in and number of people (s)he has teamed up with till then. This goal can be achieved by adding additional methods to the app/views/student_task/list.html.erb file and app/controllers/student_task_controller.rb.

* '''Use Case 2: Allow students to see the review score that teammates have given them for contributions to their team projects.'''
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Open any assignment on the “Assignments” page.
*** Open “Your Scores” to find the review scores given by teammates in the “Teammate review” column.

We noticed there is already a field “Teammate review” available in the “Your scores” (http://expertiza.ncsu.edu/grades/view_my_scores/<id>) page of each assignment, and as of now it seems to be unused. We plan to use this section for allowing the students to see their review scores given by the team mates. This can be achieved by making changes to the app/views/grades/_teammate_reviews.html.erb file.

* '''Use Case 3: Allow the instructor to be able to see the teaming information of all the students.'''
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** Open the “Teammates” link in the “Assignments” page to find the number of people the student has collaborated with till then.

This would involve adding similar changes as allowing students to view their teammates in the Instructors views.

* '''Use Case 4: Prevent students from seeing individual review scores when the number of team members who reviewed the student is less than a minimum value''', where k should be settable by the instructor when editing an assignment.
** '''Actor:''' Instructor
** '''Actions:'''
*** Instructor logs in to Expertiza.
*** A minimum value k is set by the instructor
** '''Actor:''' Student
** '''Actions:'''
*** Student logs in to Expertiza.
*** Students should be able to see individual review scores only when number of team members who reviewed the student is less than k

This can be achieved by adding an additional implementation detail that checks for the number of reviews received by the student while adding the review scores field for each student.

[[File:use_case.png‎ |frame|center|Use Case Diagram]]

==Testing Requirements==
Testing will be carried out to verify the desired functionality.
For example:
A student have a new teammate in one of the course’s assignment. Then this student should be able to see this teammate on the teammates page for this course, not just on the teammates page for this assignment.
If this new teammate gave him a new review score based on his contribution to their teamwork, this student should be able to see the review score if the number of reviews given for this assignment is higher than k, which is preassigned by the instructor for this assignment. The review access condition is shown in the figure above.

==Conclusion==

==Reference==
<references/>

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-01T00:15:03Z

Sniu: /* Use Cases */

File:Use case.jpg

2015-04-01T00:11:16Z

Sniu:

File:Use case.png

2015-04-01T00:09:35Z

Sniu: uploaded a new version of "File:Use case.png"

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-01T00:07:23Z

Sniu: /* Problem statements */

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-01T00:07:17Z

Sniu: /* Documentation */

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-04-01T00:06:58Z

Sniu:

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-03-31T23:31:21Z

Sniu: /* Introduction To Expertiza */

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-03-31T23:30:50Z

Sniu:

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-03-31T23:30:20Z

Sniu:

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-03-31T23:30:10Z

Sniu:

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-03-31T23:30:01Z

Sniu:

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-03-31T23:21:22Z

Sniu:

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-03-31T23:18:38Z

Sniu:

Expertiza - Teaming information and analytics 

Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (low performance)]</ref>
__TOC__

==Introduction==
===Purpose===
===Scope Of The Project===

==Reference==

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-03-31T23:18:17Z

Sniu:

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-03-31T23:18:07Z

Sniu:

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-03-31T23:16:19Z

Sniu:

CSC/ECE 517 Spring 2015 E1525 TIAA

2015-03-31T23:15:55Z

Sniu: Created page with " Expertiza - Teaming information and analytics Expertiza is a web application where students can submit and peer-review learning objects (articles,..."

CSC/ECE 517 Spring 2015

2015-03-31T23:12:51Z

Sniu:

==Writing Assignment 1==
*[[CSC/ECE 517 Spring 2015/ch1a 17 WL]]
*[[CSC/ECE 517 Spring 2015/ch1a 5 ZX]]
*[[CSC/ECE 517 Spring 2015/ch1a 6 TZ]]
*[[CSC/ECE 517 Spring 2015/ch1a 4 RW]]
*[[CSC/ECE 517 Spring 2015/ch1a 7 SA]]
*[[CSC/ECE 517 Spring 2015/ch1a 9 RA]]
*[[CSC/ECE 517 Spring 2015/ch1a 14 RI]]
*[[CSC/ECE 517 Spring 2015/ch1a 1 DZ]]
*[[CSC/ECE 517 Spring 2015/ch1a 20 HA]]
*[[CSC/ECE 517 Spring 2015/ch1a 3 RF]]
*[[CSC/ECE 517 Spring 2015/ch1a 12 LS]]
*[[CSC/ECE 517 Spring 2015/ch1a 13 MA]]
*[[CSC/ECE 517 Spring 2015/ch1a 2 WA]]
*[[CSC/ECE 517 Spring 2015/ch1b 21 QW]]
*[[CSC/ECE 517 Spring 2015/ch1b 23 MS]]
*[[CSC/ECE 517 Spring 2015/ch1b 10 GL]]
*[[CSC/ECE 517 Spring 2015/ch1b 27 VC]]
*[[CSC/ECE 517 Spring 2015/ch1b 22 SF]]
*[[CSC/ECE 517 Spring 2015/ch1b 15 SH]]
*[[CSC/ECE 517 Spring 2015/ch1b 18 AS]]

==Writing Assignment 2==
*[[CSC/ECE 517 Spring 2015/oss E1502 wwj]]
*[[CSC/ECE 517 Fall 2014/oss E1508 MRS]]
*[[CSC/ECE 517 Spring 2015/oss E1504 IMV]]
*[[CSC/ECE 517 Spring 2015/oss E1505 xzl]]
*[[CSC/ECE 517 Spring 2015/oss E1509 lds]]
*[[CSC/ECE 517 Spring 2015/oss E1510 FLP]]
*[[CSC/ECE 517 Spring 2015/oss E1506 SYZ]]
*[[CSC/ECE 517 Spring 2015/oss S1504 AAC]]
*[[CSC/ECE 517 Spring 2015/oss E1507 DG]]
*[[CSC/ECE 517 Spring 2015/oss M1502 GVJ]]
*[[CSC/ECE 517 Spring 2015/oss M1503 EDT]]
*[[CSC/ECE 517 Spring 2015/oss E1503 RSA]]
*[[CSC/ECE 517 Spring 2015/oss E1501 YWS]]
*[[CSC/ECE 517 Spring 2015/oss S1501 OA]]

==Final Project Design Document==

*[[CSC/ECE 517 Spring 2015 E1526 MPRI]]
*[[CSC/ECE 517 Spring 2015 S1503 LWJZ]]
*[[CSC/ECE 517 Spring 2015 S1524 FSZZ]]
*[[CSC/ECE 517 Spring 2015 M1503 EDTS]]
*[[CSC/ECE 517 Spring 2015 E1529 GLDS]]
*[[CSC/ECE 517 Spring 2015 E1525 TIAA]]

CSC/ECE 517 Spring 2015/oss E1510 FLP

2015-03-24T01:46:10Z

Sniu: /* Conclusion */

Expertiza - Fix Instructor Login Performance Issue 

Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub (low performance)]</ref>
__TOC__

==Project Description==
Currently when an Instructor logs into Expertiza,there are a lot of select* from assignments queries being fired on database which would have an adverse effect on performance. We analyzed the source of this issue and made some changes, which reduced the number of select queries executed. The performance is high improved.
The mission involved is tracing the source of the issue and modify the code to fix the issue.

===Performance issue before modification===
Before the improvement is achieved, each time an instructor logs into Expertiza, there would be several database queries, which are more than needed and take more time to render the view. Below is the console outputs when an instructor logs in.

[[File:before_modify.png|center]]

we can see that there are 7 assignment queries after load <code>_row_header.html.erb</code>, 3 assignment queries after load <code>_shared_actions.html.erb</code>, 3 assignment queries after load <code>_assignments_actions</code>. All of these queries are same.These duplicate queries have an adverse effect on the performance.

==Locate source of issues==
To locate the files that generate the duplication of queries, we use a Gem called QueryReviewer<ref>https://github.com/nesquena/query_reviewer</ref> to help trace the datebase queries. QueryReviewer is an advanced SQL query analyzer<ref>https://github.com/nesquena/query_reviewer</ref>. It accomplishes the following goals:
* View all <code>EXPLAIN</code> output for all <code>SELECT</code> queries to generate a page
* Rate a page's SQL usage into one of three categories: <code>OK, WARNING, CRITICAL</code>
* Attach meaningful warnings to individual queries, and collections of queries
* Display interactive summary on page
===Install query_reviewer===
Installing query_reviewer is simple. All you have to do to install it into your Rails 2 or 3 project is

<pre>
gem install query_reviewer
</pre>

Right now if you use bundler, simply add this to your <code>Gemfile</code>:

<pre>
# Gemfile
gem "query_reviewer"
</pre>

or to use the latest from github:
<pre>
# Gemfile
gem "query_reviewer", :github => "nesquena/query_reviewer"
</pre>

After installing and running this Gem on the Rails application, it would pop-up database query information on the webpage, as is shown below.

[[File:Query_Reviewer.jpg|center]]

We can thus follow the trace of this query reviewer page, and locate the source of the issue in <code>assignment_node.rb</code>, also the source code in <code>_assignment_action.html.erb</code>

===Analyze code===
We log into Expertiza as an instructor with the QueryReviewer activate and watch the output of QueryReviewer. The above figure shows the tracing result of the QueryReviewer and it tells us that we should pay more attention to the three files: assignment_node.rb, _row_header.html.erb and _entry.html.erb.
==== [https://github.com/fwu8/expertiza/blob/master/app/views/tree_display/actions/_assignments_actions.html.erb <code>_assignment_actions.html.erb</code>] ====
In file <code>_assignment_actions.html.erb</code>, we can find in 3 places use <code>Assignment.find(node.node_object_id)</code>, which is actually a database query request.
<pre>
1 <% owner_id = Object.const_get('Assignment').find(node.node_object_id).instructor_id %>
...
11 <% @assignment = Assignment.find(node.node_object_id) %>
...
52 <% if Assignment.find(node.node_object_id).course_id %>
...
</pre>

==== <code>_row_header.html.erb</code>] and <code>assignment_node.rb</code> ====
In [https://github.com/fwu8/expertiza/blob/master/app/views/tree_display/_row_header.html.erb <code>_row_header.html.erb</code>]:
<pre>
26 <% if parent_node.get_name == 'Courses'&& session[:user].role_id == 6 %>
27 <%else%>
28 <%= parent_node.get_name %>
29 <% if parent_node.get_directory != nil%>
30 Directory: <%= parent_node.get_directory %>
31 <% end %>
32 <% if parent_node.get_creation_date != nil %>
33 Creation Date: <%= parent_node.get_creation_date %>
34 <% end %>
35 <% if parent_node.get_modified_date != nil %>
36 Updated Date: <%= parent_node.get_modified_date %>
37 <% end %>
38 <%end%>
</pre>
we can see in this view, <code>parent_node</code> is a <code>AssignmentNode</code> object, it execute:
* <code>parent_node.get_name</code> method
* <code>parent_node.get_directory</code> method
* <code>parent_node.get_creation_date</code> method
* <code>parent_node.get_modified_date</code> method
However, in [https://github.com/fwu8/expertiza/blob/master/app/models/assignment_node.rb <code>assignment_node.rb</code>]:
<pre>
6 class AssignmentNode < Node
...
58 # Gets the name from the associated object
59 def get_name
60 Assignment.find(self.node_object_id).name
61 end
62
63 # Gets the directory_path from the associated object
64 def get_directory
65 Assignment.find(self.node_object_id).directory_path
66 end
67
68 # Gets the created_at from the associated object
69 def get_creation_date
70 Assignment.find(self.node_object_id).created_at
71 end
72
73 # Gets the updated_at from the associated object
74 def get_modified_date
75 Assignment.find(self.node_object_id).updated_at
76 end
...
82 end
</pre>
We find all these method called <code>Assignment.find(self.node_object_id)</code> method, which is actually a database query request. These 'find's are actually redundant for a specific Assignment instance. So we will figure out a way to eliminate those redundant method calls.

==Modifications==

===_assignment_actions.html.erb===
An instance variable <code>@assignment</code> is used here instead of multiple times of calling <code>.find</code> method, thus reducing database queries.
<pre>
+ <% @assignment = Assignment.find(node.node_object_id) %>
- <% owner_id = Object.const_get('Assignment').find(node.node_object_id).instructor_id %>
+ <% owner_id = @assignment.instructor_id %>
...
- <% @assignment = Assignment.find(node.node_object_id) %>
...
- <% if Assignment.find(node.node_object_id).course_id %>
+ <% if @assignment.course_id %>
...
</pre>

===assignment_node.rb===
In this class, we define a new variable <code>@assign_node</code>, and in every <code>get_</code> method, instead of using <code>Assignment.find(self.node_object_id)</code> to find the AssignmentNode object, we first search if <code>@assign_node</code> variable exist, if not, we define <code>@assign_node = Assignment.find(self.node_object_id)</code>, else we directly use <code>@assign_node</code>. Because <code>_row_header.html.erb</code> file has many <code>get_</code> method, after modification, the number of assignment queries decreases much.
<pre>
class AssignmentNode < Node
# Gets the name from the associated object
def get_name
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.name
end

# Gets the directory_path from the associated object
def get_directory
#Assignment.find(self.node_object_id).directory_path
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.directory_path
end

# Gets the created_at from the associated object
def get_creation_date
#Assignment.find(self.node_object_id).created_at
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.created_at
end

# Gets the updated_at from the associated object
def get_modified_date
#Assignment.find(self.node_object_id).updated_at
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.updated_at
end
end
</pre>

== Performance Improvement==
* Originally there are 13 queries after loading these related pages, and now there are only 5 of them. As shown below.
* The time consumed for rendering the view is 943 sec before and 284 after the modification.
We can see the performance has been highly improved. If we have a larger database, the improvement would be more significant.
[[File:after_modify.png|center]]

==Conclusion==
Before our modification, when an instructor open the expertiza website and log in, it takes much time to show the page after log in, especially when a larger database hiding behind. We saw the problem on the console windows which emerged as a duplication of unnecessary queries. After our modification, the duplication disappeared and the time consumption is reduced significantly. Now when an instructor log in expertiza, it takes shorter time to get to page after log in. Please check our new version of [https://github.com/fwu8/expertiza expertiza] on github.

==References==
<references/>

CSC/ECE 517 Spring 2015/oss E1510 FLP

2015-03-24T01:45:04Z

Sniu:

CSC/ECE 517 Spring 2015/oss E1510 FLP

2015-03-24T01:44:51Z

Sniu:

Expertiza - Fix Instructor Login Performance Issue 

Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub(low performance)]</ref>
__TOC__

==Project Description==
Currently when an Instructor logs into Expertiza,there are a lot of select* from assignments queries being fired on database which would have an adverse effect on performance. We analyzed the source of this issue and made some changes, which reduced the number of select queries executed. The performance is high improved.
The mission involved is tracing the source of the issue and modify the code to fix the issue.

===Performance issue before modification===
Before the improvement is achieved, each time an instructor logs into Expertiza, there would be several database queries, which are more than needed and take more time to render the view. Below is the console outputs when an instructor logs in.

[[File:before_modify.png|center]]

we can see that there are 7 assignment queries after load <code>_row_header.html.erb</code>, 3 assignment queries after load <code>_shared_actions.html.erb</code>, 3 assignment queries after load <code>_assignments_actions</code>. All of these queries are same.These duplicate queries have an adverse effect on the performance.

==Locate source of issues==
To locate the files that generate the duplication of queries, we use a Gem called QueryReviewer<ref>https://github.com/nesquena/query_reviewer</ref> to help trace the datebase queries. QueryReviewer is an advanced SQL query analyzer<ref>https://github.com/nesquena/query_reviewer</ref>. It accomplishes the following goals:
* View all <code>EXPLAIN</code> output for all <code>SELECT</code> queries to generate a page
* Rate a page's SQL usage into one of three categories: <code>OK, WARNING, CRITICAL</code>
* Attach meaningful warnings to individual queries, and collections of queries
* Display interactive summary on page
===Install query_reviewer===
Installing query_reviewer is simple. All you have to do to install it into your Rails 2 or 3 project is

<pre>
gem install query_reviewer
</pre>

Right now if you use bundler, simply add this to your <code>Gemfile</code>:

<pre>
# Gemfile
gem "query_reviewer"
</pre>

or to use the latest from github:
<pre>
# Gemfile
gem "query_reviewer", :github => "nesquena/query_reviewer"
</pre>

After installing and running this Gem on the Rails application, it would pop-up database query information on the webpage, as is shown below.

[[File:Query_Reviewer.jpg|center]]

We can thus follow the trace of this query reviewer page, and locate the source of the issue in <code>assignment_node.rb</code>, also the source code in <code>_assignment_action.html.erb</code>

===Analyze code===
We log into Expertiza as an instructor with the QueryReviewer activate and watch the output of QueryReviewer. The above figure shows the tracing result of the QueryReviewer and it tells us that we should pay more attention to the three files: assignment_node.rb, _row_header.html.erb and _entry.html.erb.
==== [https://github.com/fwu8/expertiza/blob/master/app/views/tree_display/actions/_assignments_actions.html.erb <code>_assignment_actions.html.erb</code>] ====
In file <code>_assignment_actions.html.erb</code>, we can find in 3 places use <code>Assignment.find(node.node_object_id)</code>, which is actually a database query request.
<pre>
1 <% owner_id = Object.const_get('Assignment').find(node.node_object_id).instructor_id %>
...
11 <% @assignment = Assignment.find(node.node_object_id) %>
...
52 <% if Assignment.find(node.node_object_id).course_id %>
...
</pre>

==== <code>_row_header.html.erb</code>] and <code>assignment_node.rb</code> ====
In [https://github.com/fwu8/expertiza/blob/master/app/views/tree_display/_row_header.html.erb <code>_row_header.html.erb</code>]:
<pre>
26 <% if parent_node.get_name == 'Courses'&& session[:user].role_id == 6 %>
27 <%else%>
28 <%= parent_node.get_name %>
29 <% if parent_node.get_directory != nil%>
30 Directory: <%= parent_node.get_directory %>
31 <% end %>
32 <% if parent_node.get_creation_date != nil %>
33 Creation Date: <%= parent_node.get_creation_date %>
34 <% end %>
35 <% if parent_node.get_modified_date != nil %>
36 Updated Date: <%= parent_node.get_modified_date %>
37 <% end %>
38 <%end%>
</pre>
we can see in this view, <code>parent_node</code> is a <code>AssignmentNode</code> object, it execute:
* <code>parent_node.get_name</code> method
* <code>parent_node.get_directory</code> method
* <code>parent_node.get_creation_date</code> method
* <code>parent_node.get_modified_date</code> method
However, in [https://github.com/fwu8/expertiza/blob/master/app/models/assignment_node.rb <code>assignment_node.rb</code>]:
<pre>
6 class AssignmentNode < Node
...
58 # Gets the name from the associated object
59 def get_name
60 Assignment.find(self.node_object_id).name
61 end
62
63 # Gets the directory_path from the associated object
64 def get_directory
65 Assignment.find(self.node_object_id).directory_path
66 end
67
68 # Gets the created_at from the associated object
69 def get_creation_date
70 Assignment.find(self.node_object_id).created_at
71 end
72
73 # Gets the updated_at from the associated object
74 def get_modified_date
75 Assignment.find(self.node_object_id).updated_at
76 end
...
82 end
</pre>
We find all these method called <code>Assignment.find(self.node_object_id)</code> method, which is actually a database query request. These 'find's are actually redundant for a specific Assignment instance. So we will figure out a way to eliminate those redundant method calls.

==Modifications==

===_assignment_actions.html.erb===
An instance variable <code>@assignment</code> is used here instead of multiple times of calling <code>.find</code> method, thus reducing database queries.
<pre>
+ <% @assignment = Assignment.find(node.node_object_id) %>
- <% owner_id = Object.const_get('Assignment').find(node.node_object_id).instructor_id %>
+ <% owner_id = @assignment.instructor_id %>
...
- <% @assignment = Assignment.find(node.node_object_id) %>
...
- <% if Assignment.find(node.node_object_id).course_id %>
+ <% if @assignment.course_id %>
...
</pre>

===assignment_node.rb===
In this class, we define a new variable <code>@assign_node</code>, and in every <code>get_</code> method, instead of using <code>Assignment.find(self.node_object_id)</code> to find the AssignmentNode object, we first search if <code>@assign_node</code> variable exist, if not, we define <code>@assign_node = Assignment.find(self.node_object_id)</code>, else we directly use <code>@assign_node</code>. Because <code>_row_header.html.erb</code> file has many <code>get_</code> method, after modification, the number of assignment queries decreases much.
<pre>
class AssignmentNode < Node
# Gets the name from the associated object
def get_name
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.name
end

# Gets the directory_path from the associated object
def get_directory
#Assignment.find(self.node_object_id).directory_path
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.directory_path
end

# Gets the created_at from the associated object
def get_creation_date
#Assignment.find(self.node_object_id).created_at
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.created_at
end

# Gets the updated_at from the associated object
def get_modified_date
#Assignment.find(self.node_object_id).updated_at
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.updated_at
end
end
</pre>

== Performance Improvement==
* Originally there are 13 queries after loading these related pages, and now there are only 5 of them. As shown below.
* The time consumed for rendering the view is 943 sec before and 284 after the modification.
We can see the performance has been highly improved. If we have a larger database, the improvement would be more significant.
[[File:after_modify.png|center]]

==Conclusion==
Before our modification, when an instructor open the expertiza website and log in, it takes much time to show the page after log in, especially when a larger database hiding behind. We saw the problem on the console windows which emerged as a duplication of unnecessary queries. After our modification, the duplication disappeared and the time consumption is reduced significantly. Now when an instructor log in expertiza, it takes shorter time to get to page after log in.
==References==
<references/>

CSC/ECE 517 Spring 2015/oss E1510 FLP

2015-03-24T01:43:43Z

Sniu: /* References */

Expertiza - Fix Instructor Login Performance Issue 

Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub]</ref>
__TOC__

==Project Description==
Currently when an Instructor logs into Expertiza,there are a lot of select* from assignments queries being fired on database which would have an adverse effect on performance. We analyzed the source of this issue and made some changes, which reduced the number of select queries executed. The performance is high improved.
The mission involved is tracing the source of the issue and modify the code to fix the issue.

===Performance issue before modification===
Before the improvement is achieved, each time an instructor logs into Expertiza, there would be several database queries, which are more than needed and take more time to render the view. Below is the console outputs when an instructor logs in.

[[File:before_modify.png|center]]

we can see that there are 7 assignment queries after load <code>_row_header.html.erb</code>, 3 assignment queries after load <code>_shared_actions.html.erb</code>, 3 assignment queries after load <code>_assignments_actions</code>. All of these queries are same.These duplicate queries have an adverse effect on the performance.

==Locate source of issues==
To locate the files that generate the duplication of queries, we use a Gem called QueryReviewer<ref>https://github.com/nesquena/query_reviewer</ref> to help trace the datebase queries. QueryReviewer is an advanced SQL query analyzer<ref>https://github.com/nesquena/query_reviewer</ref>. It accomplishes the following goals:
* View all <code>EXPLAIN</code> output for all <code>SELECT</code> queries to generate a page
* Rate a page's SQL usage into one of three categories: <code>OK, WARNING, CRITICAL</code>
* Attach meaningful warnings to individual queries, and collections of queries
* Display interactive summary on page
===Install query_reviewer===
Installing query_reviewer is simple. All you have to do to install it into your Rails 2 or 3 project is

<pre>
gem install query_reviewer
</pre>

Right now if you use bundler, simply add this to your <code>Gemfile</code>:

<pre>
# Gemfile
gem "query_reviewer"
</pre>

or to use the latest from github:
<pre>
# Gemfile
gem "query_reviewer", :github => "nesquena/query_reviewer"
</pre>

After installing and running this Gem on the Rails application, it would pop-up database query information on the webpage, as is shown below.

[[File:Query_Reviewer.jpg|center]]

We can thus follow the trace of this query reviewer page, and locate the source of the issue in <code>assignment_node.rb</code>, also the source code in <code>_assignment_action.html.erb</code>

===Analyze code===
We log into Expertiza as an instructor with the QueryReviewer activate and watch the output of QueryReviewer. The above figure shows the tracing result of the QueryReviewer and it tells us that we should pay more attention to the three files: assignment_node.rb, _row_header.html.erb and _entry.html.erb.
==== [https://github.com/fwu8/expertiza/blob/master/app/views/tree_display/actions/_assignments_actions.html.erb <code>_assignment_actions.html.erb</code>] ====
In file <code>_assignment_actions.html.erb</code>, we can find in 3 places use <code>Assignment.find(node.node_object_id)</code>, which is actually a database query request.
<pre>
1 <% owner_id = Object.const_get('Assignment').find(node.node_object_id).instructor_id %>
...
11 <% @assignment = Assignment.find(node.node_object_id) %>
...
52 <% if Assignment.find(node.node_object_id).course_id %>
...
</pre>

==== <code>_row_header.html.erb</code>] and <code>assignment_node.rb</code> ====
In [https://github.com/fwu8/expertiza/blob/master/app/views/tree_display/_row_header.html.erb <code>_row_header.html.erb</code>]:
<pre>
26 <% if parent_node.get_name == 'Courses'&& session[:user].role_id == 6 %>
27 <%else%>
28 <%= parent_node.get_name %>
29 <% if parent_node.get_directory != nil%>
30 Directory: <%= parent_node.get_directory %>
31 <% end %>
32 <% if parent_node.get_creation_date != nil %>
33 Creation Date: <%= parent_node.get_creation_date %>
34 <% end %>
35 <% if parent_node.get_modified_date != nil %>
36 Updated Date: <%= parent_node.get_modified_date %>
37 <% end %>
38 <%end%>
</pre>
we can see in this view, <code>parent_node</code> is a <code>AssignmentNode</code> object, it execute:
* <code>parent_node.get_name</code> method
* <code>parent_node.get_directory</code> method
* <code>parent_node.get_creation_date</code> method
* <code>parent_node.get_modified_date</code> method
However, in [https://github.com/fwu8/expertiza/blob/master/app/models/assignment_node.rb <code>assignment_node.rb</code>]:
<pre>
6 class AssignmentNode < Node
...
58 # Gets the name from the associated object
59 def get_name
60 Assignment.find(self.node_object_id).name
61 end
62
63 # Gets the directory_path from the associated object
64 def get_directory
65 Assignment.find(self.node_object_id).directory_path
66 end
67
68 # Gets the created_at from the associated object
69 def get_creation_date
70 Assignment.find(self.node_object_id).created_at
71 end
72
73 # Gets the updated_at from the associated object
74 def get_modified_date
75 Assignment.find(self.node_object_id).updated_at
76 end
...
82 end
</pre>
We find all these method called <code>Assignment.find(self.node_object_id)</code> method, which is actually a database query request. These 'find's are actually redundant for a specific Assignment instance. So we will figure out a way to eliminate those redundant method calls.

==Modifications==

===_assignment_actions.html.erb===
An instance variable <code>@assignment</code> is used here instead of multiple times of calling <code>.find</code> method, thus reducing database queries.
<pre>
+ <% @assignment = Assignment.find(node.node_object_id) %>
- <% owner_id = Object.const_get('Assignment').find(node.node_object_id).instructor_id %>
+ <% owner_id = @assignment.instructor_id %>
...
- <% @assignment = Assignment.find(node.node_object_id) %>
...
- <% if Assignment.find(node.node_object_id).course_id %>
+ <% if @assignment.course_id %>
...
</pre>

===assignment_node.rb===
In this class, we define a new variable <code>@assign_node</code>, and in every <code>get_</code> method, instead of using <code>Assignment.find(self.node_object_id)</code> to find the AssignmentNode object, we first search if <code>@assign_node</code> variable exist, if not, we define <code>@assign_node = Assignment.find(self.node_object_id)</code>, else we directly use <code>@assign_node</code>. Because <code>_row_header.html.erb</code> file has many <code>get_</code> method, after modification, the number of assignment queries decreases much.
<pre>
class AssignmentNode < Node
# Gets the name from the associated object
def get_name
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.name
end

# Gets the directory_path from the associated object
def get_directory
#Assignment.find(self.node_object_id).directory_path
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.directory_path
end

# Gets the created_at from the associated object
def get_creation_date
#Assignment.find(self.node_object_id).created_at
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.created_at
end

# Gets the updated_at from the associated object
def get_modified_date
#Assignment.find(self.node_object_id).updated_at
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.updated_at
end
end
</pre>

== Performance Improvement==
* Originally there are 13 queries after loading these related pages, and now there are only 5 of them. As shown below.
* The time consumed for rendering the view is 943 sec before and 284 after the modification.
We can see the performance has been highly improved. If we have a larger database, the improvement would be more significant.
[[File:after_modify.png|center]]

==Conclusion==
Before our modification, when an instructor open the expertiza website and log in, it takes much time to show the page after log in, especially when a larger database hiding behind. We saw the problem on the console windows which emerged as a duplication of unnecessary queries. After our modification, the duplication disappeared and the time consumption is reduced significantly. Now when an instructor log in expertiza, it takes shorter time to get to page after log in.
==References==
<references/>

CSC/ECE 517 Spring 2015/oss E1510 FLP

2015-03-24T01:34:21Z

Sniu: /* Performance Improvement */

Expertiza - Fix Instructor Login Performance Issue 

Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub]</ref>
__TOC__

==Project Description==
Currently when an Instructor logs into Expertiza,there are a lot of select* from assignments queries being fired on database which would have an adverse effect on performance. We analyzed the source of this issue and made some changes, which reduced the number of select queries executed. The performance is high improved.
The mission involved is tracing the source of the issue and modify the code to fix the issue.

===Performance issue before modification===
Before the improvement is achieved, each time an instructor logs into Expertiza, there would be several database queries, which are more than needed and take more time to render the view. Below is the console outputs when an instructor logs in.

[[File:before_modify.png|center]]

we can see that there are 7 assignment queries after load <code>_row_header.html.erb</code>, 3 assignment queries after load <code>_shared_actions.html.erb</code>, 3 assignment queries after load <code>_assignments_actions</code>. All of these queries are same.These duplicate queries have an adverse effect on the performance.

==Locate source of issues==
To locate the files that generate the duplication of queries, we use a Gem called QueryReviewer<ref>https://github.com/nesquena/query_reviewer</ref> to help trace the datebase queries. QueryReviewer is an advanced SQL query analyzer<ref>https://github.com/nesquena/query_reviewer</ref>. It accomplishes the following goals:
* View all <code>EXPLAIN</code> output for all <code>SELECT</code> queries to generate a page
* Rate a page's SQL usage into one of three categories: <code>OK, WARNING, CRITICAL</code>
* Attach meaningful warnings to individual queries, and collections of queries
* Display interactive summary on page
===Install query_reviewer===
Installing query_reviewer is simple. All you have to do to install it into your Rails 2 or 3 project is

<pre>
gem install query_reviewer
</pre>

Right now if you use bundler, simply add this to your <code>Gemfile</code>:

<pre>
# Gemfile
gem "query_reviewer"
</pre>

or to use the latest from github:
<pre>
# Gemfile
gem "query_reviewer", :github => "nesquena/query_reviewer"
</pre>

After installing and running this Gem on the Rails application, it would pop-up database query information on the webpage, as is shown below.

[[File:Query_Reviewer.jpg|center]]

We can thus follow the trace of this query reviewer page, and locate the source of the issue in <code>assignment_node.rb</code>, also the source code in <code>_assignment_action.html.erb</code>

===Analyze code===
We log into Expertiza as an instructor with the QueryReviewer activate and watch the output of QueryReviewer. The above figure shows the tracing result of the QueryReviewer and it tells us that we should pay more attention to the three files: assignment_node.rb, _row_header.html.erb and _entry.html.erb.
==== [https://github.com/fwu8/expertiza/blob/master/app/views/tree_display/actions/_assignments_actions.html.erb <code>_assignment_actions.html.erb</code>] ====
In file <code>_assignment_actions.html.erb</code>, we can find in 3 places use <code>Assignment.find(node.node_object_id)</code>, which is actually a database query request.
<pre>
1 <% owner_id = Object.const_get('Assignment').find(node.node_object_id).instructor_id %>
...
11 <% @assignment = Assignment.find(node.node_object_id) %>
...
52 <% if Assignment.find(node.node_object_id).course_id %>
...
</pre>

==== <code>_row_header.html.erb</code>] and <code>assignment_node.rb</code> ====
In [https://github.com/fwu8/expertiza/blob/master/app/views/tree_display/_row_header.html.erb <code>_row_header.html.erb</code>]:
<pre>
26 <% if parent_node.get_name == 'Courses'&& session[:user].role_id == 6 %>
27 <%else%>
28 <%= parent_node.get_name %>
29 <% if parent_node.get_directory != nil%>
30 Directory: <%= parent_node.get_directory %>
31 <% end %>
32 <% if parent_node.get_creation_date != nil %>
33 Creation Date: <%= parent_node.get_creation_date %>
34 <% end %>
35 <% if parent_node.get_modified_date != nil %>
36 Updated Date: <%= parent_node.get_modified_date %>
37 <% end %>
38 <%end%>
</pre>
we can see in this view, <code>parent_node</code> is a <code>AssignmentNode</code> object, it execute:
* <code>parent_node.get_name</code> method
* <code>parent_node.get_directory</code> method
* <code>parent_node.get_creation_date</code> method
* <code>parent_node.get_modified_date</code> method
However, in [https://github.com/fwu8/expertiza/blob/master/app/models/assignment_node.rb <code>assignment_node.rb</code>]:
<pre>
6 class AssignmentNode < Node
...
58 # Gets the name from the associated object
59 def get_name
60 Assignment.find(self.node_object_id).name
61 end
62
63 # Gets the directory_path from the associated object
64 def get_directory
65 Assignment.find(self.node_object_id).directory_path
66 end
67
68 # Gets the created_at from the associated object
69 def get_creation_date
70 Assignment.find(self.node_object_id).created_at
71 end
72
73 # Gets the updated_at from the associated object
74 def get_modified_date
75 Assignment.find(self.node_object_id).updated_at
76 end
...
82 end
</pre>
We find all these method called <code>Assignment.find(self.node_object_id)</code> method, which is actually a database query request. These 'find's are actually redundant for a specific Assignment instance. So we will figure out a way to eliminate those redundant method calls.

==Modifications==

===_assignment_actions.html.erb===
An instance variable <code>@assignment</code> is used here instead of multiple times of calling <code>.find</code> method, thus reducing database queries.
<pre>
+ <% @assignment = Assignment.find(node.node_object_id) %>
- <% owner_id = Object.const_get('Assignment').find(node.node_object_id).instructor_id %>
+ <% owner_id = @assignment.instructor_id %>
...
- <% @assignment = Assignment.find(node.node_object_id) %>
...
- <% if Assignment.find(node.node_object_id).course_id %>
+ <% if @assignment.course_id %>
...
</pre>

===assignment_node.rb===
In this class, we define a new variable <code>@assign_node</code>, and in every <code>get_</code> method, instead of using <code>Assignment.find(self.node_object_id)</code> to find the AssignmentNode object, we first search if <code>@assign_node</code> variable exist, if not, we define <code>@assign_node = Assignment.find(self.node_object_id)</code>, else we directly use <code>@assign_node</code>. Because <code>_row_header.html.erb</code> file has many <code>get_</code> method, after modification, the number of assignment queries decreases much.
<pre>
class AssignmentNode < Node
# Gets the name from the associated object
def get_name
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.name
end

# Gets the directory_path from the associated object
def get_directory
#Assignment.find(self.node_object_id).directory_path
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.directory_path
end

# Gets the created_at from the associated object
def get_creation_date
#Assignment.find(self.node_object_id).created_at
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.created_at
end

# Gets the updated_at from the associated object
def get_modified_date
#Assignment.find(self.node_object_id).updated_at
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.updated_at
end
end
</pre>

== Performance Improvement==
* Originally there are 13 queries after loading these related pages, and now there are only 5 of them. As shown below.
* The time consumed for rendering the view is 943 sec before and 284 after the modification.
We can see the performance has been highly improved. If we have a larger database, the improvement would be more significant.
[[File:after_modify.png|center]]

==References==
<references/>

CSC/ECE 517 Spring 2015/oss E1510 FLP

2015-03-24T01:30:25Z

Sniu: /* Performance Improvment */

Expertiza - Fix Instructor Login Performance Issue 

Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub]</ref>
__TOC__

==Project Description==
Currently when an Instructor logs into Expertiza,there are a lot of select* from assignments queries being fired on database which would have an adverse effect on performance. We analyzed the source of this issue and made some changes, which reduced the number of select queries executed. The performance is high improved.
The mission involved is tracing the source of the issue and modify the code to fix the issue.

===Performance issue before modification===
Before the improvement is achieved, each time an instructor logs into Expertiza, there would be several database queries, which are more than needed and take more time to render the view. Below is the console outputs when an instructor logs in.

[[File:before_modify.png|center]]

we can see that there are 7 assignment queries after load <code>_row_header.html.erb</code>, 3 assignment queries after load <code>_shared_actions.html.erb</code>, 3 assignment queries after load <code>_assignments_actions</code>. All of these queries are same.These duplicate queries have an adverse effect on the performance.

==Locate source of issues==
To locate the files that generate the duplication of queries, we use a Gem called QueryReviewer<ref>https://github.com/nesquena/query_reviewer</ref> to help trace the datebase queries. QueryReviewer is an advanced SQL query analyzer<ref>https://github.com/nesquena/query_reviewer</ref>. It accomplishes the following goals:
* View all <code>EXPLAIN</code> output for all <code>SELECT</code> queries to generate a page
* Rate a page's SQL usage into one of three categories: <code>OK, WARNING, CRITICAL</code>
* Attach meaningful warnings to individual queries, and collections of queries
* Display interactive summary on page
===Install query_reviewer===
Installing query_reviewer is simple. All you have to do to install it into your Rails 2 or 3 project is

<pre>
gem install query_reviewer
</pre>

Right now if you use bundler, simply add this to your <code>Gemfile</code>:

<pre>
# Gemfile
gem "query_reviewer"
</pre>

or to use the latest from github:
<pre>
# Gemfile
gem "query_reviewer", :github => "nesquena/query_reviewer"
</pre>

After installing and running this Gem on the Rails application, it would pop-up database query information on the webpage, as is shown below.

[[File:Query_Reviewer.jpg|center]]

We can thus follow the trace of this query reviewer page, and locate the source of the issue in <code>assignment_node.rb</code>, also the source code in <code>_assignment_action.html.erb</code>

===Analyze code===
We log into Expertiza as an instructor with the QueryReviewer activate and watch the output of QueryReviewer. The above figure shows the tracing result of the QueryReviewer and it tells us that we should pay more attention to the three files: assignment_node.rb, _row_header.html.erb and _entry.html.erb.
==== [https://github.com/fwu8/expertiza/blob/master/app/views/tree_display/actions/_assignments_actions.html.erb <code>_assignment_actions.html.erb</code>] ====
In file <code>_assignment_actions.html.erb</code>, we can find in 3 places use <code>Assignment.find(node.node_object_id)</code>, which is actually a database query request.
<pre>
1 <% owner_id = Object.const_get('Assignment').find(node.node_object_id).instructor_id %>
...
11 <% @assignment = Assignment.find(node.node_object_id) %>
...
52 <% if Assignment.find(node.node_object_id).course_id %>
...
</pre>

==== <code>_row_header.html.erb</code>] and <code>assignment_node.rb</code> ====
In [https://github.com/fwu8/expertiza/blob/master/app/views/tree_display/_row_header.html.erb <code>_row_header.html.erb</code>]:
<pre>
26 <% if parent_node.get_name == 'Courses'&& session[:user].role_id == 6 %>
27 <%else%>
28 <%= parent_node.get_name %>
29 <% if parent_node.get_directory != nil%>
30 Directory: <%= parent_node.get_directory %>
31 <% end %>
32 <% if parent_node.get_creation_date != nil %>
33 Creation Date: <%= parent_node.get_creation_date %>
34 <% end %>
35 <% if parent_node.get_modified_date != nil %>
36 Updated Date: <%= parent_node.get_modified_date %>
37 <% end %>
38 <%end%>
</pre>
we can see in this view, <code>parent_node</code> is a <code>AssignmentNode</code> object, it execute:
* <code>parent_node.get_name</code> method
* <code>parent_node.get_directory</code> method
* <code>parent_node.get_creation_date</code> method
* <code>parent_node.get_modified_date</code> method
However, in [https://github.com/fwu8/expertiza/blob/master/app/models/assignment_node.rb <code>assignment_node.rb</code>]:
<pre>
6 class AssignmentNode < Node
...
58 # Gets the name from the associated object
59 def get_name
60 Assignment.find(self.node_object_id).name
61 end
62
63 # Gets the directory_path from the associated object
64 def get_directory
65 Assignment.find(self.node_object_id).directory_path
66 end
67
68 # Gets the created_at from the associated object
69 def get_creation_date
70 Assignment.find(self.node_object_id).created_at
71 end
72
73 # Gets the updated_at from the associated object
74 def get_modified_date
75 Assignment.find(self.node_object_id).updated_at
76 end
...
82 end
</pre>
We find all these method called <code>Assignment.find(self.node_object_id)</code> method, which is actually a database query request. These 'find's are actually redundant for a specific Assignment instance. So we will figure out a way to eliminate those redundant method calls.

==Modifications==

===_assignment_actions.html.erb===
An instance variable <code>@assignment</code> is used here instead of multiple times of calling <code>.find</code> method, thus reducing database queries.
<pre>
+ <% @assignment = Assignment.find(node.node_object_id) %>
- <% owner_id = Object.const_get('Assignment').find(node.node_object_id).instructor_id %>
+ <% owner_id = @assignment.instructor_id %>
...
- <% @assignment = Assignment.find(node.node_object_id) %>
...
- <% if Assignment.find(node.node_object_id).course_id %>
+ <% if @assignment.course_id %>
...
</pre>

===assignment_node.rb===
In this class, we define a new variable <code>@assign_node</code>, and in every <code>get_</code> method, instead of using <code>Assignment.find(self.node_object_id)</code> to find the AssignmentNode object, we first search if <code>@assign_node</code> variable exist, if not, we define <code>@assign_node = Assignment.find(self.node_object_id)</code>, else we directly use <code>@assign_node</code>. Because <code>_row_header.html.erb</code> file has many <code>get_</code> method, after modification, the number of assignment queries decreases much.
<pre>
class AssignmentNode < Node
# Gets the name from the associated object
def get_name
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.name
end

# Gets the directory_path from the associated object
def get_directory
#Assignment.find(self.node_object_id).directory_path
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.directory_path
end

# Gets the created_at from the associated object
def get_creation_date
#Assignment.find(self.node_object_id).created_at
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.created_at
end

# Gets the updated_at from the associated object
def get_modified_date
#Assignment.find(self.node_object_id).updated_at
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.updated_at
end
end
</pre>

== Performance Improvement==
Originally there are 13 queries after loading these related pages, and now there are only 5 of them, as can been seen from the console output result below. Thus the performance is improved and the total rendering time consumption is reduced.
[[File:after_modify.png|center]]

==References==
<references/>

CSC/ECE 517 Spring 2015/oss E1510 FLP

2015-03-24T01:30:02Z

Sniu: /* _row_header.html.erb] and assignment_node.rb */

Expertiza - Fix Instructor Login Performance Issue 

Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub]</ref>
__TOC__

==Project Description==
Currently when an Instructor logs into Expertiza,there are a lot of select* from assignments queries being fired on database which would have an adverse effect on performance. We analyzed the source of this issue and made some changes, which reduced the number of select queries executed. The performance is high improved.
The mission involved is tracing the source of the issue and modify the code to fix the issue.

===Performance issue before modification===
Before the improvement is achieved, each time an instructor logs into Expertiza, there would be several database queries, which are more than needed and take more time to render the view. Below is the console outputs when an instructor logs in.

[[File:before_modify.png|center]]

we can see that there are 7 assignment queries after load <code>_row_header.html.erb</code>, 3 assignment queries after load <code>_shared_actions.html.erb</code>, 3 assignment queries after load <code>_assignments_actions</code>. All of these queries are same.These duplicate queries have an adverse effect on the performance.

==Locate source of issues==
To locate the files that generate the duplication of queries, we use a Gem called QueryReviewer<ref>https://github.com/nesquena/query_reviewer</ref> to help trace the datebase queries. QueryReviewer is an advanced SQL query analyzer<ref>https://github.com/nesquena/query_reviewer</ref>. It accomplishes the following goals:
* View all <code>EXPLAIN</code> output for all <code>SELECT</code> queries to generate a page
* Rate a page's SQL usage into one of three categories: <code>OK, WARNING, CRITICAL</code>
* Attach meaningful warnings to individual queries, and collections of queries
* Display interactive summary on page
===Install query_reviewer===
Installing query_reviewer is simple. All you have to do to install it into your Rails 2 or 3 project is

<pre>
gem install query_reviewer
</pre>

Right now if you use bundler, simply add this to your <code>Gemfile</code>:

<pre>
# Gemfile
gem "query_reviewer"
</pre>

or to use the latest from github:
<pre>
# Gemfile
gem "query_reviewer", :github => "nesquena/query_reviewer"
</pre>

After installing and running this Gem on the Rails application, it would pop-up database query information on the webpage, as is shown below.

[[File:Query_Reviewer.jpg|center]]

We can thus follow the trace of this query reviewer page, and locate the source of the issue in <code>assignment_node.rb</code>, also the source code in <code>_assignment_action.html.erb</code>

===Analyze code===
We log into Expertiza as an instructor with the QueryReviewer activate and watch the output of QueryReviewer. The above figure shows the tracing result of the QueryReviewer and it tells us that we should pay more attention to the three files: assignment_node.rb, _row_header.html.erb and _entry.html.erb.
==== [https://github.com/fwu8/expertiza/blob/master/app/views/tree_display/actions/_assignments_actions.html.erb <code>_assignment_actions.html.erb</code>] ====
In file <code>_assignment_actions.html.erb</code>, we can find in 3 places use <code>Assignment.find(node.node_object_id)</code>, which is actually a database query request.
<pre>
1 <% owner_id = Object.const_get('Assignment').find(node.node_object_id).instructor_id %>
...
11 <% @assignment = Assignment.find(node.node_object_id) %>
...
52 <% if Assignment.find(node.node_object_id).course_id %>
...
</pre>

==== <code>_row_header.html.erb</code>] and <code>assignment_node.rb</code> ====
In [https://github.com/fwu8/expertiza/blob/master/app/views/tree_display/_row_header.html.erb <code>_row_header.html.erb</code>]:
<pre>
26 <% if parent_node.get_name == 'Courses'&& session[:user].role_id == 6 %>
27 <%else%>
28 <%= parent_node.get_name %>
29 <% if parent_node.get_directory != nil%>
30 Directory: <%= parent_node.get_directory %>
31 <% end %>
32 <% if parent_node.get_creation_date != nil %>
33 Creation Date: <%= parent_node.get_creation_date %>
34 <% end %>
35 <% if parent_node.get_modified_date != nil %>
36 Updated Date: <%= parent_node.get_modified_date %>
37 <% end %>
38 <%end%>
</pre>
we can see in this view, <code>parent_node</code> is a <code>AssignmentNode</code> object, it execute:
* <code>parent_node.get_name</code> method
* <code>parent_node.get_directory</code> method
* <code>parent_node.get_creation_date</code> method
* <code>parent_node.get_modified_date</code> method
However, in [https://github.com/fwu8/expertiza/blob/master/app/models/assignment_node.rb <code>assignment_node.rb</code>]:
<pre>
6 class AssignmentNode < Node
...
58 # Gets the name from the associated object
59 def get_name
60 Assignment.find(self.node_object_id).name
61 end
62
63 # Gets the directory_path from the associated object
64 def get_directory
65 Assignment.find(self.node_object_id).directory_path
66 end
67
68 # Gets the created_at from the associated object
69 def get_creation_date
70 Assignment.find(self.node_object_id).created_at
71 end
72
73 # Gets the updated_at from the associated object
74 def get_modified_date
75 Assignment.find(self.node_object_id).updated_at
76 end
...
82 end
</pre>
We find all these method called <code>Assignment.find(self.node_object_id)</code> method, which is actually a database query request. These 'find's are actually redundant for a specific Assignment instance. So we will figure out a way to eliminate those redundant method calls.

==Modifications==

===_assignment_actions.html.erb===
An instance variable <code>@assignment</code> is used here instead of multiple times of calling <code>.find</code> method, thus reducing database queries.
<pre>
+ <% @assignment = Assignment.find(node.node_object_id) %>
- <% owner_id = Object.const_get('Assignment').find(node.node_object_id).instructor_id %>
+ <% owner_id = @assignment.instructor_id %>
...
- <% @assignment = Assignment.find(node.node_object_id) %>
...
- <% if Assignment.find(node.node_object_id).course_id %>
+ <% if @assignment.course_id %>
...
</pre>

===assignment_node.rb===
In this class, we define a new variable <code>@assign_node</code>, and in every <code>get_</code> method, instead of using <code>Assignment.find(self.node_object_id)</code> to find the AssignmentNode object, we first search if <code>@assign_node</code> variable exist, if not, we define <code>@assign_node = Assignment.find(self.node_object_id)</code>, else we directly use <code>@assign_node</code>. Because <code>_row_header.html.erb</code> file has many <code>get_</code> method, after modification, the number of assignment queries decreases much.
<pre>
class AssignmentNode < Node
# Gets the name from the associated object
def get_name
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.name
end

# Gets the directory_path from the associated object
def get_directory
#Assignment.find(self.node_object_id).directory_path
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.directory_path
end

# Gets the created_at from the associated object
def get_creation_date
#Assignment.find(self.node_object_id).created_at
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.created_at
end

# Gets the updated_at from the associated object
def get_modified_date
#Assignment.find(self.node_object_id).updated_at
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.updated_at
end
end
</pre>

== Performance Improvment==
Originally there are 13 queries after loading these related pages, and now there are only 5 of them, as can been seen from the console output result below. Thus the performance is improved and the total rendering time consumption is reduced.
[[File:after_modify.png|center]]

==References==
<references/>

CSC/ECE 517 Spring 2015/oss E1510 FLP

2015-03-24T01:29:08Z

Sniu: /* _row_header.html.erb] and assignment_node.rb */

Expertiza - Fix Instructor Login Performance Issue 

Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub]</ref>
__TOC__

==Project Description==
Currently when an Instructor logs into Expertiza,there are a lot of select* from assignments queries being fired on database which would have an adverse effect on performance. We analyzed the source of this issue and made some changes, which reduced the number of select queries executed. The performance is high improved.
The mission involved is tracing the source of the issue and modify the code to fix the issue.

===Performance issue before modification===
Before the improvement is achieved, each time an instructor logs into Expertiza, there would be several database queries, which are more than needed and take more time to render the view. Below is the console outputs when an instructor logs in.

[[File:before_modify.png|center]]

we can see that there are 7 assignment queries after load <code>_row_header.html.erb</code>, 3 assignment queries after load <code>_shared_actions.html.erb</code>, 3 assignment queries after load <code>_assignments_actions</code>. All of these queries are same.These duplicate queries have an adverse effect on the performance.

==Locate source of issues==
To locate the files that generate the duplication of queries, we use a Gem called QueryReviewer<ref>https://github.com/nesquena/query_reviewer</ref> to help trace the datebase queries. QueryReviewer is an advanced SQL query analyzer<ref>https://github.com/nesquena/query_reviewer</ref>. It accomplishes the following goals:
* View all <code>EXPLAIN</code> output for all <code>SELECT</code> queries to generate a page
* Rate a page's SQL usage into one of three categories: <code>OK, WARNING, CRITICAL</code>
* Attach meaningful warnings to individual queries, and collections of queries
* Display interactive summary on page
===Install query_reviewer===
Installing query_reviewer is simple. All you have to do to install it into your Rails 2 or 3 project is

<pre>
gem install query_reviewer
</pre>

Right now if you use bundler, simply add this to your <code>Gemfile</code>:

<pre>
# Gemfile
gem "query_reviewer"
</pre>

or to use the latest from github:
<pre>
# Gemfile
gem "query_reviewer", :github => "nesquena/query_reviewer"
</pre>

After installing and running this Gem on the Rails application, it would pop-up database query information on the webpage, as is shown below.

[[File:Query_Reviewer.jpg|center]]

We can thus follow the trace of this query reviewer page, and locate the source of the issue in <code>assignment_node.rb</code>, also the source code in <code>_assignment_action.html.erb</code>

===Analyze code===
We log into Expertiza as an instructor with the QueryReviewer activate and watch the output of QueryReviewer. The above figure shows the tracing result of the QueryReviewer and it tells us that we should pay more attention to the three files: assignment_node.rb, _row_header.html.erb and _entry.html.erb.
==== [https://github.com/fwu8/expertiza/blob/master/app/views/tree_display/actions/_assignments_actions.html.erb <code>_assignment_actions.html.erb</code>] ====
In file <code>_assignment_actions.html.erb</code>, we can find in 3 places use <code>Assignment.find(node.node_object_id)</code>, which is actually a database query request.
<pre>
1 <% owner_id = Object.const_get('Assignment').find(node.node_object_id).instructor_id %>
...
11 <% @assignment = Assignment.find(node.node_object_id) %>
...
52 <% if Assignment.find(node.node_object_id).course_id %>
...
</pre>

==== <code>_row_header.html.erb</code>] and <code>assignment_node.rb</code> ====
In [https://github.com/fwu8/expertiza/blob/master/app/views/tree_display/_row_header.html.erb <code>_row_header.html.erb</code>]:
<pre>
26 <% if parent_node.get_name == 'Courses'&& session[:user].role_id == 6 %>
27 <%else%>
28 <%= parent_node.get_name %>
29 <% if parent_node.get_directory != nil%>
30 Directory: <%= parent_node.get_directory %>
31 <% end %>
32 <% if parent_node.get_creation_date != nil %>
33 Creation Date: <%= parent_node.get_creation_date %>
34 <% end %>
35 <% if parent_node.get_modified_date != nil %>
36 Updated Date: <%= parent_node.get_modified_date %>
37 <% end %>
38 <%end%>
</pre>
we can see in this view, <code>parent_node</code> is a <code>AssignmentNode</code> object, it execute:
* <code>parent_node.get_name</code> method
* <code>parent_node.get_directory</code> method
* <code>parent_node.get_creation_date</code> method
* <code>parent_node.get_modified_date</code> method
However, in <code>assignment_node.rb</code>:
<pre>
6 class AssignmentNode < Node
...
58 # Gets the name from the associated object
59 def get_name
60 Assignment.find(self.node_object_id).name
61 end
62
63 # Gets the directory_path from the associated object
64 def get_directory
65 Assignment.find(self.node_object_id).directory_path
66 end
67
68 # Gets the created_at from the associated object
69 def get_creation_date
70 Assignment.find(self.node_object_id).created_at
71 end
72
73 # Gets the updated_at from the associated object
74 def get_modified_date
75 Assignment.find(self.node_object_id).updated_at
76 end
...
82 end
</pre>
We find all these method called <code>Assignment.find(self.node_object_id)</code> method, which is actually a database query request. These 'find's are actually redundant for a specific Assignment instance. So we will figure out a way to eliminate those redundant method calls.

==Modifications==

===_assignment_actions.html.erb===
An instance variable <code>@assignment</code> is used here instead of multiple times of calling <code>.find</code> method, thus reducing database queries.
<pre>
+ <% @assignment = Assignment.find(node.node_object_id) %>
- <% owner_id = Object.const_get('Assignment').find(node.node_object_id).instructor_id %>
+ <% owner_id = @assignment.instructor_id %>
...
- <% @assignment = Assignment.find(node.node_object_id) %>
...
- <% if Assignment.find(node.node_object_id).course_id %>
+ <% if @assignment.course_id %>
...
</pre>

===assignment_node.rb===
In this class, we define a new variable <code>@assign_node</code>, and in every <code>get_</code> method, instead of using <code>Assignment.find(self.node_object_id)</code> to find the AssignmentNode object, we first search if <code>@assign_node</code> variable exist, if not, we define <code>@assign_node = Assignment.find(self.node_object_id)</code>, else we directly use <code>@assign_node</code>. Because <code>_row_header.html.erb</code> file has many <code>get_</code> method, after modification, the number of assignment queries decreases much.
<pre>
class AssignmentNode < Node
# Gets the name from the associated object
def get_name
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.name
end

# Gets the directory_path from the associated object
def get_directory
#Assignment.find(self.node_object_id).directory_path
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.directory_path
end

# Gets the created_at from the associated object
def get_creation_date
#Assignment.find(self.node_object_id).created_at
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.created_at
end

# Gets the updated_at from the associated object
def get_modified_date
#Assignment.find(self.node_object_id).updated_at
unless @assign_node
@assign_node = Assignment.find(self.node_object_id)
end
@assign_node.updated_at
end
end
</pre>

== Performance Improvment==
Originally there are 13 queries after loading these related pages, and now there are only 5 of them, as can been seen from the console output result below. Thus the performance is improved and the total rendering time consumption is reduced.
[[File:after_modify.png|center]]

==References==
<references/>