CSC/ECE 517 Spring 2022 - E2245: View for results of bidding

CSC/ECE 517 Spring 2022 - E2245: View for results of bidding

Problem Statement

When topics are opened up for bidding, students can see how “hot” each topic is by the color it has on their topic list. However, instructors have no way to view the bidding process except by impersonating students. Furthermore, when the bidding assignment algorithm is run, there is no way to verify that it did in fact assign teams to topics they had chosen.

Edit - individuals reserve before teams are formed

Soln - Use heuristics instead of an NP-complete algorithm - More weight on larger group

Project Goal

The goal of this project is to create a field for instructors on the topic list that shows how many teams have bid for each project. Since topic lines in the topic list potentially have several fields, including partner advertisements, take care that

1. the #-of-bids field is not displayed except for projects that use bidding for topics, and
2. the field is as narrow as feasible.

Emphasis is placed on the UX design to allow instructors to quickly verify that the bidding algorithm gave as many teams as possible their first choice.

Previous Work

User Cases

Design Pattern

In-progress of documenting the utilized design patterns

Improvement on the Previous Work

Change in Use Cases

Student: This actor is responsible for submitting and deleting bids for topics while the topic selection period is open for an assignment which uses the new lottery topic selection mechanism.

Instructor: This actor is responsible for updating an assignment to use the new lottery topic selection as well as closing the bidding period and beginning the automatic topic selection. Instructor is also able to view the progress details of bids without having to impersonate students

UI design

1. Option 1: Details in a popup window

1. Option2: View bidding details in a expanded/collapsed style (Preferred)

Change in Work Flow Diagram

<Flow diagram to come>

Code changes

The following files will be changed to fulfill the requirements

Controllers:

• app/controllers/sign_up_sheet_controller.rb

Models:

• app/models/bid.rb

Views:

• app/views/sign_up_sheet/list.html.erb

Rspec:

• spec/controller/sign_up_sheet_controller_spec.rb
• spec/controller/big_spec.rb

Refactor Code to follow good coding practices
Example:
1. Rename method names more meaningfully and intuitive.

Correct Previous Design

1. Remove mentors from being included in a team's number of members count.

BEFORE

AFTER

Code placed in the wrong locations to be moved to the desired locations.
Example:

1. Example here

Functionalities added

• The instructor should be able to see how many teams have bid for each topic without having to impersonate students
  

Testing

1. Some existing test cases have been modified, which have been reverted.
   
2. Run and pass the existing RSpec Tests.
   
3. Test the UI for the deployed project.
   

UI Testing

Part 1:

• Login as the instructor6
  

Part 2:

• Login as student575 (added to the program by the instructor)
  

Future Work

• If a mentor is removed from an assignment, reassignment of mentor has to be done. (edge-case)
• Rspec for email functionality needs to be implemented.

Team Roster

• Duy Nguyen - dvnguye3@ncsu.edu
  
• Kwon HyeokJun - khyeokj@ncsu.edu
  
• Shawn S - ssaleki@ncsu.edu
  
• David Glymph - dwglymph@ncsu.edu
  

Mentor: Ed Gehringer - efg@ncsu.edu

Reference

Previous Work