How arshc0der/inventory-management-system works
Main Components
• User Interface Layer: This is built with Qt and consists of the various UI forms (.ui files) for functionalities like dashboard, registration, product management (add, update, delete), employee management, notifications, and more.
• Business Logic / Application Layer: Represented by the C++ source files (e.g., add_supplier.cpp, addorders.cpp, register.cpp, etc.) that implement the functionality for each module.
• Database Layer: The presence of database files and headers (i_m_s.db, DatabaseManager.h, DatabaseSchema.h) indicates that the system interacts with a local database. This layer manages data persistence and query execution.
• Security and Global Utilities: Global functions (globalfunctions.cpp/h) and SHA-256 based authentication (as noted in the README, though not explicitly in the file names) are key to ensuring data integrity and secure access.
Relationships and Interactions
• The UI layer interacts directly with the business logic layer. Each UI form (defined in a .ui file) is connected to a corresponding C++ file that handles events and data flows.
• Business logic modules call upon the database layer through the database manager and schema definitions for reading or updating data.
• Authentication and security modules (coded within global functions or settings classes) ensure that user credentials (using SHA-256) are validated before granting access.
• Notifications and activity tracking likely operate as a cross-cutting concern, with modules broadcasting events to update the dashboard and user interface.
Architectural Patterns and Design Principles
• The project follows a structure that is typical for desktop applications with clear separation between UI and core logic. It uses the Model-View approach inherent in Qt development (UI forms as the View, and the C++ classes as the Controller/Model).
• Even though it is a desktop application, the design leans towards the layered architecture pattern—UI / Application Logic / Data Persistence—so be sure to illustrate these layers.
Technologies and Frameworks
• Qt C++: Emphasize that all UI components are built with Qt.
• SHA-256: Note the advanced security feature used for credential verification.
• Local Database: The i_m_s.db file implies usage of a SQLite or similar embedded database engine.