Faculty Info System
Dean Merritt and the CSIS Department would like to have an application that
tracks current and prospective faculty information.
The project will involve the creation of a Web interface and a backend database.
The software used will be Microsoft SQL Server for the database, and Fusebox and Cold Fusion for the Web interface.
This software is supported by DoIT and the CSIS Technical Support Team.
Requirements Document (Paulette Muller-Girard, 9/30/03)
The purpose of the Prospective Faculty Application is to allow people
who would like to teach at the Pace School of Computer Science and Information Systems
to apply for a position by filling out a form on the Internet.
The Prospective Faculty Application should capture all the information necessary to:
The School of CSIS already has in prodcution two databases maintaining similar information
concerning faculty and staff who have already been hired.
The Prospective Faculty Application will build upon the existing data structures and web site,
adding only those elements that are necessary to extend the functionality of the existing web site.
- contact the prospective faculty
- evaluate the credentials of the prospective faculty
- track the evaluation and hiring process
- track and upload scanned copies of documents related to the application
- categorize applicants by type and active status
More specifically, The following functionality is requested:
- Obtain basic contact information from a prospective applicant allowing him/her
to set up an account for entering further details of their application.
Since the application may be lengthy, the applicant must be able
to come back to their application to edit information
- The applicant should be able to signify when their application is ready to be considered/complete/submitted.
- The applicant should be able to signify that they no longer want their application to be considered.
This implies the interface must allow an applicant to return after an application is fully submitted
and change application details.
When details of a fully submitted application are changed CSIS application reviews must be notified.
The system should flag faculty applications that have been changed.
- Applicants can elect to have their application be considered for full time or part time positions, or both.
- If the application is for a part time, adjunct position,
the applicant should be aple to signify specific time periods when they are available to teach.
- If the applicant is interested in a full time position, the applicant
should be able to indicate when they could begin teaching.
- Those CSIS faculty and staff who have access to review prospective faculty applications
should have a means of emailing the prospective faculty through the web interface.
- To be considered, an applicant must provide information
on all previous teaching experience which inlcudes, among others:
- courses taught
- level: graudate, undergraduate, other
- Applicants should also provide information about their specific skills, such as programming languages,
certifications, or additional professional qualifications
- An administrative interface to the applications which:
- Defines which CSIS faculty and staff can see which applications and their related materials
- Allows application reviewers to:
- email applicants individually or as a group
- categorize applicants by:
- what Pace courses they are qualified to teach
- what subject categories they are qualified to teach
- what department they can teach in
- Contains an email log of correspondence sent through the interface to the prospective faculty
- Contains a document repository of scanned copies of all supporting documents received concerning the applicant
- Contains comments concerning the evaluation of the applicant
- Allows appropriate CSIS faculty / staff to change the activity status of the applicant
The existing (and planned ) web site uses Cold Fusion and Fusebox.
For more information see
The backend databases reside on a Microsoft SQL Server 2000 instance.
All database changes (adding or altering structures) must be modeled in an Entity Relionship Diagram model.
The ERD must be approved by the Database Administrator prior to implementation.
The logical flow of the application must be documented via a Wireframe document, see
A thorough unit test script must be created for all web pages.