Course Scheduler

Team Members

• Alex Baca
• Alicia Bargar
• Phil Lisovicz
• Richard Marmorstein

• Requirements
• Design Plan
• Work Plan

• Part 1 – choose preferred courses
• Part 2 – schedule creator

Corsola Statistics

• Good implementation of preliminary functionality
  • some kinks, but that's what you're trying to find and figure out – what works and what doesn't and better approaches
• Working with the data is important, so it's good that you have all the data in the database
• Seems like you have a pretty clear idea of the next steps and what needs to get done

• In your documentation, please let me know how to get the data from the Registrar to the DB for your application so I can make sure the application works for future terms
  • What are your steps? Do you have scripts you used? Add all of this to the Subversion repository, e.g., in a scripts directory
• Instead of having the DB parameters in several classes, put the parameters in the web.xml and use a ServletContextListener to get that information and set up the DB connection pool
• On your about page, add links to your web pages and/or Linked in profiles or whatever you want to increase your page rank
• Include a page for recognizing the code you used–let's help those folks increase their page ranks.
• Make sure all the pages that you do not want a user to directly access (e.g., responses to Servlets) are in the WEB-INF directory

• Explanations/feedback/instructions for what the groups mean
• Dependence between courses? – I want this _and_ this course
• The Login form should submit a post, not a get request

Rather than a stand-alone web application, Richard Marmorstein developed a Chrome extension that leverages the student developers' code to allow students to visualize their schedules.