1 / 11

Team 5 Chemical Engineering Lab Scheduler

Team 5 Chemical Engineering Lab Scheduler. Zach Frichtl Brent Ellwein Ryan Poplin Shawn Windler Chris Ciscsko Erik Halvorson Ben Linden. Introduction. Our Project Web Interface Administrator Interface Scheduler Testing. Our Project. Chemical Engineering Lab Scheduler

hahnt
Download Presentation

Team 5 Chemical Engineering Lab Scheduler

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Team 5Chemical Engineering Lab Scheduler Zach Frichtl Brent Ellwein Ryan Poplin Shawn Windler Chris Ciscsko Erik Halvorson Ben Linden

  2. Introduction • Our Project • Web Interface • Administrator Interface • Scheduler • Testing

  3. Our Project • Chemical Engineering Lab Scheduler • Lab Sequence Junior/Senior Years • 7 Labs • Groups of 3 or 4 • Schedule Done by Hand

  4. Web Interface • Allow students to form groups • Allow faculty to specify lab preferences • Allow both to view schedule • Demo

  5. Administrator Interface • Control running of the scheduling algorithm. • View the scheduled labs and groups. • Modify and Add users. • Student • Faculty • Administrator • Modify and Add Labs to be scheduled. • Change the equipment list by adding or modifying equipment

  6. Scheduler • Logistical Complexity • Runtime Considerations • Optimal Solution • Three Phase Scheduler • Instructors to Labs • Students to Labs • Labs to Time

  7. Test Plan • Validation Test Plan • Requirements Specification Document • 88 total test cases • Integration Test Plan • Design Document • 26 total test cases • Unit Test Plan

  8. 2.2.3.2 Error checks the submitted fields for selecting lab preferences.  Reposting the preference screen if any conflicts are found. OK:  All information is properly filled out. Preferences are updated in the database. ERROR: No labs are selected more than once. A preference grade is not given to a lab.  Validation Test Case

  9. 6.1.0  Tests communication between the Admin Main page module / schedule modifier, and the database.  OK:  A preference is given by selecting a radio button for each lab / Connection to the database is made, the username of the faculty member, and a series of numbered preferences is then sent to the database, Connection to the database is ended. ERROR: Information is not received by the database : database server is down. Information is not received by the database : info is never sent out by the preference picker script. Integration Test Case

  10. Conclusion • Our Project • Web Interface • Administrator Interface • Scheduler • Testing

  11. Questions

More Related