Final Thesis Lacap Panis WithApprovalSheet

Running head: BUS TERMINAL MANAGEMENT SYSTEM 1
DEVELOPMENT OF BUS TERMINAL MANAGEMENT SYSTEM USING RFID
ANJANETTE A. LACAP
RACHELLE ANNE L. PANIS
A Thesis Presented to the Faculty

of the College of Science
Technological University of the Philippines
Ayala Blvd., Manila
In Partial Fulfillment of the

Requirements for the Degree
Bachelor of Science in Information Technology
February 2014
BUS TERMINAL MANAGEMENT SYSTEM 2
COLLEGE OF SCIENCE
Manila
APPROVAL SHEET
This thesis hereto entitled:
DEVELOPMENT OF BUS TERMINAL MANAGEMENT SYSTEM

USING RFID
prepared and submitted by RACHELLE ANNE L. PANIS and

ANJANETTE A. LACAP in partial fulfillment of the requirements for the degree
Bachelor of Science in Information Technology has been examined and is recommended
for acceptance and approval for ORAL EXAMINATION.
DARWIN C. VARGAS
Adviser
Approved by the Committee on Oral Examination with a grade of PASSED on February

18, 2014.
MINABELLE D. VILLAFUERTE
Chair
PERAGRINO B. AMADOR, Jr. FERDINAND G. BARRAL, Jr.

Member Member
Accepted in partial fulfillment of the requirements for the degree Bachelor of Science in
Information Technology
Prof. MARILYN M. IGNACIO

Date: OIC, Office of the Dean
ABSTRACT
The main objective of this study is to develop a terminal management system using the
technology of Radio Frequency Identification (RFID). Specifically, the project was
designed with the following features: (a) monitors the bus departure and arrival,
(b) updates and keep records of bus dispatching and driver and conductor schedules, and
(c) generates reports needed by the management. The software tools used to develop the
system were Visual Basic .NET, MySQL, and RFID reader. It was evaluated by 30
respondents composed of drivers, conductors, operators, Information Technology experts
and students using ISO 9126, an instrument that measures software quality. The overall
weighted mean of 3.6 was interpreted as “Highly Acceptable”. This indicates that the
system exhibits the following characteristics: functionality, reliability, usability,
efficiency, maintainability, and portability.
ACKNOWLEDGEMENT
In the vision of the success of this project, the authors would like to express their
gratitude and appreciation to those who contributed to the completion of this project.
First, to our dearest adviser, Mr. Darwin C. Vargas for helping and guiding us to
make this thesis possible and for always being there to encourage and support us in doing
our thesis. Without him, we will not have the direction to finish this.
To our ever supportive friends, specially, Kelsey, Lara, Ellaine, Jefferson, Josh, and
Agnes who were always there during the ups and downs of finishing the thesis, our
appreciation to your support.
We would not forget to thank our families who supported us all throughout. You were
always there to provide our needs.
Last but not the least is to God Almighty. We are very thankful to You for you have
given us the knowledge and patience we needed during the trying times.
All our efforts are dedicated to all of you.
- A.A.L. and R.A.L.P.

TABLE OF CONTENTS
Preliminaries
Title Page 1
Approval Sheet 2
Abstract 3
Acknowledgement ` 4
Table of Contents 5
List of Tables 7
List of Figures 8
Chapter
1 THE PROBLEM AND ITS SETTING
Introduction 10
Background of the Study 12
Objectives of the Study 14
Scope and Limitation of the Study 15
2 CONCEPTUAL FRAMEWORK
Review of Related Literature 17
Related Studies 29
Conceptual Model of the Study 30
Evaluation System 32
Definition of Terms 34
3 METHODOLOGY
Project Design 36
Project Development 39
Operation and Testing Procedure 42
Evaluation Procedure 43
4 RESULTS AND DISCUSSION
Project Description 44
Project Structure 44
Project Capabilities and Limitations 56
Project Evaluation 57
5 SUMMARY OF FINDINGS, CONCLUSIONS, AND
RECOMMENDATIONS
Summary of Findings 62
Conclusions 63
Recommendations 64
References 65
Appendixes
Appendix A. Evaluation Instrument for the Acceptability of the System 67
Appendix B. Tabulation Sheet 68
Appendix C. Gantt Chart 69

LIST OF TABLES
Table Page No.
Table 1 Numerical Rating Scale and its Qualitative Interpretation 33
Table 2 Qualitative Interpretation of the Numerical Rating Scale 33
Table 3 Functionality Performance 58
Table 4 Reliability Performance 58
Table 5 Usability Performance 59
Table 6 Efficiency Performance 59
Table 7 Maintainability Performance 60
Table 8 Portability Performance 61

LIST OF FIGURES
Figure Page No.
Figure 1 RFID System 19
Figure 2 RFID Tag 20
Figure 3 RFID Reader 22
Figure 4 How RFID Reader works 23
Figure 5 Conceptual Model of the Study (IPO) 30
Figure 6 Context Data Flow Diagram 37
Figure 7 Flowchart of the System 38
Figure 8 Project Development Flowchart 41
Figure 9 Entity Relational Diagram of the System 45
Figure 10 Log In Menu 46
Figure 11 Main Menu 46
Figure 12 Scheduling of Buses Menu 47
Figure 13 Destination Menu 48
Figure 14 Schedule of Arrival of Buses Menu 49
Figure 15 Schedule of Departure of Buses Menu 50
Figure 16 View Menu 51
Figure 17 Personnel Menu 52
Figure 18 Terminal Menu 53
Figure 19 Company Menu 54
Figure 20 Change Password Menu 55
Figure 21 Reports Menu 55

Figure 22 RFID Tap 56
Chapter 1
THE PROBLEM AND ITS SETTING
This chapter contains the introduction about the project study. It discusses the
background, objectives and the scope and limitation of the study.
Introduction
From the BBC news dated 2010, the streets of Manila, Philippines, are always
swarming with people and vehicles of all kinds, moving along a serpentine maze of
asphalt arteries and other byways. Whether in the performance of the day's business or in
the pursuit of less mundane preoccupations like transporting well-heeled glitterati to
various places of pleasure, indeed living in Manila requires certain knowledge of vehicles
to be found in its streets. Henry Bateman (2009) writes that the backbone of public
transport system are cars, buses, and jeepneys. For provincial transport to any point of
the country, the buses are the most common form of public utility vehicles. Buses in the
Philippines come in two varieties, ordinary and air conditioned. According to
dictionary.com, bus is a large motor vehicle, having a long body, equipped with seats or
benches for passengers, usually operating as part of a scheduled service.
There are also many advantages and disadvantages to travel by bus.
The advantages are the following: Buses offer cheap service that involves no driving
or stress for the person travelling as they don't have to take control of the vehicle; People
who ride the bus are also sharing the service and as they are not using separate cars there
are less emissions and less of an impact on the atmosphere; Buses can also be extremely
comfortable and there may be televisions and radios on board as well as this there is time
to read or do work and in this day and age people can even use the internet when
travelling; And there is also no need to look for parking places while in a built up area
and the bus may let people off nearly exactly where they want to go.
The disadvantages are the following: The bus may be a noisy and uncomfortable ride
where people have to share with other strangers, thereby having a lack of privacy; Buses
are also famed for being late and not stopping where people want them to stop; The trip
may take a longer route than go by a private transport vehicle; Buses are also sometimes
full meaning people can be left waiting for the next one to arrive; And buses can also be
crowded and people may bump and crushed to each other.
The travel time of buses varies depending on several external parameters such as
traffic and accidents. In fact, buses are stuck in traffic and are thus hampered by the
passage of junctions. This makes the management of the bus schedule in the bus stations
a difficult task. Most bus station follow fixed schedules, and do not use intelligent
systems for vehicle tracking and control. As a solution to this the departure and arrival
time of each bus should be monitored so as to allow the management in controlling every
bus trip and also to avoid different shortcomings that the bus driver, conductor and
passengers might encounter.
The researches were prompted to develop a system using a Radio Frequency
Identification also known as RFID as a medium. Radio Frequency Identification (RFID)
technology uses radio waves to identify people or objects. There is a device that reads
information contained in a wireless device or “tag” from a distance without making any
physical contact or requiring a line of sight. RFID technology has been commercially
available in one form or another since the 1970s. It is now part of people’s daily lives and
can be found in car keys, employee identification, medical history/billing, highway toll
tags, and security access cards.
Each bus will have an ID with an RFID chip embedded on it and lets the RFID reader
to scan the ID. Every scan will record the date, time of arrival / departure, name of the
bus driver and conductor, bus number, control number, and plate number. It is significant
to study this matter since it could lead to better innovations in the future that could
completely eliminate different road problems.
Background of the Study
A recent study by Harold Taylor (2013) stated that there are approximately 7,241
franchised public utility vehicles travelling around Metro Manila every day and 3.9% of
them are buses as per LTFRB records (February, 2011). Those buses usually use the
primary highways and roads which are all located in Metro Manila. For most people not
owning a private automobile, the “public utility bus” (PUB) is the only practical way to
travel on medium or long distances, since jeepneys (PUJ) are usually limited to local routes of at most
20 to 30 kilometers, both in cities and in rural areas. Because of this, traffic becomes a
serious problem due to the undisciplined loading and unloading of passengers.
Commuters experience a hard time on buses especially on rush hour. They end up
pushing one another that can lead to serious argument.

In the present situation of most bus terminals, they currently have no automated
system that monitors the arrival and departure of each bus. Many supervisors are
deployed at the station to control the entrance and the exit of buses and prepare the trip
sheets containing the schedules manually which is time consuming and inaccurate. Prior
to the arrival of the bus, a person will verify the bus and record the details of the said bus.
Also upon the departure of the bus same procedure will take place. Bus conductors and
drivers are considered as the route masters. With this they are facing many problems such
as different incidents exemplify the fact that the behavior of the conductors is not good
towards the passengers. Complaints increase every month against alleged rude behavior
of bus conductors. In many instances, people took up cudgels against the bus crew, which
exposed their insensitivity to commuters’ feelings. They also drop off passengers to
prohibited areas, not in terminals or even unloading stations that is causing traffic in all
the busy or non-busy roads.
Moreover, transport departments have no visibility over utilization of its fleet on real-
time, which results in underutilization of resources. So, all these naturally results in
avoidable stress, costly errors and sub cost optimal fleet utilization and finally
dissatisfaction and inconvenience to millions of commuters. The provision of timely and
accurate transit travel time information is so important. The new technology can help the
administrator to monitor the buses traffic while increasing the satisfaction of transit users
and reducing cost through efficient operations asset utilization.
The researchers decided to develop an automated system that would address the
common problems on the management of bus operations. A Bus Terminal Management

System (specifically provincial buses managements) in our country is way too far behind
other countries which then served as an inspiration for the researchers to pursue the
study.
Objectives of the Study
The objective of the study is to develop a Bus Terminal Management System using an
RFID.
Specifically, it aims to:
1. Design the system with the following features:
a. Monitors the time of bus departure and arrival
b. Updates and keeps the records of the terminal
c. Generates reports needed by the management
d. Schedules the buses
e. Generates schedules of drivers and conductors
2. Create the system as designed utilizing VB .NET as programming language,
MySQL as database engine and Crystal Reports as report generator.
3. Test and improve the system’s efficiency in response to management of buses.
4. Determine the acceptability of the system according to functionality, reliability,
usability, efficiency, maintainability, and portability.
Scope and Limitation of the Study

The study was developed to provide a generic “Records Management System” for bus
terminals in Metro Manila with the use of RFID technology. The specifications of card to
be used as an access ID of the authorized persons in the operations will have an
embedded RFID chip on it. The ID is tapped on the scanner and must be within the range
limited up to 1.5 inches or 38.1 mm distance only. The RFID reader detects the chip on
the ID and shows the information assigned to it such as plate number, control number,
names of the driver and conductor, date and time of the arrivals and departures of buses.
All transactions that have been made using the ID will be recorded on the system and will
also generate reports as needed by the management. This will help on keeping tracks of
the daily routine of each bus, driver, and conductor. It will then reduce the manual
handling of monitoring the operations of buses as well as the drivers’ and conductors’
performance on a daily basis.
The system will only work on the core concept of scheduling up to monitoring of the
arrival and departure of buses and all information related to it. It will not include the
tracking of the bus’ location, ticketing system, and payroll system. Any details regarding
incidents, events or activities of the bus outside the terminal premises will not be
recorded on the system.
The evaluation of the system will be defined on the functionality, accessibility,
efficiency, usability, maintainability, and portability as the user encounters the process
and its result.

The choice of method is influenced by the data collection strategy, the type of variable
and the accuracy required to consider appropriate evaluation of the system. The authors
used the process of creating “Questionnaires” which were completed and returned by the
30 respondents in five days.

Chapter 2
CONCEPTUAL FRAMEWORK
This chapter contains the review of related literature and relevant studies that have
some bearing with the present study. This chapter also discusses the conceptual model of
the study and the definition of terms.
Review of Related Literature and Studies
The following literatures provided key ideas and concepts which helped the
researchers in the conceptualization of the study.
Radio Frequency Identification (RFID)
Stephen A. Weis (2005) stated that Radio frequency identification (RFID) is a rapidly
growing technology that has the potential to make great economic impacts on many
industries. At its most basic, RFID systems consist of small transponders, or tags,
attached to physical objects. RFID tags may soon become the most pervasive microchip
in history. When wirelessly interrogated by RFID transceivers, or readers, tags respond
with some identifying information that may be associated with arbitrary data records.
Thus, RFID systems are one type of automatic identification system, similar to optical
bar codes. Radio Frequency Identification (RFID) technology is a non-contact, automatic
identification technology that uses radio signals to identify, track, sort and detect a
variety of objects including people, vehicles, goods and assets without the need for direct
contact (as found in magnetic stripe technology) or line of sight contact (as found in bar
code technology). RFID technology can track the movements of objects through a
network of radio-enabled scanning devices over a distance of several meters.
There are many kinds of RFID systems used in different applications and settings.
These systems have different power sources, operating frequencies, and functionalities.
The properties and regulatory restrictions of a particular RFID system will determine its
manufacturing costs, physical specifications, and performance. Some of the most familiar
RFID applications are item-level tagging with electronic product codes, proximity cards
for physical access control, and contact-less payment systems. Many more applications
will become economical in the coming years. While RFID adoption yields many
efficiency benefits, it still faces several hurdles. Besides the typical implementation
challenges faced in any information technology system and economic barriers, there are
major concerns over security and privacy in RFID systems. Without proper protection,
RFID systems could create new threats to both corporate security and personal privacy.
According to Landt (2001), as shown in Figure 1, Radio Frequency Identification is a
technology that uses communication via radio waves to exchange data between a reader
and an electronic tag attached to an object. It is a technology similar in theory to bar
codes. However, the RFID tag does not have to be scanned directly, nor does it require
line-of-sight to a reader. Its tag must be within the range of an RFID reader, which
ranges from 3 to 300 feet, in order to be read. This technology allows several items to be
quickly scanned and enables fast identification of a particular product, even when it is
surrounded by several other items. Radio Frequency Identification technology uses

digital data in an RFID tag, which is made up of integrated circuits containing a tiny
antenna for transferring information to an RFID transceiver.
The majority of RFID tags contain at least an integrated circuit for modulating and
demodulating radio frequency and an antenna for transmitting and receiving signals.
Frequency ranges vary from low frequencies of 125 to 134 kHz and 140 to 148.5 kHz,
and high frequencies of 850 to 950 MHz and 2.4 to 2.5 GHz. Wavelengths in the 2.4 GHz
range are limited because they can be absorbed by water.
Figure 1. RFID System
Figure 1 shows the RFID system. It is a microchip combined with an antenna in a
compact package; the packaging is structured to allow the RFID tag to be attached to an
object to be tracked. The tag's antenna picks up signals from an RFID reader or scanner
and then returns the signal, usually with some additional data (like a unique serial number
or other customized information). RFID tags can be very small - the size of a large rice
grain. Others may be the size of a small paperback book.
Radio Frequency Identification Tag
Figure 2. RFID Tag
According to Technovelgy (2012), as shown in Figure 2, an RFID tag is a microchip
combined with an antenna in a compact package; the packaging is structured to allow the
RFID tag to be attached to an object to be tracked. The tag's antenna picks up signals
from an RFID reader or scanner and then returns the signal, usually with some additional
data (like a unique serial number or other customized information). RFID tags can be
very small - the size of a large rice grain. Others may be the size of a small paperback
book. Stephen A. Weis (2005) also stated that tags are attached to all objects to be
identified in an RFID system. A tag is typically composed of an antenna or coupling
element, and integrated circuitry. Often tags carry no on-board power source and must
passively harvest all energy from an RF signal.

There are many types of tags that offer different functionalities, have different power
sources, or operate at different radio frequencies. Each of these variables helps determine
which applications a particular tag may be appropriate for and what the costs of a tag may
be. There are two types of RFID tags: passive and active. An active tag is equipped with
a battery that can be used as a partial or complete source of power for the tag's circuitry
and antenna. Some active tags contain replaceable batteries for years of use; others are
sealed units. Because they contain their own power source, active tags typically have a
much longer operating range than passive-tags. Large asset and livestock tracking
applications often use active tags, since the items they are attached to (e.g. railcars,
shipping containers, or cattle) are high in value and have physical space for a bulkier,
rugged tag. A passive tag does not contain a battery; the power is supplied by the reader.
Passive tags have the shorter read range; they are the cheapest to manufacture and the
easiest to integrate into products. Batteries are relatively expensive and cannot easily be
incorporated into some items, like paper packaging. For this reason, passive tags are the
most common tags. When radio waves from the reader are encountered by a passive
RFID tag, the coiled antenna within the tag forms a magnetic field. The tag draws power
from it, energizing the circuits in the tag. The tag then sends the information encoded in
the tag's memory.
Radio Frequency Identification Reader
From Gartner, Inc. (2010), as shown in Figure 3, an RFID reader is a radio frequency
device that emits a signal through an antenna.

Figure 3. RFID Reader
This signal is received by RFID tags that respond to interrogation by the reader.
Responses are read by the reader, and through a variety of protocols the reader can
communicate with all the RFID tags in its field. Readers generally take three forms.
Portal readers are fixed in one location; RFID tags pass through them and communicate
with the reader. Handheld readers are portable devices that can communicate with RFID
tags. Mounted readers are a special type, placed on mobile equipment such as forklifts
and cranes. They often communicate with tags in fixed locations. Also, according to Cory
Janssen, a radio frequency identification reader (RFID reader) is a device used to gather
information from an RFID tag, which is used to track individual objects. Radio waves are
used to transfer data from the tag to a reader.

According to Sarma, et al. (2002), as shown in Figure 4, RFID Reader works readers
or receivers are composed of a radio frequency module, a control unit and an antenna to
interrogate electronic tags via radio frequency (RF) communication. Many also include
an interface that communicates with an application (such as the library’s circulation
system).Readers can be hand-held or mounted in strategic locations so as to ensure they
are able to read the tags as the tags pass through an “interrogation zone.” The
interrogation zone is the area within which a reader can read the tag. The size of the
interrogation zone varies depending on the type of tag and the power of the reader.
Figure 4. How RFID Reader works

Radio frequency identification (RFID) technology has become much more common
across a number of industries, but there are a variety of different types of RFID tags and
readers, each uniquely suited to different types of applications.
RFID cards can add convenience and safety to any transaction of value and data.
Evaluation of performance, cost and security will produce a smart card system. ID cards
embedded with RFID tags, which have been used to control access in the workplace tend
to be more durable. A typical use might be proper accounting of asset and compliance
with company timekeeping policies. They also provide faster and easier access to
facilities because employees just have to tap the card to the reader. The employers can
use RFID access cards to increase worker safety and secure access to the systems. The
access cards can also help companies account for employees in the event of an accident
or, say, a terrorist attack.
The typical RFID-based controlled access solution consists of 1) tags that contain
unique identification data capable of granting or denying access to restricted areas, and 2)
a mechanism for reading the RFID tags at the access control points. RFID tags can be
placed on objects, or they may be embedded into paper or plastic ID cards. They can even
be embedded under human skin, but this is highly controversial. When the tags are read
at the access control points, their data are validated against a database in a centrally
controlled security system, and access is either granted or denied.
Visual Basic .NET

According to the website visual.about.com, Visual Basic .NET is a computer
programming system developed and owned by Microsoft. Visual Basic was originally
created to make it easier to write programs for the Windows computer operating system.
The basis of Visual Basic is an earlier programming language called BASIC that was
invented by Dartmouth College professors John Kemeny and Thomas Kurtz. Visual
Basic is often referred to using just the initials, VB. Visual Basic is easily the most
widely used computer programming system in the history of software.
Also according to Microsoft, Visual Basic is modern, high-level, multi-paradigm,
general-purpose programming language for building apps using Visual Studio and the
.NET Framework. Designed to be both easy-to-learn by beginners and powerful for
experts Visual Basic uses an English-like syntax which promotes clarity and readability
in combination with an extensive set of advanced features and a philosophy that
emphasizes flexibility, productivity, and great tooling.
Microsoft SQL Server
As posed in Techopedia (2010) MySQL is a full-featured relational database
management system (RDBMS) that competes with the likes of Oracle DB and
Microsoft’s SQL Server. MySQL is sponsored by the Swedish company MySQL AB,
which is owned by Oracle Corp. However, the MySQL source code is freely available
because it was originally developed as freeware. MySQL is written in C and C++ and is
compatible with all major operating systems. MySQL is very popular for Web-hosting
applications because of its plethora of Web-optimized features like HTML data types,
and because it's available for free. It is part of the Linux, Apache, MySQL, PHP (LAMP)
architecture, a combination of platforms that is frequently used to deliver and support
advanced Web applications. MySQL runs the back-end databases of some famous
websites, including Wikipedia, Google and Facebook- a testament to its stability and
robustness despite its decentralized, free-for-all philosophy.
Crystal Reports
According to Microsoft (2003), Crystal Reports has been part of Visual Studio since
1993, and is now the standard for reporting in Visual Studio 2005. It ships with every
copy of Visual Studio 2005 and is integrated directly into the development environment.
Crystal Reports for Visual Studio 2005 brings the ability to create interactive,
presentation-quality content to the Windows environment. With it, user can create
complex and professional reports in a GUI-based program then connect the report to
almost any database source. It can host the report in either a Web or Windows
application, with one of the Crystal Reports for Visual Studio 2005 viewer controls.
Report presentation in both Windows and HTML 3.2 or 4.0 clients is highly interactive
and provides with features such as chart drill down, report navigation, and text search.
Reports can be related to Visual Studio 2005 project in many ways:
 Embed the reports directly into the project.
 Access externally, from a file directory.
 Access as a Report Web Service from a remote server.

Features of Crystal Reports for Visual Studio
A common standard file format that allows for feature-rich reports that contain data
retrieval criteria, grouping, summary, parameter, drill down, and subreport linking
information. In Crystal Reports designer, complex report files are easily build by the
wizards and experts. The data and .NET DataSet connections use the Database Expert to
easily interact with a wide variety of database protocols, as well as proxy data in the form
of ADO.NET DataSets. Its processing speed has been significantly improved in Crystal
Reports 10 and Crystal Reports for Visual Studio 2005.
The Report viewers display Crystal Reports on forms, in both Web and Windows
applications. Crystal Reports SDK interacts with and modifies reports programmatically.
It can use one of four different object models, each with increasing levels of complexity
and power. The feature for exports data from the CrystalReportViewer control to Word,
Excel, PDF, and HTML, and Crystal Reports formats. This can also work on the page-
based report printing from any Web or Windows application.
In addition, it prompts for missing parameters and database logons from the
CrystalReportViewer control, which have missing parameters or database information, to
be easily corrected and displayed. Multilingual client support allows one to configure the
CrystalReportViewer control so that other languages can be displayed in the Tool Tips,
determined by the client browser, the ASPX page, or the environment settings for the
machine.
The Report Web Services, from an ASP.NET Web Service project, allows a person to
create a project, add a Crystal Report, and publish it as a Web service which allows
programmatic access to the reports.
The Merge module deployment ensures the correct Crystal Reports' components and
assemblies are added to a Web or Windows application that is created in Crystal Reports
for Visual Studio 2005. The scalability is offered through optimizations that are available
within Crystal Reports for Visual Studio 2005, or by upgrading to another solution in the
Crystal product family.
Seamless migration is possible from previous versions of Crystal Reports for Visual
Studio 2005. Projects created in previous versions of Crystal Reports for Visual Studio
.NET are supported at runtime without requiring design-time modifications.
Likert Scale
A Likert scale is a psychometric scale commonly involved in research that employs
questionnaires. It is the most widely used approach to scaling responses in survey
research, such that the term is often used interchangeably with rating scale, or more
accurately the Likert-type scale. A scale can be created as the simple sum questionnaire
responses over the full range of the scale commonly consists of five-level items namely
“Strongly Disagree”, “Disagree”, “Neither Agree or Disagree”, “Agree” and “Strongly
Agree”. A Likert item is simply a statement which the respondent is asked to evaluate
according to any kind of subjective or objective criteria; generally the level of agreement
or disagreement is measured. It is considered symmetric or "balanced" because there are
equal amounts of positive and negative positions.
Related Studies
The following studies provided foundation in the development of the system.
The study entitled “Bus Management System Using RFID In WSM” by Ben Ammar
Hatem and Hamam Habib (2009) developed a real-time schedule tracker system which
can inform administrators whether the bus is running on time, ahead or behind schedule.
This information is then displayed to a monitor at the bus station to offer better services
to the passengers. It also gives operator the opportunity to make dynamic changes to the
schedule time so he/she can optimize the utilization of its fleet (buses). To enable such
automation in the bus station it is necessary to identify the arriving and departing buses.
With this, a present system architecture to monitor buses traffic, integrating WSN and
RFID.
Another study entitled “Bus Management System” by Mohb Rahmat B. Mohb
Noordin (2005) was conducted by using Microsoft Visual Basic and Microsoft Access.
Briefly there are two main modules for this system. The first module was the Driver
Management module and the second module was the Bus Management Module. The
function of the system includes bus registration, maintenance record, and reminder. The
objective of the system is (1) to set reminder about any import date by the manager, (2) to
record all maintenance activities, and (3) to implement search by using recursive.
Conceptual Model of the Study
The conceptual framework of the system consists of INPUT, PROCESS and
OUTPUT which helped the researchers to analyze and begin with the planning of the
project.
INPUT PROCESS OUTPUT

Knowledge Requirements:
 Project Design
 Bus Management
System Bus Terminal
 Project
 Visual Basic .NET Management
Development
Programming System Using RFID
 Database  Operation and
Management
Testing Procedure
 RFID Functionality
and Reliability
 Evaluation
 Lickert Scale
Procedure
 ISO 9126
Software Requirements:
 Visual Basic .NET
 MYSQL
 Crystal Reports
 Adobe Photoshop
Hardware Requirements:
 RFID
Scanner/Reader
 Computer Unit with
4GB RAM, 128GB
Storage
EVALUATION
Figure 5. Conceptual Model of the Study

Input
The Input consists of three parts, knowledge requirements, software requirements, and
hardware requirements. First is the knowledge requirements which include study of
related lessons, discussion, activities, and other related information about Bus
Management and the RFID infrastructure. Second is the software requirements where
Microsoft Visual Basic .NET was used because its features include an XAML-based
designer, workflow designer, LINQ to SQL designer (for defining the type mappings and
object encapsulation for SQL Server data). For the database, Microsoft SQL Server 2008
Express edition was used which includes the core database engine. While there are no
limitations on the number of databases or users supported, it is limited to using one
processor, 1 GB memory and 4 GB database files (10 GB database files from SQL Server
Express 2008 R2. It is intended as a replacement for MSDE. The tool includes both script
editors and graphical tools that work with objects and features of the server. Finally, for
hardware requirements, a computer unit with dual core processor, at least 4GB RAM,
disk space of 128GB and with Windows 7 Operating System was used. For the RFID
reader, the ACM Brand with reader range of 3 to 15cm and has a USB output interface
was used.
Process
There are four main steps of processes in the study namely; project design, project
development, operation and testing / debugging, and evaluation procedure. The project
design includes the general features of the project. The project development involves data
gathering and explaining how the project was conceptualized until it was finished. The
operation and testing procedure discusses how the project was encoded, debugged and
checked until corrections were made. The evaluation procedure describes how the project
was evaluated by the users and experts. It also includes the respondents’ reactions and
individual results of the entire system.
Output
The output of the study is the Bus Terminal Management System Using RFID.
Evaluation System
This section shows and explains the Respondents’ Profile, Statistical Method,
Evaluation Instrument, and the Operational Definition of Terms.
The respondents for this project were 10 Bus Drivers, 10 Bus Conductors, 5
Professionals, and 5 IT Students. They determined the merits, worth and significance of
the project based on the criteria that have been set as standards.
Evaluation Instrument
Respondents answered an evaluation form using the criteria defined by ISO 9126. The
criteria includes operability, maintainability, portability and efficiency. Criteria were
rated on a scale of 1-4, with four (4) as the highest or “Highly Acceptable”, and three (3)
as “Very Acceptable”, two (2) as “Acceptable”, and one (1) as lowest or “Not
Acceptable” as shown in Table 1.

Table 1.
Numerical Rating Scale and its Qualitative Interpretation
Numerical Rating Descriptive Rating
4 Highly Acceptable
3 Very Acceptable
2 Acceptable
1 Not Acceptable
The mean scale has ranges from 1 to 4, as shown in Table 2. The mean average of
“Highly Acceptable” ranges 3.51 to 4.00 followed by the ranges of 2.5 to 3.5 for the
“Very Acceptable”. As for “Acceptable” ranges from 1.5 to 2.5 and with the minimal
ranges of 1.0 to 1.5 for “Not Acceptable” description.
Table 2.
Qualitative Interpretation of the Numerical Rating Scale
Numerical Rating
3.4 – 4.0 Highly Acceptable
2.6 – 3.3 Very Acceptable
1.8 – 2.5 Acceptable
1.0 – 1.7 Not Acceptable
Statistical Method
The statistical method was used to determine the result of the evaluation given by the
respondents. The statistical method has the following formula :
Formula: = mean ; n = no. of respondents ; i = no of responses
Based on the formula, the mean was computed by getting the sum of all the responses
and dividing it by the number of the respondents.
Operational Definition of Terms
Below are the terms and their definitions to be easily understood.
Radio Frequency Identification (RFID) is a chip used to track information at a
distance.
RFID Reader is a device used to read an RFID Card at a proximity.
RFID Tag picks up signals from an RFID reader or scanner and then returns the signal,
usually with some additional data.
Identification Card (ID) is any document which may be used to verify aspects of a
person's personal identity.

Bus is a large motor vehicle designed to carry passengers between stopping places along
a regular route. The plate number and other details of bus are the parameters used on the
system.
Terminal is the location where the buses depart and arrive. It is another parameter that
needed to be stored on the RFID Card.
Driver is a person who drives the bus and uses the RFID Cards with the information
stored on it.
Conductor is a person who collects fares and sells tickets and also uses the RFID Cards
with the information stored on it.

Chapter 3
METHODOLOGY
This chapter presents the project design, project development, operation and testing
procedure, and evaluation procedure.
Project Design
The project was designed to have an easy and fast gathering of data on the arrival and
departure of a bus in a terminal using RFID as a medium. The system assures data
storage for long period of time and makes the present system automated. The RFID tag
was embedded to the ID and then scanned to the RFID reader and transmitting the data in
the program. Then the program will show and/ record the information that was scanned.
In this manner the arrival and departure of the bus will be easily filed.
Data Flow Diagram of the System
Reports
ADMIN MANAGER
Add / Delete Employee

Development of Bus Terminal Management Validate Data
Add / Delete Bus & Terminal System Using RFID
Schedule Departure & Arrival
Data Store
Bus Departure /Arrival

DRIVER
Employee Data CONDUCTOR
Figure 6. Context Data Flow Diagram
The context diagram of the system shown in Figure 6 describes the interaction of
different users towards the system. The Admin user can add, delete and update the
Employee, Bus and Terminal details, as well as scheduling of bus departure and arrival.
The Driver and Conductor, who will use the RFID Card with the information stored on it
will tap on the reader, then the system will capture its data. The Manager can now
generate reports from the system upon complete updating of bus transactions.
Flowchart of the System
START
Log in as Admin Upon Arrival, tap

the RFID card of
Driver & Conductor
on the reader
Schedule Bus
Departure
System capture data

on card (Driver
Tap the RFID card Name, Date & Time)
of Driver &
Conductor on the
reader
Generate Report
NO Is the Card
Register the Card
Accepted?
YES
END
System capture data
on card (Driver
Name, Date & Time)
Figure 7. Flowchart of the System

The System Flowchart as shown in Figure 7 illustrates the process on how the System
and RFID Card will work on the Bus Operations, specifically on scheduling departure
and arrival on terminals. The system will work on capturing the data of RFID Card which
will then be validated if the schedules are being followed by the Driver and Conductor.
The information that will be stored on the card is the Name of the Driver or Conductor.
The system will save the date and time when the RFID Card has been tapped on the
reader during the departure and arrival of bus.
Project Development
The Project Development was conducted in six phases are shown in Figure 8.
The first phase is the planning, this includes data gathering. This as already discussed
they do not have a systematic scheduling of departure and arrival of buses, it creates other
issues such as mishandling of the passengers. In line with addressing such problem, an
automation of their process was taken into consideration by the researchers.
The second phase is modeling, this is where the researchers identified the needed
modules to be included on system, who will use the system and how it can provide a
scheduling process as well as producing reports that are necessary to the Managers.
The third phase is Software Design, this involves deciding which system capabilities
are to be implemented in the system and which hardware to use. This is one of the most
important phases, as the user must be able to perform his/her task more efficiently. With
the automation of process, the system and device should be able to sustain the operational
management.
The fourth phase is development, this involves the program coding of the system,
design integration, as well the process of read/ write of data to RFID card and the
function of the RFID reader.
Testing and debugging followed in order to check if there are problems and/or errors
in the system. When the system encounters some difficulties, the researchers went to
device check-up and/or to program coding to fix and correct problems and/or errors.
Finally, the evaluation phase where the system was evaluated by the respondents for
the computation of mean to determine its acceptability according to design, usability,
reliability, portability, efficiency, and convenience.

Project Development Flowchart
START
Planning
Modeling
Software Design
Development
Testing &
Debugging
Evaluation
NO Is the System
Acceptable?
YES
END
Figure 8. Project Development Flowchart

Operation and Testing Procedure
The system’s operational procedure was done by following the steps below:
Installing the Software
1. Made sure that the computer meets the requirements of the system.
2. The manuals for the program or the readme file located in the same directory as
the installation commonly contain exact instructions on how to install the
program.
3. Waited until the application is completely installed.
Operations Procedure
1. Logged in to the system using Admin username and password
2. The Admin user registered the Employee (Driver /Conductor) on References
tab – Personnel button
3. Inputted details of Bus & Terminal destination on References tab – Terminal
button
4. On Scheduling tab, set the Bus Allocation, Terminal Destination and Schedule
of departure and arrival.
5. Generated the schedule created.
Testing Procedure
The steps conducted to test the system are as follows;
1. Tapped the ID to the RFID reader.
2. Scanned the ID to the RFID reader.

3. The system will capture the data from the RFID Card
4. Made sure if the details are correct and displayed on the screen.
5. Viewed on the View All reports.
Evaluation Procedure
The system was evaluated by 30 respondents: 10 Bus Drivers, 10 Bus Conductors, 5
IT Students, and 5 Professionals.
The following procedure gave a complete evaluation of the system:
1. Each respondent was given an evaluation sheet.
2. The developers discussed the flow of the system and showed some demonstrations
to the respondents how the system will work.
3. The developers provided the manual to the users so that they have a guide to do
the test and evaluate its performance.
4. The respondents gave the evaluation rating of the system.
5. The individual results were tabulated and the mean was computed to determine its
acceptability according to design, usability, reliability, portability, efficiency, and
convenience.
Chapter 4
RESULTS AND DISCUSSION
This chapter presents the project description and structure, capabilities and limitations,
project test results and the evaluation result of the project prototype.
Project Description
The study developed is a Bus Terminal Management System using Radio Frequency
Identification (RFID). The main purpose of the study is to monitor the arrival and
departure of the bus in the terminal using systematized scheduling process. The system
was created in Microsoft Visual Studio and can run on a computer with operating system
Windows 7 Professional or higher, processor should be Pentium(R) IV CPU 1.5 GHz.
The Memory is 4GB RAM and the Hard Disk Space is 128GB. The project aims to
improve the efficiency of bus operations by providing them an easy and accurate
capturing of data through the use of RFID Cards.
Project Structure
The Bus Terminal Management System mainly focuses on the arrival and departure of
the buses. The figures that follow illustrate how the system will work starting from the
creation of the user, input of Employee’s information, Bus and Terminal details, and the
creating schedule of trip up to generating of reports. The integration RFID reader will
enable the system to capture the data from RFID card of the user. The data of the card
that will be saved in the on system is the date and time of departure and arrival, when the
user taps on the reader located at the terminal.

Entity Relational Diagram of the System
Figure 9. Entity Relational Diagram of the System
Figure 9 illustrates the Entity Relational Diagram of the system where the information
shows the relationship between the schedule of Driver and Conductor with the Bus and
the expected details of departure and arrival for the output of system.
System Interface
Figure 10. Log In Menu
The first screen of the system is the Log in Menu, shown in Figure 10. This is the
starting point of the system where the Administrator has the capability to create and
update the information needed in the system. The admin user is the only access that can
control or modify the details of employees, buses and terminals needed for scheduling the
trip.
Figure 11. Main Menu

The Main Menu as shown in Figure 11, is the next screen of the system after logging
in of the admin user. The four main tabs of the system can be found on the upper left
corner, starting from Scheduling, References, System and Reports.
Figure 12. Scheduling of Buses Menu
The Scheduling of Buses, shown in Figure 12 consists of Buses, Destination,
Schedule, and View All sub-menus. The first button is the Buses where the admin will
indicate the details such as Bus Id, Plate Number, OR number and CR number. For the
details of Driver and Conductor the admin will indicate the RFID number on the system
corresponding to the bus number assigned to them.
Figure 13. Destination Menu
The next sub-menu is the Destination Menu, shown in Figure 13. This is where the
admin will indicate the details of buses destination, the information such as terminal
location, the route and travel time are included on this process.
Figure 14. Schedule of Arrival of Buses Menu
The Schedule of Arrival of Buses Menu, Figure 14 is where the admin can view the
schedule of the arrival of buses in different terminals. In this process, they also have an
option to Add or Update details of arrival.

Figure 15. Schedule of Departure of Buses Menu
In the Schedule of Departure of Buses Menu as reflected in Figure 15, same as the
arrival, the admin can view the schedule of the departure of buses in different terminals.
They can also modify the details of departure using Add or Update button.
Figure 16. View Menu
The View All sub-menu shown in Figure 16, is the View Menu of the schedule of
buses for each terminal. This allows the admin to choose what terminal and destination to
view the arrival and departure details.

Figure 17. Personnel Menu
The References tab of the system consists of three sub-menus. The first sub-menu is
the Personnel, shown in Figure 17 where the Admin can Add, Delete, and Update the
information regarding the personnel of the company.

Figure 18. Terminal Menu
The next sub-menu is the Terminal Menu, shown in Figure 18. The Admin can Add,
Delete, and Update location of the terminal destination of the company.

Figure 19. Company Menu
The last sub-menu shown in Figure 19 is the Company Menu. This is where the
Admin indicates the name of the company as well as the company code. The system is
capable of handling multiple account of different companies. It just needs to modify the
content of References tab.

Figure 20. Change Password
Figure 20 shows the process on how to Change Password of the system user.
Figure 21. Reports Menu
The Reports tab shown in Figure 21 is where to generate the reports. The type of
reports that the system produces are the Bus List, Route, Schedule and Personnel. It can
be generated by terminal location.

Figure 22. RFID Tap
The interface of RFID Tap shown in Figure 22 is the screen when the system is ready
to capture the data from RFID Card upon departure and arrival at the terminal. The
operational process is when the Driver and Conductor tap the card, the date and time will
be recorded on the corresponding bus number assigned to them.
Project Capabilities and Limitations
The capabilities of the Bus Terminal Management System are as follows:
1. The system is capable of scheduling the departure and arrival of buses in all
terminals.
2. The system is capable of monitoring the time of arrival and departure of buses
from different terminals.
3. The system is capable of modifying the details of created schedule simultaneously
by selection of Terminal Destination.
4. The system can capture the real-time data through RFID Card and reader and save
the record accurate.
5. The system can provide the main reports needed in the operations such as Bus list,
Route, Schedule and Personnel.

The limitations of the system are as follows:
1. The system does not include the control in ticketing system.
2. The system is not capable of tracking the location of the bus because it does not
include GPS feature.
3. The system is not capable of providing report for any accounting or payroll
matters.
Project Evaluation
The project was evaluated by 30 respondents composed of 10 Bus Drivers, 10 Bus
Conductors, 5 Professionals, and 5 IT Students. The criteria include operability,
maintainability, portability, and efficiency of the system. It also includes the usability of
the system to perform the operations of bus scheduling, if they are satisfied on how the
system will produce the expected result especially the drivers and conductors.
Summary of Respondents’ Evaluation
Table 3.
Functionality Performance
A. Functionality Mean Descriptive Meaning
1. Suitability 3.6 Highly Acceptable
2. Accurateness 3.5 Highly Acceptable
3. Interoperability 3.7 Highly Acceptable
Mean 3.6 Highly Acceptable
The result regarding the functionality performance gained a total mean of 3.60, which is
equivalent to a Highly Acceptable rating. This indicated that the system is user-friendly,
accurate, and provides convenience and comfort in terms of the end-user.
Table 4.
Reliability Performance
B. Reliability Mean Descriptive Meaning
1. Maturity 3.5 Highly Acceptable
2. Fault Tolerance 3.2 Very Acceptable

The reliability performance of the system as shown in table 4 shows that the overall
mean rating of 3.4 which equivalent to Highly Acceptable signifies that the system can
perform in terms of the process.
Table 5.
Usability Performance
C. Usability Mean Descriptive Meaning
1. Understandability 3.8 Highly Acceptable
2. Learning Process 3.9 Highly Acceptable
3. Operability 3.7 Highly Acceptable
The usability performance of the system as shown in table 5, obtained an overall mean
of 3.8, which is equivalent to a Highly Acceptable rating. This proves that the system is
easy to operate, to learn, and to understand.
Table 6.
Efficiency Performance
D. Efficiency Mean Descriptive Meaning
1. Time Behavior 3.4 Highly Acceptable

2. Resource Behavior 3.5 Highly Acceptable
The efficiency performance of the system as shown in table 6, achieved an overall mean
of 3.4 which is equivalent to Highly Acceptable rating. This attests that the time behavior,
and resource utilization of the integrated system performs very well.
Table 7.
Maintainability Performance
E. Maintainability Mean Descriptive Meaning
1. Stability 3.6 Highly Acceptable
2. Testability 3.7 Highly Acceptable
The result of evaluation regarding the system’s maintainability performance as shown in
table 7, obtained an overall mean of 3.6, which is equivalent to Highly Acceptable rating.
This indicates that the system is easily diagnosed for issues. Also changes and tests can be
applied effortlessly.
Table 8.
Portability Performance
F. Portability Mean Descriptive Meaning
1. Installation Process 3.8 Highly Acceptable
2. Adaptability 3.7 Highly Acceptable
The result of the evaluation about the system’s portability performance as shown in
table 8 acquired an overall mean of 3.8, which is equivalent to a Highly Acceptable
rating. This indicates that the system is portable in the requisites of adaptability,
conformance, and replace ability.

Chapter 5
SUMMARY OF FINDINGS, CONCLUSIONS, AND RECOMMENDATIONS
This chapter discusses the summary of findings, conclusions, and the corresponding
recommendations of the study.
Summary of Findings
Findings on the evaluation show that:
1. The developed system yielded a mean rating of 3.6 interpreted as “Highly
Acceptable” in terms of functionality. The functions included in the system are
fully functional.
Acceptable” in terms of reliability. The system does not terminate despite errors
or bugs encountered.
Acceptable” in terms of usability. Display instructions and user interface are easy
to understand. The system is easy to operate.
4. The developed system yielded a mean rating of 3.4 interpreted as“Highly
Acceptable” in terms of efficiency. The system can execute the request in a
timely manner. The system uses resources efficiently and appropriately.
Acceptable” in terms of maintainability. The system can easily be modified for
expansion and correction.

Acceptable” in terms of portability. The system can run on different operating
environments. The system can be easily be installed.
The overall mean for all criteria contained in the ISO 9126 evaluation instrument for
the project yielded an average of 3.60 which indicates that the project prototype is
effective.
Conclusions
The conclusions of the study are the following:
1. The system can perform the following features:
a. Create schedule of departure and arrival of bus in different terminals.
b. Personnel data are encoded on the RFID Card.
c. Bus and terminal details can be modified every schedule.
d. Straight forward process adopted from operational workflow.
e. Multiple assigning of personnel on the same schedule.
f. Capture real-time records of data using RFID reader.
g. Static connection configuration.
h. Enables the user to view and generate reports.
i. The system can be easily implemented and easy to operate.
2. The system was created as designed by operations flow of bus.

3. The system is highly acceptable in terms of functionality, reliability, usability,
efficiency, maintainability, and portability.
Recommendations
For further improvements of the system, the following recommendations are put
forward:
1. Improve the design by adding functions to the system like ticketing and
payroll system.
2. Include a web based application for the system.
3. Improve handling of database and put back-up of records.
4. Include import report to Microsoft excel.

References
Bednarz, A. (2003, November 3). Defense Department goes on offense with RFID.
Network World Fusion. Retrieved August 4, 2013 from
http://www.nwfusion.com/news/2003/1103forresterside.html
Booth-Thomas, C. (2003, September 22). The See-it-all chip: Radio-frequency

identification—with track-everything-anywhere capability, all the time—is about to
change your life. Time, 162, pA8.
Cory Janssen, (ND), Definition - What does Radio Frequency Identification Reader
(RFID Reader) mean? Retrieved September 20, 2013 from
http://www.techopedia.com/definition/26992/radio-frequency-identification-reader-rfid-
reader
Dowbenko, U. (n.d.) VeriChip: RFID microchip implants for humans. Retrieved

September 11, 2013 from
http://www.conspiracyplanet.com/channel.cfm?channelid=74&contentid=900
EPC Global. (2003) Guidelines on EPC for Consumer Products. Retrieved September 11,
2013 from http://www.epcglobalinc.org/public_policy/public_policy_guidelines.html
Garfinkel, S. (2002, October). An RFID bill of rights. MIT Technology Review.

Retrieved September 12, 2013 from
http://www.simson.net/clips/2002.TR.10.RFID_Bill_Of_Rights.html
Gartner, Inc. (ND), RFID reader Retrieved September 20, 2013 from
http://www.gartner.com/it-glossary/rfid-reader/
Microsoft Corporation, (ND), Microsoft SQL Server, Retrieved September 29, 2013 from
http://msdn.microsoft.com/en-us/library/bb545450%28v=sql.10%29.aspx
Hesseldahl, A. (2004, July 29). A hacker’s guide to RFID. Forbes.com. Retrieved August
6, 2013 from http://www.forbes.com/home/commerce/2004/07/29/cx_ah_0729rfid.html.
Kosta, E., (2007), ‘RFID Technology: When Innovation Brings Along Data Protection
Challenges’, Proceedings of the 46th FITCE Congress – “The broadband way to the
future”, Retrieved September 21, 2013 from
www.fidis.net/resources/deliverables/profiling/d770/doc/38
Microsoft Corporation, (ND), What is Crystal Reports?, Retrieved September 29, 2013
from http://msdn.microsoft.com/en-us/library/ms225593%28v=vs.80%29.aspx
Microsoft Corporation, (ND), Features of Crystal Reports for Visual Studio, Retrieved
October 15, 2013 from http://msdn.microsoft.com/en-
US/library/ms225360%28v=vs.80%29.aspx
Molnar, D., Wagner, D.A. (2004, June 8). Privacy and security in library RFID: Issues,
practices and architectures. Retrieved September 30, 2013 from
http://www.cs.berkeley.edu/~dmolnar/library.pdf.
Norlin, Lucy (ND) A Secure Balance Retrieved September 21, 2013 from
http://asumag.com/security/ID_systems/university_secure_balance/
Ronak Shah (2005) A System’s Approach to the Evaluation of Radio Frequency

Identification (RFID) in the Defense Industry Retrieved September 21, 2013 from
http://est.mit.edu/HeadLine/shah_networld.html
R. Moroz Ltd. (2004, July). Understanding Radio Frequency Identification (RFID)

(Passive RFID). Markham, Ontario: R. Moroz Ltd. Retrieved September 4, 2013 from
http://www.rmoroz.com/rfid.html
Techopedia, (ND), Definition – What does SQL Server mean?, Retrieved October 15,
2013 http://www.techopedia.com/definition/1243/sql-server
Appendix A
EVALUATION SHEET FOR THE ACCEPTABILITY

OF SYSTEM

Ayala Blvd., Ermita, Manila
College of Science
Evaluator’s Name(Optional):________________________________________________
Instruction: Please evaluate the system using the given scale and placing a checkmark on
the appropriate column corresponding to your response.
4 - Highly Acceptable 3 – Very Acceptable 2 - Acceptable 1 - Not Acceptable

FUNCTIONALITY 1 2 3 4
1. Suitability – essential functionality of characteristics and refers to the
appropriateness of the functions of the software.
2. Accurateness – refers to the correctness of the function.
3. Interoperability – concerns the ability of a software component to interact
with other components or system.
RELIABILITY
4. Maturity – concerns about the frequency of failure of the software.
5. Fault Tolerance – ability to withstand from component or environmental
failure.
USABILITY
6. Understandability – ease of which the system functions can be understood.
7. Learning Process – learning effort for different users.

8. Operability – ability of the software to be easily operated by a given user in
a given environment.
EFFICIENCY
9. Time Behavior – response time for a given thru put.
10. Resource Behavior – characterizes resources used.
MAINTAINABILITY
11. Stability – sensitivity of a change of a given system that is the negative
impact that may be caused by system changes.
12. Testability – characterizes the effort needed to verify a system change.
PORTABILITY
13. Installation Process – characterizes the effort required to install the software.
14. Adaptability – provides flexible environment.
Comments/Recommendations:
______________________________________________________________________________
______________________________________________________________________________
Appendix B
TABULAR SHEET
Respondents Functionality Reliability Usability Efficiency Maintainability Portability
1 4 3 4 4 3 4 4 4 4 4 4 4 4 4
2 4 4 4 4 3 4 4 3 3 4 4 4 3 4
3 3 4 3 3 2 3 4 3 3 4 4 2 3 3
4 4 4 4 3 4 4 3 4 4 3 4 3 4 4
5 4 4 4 3 3 4 4 3 4 4 4 4 3 4
6 4 4 4 3 4 3 3 3 3 3 3 4 4 4
7 4 3 4 4 4 4 4 3 4 3 4 4 4 4
8 4 4 4 4 3 4 4 4 4 4 3 3 4 4
9 4 4 4 4 3 4 4 4 3 4 4 4 4 4
10 4 3 4 3 3 4 4 4 4 3 4 4 4 3
11 4 4 4 4 2 4 4 4 3 2 3 4 4 4
12 4 4 4 3 2 4 4 4 3 2 3 4 4 3
13 3 4 3 3 3 4 4 4 3 4 4 4 4 4
14 3 3 4 4 4 4 4 3 3 4 3 3 4 4
15 4 3 3 4 4 4 4 4 3 3 4 4 3 4
16 4 4 4 4 4 4 3 4 4 4 4 4 4 3
17 4 3 4 3 4 4 4 4 3 4 4 3 4 4
18 4 3 3 4 3 4 4 3 3 4 4 3 4 4
19 3 3 4 4 3 4 4 4 3 4 4 4 3 4
20 3 3 4 3 4 3 4 4 3 3 4 4 3 3
21 4 3 4 3 3 4 4 3 4 3 3 4 4 4
22 3 4 3 4 3 4 4 4 3 3 4 4 4 3
23 4 4 4 3 3 3 3 4 3 3 3 4 4 4
24 3 3 4 3 3 3 4 4 3 4 4 3 4 3
25 3 4 4 3 3 3 4 3 3 4 4 3 4 4
26 3 4 3 3 3 4 4 4 3 4 3 3 4 4
27 4 4 2 4 4 4 4 4 4 4 3 4 4 4
28 3 3 3 4 4 4 4 4 4 3 2 4 4 4
29 3 3 3 4 3 4 4 4 4 3 2 4 4 4
30 3 3 4 4 3 4 4 4 3 4 4 4 4 3
3.6 3.53 3.67 3.53 3.23 3.8 3.87 3.7 3.37 3.5 3.57 3.67 3.8 3.73
Average 3.6 3.38 3.79 3.44 3.62 3.77
Overall Mean 3.6
Appendix C
GANTT CHART
In scheduling tasks, the bars represent each activity and each bar represents the relative
length of the task. Considering the system development cycle has its 6 major tasks, the
study phase, analysis phase, design phase, development phase, testing and debugging, and
implementation.
Tasks Jun Jul Aug Sep Oct Nov Dec Jan Feb
Initial Data
Gathering
Problem Analysis
&
Conceptualization
Chapter 1
Documentation
Chapter 2
Documentation
Chapter 3
Documentation
Preliminary
Design
Project
Development
Testing and
Debugging
Chapter 4
Documentation
Chapter 5
Documentation
Final Defense
Final Report

Final Thesis Lacap Panis WithApprovalSheet

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Final Thesis Lacap Panis WithApprovalSheet

Uploaded by

Copyright:

Available Formats

Running head: BUS TERMINAL MANAGEMENT SYSTEM 1

DEVELOPMENT OF BUS TERMINAL MANAGEMENT SYSTEM USING RFID

RACHELLE ANNE L. PANIS

A Thesis Presented to the Faculty

In Partial Fulfillment of the

Technological University of the Philippines

This thesis hereto entitled:

DEVELOPMENT OF BUS TERMINAL MANAGEMENT SYSTEM

prepared and submitted by RACHELLE ANNE L. PANIS and

Approved by the Committee on Oral Examination with a grade of PASSED on February

PERAGRINO B. AMADOR, Jr. FERDINAND G. BARRAL, Jr.

Prof. MARILYN M. IGNACIO

appreciation to your support.

always there to provide our needs.

All our efforts are dedicated to all of you.

- A.A.L. and R.A.L.P.

1 THE PROBLEM AND ITS SETTING

Background of the Study 12

Objectives of the Study 14

Scope and Limitation of the Study 15

Review of Related Literature 17

Conceptual Model of the Study 30

Operation and Testing Procedure 42

4 RESULTS AND DISCUSSION

Project Capabilities and Limitations 56

5 SUMMARY OF FINDINGS, CONCLUSIONS, AND

Appendix A. Evaluation Instrument for the Acceptability of the System 67

Appendix B. Tabulation Sheet 68

Appendix C. Gantt Chart 69

Table Page No.

Table 1 Numerical Rating Scale and its Qualitative Interpretation 33

Table 2 Qualitative Interpretation of the Numerical Rating Scale 33

Table 3 Functionality Performance 58

Table 4 Reliability Performance 58

Table 5 Usability Performance 59

Table 6 Efficiency Performance 59

Table 7 Maintainability Performance 60

Table 8 Portability Performance 61

Figure Page No.

Figure 1 RFID System 19

Figure 2 RFID Tag 20

Figure 3 RFID Reader 22

Figure 4 How RFID Reader works 23

Figure 5 Conceptual Model of the Study (IPO) 30

Figure 6 Context Data Flow Diagram 37

Figure 7 Flowchart of the System 38

Figure 8 Project Development Flowchart 41

Figure 9 Entity Relational Diagram of the System 45

Figure 10 Log In Menu 46

Figure 11 Main Menu 46

Figure 12 Scheduling of Buses Menu 47

Figure 13 Destination Menu 48

Figure 14 Schedule of Arrival of Buses Menu 49

Figure 15 Schedule of Departure of Buses Menu 50

Figure 16 View Menu 51

Figure 17 Personnel Menu 52

Figure 18 Terminal Menu 53

Figure 19 Company Menu 54

Figure 20 Change Password Menu 55

Figure 21 Reports Menu 55

Figure 22 RFID Tap 56

THE PROBLEM AND ITS SETTING

background, objectives and the scope and limitation of the study.

the pursuit of less mundane preoccupations like transporting well-heeled glitterati to