Bestlink College of the Philippines
| Name | Role |
|---|---|
| Jessa Lingahan | Project Manager |
| Andrei Heather Quintos | System Analyst |
| Chester Baltazar | Programmer |
| Axl Ron Bunao | Document Specialist |
| Jomari Corre | Business Specialist |
- Chapter 1 – Project Background
- Chapter 2 – Review of Related Studies and Projects/Systems
- Chapter 3 – Project/System Development
The objective of this project is to create a Point of Sale (POS) System for Angelo's Burger, owned by Nelia Flores Polledo, located at Bagong Buhay II, Sampol Market, in front of 7 Eleven, CSJDM, Bulacan. The POS system will be web-based. It will automate order processing, record sales, and track inventory in real-time.
There will be two types of users for the POS System: the administrator and the staff member. The purpose of the POS System is to improve efficiency, accuracy, and service quality. By moving away from manual order processing, Angelo's Burger can boost customer satisfaction by providing faster service.
Angelo's Burger is a small local food business that offers burgers and snacks to its customers. The business is growing, but many of its daily operations are still done manually — order taking is written on paper, sales are recorded in notebooks, and inventory is checked by counting items one by one. These manual processes lead to slow transactions, errors in computation, misplaced records, and difficulty monitoring stocks, especially during busy hours.
To support the business operations, this project proposes developing a Point of Sale (POS) System specifically designed for Angelo's Burger. This system will automate order-taking, compute sales, and track inventory. It will also help staff manage data more easily and provide clearer reports for decision-making.
| Problem | Solution |
|---|---|
| Lack of Sales Performance Visibility | Sales Performance Dashboard |
| Limited Stock Visibility Causing Stockouts | Stock Monitoring with Low Stock Alerts |
| Lack of Monthly Performance Evaluation and Comparison | Sales Report Generation with Month-to-Month Comparison |
| Limited Payment Options | Digital Wallet Payment Method |
| Unrecorded or Missing Transaction Records | Digital Order Logging |
| Problem | Description |
|---|---|
| Lack of Sales Performance Visibility | The absence of a centralized sales dashboard displaying key sales metrics prevents management from efficiently assessing sales operation performance. |
| Limited Stock Visibility Causing Stockouts | The lack of visibility into stock levels makes it difficult to track available stock. Items may run out without notice, leading to stockouts and lost sales opportunities. |
| Lack of Monthly Performance Evaluation and Comparison | Management evaluates monthly operations manually, which is time-consuming and prone to errors, restricting visibility and accuracy of performance evaluation. |
| Limited Payment Options | The business relies only on cash payments, causing inconvenience when customers have no cash and leading to lost sales opportunities. |
| Unrecorded or Missing Transaction Records | Transactions are occasionally missed or forgotten by staff, making it difficult for the admin to maintain transparency in business operations. |
Helps the client process transactions faster, track sales and inventory accurately, and manage records efficiently.
- Improved Efficiency – Faster order processing and smoother workflow.
- Reduced Errors – Minimizes mistakes in orders, inventory, and sales records.
- Better Decision Making – Provides accurate reports on sales, inventory, and customer demand.
- Enhanced Customer Service – Quicker service and more organized transactions.
Enhances students' skills in system development, analysis, and real-world problem solving.
- Hands-On Experience – Allows students to apply what they learned in systems analysis, programming, and documentation.
- Skill Development – Improves teamwork, problem-solving, coding, and communication skills.
- Portfolio Material – Provides a real project they can use for future academic or professional requirements.
Serves as a reference project that reflects the school's commitment to quality and technology-based research.
- Quality Research Output – Adds to the institution's collection of meaningful and practical research projects.
- Supports Curriculum Goals – Shows how theories taught in class are applied in real-life problems.
- Reference for Future Researchers – Can be used as a guide or basis for future system development studies.
Provides a useful reference for improving or developing similar POS systems in future studies.
- Additional Knowledge Source – Provides insights, data, and documentation that can improve related studies.
- Foundation for Enhancements – They can update, improve, or expand the system based on this work.
| Feature | Description |
|---|---|
| Sales Performance Dashboard | Displays updated sales information, allowing the business to easily view total sales, profit, number of today's orders, and total customers. The dashboard automatically updates once a transaction is completed. |
| Stock Monitoring with Low Stock Alerts | Allows the business to monitor the quantity of each item as sales are made. When an item reaches a set threshold, the system automatically triggers a low stock alert. |
| Sales Report with Month-to-Month Comparison | Provides a monthly summary of sales, showing total sales, profit, and other metrics. Includes a comparison with previous months, allowing the business to track changes and identify trends. |
| Digital Wallet Payment Method | Allows customers to choose from different payment methods, including e-wallets, making transactions easier and more convenient. |
| Digital Order Logging | Automatically records all sales and transactions once an order is completed, ensuring no data is missed or forgotten. |
The scope of this project covers the development of a Point of Sale (POS) system used in one business location. The system is intended for in-store use and supports the recording and management of sales transactions during daily business operations.
Handles all user-related operations in the POS system.
- Role Management – Define roles like Admin and Staff, assign permissions, and limit access to specific features for Staff.
- Account Administration – Create and delete user accounts.
- Authentication – Secure login for users using username and password.
Handles all sales and transaction-related operations in the system.
- Order Management – Manages the creation, updating, and completion of customer orders.
- List of Menus – Displays menu items with their name and price, which can be selected for order creation.
- Payment Handling – Processes payments via cash or digital wallet.
- Receipt Generation – Produces digital receipts that are ready to print for completed transactions.
- Order Logging – Records all order activities for auditing and tracking purposes.
- Total Price & Change Calculation – Calculates the total price of orders and the change based on the payment received.
Ensures accurate tracking and control of stock levels.
- Stock In – Handles the restocking of existing products and ingredients.
- Stock Out – Displays items that are out of stock, helping identify products that need restocking.
- Stock Update – Allows updating of stock quantity, preventing changes to other product details.
- Stock Archive – Stores removed or inactive products instead of deleting them, preventing loss of important data.
- Stock Overview and Monitoring – Provides visibility and alerts for inventory status.
- Low Stock Alert – Notifies when stock reaches a minimum level to avoid stockouts.
Tracks and analyzes sales performance to help the business make informed decisions.
- Monthly Sales Summary – Shows total sales for each month and includes total profit, total items sold, total orders, and average items per order.
- Sales Performance Comparison – Compares sales performance with previous months.
- Export & Print Reports – Allows reports to be exported (Excel, PDF) or printed for review.
Provides an overview of key business metrics.
- Total Sales – Shows the total money received today.
- Profit – Shows the profit earned today.
- Today's Orders – Shows the number of orders completed today.
- Total Customers – Shows the number of customers today.
The objectives of the proposed POS system are focused on improving the accuracy, efficiency, and security of business operations:
- Provide up-to-date sales information that enables the business to monitor performance continuously.
- Ensure stock availability by maintaining sufficient inventory levels to meet customer demand.
- Review monthly business activity by generating reports that summarize sales, total revenue, and key metrics.
- Offer customers payment options, such as e-wallets, for convenience and flexibility.
- Maintain a complete record of all sales transactions to prevent data loss.
| Deliverable | Description |
|---|---|
| Log In | Allows users to securely access the POS system. |
| Log Out | Allows users to securely exit the POS system. |
| Add Product | Add new products and stock them into the inventory. |
| Edit Product | Modify existing product details. |
| Archive | Allows admins to remove products from the active inventory without permanently deleting them. |
| Price | Shows product price in customer orders. |
| Complete Order | Finalize a customer order. |
| Reset Order No | Refresh order numbers if the system malfunctions. |
| Account Creation | Create new staff accounts, including admin accounts, and manage their access. |
| Category | Organize products into categories for easy management. |
| Stock Request | Request additional stock from the admin. |
| Total Orders | Shows the total number of orders processed. |
| Total Sales | Displays the total sales amount. |
| Average Order Value | Calculates the average value of each order. |
| Average Items per Order | Shows the average number of items per order. |
| Total Customers | Displays the total number of customers served. |
| Out of Stock | Indicates products that are completely out of stock. |
| Low Stock | Alerts for products that are running low. |
| Revenue | Shows the total income generated from sales. |
| Profit | Displays the net profit after costs. |
| Order Log | Keeps a complete record of all processed orders. |
| Printable Receipt | Generates a receipt that can be printed for customers. |
| Sales Report | A monthly summary of sales data used to track revenue, profit, and overall business performance. |
The following are explicitly excluded from this project:
- Inventory Purchasing & Supplier Management – The POS tracks stock but does not handle buying from suppliers or managing purchase orders.
- Employee Payroll & Scheduling – Calculating salaries or managing staff shifts is not part of the system.
- Customer Refunds & Returns – Giving refunds, processing returns, or adjusting payments is not included.
- Accounting & Bookkeeping – The POS can track sales and calculate basic profit, but it does not create full financial reports, manage ledgers, or handle taxes.
- Advanced Order Customization – Complex or special orders beyond basic options are not included.
- Loyalty & Rewards Programs – Customer points, membership rewards, or promotional discounts are not tracked.
The SDLC is a structured process through which software is planned, designed, developed, tested, and maintained. It provides a framework that divides the development of software applications into distinct phases, ensuring that each stage is systematically executed.
The team used Agile methodology throughout the project's completion, enabling sprint-based iterative work where members focus on the most important tasks, implement them, test, and review gradually.
Planning Phase
The team came up with the idea to create a POS system for a small food business to replace manual record-keeping. Interviews were held with the business owner and cashier to understand their problems and expectations. A comprehensive project timeline was outlined, dividing development into short sprints and iterations.
Analysis Phase
The team deeply analyzed information gathered from interviews with the business owner and cashier. They examined transaction processes, order handling, and record-keeping practices to identify inefficiencies. System requirements were analyzed to determine key functional needs: order processing, inventory tracking, and sales reporting.
Design Phase
The system is designed to be clean, simple, and easy to navigate, ensuring efficient order-taking and accurate sales tracking. Access via smartphones and portable devices is recommended exclusively for the admin, while cashiers are advised to use larger screens. Users can log in through two options: one for staff and one for the admin.
Admin
Staff
Development Phase
The POS system was built using an iterative approach that prioritized essential functionality before advancing to more complex features. Core features (selecting menu items, recording orders, calculating totals) were developed first. Inventory management and sales reporting were added in subsequent iterations.
Technology Stack:
- HTML & CSS – User interface structure and styling
- JavaScript – Core functionality and interactive components
- EJS (Embedded JavaScript) – Dynamic page generation based on user roles
- MongoDB – NoSQL database for flexible data storage
- Node.js + Express – Server-side execution and backend framework
- Git – Version control for collaboration and code tracking
Testing Phase
The POS system was thoroughly tested to ensure all features functioned correctly. Core functionalities (menu selection, order recording, total calculation), inventory management, and sales report generation were all verified. Both cashier and admin roles were tested to verify login credentials, access restrictions, and user permissions.
Implementation
The system will be installed on the business's trusted devices, including computers, tablets, and smartphones. Secure login protocols will be implemented to prevent unauthorized access. Staff will attend training seminars, a reliable database will store all transaction data, and regular backups and security measures will be put in place.
Maintenance
The system will be continuously monitored for performance issues and security threats. Hardware components will undergo continuous testing, data will be backed up regularly, and the system will be periodically checked and adjusted for optimal performance.
| ID | Task Name | Role | Start Date | End Date | Status |
|---|---|---|---|---|---|
| 1 | Look for client | All members | 12/10/2025 | 12/12/2025 | DONE |
| 2 | Drafting Questions | Business Specialist | 12/12/2025 | 12/15/2025 | DONE |
| 3 | Interview | Project Manager / Business Specialist | 12/20/2025 | 12/20/2025 | DONE |
| 4 | System Design | System Analyst / Programmer | 12/21/2025 | 1/4/2026 | DONE |
| 5 | 1.1 Project Background | Project Manager / Business Specialist | 12/9/25 | 12/8/25 | DONE |
| 6 | 1.1.1 Problem Opportunity | Business Specialist | 12/9/25 | 12/13/25 | DONE |
| 7 | 1.1.2 Benefits | System Analyst / Business Specialist | 12/9/25 | 12/13/25 | DONE |
| 8 | 1.1.3 Goals | Project Manager / Business Specialist | 12-14-25 | 12-16-25 | DONE |
| 9 | 1.2.1 Objectives | Project Manager / Business Specialist | 12-14-25 | 12-16-25 | DONE |
| 10 | 1.2.2 Deliverables | All members | 12-17-25 | 12-17-25 | DONE |
| 11 | 1.2.3 Out of Scope | Programmer / System Analyst | 12-18-25 | 12-20-25 | DONE |
| 12 | 1.3 Project Plan | All members | 12-18-25 | 12-20-25 | DONE |
| 13 | 1.3.2 Project Timeline | Project Manager | 12-4-25 | 1-7-26 | DONE |
| 14 | 1.3.3 Issues and Policy Implications | Business Specialist | 12-21-25 | 12-20-25 | DONE |
| 15 | 1.3.5 Service Transition | System Analyst / Project Manager | 12-26-25 | 12-27-25 | DONE |
| 16 | 1.4 Technical Features | Project Manager / System Analyst | 12-26-25 | 12-27-25 | DONE |
| 17 | 1.5 Project Organization and Staffing | All members | 12-26-25 | 12-27-25 | DONE |
| 18 | 1.6 Project Budget | All members | 12-30-25 | 12-30-25 | DONE |
| 19 | Checking Chapter 1 | All members | 01/15/26 | 01/15/26 | DONE |
| 20 | 2.1 Local | Business Specialist | 1-13-26 | 1-16-26 | DONE |
| 21 | 2.2 Foreign | Document Specialist | 1-13-26 | 1-16-26 | DONE |
| 22 | 2.3 SYRTTS (Comparative Analysis) | System Analyst | 1-13-26 | 1-18-26 | DONE |
| 23 | 3.1 Design Layout | Programmer / System Analyst | 1-19-26 | 1-22-26 | DONE |
These tasks were recorded as double entries to show both the initial checking phase and the completion after revisions.
Project Background (1.1) – Project Manager / Business Specialist
Checked on January 15 — needed revision due to missing context and unclear introduction. Revised and completed on January 19.
Problem Opportunity / Description (1.1.1) – Business Specialist
Checked on January 15 — needed revision because the problem statement was vague. Revised and completed on January 19.
Goals (1.1.3) – Project Manager / Business Specialist
Checked on January 15 — needed revision to make goals more specific and measurable. Revised and completed on January 19.
Objectives (1.2.1) – Project Manager / Business Specialist
Checked on January 15 — needed revision because objectives were not aligned with goals. Revised and completed on January 19.
Deliverables (1.2.2) – All Members
Checked on January 15 — needed revision to clearly define expected outputs. Revised and completed on January 19.
Out of Scope (1.2.3) – Programmer / System Analyst
Revised and finalized on February 1. Clarified what is excluded to avoid scope creep.
Technical Features (1.4) – Project Manager / System Analyst
Revised and checked on January 15 (minor clarifications added). Finalized on January 15.
| Risk | Impact | Description | Solution |
|---|---|---|---|
| Data Entry Errors | Medium | Incorrect input of inventory, prices, or menu items leading to inaccurate sales and inventory reports. | Implement validation checks, use standardized forms or dropdowns, conduct regular audits, and train staff on proper data entry. |
| Staff Resistance to Change | Low | Staff may be slow to adopt the new POS system, affecting productivity. | Involve staff early in system design and provide proper training. |
| System Downtime or Technical Issues | High | Hardware or software failures that stop the POS from operating, delaying transactions. | Perform regular maintenance, maintain backup servers, have an IT support plan, and monitor system health. |
| Manual Payment Confirmation | High | Staff manually confirms QR payments, which can lead to mistakes, delays, or confirming unpaid transactions. | Use a validation process where staff checks the transaction timestamp and reference number on the customer's payment app before confirming. |
| Internet Downtime | Medium | Temporary loss of internet connection may interrupt real-time transaction processing. | Prepare a backup mobile hotspot that can be connected by staff when the main Wi-Fi connection is unavailable. |
| Data Loss/Corruption | High | Loss or corruption of transaction, inventory, or customer data due to system crashes or accidental deletion. | Implement regular backups, use cloud storage, and have a recovery plan in place. |
To ensure a smooth transition from manual methods to the POS system, a hands-on training seminar is delivered to teach administrators and staff how to effectively operate the system. The session is designed to walk users through real workflows step by step.
Training Seminars
A structured, role-based training session that explains how to use the POS system during daily operations. For staff, the seminar covers logging in, processing sales, correcting incorrect entries, and completing routine transactions. For administrators, it explains how to manage products, update prices, monitor transactions, and generate reports.
Live Demo with Open Q&A
The live demo reinforces the seminar by showing the system in action using real-world scenarios. The facilitator demonstrates common tasks and intentionally creates mistakes to show how errors can be identified and resolved. Participants are encouraged to interrupt the demonstration at any point to ask questions or raise situations they might encounter on the job.
| Specification | Min | Max | Description |
|---|---|---|---|
| Processor | Intel Core i5-7th CPU @ 1.7GHz | Intel Core i5-12th, 2.7GHz | Faster processing performance |
| RAM | 8 GB | 16 GB | Supports multitasking |
| Device | Dell | Vivobook | Reliable laptop device |
| Software | Type | Description |
|---|---|---|
| Microsoft Windows 10 Education | Operating System | Runs the system |
| MongoDB Compass | Database | Stores system data |
| JavaScript | Backend | Handles system logic |
| EJS (Embedded JavaScript) | Frontend | Displays user interface |
| Git | Version Control | Manages code versions |
| Visual Studio Code 1.107.1 | IDE | Used for coding |
| Node.js | JavaScript Runtime Environment | Used for server-side execution |
| Express | Backend Framework | Used to build server-side applications |
| Technology | Purpose |
|---|---|
| HTML | Creates the structure of webpages (headings, text, images, buttons). |
| CSS | Designs and styles the webpage including colors, layout, and fonts. |
| JavaScript | Makes websites interactive and dynamic. |
| Node.js | Runtime environment allowing JavaScript to run on the server. |
| Express.js | Web framework for Node.js that simplifies building web servers and APIs. |
| MongoDB | NoSQL database storing data in JSON-like documents; flexible and scalable. |
| EJS | Templating engine for Node.js that creates dynamic HTML pages using embedded JavaScript. |
| Visual Studio Code | Lightweight, powerful code editor supporting many programming languages. |
| Git Bash | Command-line tool for Windows that lets developers use Git and Unix-style commands. |
| Role | Name & Contact | Responsibilities |
|---|---|---|
| Project Manager | Jessa Lingahan — lingahanjessa17@gmail.com | Plans and monitors the project timeline, coordinates team activities, manages risks, and ensures deliverables are completed on time. |
| Programmer | Chester Baltazar — chesterbolt15@gmail.com | Develops system features, writes and maintains code, and fixes bugs to ensure proper system functionality. |
| System Analyst | Andrei Quintos — andreiheatherquintos@gmail.com | Analyzes system requirements, designs workflows, and ensures the system meets business and technical needs. |
| Business Specialist | Jomari Corre — jomaricorre14@gmail.com | Provides business requirements, validates system functions, and ensures the system aligns with operational goals. |
| Document Specialist | Axl Ron Bunao — axlronbunao@gmail.com | Prepares, organizes, and maintains system documentation, reports, and technical records. |
| Budget Item | Description | Cost |
|---|---|---|
| Laptop (personal) | Used for system development and documentation | ₱30,000.00 |
| Transportation Expenses | Travel costs for meetings, data gathering, and project-related activities | ₱357.00 |
| Data Load | Mobile internet data for online research, communication, development, and testing | ₱250.00 |
| Phone | Mobile phone used for communication and testing during development | ₱15,000.00 |
| Wi-Fi Subscription | Internet connectivity | ₱2,997.00 |
| Foods and Drinks | Expenses for food and beverages provided during system development | ₱1,500.00 |
| Total Cost | ₱49,187.00 |
A fast and easy-to-use point-of-sale system that streamlines sales, inventory, and transactions for businesses.
Shops using KaHero POS:
- Malayan Rice Depot Corp. – a rice depot business
- GenTea Milk Tea – a milk tea and burger shop located in General Trias, Cavite
Developers:
- Christian Clapton Edison Orioste – CTO / Technical Lead
- Manuel Banderada – Junior Software Developer
- Elvie Mae Bucana – QA / Support
- Johnryl Candelon – Web Developer
Link: https://www.kahero.co/
A simple, locally made point-of-sale system for managing sales and inventory, designed to help small businesses track transactions and stock.
Shops using Kwenta POS:
- Burger Stands and Stalls – easy to set up on a single Android tablet
- Coffee and Milk Tea Stalls – used for rapid order input and remote sales monitoring
Developers:
- Ronald Dale Fuentebella – Founder and Lead Full-Stack Developer
- Mufat'z-Anni J. Mohammad (Mufa Mohammad) – Co-founder and Business/Operations Specialist
Link: https://www.kwentapos.com/landing
A cloud-based point-of-sale system for Filipino SMEs, offering sales tracking, inventory management, and staff monitoring. Affordable, easy to use, and ideal for retail shops, cafés, and restaurants.
Shops using UTAK POS:
- Castro Pharmacy – a local pharmacy using UTAK POS for business operations
- Barkhaus (Eastwood) – a pet store/café using UTAK POS
Developers:
- Leif Collin Ang – Full-Stack Developer at UTAK
- Rafael Topasi – Software Engineer at UTAK
Link: https://utak.io/
A cloud-based POS system for restaurants and retail, offering sales, inventory, employee management, and reporting on tablets, kiosks, and desktops, with features like online ordering and customer loyalty.
Shops using KwickPOS:
- Peter Chang – Restaurant owner praising real-time online reporting and multi-location management
- Mr. PJ Wings – Restaurant owner who noted improved order processing and back office organization
- Crafty Crab – A restaurant cited for managing menus and customer records effectively
Developers:
- Tom Jin – Co-founder of KwickPOS, Silicon Valley technologist
- Ming Ye – Co-founder with deep experience in computer science and restaurant software
Link: https://www.kwickpos.com/quick-service/
A cloud-based restaurant management system built for fast and full-service restaurants. Allows restaurants to take orders, process payments, manage inventory, track sales, and run customer loyalty programs.
Shops using Toast POS:
- Shake Shack – popular burger and fast-casual chain
- Black Tap – known for gourmet burgers and shakes
- Bluestone Lane – café & restaurant brand
Developers:
- Steve Fredette – Co-Founder; President with product & engineering background
- Aman Narang – Co-Founder; CEO (effective 2024)
- Jonathan "Jon" Grimm – Co-Founder; Chief Technology Officer (CTO)
Link: https://pos.toasttab.com/
A cloud-based restaurant POS that manages orders, payments, inventory, tables, and reporting for food and beverage businesses.
Shops using Foodics:
- 7Ribs – a restaurant using Foodics for sales and operations
- Koobs Cafe – café that adopted Foodics for order taking and inventory
- Mazaj Maghrebi – restaurant using Foodics POS
Developers:
- Ahmad Al-Zaini – Co-Founder & Chief Executive Officer (CEO)
- Mosab Alothmani – Co-Founder & Chief Technology Officer (CTO)
Link: https://www.foodics.com/
| Feature | KaHero | Kwenta | UTAK | KwickPOS | Toast | Foodics | This Project |
|---|---|---|---|---|---|---|---|
| Dashboard | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Inventory | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Reports | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| POS | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Print Receipt | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Payment Method | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Low Stock Alert | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Order Log | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Archive | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Account Creation | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
This chapter covers the design and layout of the POS system, including:
-
BPA (Business Process Analysis) – Mapping of existing and proposed workflows
-
ERD Model – Entity Relationship Diagram showing data structure and relationships
-
Use Case Diagram – Illustrating system interactions between users (Admin & Staff) and the system
-
Flowchart – Step-by-step process flows for key system operations
-
System Architecture – Overall technical structure of the system
The system provides separate interfaces for Admin and Staff users, with role-specific access to features:
Admin
Staff
This section presents the system requirements necessary for the effective implementation and operation of the proposed POS system. These requirements focus on compliance with applicable laws and policies, as well as the implementation of security measures to protect transactions, inventory, data, and user information.
| Specification | Min | Max | Description |
|---|---|---|---|
| Processor | Intel Core i5-7th CPU @ 1.7GHz | Intel Core i5-12th, 2.7GHz | Faster processing performance |
| RAM | 8 GB | 16 GB | Supports multitasking |
| Device | Dell | Vivobook | Reliable laptop device |
| Software | Type | Description |
|---|---|---|
| Microsoft Windows 10 Education | Operating System | Runs the system |
| MongoDB Compass | Database | Stores system data |
| JavaScript | Backend | Handles system logic |
| EJS (Embedded JavaScript) | Frontend | Displays user interface |
| Git | Version Control | Manages code versions |
| Visual Studio Code 1.107.1 | IDE | Used for coding |
| Node.js | JavaScript Runtime Environment | Used for server-side execution |
| Express | Backend Framework | Used to build server-side applications |
-
Civil Code of the Philippines – Republic Act No. 386
Covers breach of contract. If a party fails to follow a contract or agreement (e.g., the client refuses to pay after the system is delivered), it may be considered breach of contract, and civil cases for damages may be filed. -
Intellectual Property Code of the Philippines – Republic Act No. 8293
The source code, design, and program are protected as intellectual property. Copying, distributing, modifying, or selling the system without permission may be considered copyright infringement. -
Cybercrime Prevention Act of 2012 – Republic Act No. 10175
If someone illegally accesses, alters, or damages the system, it may fall under cybercrime offenses such as: illegal access, data interference, system interference, and computer-related fraud. -
Electronic Commerce Act of 2000 – Republic Act No. 8792
Governs electronic transactions and digital systems. If someone manipulates electronic records or transactions in the system, they may face legal consequences. -
Software Piracy Laws – Republic Act No. 8293
Copying and sharing software without authorization is considered theft. -
Plagiarism – Republic Act No. 8293
Copying or stealing the ideas or work of others without proper credit. -
Piracy – Republic Act No. 8293 / Presidential Decree No. 532
Illegal copying, distribution, or use of someone's work.
-
Access Control – Regulates who can view or use resources within a system, ensuring users are granted appropriate permissions based on their roles, preventing unauthorized access.
-
JWT Token (JSON Web Token) – A compact and secure digital token used to transmit information between a client and server for authentication. It contains encoded user data and a signature verifying authenticity, allowing systems to confirm identity without repeated logins.
-
Hashed Password – A password transformed into an unreadable string using a hashing algorithm before being stored in a database, protecting user credentials even if the system is compromised.
-
Account Expiration – A set date or time when a user's account becomes inactive, requiring renewal or reactivation to regain access.
-
Token Expiration – A time limit after which an authentication token (like a JWT) is no longer valid, requiring a new token for continued access.
This outlines the requirements to ensure a smooth shift from manual methods to the POS system by preparing administrators and staff through hands-on training before full deployment.
Training Seminars:
Teach staff and administrators how to operate the POS system in daily operations. Staff learn sales processing and error correction, while administrators learn product management, transaction monitoring, and report generation. Tasks are demonstrated in real time for practical understanding.
Live Demo with Q&A:
Reinforce training with real-world demonstrations and error handling. Participants can ask questions and explore scenarios to gain confidence in using the system independently.
| Report Name | Input | Expected Output | Notes |
|---|---|---|---|
| Low Stock Alert | Product reaches minimum stock level | System shows low stock indicator | Indicator only (no restriction) |
| Out of Stock | Product quantity becomes zero | System shows out-of-stock indicator | Can still process orders |
| Delete Product | User deletes a product | Product is removed from the system | May not be practical because it can cause data loss and affect record tracking |
| Login Attempt | User enters login credentials | System allows or denies access | No login attempt tracking |
| Account Creation | Staff creates a new account | New account is successfully created | Staff is allowed to create accounts |
| Same Browser Access | User opens system in the same browser | System remains accessible | Can be accessed within the same browser session |
| # | Procedure | Input | Expected Outcome |
|---|---|---|---|
| 1 | Login (Valid) | Correct username and password | User is logged in and redirected to dashboard |
| 2 | Login (Invalid) | Incorrect username or password | System displays error message |
| 3 | Add New Product | Product name, price, and quantity | Product is added to inventory |
| 4 | Edit Product | Updated product details | Product information is updated |
| 5 | Archive Product | Select product and archive | Product is removed from active list and stored in archive |
| 6 | Restore Product | Select archived product and restore | Product returns to active inventory |
| 7 | Process Order | Selected items and confirmed order | Order is recorded and total is correct |
| 8 | Inventory Update | Completed transaction | Stock is reduced automatically |
| 9 | Generate Report | Selected date range | Sales report is displayed correctly |
| 10 | Logout | Click logout | User is logged out and returned to login page |
Bestlink College of the Philippines — BSIS Research Thesis Project