CORDOVA PUBLIC OF COLLEGE

COLLEGE OF COMPUTER STUDIES

Software Project Management Plan

For

CPC COMPUTERIZED VOTING SYSTEM

Signature
Roneth M. Jubay
John Paul S. Rosende
Monaliza Bautista
Cecile Marie Tual

Change History

Preface
The purpose of this document is to specify the project plan to develop the CPC Computerized
Voting System. This document outlines a brief plan about how the project will be shape. It also
includes the milestones and deliverables. Updates of this document will serve to record the
progress of the project.

Table of Contents
Signature ... 2
Change History 3
Preface ... 4
Table of Contents . 5
List of Figures ... 6
List of Tables . 7
Project Summary . 8
1.1 Purpose, Scope and Objectives ....... 9
1.2 Constraints .... 9
1.3 Project Deliverables ... 9
1.4 Schedule and Summary .... 9
1.5 Milestone . 9
References . 10
Definition of Terms .. 11
Project Organization ... 12
1.6 Internal .. 12
1.7 External . 12
1.8 Roles and Responsibilities 12
Staffing Plan . 13
Work Plan .... 14
Process Model .... 15

List of Figures

List of Tables

Project Summary
1.1 Purpose, scope and
objectives__________________________________________________________ _______
The main purpose of CVS is to improved voting services to the students through
fast, timely and convenient voting. Require less number of staff during the election. This
system is a lot easier to independently moderate the elections and subsequently
reinforce its transparency and fairness.
The specific objectives of the project include:
Reviewing the existing/current voting process or approach
Coming up with an automated voting system
Implementing a an automated/online voting system
Validating the system to ensure that only legible students are allowed to vote.

1.2 Constraints
_______________________________________________________ _________
Time factor was the greatest barrier to the successful completion of this exercise since
it had to be done within the semester. The biggest constraints to be aware of will be
project submission date on 10/11/2016. The project team members are required to
work together regardless of the commitment of each member to deliver the final
product before deadline.

1.3 Project Deliverables

_______________________________________________________________
This project shall be finished on October 11, 2016, the end of first semester of
Software Engineering subject. All codes shall be written in PHP language. The testing
is done via XAMPPSERVER.

1.4 Schedule and Summary

____________________

_____________________
Software Requirement System

June 21, 2016

Software Project Management

Plan

July 7, 2016

Implementation (kick-off)

July 26, 2016

Project Completion

October 11, 2016

1.5 Milestone
_____________________

____________________

References
Bellis, M.

(2007). The History of Voting Machines.

Retrieved November 9, 2006 from:

http://inventors.about.com/library/weekly/aa111300b.htm
http://wwwis.win.tue.nl/2R690/projects/spingrid/spmp.pdf
Software Engineering- A practitioner's Approach by Roger S. Pressman: 6th edition
McGraw Hill, 2005

Definition of Terms
ABBREVIATION
CVS
CPC
SSC
Milestone

DEFINITION
COMPUTERIZED VOTING SYSTEM
CORDOVA PUBLIC COLLEGE
SUPREME STUDENT COUNCIL
An event that receives special attention. It is often put at the
end of a stage to mark the completion of a work package or
phase.

Project Organization
1.6 Internal

____________________

___________________ __
All the work on this project will be performed by Jubay, Rosende, Bautista, and Tual.
Jubay as a project manager meets with the team twice a week to discuss possible
changes and modification.

Roneth Jubay
PROJECT MANAGER

John Paul
Rosende
Monaliza
Bautista
DBMS-DEVELOPER

Cecile Marie Tual

TESTER

1.7 External

____________________

___________________ __

1.5 Roles and Responsibilities

_____

____________________

__

ROLES
Project Manager

Programmer

DBMS-Developer

Tester

RESPONSIBILITIES
1. Plans, organizes, coordinates, control the activities of the
group
2. Has the overall responsibilities for the success of the
project.
3. Leads the team in producing, assessing, updating, and
reporting on the plan.
4. Review of testing results and defects to determine/assess
impact to overall project plan and implementation schedule.
5. Review and Approval of the testing strategy, approach,
and plans.
1. Assist with design, analysis, maintenance, documentation,
and testing of software.
2.Code, debug, test, and document routine application
programs
3. Design new systems or enhancements to existing systems.
4. Verify that system meets performance criteria.
5. Advise or train users regarding the technical aspects and
use of standard software packages.
6. Design/modify, code, debug, test, and document
moderately complex application systems.
1. Collect information to analyze and evaluate existing or
proposed systems.
2. Prepare detailed flow charts and diagrams outlining
systems capabilities and processes.
3. Select among authorized procedures and seek assistance
when guidelines are inadequate, significant deviations are
proposed, or when unanticipated problems arise.
4. Write and maintain system documentation.
1. Execute and log the tests, evaluate the results and
document problems found.
2. They monitor the testing and the test environment, often
using tools for this task, and often gather performance
metrics.
3. Throughout the testing life cycle, they review each others
work, including test specifications, defect reports and test
results.

Staffing Plan
_Roneth Jubay_
PROJECT MANAGER

John Paul
Rosende
PROGRAMMER

Monaliza Bautista

Cecile Marie Tual

TESTER

DBMS-Developer

Work Plan
Week 1

SRS Chapter 1
documentation.

Introduction

and

Chapter

Overall

Description

Week 2

SRS Chapter 3 Specification requirements

Week 3

SPMP Chapter 1 Overview, Chapter 2 References, Chapter 3 Definition,

Chapter 4 Project Organization

Week 4

SPMP Chapter 5

Week 5

SPMP Chapter 6 Technical Process Plans and Supporting Process Plans.

Week 6

SDD Chapter 1 Introduction and Chapter 2 References.

Week 7

SDD Chapter 3 Decomposition Description and Chapter 4 Dependency

Description.

Week 8

SDD Chapter 5 Interface Description.

Week 9

SDD Chapter 6 Detailed Design.

Week
10

SDD Chapter 7 Appendices and Chapter 8 Index.

Process Model
A process model for software engineering is chosen based on the nature of the
project and application, the methods and tools to be used, and the controls and
deliverables that are required.
The model is used to build the COMPUTERIZED VOTING SYSTEM software is The
Prototyping Model. The prototyping paradigm is: - Water fall model

Fig.1.2 Waterfall Model

The waterfall model is a software development model in which a systems

development is viewed as flowing downwards through the phases of the system
development process. The waterfall methodology is powerful, prcised, and
thorough. It has a number of phases that have to be implemented in a sequential
manner.