Web Based Student Registration System ECE 345 Design Project

Gary Chen and Otto Lee

Project Proposal TA: Ajay Patel September 15, 1999

Introduction The goal of this project is to provide a readily accessible and user-friendly system for students to register for classes. This would be similar to the current U of I Direct system, but it will also feature the following advantages. 1) As a webbased system, students will be able to have access from any computer that has a web browser and is connected to the Internet. 2) With a graphical interface, this system will be more user-friendly and intuitive to use. The introduction of on-line registration was an enormous improvement over the old, cumbersome paper-based method. In much the same way, we hope our web-based system will improve over the current text-based, esoteric U of I Direct. Project Goals and Intended Functions Our web-based system will have the following functionality: Students can access the system using any computer connected to the Internet and equipped with a web browser. Once they are logged in, they can add, drop, and exchange classes. They can also view their weekly schedule in tabular form. A campus map will be displayed detailing the location of each of their classes. A counter will also be displayed indicating how many hours left a student has before completing his/her graduation requirements. Administration would also be able to make changes to the registration database, and they will be able to place stipulations on registration, particularly adjusting the maximum credit hours a student can take.

Block Diagram Username and Password Page

Student Schedule

Student Registration Page

Campus Map

Back-End Database

Performance Requirements Rather than using the actual U of I database for our system, we will create a small mock database to demonstrate how our system works. The main indicator of performance will be the functionality, reliability, and stability of our system. Testing Procedures The most practical test for our system will be to have a tester use all its functions while trying to register for classes. Cases and stipulations to test for: Students registration is protected by a login and password. Students choice of classes have been accurately recorded/updated in the system database. Students cant register for classes not offered that semester. Students cant register for two classes that meet at the same time. Students cant go over 18 hours. Students cant register for a class thats full. Map correctly depicts the locations of the students classes. Weekly schedule accurately shows the students schedule. Hours-Remaining counter works accurately.

Schedule

11/01/99 11/08/99 11/15/99 11/22/99 11/29/99 12/06/99 12/13/99

Connect individual circuits together to test and debug the entire Testing and debugging Begin final report and Presentation Thanksgiving Vacation Project demo and oral report, finish final written report Final report due

WEEK OF 9/13/99 9/20/99 9/27/99 10/04/99 10/11/99 10/18/99

TASKS TO BE COMPLETED Submit Proposal Research, obtain, and set-up required software. Investigate hardware options. Design basic interface. Sign up for Design Review. Continue designing interface. Create mock courses and students. Create campus map. Create weekly class schedule table.

10/25/99 11/01/99 11/08/99 11/15/99 11/22/99 11/29/99 12/6/99 12/13/99 Special Circuit

Design and implementation of database Design and implementation of database Design and implementation of database Connect database with interface. Test and debug. Thanksgiving Vacation Demo and Presentation. Final Report

We will design, assemble, and test, a small-signal low-frequency (<100kHz) amplifier circuit with specifications to be given by the TA.

Cost Labor $40/hour x 2.5 x 120 hours x 2 partners = $24,000 Parts Computer for server Web Server software Database system Parts subtotal Labor subtotal Project total $2,000 $500 $250 $2,750 $24,000 $26,750