This chart contains a history of this document's revisions. All revisions are also tracked by the Wiki's version control mechanism. The different versions are listed here for quick reference.
| Version | Primary Author(s) | Description of Version | Date Completed |
|---|---|---|---|
| Draft | TheHomeTeam | Initial draft created for review and comments | 2003/2/17 | |
| Milestone 2 Revision | JonboyCorbin and DennyDaugherty | Revised for Milestone 2 | 2003/2/26 |
This is our project plan for the Harrisburg Habitat Homeowner Database project.
1. Introduction
1.1 Project Overview
1.2 Project Deliverables
1.3 Evolution of the Software Project Management Plan
1.4 Reference Materials
1.5 Definitions and Acronyms
2.1 Process Model
2.2 Organizational Structure
2.3 Organizational Boundaries and Interfaces
3.1 Management Objectives and Priorities
3.2 Assumptions, Dependencies, and Constraints
3.3 Risk Management
3.4 Monitoring and Controlling Mechanisms
4.1 Methods, Tools, and Techniques
4.2 Software Documentation
5. Work Packages, Schedule, and Budget
5.1 Work Packages
5.2 Dependencies
5.5 Schedule
Our purpose is to develop a database application for Habitat for Humanity of the Greater Harrisburg Area. The database application will help Harrisburg Habitat track information pertaining to local Habitat homeowners. It will track the mortgages of each homeowner, and will also track other important homeowner information. It is our hope that such a database application will relieve Harrisburg Habitat's office staff much of the tedious labor currently involved with their current system. The database application will also improve the quality, quantity, and usability of homeowner information.
Harrisburg Habitat for Humanity adds to Habitat For Humanity's primary mission of ridding the world of substandard housing by working towards ridding the city Harrisburg of substandard housing. It is the belief of Habitat for Humanity that everyone in the world deserves a decent place to live. In order to do this, through volunteers,they build houses and sell them at with a low cost interest-free mortgage to people in need. The database application will help Harrisburg Habitat track information about current homeowners, and future homeowners.
All deliverables will be delivered directly to the Harrisburg Habitat Office in person on Saturday, May 3rd. Prior to May 3rd, the team will come in earlier to set up the application environment, which includes PostgresSQL, Apache, and Tomcat. The team will also go into Harrisburg Habitat early on to help them set up their network.
- Working database running on PostgresSQL
- Working application
- Documentation on how to use the system
- Design Documentation of the system
1.3 Evolution of the Software Project Management Plan
This document will change over time as needed. This document is stored in a wiki, so changes are easy to do, and are tracked in detail.
| Version | Primary Author(s) | Description of Version | Date Expected |
|---|---|---|---|
| Draft | TheHomeTeam | Initial draft created for review and comments | 2003/2/17 |
| Version One | TheHomeTeam | This will be the first "official" version of this document. It will be as complete as possible. All important dates will be filled in. | 2003/2/20 |
| Version Two | JonboyCorbin and DennyDaugherty | This will be the Milestone Two version of the document. | 2003/2/26 |
Nothing referenced yet.
Not yet applicable.
We are planning on using an incremental process model. As software requirements are specified, they will be prioritized high, medium, or low. Later, these will be split into increments, which will be build one after the other.
Project Schedule*
| Work Product Name | Planned Completion Date | People Who Must Sign Off on the Work Product |
|---|---|---|
| Project Proposal | 2003/2/18 | Fred Silva and Brian Nejmeh |
| Project Plan | 2003/2/27 | Fred Silva |
| Software Requirements | 2003/2/27 | Fred Silva |
| Database Design | 2003/3/13 | TheHomeTeam |
| User Interface Design | 2003/4/8 | Fred Silva and TheHomeTeam |
| Completed Database Application | 2003/4/22 | Fred Silva and TheHomeTeam |
| Application Documentation | 2003/5/6 | Fred Silva and TheHomeTeam |
Nonchanging:
Milestone 2:
2.3 Organizational Boundaries and Interfaces
The TheHomeTeam is working with Harrisburg Habitat for their project for Database Applications. The TheHomeTeam will handle all development and development-related activities, as well as working with Harrisburg Habitat to meet their requirements as much as is possible, and working to meet the requirements for their Database Applications class.
JimHurne is the official project contact with Harrisburg Habitat. All team members will be responsible for assuring that the project meets the class requirements for Database Applications.
3.1 Management Objectives and Priorities
The rotating project lead will be responsible for management related issues. The project lead should keep in contact with all project members and make sure they are meeting their responsibilities. Project lead will delegate responsibilities, if necessary. The project lead will also be responsible for status reports during their term.
3.2 Assumptions, Dependencies, and Constraints
The first and foremost risk to the project is not being able to produce deliverables on schedule. The second risk is that the project will not be able to sufficiently meet project requirements to be useful, or that the project requirements will not be accurate.
Following this Project Plan and keeping on constant communication with team members will help to reduce these risks.
See section above on Process Model
4.1 Methods, Tools, and Techniques
Not all tools have been determined yet. We are currently leaning towards using JSP, struts, and PostgreSQL. The operating system may be Linux, or Windows. This has not been determined, and will not affect most of our application development anyway.
Source code control will be accomplished using either CVS or Subversion.
All project documents will be maintained on this wiki.
Quality assurance practices have not yet been determined.
All documentation will reside in this wiki.
Subpackages not yet defined.
- Software Requirements
- Documentation
- Software
To be determined.
See also Process Model
2/18 - Milestone 1 Finished - Project Proposal
2/19 - Meeting with Fred Silva
2/26 - Meeting with Fred Silva - Review draft Project Plan and Requirements
2/27 - Milestone 2 Finished - Requirements Definition - Updated Project Plan
3/5 - Meeting with Fred Silva - Review Application Prototype
3/12 - Meeting with Fred Silva - Review Milestone 3
3/13 - Milestone 3 Finished - Database Application Analysis
4/8 - Milestone 4 Finished - Database Application Design
4/22 - Milestone 5 Finished - Database Application Implementation
5/6 - Milestone 6 Finished - Application Turnover and Final Presentation
Not yet applicable.
Include additional components needed to manage your specific project. Possibilities include subcontractor management plans, security plans, training plans, hardware procurement plans, facilities plans, installation plans, cutover plans, and software maintenance plans.
|
| Page Execution took real: 123.734, user: 14.570, sys: 0.690 seconds |