លំហសិក្សាកម្ពុជា លំហសិក្សាកម្ពុជា V1.0
ចូល ចុះឈ្មោះ
អត្ថបទរបស់ Line William Default
0 អ្នកតាមដាន 1 កំពុងតាមដាន 2 អត្ថបទ
—
Architectural Design and Engineering Analysis of an Enterprise Point-of-Sale and Inventory Management System Utilizing Advanced Object-Oriented Patterns in Python, Flask, and MySQL
Small and Medium Enterprises (SMEs) frequently experience operational friction due to an over-reliance on manual record-keeping, non-centralized spreadsheets, and informal accounting practices1. These traditional tracking methods introduce stock quantity drift, pricing mismatches, untraceable refund actions, and an inability to analyze daily or monthly gross and net profitability1. This research paper presents a comprehensive structural and technical analysis of the SME Point-of-Sale (POS) and Inventory Management System—a multi-tier web application engineered to centralize inventory tracking, terminal transactions, role-based governance, and financial reporting1. Built upon Python 3.12/3.13, Flask 3.x, and MySQL 8.0, the application implements a layered architectural topology comprising Model, Repository, Service, and Controller/Route layers1. The system heavily leverages advanced Object-Oriented Programming (OOP) paradigms, including validated dataclasses with controlled properties, Strategy patterns for dynamic calculation of discounts and payment processing, Template Method patterns for multi-format report exports, Factory patterns for standardized entity instantiation, and Repository composition for isolated database operations1. System security is maintained through Bcrypt password hashing, time-bound email One-Time Passwords (OTP) stored via cryptographic SHA-256 digests, dynamic Role-Based Access Control (RBAC), parameterized SQL queries, and strict activity auditing1. Transactional safety during concurrent terminal sales is guaranteed through database-level pessimistic row locking (SELECT ... FOR UPDATE) alongside a tokenized short-term stock reservation engine1. The resulting codebase spans approximately 3,300 lines of application code, 14 relational database tables, over 40 HTTP endpoints, and a suite of automated unit tests1. This paper provides an exhaustive architectural decomposition, evaluates empirical test results, analyzes an identified design flaw in eager strategy instantiation, and outlines necessary engineering enhancements for enterprise production readiness1.
12 Oct 2026 0 79