InvenDora: A web-based meat inventory management system for Lolong
and Lucy's Goat store
A Design Project
Presented to the Faculty of the
Department of Computer, Information Sciences and Mathematics
University of San Carlos
In Partial Fulfillment
of the Requirements for the
CIS 2205- Design Project Course
By
Jason Kyle Avanceña
Ma. Carmela L. Labandiro
Jon Francis S. Pasana
Ashley Mae M. Turla
Beethoven Arellano Jr.
Adviser
December 2021
ABSTRACT
Creating a paper receipt and misplacing it could hinder your business and
could harm it. A mistake of losing one's order receipt could also be a danger of
losing a customer. Creating the order in paper-based takes time especially if you
wrote the wrong information. Being able to digitize a business is an assurance
not only for keeping track of your order history but it is also a great way for you to
grow your brand, gain new insights and acquire loyal customers. The InvenDora
system is a user-friendly system that tracks the order history, orders of the
customers, updates, adds a user, updates stock, and creates a new order in the
most simple way possible
ii
TABLE OF CONTENTS
ABSTRACT ii
TABLE OF CONTENTS iii
LIST OF FIGURES v
LIST OF TABLES vi
CHAPTER 1 1
1.1 Rationale of the Study 1
1.2 Statement of the Problem 2
1.2.1 General Objective 2
1.2.2 Specific Objectives 2
1.3 Significance of the Study 3
1.4 Scope and Limitations 4
CHAPTER 2 5
CHAPTER 3 10
CHAPTER 4 13
4.1 Conceptual Framework 13
4.2 Analysis and Design 14
4.2.1 Use Case Diagram and Description 14
4.2.2 Entity Relationship Diagram 18
4.3 Development Model 19
4.4 Development Approach 21
4.5 Software Development Tools 22
4.6 Project Management 23
4.6.1 Schedule and Timeline 23
4.6.2 Responsibilities 25
iii
4.6.3 Budget and Cost Management 26
4.7 Verification, Validation and Testing 27
BIBLIOGRAPHY 28
APPENDIX A 31
APPENDIX B 33
APPENDIX C 34
CURRICULUM VITAE 46
iv
LIST OF FIGURES
Figure 1. Data Flow and Framework 13
Figure 2. Use Case Diagram 14
Figure 3. Entity Relationship Diagram 18
Figure 4. AGILE Development Model 19
Figure 5. Development Approach 21
v
LIST OF TABLES
Table 1 : Summary of Related Systems 9
Table 2 : Use Case Description of Log In 15
Table 3 : Use Case Description of Create, Edit, Manage Product 15
Table 4 : Use Case Description of Create, Edit, Manage Reservation/Orders 16
Table 5 : Use Case Description of Create New User/Admin 17
Table 6 : Use Case Description of View History and Order Details 17
Table 7 : Software Development Tools 21
Table 8 : Gantt Chart of Activities, First Semester, SY 2021-2022 23
Table 9 : Responsibilities 26
Table 10 : Budget and Cost Management 26
Table 11 : Acronyms and Definitions 34
Table 12 : Functional Requirements 35
vi
CHAPTER 1
INTRODUCTION
1.1 Rationale of the Study
Since the creation of the first computers and systems, accounting and
businesses in general have benefited greatly from the numerous functions
brought by advancing technology. Information technology revolutionized and
significantly sped up growth in businesses across industries around the globe by
creating efficiency and providing a safe, reliable way for storing financial and
important data. Thus, more and more advancements eventually led to
computerized systems dedicated to handling and easing all finance related
matters and were created with the purpose of replacing the traditional, manual
ways of accounting.
There is no argument to switching over from a manual accounting system
to a more modern, computerized system. In manual accounting, journal entries,
invoices and other documents are to be made by hand, while computerized
accounting has users inputting this information into software programs dedicated
to handling these tasks. With this, computerized accounting systems produce
information much faster compared to manual accounting systems (Amahalu et
al., 2017). However, it must be taken into account that a change in the way
business is handled can have a different impact on productivity, especially in its
early days when users still have to learn the new system and adapt to it. Costs,
maintenance, and installation fees are also significantly higher when compared to
manual accounting. Nevertheless, performance is also significantly higher, and
the period during the adoption of computerized systems does not have a great
negative impact on business. Studies show that users who utilize computerized
accounting systems finish their job more effectively and have greater quality and
quantity of work, and while users who still use manual accounting claim they
finish their job accurately, they still find computerized systems to be more
convenient to use and set (Arcega et al., 2015).
1
With all this, the PovaDora goat store family business has been running
on a manual accounting system ever since it started. The family has been
struggling in organizing the records of receipt in its paper-based form most
especially if they lose it. Having paper-based records of receipts and order
records may also need a lot of space for storing, as there are a lot of orders from
the different customers. It also takes time in writing the record, especially since
everything is handwritten. This difficulty also includes updating the order where
our client needs to carefully write the order and receipt. Thus, it would be safe to
say that transitioning from a manual system to computerized will be a large help
to PovaDora, and even much more so if they were to adopt a system that takes
into account the form and heart of their business, meat products.
1.2 Statement of the Problem
1.2.1 General Objective
The main goal of this research is to create a web-based inventory
management application specially designed for a meat-based
business, namely Povadora’s Goat Store.
1.2.2 Specific Objectives
This research aimed at:
1. To improve upon the work conditions and business efficiency
in Povadora’s Goat Store by allowing the business to
transition from manual paperwork to a computerized system.
2. To identify and improve upon aspects of an inventory system
that can cater to and benefit the management of inventories
mainly storing meat.
2
○ Add and create functionality for keeping track of how
many kilos of a certain product is currently
available/stored
1.3 Significance of the Study
The output of this research is a web-based inventory management system
beneficial to the following:
PovaDora Family Business. The business has been documenting their
data on papers, which takes time and has the risk of losing important information.
With the inventory management system, they will be able to keep track of their
inventory safely and efficiently.
Customers. People want meat products to be fresh, delivered on time,
and within their budget. This inventory management system can help guarantee
that the freshness of the meat is kept tracked, while also accounting for the right
price range, so that customers can buy the best goat meat quality there is.
Meat Shops. Meat Shops are a necessity as they provide quality meat
products that we use in our everyday meals. An inventory management system
can help improve the management in the quality and quantity of meat provided to
the customers.
Computing Field. People in the computing field, especially those that
specialize in Inventory Management Systems can make use of the different
functionalities that the application presented in the research. Further research
can be made to create more efficient algorithms to keep track of the inventory
data.
3
1.4 Scope and Limitations
The system utilized a database catered to handling products and
inventory. The database entries contain information for managing meat products,
namely the product’s name, available stock (in kilograms), and price per
kilogram. Its features are based only on recommendations and gaps in the
PovaDora business.
The system only has two types of users: (1) Registered users and (2)
Administrators. Both of these types of users can only be created by an
administrator. There is one provided default administrator account, while
users/employees must agree to having a registered account should they be
registered users. Internet connection is always present when using the
application.
4
CHAPTER 2
RELATED SYSTEM
With the advent of computing systems and technology, a lot of systems
have been created by engineers to boost efficiency in handling and managing
data with regards to business and sales. Inventory management systems that
keep track of finances, sale history, and current inventory stock are
commonplace and prove very beneficial to businesses through the use of
automation and ease of use, brought by its design and the many functions that
computers can provide to users.
Security
Most if not all inventory systems have functions in place in order to protect
assets and data. One of these functions is an admin system, wherein different
users and accounts are registered within a database that have assigned levels of
permission for access to certain functionalities of the system. To add, only users
that have been given accounts may actually use the system in order to prevent
unwanted tampering of inventory data and create a way for allowed identities to
be verified.
As such, Abisoye et al. (2013) implemented a login page as the entry point
for their system to ensure security, after which a splash screen and the main
menu is shown upon successful entry.
Main Inventory System Functionality
Inventory systems implement functions that serve their desired goal, which
is to keep track of important business inventory information and the like. One of
these important functions comes in the form of a module/page that allows the
user to record, update, or add stock and show inventory history and activity.
Soegoto & Palalungan (2020) implements a related module within their
information system that records receipts and inventory sent to other divisions in
5
the business. This data and history is recorded and can be found in the system’s
Details menu.
Traceability
Basic inventory management and traceability tracking are must-have
features in software systems for all meat producers. Traceability is the
identification of individual, real-life goods using a "lot number" or "batch number"
that stays with each food item as it passes through the inventories, and inventory
management encompasses a set of business activities that include receiving,
production, and sales.
Meat processors must keep records for basic inventory management and
traceability, the receiving of products will include the parts of the meat ordered. A
batch number should be entered for each item received. If the supplier or original
maker hasn't allocated a batch number to the item, you'll need to assign one. All
of your final product sales should be tracked. Customers' identities, as well as the
batch number of each item sold to them, should be kept track of. Recall features
should be able to simply construct a report that traces the supplier, inventories
in-stock, goods created, and consumers for any ingredient or finished product
using the lot tracking utilized throughout the system. For actual recall events, as
well as simulated recalls and traceability verification for third-party audits and
certifications, it's critical to use recall features.
ACCTivate
The ACCtivate system is an inventory management system that includes
lot tracking, partial catch-weight support, and barcode scanning, but no scale
integration. ACCTivate can track inventory down to the component level and
calculate sales based on weight. Tracking both pieces and weight for inventory
tracking and reporting does not work. Only on sale is the catch weight. It is
possible to manually add weights to each piece, but it is not compatible with a
digital scale.
6
ACCTivate is a client/server software solution for Microsoft Windows that
connects with QuickBooks desktop versions. For a multi-user situation, you'll
need to install it on your own computer, which should be a server computer on
your LAN. Instead of maintaining your own server, you might pay a fee to have it
hosted by a third-party hosting service.
DEAR Inventory
The DEAR Inventory is a cloud-based inventory management system
that's simple to use and best suited for uniform weight final products, such as 12
ounce packaged beef jerky. DEAR includes powerful lot monitoring and food
safety recall functions, as well as barcode scanning and label printing, and it will
generate recall customer letters automatically. DEAR integrates with a variety of
cloud-based systems, including cloud-based accounting systems QuickBooks
Online and XERO, eCommerce solutions Shopify, Amazon, Bigcommerce,
WooCommerce, Magento, eBay, Neto, and Etsy, shipping logistics system
ShipStation and point-of-sale and payment processors PayPal, Vend, Stripe,
and Square. For individuals who want to personalize reports and forms, DEAR
now integrates with MS-Office Word.
At-Thoyyib Shop Inventory Management System
At-Thoyyib Inventory Management System is an online system that
facilitates the management, entry and exit of goods, namely frozen goods,
household items and organic drugs. Rather than writing down inventory data on a
book which could be damaged or have written the wrong data, At-Thoyyib
Inventory Management System provides an easier way of recording data and an
efficient and accurate report generation for the store manager. The system uses
the Waterfall Model as it is easy to explain to users. It includes an Inventory
Module for displaying categorized items, Search Module to search for items and
suppliers, Supplier Module for the list of suppliers, Payment Module to record the
sales, Damaged Goods Module to keep track of damaged goods, and Reporting
Module to compile a list of all the reports.
7
Inventory Optimization of Fresh Foods
Fresh food, such as meat products, can easily spoil within a matter of
days when not properly managed. There should be an inventory control system
for fresh products. A study was conducted on analyzing the inventory
management of fresh pork in Shang Mao Cheng Supermarket. First, it is found
that consumers are sensitive to the price and freshness of the pork. Second, the
best sales cycle of pork is three days, as the fourth day will cause a decrease in
quality. Third, the price is the highest during the preservation period of the meat,
slightly higher than market price, and gradually decreases at the end of the sales
cycle.
Web-Based Inventory Management System
This system was created to improve inventory management for a small
business company. Using a web-based inventory system, it would allow multiple
users to access from varied locations, allow the office to easily gain access to
store information and perform system maintenance, easily implement business
rules and update business data, boost efficiency in managing the daily business
activities, which can result in more satisfied customers, increasing revenue.
As shown in Table 1 are the related systems being cited in this study.
8
Table 1
Summary of Related Systems
Name of Website Tracking Barcode Software Inventor Search
Application application Scanning Application y Module Module
ACCTivate ✔ ✔ ✔
DEAR ✔ ✔
At-Thoyyib ✔ ✔ ✔
InvenDora ✔ ✔ ✔ ✔
9
CHAPTER 3
TECHNICAL BACKGROUND
This chapter discusses the various tools, features, and concepts that were
discovered to be beneficial to the proposed system.
Hypertext Transfer Protocol Secure (HTTPS)
The session between the web server and the browser on your mobile
device is encrypted if you see https. By glancing at the Uniform Resource
Locator (URL) in your browser's web address bar, you may quickly identify web
servers that have https enabled.
The Secure Socket Layer (SSL)/Transport Layer Security (TLS) protocol is
a combination of the Hypertext Transfer Protocol (HTTP) and the Secure Socket
Layer (SSL)/Transport Layer Security (TLS). TLS is a security and authentication
protocol that is widely used in browsers and Web servers. SSL encrypts data
sent over an SSL connection with the use of a public key. SSL is supported by
the majority of web browsers.
Hyper Text Markup Language (HTML)
HyperText Markup Language (HTML) is the set of markup symbols or
codes inserted into a file intended for display on the Internet. It is the computer
language that facilitates website creation. The markup tells web browsers how to
display a web page's words and images. HyperText is the method by which
Internet users navigate the web. By clicking on special text called hyperlinks,
users are brought to new pages. The use of hyper means it is not linear, so users
can go anywhere on the Internet simply by clicking on the available links. This is
the main structure that the web application uses.
CSS Framework
CSS frameworks provide a basic structure for designing consistent
solutions to tackle common recurring issues across front end web development.
They provide generic functionality which can be overridden for specific scenarios
10
and applications. This greatly decreases the time needed to start creating
applications and websites. It is particularly useful when arranging all the
application’s functionalities with a friendly user interface in mind, allowing the
user to use the application with ease. The CSS Framework goes hand-in-hand
with HTML to create the UI and design of the application, which will be the main
interactive point end-users will depend on.
Database MySQL
MySQL is an open source Relational Database Management System
(RDBMS) with a client-server model. RDBMS is a software or service used to
create and manage databases based on a relational model (Richard B. 2021). It
creates a database for storing and manipulating data, using a key to link data
from two different tables. This is widely used by e-commerce and warehouses to
organize data. The developers will make use of MySQL to create the main
database and will serve as an important back-end module in the application.
Git
Git is a distributed revision control system that is accessible as free
software on all major development platforms. Git distinguishes itself from its
forerunners by elevating the software's modifications to first-class citizens.
Software revisions are important to developers, and git enables this by providing
each developer with a complete private copy of the software repository and a
variety of techniques to manage changes inside it. The ability to link a local
repository to many remote ones enables developers and their managers to
create a wide range of interesting distributed processes, the majority of which
would be difficult to run on a standard centralized version control system. The
local repository also makes git more responsive, simple to set up, and
independent of the Internet.
GitHub is a git repository hosting service that uses a Web-based user
interface to simplify many repository maintenance activities while also
encouraging collaboration in open source projects. (Spinellis, 2012, 100-101). It
11
is the main repository that the developers will use to keep track, update, and
manage the development of the application.
PHP language
PHP is a free popular server-side open-source programming language
mainly used in developing web applications and sites. Its features include but are
not limited to:
● Manipulate, add, manage, delete, create files on the server (back-end)
● Communicate with a database
● Allow developers to create dynamic content on the webpage
● Control permissions, who uses the application
Mainly in the back-end, the application will use PHP as its main
programming language. It is used to communicate with the database created
using MySQL, and its seamless integration and ability to be embedded with
HTML allows for ease of development.
12
CHAPTER 4
DESIGN AND METHODOLOGY
4.1 Conceptual Framework
Figure 1 presents the main flow of the application and how data is
processed. There are four main modular components that work in conjunction to
achieve the desired functionalities. Each component’s functionalities are
categorized into their own in the figure.
1. Product Database: Show different products in stock, their
descriptions, and price per kilo.
2. Order/Reservation: Keeps track of current orders or reservations
and respective customer information, and history of past orders.
3. User System: For security and administrative capabilities.
Figure 1. Data Flow and Framework
13
4.2 Analysis and Design
4.2.1 Use Case Diagram and Description
The application requires a registered user in order to access and
use the system’s features and functionalities. This user’s capabilities
include logging in and out of the system, accessing and viewing the
products in stock, adding new products, creating reservations, and
managing reservations (order finished, order cancelled, etc.). The user
must be created in the database beforehand in order to be able to access
the system using their own supplied login credentials. Admins are given
this capability to create new user accounts.
Figure 2. Use Case Diagram
14
Table 2
Use Case Description of Log In
Use Case Name: Log In
Brief Description: A registered user logs in to the system
Actor: Registered User
Precondition: The user must already have an account
The user must be on the Login Page
Post-condition: The user successfully logs in to the system
Flow of Activities: 1. Input the required fields - username and password
2. Click the Login button
Alternative Flow: 2.1 If not all text fields are inputted, an error message
will be prompted and the sign in will be unsuccessful
2.2 If the text field contains an invalid input, an error
message will be prompted and the sign in will be
unsuccessful
Table 3
Use Case Description of Create, Edit, Manage Product
Use Case Name: Create, Edit, Manage Product
Brief Description: A user is able to create, edit and manage products
Actor: Admin, Registered User
Precondition: The user must be on the Products page
Post-condition: The user can view the list of products
Flow of Activities: Create a new Product
3. Add a new product by clicking the New Product
button
4. Input all the product information required
5. Click Add product
Search a Product
6. Click on the search bar
7. Input the product to be searched
8. Click the Search button
9. A list of Products will be returned
Alternative Flow: 2.1 If not all text fields are inputted, an error message
15
will be prompted and the add product will be
unsuccessful
2.2 If the text field contains an invalid input, an error
message will be prompted and the add product will be
unsuccessful
3.1 If there is a mistake with the information with the
added product, the user clicks on Edit.
3.2 Edit the information needed to be changed
3.3 Click the Save button
7.1 If there is no Product listed, a blank Product page
will be shown
Table 4
Use Case Description of Create, Edit, Manage Reservation/Orders
Use Case Name: Create, Edit, Manage Reservation/Orders
Brief Description: A user is able to create, edit and manage
reservation/orders
Actor: Admin, Registered User
Precondition: 1. To create a new order, user must be on the New
Order Page
2. To view order list, user must be on the Orders
Page
Post-condition: The user can view the list of orders
Flow of Activities: Create a new Order
1. Go to New Order Page
2. Input the Customer and New Order Information
3. Click Add Order button
Search Order
4. Click on the search bar
5. Input the order to be searched
6. Click the Search button
7. A list of orders will be returned
Alternative Flow: 2.1 If not all text fields are inputted, an error message
will be prompted and the add order will be
unsuccessful
2.2 If the text field contains an invalid input, an error
message will be prompted and the add order will be
unsuccessful
3.1 If there is a mistake with the information with the
16
added order, the user clicks on Edit.
3.2 Edit the information needed to be changed
3.3 Click the Save button
7.1 If there is no Order listed, a blank Order page will
be shown
Table 5
Use Case Description of Create New User/Admin
Use Case Name: Create New User/Admin
Brief Description: A user is able to add a new user/admin
Actor: Admin, Registered User
Precondition:
Post-condition: The user can view the listed users
Flow of Activities: 1. Click the New User button
2. Input all the necessary information for the new user
3. Click Add User button
Alternative Flow: 2.1 If not all text fields are inputted, an error message
will be prompted and the add user will be unsuccessful
2.2 If the text field contains an invalid input, an error
message will be prompted and the add user will be
unsuccessful
Table 6
Use Case Description of View History and Order Details
Use Case Name: View History and Order Details
Brief Description: A user is able to view the history and past order details
Actor: Admin, Registered User
Precondition: User must be on the History Page
Post-condition: The user can view the history of past orders
Flow of Activities: 1. User can view on the details of past orders
17
4.2.2 Entity Relationship Diagram
Figure 3. Entity Relationship Diagram
As shown in Figure 2, Use Case Diagram, the registered user can access
all the modules . The admin can access all modules.
18
4.3 Development Model
The project will be implemented through the agile method. The agile
method is able to administer the process for managing a project that involves
constant collaboration and working in continuous iterations of development and
testing throughout the software development cycle of the project. In addition, it
breaks down the project into several phases to deliver project accomplishments
smoothly. (Hamilton, 2021)
Figure 4. AGILE Development Model
The AGILE Development Model consists of the following steps, each of
which must be completed before moving on to the next.
Plan refers to the gathering of all possible requirements of the system.
The researchers will interview the client about their business information
gathering for the project in order to identify the system’s main functionalities and
provide possible solutions through the system.
19
Design involves the process of identifying possible features and how the
system will operate for the user. The researchers will design a prototype of the
system in order to provide a visual representation of the system to the client.
Development is the stage where both front-end, back-end and also the
database will be coded.
Test this is the stage where it entails a thorough examination of the
features and the functionalities of the system and its other components to identify
any potential problems. The blockbox testing will be performed by the developers
in collaboration with the client.
Deploy this is the stage where the application will be available on the
web.
Review this stage refers to reviewing the system after the deployment and
further testing will also be conducted.
Launch this is the final stage, it is where the system will be released for
the client to be used.
First, the researchers must figure out what the client expects from the
system. The client was searching for a simple approach to manage their sales,
such as adding, updating, reading, and/or deleting/cancelling orders transactions,
these will be some context of the system. The method then progresses to the
following level until the last stage is accomplished. This method enables rapid
and continuous collaboration as well as the breakdown of the application
development into sprints in order to meet a deadline and test the outcomes.
Every sprint requires everyone’s participation. Goals that were not met in the
previous sprint can be carried over to subsequent sprints.
20
4.4 Development Approach
The application system was designed using a mixture of the top-down and
bottom-up approach. First, the main product database component was created
as this was essential for creating two of the other main components, the Report
System and the Reservation System. The user/admin system was designed
separately from the other components as there is not much overlap in
functionality between them except for access and permission. Figure 4 presents
the approach that was used in the study.
Figure 5. Development Approach
4.5 Software Development Tools
The table below is the list of the tools the researchers use in the
development process, as well as their versions, sources, and
functionalities.
Table 7
Software Development Tools
Software Version Functions
Visual Studio Code 1.5.0 Text editor
Visual Studio 2019 16.11 Text editor
21
Google Chrome 86.0.4240.75 Provides a web
browser simulation of
the application.
PHPMyAdmin 4.9.7 This program is used
to access, utilize, and
manage the
database.
MySQL 8.0.21 To provide a
relational database
management system
XAMPP 7.2.34 Used for setting up
the database server.
Git 2.29.0 Free and
open-source
distributed
version-control
system
Github N/A Merging of code
online and keeping
track of updates from
other developers.
4.6 Project Management
This section covers the topics on schedule and time, responsibilities,
budget and cost management.
22
4.6.1 Schedule and Timeline
To ensure that the output is completed efficiently, the researchers
must adhere to the system’s development timetable and deadline.
Table 8
Gantt Chart of Activities, First Semester, SY 2021-2022
First Semester
Month September October November December
Week 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4
Activities
Plan - Data Gathering
Plan - Documentation
- Chapter 2 Related
System
Plan - Documentation
- Chapter 3 Technical
Background
Plan - Research
Objectives &
Statement of the
Problem
Plan - Documentation
- Chapter 4 Design
and Methodology
Plan - Appendices &
CV
Plan - Documentation
- Chapter 1 &
Abstract
Design - Designing of
Prototype based on
Specifications
Finalizing the
23
Documents
Develop - Initial
UI/UX Development
Develop and Test -
Sprint 1 UI/UX
Development Design
Changes - Web
Develop and Test -
Sprint 2 Login and
Registration Page
and Dashboard
Develop and Test -
Sprint 3 History
Module
Develop and Test -
Sprint 4 Add Product
Module
Develop and Test -
Sprint 5 Product List
and New Order
Module
Develop and Test -
Sprint 6 Order List
and Search Module
Test - User
Acceptance Testing
Presenting to Client
and Application
Review
4.6.2 Responsibilities
As the system develops, members are assigned to one or more
modules. If a member’s module is unable to be completed, the other
members can aid in the completion of the module.
24
Table 9
Responsibilities
Member Role Assignment
Jason Kyle Avanceña Front-end and Back-end Login & Registration Page
Developer and Dashboard
Ma. Carmela Labandiro Front-end and Back-end History Module and Add
Developer Product Module
Jon Francis S. Pasana Front-end and Back-end Product List Module and
Developer New Order Module
Project Manager
Ashley Mae M. Turla Front-end and Back-end Order List Module and
Developer Search Module
4.6.3 Budget and Cost Management
Members must strictly stick to the expenses listed in the table
below when developing the system in order to reduce the amount of
money spent on the system’s development and research as a whole.
Table 10
Budget and Cost Management
Items Quantity Cost
Laptop 1 20,000.00
Data/Wifi 1 999.00
Electric Bill 1 500.00
Snacks 10 250.00
Hostinger (web hosting) 1 1500.00
Total 14 23,249
25
4.7 Verification, Validation and Testing
When used on large systems, black-box testing is effective. Block-box
testing refers to testing a system without prior knowledge of the coding or internal
workings. User-acceptance testing is a type of testing in which the end user, such
as the client, verifies the application’s functionality and accepts the software
application before it is deployed. UAT is done at the end of the testing process.
The block box testing method will be used by the researchers. Black box
testing enables testers to examine and analyze data communication between
modules as well as their functionalities. Two(2) family members of the owner will
conduct the testing. Furthermore, any bugs discovered will be documented and
fixed by the developers.
Afterterwards, the system will be validated for User Acceptance Testing to
ensure it is ready for deployment. The system will then be evaluated, with
features, durability, usability and efficiency rated. Miss Celine Povadora, the
daughter of the owner of Lolong and Lucy’s Goat Store will carry out the task.
26
BIBLIOGRAPHY
Abisoye, O. A., Boboye, F., & Abisoye, B. O. (2013, September 1). Design of a
computerized inventory management system for supermarkets. Index of /.
Retrieved September 16, 2021, from
[Link]
Akihiko Tozawa, Michiaki Tatsubori, Tamiya Onodera, and Yasuhiko Minamide.
2009. Copy-on-write in the PHP language. SIGPLAN Not. 44, 1 (January
2009), 200–212. DOI:[Link]
Amahalu, N., Abiahu, M.-F. C., & Chinyere, O. (2017, July 27). Comparative
analysis of computerized accounting system and manual accounting
system of quoted microfinance banks (mfbs) in Nigeria. SSRN. Retrieved
October 21, 2021, from
[Link]
Arcega, C. K., Datinguinoo, E., Guerra, J., Guno, C., Mayuga, H. J., Villamena,
E., & Manongson, J. L. (2015). Computerized vs. Non-computerized
Accounting System of Small and Medium Enterprises in Lipa City,
Philippines: A Comparative Analysis . Asia Pacific Journal of Academic
Research in Business Administration , 1(1), 48–55.
Boiko, A., Shendryk, V., Boiko, O. (2019). Information systems for supply chain
management: uncertainties, risks and cyber security. ScienceDirect.
Retrieved October 1, 2021 from
[Link]
article/pii/S1877050919301152.
D. Spinellis, "Git," in IEEE Software, vol. 29, no. 3, pp. 100-101, May-June 2012,
doi: 10.1109/MS.2012.61.
Hamilton, T. (2021, September 24). Agile Methodology: What is Agile Software
Development Model & Process in Testing?. Guru99. Retrieved October 1,
2021, from [Link]
Hayes, A. (2021, May 19). Hypertext markup language – html. Investopedia.
Retrieved September 15, 2021, from
[Link]
27
Huang, K. (September 27, 2019). Inventory Optimization of Fresh Foods Based
on Shang Mao Cheng Supermarket. ACM. Retrieved October 1, 2021,
from [Link]
4384.
Ilias, J., Kasim, S., Hassan, R., Mahdin, H., Ramli, A. A., Fudzee, M. F. M., &
Salamat, M. A. (2017, November 12). At-Thoyyib Inventory Management
System. CORE. Retrieved September 17 2021, from
[Link]
Mazlan, M. B. (2007, July). Inventory Storage System. CORE. Retrieved
September 17, 2021, from [Link]
Sanyal, C. (2005). Development of a Web Based Inventory Management System
for a Small Retail Business. All Regis University Theses. Retrieved
October 1, 2021, from
[Link]
=theses.
Saxena, R. (2019, January 9). A beginner's guide to Css front end frameworks.
Medium. Retrieved September 15, 2021, from
[Link]
45a499456b.
Soegoto, E. S., & Palalungan, A. F. (2020). Web based online inventory
information system. IOP Conference Series: Materials Science and
Engineering, 879, 012125.
[Link]
Software for inventory & traceability tracking for meat processors. University of
California, Agriculture and Natural Resources. (n.d.). Retrieved September
16, 2021, from
[Link]
sources/sdf/.
What is an API? The (Complete) application programming interface definition.
The BigCommerce Blog. (2021, February 25). Retrieved September 15,
2021, from
[Link]
28
What is mysql: Mysql explained for beginners. (2021, August 19). Hostinger
Tutorials. Retrieved September 30, 2021, from
[Link]
29
APPENDIX A
TRANSMITTAL LETTER
30
31
APPENDIX B
INTERVIEW GUIDE
The researchers conducted an interview with the client with open-ended
questions in order to gain more insight and information about their business and
what possible features and functionalities may be implemented in order to appeal
to their workflow. The answers were utilized to tailor the inventory system to their
needs. The guide questions are shown below:
1. What is your business?
2. What is the flow of your business/how is your business run?
3. What systems do you have in place for the business? (inventory
management, stock management, etc.)
4. How do you currently manage your data?
5. What are the usual problems you encounter when running your
business?
6. Are there any aspects of your business that you’d like to be more
efficient?
7. Is your business using any digital applications or programs?
8. Would you prefer to be using more digital applications?
32
APPENDIX C
SOFTWARE REQUIREMENT SPECIFICATION
1. Introduction
1.1. Purpose
This document describes the features, interfaces, and limitations of the
InvenDora system. It also describes how the system's users will interact with it.
This document serves as the system's skeleton and is useful for both developers
and future users.
1.2 Definitions, acronyms and abbreviations
Table 11
Acronyms and Definitions
Term Definition
InvenDora The name of the web-based meat
comes from the Povadora family
inventory management system for
Lolong and Lucy's Goat store
Inventory A complete list of items, products,
orders, sales etc.
Agile A software development methodology
by breaking the development of the
project into several phases, it involves
constant participation of the client.
PHP Hypertext Preprocessor
HTTPS Hypertext Transfer Protocol Secure
HTML HyperText Markup Language
URL Uniform Resource Locator
SSL Secure Socket Layer
33
TLS Transport Layer Security
CSS Cascading Style Sheets
2. Overall Description
2.1. User Needs
The InvenDora system as stated previously will not be accessible without
an internet connection. The users need to be connected to a WIFI or mobile data
to use the system and have access using a web browser such as Google
Chrome, Firefox, etc.
2.2 Assumptions and Dependencies
The InvenDora will be based on the systems that had stated in chapter 2
the related systems, some of the ideas of the said systems will be used on the
InvenDora system.
3. System Features and Requirements
3.1 Functional Requirements
Table 12
Functional Requirements
ID FUNC-001
Title Dashboard - Admin Features
Description When the admin has successfully
logged in to its account, the admin will
see the dashboard wherein the main
34
functionalities of the website such as
register new admin.
ID FUNC-002
Title Products Module
Description List of products available will be
viewed here, the admin can also
update the certain product, search the
certain product name and can also
add new product.
ID FUNC-003
Title New Order Module
Description This creates a new order, it needs the
customer’s information and the order
information of that customer with the
date ordered and the delivery date.
ID FUNC-004
Title Orders Module
Description The admin can view all the list of
pending orders with received, update
35
and a cancel button for the admin to
be clicked. The admin can also search
the last name of the customer to find it
easily.
ID FUNC-005
Title History Module
Description The admin can view the list of the
transaction history with the employee
name who has handled that certain
order.
3.2 System Features
● Search - able to search a certain order, name of the customer and the
product name.
● Admin Dashboard - the admin will be able to register new accounts for its
employees.
● Registration Sheet - Creation of structured documents. These are used to
collect the required information of an employee's identity.
3.3 Nonfunctional Requirements
● Internet connection is required
● Registered admin users have complete access to the system's features.
● InvenDora is a web-based application
● The system can only be accessed online
● Only registered users can login to the system
36
Wireframe of Invendora: A web-based meat inventory management system
for Lolong and Lucy's Goat store
Login Form
In this page this where the admin will input their credentials
1. User will input its username credentials
2. User will input its password credentials
3. Login button, the user will input their credentials and will be verified when
the button is clicked.
37
Home page
The home page is the landing page of the admin when logged in.
1. Register button, when clicked the admin can create a new admin account.
2. Home button, when clicked the user will be redirected to the home page.
3. Products button, when clicked the user will be redirected to the product
page.
4. New Order button, when clicked the user will be redirected to the New
Order page.
5. Orders button, when clicked the user will be redirected to the Orders page.
6. History button, when clicked the user will be redirected to the history page.
7. Logout button will let the user log out to their account and will be
redirected to the landing page which is the login page.
38
Register form
1. Register button, when clicked the inputted credentials will automatically
save to the database and create the account.
39
Products Page
This is where the admin adds a new product, search, update and delete.
1. The user can search specific product name in just inputting it in the search
box
2. Search button, when clicked the list of products being searched will
display.
3. New Product button, when clicked the user will redirect to the new product
modal.
4. Update button, let the user update the product.
5. Delete button, the product will be deleted from the list.
40
New Product Modal
1. User will input the product id of that new product created.
2. User will input the product name.
3. Users will be able to input the product description.
4. Users will input the price per kilogram.
5. Users will input the available stock.
6. Add Product button, when clicked the product will be added and the user
will be redirected to the Products page.
41
New Order Page
This is where the admin adds a new customer information together with their
order
1. User will input last name of the customer
2. User will input First name of the customer
3. User will input email address of the customer
4. User will input the contact number of the customer
5. User will input the address of the customer
42
6. User will choose product the customer will order in which the product is
already added
7. User will input the quantity
8. User will select the date the customer ordered
9. User will select the date the customer wants it to be delivered.
10. Add Order button, when clicked all the information above will be saved
and the user will be redirected back to New Order Page.
Orders Page
This is where the admin manages the order of each individual customer.
1. User inputs the customer’s last name to find the customer’s order
2. Search button, when clicked the customer’s order will be displayed.
3. Truck icon, when clicked the customer’s order will be marked as received
and will be added to the history.
4. Update button, when clicked the user can update the customers order or
the customers information.
5. Cancelled button, when clicked the order will be cancelled and the order
will be placed in the history page.
43
History Page
This is where the admin can see the history of the customers ordered.
1. Details button, when clicked the user will be able to view the information of
that order, the user will be redirected to the details page.
2. Retrieve button, when clicked the user will be able to retrieve that order
back to the orders page.
Details
This is where the admin can view the details of the order in the history page.
44
CURRICULUM VITAE
CONTACT INFORMATION
Full Name: Jason Kyle Avancena
Current Address: Centro Mandaue, Cebu
Phone Number: +63 9165847986
Email Address: jkra662200@[Link]
PERSONAL INFORMATION
Date of Birth: June 20, 1999
Age: 22
Citizenship: Filipino
Gender: Male
Marital Status: Single
EDUCATIONAL BACKGROUND
2006 - 2012 St. Joseph’s Academy - Mandaue
Elementary/Primary Education
2012 - 2016 St. Joseph’s Academy - Mandaue
High School/Secondary Education
2016 - 2018 St. Joseph’s Academy - Mandaue
Science, Technology, Engineering, and Mathematics (STEM)
Strand
Senior High School
2018 - Present University of San Carlos
Bachelor of Science in Information Technology
45
CONTACT INFORMATION
Full Name: Ma. Carmela L. Labandiro
Current Address: Canduman Mandaue City
Phone Number: +63 9150436906
Email Address: carmelalabandiro@[Link]
PERSONAL INFORMATION
Date of Birth: July 6, 1999
Age: 21
Citizenship: Filipino
Gender: Female
Marital Status: Single
EDUCATIONAL BACKGROUND
2006 - 2012 Canduman Elementary School
Elementary/Primary Education
2012 - 2016 St. Joseph’s Academy - Mandaue
High School/Secondary Education
2016 - 2018 St. Joseph’s Academy - Mandaue
Science, Technology, Engineering, and Mathematics (STEM)
Strand
Senior High School
2018 - Present University of San Carlos
Bachelor of Science in Information Technology
46
CONTACT INFORMATION
Full Name: Jon Francis S. Pasana
Current Address: Pajac, Lapu-lapu City
Phone Number: +63 9956171693
Email Address: francispasana@[Link]
PERSONAL INFORMATION
Date of Birth: April 2, 2001
Age: 20
Citizenship: Filipino
Gender: Male
Marital Status: Single
EDUCATIONAL BACKGROUND
2007 - 2013 Holy Infant School - Montessori, Lapu-lapu City
Elementary/Primary Education
2013 - 2017 Sacred Heart School - Ateneo de Cebu
High School/Secondary Education
2017 - 2019 Sacred Heart School - Ateneo de Cebu
Science, Technology, Engineering, and Mathematics (STEM)
Strand
Senior High School
2019 - Present University of San Carlos
Bachelor of Science in Computer Science
TECHNICAL SKILLS
● Microsoft Office
● Programming (C, Java, Lua)
47
● Web Development (HTML, CSS, MySql, JavaScript, PHP)
● Adobe Premiere, Adobe Photoshop
● Others (Clip Studio Paint, Paint Tool SAI)
WORK EXPERIENCE
Cebu City Risk Reduction and Management Council
N Escario St., Capitol Site, Cebu City, Cebu
On-The-Job Trainee
(January - February, 2019)
48
CONTACT INFORMATION
Full Name: Ashley Mae M. Turla
Current Address: Lamac, Consolacion
Phone Number: 09177127872
Email Address: ashleymturla@[Link]
PERSONAL INFORMATION
Date of Birth: April 3, 2001
Age: 20
Citizenship: Filipino
Gender: Female
Marital Status: Single
EDUCATIONAL BACKGROUND
2007 - 2013 Saint Louis College - Cebu
Elementary/Primary Education
2013 - 2017 Saint Louis College - Cebu
High School/Secondary Education
2017 - 2019 Saint Louis College - Cebu
Science, Technology, Engineering, and Mathematics (STEM)
Strand
Senior High School
2019 - Present University of San Carlos
Bachelor of Science in Computer Science
TECHNICAL SKILLS
● Has sufficient knowledge in Microsoft Office Applications
49
● Sufficient experience in Programming languages such as C, Java, HTML,
CSS, MySQL, PHP, Javascript.
● Has sufficient background experience in Visual Studio, GitHub, JIRA.
● Sufficient experience in Frameworks such as Laravel, ReactJS.
WORK EXPERIENCE
Mendero Medical Center
Cebu North Road, Consolacion, Cebu
On-The-Job Trainee
March 2019
50