SmartPOS: A Web-Based Point-of-Sale and Inventory Management System

Small retail shops such as mini-marts often record sales and stock manually or in disconnected spreadsheets, which makes it difficult to know current stock levels, track daily sales, or stop a cashier from selling an item that is already out of stock. SmartPOS is a web based Point-of-Sale and Inventory Management System built with Python, Flask, and MySQL that lets an Admin manage products and view sales reports, a Cashier process sales at checkout, and a Customer hold a simple account to view their own purchase history. The system applies Object-Oriented Programming through a layered architecture that separates domain models, business services, and database repositories. Core features include role-based authentication, product and stock management, a sales/checkout workflow that automatically updates inventory, product search, and a sales report page. Given a 5-week development window, the team will build the minimum required features first and treat extras such as discounts and customer accounts as optional stretch goals. The expected output is a working Flask application backed by a MySQL database, supported by test cases and a live demonstration of a full sale transaction.

FitTrack — Web-Based Gym Management, From Member Sign-Up to Self-Service

Many gyms still manage member information, memberships, attendance, and trainer scheduling using paper records or disconnected spreadsheets. This slows down daily operations, increases the chance of data-entry errors, and makes it difficult for staff to quickly check a member's status or history. This proposal presents the design of the Gym Management System (GMS), a web-based application built with Python, Flask, and MySQL that centralizes member registration, online membership purchase, attendance logging, trainer-session booking, and payment tracking within a single role-based platform. Visitors can browse membership plans and trainers freely; creating an account is only required to purchase a membership or request a trainer. The system supports four roles (Administrator, Staff, Trainer, and Member) each governed by a role-and-permission model that restricts every user to the features relevant to their responsibilities. Members log in to their own self-service dashboard to view their current membership plan and expiry date, their assigned trainer, their attendance history, and the total amount they have spent on membership and trainer sessions. The application is built on a three-layer object-oriented architecture (Domain Models, Service Layer, and Repository Layer) on top of a normalized MySQL database, keeping the codebase testable, maintainable, and easy to extend. This document sets out the problem the system addresses, its objectives and scope, its target users and stakeholders, its proposed features, its object-oriented and database design, and the timeline the team will follow to deliver it.

Gym Membership management System

Many small and medium-sized gyms still manage members using paper forms, spreadsheets, and manual payment records. These methods can take time, cause data entry mistakes, and make it difficult for staff to know whether a member is active or has expired. This project proposes a Gym Membership Management System to make these tasks easier and more organized. The system will be a web application developed using Python, Flask, and MySQL, with Object-Oriented Programming principles. It will provide separate access for Admin, Staff, Trainer, and Member users. Admin and Staff can manage members, membership plans, payments, and attendance. Trainers can view assigned members and training sessions, while Members can view their own membership, payment, and attendance information. The system will also provide search, filtering, expiry status, and simple reports such as daily revenue and membership status. The application will use a four-layer structure: Model, Repository, Service, and Route. Development will follow five two-week sprints, with testing performed during development. The expected result is a working prototype that reduces manual work, keeps records organized, improves membership checking, and provides a clear way to manage gym information in one system.

មេរៀនអនុវត្តទី ៦៖ Decorator-Based Secure User Management System

លំហាត់នេះបង្រៀននិស្សិតឱ្យអនុវត្ត Decorators និង Cross-Cutting Concerns តាមគម្រោងជាក់ស្ដែង ដោយចាប់ផ្ដើមពី Permission, Role, User និង Session ហើយបន្តទៅ Logging, Timing, Validation, Authentication, Authorization, Error Handling, Retry និង Caching Decorators។ បន្ទាប់មក Decorators ទាំងនេះត្រូវបានភ្ជាប់ជាមួយ UserService ដើម្បីបង្កើត RBAC-Based User Management System ដែល Admin, Manager និង Viewer មានសិទ្ធិខុសគ្នា។ តាមរយៈការអនុវត្តនេះ និស្សិតនឹងយល់ថា Decorator មិនមែនគ្រាន់តែជា Python Syntax @... ប៉ុណ្ណោះទេ ប៉ុន្តែជាវិធីរចនាកូដសម្រាប់បំបែក Behavior ដែលប្រើស្ទួនចេញពី Core Business Logic ឱ្យ Code មានភាពស្អាត អាចប្រើឡើងវិញបាន ងាយសាកល្បង និងងាយថែទាំ។

ADVANCED OOP — R&D PROJECT PROPOSAL INTERACTIVE QUIZ ENGINE

This research and development project proposal presents the design, architecture, and implementation strategy for the Interactive Quiz Engine, a web-based educational assessment platform built with Python, Flask, and MySQL. Educational institutions frequently suffer from feedback delays caused by manual test grading, non-reusable assessment materials, and fragmented student tracking across spreadsheets and paper records. The Interactive Quiz Engine directly addresses these inefficiencies by introducing a multi-format quiz creation tool, automated evaluation pipelines for objective question types, and centralized attempt history tracking. By leveraging core Object-Oriented Programming (OOP) principles—specifically polymorphism, encapsulation, and layered repository design—the engine cleanly separates core business logic (e.g., dynamic answer evaluation) from data persistence and interface routing. The software enables educators to author quizzes containing Multiple Choice (MCQ), True/False, and Short Answer questions within minutes, while providing students with instant score feedback upon submission. Expected project outcomes include a operational 5-layered Flask/MySQL web application, complete automated test suites, dynamic class performance reporting, and comprehensive architectural documentation suitable for academic defense.

Vehicle Inventory and Sales Management System for SMEs

Small and Medium Enterprises (SMEs) that sell vehicles need an effective way to manage vehicle inventory and sales records. Some businesses may use manual records, spreadsheets, or separate files to manage their daily operations. This can make it difficult to track available and sold vehicles, record stock movements, manage sales, and retrieve important information. This project proposes the development of a web-based Vehicle Inventory and Sales Management System for SMEs. The system will help users manage vehicle inventory, stock movements, customers, sales, and invoices in one centralized system. It will also include Role-Based Access Control (RBAC) to control user access based on their roles. The system will be developed using Python and Flask, with MySQL as the database. Object-Oriented Programming principles will be applied by organizing the system into domain models, services, repositories, and routes. The expected result is a functional and well-organized web-based system that helps SMEs manage vehicle inventory and sales operations more efficiently.

ដើមឈើនៅទន់ ត្រូវការបង្គោល; មនុស្សនៅមិនទាន់ចាស់ទុំ ត្រូវការអ្នកដឹកនាំ

ការប្រគល់ការងារធំ មិនគួរធ្វើដោយផ្អែកលើទំនុកចិត្តតែមួយមុខទេ តែត្រូវសាកល្បងសមត្ថភាព ចរិត ទំនួលខុសត្រូវ និងភាពចាស់ទុំជាដំណាក់កាល។ នៅពេលមនុស្សម្នាក់បង្ហាញថាអាចធ្វើការបានល្អជាបន្តបន្ទាប់ និងអាចឈរដោយខ្លួនឯងបាន ទើបសមនឹងទទួលតួនាទី និងសិទ្ធិសម្រេចចិត្តធំជាងមុន។

'Study Sprout' Gamified Learning Management System

This project presents a gamified Learning Management System (LMS) designed using the Flask Application Factory Pattern and standard Blueprint architecture to isolate system responsibilities across presentation, business logic and data access layers. The platform incorporates gamification features including experience points (XP), character leveling, daily login streaks, course boss combat systems and Pomodoro focus timers to boost student engagement. Security is established using standard Role-Based Access Control (RBAC) via route decorators, secure password hashing, Bcrypt/Argon2 and encrypted, flag-protected session cookies to track student performance. The database architecture links core user profiles, enrollments, course lessons, focus logs and metrics using a relational schema to track academic progress and platform interaction.

លំហាត់មេរៀនទី ៧៖ SOLID Principles and Refactoring

មេរៀនទី ៧ ផ្ដោតលើ SOLID Principles និង Refactoring ដើម្បីឱ្យនិស្សិតយល់ពីការរចនា Software ឱ្យមាន Responsibility ច្បាស់, Coupling ទាប, Cohesion ខ្ពស់ និងងាយពង្រីក។ និស្សិតសិក្សា SRP សម្រាប់បំបែក Responsibility, OCP សម្រាប់ពង្រីក Behavior ដោយមិនកែ Stable Core Logic, LSP សម្រាប់ធានាថា Subtype អាចជំនួស Base Type បានដោយសុវត្ថិភាព, ISP សម្រាប់បំបែក Interface ធំៗទៅជា Contracts តូចៗ និង DIP សម្រាប់ឱ្យ High-Level Logic ពឹងលើ Abstraction ជំនួស Concrete Implementation។ ក្នុងការអនុវត្ត និស្សិតធ្វើ Refactoring ពី Class ធំដែលមានតួនាទីច្រើន ទៅជា Components ដូចជា UserValidator, PasswordHasher, UserRepository, Notifier, Auditor និង UserService ហើយប្រើ Protocol, Dependency Injection និង Fake Dependencies សម្រាប់ Testing។ សរុបមក មេរៀននេះជួយឱ្យនិស្សិតអាចកំណត់ Code Smells, កែលម្អ Code Structure និងបង្កើតប្រព័ន្ធដែលងាយអាន ងាយសាកល្បង ងាយថែទាំ និងងាយពង្រីក។

Design and Development of Retail POS and Inventory Management System Using PyQt6 and SQLite3

Small retail businesses often face difficulties in managing products, inventory, sales transactions, and sales records efficiently when using manual or paper-based methods. These methods may result in inaccurate inventory records, calculation errors, and difficulties in tracking sales information. This project aims to design and develop a desktop-based Retail Point of Sale (POS) and Inventory Management System to improve the management of retail operations. The system is developed using PyQt6 for the graphical user interface and SQLite3 for local database management. The Research and Development (R&D) approach is applied to identify system requirements, design the system architecture and database, develop the user interface and core functions, and plan system testing. The proposed system includes product management, inventory management, sales transactions, search functionality, stock monitoring, tax and discount calculation, and sales reporting. The system is expected to provide a simple and efficient solution for managing retail products, inventory, and sales while reducing manual work and improving data accuracy.

មេរៀនទី១៖ សេចក្ដីផ្ដើមអំពីការស្រាវជ្រាវ ការអភិវឌ្ឍកម្មវិធី និង R&D

នៅក្នុងការសិក្សាកម្រិតឧត្តមសិក្សា និស្សិតមិនគួររៀនត្រឹមតែទ្រឹស្តី ឬចេះប្រើបច្ចេកវិទ្យាដែលមានស្រាប់ប៉ុណ្ណោះទេ។ និស្សិតគួរត្រូវបានបណ្តុះបណ្តាលឱ្យមានសមត្ថភាព សង្កេតបញ្ហា កំណត់សំណួរ ស្វែងរកភស្តុតាង បង្កើតដំណោះស្រាយ និងវាយតម្លៃលទ្ធផល។ ដំណើរការនេះអាចកើតឡើងតាមរយៈការស្រាវជ្រាវ (Research) ការអភិវឌ្ឍកម្មវិធី (Software Development) ឬការរួមបញ្ចូលទាំងពីរជា Research and Development (R&D)។ មេរៀនទី ១ នេះ ណែនាំនិស្សិតឱ្យយល់ច្បាស់ពីភាពខុសគ្នា និងទំនាក់ទំនងរវាងវិធីសាស្ត្រទាំងបី ព្រមទាំងជួយឱ្យនិស្សិតចាប់ផ្តើមគិតអំពីបញ្ហាជាក់ស្តែងដែលអាចយកមកធ្វើជា Research Project, Software Project ឬ Integrated R&D Project។ ក្នុងវគ្គសិក្សានេះ និស្សិតនឹងបន្តពីការកំណត់ប្រធានបទ រហូតដល់ Research/R&D Proposal, Proposal Defense, Implementation, Evaluation, Final Report និង Final Defense។

លំហាត់មេរៀនទី៥៖ Factory Method and Abstract Factory

លំហាត់មេរៀនទី ៥ ផ្ដោតលើ Factory Method និង Abstract Factory ដើម្បីឱ្យនិស្សិតយល់ពីការបំបែក Object Creation ចេញពី Client Code និង Business Logic។ និស្សិតរៀនពី Direct Object Creation Problem, Simple Factory, @classmethod ជា Alternative Constructor, Registry-Based Factory, Factory Method និង Abstract Factory សម្រាប់បង្កើត Concrete Objects ឬ Product Families តាម Runtime Requirement និង Configuration។ ក្នុងការអនុវត្ត និស្សិតបង្កើត NotifierFactory, UserFactory, Report Creators និង Light/Dark UI Factories ហើយភ្ជាប់ Factory ជាមួយ Protocol, Open/Closed Principle និង Dependency Injection ដើម្បីកាត់បន្ថយ Coupling និងធ្វើឱ្យប្រព័ន្ធងាយសាកល្បង និងងាយពង្រីក។ សរុបមក មេរៀននេះជួយឱ្យនិស្សិតយល់ថា Factory Pattern មានប្រយោជន៍នៅពេល Object Creation មាន Concrete Implementations ច្រើន ឬត្រូវជ្រើសរើសតាម Runtime ដោយរក្សា Architecture ឱ្យមានភាពបត់បែន និងមានរចនាសម្ព័ន្ធច្បាស់។