CSC/ECE 517 Spring 2017/E1731 Improve Score Calculation: Difference between revisions
(Created the page with expertiza introduction) |
(→Problem Description: Current Scenario and Proposed Solution added) |
||
| Line 5: | Line 5: | ||
==Problem Description== | ==Problem Description== | ||
===Current Scenario=== | |||
Expertiza store the scores based on each response to each criterion, but no holistic scores are stored. The answers table only contains the score that A gives B on each criterion. This means that if we need to know what score user A gives to user B based on 100, we have to rely on the code to calculate it every time the scores are requested. This design slows down Expertiza as every time instructor clicks on "View Scores", all the calculations are done to display the score. The situation is even worse if we want to weight the scores by the reputation of each reviewer, which is a measure of how closely that reviewer's scores match other reviewers. The system potentially has to do thousands of arithmetic calculations to display the score for a particular assignment. | |||
===Proposed Solution=== | |||
We propose that we have two mechanism to handle holistic scores, depending on the current state of the assignment: | |||
* OnTheFlyCalc: Calculates holistic scores over a set of data: A set of records in answers table, namely the responses from user A to user B on each criterion. | |||
** When an assignment is still ongoing, the reputations for each reviewer will be calculated and handled by OnTheFlyCalc. | |||
* LocalDBCalc: Calculates the holistic score over a single db query: "get the score that user A gives user B on assignment 999 on round 2" | |||
** When an asignment has finished, all the reputations will be calculated by LocalDBCalc and stored, since they are finalized. So, when the scores are requested, it is fetched using a single db query and displayed. | |||
In this project, our goal is to make the OnTheFlyCalc and LocalDBCalc work for peer-review scores only, by making sure the code is extensible for further work. | |||
==Design Plan== | ==Design Plan== | ||
Revision as of 22:50, 6 April 2017
Introduction
Expertiza is an opensource web based platform developed to assist students in educational institutions to perform peer reviews and group projects. The reviewing is done through a mechanism where students will be sent request to review work and the system will analyze and publish a summarized report. The software is designed in MVC (Model-View-Controller) architecture using ruby on rails.
Problem Description
Current Scenario
Expertiza store the scores based on each response to each criterion, but no holistic scores are stored. The answers table only contains the score that A gives B on each criterion. This means that if we need to know what score user A gives to user B based on 100, we have to rely on the code to calculate it every time the scores are requested. This design slows down Expertiza as every time instructor clicks on "View Scores", all the calculations are done to display the score. The situation is even worse if we want to weight the scores by the reputation of each reviewer, which is a measure of how closely that reviewer's scores match other reviewers. The system potentially has to do thousands of arithmetic calculations to display the score for a particular assignment.
Proposed Solution
We propose that we have two mechanism to handle holistic scores, depending on the current state of the assignment:
- OnTheFlyCalc: Calculates holistic scores over a set of data: A set of records in answers table, namely the responses from user A to user B on each criterion.
- When an assignment is still ongoing, the reputations for each reviewer will be calculated and handled by OnTheFlyCalc.
- LocalDBCalc: Calculates the holistic score over a single db query: "get the score that user A gives user B on assignment 999 on round 2"
- When an asignment has finished, all the reputations will be calculated by LocalDBCalc and stored, since they are finalized. So, when the scores are requested, it is fetched using a single db query and displayed.
In this project, our goal is to make the OnTheFlyCalc and LocalDBCalc work for peer-review scores only, by making sure the code is extensible for further work.