DESIGN AND DEVELOPMENT OF A TRAFFIC TICKETING SYSTEM FOR PUBLIC

ORDER AND SAFETY OFFICE SAN CARLOS CITY, PANGASINAN

A Capstone Presented to the Faculty

of the Pangasinan State University
San Carlos City Campus
San Carlos City, Pangasinan

In Partial Fulfillment
of the Requirements for the Degree
________
Major in _______

Name:

February 2022
 CHAPTER 1

INTRODUCTION

Globalization and scientific and technological advancements had profound effects

on people’s lives. A closer examination of the consequences reveals that a very practical

and modern style of life prevails in nearly every part of people’s lives, including the

legal side. People’s levels of crime and offenses are also affected by technological

advancements, because they are intertwined, law and society are inextricably linked.

The prosecution of offenses and the handling of traffic accidents are covered by law

enforcement in the field of road traffic and transportation.

The information of the offender, the type of offense, the location of the offense,

the evidence demanded, the time of trial, and the data of the law enforcement officer,

as well as the signature, are all listed on a traffic ticket.

(https://www.researchgate.net/publication/2016.)

Violations of traffic laws on the roadways had been on the rise for a few years.

As we all know, the majority of young people are interested in these types of activities,

where they break the regulations and do not follow the city’s traffic code of conduct.

They had the freedom to drive their vehicles or motorbikes whenever they choose.

There are several causes for this, one of which is that there is no strict supervision of

children nowadays.

The important area of traffic enforcement and the associated aspects of

education and encouragement are considered. Unless traffic management was logically

applied and consistently enforced, it would not be effective. Enforcement must be

considered an integral part of traffic management. To ensure that the fundamental

purpose of each road was identified, agreed upon, and understood, a taxonomy or

hierarchy of all roads must be developed as a foundation for logically implementing

traffic management approaches. The author describes a functional classification of

roads appropriate for traffic management and a process for constructing such a system.

Signage and delineation, pedestrian and bicycle facilities, intersections, traffic signals,

road capacity, parking, roadside safety, and roadway lighting are only a few of the

topics covered in the following chapters. The crucial field of traffic enforcement, as well

as the related factors of teaching and encouragement.

Road safety one of the major subjects within the transport policy of the City of

San Carlos. Most traffic accidents are caused by driver inattentiveness. Drivers are often

unaware of their lack of concentration or the distracting effects that in-vehicle chores

have on their performance. In this context, the majority of traffic violations, such as

speeding or ignoring stop signs, are unintentional and they occur due to the lack of

concentration rather than because drivers deliberately intend to break the law.

The proposed project, Design and Development of a Traffic Ticketing System for

the Public Order and Safety Office of San Carlos, aimed to address issues with driving

infractions. The goal of this proposed project was to optimize the manual process or

transaction order in order to streamline all procedures.

The problem cited for this research is the inconveniences brought to the traffic
enforcers by taking so much time in writing and signing to the Local Ordinance Violation

Receipt, that describes the violation of the drivers being called or apprehended for

traffic violations. Another problem for the apprehended traffic violators was due to the

time given for the traffic enforcers to note the traffic violations; it gives more time for

both the enforcers and violators to negotiate on the said violations.

1.1 PROJECT CONTEXT

In today’s generation, motorist tend to become defiant at traffic laws on the

roads and become reckless when it comes to public order, safety, discipline, and road

awareness. Most of the time, motorists are unaware of the implications of their

ignorance of traffic regulations and offenses, which may result in them receiving

citation tickets from traffic enforcers. Consequently, they have to abide inconveniences

by going to the traffic authority office to pay a respective amount, due to their

violations.

The problem cited for this project is the inconveniences brought to the traffic

enforcers by taking so much time in writing and signing to the Local Ordinance Violation

Receipt, that describes the violation of the drivers being called or apprehended for

traffic violations.

The traffic enforcers are responsible for implementing rules and laws, and

making sure that the traffic is moving smoothly as possible, and motorists comply

diligently when using public roads. They are also responsible if the motorists wear

proper dress codes, registered their vehicles and complete papers, including their
driving license. Also, one of their main objectives is issuing a citation ticket, if the

motorists tend to violate any rules. As a guide for the traffic enforcers, he refers to their

paper citation ticket be able to take action.

This project is focused on the design and development of traffic ticketing system.

The proposed system is bounded by some restrictions. It includes advantages and

disadvantages of the system. The proposed system is faster and efficient in forwarding

the data on the server.

This will also help the File Administrators in the head office to receive complete

citation reports that will drastically save administration time.

The technological developments also have impacts on levels of crime and

offenses committed by people. Law and society are two inseparable things since they

are interrelated. Law enforcement on Road Traffic and Transportation covers the

prosecution of violations and handling of Traffic Accidents.

1.2 PURPOSE AND DESCRIPTION

The goal of developing a ticketing system was to assist and improve the POSO San

Carlos’ effectiveness, to quickly find the ticket’s issues, violations, information, and

status. The used of a traffic ticketing system can make it easier to respond to a client’s

complaint. It can readily handle the issues that their clients have mentioned. This

system can help them strengthen their skills in resolving and learning about various

problems that arise, throughout the implementation of the system, and the proponents

are kept informed about what is going on.

 This project was conducted to design and develop a Traffic Ticketing System for

Public Order and Safety Office (POSO) San Carlos.

The proposed project was bounded by some restrictions. It was consists of

advantages and disadvantages of the system. The proposed project is faster and

efficient in managing the data on the system. The POSO administrator has the rights to

manage and control the system. Authorized officers inside the office has limited access

and they can’t change or edit the data. It also accessible by the users or violators but

they can only view their records and they don’t have the rights to control and manage

the system.

1.3 OBJECTIVES OF THE PROJECT

The main objective is to Design and Development of a Traffic Ticketing System in

Public Order and Safety Office San Carlos City.

1. To identify the current ticketing procedures at POSO San Carlos;

2. To describe the features in the design and development of the system;

3. To describe the hardware and software specifications of design and

development of the system; and

4. To test the acceptability of the developed system.

This project aimed to create a web-based system that would serve as the primary

platform to simplify the recording and managing of traffic ticketing for POSO San

Carlos. Manual recording of motorists’ traffic violation can be tedious and inefficient.

Paper citation ticket can be damaged and has possibility to be lost before traffic
enforcers submit it to the head office. Also, corruption is currently rampant to the Public

Order and Safety Office (POSO) San Carlos, which results to collection loss.

Generally, the project aims to:

Design and Develop Traffic Ticketing System for Public Order and Safety Office

San Carlos, so that it would gave the traffic enforcers, and file administrators an

alternative and efficient way of submitting, recording, and viewing of violators.

Specifically, the study aimed to enable Public Order and Safety Office

(POSO) San Carlos to submit citation ticket using a web-based system. Second, is to

lessen the difficulty of recording and managing traffic violations. Third, to enable the

traffic enforcers to send violation activities of motorists, and lastly is to enable file

administrators to manage records and generate printout figure of every violation of

motorists.

1.4 SIGNIFICANCE OF THE PROJECT

The researchers presented the importance or relevance of the project in this

section and this is where important contributions from the study outcomes are

enumerated.

The traffic ticketing system’s development is the very core in improving the

existing manual process of Public Order and Safety Office which can be benefited by the

following:

Public Order and Safety Office. The deployed system will aid in making the
process of record management on vehicle violation management easily. The agency

will no longer have to deal with the time-consuming process of claiming a license. This

will also help them in locating files and records on traffic violation and be more aware

of any traffic incidents that may occur which in return will help in resolving the

occurred problem.

Driver/Violators. Through the developed system it will give ease to the violator

in claiming of their confiscated license for traffic violation because of the system’s

capability on viewing the lists of confiscated license. With the developed system it will

help the violators check their penalties through the online capability of the system.

Municipality of San Carlos City. With the online reporting of traffic incidents

of the system the citizens will be aware of any road blockage or traffic congestion and

can think of a different route. The citizens of San Carlos City will be more aware of any

traffic incidents that may occur.

Developers. The developers will enhance their knowledge, skills and experience

on how to work as an IT professional. This will also serves as a training ground that

will prepare them to face the challenges of the changing world.

Future Developers. This may serve as their reference or guideline if they intend

to develop similar studied. And they could enhance the system by adding new features

and modifications.

1.5 SCOPE AND DELIMITATION

This study aimed to design and develop a Traffic Ticketing System for Public
Order and Safety Office (POSO) on the existing manual traffic ticketing system in San

Carlos City, Pangasinan. The proposed system regulated by the Public Order and Safety

Office's was simple to use and had a pleasing user interface. It is necessary for

management and staff to have system user credentials in order to access the system's

data and functions.

Moreover, the system, the features, hardware and software specifications of

design and development of the system were also considered.

Furthermore, the system has three (3) levels of user which are the

administrators, the officers, and the drivers or violators. The administrators can control,

access and manage all the data and features of the system while the officer has only

limited access and the drivers/violators are capable to view only their records and

account information. This system stores the list of traffic offenses and along with this

data was the fine or penalty rate in each of these, but it can’t accept payment directly.

In every traffic offense ticket, the violator can be fined for multiple offenses. This

project also generates a printable Driver’s Information and Records, Traffic Offense

Ticket, and Reports.

The system helped the users to have secure access but limited, and they couldn’t

easily access the system without data connection. It also included the peripheral

problems that may caused by its limitations such as power interruption, and data

connection failure. The information of the offender, the type of offense, the location of

the offense, the evidence demanded, the time of trial, and the data of the law

enforcement officer, as well as the signature, are all listed on a traffic ticket.
 The system was operational within the vicinity of San Carlos City, Pangasinan. In

addition, renewal of licenses was not supported by the system.

CHAPTER 2

REVIEW OF RELATED LITERATURES AND SYSTEMS

The literature and studies cited in this chapter tackled the different concept,

understanding, and ideas, generalization or conclusions and different development

related to study of the traffic ticketing from the past up to the present and which serves

as the researchers guide in developing the project. The literature reviewed here

provided the researchers insights into the subject matter of the present study. It also

consists of the Technical Background, Related Literatures, Related Studies, Synthesis,

Conceptual Framework, and Definition of Terms.

The concepts and conducted studies related to the phenomenon of traffic

ticketing were also included in this chapter helps in familiarizing information that are

relevant and similar to the present study.

2.1 TECHNICAL BACKGROUND

This part of the project presents the technical solution of the study which

includes the hardware and software requirements where the developers used in
developing of the project Design and Development of a Traffic Ticketing System for

Public Order and Safety Office San Carlos City, Pangasinan.

Hardware Requirements

Computer hardware refers to the physical parts of a computer and related

devices. Internal hardware devices include motherboards, hard drives, and RAM.

External hardware devices include monitors, keyboards, mice, printers, and scanners.

This includes the personal computer.

Software Requirements

Software is a general word that refers to computer programs. Computer software

includes related concepts such as software programs, applications, scripts, and

instruction set. As a result, installing new programs or apps on your computer is

synonymous with installing new software.

Because software is "virtual," or not tangible like computer hardware, it may be

difficult to define. Instead, software is made up of lines of code that have been

compiled into a computer program by computer programmers. When a software

application is installed, it is saved as binary data that is transferred to the hard drive of

the computer. Because software is virtual and takes up no physical space, it is far

simpler (and typically less expensive) to update than computer hardware.

While software, at its most basic level, consists of binary code, CD-ROMs, DVDs,

and other forms of media used to transfer software may also be referred to as
software. As a result, when you purchase a software program, it is often packaged on a

disc, which is a physical medium for storing the software.

2.2 REVIEW OF RELATED LITERATURES AND SYSTEMS

For further understanding of the project, the researchers made used of different

reading materials related to the “Design and Development of Traffic Ticketing System”.

These materials such as books, magazines, newspapers, thesis, and other web articles

are essential in broadening the knowledge of the researchers. These would also guide

the researchers to achieve their target objectives by getting ideas on other related

studies and make improvements as possible.

2.1.1. RELATED LITERATURE

The literature and studies cited in this chapter address various concepts,

understandings, and ideas, generalizations or conclusions, and diverse developments

connected to the system from the past to the present and serve as the researchers'

guidance in constructing the project. Those included in this chapter also help to

familiarize the reader with knowledge that is relevant to and comparable to the current

research.

2.1.2. RELATED STUDIES

LOCAL LITERATURE
 a.) Leoncio, A., & Camata, F. (2017). MMDA E-Ticketing System.

In light of these findings, the proponents concluded that; based on the result of

our surveys, the motorists believed that the proposed system is more effective and

efficient than the manual system they currently used. Most of the driver-respondents

believed that the manual ticketing can be improved into automated ticketing system

which is more capable and efficiency than the existing system. The proposed system

includes confirmation on printing of the ticket to generate reports of violator’s record

and previous transaction with less error than the existing system. The proponents also

put the proposed system online and real time application on recording actual traffic

violation, and record it directly via mobile signal, through a secured internet access data

storage system and reporting it to the central office. The respondents are satisfied with

the proposed ticketing system by using android phone and IMZ series mobile printer

provides lesser time in the process of issuing ticket. The proposed system is faster and

secure to use than the existing system. The more the time spent on negotiation, will

usually lead to corruption or bribery. So as to mitigate the effect of corruption and/or

bribery, the system that the research seeks to solve is transparency. In the sense that,

actual and real time reporting should be done simultaneously with punching the

violation.

b.) Mangahas, M.C. (2019). An Assessment on the Coordination of the Metro

Manila Development Authority with the Local Government Units of

Mandaluyong, Makati, Taguig, and Quezon City in Addressing Traffic

Congestion.

Based on the findings of this paper, if the unification of traffic policies of the

LGUs in Metro Manila is still not evident and existing, the responsibility of the

coordinating mechanism would primarily be relegated to the MMDA. The local

governments would also be accountable but only because they are given the power and

autonomy on their own cities as per mentioned in the LGC. MMDA would be held

responsible because of their failure to create a better coordinating mechanism with the

local governments in solving traffic congestion in EDSA and C-5. Although, it has also

been found out that traffic congestion is not that much a result of incoordination

between the LGUS and MMDA, but also due to the confusion and conflict that the lack

of coordination between the institutions involved gives to the motorists and other

groups affected.

The coordinating mechanism presently used by the MMDA with the LGUs in

solving traffic congestion achieved mixed results when observed through the indicators

used in this paper. In the socio-legal factor, both MMDA and the LGUs know where they

stand – they know their own and the other’s mandates and institutional framework.

Secondly, in the socio-technical factor, communication through regular monthly

meetings among the LGUs is an evident factor that there is a communication scheme.

However, in regards to the existence of i-ACT, only MMDA, Taguig, Makati, and Quezon

City are said to have successful communication schemes.

Finally, in the socio-psychological indicator, MMDA is aware that they are an

administrative body that should create a step towards an inter-organizational

relationship between them and the LGUs in Metro Manila. On the other hand, the LGUs

are also knowledgeable of their power as autonomous bodies that are granted authority

to create and alter policies based upon the needs and situation of their local

communities. However, due to the fact that they are working separately and deviate

from the unified traffic schemes they created through the MMC, they have difficulties in

identifying which institution should be followed on specific roads.

These results show that the coordinating mechanism exercised by the MMDA

with the four chosen LGUs in addressing traffic congestion in specific Metro Manila

roads were partially effective but still have significant flaws. While MMDA is on the right

track in terms of MMC holding regular monthly meetings, there are still some gaps in

their coordinating mechanism which is essentially needs to be addressed.

c.) Frialde, M. (2016). Metro Manila Adopts Uniform Traffic Violation Ticket

According to the MMDA, Resolution No. 12-02 or "Adopting a Uniform Ticketing

System" was approved following a study conducted by a technical working group.

Under the new unified ticketing and penalties system, penalties for traffic violations

would now range from P500 for such violations as "disobedience to traffic signs" to

P2,500 for operating a taxi with a defective or tampered meter.

It would be recalled that a uniform ticketing system was earlier made effective

for traffic violations across Metro Manila. However, the MMDA and the various local

government units could not agree on a uniform schedule of fines for violation.

The MMDA earlier argued that there is no need to have a uniform set of fines for
violations under a single traffic violation ticketing system.

The single traffic violation tickets now being used are called the Unified

Ordinance Violation Receipts (UOVR), bearing the logos of the MMDA, the Land

Transportation Office (LTO) and the 17 Metro Manila LGUs. The UOVR is designed to be

tamper-proof and will have several security features to prevent forgery.

With the use of the UOVR, a motorist who gets apprehended for a traffic

violation and gets his driver’s license confiscated, can use the single traffic violation

ticket as temporary license. Should the motorist be flagged down in another city, he will

no longer be issued another traffic violation ticket for driving without a license on

presentation of his UOVR.

The MMDA says the UOVR is valid only for a single common offense. Should a

motorist be issued an UOVR in one city for speeding, he could be issued another UOVR

for committing another violation in another city, such as beating the red light.

Prior to the approval of a uniform set of fines, each LGU imposes its own set of fines for

traffic violations with Makati and Quezon City having stiff fines for traffic violations,

The MMDA said the UOVR will also be recognized by traffic enforcers of the LTO.

d.) Sabio et al., (2016). TRAFFIC MANAGEMENT CENTER'S ENFORCEMENT

AND TRAFFIC COLLISION IN DAVAO CITY.

Based on the findings of the study, the researchers conclude that the traffic

enforcement of the Traffic Management Center in Davao City and the traffic collision

are manifested but may differ on how the traffic enforcers used their ability on traffic
direction and control as well as apprehending traffic violators. Similarly, vehicular

accidents and accidents involving pedestrian may be attributed on how the drivers

respond to policies and how the traffic enforcers police their areas of responsibility. This

study is based on the work of Akers (1990) on rational choice, deterrence and social

learning theory which believed that people choose to obey or violate the law,

specifically traffic laws, after calculating the gains and consequences of their actions.

However, it is difficult to prove the effectiveness of deterrence since only those

offenders not deterred come to the notice of law enforcement. This affirms the study of

Siegel (1992) that law-violating behavior should be viewed as an event that occurs

when an offender decides to risk violating the law after considering his or her personal

situation and situational factors. This means that a person evaluates the risk of

apprehension, the seriousness of the expected punishment, etc. Ultimately, we can say

that when traffic enforcement is highly enforced, traffic collision will be minimized.

Accidents on pedestrians and traffic signs and other related problems on traffic can be

attributed on how the bystanders understand traffic rules policies.

e.) Suarez, A. (2016). Single Ticketing System in Expressways.

According to an article posted at the government's Public-Private Partnership

website, DOTC Secretary Joseph Emilio Abaya said that the single ticketing system

would eventually be implemented in toll collection at various expressways.

f.) Acorin. (2017). E-Ticketing System of Traffic Management Group of

Zamboanga City.

Traffic violations occur when a driver violates a traffic law, these are the laws

created by the government to be followed by the citizens of the Philippines. These piece

of legislation is found at Republic Act No. 4136 “An act to compile the Laws relative to

Land Transportation and Traffic Rules, to Create a Land Transportation commission and

for other purposes”. In the Philippine Constitution the driving violations is divided into

four categories: Violation in connection of Licensing, (ii) Violations in connection with

motor vehicle registration/renewal/operation, (iii) Violation in connection with

dimensions, specifications, weight and load limits, (iv) Violation in connection with

franchise” (Fines and Penalties for Violations of Laws, 2014). Max speed Auto portal

Inc. (n. d ).

Listed the 10 most common driving violations in the Philippines: Disregarding

Traffic Signs, Obstruction, Number coding or Color coding, Illegal Parking Stalled

Vehicle, Loading and Unloading in Prohibited Areas, Truck ban, Reckless Driving,

Motorcycle lane policy, Illegal Counter flow. Retrieved from-philippines-respective-fines-

2770.Organizations that are responsible for dealing the driving violators are: Land

Transportation Office (LTO), Land Transportation Franchising and Regulatory Board

(LTFRB), Traffic Management Group (TMG), Metropolitan Manila Development Authority

(MMDA). Land Transportation Office (May,2017) These law enforcers from different

organizations main goal is to implement and enforce the laws regarding land

transportation. Law enforcers from LTO used TOP or Temporary Operators Permit and

from the Local Government they used Citation form or City Ordinance form to
apprehend all violations and it is strictly required to be issued to the violator at the

location and time of apprehension, this will also serve as the driver’s temporary permit.

FOREIGN LITERATURE

a.) Jang, Y.M. (2016). Enabling Smart Traffic Violations Ticketing in

Vehicular Named Data Networks.

In this study, we present an architecture for a smart and efficient traffic violation

ticketing system for vehicles with future Internet technologies such as NDN. Our

architecture will enable traffic law officials to identify drivers and violating vehicles

without chasing and putting lives in danger. In order to achieve this, we apply basic

VNDN operations into our Smart Cop system, where a cop vehicle periodically

broadcasts an Interest packet for violation entries saved by every ordinary vehicle in its

local memory (PTE). This exchange of PTE enables a cop vehicle to issue a relevant

ticket to the offender. Later on, the offenders’ vehicle, when connected to any road side

unit, pays the charged ticket autonomously. As a result, all the manual operations and

delays caused by human errors are skipped. In the end, we also enlist the future work

directions for improving and implementing our proposed Smart Cop system into real

test-bed environments and simulations. The simulations show that the ticket issuing

delay and its messaging cost depend upon the number of violators, vehicles, and speed

of the vehicles on the road.

b.) Shamsunnahar, Y. (2019). Modeling and Analysis of Ticketing Channel

Choice for Intercity Bus Passengers: A Case Study in Beijing, China.

The data used in this study originate from a survey that took place in Beijing, the

capital of China, in March 2018. The questionnaire is designed with the aim of capturing

passengers’ ticketing channel choice behavior and the multidimensional nature of bus

passenger transportation. There are four major sections in the questionnaire. The first

section investigates ticketing channel choice through three questions. The second

section contains 12 questions about attitude of passengers to the ticketing channel

adopted. The third section includes six questions about trip characteristics of the

respondents. The fourth section is composed of five questions focusing on the

sociodemographic information of the passengers.

This study investigates demographic information, trip characteristics, and

respondents’ current ticketing channel choices. In terms of ticketing channel usage, we

provided five distribution channels for respondents to choose from, including service

counters at a station, ticketing agencies, websites, and apps. Passengers could mark

their current choices across the ticket purchasing process, and this enabled us to

understand passengers’ current channel preference. We also investigated trip

characteristics related to trip frequency, trip purpose, decision-making period prior to a

given trip, and the timeframe prior to any given ticket purchase. We only required

participants to report the current trip, including business trip or nonbusiness trip. The

sociodemographic information collected in the last section of the questionnaire

encompassed questions regarding gender, age, education background, occupation,

monthly income, etc.

c.) Zhu, L. (2018). An Efficient Traffic Congestion Monitoring System on

Internet of Vehicles.

This paper proposes a distributed traffic congestion monitoring system on the

IoV. The system responsively reacts to numerous requests concerning the traffic

congestion situation by combining the advantages of MQTT, a lightweight protocol that

has the ability to support low-bandwidth and high-latency vehicular environments, and

VD sensors, which have high reliability and accuracy in traffic-flow monitoring.

Furthermore, real-time data were used to formalize the traffic-flow factors and predict

traffic congestion states through a fuzzy rule-based scheme. The proposed system not

only effectively monitors traffic congestion but also reduces response time. The

designed traffic congestion verification process can help in improving local traffic

congestion prediction efficiency, and origin-destination traffic congestion service

improves service quality, which will be provided for drivers. Experimental results

showed that the proposed system was effective in predicting traffic congestion states in

terms of accuracy and system response time. In future studies, the authors intend to

improve the system’s flexibility by enhancing the segmented structure to a hybrid

structure in which traffic-flow estimation can be based on both VD sensors and vehicle-

to-vehicle communications. The authors additionally intend to improve local segment

traffic congestion prediction and origin-destination traffic congestion service for

suitability with the hybrid segmented structure.

d.) Fuzhong, N. (2018). Self-Adapting Routing Overlay Network for

Frequently Changing Application Traffic in Content-Based Publish/Subscribe

System.

In this paper, we propose a self-adapting routing strategy for frequently

changing application traffic in content-based publish/subscribe system. The strategy

firstly trains the traffic information and then uses this training information to predict the

application traffic in the future. Finally, the strategy reconfigures the topology of the

overlay network based on this predicting information to reduce the overall traffic cost. A

predicting path is also introduced in this paper to reduce the reconfiguration numbers in

the process of the reconfigurations. The experimental results show that the strategy

could reduce the overall traffic cost of the publish/subscribe system in less

reconfigurations. In the future work, we will implement our strategy in our prototype

system.

e.) Dongkyun et al., (2015). Towards Content-Centric Traffic Ticketing in

VANETs: An Application Perspective.

In this paper, we present an architecture for a smart and efficient Traffic

Violation Ticketing system for vehicles with future internet technologies such as CCN.

Our architecture will enable traffic law officials to identify drivers and violating vehicles

without chasing and putting lives in danger. In order to achieve this, we apply basic

VCCN operations into our TVT system, where a cop vehicle periodically broadcast an

interest packet for violation entries saved by every ordinary vehicle in its local memory
(PTE). This exchange of PTE enables a cop vehicle to issue a relevant ticket to the

offender. Later on, the offenders’ vehicle when connected to any road side unit, pays

the charged ticket autonomously. In result, all the manual operations and delays caused

by human errors are skipped. In the end, we also enlist the future work directions for

improving and implementing our proposed TVT system into real test-bed environments

and simulations.

f.) Capuni et al., (2015). A Police Traffic Ticketing System with Autonomous

Vehicles.

In order to be able to compute the ought to set, we use a non-sophisticated

method of repeating the same time dependent secret at two consecutive times. For the

same reason, a vehicle releases information about its precise location in plaintext. The

first open question would be if there is such a cryptographic tool that allows us to drop

these –somewhat harsh – constraints. Second, a further validation of the result should

be made using a real implementation.

g.) Hurtado, D. (2015). INTEGRATED TRAFFIC TICKETING MANAGEMENT

SYSTEM.

In conclusion, traffic police corruption is a problem that cannot be addressed

with a single program. These joint strategies are feasible to implement since many of

the aspects proposed herein are already undertaken at different levels or scopes by

different agencies. However, the author is convinced that the idea of having a
coordinating local agency (ITtiMS) in charge of the whole ticketing system is essential

for the success of such efforts. ITtiMS would manage the system and track its

effectiveness thought performance measures. Moreover, it will create a basic platform

for the implementation and adjustment of various different strategies, not only to

reduce police traffic corruption, but also increase the effectiveness and efficiency of the

whole system.

h.) Wang, J. (2016). Event-Driven Traffic Ticketing System.

In the first chapter, we firstly introduced the significant role of video event

detection in our society and the corresponding computer techniques. The motivation

and structure were also detailed respectively in this chapter. As our goal was to study

the computer vision technique and develop an event detection application, a novel

schema of event-driven traffic ticketing system was proposed in this thesis. The whole

system consists of four primary modules, event detection module, plate number

recognition module, database management module and traffic tickets notification

module. Followed by the structure created in first chapter, the second chapter

conducted a detailed literature review. The-state-of-the-art of moving object detection

and license plate recognition methods were summarized in this Chapter. In addition, the

considered techniques and algorithms were evaluated for achieving the objectives of

this thesis. After reviewing multiple papers, the research question and methodology

were present in Chapter 3. The specific experiment design and implementation were

introduced in Chapter 4. This chapter was made up of two important modules, event
detection and plate number recognition, in the entire system. In event detection

module, foreground detection method was used to detect the passing vehicles. Then, a

combination of points features extraction and KLP was used to track the captured

vehicle. After analyzing whether the trajectory of moving vehicle meets the probability

of a predefined event occurrence, the state signal will be sent to trigger the plate

number recognition module. In the module, a novel dual scan method (Secondary

Positioning) was introduced to localize the plate number area. A rough area contains

plate number will be cropped by the first scan, which search the red pixels in HSV

colour space. The specific plate number was extracted by the horizontal and vertical

projection of its edge information in the second scan. Then, the character recognition

processes will be conducted by template matching. The system will send traffic ticket

notification information to the owner of the plate number registered in the database of

the system. The other two modules are implemented in MYSQL database and MATLAB.

Chapter 5 showed our experimental results and discussion about the involved methods.

Additionally, this thesis analyzes the core algorithms and approaches which are

suitable for this system. Due to the importance and influence of the plate number

recognition module, this thesis focuses on analyzing computer vision techniques with

respect to implement plate number recognition. The given methods and algorithms in

this thesis answer the research question of this thesis. Further, this thesis also improves

the traditional Template Matching method used in character recognition. Specifically,

the character templates are grouped into four classes according to the symmetric

characteristic of characters. Results show the improved method has a better

performance than traditional one.

I.) Iksan, M. (2019). The Benefits of the E-Traffic Ticketing (E-Tilang) System

in the Settlement of Traffic Violation in Indonesia.

The benefit of E-Ticket in the settlement of online traffic violations is the

digitization of the ticketing process, by utilizing this technology in recording

transnational offenses and the ticketing process will be more effective and efficient as

well as assisting the police in administrative management. E-ticket is an application that

can be utilized by the community where people can know the cost to be paid directly.

This application can be used by two users, the first is the police and the second is the

judiciary. On the police side, the system will run on a tablet computer with the Android

operating system while on the prosecutor's office the system will run in the form of

websites, as executor such as manual trial process.

The E-Ticket application does not apply the function as an introduction to pay a

fine to the Bank/Registrar because the mechanism involves a form or a ticket paper, on

an E-ticket form or a proof of violation paper is not used, this application only sends a

reminder in the form of a ticket ID which stores all data or records Police regarding the

chronology of a speeding ticket to be given to a court or prosecutor's office with a

website with the same database integration. The obstacles are the number of people

who do not yet understand how to solve E-ticket, have no E-ticket downloaded app on

Android, violators have no account at Bank, network application accessibility with dual

band 3G / 4G, and the public assumption that E-ticket system as a process convoluted.
2.1.3. SUMMARY OF RELATED LITERATURE

Table 1. Summary of Related Literature

Article/Title Advantages Disadvantages

MMDA E-Ticketing System is more Only the authorized

MMDA E- effective and efficient than the personnel can

Ticketing manual system they currently access the system

System used. Most of the driver- with the use of its

respondents believed that the username and

manual ticketing can be improved password for the

into automated ticketing system security purposes.

which is more capable and

efficiency than the existing system.

The proposed system includes

confirmation on printing of the

ticket to generate reports of

violator’s record and previous

transaction with less error than the

existing system. The proponents

also put the proposed system

online and real time application on

recording actual traffic violation,

 andrecord it directly via mobile

signal, through a secured internet

access data storage system and

reporting it to the central office.

Enabling Smart In this study, we present an Only the authorized

Traffic Violations architecture for a smart and personnel can

Ticketing in efficient traffic violation ticketing access the system.

Vehicular system for vehicles with future

The simulations
Named Data Internet technologies such as NDN.
show that the ticket
Networks Our architecture will enable traffic
issuing delay and its
law officials to identify drivers and
messaging cost
violating vehicles without chasing
depend upon the
and putting lives in danger. In
number of violators,
order to achieve this, we apply
vehicles, and speed
basic VNDN operations into our
of the vehicles on
Smart Cop system, where a cop
the road.
vehicle periodically broadcasts an

Interest packet for violation entries

saved by every ordinary vehicle in

its local memory (PTE).

 2.3. SYNTHESIS

All the literature and studies reviewed were contributory to the present study in

one way or another. The concepts mentioned on Traffic Ticketing System were

relevant to the present project because these served as foundation in the development

of Traffic Ticketing System without the use of paper all acts of traffic violation are

recorded by the digital system thereby reducing the cost of paper as a proof of

infringement. By utilizing technology, the whole process of speeding tickets will be

more efficient and also effective also help the POSO personnel in administrative

management. The concept on Traffic Ticketing System is used as basis by the

researchers in the formulation of the proposed project to be considered in the features

that should be included in the development of the project.

2.4. CONCEPTUAL FRAMEWORK

A concept map is a diagram that illustrate the Input, Process and Output

between the concepts. It is a graphical tool that is often used by graphic designers,

engineers and architects to structure and organize knowledge. Conceptual maps

typically depict ideas and information as boxes, which are connected with label arrows

in a hierarchical structure that is downward branching. This project made use of the

system’s analysis of input, process, and output. The input phase consists of the

Administrator login, Officer login and User’s login. The process phase consists of

analyzing the gathered and analyzed data of the system user. The result of this study

under the output phase will be proposed Design and Development of Traffic Ticketing

System for Public Order and Safety Office San Carlos.

 INPUT
Users:
 Admin PROCESS
 POSO personnel
OUTPUT
 Driver/Violators

Procedures: AGILE SCRUM

DESIGN AND
 Violations/ METHODOLOGY
DEVELOPMENT OF A
Penalties Initiate TRAFFIC TICKETING
 Records Planning SYSTEM FOR PUBLIC ORDER
Implementation AND SAFETY OFFICE
Requirements Review and SAN CARLOS CITY,
 Hardware Retrospect PANGASINAN.
 Software Release
-XAMPP
-PHP

Feedback

Figure 1. Paradigm of the Study

CONCEPTUAL MAPPPING

The developers used Conceptual Mapping to illustrate and explain the process in

order to come up with the final output. The figure below shows the conceptual mapping

of the Design and Development of Traffic Ticketing System for Public Order and Safety

Office San Carlos.

 Figure 2. Conceptual Mapping

2.5 DEFINITION OF TERMS

The following terms are operationally and briefly defined to let the readers have

a clearer understanding on the concepts and idea used in this study:

Administrators. Refers to the end-users of the system, the administrator holds

all the data, control, maintain, and routinely perform duties to improve utilization of the

proposed Traffic Ticketing System.

Citation Ticket. Civil Traffic Citation is a noncriminal traffic violation that is not

punishable by incarceration and for which there is no right to a trial by jury or a right to
court-appointed counsel.

Fine. A penalty of money that a court of law or other authority decides has to be

paid as punishment for a crime or other offense. The amount of a fine can be

determined case by case, but it is often announced in advance.

License. A driver's license is issued on a state-by-state basis and the right to

drive is a privilege which may be revoked, suspended, or cancelled for failure to comply

with state or municipal driving laws and regulations.

Public Order and Safety Office (POSO). An agency within the Municipality

of San Carlos City that is in charge of setting policies concerning traffic control. It is also

responsible in coordinating and regulating the implementation of all programs and

projects concerning traffic management specifically those that pertains to enforcement,

engineering and education.

Road Traffic Safety. Refers to the methods and measures used to prevent

road users from being killed or seriously injured.

System. It refers to any group of component pieces that work together to

complete a purpose.

Technology. It is the application of scientific knowledge for practical purpose,

especially in industry.

Traffic. The term "traffic" includes slow movement or congestion of pedestrians,

ridden animals, vehicles, street cars, and other conveyances, either singly or together,

while using any highway for purposes of travel.

Traffic Accident. An increasing cause of death and injury around the world,
and several countries have launched road safety.

Traffic Codes. Are laws that generally include provisions relating to the

establishment of authority and enforcement procedures, statement of the rules of the

road, and other safety provisions.

Traffic Ticket. A notice issued by a law enforcement official to a motorist or

other road user, indicating that the user has violated traffic laws.

Traffic Violation. Traffic violation is any violation of vehicle laws that is

committed by the driver of a vehicle, while the vehicle is moving. Such violations are

also referred to as moving violations. Laws relating to moving violations and the

associated penalties vary by jurisdiction (Moving Traffic Violation Law & Legal

Definition, 2011).

Vehicles. Every device in, upon, or by which any person or property is or may

be transported or drawn upon a highway, except devices moved by human power or

used exclusively upon stationary rails or tracks.

Vehicle Owner. Owner means a person who holds the legal title to a vehicle.

The term includes a conditional vendee or lessee, in the event a vehicle is the subject of

an agreement for the conditional sale or lease thereof, with or without the right of

purchase upon performance of the conditions stated in the agreement and with an

immediate right of possession vested in the conditional vendee or lessee. (NRS ,2004).
 Chapter 3

METHODOLOGY

This chapter of the study consists of the Methods, Plans and Calculations that

have been used in the system. It also includes the Implementation Plan and the Figures

that shows the flow of the system.

3.1 METHODS
 For developing the traffic ticketing system, Scrum Methodology is used as it is

suited for this project that require the combined intellect of more than one individual.

The complex problems that are appropriate to tackle with Scrum require the combined

focus of a team. Agile processes have been thrust into the limelight by work recently

done in the area of software development.

Scrum is a framework utilizing an agile mindset for developing, delivering, and

sustaining complex products, with an initial emphasis on software development,

although it has been used in other fields including research, sales, marketing and

advanced technologies. It is designed for teams of ten or fewer members, who break

their work into goals that can be completed within time-boxed iterations, called sprints,

no longer than one month and most commonly two weeks. The Scrum Team assess

progress in time-boxed daily meetings of 15 minutes or less, called daily scrums. At the

end of the sprint, the team holds two further meetings: the sprint review

which demonstrates the work done to

stakeholders to elicit feedback, and

sprint retrospective which enables the team to reflect

and improve.

Figure 3. Agile Scrum

Process
 The Agile Scrum processes address the specific activities and flow of a Scrum

project. In total there are 19 processes which are grouped into following five phases:

• Initiate - This phase includes the processes related to initiation of a project: Create

Project Vision, Identify Scrum Master and Stakeholder(s), Form Scrum Team, De-

velop Epic(s), Create Prioritized Product Backlog, and Conduct Release Planning. 

The Initiate phase consists of following six processes:

• Create Project Vision - In this process, the Project Ticketing System is re-

viewed to create a Project Vision Statement that will serve as the inspiration and

provide focus for the entire project. The Admin is identified in this process.

• Identify Scrum Master and Stakeholder(s) - In this process, the Scrum

Master and Stakeholders are identified using specific Selection Criteria.

• Form Scrum Team - In this process, Scrum Team members are identified. Nor-

mally the Admin has the primary responsibility of selecting team members, but

often does so in collaboration with the Scrum Master.

• Develop Epic(s) - In this process, the Project Vision Statement serves as the

basis for developing Epics. User Group Meetings may be held to discuss appropri-

ate Epics.

• Create Prioritized Product Backlog - In this process, Epic(s) are refined,

elaborated, and then prioritized to create a Prioritized Product Backlog for the

project. The Done Criteria is also established at this point.

• Conduct Release Planning - Conduct Release Planning-In this process, the

 Scrum Core Team reviews the User Stories in the Prioritized Product Backlog to

develop a Release Planning Schedule, which is essentially a phased deployment

schedule that can be shared with the project stakeholders. Length of Sprint is

also determined in this process.

• Plan and Estimate -This phase consists of processes related to planning and esti-

mating tasks, which include Create User Stories, Approve, Estimate, and Commit

User Stories, Create Tasks, Estimate Tasks, and Create Sprint Backlog. 

The Plan and Estimate phase consist of following five processes:

• Create User Stories - In this process, User Stories and their related User Story

Acceptance Criteria are created. User Stories are usually written by the Admin

and are designed to ensure that the user’s requirements are clearly depicted and

can be fully understood by all stakeholders. User Story Writing Exercises may be

held which involves Scrum Team members creating the User Stories. User Stories

are incorporated into the Prioritized Product Backlog.

• Approve, Estimate, and Commit User Stories - In this process, the Admin

approves User Stories for a Sprint. Then, the Scrum Master and Scrum Team es-

timate the effort required to develop the functionality described in each User

Story, and the Scrum Team commits to deliver the user requirements in the form

of Approved, Estimated, and Committed User Stories.

• Create Tasks - In this process, the Approved, Estimated, and Committed User

Stories are broken down into specific tasks and compiled into a Task List. Often a
 Task Planning Meeting is held for this purpose.

• Estimate Tasks - In this process, the Scrum Core Team, in Task Estimation

Meetings, estimate the effort required to accomplish each task in the Task List.

The result of this process is an Effort Estimated Task List.

• Create Sprint Backlog -In this process, the Scrum Core Team holds Sprint

Planning Meetings where the group creates a Sprint Backlog containing all tasks

to be completed in the Sprint.

• Implement - This phase is related to the execution of the tasks and activities to

create a ticketing system. These activities include creating the various deliverables,

conducting Daily Standup Meetings, and grooming (i.e., reviewing, fine-tuning, and

regularly updating) the Product Backlog at regular intervals.

The Implement phase consists of following three processes:

• Create Deliverables - In this process, the Scrum Team works on the tasks in

the Sprint Backlog to create Sprint Deliverables. A Scrum board is often used to

track the work and activities being carried out. Issues or problems being faced

by the Scrum Team could be updated in an Impediment Log.

• Conduct Daily Standup - In this process, everyday a highly focused, Time-

boxed meeting is conducted referred to as the Daily Standup Meeting. This is the

forum for the Scrum Team to update each other on their progress and any im-

pediments they may be facing.

• Groom Prioritized Product Backlog - In this process, the Prioritized Product

 Backlog is continuously updated and maintained. A Prioritized Product Backlog

Review Meeting may be held, in which any changes or updates to the backlog

are discussed and incorporated into the Prioritized Product Backlog as appropri-

ate.

• Review and Retrospect - This phase is concerned with reviewing the deliverables

and the work that has been done and determining ways to improve the practices

and methods used to do project work. 

The Review and Retrospect phase consists of following three processes:

• Convene Scrum of Scrums - In this process, Scrum Team representatives

convene for Scrum of Scrums (SoS) Meetings in predetermined intervals or

whenever required to collaborate and track their respective progress, impedi-

ments, and dependencies across teams. This is relevant only for large projects

where multiple Scrum Teams are involved.

• Demonstrate and Validate Sprint -In this process, the Scrum Team demon-

strates the Sprint Deliverables to the Product Owner and relevant stakeholders in

a Sprint Review Meeting. The purpose of this meeting is to secure approval and

acceptance from the Admin for the Deliverables created in the Sprint.

• Retrospect Sprint -In this process, the Scrum Master and Scrum Team meet to

discuss the lessons learned throughout the Sprint. This information is docu-

mented as lessons learned which can be applied to future Sprints. Often, as a re-

sult of this discussion, there may be Agreed Actionable Improvements or Up-

 dated Scrum Guidance Body Recommendations.

• Release - This phase emphasizes on delivering the Accepted Deliverables to the

user and identifying, documenting, and internalizing the lessons learned during the

project. 

The Release phase consists of following two processes:

• Ship Deliverables - In this process, Accepted Deliverables are delivered or transi-

tioned to the relevant stakeholders. A formal Working Deliverables Agreement

documents the successful completion of the Sprint.

• Retrospect Project - In this process, which completes the project, organizational

stakeholders and Scrum Core Team members assemble to retrospect the project

and identify, document, and internalize the lessons learned. Often, these lessons

lead to the documentation of Agreed Actionable Improvements, to be imple-

mented in future projects.

3.2. REQUIREMENT ANALYSIS

This project was developed to operates within the following environment:

a. Operating system Windows

b. Database MySQL and Software to develop the system.

c. Browser Internet Explorer and above, Mozilla Firefox, Google Chrome

Performance.
The following Data Flow Diagram shows the flow of the Traffic Ticketing System in

Public Order and Safety Office San Carlos City, Pangasinan.

Figure 4. Data Flow Diagram
 Figure 5. Flowchart

Flow Chart of the Manual Existing Traffic Ticketing Process

When a traffic enforcer issues a ticket to a violator he confiscates the violator’s

license. The enforcer gives ticket to the violator then reports to the POSO office for

submitting the issued tickets for the day. For every second and third offense the

original violation fee will be doubled and the fourth offense will be impounding of

vehicle. The violator must go the POSO office and pay his violations to the license

director of POSO. After completing the payment his license or the impounded vehicle

can be released.

3.2.1. POPULATION AND LOCALE OF THE STUDY

This project was conducted at Public Order and Safety Office in San Carlos City.

The researchers selected Public Order and Safety Office as its project locale so that it

can easily be tested. This is also the venue for the institution to level-up in terms of

publication because the technology is still not available.

Public Order and Safety Office started March 01, 2012. And it is located at Palaris

Street San Carlos City, Pangasinan. P/MAJ. George R. Bacani (RET.) is the current Head

Chief of POSO.

Respondents of the Study. The study's target sample is consisting of fifty (50)

respondents from the Public Order and Safety Office management that involved the

administrator, officers and violators, who can operate and evaluate the developed

traffic ticketing system. These respondents were chosen on purpose and for the sake of

convenience for this investigation. As a result, the researchers chose to set a target

number of respondents for convenience, but this should ensure that the study's goals

are met.
3.2.2. DATA INSTRUMENTATION

Instrumentation and Data Collection

To achieve the data from the research locale, interview was carried out by the

researchers.

Structured Interview. A structured interview or a standardized interview is a

qualitative research method commonly used in survey research. The aim of this

approach is to confirm that each interview is offered with exactly the same questions in

the same order. This guarantees that answers can be reliably collected and that

comparisons can be made with confidence between sample subgroups or between

different survey periods (Bryant, 2014).

The developers conducted an interview with Mr. Dino Paulo Martinez, the

assigned personnel in Public Order and Safety Office. Through discussion and direct

questioning, the developers were able to acquire the data needed in development of

the study.

Document Analysis. It is a technique used to gather requirements during the

requirements elicitation phase of a project. It describes the act of reviewing the

existing documentation of comparable business processes or systems in order to extract

pieces of information that are relevant to the current project, and therefore should be

consider projects requirements (Adams, n.d.).

The developers analyzed the given resource documents provided by POSO to be

able to visualize some of the system requirements. It also helped the developers

understand the existing system of the agency that will aid in the development of the

system.

Internet Research. The internet is unimaginable powerful research assistance,

but can also be time wasting, frustrating and misleading. However, it has a great future

and the benefits are numerous. Although the internet may appear to be more

advantageous than using the library, one has to look at the quality Web based

information as in most cases no reviews and evaluations have been done by experts on

the subject. There is vast information of data that can be accessed to aid with

independent learning (Wimmer, 2006).

The internet is quickest way in gathering information of a certain topic. With

the said tool, the developers gain ideas, topics, related literatures, and links with the

use of the internet in the development of the system. It made the developers

researching of data easy instead of manually searching of related studies in

mountain of files.

The researchers employed  the "Likert Scale" as a data gathering tool for the

questionnaire survey that will be undertaken with the stakeholder's staffs to collect

feedback on the efficiency, design, and functionality of the proposed system.

Furthermore, the researcher will use the Likert Scale because it is one of the

finest and fastest ways to collect data.

The Likert Scale composed of five (5) scales which includes “Strongly Agree
 - 5”, “Agree - 4”, “Neutral - 3”, “Disagree - 2”, and “Strongly Disagree - 1”.

3.3 DATA ANALYSIS

Tools for Data Analysis

The following tools will aid the researchers in the development of proposed

system.

Database Schema. A database schema is described in a formal language

supported by the database management system. A database schema is a collection of

meta-data that describes the relations in a database. A schema can be simply described

as the "layout" of a database or the blueprint that outlines the way data is organized

into tables (Chapple, n.d.).

The developers used the database schema as a tool for data analysis to show the

organized way to presenting the data of the system’s database. It also provided the

developers on making the proper structure of the database

Entity-Relationship Diagram (ERD). This is used in analysis to describe the

data requirements and assumption in the system. ERD also set the stages for the

design of database (Lewis, 2009).

The developers used the entity-relationship diagram as a tool for data analysis to

show the relationship between the entities in the database of the system. The

developers used this as a tool to clearly visualize a relational database

Flow Chart. Flow Chart is a graphical method of documenting a process. This

diagram that shows the sequential steps of a process that goes into creation of a
service (Lewis, 2009).

The developers made used of the flow chart to represent the step-by-step manual

procedure in Public Order and Safety Office using boxes and arrows denoted various

states of processes.

Scrum. Scrum is a framework utilizing an agile mindset for developing,

delivering, and sustaining complex products, with an initial emphasis on software

development, although it has been used in other fields including research, sales,

marketing and advanced technologies. It is designed for teams of ten or fewer

members, who break their work into goals that can be completed within time-boxed

iterations, called sprints, no longer than one month and most commonly two weeks.

The Scrum Team assess progress in time-boxed daily meetings of 15 minutes or less,

called daily scrums. At the end of the sprint, the team holds two further meetings: the

sprint review which demonstrates the work done to stakeholders to elicit feedback, and

sprint retrospective which enables the team to reflect and improve.

The developers used the tool to show what system functions are performed by

the actor. It also aided the developers the roles of the actors in the system will be

depicted .This high-level view of the system provides a context for the developers of

the more detailed use case specifications.

Weighted Mean. It is similar to an arithmetic mean which is the most common

type of average, where instead of each of the data points contributing equally to the

final average, some data points contribute more than others. The notion of weighted

mean plays a role in descriptive statistics and also occurs in a more general form in
several other areas of mathematics (“Weighted Mean”, 2011).

The data gathered from the Questionnaire survey would be scaled using the

Likert Scale and its data will be used to calculate its mean and standard deviation. The

computed weighted average would scale if the system met the expectations of the

stakeholders or if it needs to be improved. The formula and tables below will show the

computations, scales, and range of each mean derived from the respondents.

The mathematical formula for the weighted arithmetic mean is shown below:

W = weighted average

n = number of terms to be averaged

wi = weights applied to x values

Xi = data values to be averaged

Where WM = weighted mean

W = weight of each item

N = the number of terms (the total number of items or numbers

averaged)

X = the averaged value of each individual item in the list of numbers

The developers used the weighted arithmetic mean to calculate the expected
feedback, each question has five (5) options, one for each item; namely, 5 (Strongly

Agree), 4 (Agree), 3 (Neutral), 2 (Disagree), and 1 (Strongly Disagree).

In interpreting the points of the survey, the following scale will be used:

Table 1. Scales and Points of the Questionnaire Survey

Scale Range Descriptive Rating Description

When there is 100% agreement in
5 4.51 – 5.00 Strongly Agree
the indicators.
When there is 75% agreement in
4 3.51 – 4.50 Agree
the indicators.
When there is 50% agreement in
3 2.51 – 3.50 Neutral
the indicators.
When there is 25% agreement in
2 1.51 – 2.50 Disagree
the indicators.
When there is no agreement in the
1 1.0 - 1.50 Strongly Disagree
indicators.

3.4 DESCRIPTION OF PROTOTYPE

Prototyping is a Rapid Action Development (RAD) method. In this method, the

analysis, design and implementation phases performed concurrently and repeatedly in a

cycle until the system is completed. With this methodology, the basics of analysis and

design are completed. Then the work on the system prototype begins immediately

(Gould, 2016).

In this phase, the work is to assemble every module that had been implement in

the previous step to complete a finalize system prototype. Prototypes will be introduced

to end users who will utilize them for testing and evaluation purposes. At this time, they

will be providing feedback, clarify needs and relay requirements. As per requirements of
end users derived through feedback and testing, the prototypes will be continuously

altered until such time it has reached near perfection.

3.5. THE PROPOSED IMPLEMENTATION PLAN

This is the last phase, which de ve l op e d a n d fi na l i ze d the modules within

time frame from design phases and assemble it to be a final version system and deliver

to end user.

The proposed System Implementation Plan is shown in the table below. It

includes the strategies, activities, people involved, and the time duration for each

activity.

Table 2. Implementation plan.

STRATEGY ACTIVITIES PERSON’S DURATION

INVOLVED

Approval from the Letter’s for the Developers, 1 day

Public Order Administrator for Administrator

And Safety Office approval

Administration

Gathering Data Interview with Developers, 2 days

the Administrator Administrator

and gathering

the information

about manual
 process they

used.

System Development Using PHP, Developers 3 Months

HTML, CSS, and 1week

Bootstrap,

JavaScript,

jQuery, MySQL

and XAMPP to

build the

whole system.

System Testing Testing the Administrator,

actual process of Developers 3 weeks

traffic ticketing

system on the

developed

system.

System Implementation Developers, 3 days

implementation of the system in Administrator

Public Order and

Safety Office

together with the

management
 and developers.

Personal Sharing

of System

Chapter 4

RESULTS AND DISCUSSIONS

The results and discussions will be served for the Design and Development of a

Traffic Ticketing System in Public Order and Safety Office San Carlos City Pangasinan. It

includes User Requirement, Technical Solutions, Hardware Requirements, Software

Requirements, Evaluation, Findings and Analysis of the System.

4.1 USER REQUIREMENT

The requirements analysis determined whether a system or software project

will be successful or become a failure. Documented, executable, quantitative, testable,

and traceable requirements must be met as well as being linked to specific business

needs or opportunities and detailed enough for system design and its development.

The first stage of the data collection procedure was collecting the

important details about the status of Traffic Ticketing System that served as a crucial

source of data in the identification of requirements. The developers employed online

journals and an analysis of some recent published studies in digital books as

secondary data sources.

 After acquiring the relevant information, the developers analyzed the system's

problem. The programmers created the user's requirements. In order to meet the

system's planned concept, the developers carefully examined all of the requirements

needed to make sure that the system will run successfully and free with errors

4.2 TECHNICAL SOLUTIONS

The developers created a system called Traffic Ticketing using PHP, HTML, CSS,

Bootstrap, JavaScript, jQuery, MySQL, XAMPP. This Design and Development of a

Traffic Ticketing System in Public Order and Safety Office San Carlos City, Pangasinan

was created using version 7 of PHP. The system might not operate well with the old

PHP version such as PHP version 5 and below. The PHP version 6 and 7 can run the

system without any problems but PHP version 8 might have because it is an up-to-

date version of PHP that have a lot of new features, improvements, and

developments.

In addition, for its User Interface Design, developers used a HTML and CSS for

a better lightings and design that the user will satisfy within each page while they

using Design and Development of a Traffic Ticketing System without any distraction.

And also, Bootstrap for a responsive design, by the use of HTML, CSS, Bootstrap, we

can create a user-friendly interface.

Finally, developers also used JavaScript and jQuery to add some functions of the

system, for Back-end, developers used MySQL. Developers used XAMPP allows you to

build your website offline by using your local server.

4.3 HARDWARE AND SOFTWARE REQUIREMENTS

Hardware Requirements

Computer hardware refers to the physical parts of a computer and related

devices. Internal hardware devices include motherboards, hard drives, and RAM.

External hardware devices include monitors, keyboards, mice, printers, and scanners.

This includes the personal computer.

Table 3. Hardware Used by the Developers

Personal Computer is used in developing the system with:

Description Minimum Requirement

Operating System Windows 10 Pro 64-bit

Intel(R) Core (TM) i5-2500 CPU @ 3.30GHz 3.30

Processor GHz

RAM 8GB RAM

Hard Disk Drive 500 GB

Internet Connection YES

Table 4. Hardware Requirement for Users Mobile Device

On Mobile Devices, the following are required for the best performance of the

system:

Description Minimum Requirement

Operating System Any version of Android and iOS

Processor 1.1 GHz or higher

 RAM 512 MB or more

Storage 20MB free or more

Wireless Internet
YES
Connection

Software Requirements

Software is a general word that refers to computer programs. Computer software

includes related concepts such as software programs, applications, scripts, and

instruction set. As a result, installing new programs or apps on your computer is

synonymous with installing new software.

Because software is "virtual," or not tangible like computer hardware, it may be

difficult to define. Instead, software is made up of lines of code that have been

compiled into a computer program by computer programmers. When a software

application is installed, it is saved as binary data that is transferred to the hard drive of

the computer. Because software is virtual and takes up no physical space, it is far

simpler (and typically less expensive) to update than computer hardware.

While software, at its most basic level, consists of binary code, CD-ROMs, DVDs,

and other forms of media used to transfer software may also be referred to as

software. As a result, when you purchase a software program, it is often packaged on a

disc, which is a physical medium for storing the software.

Software used in the system:

Bootstrap
 Bootstrap is a free and open-source CSS framework for front-end web

development that is responsive and mobile-first. It includes design templates for

typography, forms, buttons, navigation, and other interface components that are CSS-

and (optionally) JavaScript-based.

CSS

CSS, which stands for Cascading Style Sheets, is a language used to describe the

appearance of Web pages, such as colors, layout, and fonts. It enables the presentation

to be adapted to multiple kinds of devices, such as huge displays, tiny displays, or

printers. CSS is not reliant on HTML and may be used in conjunction with any XML-

based markup language.

Code Igniter

Code Igniter is an open-source software rapid development web framework, for

use in building dynamic web sites with PHP.

FileZilla

FileZilla is a free and open-source, cross-platform FTP application, consisting of

FileZilla Client and FileZilla Server. Clients are available for Windows, Linux, and macOS,

servers are available for Windows only. Both server and client support FTP and FTPS,

while the client can in addition connect to SFTP servers.

HTML

The Hyper Text Markup Language (HTML) is a collection of markup symbols or codes

that are added to a file for Internet display. The markup instructs web browsers on how
to display the content and graphics on a web page.

Infinity Free

Infinity Free is an independent free hosting initiative, dedicated to providing reliable

free hosting services.

JavaScript

JavaScript is a dynamic programming language used for web development, web

applications, game creation, and many other things. It enables you to integrate

dynamic features into web pages that you would not be able to do with only HTML and

CSS.

jQuery

jQuery is an open-source JavaScript library that makes it easier to create and

navigate online applications. jQuery makes HTML Document Object Model (DOM)

manipulation, Asynchronous JavaScript and XML (Ajax), and event handling easier.

MySQL

MySQL is a relational database management system that uses SQL (Structured

Query Language). The program is used for a variety of tasks, including data

warehousing, e-commerce, and logging. However, the most popular use of MySQL is as

an online database.

PHP

PHP stands for PHP: Hypertext Preprocessor, a programming language used to

construct dynamic and interactive HTML Web sites. When a website visitor visits a
page, the server executes PHP instructions and provides the results to the visitor's

browser.

XAMPP

XAMPP is a free and open-source cross-platform web server solution stack

package built by Apache Friends that includes the Apache HTTP Server, the MariaDB

database, and interpreters for PHP and Perl scripts. Because most practical web server

installations employ the same components as XAMPP, it is straightforward to convert

from a local test server to a live server.

4.4 FINDINGS AND ANALYSIS OF THE SYSTEM

4.4.1 Process of the existing traffic ticketing system.

Public Order and Safety Office San Carlos are currently using a manual

system in the management of issued tickets of violators. With the current

existing system it is difficult to manage these records and provide accurate

archiving of information.

The manual processes of the current system that they are using were

consequently time-consuming and less orderly. Thus it will take longer time for

the officers to retrieve certain file. Furthermore, data stored in filing cabinets is

easily accessed by anyone without the implementation of a high security

system. . If the record is lost the data will be completely lost. The process is

presented in Figure 6.
 Figure 6. Existing Process

The figure shows the manual existing process of Public Order and Safety Office where

they are using Microsoft Excel for listing the records of violators who committed

violations and generating reports themselves.

4.5 FEATURES OF THE DEVELOPED SYSTEM

The features of the system are presented in different modules. These modules

were discussed in the succeeding pages

4.5.1 Shows the log-in page of the admin, officer and violator.
4.5.2 Login Page

This page shows the login page of every administrator, officers and violators.

4.4.4 Shows the Registration Form of the Traffic Ticketing

System.
 This page shows the Registration Form.

1.

2.

3.

4.

4.4

4.4.1

4.4.2

4.4.3

4.4.4

4.4.5

4.4.5 Shows the Main page of the Traffic Ticketing System.

This page shows the navigation contents: Violators, Apprehensions, Payments, Users,

Maintenance, Post and Reports.

1.

2.

3.
4.

4.4

4.4.1

4.4.2

4.4.3

4.4.4

4.4.5

4.4.6

4.4.6 Shows the Administration Account

 This page shows the admin account that can access and manage all the data and

features of the project they can easily add, update and delete immediately the records

of violations committed by violators

4.4.7

4.4.7 Shows the Officer Account

This page shows the Officer Account that can access to report a violator. They can

easily send reports using this system.

4.4.8 Shows the Adding Violator

This page shows adding a violator who committed violations.

4.4.9 Shows the Violator Account Index

This page shows to edit a user or violator who committed violations.

4.4.10 Shows the Violator List

Index
This page shows the list of Violator.

1.

2.

3.

4.

4.4

4.4.1

4.4.2

4.4.3

4.4.4

4.4.5

4.4.6

4.4.7

4.4.8

4.4.9
4.4.10

4.4.11

4.4.11 Shows the Violation List Index

This page shows the list of Violations.

1.

2.

3.

4.

4.4

4.4.1

4.4.2

4.4.3

4.4.4

4.4.5

4.4.6

4.4.7

4.4.8

4.4.9

4.4.10

4.4.11

4.4.12

4.4.12 Shows the User Index

This page shows the User Index.

1.

2.

3.

4.
4.4

4.4.1

4.4.2

4.4.3

4.4.4

4.4.5

4.4.6

4.4.7

4.4.8

4.4.9

4.4.10

4.4.11

4.4.12

4.4.13

4.4.13 Shows the New User Index

This page shows the New User Index.

1.

2.

3.

4.

4.4

4.4.1

4.4.2

4.4.3
4.4.4

4.4.5

4.4.6

4.4.7

4.4.8

4.4.9

4.4.10

4.4.11

4.4.12

4.4.13

4.4.14

4.4.14 Shows the Traffic Citation

Ticket
This page shows the process of Traffic Citation Ticket issued by violators.

1.

2.

3.

4.

4.4

4.4.1

4.4.2

4.4.3

4.4.4

4.4.5

4.4.6
4.4.7

4.4.8

4.4.9

4.4.10

4.4.11

4.4.12

4.4.13

4.4.14

4.4.15

4.4.15 Shows the License List

Index
This page shows the information about the license of violators.

1.

2.

3.

4.

4.4

4.4.1

4.4.2

4.4.3

4.4.4

4.4.5

4.4.6

4.4.7

4.4.8
4.4.9

4.4.10

4.4.11

4.4.12

4.4.13

4.4.14

4.4.15

4.4.16

4.4.16 Shows the Apprehensions

Index
This page shows the Apprehension Index only admin had access to add, update and

delete the violators who committed violations.

1.

2.

3.

4.

4.4

4.4.1

4.4.2

4.4.3

4.4.4

4.4.5

4.4.6

4.4.7

4.4.8

4.4.9
4.4.10

4.4.11

4.4.12

4.4.13

4.4.14

4.4.15

4.4.16

4.4.17

4.4.17 Shows the Apprehensions

Reports
This page shows the list of Apprehension Reports.

1.

2.

3.

4.

4.4

4.4.1

4.4.2

4.4.3

4.4.4

4.4.5

4.4.6

4.4.7

4.4.8

4.4.9
4.4.10

4.4.11

4.4.12

4.4.13

4.4.14

4.4.15

4.4.16

4.4.17

4.4.18

4.4.28 Shows Confiscation Report

Page
This page shows the list of Confiscation.

1.

2.

3.

4.

4.4

4.4.1

4.4.2

4.4.3

4.4.4

4.4.5

4.4.6

4.4.7

4.4.8
4.4.9

4.4.10

4.4.11

4.4.12

4.4.13

4.4.14

4.4.15

4.4.16

4.4.17

4.4.18

4.4.19

Shows the New Payment Index

This page shows the process of Payment Index.

1.

2.

3.

4.

4.4

4.4.1

4.4.2

4.4.3

4.4.4

4.4.5

4.4.6

4.4.7
4.4.8

4.4.9

4.4.10

4.4.11

4.4.12

4.4.13

4.4.14

4.4.15

4.4.16

4.4.17

4.4.18

4.4.19

4.4.20

4.4.19 Shows the Payment Index

4.4.11

4.4.12

4.4.13

4.4.14

4.4.15

4.4.16

4.4.17

4.4.18

4.4.19
4.4.20

4.4.21 Shows the Print

Apprehension Page

4.4.22 Shows the Print

Apprehension Index
This page shows the Printable Apprehension List.

1.

2.

3.

4.

4.4

4.4.1

4.4.2

4.4.3

4.4.4

4.4.5

4.4.6

4.4.7

4.4.8

4.4.9

4.4.10

4.4.11

4.4.12

4.4.13

4.4.14

4.4.15
4.4.16

4.4.17

4.4.18

4.4.19

4.4.20

4.4.21

4.4.22

4.4.23

4.4.23 Shows the Print

Confiscation Page
1.

2.

3.

4.

4.4

4.4.1

4.4.2

4.4.3

4.4.4

4.4.5

4.4.6

4.4.7

4.4.8

4.4.9
4.4.10

4.4.11

4.4.12

4.4.13

4.4.14

4.4.15

4.4.16

4.4.17

4.4.18

4.4.19

4.4.20

4.4.21

4.4.22

4.4.23

4.4.24

4.4.24 Shows the Print

Confiscation Index
This page shows the Printable Confiscation List.

1.

2.

3.

4.

4.4

4.4.1

4.4.2

4.4.3

4.4.4
4.4.5

4.4.6

4.4.7

4.4.8

4.4.9

4.4.10

4.4.11

4.4.12

4.4.13

4.4.14

4.4.15

4.4.16

4.4.17

4.4.18

4.4.19

4.4.20

4.4.21

4.4.22

4.4.23

4.4.24

4.4.25
 4.4.25 Implementation of the System

Figure 7. System Implementation

This figure shows the actual photo of the developers together with the current POSO

Chief, P/MAJ. George R. Bacani (RET.).

4.4.26 Evaluate and test the

performance of the System.

Figure 8. System’s Performance Testing

This figure shows the actual photo where the developers guide the POSO Chief
on how to use and manage the developed traffic ticketing system.

4.4.27

4.4.28. Acceptability test of the System

In the completion of the developed Traffic Ticketing System, the system is

prepared for an acceptability test. The following questions were scaled as follows: 5 -

Strongly Agree, 4 - Agree, 3 - Neutral, 2 - Disagree, and 1 - Strongly Disagree.

The data gathered which were analyzed and interpreted. It also provides the

analysis and interpretation of data that has been organized according to the statement

of the problem and presented through tables.

Table 6. Respondents Sex Survey

Sex Number of Respondents Percentage

Male 30 60%
Female 20 40%
Total 50 100%

It could be gleaned on the table that majority of the respondents that used in

this project is male with a frequency of 30 or 60%, on the other hand, female

respondents appeared to have 20 responses which is 40% of the total population.

This indicates that male tend to get caught in traffic laws than female.

Table 7. Respondents Age Survey

Age Number of Respondents Percentage

16 to 20 years old 5 10%
 21 to 25 years old 15 30%
26 years old and above 30 60%
Total 50 100%
The table shows that most of the respondents are ages 26 years and above as

evidence by the frequency of thirty (30) or 60%. Likewise, ages 21 -25 garnered 30%

of the total population or a frequency of fifteen (15) while only five (5) of them ages

16 – 20 as indicated by the 10%. The result supports the common notion that most of

the respondents are at legal age.

Table 8. Learnability Survey

Mea Interpretatio
Learnability
n n

1. It is simple to get started with the system. 4.46 Agree

2. The ticketing system features was easy to un-

4.06 Agree
derstand.

3. I understand the process of the system easily. 4.18 Agree

4. Traffic ticketing system was easy to use. 4.52 Strongly Agree
Overall Weighted Mean 4.31 Agree
Legend: 1.0-Strongly Disagree, 1.51-2.50-Disagree, 2.51-3.50-Neutral,3.51-4.50-Agree,4.51-5.0-Strongly Agree

Table 8 shows that in terms of the learnability, the indicator that obtained the

highest mean of 4.52 which interpreted as strongly agree is indicator 4 which is

“Traffic ticketing system was easy to used.” On the other hand, indicator 2 “The

ticketing system features was easy to understand. ” got the lowest mean of 4.06

which interpreted as agree. Generally, the system in terms of its learnability

appears to be easy as supported by a mean of 4.31 which is interpreted as Agree.

 Based on the result, respondents believed that the proposed traffic system was

more effective and efficient than the manual system they were using at the time

since it can be learned easily.

Table 9. Efficiency of Use Survey

Efficiency of Use Mean Interpretation

1. The system doesn’t have any bugs/er-

3.8 Neutral
ror.
2. This system was easy to operate. 4.18 Agree
3. The system features are working well. 4.48 Agree
4. The system provides a better services
4.4 Agree
than the manual process.
Overall Weighted Mean 4.22 Agree
Legend: 1.0-Strongly Disagree, 1.51-2.50-Disagree, 2.51-3.50-Neutral,3.51-4.50-Agree,4.51-5.0-Strongly

Agree

Table 9 shows that in terms of the efficiency of used, a mean of 4.48 which

interpreted as agree that the system features are working well. A mean of 3.8

which interpreted as neutral that the system doesn’t have any bugs/error.

Therefore, the overall weighted mean is 4.22 which interpreted as “Agree’’

Clearly, based on the study of Leoncio and Camata (2017), respondents are

fascinated on the use of the proposed system in terms of its efficiency since

respondents agreed that manual ticketing could be upgraded to an automated

ticketing system that is more capable and efficient than the current system.

Table 10. User Satisfaction Survey

 The user satisfaction in using the system is evaluated in the acceptability test of

the system. Table 11 shows the acceptability test according to user satisfaction of the

system.

Table 10. User Satisfaction Survey

User Satisfaction Mean Interpretation

1. Is the system helps you to make your

4 Agree
task easier and better

2. Using this system is not a waste of

4.48 Agree
time.
3. This system helps the majority to send
4.24 Agree
and facilitate the task.
4. I get what I expect when I scan this
4.3 Agree
system.
5. The system is very helpful. 4.64 Strongly Agree
6. The system is friendly user. 4.76 Strongly Agree
7. I am satisfied in using this system. 4.24 Agree
Overall Weighted Mean 3.77 Agree
Legend: 1.0-Strongly Disagree, 1.51-2.50-Disagree, 2.51-3.50-Neutral,3.51-4.50-Agree,4.51-5.0-Strongly

Agree

Table 10 presents seven indicators to determine the satisfactory level of the

respondents on the use of proposed traffic system. As shown in the table, the

indicator with the highest mean score of 4.76 which interpreted as strongly agree

is indicator 6 which is “The system is friendly user.” However, indicator 1 “Is the

system helps you to make your task easier and better .” obtained the lowest mean
 score of 4 which interpreted as Agree. The overall weighted mean in terms of

satisfaction is 3.77 which interpreted as “Agree’’. This implies that majority of the

respondents are satisfied on the utilization of the proposed system as evidence by

their responses.

This study is supported by the result presented by Iksan (2019) that the

significance of an E-Ticket in the settlement of traffic violations is the digitalization

of the ticketing process. By using this technology to record traffic offenses, the

ticketing procedure will be more effective and efficient, as well as supporting the

police in administrative control.

Table 11. Reliability Survey

Reliability Mean Interpretation

1. The system is fast. 4.34 Agree
2. I feel secure when using this sys-
4.14 Agree
tem.
3. The system does what I expect. 4.14 Agree
Overall Weighted Mean 4.21 Agree
Legend: 1.0-Strongly Disagree, 1.51-2.50-Disagree, 2.51-3.50-Neutral,3.51-4.50-Agree,4.51-5.0-Strongly

Agree

Table 11 shows that in terms of the reliability, a mean of 4.34 which interpreted as

agree that the system is fast. A mean of 4.14 which interpreted as agree that the

system does what I expect. Therefore, the overall weighted mean is 4.21 which

interpreted as “Agree’’. The result implies that the system's process and results
validation are both consistent and reliable.

Table 12. Overall Survey

The overall acceptability survey was evaluated with the computation of the entire

acceptability.

Criteria Mean Interpretation

Learnability 4.31 Agree
Efficiency of Use 4.22 Agree
User Satisfaction 3.77 Agree
Reliability 4.21 Agree
Overall Weighted Mean 4.13 Agree
Legend: 1.0-Strongly Disagree, 1.51-2.50-Disagree, 2.51-3.50-Neutral,3.51-4.50-Agree,4.51-5.0-Strongly

Agree

As shown in table the data resulted the overall weighted mean for the overall

survey is 4.13 which interpret that the overall survey result is “Agree”.

The overall acceptability test obtained a weighted mean of 4.13 and was found to

be in accordance. Each acceptability test's weighted mean was added together, and the

overall weighted mean was calculated. The outcome indicates that the company

successfully accepted the developed system.

 Chapter 5

SUMMARY, CONCLUSIONS AND RECOMMENDATIONS

This chapter summarizes the findings of the study, presents the conclusions to

the problems concerned with the Design and Development of a Traffic Ticketing System

for Public Order and Safety Office San Carlos City, Pangasinan and provides

recommendation and further development of the study.

5.1 Summary

Since Public Order and Safety Office makes use of manual traffic ticketing which

is prone to human errors and inconsistencies the developers proposed a project entitled

Design and Development of a Traffic Ticketing System for Public Order and Safety
Office San Carlos City, Pangasinan . The developers sought to aid in the current

problems of the existing manual traffic ticketing system.

This descriptive-developmental research, adopted in the development of the

system. The developers identified and analyze the client’s system requirements. It

focuses on the client’s needs firstly rather than focusing into technical aspects.

To provide vital input to the study the developers used method in gathering

data. The primary source of data was an structured interview with P/MAJ. George R.

Bacani (RET.) the current Head Chief of Public Order and Safety Office. Through the

gathered data the developers were able to identify the requirements of the system. The

secondary sources of data were the use of Internet, and library researches that aid the

developers to gather important details about the development of this system.

Lastly, the survey method was employed to collect data, together with

descriptive approach were used to conduct this project. A questionnaire were used as a

tool for gathering information for the participants of this project. The following findings

are specified as; Learnability, in this findings the system received a 4.31 evaluation and

agrees which interpret that the system is easy to learn; Efficiency of Use, the system

received a 4.22 evaluation and agrees which interpret that the system is efficient to

use; User Satisfaction, the system received a 3.77 evaluation and agrees which

interpret that the system satisfied the users; and Reliability, the system received a 4.21

evaluation and agrees which interpret that the developed system is reliable and met its

objectives.
5.2 Conclusions

Based on the findings the conclusions were drawn. The manual system of Public

Order and Safety Office encounters difficulty in organizing any issued tickets of violators

and monitor the offenses of the violator. Due to the manual process it produces

inconsistent information. The developers have made a solution to the identified problem

of the existing system.

The minimum hardware and software requirements were made for the system’s

efficiency and accuracy. With the use of the developed system, effective and efficient

management of violator’s records is made possible.

The developers also concluded that the system is completely functional and

dynamic as a result of the whole data collected from the respondents. As a result, the

users unanimously agree that the system's implementation and use can accomplish

these goals.

The developers proposed a project that sought to;

 To identify the current ticketing procedures at POSO San Carlos;

 To describe the features in the design and development of the system;

 To describe the hardware and software specifications of design and

development of the system; and

 To test the acceptability of the developed system.

The implementation of the proposed project will aid Public Order and Safety

Office Public Order and Safety Office in their work and solve the identified problems. It

will also helps the organization for better ticketing service and reduce the cost of
operation in terms of manpower. Furthermore, it can also help the management to ease

their daily tasks in better and convenient way through this project. Therefore, it is

believed that the system could lessen the difficulty of recording and managing traffic

violations.

5.3 Recommendations

Recommendations are provided to indicate what future developers should do to

improve its effectiveness in a fair and logical way. Furthermore, the recommendations

reflect how the project is used and how important it is to its users.

Based on the findings and conclusions the developers of this project have made

the following recommendations:

• Further development and study to this project is recommended, the system is open

for improvements and system proposals that could contribute to the project devel-

opment.

• Meeting the software and hardware specifications is highly recommended in order to

execute the program efficiently.

• The developers recommend that the developed system should considered to be

used by the Public Order and Safety Office for them to have a better ticketing ser -

vice as well as easier to handle their daily tasks.

• The future Information Technology students and developers are encouraged to im-

prove and enhance this project, as well as to expand and add new features that are

not currently present in the system in order to make it more functional.

 The developers recommend the implementation of the developed system to ease

the use of managing all the records and generating summary reports. The use of

the developed system will improve the process and services offered by the

agency. The system must be integrated for it solves the given problems of the

existing Traffic Violations Management System.

 The developers recommend the agency to have the required software and

hardware requirement for functions of the system will be fully optimized and

maximized.

 To the future developers whose studies are the same nature as this, the

developers recommend additional features to further enhance the system. Lastly,

the future developers should come up with a mechanism to monitor the

violations in real-time.