Quezon City University: Front-End Product and Sales Monitoring System For Manila Bible Seminary's Canteen

QUEZON CITY UNIVERSITY i
Front-End Product and Sales Monitoring System for Manila Bible

Seminary’s Canteen
A Software Engineering Project Documentation

Presented to
The Department of Information Technology
Quezon City University
In Partial Fulfillment
of the Requirements for the Degree
Bachelor of Science in Information Technology
BSIT – SBIT2E
Group 2
Arbado, Dean Joseph Ivan
Arce, Jeromel
Avila, Aira Janine
Bagacay, Genesis
Inigo, Paulo Miguel
Jabla, Carlo
Latosa, Jasmin
Llaneta, Von Andrei
Lumontod, Christian
Quinto, Daniel
Romerosa, Diana Jane
Sacyaten, Ana Cecilia
(March 23, 2022)
DEPARTMENT OF INFORMATION TECHNOLOGY

QUEZON CITY UNIVERSITY ii
APPROVAL SHEET
In partial fulfillment of the requirements for the degree BACHELOR OF SCIENCE IN

INFORMATION TECHONOLOGY, this Software Engineering project entitled
(“<Please Insert Your Title>>”), has been prepared and submitted by << Please insert
members alphabetically, upper case, Last Name, First Name, Middle Initial Format>>,
who hereby
<< Please Insert Your Advisers Name >>

System Architecture and Design Mentor
Approved by the Committee for Project Presentation with a notation of

___________________ on Date Month, 2022
ISAGANI M. TANO, DIT

Chairperson, Project Presentation Committee
Accepted and approved in partial fulfillment of the requirements for the degree
BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY.
ISAGANI M. TANO, DIT

Dean, Department of Information Technology
Date:_______________

QUEZON CITY UNIVERSITY iii
DEDICATION

QUEZON CITY UNIVERSITY iv
ACKNOWLEDGEMENT

QUEZON CITY UNIVERSITY v
EXECUTIVE SUMMARY
(This part contains summary of your study, every Chapter’s contents. Create this at the
end of your project development.)

QUEZON CITY UNIVERSITY vi
TABLE OF CONTENTS
Approval Sheet.................................................................................................................... ii
Dedication .......................................................................................................................... iii
Acknowledgement ............................................................................................................. iv
Executive Summary ............................................................................................................ v
Table Of Contents .............................................................................................................. vi
List Of Tables .................................................................................................................. viii
List Of Figures ................................................................................................................... ix
List Of Appendices ............................................................................................................. x
CHAPTER I Project Background ..................................................................................... 11
Introduction ................................................................................................................... 11
Project Background and Context .................................................................................. 11
Project Purpose and Description ....................................Error! Bookmark not defined.
Main Objective...........................................................Error! Bookmark not defined.
Specific Objectives ....................................................Error! Bookmark not defined.
Scope and Delimitations of the Project ..........................Error! Bookmark not defined.
Definition of Terms....................................................................................................... 12

QUEZON CITY UNIVERSITY vii
CHAPTER II Review of Related Literature and System.................................................. 14
CHAPTER III Technical Specifications ........................................................................... 15
Software ........................................................................................................................ 21
Hardware ....................................................................................................................... 21
Technologies ................................................................................................................. 21
Diagrams and Flowcharts ..............................................Error! Bookmark not defined.
Network Layout ............................................................................................................ 26
Hardware Design Layout ...............................................Error! Bookmark not defined.
CHAPTER IV Methodologies .......................................................................................... 34
System Requirement Specifications ............................................................................. 34
System Development Methodologies ........................................................................... 36
Testing Procedures ........................................................................................................ 39
CHAPTER V Summary and Recommendation .................Error! Bookmark not defined.
Summary ....................................................................................................................... 42
Recommendations ......................................................................................................... 43
Appendices........................................................................................................................ 44
References ..........................................................................Error! Bookmark not defined.

QUEZON CITY UNIVERSITY viii
LIST OF TABLES
Table no. Table Title Page No.

QUEZON CITY UNIVERSITY ix
LIST OF FIGURES
Figure no. Figure Title Page No.

QUEZON CITY UNIVERSITY x
LIST OF APPENDICES
Appendix Title Page No.

QUEZON CITY UNIVERSITY 11
CHAPTER I
PROJECT BACKGROUND
Introduction
Manila Bible Seminary is a semi well known seminary for upcoming preachers
and teachers in the biblical field of expertise, as well as musicians in various sectors. It
has been in business for over 30 years. It is found within the area of Pablo Dela Cruz St.,
San Bartolome, Novaliches, Quezon City. It consists of an administration leading its
employees, teachers, and students like any other kind of school or educational
establishment. Within its premises, there is found a small canteen for students to buy
snacks and meals from, as well as a place to relax, unwind, and recalibrate. The owner of
this said canteen is one of the employees of the seminary whom is working within the
Accountancy division of the seminary. The canteen’s employee is comprised of a humble
middle-age woman, as well as seminary student volunteers.
The canteen of the seminary has a certain daily routine of which is done by both
the owner and the employee every morning. They would gather just enough raw
ingredients to cook for a day’s worth of service, snacks, and delicacies and aims to
completely sell out the aforementioned products - or give away the said products to
students to avoid the spoilage and waste of food.

Project Background and Context
Having a computerized tool that is able to store data, process data, and provide
accurate information is useful for businesses if they aim to progress themselves further.
This can be done by having a monitoring system, as a system like it would be able to
maximize the utility of the data acquired in order to make better business decisions
(Margareta et. al, 2018).
Furthermore, a sales monitoring system enables businesses to know where they
have been, allowing them to identify the strategies that work in their favor to pursue
further success down the road, and as well as identifying which do not work. It fine-tunes
your game plan based on actual figures created and assessed over time (Nwadike P.,
2021).
For Manila Bible Seminary’s Canteen, the system to be developed aims to have a
master list of products, ability to perform and monitor transactions, provide receipts, and
provide sales report.
Project Purpose and Description
Main Objective
The main objective of the study is to develop a Front-end Products and Sales
Monitoring System for Manila Bible Seminary’s Canteen that is efficient, effective and
easy to use.

Specific Objectives
1. To develop a system that is able provide a master list of front-end products.
2. To develop a system that is able to categorize cooked food and packaged food.
3. To develop a system that performs store transactions, which includes items
listing and payment.
4. To develop a system that generates sales history and a sales summary report.
5. To develop a system that has account management.
Scope and Delimitations of the Project
Scope
• The proposed system aims to provide a list of potential front-end products

that the canteen is selling during work hours.
• The proposed system aims to systemize the canteen’s process transaction
recording done within the day.
• The proposed system aims to provide a sales history list with the given
product, price, description, and date of transaction.
• The proposed system aims to compute the total price of the front-end
products to be purchased by students and/or teachers from the canteen.

Limitations
• The system will only track front-end products (delicacies, packaged

snacks, cooked food, meals, etc.) sold by the canteen, as specified by the
beneficiary themselves.
• The system will not track back-end products (raw ingredients) as it is
clarified by the canteen that:
o They replenish their raw stock daily.
o They aim to have nothing left after finishing up for the day.
o They give away leftover cooked meals at the end of the day.
• The system will not track the distributors of the raw ingredients as it is
clarified by the canteen that they provide their own stock of products.
• The system will not track the expiration date of the products within the
canteen:
o They replenish their raw stock daily.
o They aim to have nothing left after finishing up for the day.
o They clarified that for packaged snacks or food they manually do
FEFO (First expired, First out) for their expiry date management.
Operational Definition of Terms
Front-End Products. Is the first product that a new customer buys. For the
proposed project, defines the food served by the canteen through the likes of delicacies,
packaged snacks, cooked food, meals, etc.
Back-End Products. Are the other products you can offer to your existing
customers after they’ve made their initial purchase. For the proposed project, it pertains
to the raw ingredients purchased by the canteen in order to cook front-end products.

CHAPTER II
REVIEW OF RELATED LITERATURE AND STUDIES
Foreign Literature, Studies and Systems
As stated by Margareta & Amesanggeng (2018), a computerized tool that can
store data, process data, and provide desired information accurately is useful for the
company to progress its business. A company needs a monitoring system so that the
information data obtained can be maximized when the data is needed to make a decision.
If the monitoring system cannot be managed properly, it will cause various kinds of
problems that can disrupt the activities of the company. Therefore, it is very important for
a business to have and maintain these systems.
Research conducted by B. P. Zelentsov. (2020) states that the goal of the study is
to create an analytical model of item dependability for settings including technical status
monitoring with a constant inspection frequency and a variety of inspection faults and
failures. The proposed model allows for the calculation and prediction of dependability
indicators while taking explicit and hidden failures, as well as monitoring system factors,
into account. The impact of numerous elements on the level of dependability should be
taken into account while creating new systems and enhancing maintenance processes for
existing systems.
According to Nwadike P. (2021) it’s tough to know what to do next if you don’t
know where you’ve been. Monitoring sales performance allows everyone on the sales
team to identify which strategies are working and which aren’t. By monitoring your
team’s performance, you can make informed judgments. Rather than relying on guessing,
you can fine-tune your game plan based on actual figures created and assessed in real-
time. Furthermore, sales performance analyzes more than just total sales.
According to Audra Bianca, (2015) by using a Sales Monitoring System, a
company makes strategic business decisions regarding purchased raw materials,
scheduling production, pricing, logistics and other decisions in the supply chain. Sales
and inventory enables the company data to increase or decrease production in the factory
so the company won’t have too many finished goods stored in their inventory. The
system collects data to aid in production scheduling. For example, some systems use
recent sale data to forecast how many of a type product will be needed to meet consumer
demand in the near future. The monitoring includes the levels of the product at all
location. The system compares current inventory levels of product and number for
scheduled production with the amount needed and it determines if the level of production
must be changed or not, if change is necessary, the system sends a message to the master
production scheduler to increase production. Also, the system slows down the production
if the products retail sales don’t meet the sales that the company wants to reach.
According to A. Tajewati et al. (2019) Business Government & Enterprise is a
field in PT. Telkom Indonesia is engaged in a large scope, namely marketing products to
businessmen, government agencies, and large companies that use internet access with
different access to home internet. This field requires a reporting system and data
monitoring to make employee performance more efficient. Where reporting and

monitoring contract data or sales will only be accessed through the website so that it
makes it easier for employees to access and make performance more efficient.
Monitoring System is a group of integrated elements that collect and analyze information
from ongoing projects. The purpose of the monitoring system is that sales in the Business
& Enterprise Business can continue to be monitored to the maximum.
According to Magerer, L. K. (2017), the majority of small-scale shops have yet to
embrace technology in their operations, with only 17% having installed a computer-based
system. The study recommends a small-scale shop in Kenya use an application for
inventory accounting and management. The application improves retail accounting and
inventory management operations by overcoming the limitations of the traditional paper-
based approach used by most small businesses. The tool aids merchants in managing
kiosk merchandise, inventories, and sales reports. It has a barcode system built in to make
inventory tracking easier. It has incorporated the VMI system, which allows suppliers to
maintain track of product stock levels, allowing for more efficient and effective inventory
management. The proposed solution was created using an agile development life cycle,
which allows for the solution to be reworked as needed. The solution was designed with a
front-end that was implemented as a mobile app and a back-end that was implemented as
a web app. The web application provides sales statistics and system management, while
the mobile application is utilized by retailers to manage their shop and suppliers to keep
track of inventory levels.

According to Kiselevich, Mitryushkin, Khvistani (2018), digital inventory
accounting, attributed to consumption, allows to differentiate the distribution of stocks
on traditionally sold, promotional, preferential or free meals / drinks, as well as to take
into account the consumption of stocks in connection with damage and combat.
Local Literature, Studies and Systems
According to Laban et al. (2018), a sales monitoring system is a solution for the
management of a small to medium-sized business. It is used to create sales orders,
product orders, payment receipts, and any kind of reports for the management of the
business. The sales monitoring system is also used for easy monitoring of the sales,
updating the price and quantity of the items stored.
According to Dikitanan et al. (2020), nowadays everyone is dependent on
technology. Technologies help people to keep in touch with each other by using mobile
phones and computers. As an ICT student, we conducted research and proposed a
computerized system for our chosen client. Mr. John Hojilla is the owner of Yanz & John
Apparel that still uses a manual system. The main problem with this manual system is
that it can lead to low profit and give the owner a hard time. Yanz and John Apparel
encountered difficulty in monitoring their product and maintaining their security. To
prevent this, the researchers provided a database for the system to lessen the time of
monitoring the products because unorganized products can cause an error.
According to Irawan. R et al. (2021) sales monitoring information system based
on the website can process transaction data so as to produce information in monitoring

sales reports without having to open documents, as well as using the application of sales
forecasting to get sales prediction results. This website-based monitoring information
system conducts interviews and direct observations as a method of data collection.
Monitoring is a systematic collection and analysis of information for an individual
activity. It is widely used in organizations like schools to keep track of day-to-day
operations. Balmes (2016) concluded that the manual day to day monitoring system is
much less efficient. The problems encountered by the faculty members and Dean
contributed to the ineffectiveness and inefficiency of the existing manual system. The
system is a great help because it will lessen the conflicts encountered by the users.
Synthesis of the Reviewed Literature, Studies and Systems
As stated by Labal et al. (2018), a Sales Monitoring System is the type of system
of which small to medium-sized businesses mostly use in order to create sales orders,
product orders, payment receipts, and varying kinds of reports of which is made and
received by the business owner and managers in order to manage and assess the business
properly. It acts as a speedy systemized solution that aids in performing company
processes and procedures in order to maximize efficiency and provide convenience to
company personnel.
Based off Nwadike P. (2021), it is also hard to know what to do next with your
business if you yourself do not know where you’ve been. Having a Sales Monitoring
System allows businesses to identify which strategies are working that brings the them
success, and which do not. Instead of relying on guessing, using a system that focuses on
sales monitoring enables you to get actual figures created and gives accessibility to more
options when assessing the path you would eventually take.
Keeping these in mind, they are the benefits in providing your business a sales
monitoring system. They are in the likes of having product awareness, sales monitoring,
sales report, and more. By having an asset like it, businesses are able to make clear and
sharper decisions that may bring them further success, as well as expand their business
prowess as a whole thanks to processed information that they acquire by using a sales
monitoring system.

CHAPTER III
TECHNICAL SPECIFICATIONS
SOFTWARE
To run the program, the beneficiary would need the following software:
• Operating System: Windows 8, 10 or 11
• Database: XAMPP (MySQL)
• Framework: .NET Framework 4.7.2

HARDWARE
To run the program, the beneficiary would need the following hardware:
• Processor:
o Intel Core-2-Duo or Above
o AMD A8-7600 or Above
• Graphics Card:
o Intel UHD Graphics
o AMD Vega 8
• Storage: Minimum of 100 MB available space
• Memory: Minimum of 4 GB RAM
TECHNOLOGIES
The technologies used to create the system are as follows below:
• Microsoft Visual Studio 2012/2019
• XAMPP Control Panel

FLOWCHART

Found above would be the entire system flow of how users interact with the
system. It ranges from registering an account, to logging in regardless of whether the
account would be an Admin-type or a Cashier-type. As seen above, the Admin would
have privileges to access every available feature found within the system, whilst the
Cashier would only be able to actively interact with two features: the Product’s Master
List and the Transaction Form.
ENTITY RELATIONSHIP DIAGRAM
The diagram shows the connection between the database tables that the system is
utilizing. It showcases the Accounts, Products, Cart, and Sales tables alongside the
attributes that each of them have.

Database: mbs_db
Table: accounts
Field Name Data Type Field Size Description
username varchar 125 For log in form.
password varchar 125 To secure the account.
To specify which user will be
usertype varchar 125
accessed afterwards.
full_name varchar 125 To identify who handles the account.
email varchar 125 To have a way to contact the user.
contact varchar 125 To have a way to contact the user.
Table 1: Data Dictionary of Accounts Table
Database: mbs_db
Table: cart
To specify what product has
cart_prodname varchar 125
been added to the cart.
To specify what kind of product
cart_prodtype varchar 125
has been added to the cart.
To specify how many of the
cart_prodquantity decimal 10 same product has been added to
the cart.
To specify what the total price of
cart_prodtotalprice decimal 10 the products found within the
cart is.
To specify when the transaction
cart_proddate varchar 125
happened.
Table 2: Data Dictionary of Cart Table

Database: mbs_db
Table: products
prod_name varchar 125 To specify what the product is.
prod_type varchar 125
has been added or updated.
To give more clarification to
prod_desc varchar 125 what the product is supposed to
be.
Table 3: Data Dictionary of Products Table
Database: mbs_db
Table: sales
To specify what product has
sales_prodname varchar 125 been added to the sales
monitoring form.
sales_prodtype varchar 125 has been added to the sales
monitoring form.
To specify how many of the
sales_prodquantity decimal 10 same product has been added to
the sales monitoring form.
To specify what the total price
sales_prodtotalprice decimal 10 of the product found within the
sales monitoring form is.
To record when the transaction
sales_proddate varchar 125
happened.

USE CASE DIAGRAM
• The login form is accessible by both types of users so that they may be able to
redirect themselves to their own menus.
• The Admin has power to interact with every possible system ability or feature.
• Both the Admin and Cashier user type are able to manipulate products found
within the system.
• Only the Admin is able to view and interact with the Sales and Transaction
Monitoring feature of the system.

CONTEXT DIAGRAM
The Admin and Cashier are able to directly interact with the system itself whilst
the Customer would only provide their order to which the system would process with the
help of either two latter users. The system would provide more details and information to
the Admin as they are the ones deemed to be the overall overseer of the information
going in and out of the system. The Cashier would take part only in relevant actions such
as providing product details and processing transactions.

NETWORK LAYOUT
The layout of the connection between the system, the device to be used, and the
database is rather quite simple – as per structure based on the canteen and the beneficiary
themselves. They would most likely have one multipurpose laptop that would act as the
system for both Admin and Cashier users. This is simply because the system is built with
a Local Area Network (LAN) in mind, meaning it has no need to connect to the internet
and it would act in a local environment only.

USER INTERFACE DESIGN
The figure above showcases the Login Form to which features two text boxes, a
combo box featuring the user types Admin and Cashier, as well as other quality of life
features including the Login button and the Register button.

The figure above showcases the Registration Form to which features various text
fields to input needed information from the user in order to register a Cashier account
into the system.
The figure above simply showcases the Admin’s Menu once the user logs in.

The figure showcases the Cashier’s Menu once the user logs in as one.
The figure above showcases the Accounts Management Form that only the
Admin-type users are able to see. Featured within it are decoy accounts based off
Genshin Impact’s roster.

The figure above showcases the Products Master List both Admin and Cashier
users are able to manipulate in order to insert the canteen’s potential front-end products,
edit their details, or outright delete them.

The figure above showcases the Transaction Form, or more so known as Point of
Sale within the actual system. This is where the canteen transactions and sales recording
occur.

The figure above showcases the Sales Records form of which presents every
transaction that happened using the system.
CHAPTER IV
METHODOLOGIES
System Requirement Specifications
SOFTWARE
To fully utilize the system properly, the software specifications the user must
have are as follows:
• Operating System: Windows 8, 10 or 11

▪ To run the program, the user must have a few variations of
the recent releases of Microsoft’s Windows operating
system.

• Database: XAMPP (MySQL)

▪ To operate and manage the database the program is using,
the user must install any version of XAMPP and its pre-
requisites to be able to fully utilize the database.
• Framework: .NET Framework 4.7.2

▪ To run the program more efficiently, the user must install
Microsoft’s .NET Framework version 4.7.2 specifically as
it is the Framework the system was developed in.
HARDWARE
To fully utilize the system properly, the hardware specifications the user must
have are as follows:
o Processor:
▪ Intel Core-2-Duo or Above
• The program should be able to run smoothly if the

computer system the program is running on is
around the Dual Core to Intel i5 10th/11th
Generation of processors.
▪ AMD A8-7600 or Above
• The program should be able to run smoothly if the

computer system the program is running on is
around the AMD A8-7600 to Ryzen 5 3600
Generation of processors.
o Graphics Card:
▪ Intel UHD Graphics
• Any built-in graphics component from Intel would

work.
▪ AMD Vega 8
• Any built-in graphics component from AMD’s

Ryzen 3 component would work.
o Storage: Minimum of 100 MB available space

▪ The computer system the program would be running on
should at least have around 100 Megabytes of space.
o Memory: Minimum of 4 GB RAM
▪ The computer system the program would be running on
should at least have a minimum amount of 4 Gigabytes of
RAM in order to function smoothly.
System Development Methodologies
Waterfall Method
A. Requirement Gathering and Analysis
Within the initial stage of the project, the proponents sought out to the beneficiary
and conducted interviews in regards to the kind of processes and work flow that
the canteen has been doing throughout the years. Through the interviews,
information about what traditional work or processes the canteen operates on,
how they are going to bring benefits once systemized, how they are to be
implemented, and what type of system is going to be made overall were gathered
and analyzed.
B. System Design
Through the information gathered prior to this phase, specifications about what
kind of computer system and what programs were chosen in the likes of having
Visual Basic .NET be the foundation of the programming language majorly used
to provide functionality to the system. Visual Studio was used to provide an
efficient workspace to create the interface of the system. Finally, XAMPP or
MySQL was utilized to provide the database connection for the system.
C. Implementation
To begin development, the system was created according to a step-by-step
scenario of finishing off one Visual Basic Form after the other. Firstly, the design
of the form and the placement of the buttons, text fields, drop-down lists, and the
likes were initially placed. Afterwards, coding their functionality came after the
initial design was polished and done.
This was done similarly to the idea of Unit Testing.
D. Integration and Testing
After individually designing each form, as well as coding its functionality, the
forms were compiled into one system and were interconnected through the means
of designing and creating Menu Forms. Menu Forms acted as gateways for the

users to go from one form to another regardless of the type of user they were
(Admin, or Cashier).
E. Deployment of System
The system is yet to be deployed within the canteen as it is planned to be launched
after the testing, project presentations, and approval of the beneficiary are done.
F. Maintenance
Once the system reaches post-deployment, there are plans of innovating and
fixing issues through the act of releasing new versions of the system.
Conceptual Framework
The diagram presents the concept of the system and the requirements it contains:
Input: The proponents gathered information about the proposed system through
conducting interviews with the beneficiary and doing research about potential
systems to be developed. Afterwards, goal setting was done in order to have a
concise path for system development having to create an efficient and easy-to-use
system in mind.
Process: The system was developed according to the information gathered from
the beneficiary’s suggestions, and their requirements. It was further developed by
following the analyzed information through the means of diagrams and
flowcharts. System Testing has also been conducted to further improve various
functionalities that the system possesses.

Output: The end-product program was made according to the gathered
information, diagrams and concepts, and testing.
Testing Procedure
A. Code Quality Review
As the system approaches development, the quality of the code has been
thoroughly examined by the Programmer and Database Manager amidst
development. Members of the makers of the system’s interface also
participate in examining the codes to identify the structure of each form’s
functionality, the purpose of the sets of Classes or Subs the system is utilizing,
and the interconnection between forms to know its processes.
B. Unit Testing

Throughout the development of the program, various iterations of the system
were made and kept stashed unto an archive for potential backtrack usage if
the current build being developed ever developed fatal flaws within its
functionality or interface. Testing each form before moving unto developing
another also became an efficient way of creating the system altogether. Whilst
testing, the programmer and the members of the makers of the system
interface also bundled together to discuss purposes, connections between code
classes and subs, and form connections to thoroughly polish the system.
C. Integration Testing
When testing the system as a whole, certain flaws came to light and there
might be of risk of having more that may be overlooked, though so far
everything that did came to light were dealt with. The system is fully
interconnected now as well through Menu Forms provided for each type of
user that will be interacting and managing it.
D. Performance Testing
To know how well the system fares in other devices, a build of the system
were shared between the programmer and the makers of the system interface
to test how smooth and how fast the system runs on various devices.
Concerning desktops, it runs fine. Concerning laptops however, there is a
slight bit of slowness in comparison to desktops. In regards to the type of bit

the system can run on though, it would only mostly run at best if it was with a
x64 bit Operating System.
E. Security Testing
Regarding the security of the system, it has two types of users that may
manage and interact with it. They are as follows:
a.) Admin – they possess the power to interact, manipulate, and use all of
the features that the system provides, including those that other user
types are unable to see due to the difference in user level.
b.) Cashier – they possess the ability to interact with two forms only:
a. Products Master List – contains all of the potential front-end
products that the canteen sells. It is categorized by the type of
product they are.
b. Transaction Form – contains the main processes of the system
in regards to choosing which products are to be bought by the
customer, as well as recording the transaction that occurred for
sales and transaction monitoring.
This was done according to the potential user to be interacting with the
system itself upon deployment.

CHAPTER V
SUMMARY AND RECOMMENDATIONS
This chapter contains the summary and recommendations that have been reached
by the proponents whilst undertaking this project. The results of the project are
summarized to show how effective the system is and recommendations are given as well
to further improve future development of the project or for future researchers.
Summary
The proposed system consists of 4 computer units and a barcode scanner. The
barcode scanner is for scanning the barcode sticker and will be deciphered to print a
readable item description. Each computer unit is connected to a Local Area Network
(LAN) and connected to a single database for retrieving/sending data from 1 computer
unit as a Server. The usage of barcode scanner is to record the stocks that has been
released in the warehouse of the company. The proposed system requires a network hub
for connecting the 4 computer units. The Windows 7 Professional will be used as an
operating system for the computer and MySQL will used as the database of the system.
These hardware and software will be used for five years to handle or to maintain the
inventory system with barcode scanner and the Local Area Network. The Uninterrupted
Power Supply (UPS) will not be provided though it is essential; the company will decide
for providing the equipment.

Recommendations
The proposed inventory system with barcode scanner enables the company to
control the company’s asset tracking needs and fixed assets. Barcode Technologies are
known of their quality, proven reliability, ergonomic design, and ease of use. This kind
of inventory system monitors the products of the company to gain visibility and control
the inventory and stock levels. It also reduces time spent searching for inventory,
eliminate stock outs, and improve customer service. Inventory levels and reorder points
will now be easy to manage, track, and control. The (name of the company) has an
inventory system which is manually conducted. Innovation from manual to computerized
will greatly benefit the company.

APPENDICES
(All APPENDICES must have separate pages.)

APPENDIX A
Gantt Chart

APPENDIX B
Context Diagram
(and so on… complete the Appendices indicated in the Table of Contents)

APPENDIX E
(…and so on, PLS. SEE THE TABLE OF CONTENTS.)

BIBLIOGRAPHY
(Use APA Style 6th Edition, label them with Books, Dictionaries,
Online Sources, etc.)
Books
Journals
Online Sources

CURRICULUM VITAE
(Center this on a page)

(Individual CV follows. Example of format given on the next page.)

JAMES L. DELA CRUZ Your photo
Blk. 8 Lot 10 Pines Ville, North Fairview, Quezon City
here 1x1
0917 7654321
jamesdc@yahoo.com
______________________________________________________________________
PERSONAL INFORMATION
Date of Birth:
Place of Birth:
Citizenship:
Gender:
Civil Status:
Interest:
______________________________________________________________________
EDUCATIONAL BACKGROUND
Primary:
Secondary:
Tertiary:
Bachelor: Quezon City Polytechnic University (Information Technology)
______________________________________________________________________
PERSONAL QUALIFICATION
Note:
1. Kindly follow all the instructions. Delete unnecessary details especially those enclosed in
parenthesis and with red fonts.
2. Use Font Times New Roman size 14 for your Title (Title Page), Times New Roman 12 for the
rest with Double Spacing.
3. Print your document in a LONG BONDPAPER. Submit in a folder with clip.
4. Include page numbers (except on chapter titles)
5. Photo must be in uniform or business attire.


Quezon City University: Front-End Product and Sales Monitoring System For Manila Bible Seminary's Canteen

Uploaded by

Document Information

Original Description:

Original Title

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

Quezon City University: Front-End Product and Sales Monitoring System For Manila Bible Seminary's Canteen

Uploaded by

Copyright:

Available Formats

QUEZON CITY UNIVERSITY i

Front-End Product and Sales Monitoring System for Manila Bible

A Software Engineering Project Documentation

(March 23, 2022)

DEPARTMENT OF INFORMATION TECHNOLOGY

In partial fulfillment of the requirements for the degree BACHELOR OF SCIENCE IN

<< Please Insert Your Advisers Name >>

Approved by the Committee for Project Presentation with a notation of

ISAGANI M. TANO, DIT

ISAGANI M. TANO, DIT

DEPARTMENT OF INFORMATION TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY

end of your project development.)

DEPARTMENT OF INFORMATION TECHNOLOGY

Dedication .......................................................................................................................... iii

Executive Summary ............................................................................................................ v

Table Of Contents .............................................................................................................. vi

List Of Tables .................................................................................................................. viii

List Of Figures ................................................................................................................... ix

List Of Appendices ............................................................................................................. x

CHAPTER I Project Background ..................................................................................... 11

Project Background and Context .................................................................................. 11

Project Purpose and Description ....................................Error! Bookmark not defined.

Main Objective...........................................................Error! Bookmark not defined.

Specific Objectives ....................................................Error! Bookmark not defined.

Scope and Delimitations of the Project ..........................Error! Bookmark not defined.

DEPARTMENT OF INFORMATION TECHNOLOGY

CHAPTER II Review of Related Literature and System.................................................. 14

CHAPTER III Technical Specifications ........................................................................... 15

Diagrams and Flowcharts ..............................................Error! Bookmark not defined.

Network Layout ............................................................................................................ 26

Hardware Design Layout ...............................................Error! Bookmark not defined.

CHAPTER IV Methodologies .......................................................................................... 34

System Requirement Specifications ............................................................................. 34

System Development Methodologies ........................................................................... 36

Testing Procedures ........................................................................................................ 39

CHAPTER V Summary and Recommendation .................Error! Bookmark not defined.

References ..........................................................................Error! Bookmark not defined.

DEPARTMENT OF INFORMATION TECHNOLOGY

Table no. Table Title Page No.

DEPARTMENT OF INFORMATION TECHNOLOGY

Figure no. Figure Title Page No.

DEPARTMENT OF INFORMATION TECHNOLOGY

Appendix Title Page No.

DEPARTMENT OF INFORMATION TECHNOLOGY

San Bartolome, Novaliches, Quezon City. It consists of an administration leading its

Accountancy division of the seminary. The canteen’s employee is comprised of a humble

middle-age woman, as well as seminary student volunteers.

students to avoid the spoilage and waste of food.

DEPARTMENT OF INFORMATION TECHNOLOGY

Project Background and Context

(Margareta et. al, 2018).

Furthermore, a sales monitoring system enables businesses to know where they

provide sales report.

Project Purpose and Description

DEPARTMENT OF INFORMATION TECHNOLOGY

1. To develop a system that is able provide a master list of front-end products.

3. To develop a system that performs store transactions, which includes items

listing and payment.

5. To develop a system that has account management.

Scope and Delimitations of the Project