Software
Project Survival Guide
Software Development Plan
Top Level Contents
Detailed Contents
Revision Chart
Preface
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. Project Organization
2.1 Process Model
2.2 Organizational Structure
2.3 Organizational Boundaries and Interfaces
2.4 Project Responsibilities
3. Managerial Process
3.1 Management Objectives and Priorities
3.2 Assumptions, Dependencies, and Constraints
3.3 Risk Management
3.4 Monitoring and Controlling Mechanisms
3.5 Staffing Plan
4. Technical Process
4.1 Methods, Tools, and Techniques
4.2 Software Documentation
4.3 Project Support Functions
5. Work Packages, Schedule, and Budget
5.1 Work Packages
5.2 Dependencies
5.3 Resource Requirements
5.4 Budget and Resource Allocation
5.5 Schedule
Revision Chart
| Version |
Primary Author(s) |
Description of Version |
Date Completed |
| Draft |
JJH, CJD |
Initial draft created for
distribution and review comments |
02/24/04 |
Introduction
Project Overview
This project is beneficial to the West Shore Evangelical Free Church in terms of tracking the opinions of its members. We will be creating the survey system so that the administration can receive the results in order to better assess to the needs of the church members in the community. West Shore Evangelical Free Church has tried to further push ministry toward using the latest technology with the inclusion of login names and accounts on their web site ( Becoming Like Jesus )so that their members can track and find contact information of other members as well as stay informed about the latest events happening with the church. Brad Coverdale will be in frequent contact with Joel Worrall as the project progresses to address concerns and to give ideas of how to make the application better.
Project Deliverables
- Customizable Single Question Creation System (Web Interface)
- Customizable Multiple Survey Creation System (Web Interface)
- End User Single Question Interface (Web Interface)
- End User Multiple Survey Interface (Web Interface)
- End User Real-Time Result Viewer (Web Interface)
Evolution of the Software Project Management Plan
| Version |
Primary Author(s) |
Description of Version |
Date Expected |
| Preliminary |
JJH, CJD |
Second draft incorporating
initial review comments, distributed for final review |
02/24/04 |
| Final |
CJD, BJC |
First complete draft,
which is placed under change control |
5/4/04 |
Reference Materials
We are not using any other reference materials at this time.
Definitions and Acronyms
- Creator - The Administrator user of all of the survey system
- Customer - West Shore Evangelical Free Church
- Customizable Single Creation System - This will allow the "creator" to create a single survey question.
- Customizable Multiple Survey Creation System - This system will allow the "creator" to create multiple customizable surveys with multiple customizable questions included in the survey.
- End User - Any user that views the customers web site
- End User Multiple Survey Interface - This interface will give the end-user the ability to select a survey that they want to take and to answer the questions defined for that survey
- End User Real-Time Result Viewer - A Interface by which the End-User can view the results of the survey they have just taken, or the Single question they have just answered.
- End User Single Question Interface - A small demo interface that will be integrated into the main page of the customers web site.
Project Organization
Process Model
We will be using an evolutionary prototyping model where we will gather requirements, prioritize them,
and build the system incrementally occasionally getting feedback from the customer.
- Milestone 1: Project Proposal and Preliminary Project Plan - This project
milestone will require significant interaction with the project organization
to define the scope of the project.
- Milestone 2: Requirements Definition - This milestone will involve gathering
and analyzing the functional and non-functional requirements for the database
application. This will culminate in the development of a requirements document
detailing the functional and non-functional requirements (including security,
performance and back-up requirements) of the proposed database application.
- Milestone 3: Database Application Analysis; Updated Project Plan - This
milestone focuses on an analysis of the requirements in terms of a data schema
and business rules required to build the database application. Each project
will select and use an appropriate database design tool that supports ER or
UML modeling. The database application analysis will include the use of low-fidelity
user interface prototypes of key application inputs and outputs (forms, reports,
etc.). The database technology used to implement the system will be selected
at this time. In addition, known project issues will be discussed and the
project plan will be updated.
- Milestone 4: Database Application Design; Delivery of First Increment; Updated
Project Plan - This milestone focuses on the design of the database application
based on the requirements and database application analysis. The database
application design will include the physical design and normalization of the
database along with actual user interface designs for all application input
and output (forms, reports, etc.) based on the low-fidelity prototypes. The
first increment of the database functionality will be prototyping as part
of this milestone . In addition, known project issues will be discussed and
the project plan will be updated.
- Milestone 5: Development of Increment 2; - This milestone will result in
the final implementation of the database application based on the database
application design. The final implementation will include the functionality
defined in Increment 2. In addition, known project issues will be discussed
and the project plan will be updated.
- Milestone 6: Testing and Performance Improvement - It will include testing
of the final application as well as any performance improvements necessary
to satisfy the requirements. The application will then be prepared for complete
transfer to the sponsor organization, thus releasing the development team
from any future responsibilities of maintenance or upkeep.
| Work Product Name |
Planned Completion Date |
Placed Under Change Control? |
Deliverable to Customer? |
People Who Must Sign Off on the Work
Product |
| Software Project
Management Plan This is the
controlling document for managing a software project, and
it defines the technical and managerial processes
necessary to deliver the project requirements.
|
02/24/04 |
Yes |
No |
All Team Members |
| Software Requirements Specification |
02/24/04 |
Yes |
Yes |
All Team Members |
| Final Implementation of Project Requirements |
4/26/04 |
Yes |
Yes |
All Team Members |
Complete turnover of Project to Sponsor
This will contain both the final application, and the
supporting documentation and user's guide. |
5/4/04 |
Yes |
Yes |
All Team Members |
Organizational Structure
Organizational Boundaries and Interfaces
- West Shore Evangelical Free Church - customer
- Development Team
Project Responsibilities
| Responsibility |
Persons responsible |
| Project Manager |
Brian Nejmeh |
| Team Liaison |
Brad Coverdale |
| Engineering Manager |
Joshua Henry |
| Quality Assurance Manager |
All |
| Database Design Manager |
Christina Felts |
| Requirements Development |
Brad Coverdale ,
Christina Felts |
| Web Design Manager |
Chris Dries |
Managerial Process
Management Objectives and Priorities
- Have a working survey system
- Make sure system is easy to work with for those who are not necessarily technically knowledgeable
- Make a interface for creating customized surveys
- Display results of surveys
Assumptions, Dependencies, and Constraints
- We will be using MySQL, JSP, and JDBC – these are the technologies that the web server has running
- We need to use the user login already in the system
- Keep answers anonymous but be able to keep track of whether someone has taken a survey already
- Only certain types of questions
Risk Management
The risks of this project will be monitored by the project manager at the completion of each Milestone, and throughout the project by the team members.
Monitoring and Controlling Mechanisms
The development of this project will be monitored by the project manager at the completion of each Milestone.
Staffing Plan
The entire project will be staffed by the above mentioned individuals.
Technical Process
Methods, Tools, and Techniques
- The system will be developed on a system similar to the customers web server which is running MySQL, JSP, and JDBC
- Some of the software tools we will use for this project are but are not limited to Macromedia Dreamweaver, PHPmyAdmin, Microsoft Visio, Microsoft Word, Microsoft Powerpoint, or other similar products.
- We will be using UML data modeling to design the structure of the underlying database, and storyboards or other similar methods to develop the basic flow and layout of the user interfaces.
- Quality assurance
practices will include various methods of technical peer review,
unit testing, incremental development, system
testing, and group discussions between the team members.
Software Documentation
- Project Plan
- Software Requirements Specification
- Milestones 1-6
- Creator and End User usage guide or tutorial
Project Support Functions
Work Packages, Schedule, and Budget
Work Packages
Dependencies
See above chart.
Resource Requirements
- 1 development and testing web server running JSP, JDBC and MySQL
- 1-2 requirements gatherers
- 4 system designers
- 1 documentation manager
- 1 database modeler and creator
- 2-3 JSP programmers
Budget and Resource Allocation
There is no expected budget at this time
Schedule
- Milestone 1 - February 12, 2004
- Milestone 2 - February 26, 2004
- Milestone 3 - March 11, 2004
- Milestone 4 - April 6, 2004
- Milestone 5 - April 22, 2004
- Milestone 6 - May 4, 2004