System Requirements Specifications
Career Fair Registration System
1. Introduction
1.1 Purpose
The purpose of this document is to identify and outline the requirments for designing a web page interface to manage Career Fair Registration. The web interface will also be accessible by students to search through the companies attending the Career Fair, as well as an administrative interface to edit entries submitted by companies.
1.2 Project Description
1.2.1 Description
The Career Fair Registration System will be an upgrade to the current web interface. As the system is set up now, companies can enter limited information into a web page. The information is then sent to Jan Ford, the director of career services, to be compiled and edited by hand before finally going into a career fair booklet. The new system will do as much as possible to automate much of this process, and make everything easier for everyone involved, plus adding the new ability for students to be able to search through the company list to choose companies that interest them easily.
1.2.2 Scope
The current system in place is a CGI (common gateway interface) web page that simply emails the information submitted to Jan Ford. The new system will use ASP (active server pages) to interface to an online database, storing all the information to be searched through and even printed out into a career fair booklet in the end. The new program will most likely only be used for the Rose-Hulman career fair registration, although it could be modified slightly to be used for other similar projects if necessary. The context diagram for this project can be found in figure 1.2.2a.
· Figure 1.2.2a Context Diagram for the Career Fair Registration System.
2. Data Model
2.1 Considerations
The web interface will collect specific bits of information from each company that submit information into the database. The information collected includes:
· Company name
· Company address
· Company web site
· Any number of company representatives, along with each representatives job position and tee-shirt size
· List of majors the company is seeking to employ
· Type of employment (Co-op, Internship, or Full Time)
· A description of the company
· An optional image file for a logo of the company
The information and the relationships between them may be observed in figure 2.2a, the the Entity Relationship Diagram for the Career Fair Registration System.
2.2 Entity Relationship Diagram (ERD)
· Figure 2.2a Entity Relationship Diagram for the Career Fair Registration System
2.3 Requirements
All the web page programming is being done using ASP. The requirements for running these pages are any web site that supports ASP, which unfortunately the Rose Hulman web server does not. The new career fair registration system will have to be stored on a different web site until such a time that it may be moved onto the Rose Hulman system. The only requirements other than web space is for the site to be used by companies to input their information to register for the career fair, and for an administrator to review this information for incorrect or inappropriate information. The web interface will allow companies to add information directly into the database, to be later checked by an administrator.
3. Process Model
3.1 Considerations
When fully implemented, the system will not require any technical maintenance—the web interface will be all that is necessary to update the database. The only consideration is that this system cannot currently be implemented on the Rose-Hulman web site. The companies may submit data, including a password so that they can edit their information later if needed. The students may only view or search through the database. The administrator may view and search the database, and can change any entry in the database, or delete any entry.
3.2 Data Flow Diagram (DFD)
· Figure 3.2a Data Flow Diagram for Career Fair Registration System
4. Revised Plans
4.1 Remaining Phases
The remaining phases for the enhancement project are: design for several pages, connecting the pages to the database, a second prototype, debugging, testing, and completion. Below is the projected time schedule to finish these remaining phases.
4.2 Schedule
This is a rough estimate that may be subject to change as the problem is analyzed further. Refer to Figure 4.2a for a more detailed breakdown of the revised schedule.
|
Phase |
Estimated Time for Completion |
|
Design |
2-3 weeks |
|
Prototype and implementation |
2 weeks |
|
Connecting to Database |
2-3 weeks |
|
Debugging, testing, and completion |
4 weeks |
· Figure 4.2a Estimated Times for Phase Completions
5. Conclusion
5.1 Summary
The project as a whole will save a lot of time and trouble when compared to the system as it stands. The new system will automate many of the processes taking place now, and even be used to gather the information to print out the career fair booklet when all companies have registered. The site may be extended with more ASP pages to expand the usefulness of this site at a later date if required, and the database can be saved for use in future career fairs. In this way, companies that have already entered in information will just be able to visit their page and resubmit the same data, making any corrections necessary. In the end, this will be a very time saving system that is easy to use for non-technical users.
5.2 Conclusion and Recommendation
For
our group, this project may be too large to finish in the given time
constraints. The project should easily
be able to be completed during the next academic quarter, pending any serious
problems. It is therefore our
recommendation that this project be continued during the next quarter.
5.3 Contacts
Team 99:
Student 1 (student1@rose-hulman.edu)
Student 2 (student2@rose-hulman.edu)
Student 3 (student3@rose-hulman.edu)