1.1 Project Overview

The existing camp management system consists of an MS Access database with a single table. Camp participants send their registration information via surface mail. Participant information is manually entered from the registration form to the database. Address information is extracted in order to print mailing labels for registration confirmation. All team and league generation, participant room assignments, scheduling, and other tasks are performed manually. The organization desires a database system that will accept online registrations, minimize problems associated with differences in the time of registration and receipt of payment, reduce the amount of time required for data entry, and automate as many camp setup tasks as possible.

1.2 Project Deliverables

• Database Application
• User Manual
• System Administrators Manual
• Training on the System

1.3 Evolution of the Software Project Management Plan

Version	Primary Author(s)	Description of Version	Date Expected
Draft	Nate Rudd	Initial draft created for distribution and review comments	2/27/03
Preliminary	TBD	Second draft incorporating initial review comments, distributed for final review	TBD
Final	TBD	First complete draft, which is placed under change control	TBD
Revision 1	TBD	Revised draft, revised according to the change control process and maintained under change control	TBD
etc.	TBD	TBD	TBD

2.1 Process Model

• Project Life Cycle Model - We will follow the Database Application Life Cycle Model. This will look a lot like a waterfall model.
• Milestones - To take a look at the major milestones that we will be working on and their major due dates take a look at the Milestone List page.
• Risks - Primary risk items exist in a potentially unrealistic schedule and in personnel shortfalls. Incremental development and prioritization will be utilized to manage scheduling risks while job matching, knowledge and resource sharing, and message boards will be used to handle potential personnel shortfalls.
• Budget - Because the organization has decided to accept payment by personal check only, there are no fees associated with debit or credit card transactions. We intend to utilize free, open-source technologies on the development end so there is effectively no budget for this project.

2.3 Organizational Boundaries and Interfaces

• Messiah College - We have to interface with them on our project to find a place to end up storing the databases we create.
• Messiah College Basketball - Sponsoring organization who we get our design information and who we answer to for questions.

2.4 Project Responsibilities

• Brendan Post
  • Primary liaison to Messiah College ITS and Webmaster
  • Researcher of existing relevant technologies
  • Programmer, web and database development
  • Project documentation and milestone development
• Andrew Proper
  • Primary liaison to Mr. Rick Van Pelt, Messiah College Basketball Team
  • Researcher of existing relevant technologies
  • Programmer, web and database development
  • Project documentation and milestone development
• Nathaniel Rudd
  • Server environment setup and maintenance for development
  • Programmer, web and database development
  • Project documentation and milestone development

3.1 Management Objectives and Priorities

• Reporting - We plan to update this webpage constantly with updates on how our project is turning out.
• Communication - Using the Webboard we can post messages to each other on top of what we are each working on.

3.2 Assumptions, Dependencies, and Constraints

• Assumptions - We assume that we can obtain the appropriate software to run our databases and upload them at the end of the year to Messiah's site.
• Dependencies - Sine we are developing web driven interfaces we are dependent on the network at Messiah.
• Constraints - None at this time

3.3 Risk Management

Primary risk items exist in a potentially unrealistic schedule and in personnel shortfalls. Incremental development and prioritization will be utilized to manage scheduling risks while job matching, knowledge and resource sharing, and message boards will be used to handle potential personnel shortfalls.

3.4 Monitoring and Controlling Mechanisms

Our progress and quality control will be partially monitored by our teacher, Professor Nejmah in his grading. We will also be keeping each other accountable for quality.

4.1 Methods, Tools, and Techniques

• Server - There must be a server that can serve MySQL and handle PHP cgi-scripts. Right now we are using an Apache Server running on a MacOS X machine. It has been set up to run PHP and MySQL.
• Client - It must be a machine that can view web pages.

4.2 Software Documentation

• Administrator's Manual
• User's Manual

5.1 Work Packages

1. Requirements Document
2. ER Logical Schema
3. MySQL Implementation
4. Manuals

5.4 Budget and Resource Allocation

Because the organization has decided to accept payment by personal check only, there are no fees associated with debit or credit card transactions. We intend to utilize free, open-source technologies on the development end so there is effectively no budget for this project.

5.5 Schedule

Please take a look at our Milestone List page.