What’s the hardest part of any class? Is it the material covered? The expectations of the assignments? The assignments themselves?
And how would you figure this out? Scraping Piazza? It’d be very difficult and potentially faulty to parse through all that data. Course evals are helpful, but often very biased.
So what then? This information is extremely valuable for professors in shaping the curriculum of their course, such that they can provide the best instruction for their students. However, when an issue does occur - whether it be conceptual understanding, problem solving, or something in between - Instructors often do not have a good way of tracking specific potential issues in their course, especially over long periods of time.
We are designing N-Queue to capture issues raised during office hours and TA hours in hopes of giving instructors as much information possible regarding a central issues of a course, beyond what would be normally realized through course reviews or scraping through hundreds of piazza posts. Thus we are designing an extremely user friendly platform that will benefit students and instructors, in hopes of solving student issues faster, and helping instructors know where improvements can be made, so that issues don’t surface again.

Team

Project Manager

James Pointdexter

Electrical Engineering

jvp2@princeton.edu

Luis Gonzalez-Yante

Electrical Engineering

luisg@princeton.edu

Richard Henry

Computer Science

rh11@princeton.edu

Isaac Resendes

Computer Science

resendes@princeton.edu

Design Document

Click to Download our Design Document

Timeline

March 19

Porting to Google Clould Platform

March 26

TA View Done

April 2

Define Api's

April 16

Instructor View Done

April 23

Wiki Page Done

April 30

Front End Testing

May 7

Back End Testing