Revisions
|
Version |
Primary Author(s) |
Description of Version |
Date created |
|
Third |
Bobby Lusk |
Updated the Draft with new information |
4/22/2004 |
Preface
This
is the project plan for the HELP Ministries DB project.
1. Introduction
1.1 Project Overview
Christian
Churches United HELP Ministries is an emergency human service agency. They work
with people who are in need of life sustaining services. This includes: food
pantry referrals, emergency shelter placement, prescription medication
assistance, rental assistance and travel assistance. HELP has a database that
maintains name and case history of their clients who come to them for help, and
for the organizations that provide some of the amenities.
HELP
would like to design and print reports based on different search criteria for
different purposes. They would also be able to modify the DB according to their
needs: like adding new fields, to
perform queries and do searches. Their
main requirement is that they keep the current DB, but iron out the glitches
and add more functionality in printing reports.
1.2 Project Deliverables
This
project will culminate in having a new working, and bug-free Microsoft Access
DB that is similar to the DB currently used by help, but updated for extended
usability and scalability, being given to HELP.
The first deliverable will have a fairly complete understanding and
modeled view of the underlying DB structure, as well as a rough prototype of
the DB and its GUI to be tested for functionality and user-friendliness. The second deliverable will iron out any
implementation issues and refine the DB and the GUI. A third deliverable will include some project
extensions such as enabling a remote user on a laptop to work with a copy of
the database, synching any updates upon returning to the HELP offices.
1.3 Evolution of the Software Project
Management Plan
This
document will be updated and corrected as our project advances in order to keep
us on track with our goals depending on any unforeseen difficulties.
1.4 Reference Materials
None
at this time.
1.5 Definitions and Acronyms
DB Database
CCU
GUI Graphical User Interface
2. Project Organization
2.1 Process Model
The
project will be developed using an incremental approach.
Project
Milestones
Milestone
1: Project Proposal and Preliminary Project Plan
Milestone
2: Requirements Definition, updated project plan
Milestone
3: Database Application Analysis; updated project plan, UML model of DB
Milestone
4: Database Application Design; Delivery of First Increment; Updated project
plan
Milestone
5: Development of Increments 2 and possibly 3; Testing and Performance
Improvement
Milestone
6: Acceptance Testing; Application Turnover and Final Project Presentation
|
Work Product
Name |
Planned Completion
Date |
People Who
Must Sign Off on the Work Product |
|
Project Proposal Project Plan Updated Project Plan |
|
John Scarpato and Brian
Nejmeh John Scarpato John Scarpato |
2.2 Organizational Structure
Program
Director at HELP: John Scarpato
Technical
Contact at HELP: Dan
2.4 Project Responsibilities
|
Responsibility |
Persons
responsible |
|
Requirements and project
plan |
David |
|
UML and Data Model |
Ria |
|
DB implementation and
testing |
Bobby |
|
Team Contact |
David |
3. Managerial Process
3.1 Management Objectives and
Priorities
The
project lead for each part of the project will be responsible for making sure
that goals for their section are met, and for delegating responsibility for the
parts of that milestone.
3.2 Assumptions, Dependencies,
and Constraints
This
Project should have a similar GUI to the current one, in terms of the flow of
the interface, in order to make it easier for HELP staff to get accustomed to
it. We are also assuming that the
process of exporting the data from the Alpha 5 database into the one we create
will be possible and not take extensive work.
3.3 Risk Management
The
only Risk we foresee at this time is that of completing the project, which is
more of a requirement than a risk.
4. Technical Process
4.1 Methods, Tools, and
Techniques
We
will model a new DB in a Microsoft Access database application in order to
create a better working and better designed database that HELP can use. We will still attempt to keep the Interface
level of the DB similar to what HELP staff currently experience, changing it
where needed and where logic and ease of use would benefit.
Quality
will be assured through testing throughout the steps, as well as prior to
deployment.
5. Work Packages, Schedule, and Budget
5.1 Work Packages
1. UML data model
·
Understand
current model
·
Recreate Tables
from Scratch, maintaining that Business rules are followed.
2. GUI development
·
GUI must have
logical flow and intuitive design
·
GUI will be
extensively based on the current layout of the DB
·
Get HELP feedback
on our GUI prototype
3.
Develop Final DB
·
Populate the DB
with the previous Data
·
Testing and bug
checking
5.2 Dependencies
Developing
the UML data model is a very important stage, because it must be decided upon
before the DB can be created and tied into the GUI. The GUI itself can be created without having
the complete DB yet, as we will most likely be creating it in Html.
5.5 Schedule
Milestone
1:
Milestone
2:
Milestone
3:
Milestone
4:
Milestone
5:
Milestone
6: