1.

Introduction

1.1 Project Overview

Generally, the study focuses on the development of an automated voting system for the student council
election by the college and senior high school students of AMA Computer College Batangas. It is
designed to be deployed via a local area network. The system allows only the admin to register students
using their USN. This task which involves a large number of student data is made easier by the use of
CSV. The admin will then provide a unique password to each of the student-voters. The admin can
create teacher admins to help hasten the registration/activation of student accounts. Without the
activation from the admin/s, the students will not be able to access the system. This is an added security
enabled by the system to prevent students from using USN other than his or hers. Only after activation
users can cast their votes. A student can vote only once with the system. Any succeeding attempts to
vote using his or her USN will result to an error message informing the user that the voting token has
already been used up for that account. The admin also manages, edits, deletes and updates all the
candidates and students. The system has high security features to reduce false votes.

1.2 Project Deliverables

The project team will deliver a working system at the end of the project that satisfies the requirements.

Documentation will also be delivered by the project team during the course of the project.

2. Project Organization

2.1 Software Process Model

A system development methodology refers to the framework that is used to structure, plan, and control
the process of developing an information system. In developing this Capstone project, the iterative
model was used. Iterative model attempts to reduce inherent project risk by breaking a project into
smaller segments and providing more ease-of-change during the development process. The user is
involved throughout the process, which increases the likelihood of user acceptance in the final
implementation. Small-scale mockups of the system are developed following an iterative modification
process until the prototype evolves to meet the user’s requirements. A basic understanding of the
fundamental problem is necessary to avoid solving the wrong problem.

Figure 3.1 illustrates the steps involved in the Iterative Model.

2.2 Roles and Responsibilities

1. Project Leader

The project leader motivates the team members to perform their tasks. It helps the team in allocating
the tasks and resolving issues. It manages the budget, schedule, and all project procedures of the
project.

2. System Programmer

A system programmer encodes project requirements by converting work flow information into
computer language. It tests the system and finds and resolves problems.

3. Designer

Create visual concepts to communicate idea that is usable and desirable to use. It develops the overall
layout and design for the system.

4. Documenter

The documenter documents all information of the system.

5. Tester

The tester executes and logs the tests, evaluate the result and document problems found.
2.3 Tools and Technique

Analytical Tools

As system analysis tools, these are basically paper models of the would-be-system: that is, abstract
representations of what will eventually become a combination of computer hardware and software.
These were important tools used by the researchers to focus on important system features, define the
inputs, processes and outputs, and design the overall structure of the software product.

Program Flowchart. A flowchart is a diagram that depicts a process, system or computer algorithm.
They are widely used in multiple fields to document, study, plan, improve and communicate often
complex processes in clear, easy-to-understand diagrams. Flowcharts use different shapes to define the
type of step, long with connecting arrows to define flow and sequence.

Entity Relationship Diagram (ERD). Is a data modeling technique that graphically illustrates an
information system’s entities and the relationships between those entities. An ERD, is a conceptual and
representational model of data used to represent the entity framework infrastructure.

Use Case. It is a graphic depiction among the elements of a system. A use case is a methodology used in
system analysis to identify, clarify, and organize system requirement.

Data Flow Diagram (DFD). The DFD captures the main components of the information system and
represents the flow of data between them. More specifically, it is a graphical technique that depicts the
flow of information and the processes involved in transforming inputs to outputs. It is conceptual rather
than technical in the level of abstraction components are presented.

The proponents also applied development tools that are free and open- source. Since the website
contains dynamic pages, it is necessary to use PHP: Hypertext Preprocessor (PHP) which is embedded
into HTML. In addition, MySQL was used for the back-end application.

3. Project Management Plan

3.1 Task

3.1.n Task-n

1. Initialization

2. Requirements and Planning

3. Design

4. Implementation

5. Testing
6. Deployment

7. Evaluation

3.1.n.1 Description

Initialization. The whole process must be well-planned in its initial stages. Data were gathered, resources
were obtained, responsibilities were distributed among members of the research team and a time-
frame was laid out. This was to ensure the Capstone project was delivered within schedule using
available resources.

Requirements and Planning. This part plays a key role in the software development process. It was used
to gather information needed to give an insight into the product, its functionality, design, and
implementation. During development, the researchers established the system requirements. The
software application and the required specifications should adhere to the developing process. This is
essential to create a correct system.

Design. Design can be divided into architectural (preliminary) design and detailed design. In the
architectural design phase, the overall design for the software was developed, allocating all the
requirements to software components. In detailed design, the architectural design was expanded to the
33 unit level. Constraints and system resource limits were re-estimated and analyzed, and staffing and
test resources were validated.

Implementation. During this process, all the software programs were created and tested. In this process,
the researchers checked for technical accuracy and verified that it implemented the planned design.

Testing. During this phase the software units were tested for errors or bugs and were incorporated into
a completed system. Any non-conformance in this phase were detected, documented, and corrected;
and it was demonstrated that the system meets the requirements. The integration and test plans were
executed, the software documentation updated and completed, and the products finalized for delivery.

Deployment. Maintenance operation takes place after the system has been designed and developed
completely. The software was checked to see modifications were made to the software to maintain its
operational capabilities and to upgrade its capacity to support its users.

Evaluation. The final phase of the Iterative Model is evaluation which measures the effectiveness of the
system and evaluates potential enhancements. This was where the final product was tested out and
evaluated by the intended users.

3.1.n.2 Deliverables and Milestones

The tables below discuss the project deliverables and milestones with the corresponding purpose
or description and dates.
 Milestone List

Milestone Milestone Criteria Duration Date

Initialization Data were gathered, resources 06/28/2019

obtained, responsibilities were
distributed among members of the
research team and time-frame was laid
out.

Requirement Planning Requirements specifications are 06/28/2019

complete, finished, approved and
appropriate for design planning.

Analysis and design Overall designs were developed. 07/01/2019

Requirements were allocated to
software components.
Constraints and system resource limits
were re-estima

Implementation 07/09/2019

Testing and Deployment 07/16/2019

Evaluation 07/20/2019

Completion

3.1.n.3 Resources Needed

The system requirements for the LAN-based voting system, classified into hardware and software
requirements, are specified below to ensure that the system will function correctly. The system requires
an Internet browser to run the system. The hardware requirement is a laptop or equivalent machine
with the used and recommended specifications shown in Table 4.1.
 Table 2.1.1 Hardware Specification

Quantity Hardware Used Recommended

Intel Core i5 Intel Dual Core or

1 Processor
1.7GHz higher

4 GB DDR3 1 GB DDR3 or
1 RAM
Memory higher

1 Hard Drive 1 GB 500 Mb or higher

1366x768
1366x768
1 Monitor resolution or
resolution
higher

The used and recommended software requirements are also specified in Table 2.2.1.

Table 1.2.1 Software Specification

Quantity Software Used Recommended

1 Internet Browser Google Chrome Google Chrome

MySQL ver. MySQL ver.

1 Database Mysqlnd 5.0.12- Mysqlnd 5.0.12-
dev 20150407 dev 20150407
Operating Winhdiogwhesr7
1 Windows 8
System or
Apache Apache
1 Web Server
ver.2.4.23 ver.2.4.23
1 XAMPP V7.0.13 V7.0.13 or higher
Dependencies and Constraints

A windows-based computer with at least an intel dual core or higher processor and 1 GB DDR3 or higher
memory.

Windows 7 or higher.

Web-based SQL server.

Constraints

• The project constraints are as follows:

Time

Budget

Technical Knowledge

Risks and Contingencies

1. Inappropriate version of the tools and components.

1. Select specific versions of tools and components to use and every member will stick to the choice
throughout the entire project.

2. Failure to meet deadlines for deliverable.

2. Set up milestones ahead of time of the final due date for every deliverable.

3. Unavailability of resources.

3. Reassign resources to fill the gap.

4. Requirements change.

4. Aware the client of the amount of change that will be accommodated within the term of the project.

5. Accidental loss of valuable information.

5. The majority of the work will be done using online collaboration tools, including version control
software, and the subsequent documents stored online to minimize the chances of loss of data.

5. Copies of work not stored online will be kept by all team members.

6. System contains bugs/ errors.

6. The entire team will plan and perform in-deep testing and debugging phase in order to avoid system
bugs.

7. System fails to connects with the database.

7. The entire team will plan and perform in-deep testing and debugging phase to avoid database
connection problems.

Assignments

Timetable

Access to Admin Page

Administrator

Administrator logs in and connects to the Administrator page where he will have access to create a new
election, modify an election, voting, tally and/or decrypt the votes. Connect to the network via actor
network. Connect to the database via actor database.

1.User enters username and the password. The username and password are assigned and given to the
users earlier. According to the username, system will connect the user to the Administrator page or
directly to the voting page. If user is the administrator, he will be connected to the admin page and will
have access to the admin links.

Users

This use case describes how to access to the e-voting system.

Invalid usernames and passwords will not be logged in and will have error pages displayed.