Software Project Management Plan

BGTracks System CSC 480
Software Project Management Plan
For The
BGTracks System
23 October 2009
Prepared for:
Boys & Girls Club of Sequoias
Prepared by:
Christopher Horner
Fernandito Eugenio
Heath Ivie
John Hancock
Kenneth Brower
Marlo Castillo
Michael Adams

1
Revision Sheet
Release No. Date Revision Description
Approvals
Title Printed Name Signature Date

Client Representative
Project Manager

2
Project Leader
TABLE OF CONTENTS
Page #
1.0 INTRODUCTION
1.1 Project Overview…………………………………………………………... 5
1.2 Project Deliverables………………………………………………………... 5
1.3 Evolution of the SPMP…………………………………………………….. 5
1.4 Reference Materials………………………………………………………... 6
1.5 Definitions and Acronyms…………………………………………………. 6
2.0 PROJECT ORGANIZATION

2.1 Process Model………………..……………………………………………..9
2.2 Organizational Structure…………………………………………………… 10
2.3 Organizational Boundaries and Interfaces…………………………………. 10
2.4 Project Responsibilities……………………………………………………..11
3.0 MANAGERIAL PROCESS

3.1 Management Objectives, Priorities, Reporting……………………………..14
3.1.1 Objectives……………………………………………………………. 14
3.1.2 Priorities……………………………….….…………………………..14
3.1.3 Reporting………………………………...............................................
14
3.2 Assumptions, Dependencies, and Constraints……………………………... 14
3.3 Risk Management………………………………………………………….. 15
3.4 Monitoring and Controlling Mechanics……………………………………15
3.5 Staffing Plan………………………………………………………………...
16
4.0 TECHNICAL PROCESS

4.1 Methods and Tools……………..…………………………………………...19
4.2 Software Documentation………………………………………………….. 19
4.3 Project Support Functions…………………………………………………..20
5.0 WORK PACKAGES, SCHEDULE, BUDGET

5.1 Work Packages……………………………………………………………...22
5.2 Resource Requirements……………………………………………………. 22
5.3 Budget and Resource Allocation…………………………………………... 23
5.4 Schedule………………………..…………………………………………...24

3
1.0 INTRODUCTION

4
1.0 INTRODUCTION
1.1 Project Overview
The project was undertaken to provide the Boys & Girls Clubs of the Sequoias with a web based
software solution that delivers a scalable, secure, and reliable tracking and reporting on the
personal information and attendance of their membership and staff.
This document provides an overview on the planning or the blueprint on the process to develop
the BGTracks System from planning all the way to deployment.
1.2 Project Deliverables
The project deliverables of the project and the delivery dates are as follows:
Project Deliverables
Item Delivery Date Delivery Location QTY
BGTracks System 10/30/2009 National University 1
User Documentation 10/30/2009 National University 1
The BGTracks System would be the software program on a DVD. This will include all
programs and files that will be needed to install and run the BGTracks System. It is assumed
that other programs like a Web Browser is already installed in all applicable systems of the Boys
& Girls Club sites.
The User Documentation is an overview of the features and capabilities of the BGTracks System
and also includes sections for the installation and use of the BGTracks System. This will be in
the form of a soft copy or file delivered to representative of the Boys & Girls Club of the
Sequoias.
1.3 Evolution of the SPMP
The typical evolution of software would include plans for future versions and upgrades of
the software.
As of the present, the current evolution for the BGTracks System is to research, plan and
develop the program. The current evolution for the BGTracks System only accounts for
its development through implementation and deployment. The SPMP as of right now is
planning for the analysis, design, development, coding, testing, and implementation of
the BGTracks System for the Boys & Girls Club of the Sequoias.
Future evolution of the BGTracks System in terms of additional releases and or upgrades
5
can still be evaluated and implemented at a later date if the need arises.
1.4 Reference Materials
For the CSC 480 project site for the BGTracks System including wikis and other project
documents please reference:
http://code.google.com/p/nucsc480project/
The layout and the template used for this SPMP document can be found on National
University’s eCollege, in the September 2009 course, under the Doc Sharing tab:
http://myonlinelogin.com/ec/crs/default.learn?
CourseID=3601366&CPURL=myonlinelogin.com&Survey=1&47=4308408&ClientNod
eID=405010&coursenav=0&bhcp=1
For the latest and most up-to-date version of this document and other project documents,
please reference the Downloads section of the CSC 480 Google Project site at:
http://code.google.com/p/nucsc480project/downloads/list
1.5 Definitions and Acronyms
Members – Children who attend the Boy & Girls Club of the Sequoias.
Site – Location of a building of The Boys & Girls Club of the Sequoias. Can also
reference a unit of the Boys & Girls Club of the Sequoias.
Unit – Unit describes both the physical location of a Boys & Girls Club site, and the idea
of a site object with its employees, members, and activities.
Member ID Number – A 1 to 9 digit number that uniquely identifies a member of the

Boys & Girls Club of the Sequoias.
Staff ID Number – A 1 to 9 digit number that uniquely identifies a staff member of the
Boys & Girls Club of the Sequoias.
.xls – Microsoft Excel Spreadsheet file format. Some of the files referenced in the
document is in Excel format.
Household – refers either to a family or group of people living in a residence.

6
SPMP – Software Project Management Plan. The Software Project Management Plan
document outlines the planning of the project and includes the scope, estimate of the
work involved to be done for the project and the project schedule.
SRS – Software Requirements Specification. The Software Requirements Specification

document describes the behavior of the system that will be developed.
SDD – Software Design Document. The Software Design Document specifies the design
elements that will be utilized and included in the development of the BGTracks System.
OCD – Operational Concept of Design. The Operation Concept of Design document

provides a high-level overview of the BGTracks System.
GPL – General Public License. A General Public License is a widely used free software
license. The BGTracks System will utilize a GNU GPL version 2 license.
Proj. – Projected.
Est. – Estimated.
SVN – Subversion Network. The SVN is the online repository for the source code for
the BGTracks System. It is able to keep both current and historical versions of the source
code to show the progression or development of the project. Other applicable files such
as documents are also kept in the SVN repository.

7

8
2.1 Process Model
The main milestones identified in the project are:
Project Initiation Date: 08/10/2009
The project was initiated on August 8, 2009 during the first meeting of the CSC 480A
class. At that time, an overview of the project timeline and project requirements was
covered. Also, possible projects was proposed but final approval and the decision to go
forward with to move forward with an agreed upon specific project was made at a later
date.
The project initiation task is mainly identifying the specific system that will be developed
by the CASC 480 Group.
Testing: 10/23/2009
The current testing cycle for the Project is slated to begin on Friday, October 23, 2009.
For a list of the UAT cases for the BGTracks System, please reference Section 3.2.12 of
the Software Requirements Specifications Document.
Presentation: 10/30/2009
Presentation of both the completed BGTracks System and all applicable documents
pertaining to the project has been set for Friday, October 30, 2009 from 5p-8p PST. All
parties involved in the BGTracks System project including the client, CSC 480 team and
professional reviewers will be in attendance.
Implementation: TBA
Implementation of the BGTracks System into the sites of the Boys & Girls clubs of the
Sequoias involves the process of successfully installing the software into the applicable
systems of the sites. There is not a set date for the implementation of the BGTracks
System. The date will be mutually agreed upon pending the completion of the
presentation to the clients and agreement of the presented system.
Project Termination Date: TBA

9
The project termination activities would be the successful presentation of the BGTracks
System and successful implementation BGTracks System at the Boys & Girls Clubs of
the Sequoias sites. The termination date will be mutually agreed upon at a later date and
would occur after implementation.
2.2 Organizational Structure
The structure of the NUCSC480 organization is depicted as the following. Please note that while
Professor Aslam-Mir is listed as the project advisor over all of the CSC480 Project organization,
Professor Aslam-Mir acts only in an advisory and guidance role and will not be directly involved
in any of the related hands-on tasks and duties associated with the planning, development, testing
and implementation of the BGTracks System.
Organizational Structure of the CSC 480 Project Team:

Shahzad Aslam-Mir
NU Professor
Project Advisor
Fernandito Eugenio
Project Manager
Heath Ivie Jon Hancock Ken Brower

Development Lead Design Lead Database Lead
Chris Horner Marlo Castillo Michael Adams

Project Member Project Member Project Member
Name Title
Prof. Shahzad Aslam-Mir Project Advisor
Fernandito Eugenio Project Manager
Heath Ivie Development Lead
Jon Hancock Design Lead
Ken Browe Database Lead
Chris Horner Project Team Member
Marlo Castillo Project Team Member

10
Michael Adams Project Team Member
2.3 Organizational Boundaries and Interfaces
The organizations identified and connected in association with this project include:
Project Organization : CSC480 Group – This is the main organization that is responsible for the
analysis, design and development of the BGTracks System Program for the Boys & Girls Club of
the Sequoias.
Parent Organization : National University – National University is the parent organization of

the CSC480 group and oversees and advises the CSC480 group. The primary contact and liaison
with National University is with Shahzad Aslam-Mir, professor with National University.
Customer Organization : Boys & Girls Club of the Sequoias is the client who the BGTracks
System is being developed for. The BGTracks System will replace their current membership and
staff attendance and reporting software for all sites of the Boys & Girls Club of the Sequoias.
2.4 Project Responsibilities
The following table lists members of the NUCSC480 project team and the main duties and
responsibilities of each member.
Name Duties and Responsibilities

Heath Ivie Lead by providing a project vision and roadmap
Design core libraries, write code and unit tests
Measure performance and find bottlenecks to optimize
Review code changes and provide constructive feedback

Fernandito Eugenio Manager the project
Plan the scope of release milestones and track progress

Marlo Castillo Write end-user documentation and examples
Test the system before each release

Jon Hancock Lead by providing a project vision and roadmap

11
Create graphic artwork, audio, and other data assets
Lead the UI design and incorporate feedback

Chris Horner Set up and maintain build tools and test automation
Package releases from release branches

Ken Brower Define database schemas and persistence layers
Design core libraries, write code and unit tests
Review code for security and scalability

Michael Adams Document our development process and help new members
Test the system before each release
Manage legal aspects of COTS implementation
Other duties not currently identified will be assigned to applicable project members as they
appear during the Software Development process.

12

13
3.1 Management Objectives and Priorities
The software design project came about as a means to try and replace the current implementation
in place at the Boys & Girls Club of the Sequoias in regards to Membership tracking and
reporting. The current system in place has inherent security flaws that could be exploited to
allow unauthorized access to restricted data. In the process of trying to replace the current setup,
other features and design improvements were identified to be included for the design of the
BGTracks System program.
3.1.1 Objectives
The main objectives of this project is:
-To close the security flaws inherent with the current software implementation used for
member attendance at the Boys & Girls Club of the Sequoias sites while also making
available the reporting features found on the current software in place.
-Another objective would be to allow for a web based implementation of the BGTracks
System and to have a more user-friendly interface in regards to the check in check out
process for members and providing the same features to the staff.
3.1.2 Priorities
The main priorities would be to develop the check in and checkout capability for both
members and staff of the Boys & Girls Club of the Sequoias and also to have a flexible
reporting capability to display the stored attendance data.
3.1.3 Reporting
In terms of reporting, the project team is required to submit a weekly status report to
Professor Shahzad Aslam-Mir detailing their involvement and actions for the previous
week. This report should include the items attempted and completed during the past
week and also any issues identified that would be needed to be addressed.

14
3.2 Assumptions, Dependencies, and Constraints
Below is a list of the assumptions, dependencies and constraints identified for the BGTracks
System project. This is a working list that could be adjusted based on needs and constraints
encountered during the software development process.
Assumptions:
- Every member of the project team has a computer for use to work on the project.
- Every member is able to access the Internet particularly the Google project site and the
SVN repository that can be
- Every member is able to download, install and utilize all applicable software and tools
needed for this project including Eclipse.
- All needed hardware that the Software Tracking Program will utilize is already in
place at the facilities of the Boys & Girls Club of the Sequoias.
Dependencies:
- The project is dependent on the current hardware/software policies and procedures in

place for the Boys & Girls Club of the Sequoias.
Constraints:
- The user interface must be viewable on a monitor with a 1024x768 resolution or larger.
Design mechanisms are limited to the capabilities of HTML, CSS and JavaScript.
- Any attendance logs made either by an employee or member can be tracked in the
Reporting function of the BGTracks System.
- Any members enrolled or added into the system will be able to be referenced or accessed
by the Attendance function and also the Reporting function of the BGTracks System
program.
- Any activities created can be accessed by the Attendance and Reporting functions of the
BGTracks System Program.
3.3 Risk Management

The project team is aware of the risk factors associated with the BGTracks System project. To
address this, a ticketing system has been implemented on the Google project web site to identify,
assess, and address any issues that come up during the BGTracks System project.
The link to this ticketing system is listed below:

http://code.google.com/p/nucsc480project/issues/list
15
3.4 Monitoring and Controlling Mechanisms
The project team is aware that many issues can come up during the development process.
Current reporting mechanisms include Weekly Status reports submitted at the end of each week
and emails sent to the group as a whole specifying any current or outstanding issues pertaining to
the project.
3.5 Staffing Plan
The following outlines the estimated hours to complete all the identified components for the
project. Note, 1 day is equal to 1 business or work day and would equal to 8.0 hours.
Staffing Plan
Task Name Est. Duration Est. Hours
Scope 1 day 8.00
Analysis/Software Requirements 10 days 80.00
Get Feedback from stakeholders 10 days 80.00
Sub Total: 168.00

Design Phase 8 days
Clock In/Out Procedure 1 day 8.00
-User Login/Logout 1 day 8.00
-General Attendance Check In/Out 2 days 16.00
-Specific Activity Check In/Out 2 days 16.00
-Mass Activity Check In/Out 2 days 16.00
-Schedule Activities 8 days 64.00
-Member Enroll 4 days 32.00
-Mass Member Enroll 4 days 32.00
-Reporting 8 days 64.00
-Emergency Roster Report 8 days 64.00
-Weekly Attendance Report 8 days 64.00
Sub Total: 384.00

Development Phase 3 days
-Clock In/Out Procedure 2 days 16.00
16

-Schedule Activities 1 day 8.00
-Data Entry 1 day 8.00
-Member Enroll 1 day 8.00
-Mass Member Enroll 1 day 8.00
-Reporting 1 day 8.00
-Emergency Roster Report 1 day 8.00
Sub Total: 144.00

Testing Phase 3 days
Attendance 2 days 24.00
-Clock In/Out Procedure 2 days 16.00
Scheduling 2 days 16.00
-Schedule Activities 2 days 16.00
-Data Entry 2 days 16.00
-Member Enroll 2 days 16.00
-Mass Member Enroll 2 days 16.00
Reporting 2 days 16.00
-Emergency Roster Report 2 days 16.00
-Weekly Attendance Report 2 days 16.00
Sub Total: 224.00

Documentation 5 days 40.00
SRS Document 5 days 40.00
SDD Document 5 days 40.00
Concept of Operation 5 days 40.00
SPMP Document 5 days 40.00
Sub Total: 200.00

Presentation 1 day 3.00
Sub Total: 3.00

17
Deployment 2 days 16.00

Sub Total: 16.00
Grand Total: 1139.00 Hrs

18
4.1 Methods and Tools
Methods
The main development method that will be used for creating the BGTracks System
would be the Scrum method. After extensive discussion within the group, it was
decided to proceed with this method instead of more linear Software development
method.
This was done due to the limited time available for the software development process
of the BGTracks System. The project team recognized the pitfalls of allocating more
time to requirements gathering and documentation and leaving not enough time for the
development or creation of the BGTracks System.
Tools
For the tools utilized in the development process, please reference Section 5.2, the
Resource Requirements portion of this document.
4.2 Software Documentation
The following is a list of the documents that are required and developed
1. Software Project Management Plan: Outlines the process of the BGTracks System and
specifies the projected schedule for the whole Software Design Process. The SPMP
identifies the project deliverables and milestones and also the project schedule.
2. Software Design Document: Document that details the process and design of the
software. This document would specify the needed design factors and requirements that
would go into the design elements of the BGTracks System.
3. Software Requirements Specifications: Document that details the given requirements

of the BGTracks System.
4. Concept of Operations: Document that summarizes the operations of the BGTracks

System.

19
5. Software User’s Documentation: This document identifies the features and capabilities
of the BGTracks System. It also contains user specific information such as use and
troubleshooting the BGTracks System. Document that contains the user manual and all
information that prospective users would find useful in regards to their use of the
BGTracks System.
6. Testing Plan : The Testing Plan document outlines or describes our systematic approach
for testing the BGTracks System. It will be used to confirm that we meet the design
requirements previously outlined for the BGTracks System.
The documents including this one can be found on the downloads section of the project website:
http://code.google.com/p/nucsc480project/downloads/list
4.3 Project Support Functions
At the moment, there have not been any provisions made for project support functions. The only
support function currently available is the ticketing system available on the project web site.
Future support functions and implementation of such functions could be discussed with the client
at a future date.

20

21
5.1 Work Packages
The work packages identified for the BGTracks System include:
Attendance: Attendance would entail any check in or check out procedure either
pertaining to a member or an employee of the Boys & Girls Club of the Sequoias. The
identified sections of this part is the member and employee check/in, activity check in/out
and user login/out.
Scheduling: This section covers any activities that can be scheduled or made using the
BGTracks System.
Data Entry: Members can either be enrolled individually or in groups. Also, member
records can be updated and deleted using this work package.
Reporting: This section covers available reporting methods found in the BGTracks
System and include the Weekly Attendance Report and the Emergency Roster Report.
5.2 Resource Requirements
The hardware resources identified to be required on this project include:
Computer/workstation/notebook: Each member should have a computer or workstation

available to use for this project. No particular funds have been allocated for any
acquisition or rental of hardware resources
Internet hardware and active Internet connection: Each project member should have
all the necessary hardware and an active connection to be able to access the project web
site and the SVN repository. Also an Internet connection is required to download all the
necessary software needed for the development of the BGTracks System.
The software resources required for the project are:
Microsoft Office: Documents associated with this project are created as Word
documents. Also, charts and tables of date may be portrayed using either Excel
formatting or spreadsheets.
22
OpenOffice: OpenOffice is a free software application suite developed by Sun

Microsystems. OpenOffice has the capability of opening and changing Microsoft Office
documents. Since Microsoft Office requires a license to use and if a Project Team
Member does not have Microsoft Office or a specific component, OpenOffice can be
used instead of Microsoft Office in working with project documents.
Eclipse: Eclipse is a multi-language software development environment that is used to

develop applications in Java.
Tomcat Web Server: Tomcat is a Java based web server used over the Internet.
MySQL: This is a relational database program will emulate the database that would hold
the information including members and employees for the Boys & Girls Club of the
Sequoias.
Firefox or Google Chrome: The web browser is needed to access the Google project
web site and is also the main browser platform required to run the Web Application for
the BGTracks System.
Google Code: Google Code is a project hosting resource that will contain the project web
site.
The software required for this project was identified and selected after extensive research and
review based upon specific criteria. The overwhelming factor or criteria used is cost of the
resource materials. Since the above software resources are free and readily available on the
Internet, which provided a compelling factor in the selected software resources. The resources
selected provide the functional and tools needed to successfully develop the BGTracks System
program for the Boys & Girls Club of the Sequoias.
5.3 Budget and Resource Allocation
Since it is assumed that all hardware are already available to the project team and all software
resources needed are either already installed or are freely available for download on the Internet,
no budget has been allocated for any acquisition of any hardware or software resources.
Hardware Requirements: All hardware resources needed by the CSC 480 project team should
already be acquired and available for use by the SCS 480 Project team. No funds have been
allocated for hardware acquisition.
Software Requirements: All project team members should have needed software already
available. Other software identified that will be utilized for the project like Apache, Eclipse and
MySQL can be downloaded and installed via the Internet. No funds have been allocated for
future software acquisition.

23
Wages: Since the development for the BGTracks System is undertaken as a Capstone project for
the CSC 480 class at National University, all hours worked by the CSC 480 Project Team will
not require any wages to be earned. No additional cost or budget is expected to be incurred.
Proposed Budget

Hardware Requirements
Estimated Cost: $0.00

Subtotal: $0.00

Software Requirements

Subtotal $0.00

Wages

Subtotal $0.00

Grand Total: $0.00
The main resource allocation that is allocated for the project would be the man hours expended
by the project team. This is the time spent be the project team in all areas of the development
process. The estimated hours for the project is covered in Section 3.5.
5.5 Schedule
Below is the projected schedule for the components of the project. Please note that estimates the
total hours it would take for the specified tasks. Multiple CSC 40 members can work on
specified tasks and so tasks duration could be accomplished faster while the number of hours
worked would still stay the same.
Task Name Est. Duration Proj. Start Est. Finish

Scope 1 day 8/10/2009 8:00 8/10/2009 17:00
Analysis/Software Requirements 10 days 8/11/2009 8:00 8/24/2009 17:00
Get Feedback from stakeholders 10 days 8/11/2009 8:00 8/24/2009 17:00
Design Phase 8 days 9/10/2009 8:00 9/17/2009 17:00

24
-Clock In/Out Procedure 1 day 9/10/2009 8:00 9/10/2009 17:00

-User Login/Logout 1 day 9/10/2009 8:00 9/10/2009 17:00
-General Attendance Check
In/Out 2 days 9/11/2009 8:00 9/12/2009 17:00
-Specific Activity Check In/Out 2 days 9/11/2009 8:00 9/12/2009 17:00
-Mass Activity Check In/Out 2 days 9/13/2009 8:00 9/14/2009 17:00
-Schedule Activities 8 days 9/10/2009 8:00 9/17/2009 17:00
-Member Enroll 4 days 9/10/2009 8:00 9/14/2009 17:00
-Mass Member Enroll 4 days 9/15/2009 8:00 9/18/2009 17:00
-Reporting 8 days 9/10/2009 8:00 9/17/2009 17:00
-Emergency Roster Report 8 days 9/10/2009 8:00 9/17/2009 17:00
-Weekly Attendance Report 8 days 9/10/2009 8:00 9/17/2009 17:00
Documentation 5 days 8/25/2009 8:00 8/29/2009 17:00

-SRS Document 5 days 8/25/2009 8:00 8/29/2009 17:00
-SDD Document 5 days 8/25/2009 8:00 8/29/2009 17:00
-Concept of Operation 5 days 8/25/2009 8:00 8/29/2009 17:00
-SPMP Document 5 days 8/25/2009 8:00 8/29/2009 17:00
Development Phase 5 Days 9/18/2009 8:00 9/22/2009 17:00

-Clock In/Out Procedure 2 days 9/18/2009 8:00 9/19/2009 17:00
In/Out 3 days 9/18/2009 8:00 9/20/2009 17:00
-Schedule Activities 1 day 9/20/2009 8:00 9/20/2009 17:00
Data Entry 1 day 9/20/2009 8:00 9/20/2009 17:00
-Member Enroll 1 day 9/21/2009 8:00 9/21/2009 17:00
-Mass Member Enroll 1 day 9/21/2009 8:00 9/21/2009 17:00
-Reporting 1 day 9/22/2009 8:00 9/22/2009 17:00
-Emergency Roster Report 1 day 9/22/2009 8:00 9/22/2009 17:00
Testing Phase 3 days 10/23/2009 8:00 10/25/2009 17:00

-Attendance 3 days 10/23/2009 8:00 10/25/2009 17:00
-Clock In/Out Procedure 2 days 10/23/2009 8:00 10/24/2009 17:00
In/Out 3 days 10/23/2009 8:00 10/25/2009 17:00
-Scheduling 3 days 10/23/2009 8:00 10/25/2009 17:00
25
-Schedule Activities 3 days 10/23/2009 8:00 10/25/2009 17:00

-Data Entry 2 days 10/23/2009 8:00 10/24/2009 17:00
-Member Enroll 2 days 10/23/2009 8:00 10/24/2009 17:00
-Mass Member Enroll 2 days 10/23/2009 8:00 10/24/2009 17:00
-Reporting 2 days 10/23/2009 8:00 10/24/2009 17:00
-Emergency Roster Report 2 days 10/23/2009 8:00 10/24/2009 17:00
-Weekly Attendance Report 2 days 10/23/2009 8:00 10/24/2009 17:00
Presentation 1 day 10/30/2009 17:00 10/30/2009 20:00
Deployment 1 day TBA TBA

26

Software Project Management Plan

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Software Project Management Plan

Diunggah oleh

Hak Cipta:

Format Tersedia

BGTracks System CSC 480