CSC/ECE 517 Fall 2018/E1856 Allow reviewers to bid on what to review: Difference between revisions
(→Models) |
|||
| Line 1: | Line 1: | ||
== Description == | == Description == | ||
Students | |||
Students currently are able to “bid” for the projects that they want to do as an assignment. On the other hand, for reviewing others’ work, the policy that’s currently in use is called “first-come-first-serve”. | |||
In this project, we update the “first-come-first-serve” policy for assigning projects to reviewers, to the “bidding” policy. In the backend, we implement the “top trading cycles” algorithm. And we modify the controller to meet the needs of the algorithm. At the front end, we create an UI design to present to the students their choices to select. | |||
== Introduction == | == Introduction == | ||
Revision as of 19:54, 13 November 2018
Description
Students currently are able to “bid” for the projects that they want to do as an assignment. On the other hand, for reviewing others’ work, the policy that’s currently in use is called “first-come-first-serve”.
In this project, we update the “first-come-first-serve” policy for assigning projects to reviewers, to the “bidding” policy. In the backend, we implement the “top trading cycles” algorithm. And we modify the controller to meet the needs of the algorithm. At the front end, we create an UI design to present to the students their choices to select.
Introduction
Current System Status
Regarding to the functionality of review mapping, it's necessary to describe some of the related models and controllers in expertiza and how they are organized to fully implement the functionality.
Models
When an assignment is released, an instance of Assignment is created and corresponding topic instances of SignUpTopics are also imported, indicating that different topics are available for students to choose from within this assignment.
Design
Almost all of the functionality for our project has already been implemented in the review portions of the Expertiza system. Because of this, we will approach this project by first using a decorator pattern to add lottery capability to the review mapping controller for choosing topics. Then we will duplicate the view for choosing project topics and modify it so that it interacts with the review mapping controller. We understand that this is not DRY code, so we will try to address this problem by seeing if there is any way we can modify the choose project topics page in order to reuse its code, yet still fulfill the functionality of review mapping.
Implementation
Challenges
Testing
Design Patterns
Model View Controller - Expertiza uses the Ruby on Rails framework which is set up to use the Model View Controller software pattern.
DRY Principle - We will be attempting to write our code in a dry way, that being that code within the system is not duplicated.