System Requirements Specifications
Career Fair Online Registration System
1. Introduction
1.1 Purpose
The purpose of this document is to define and make clear the requirements for modifying the existing Career Fair Online Registration System (CFORS). This document will also display how data will flow through the system, and how entities will interact with that data.
1.2 Project Description
1.2.1 Current System
The career fair online registration system offers companies a paper free way to register for the annual Rose Hulman career fair. Currently, the system takes input over the web, and e-mails that information to the associate director of career services (ADCS), currently Jan Ford. The ADCS then compiles this information manually to create the career fair booklet.
1.2.2 Scope
Our modifications will not increase the scope of this system from a user’s perspective because we are only modifying the way that the data is processed. Our modifications will add complexity to the back end of the project, but hopefully will reduce the time commitment of the ADCS.
· Figure 1.2.2a: Context Diagram for CFORS
1.2.3
Proposed System Improvement Objectives
The system that we are proposing will ease the workload and save time for the ADCS. The project team proposes the following improvements to accomplish this:
· To eliminate all the e-mails currently being sent to the ADCS, the new system will input each company’s information into an Oracle database.
· Currently there is no way for a company to view or modify the information that they submitted in the registration process. The new system will e-mail a user name and password to the company so that they may view or modify existing information in the database online. There will also be an administrator webpage allowing the administrator to view or modify existing information stored in the database.
· At this time, the ADCS has to manually organize the information into a career fair booklet. The proposed system will be able to take the information and generate dynamic online reports of the submitted information concerning the company.
· The existing system does not have a method for students to search or view which companies will be coming to the Rose Hulman career fair. The new system will allow students to search the database for the companies attending. Students may be able to search for companies by name, majors usually hired, location, and type of candidate hired (intern/co-op/full time).
· The new system will be flexible enough to allow easy cusomization for other future fairs.
For a visual overview of how the new system fits in, see figure 1.2.2a
2. Data Model
2.1 Web Front End
The web based front end will allow companies to input information in an online form, however, it will not be required to store that information. Rather, a CGI script will send the information to an Oracle database. Likewise, when users make a request for information using the web, a CGI script will retrieve the specified information from the database and display it. Therefore, the web interface has no data storage responsibilities.
2.2 Database Back End
· Figure 2.2a ER Diagram of the Oracle Tables
The Oracle database will provide a single consistent place to store the system’s data. The representation of that data is quite simple (as shown in figure 2.2a). Only two tables will be required, a company table and a representatives table.
The company table will contain the majority of the information, including but not limited to the following:
· Company Contact Information (address, phone, e-mail, etc.)
· Majors Usually Hired
· Positions Currently Open
· Brief Company Description
· Number of Representatives Attending the Fair
The representatives table will contain mappings between individual companies and the representatives that they are sending. The representatives table will also contain each representative’s name, position, and T-shirt size.
3. Process Model
3.1 Data Flow
Diagram (DFD)
· Figure 3.1a: Data Flow Diagram for CFORS
The above figure, figure 3.1a, shows how data will move throughout the system. Central to all operations is the Oracle database. All user access is through web pages. Labels on links refer to the type of data being transferred.
3.2 Requirements
Thus far, the project team has a database at its disposal. They have also modified the old HTML files from the old registration page for the new page. It is necessary that the team write several CGI scripts for the project. They will need to write scripts for the administration page, the registration pages, and the student search page.
4. Revised Plans
4.1 Remaining Phases
Design, prototype and implementation, debugging, testing, and completion are the remaining phases for this enhancement project. Following is the projected time schedule to finish these remaining phases.
4.2 Schedule
Figure 4.2a describes the amount of time to be devoted in
order to complete each phase of the project.
The table also describes how much time has been devoted to the project
thus far.
|
Phase |
Estimated Time for
Completion |
Estimated
Man-Hours |
Actual Man Hours |
Status |
|
Brainstorming / Feasibility Proposal |
2
weeks |
8 |
7.5 |
Completed |
|
Analysis / Learn Tools |
2
weeks |
25 |
24 |
Completed |
|
Design |
5
weeks |
100 |
6 |
Active |
|
Prototype and Implementation |
5
weeks |
100 |
6 |
Active |
|
Debugging, Testing, and Completion |
2
weeks |
10 |
N/A |
Planned |
|
TOTAL |
16
weeks |
243 |
43.5 |
N/A |
· Figure 4.2a Estimated and Actual Times for Phase Completions
5. Conclusion
5.1 Summary
The current Rose Hulman Career Fair Registration System is a useful system, however, it is inefficient for the ADCS. The proposed system will alleviate the amount of time required for the associate director of career services to assemble a career fair booklet. This system will also allow students to search for companies attending the fair via the web. Another useful feature will be the addition of an administration page for easy access and modification of company information.
5.2 Conclusion and Recommendation
In conclusion, for a group of three students, this is a feasible project to complete. We believe that the features described in the summary are an excellent way of improving the registration process for the career fair. A separate database should also be allocated to the career services department for this system. The project team also recommends continued interaction with the ADCS to ensure that the system will meet the specifications.
5.3 Contacts
Project Team
Chris Unton (812) 232-2871 chris.unton@rose-hulman.edu Chuck Maupin (812) 877-8501 charles.maupin@rose-hulman.edu James Munafo (812) 237-0280 james.munafo@rose-hulman.edu
Career Services
Jan Ford (812) 877-8338 janice.h.ford@rose-hulman.edu