A SAMPLE PROJECT PROPOSAL

Introduction

The Campus Safety Department of the University has the responsibility to keep the peace and maintain a safe environment for students on the university campus. This department is entrusted with the following responsibilities : Monitor and control traffic violations such as :

1. Illegal parking (eg. issuing parking tickets, moving tickets, etc)
2. Speeding violation (eg. issuing speeding tickets)
3. Traffic Accidents (eg. generating accident reports)

Monitor and control criminal incidents such as :

1. Larceny
2. Breaking and Entering
3. Malicious Destruction of Property
4. Disorderly or Uncooperative Conduct
5. Assault
6. Intrusion Alarm

Record and monitor other incidents such as :

1. Safety or Hazards Checks
2. Medical Assist
3. Lost and Found
4. Fire Alarm
5. Police Dept. Assists

Objective

To set-up a user friendly information system for the Campus Safety Department using Paradox version 4.5 for Windows, with capabilities for :

1. Security control (eg. System and user login control)
2. Editing records (eg. Add records, delete records, etc)
3. Searching records (eg. by ID no., Name or Vechicle Registration no.)
4. Generating reports (eg standard or ad hoc reports)
5. Database back-up or Archive
6. Database Adminstration (eg. Rebuilding a database, etc)
7. Browsing the Database attributes where students have the Right-To-Know

Problem Definition

The existing data collection system at Campus Safety is mainly manual. There is a partially operating database system that is unable to search records, having some missing links between tables, unable to generate reports and not operating efficiently.

Procedure

The basic approach for this software project are :

1. Interview with Campus Safety Officer to determine requirements
2. Perform the System Analysis
   • Identify entities, relationships and processes
   • Determine attributes of the entities
   • Identify primary key/s
   • Determine cardinality and relationships
   • Identify foreign key/s
   • Create the Data Dictionary
   • Design Entity-Relationship diagrams
   • Create additional design diagrams if necessary (eg. Data Flow Diagrams, etc)
3. Design and create Database tables structure
4. Link database tables
5. Design and code Forms
6. Design and code queries
7. Design and create reports layout
8. Design program code
9. Test the alpha version software
10. Debug the software if necessary
11. Demo the working model software to the users in the Campus Safety for beta testing
12. Design the User manual and Technical manual
13. Prepare for the oral presentation.

Estimated Schedule

Expected Results

On completion of the software project, a working information system will be setup at Campus Safety with the required documentation.