How smphuc/project_manament works
Main Components
• Frontend Client: Represented by HTML, CSS, and JavaScript files (for example, files like 1.html, 1.css, 1.js, and many CSS resources in public/ and other css files). This is the interface where users (lecturers, students, administrators) interact.
• Application Layer (Backend – CodeIgniter MVC):
– Controllers: Folder “application/controllers” (e.g., LecturerManagement_Controller, StudentManagement_Controller, Login_controller, etc.). These handle incoming requests and coordinate responses.
– Models: Folder “application/models” (e.g., LecturerModel, StudentModel, etc.). They encapsulate data operations and business logic.
– Views: Folder “application/views” (numerous view files for different pages like login_view, manage_students_view, etc.) which present the UI.
• Core Framework: The “system” directory contains the CodeIgniter core libraries, which handle routing, security, session management, and other fundamental services.
• Configuration & Helpers: In “application/config”, “application/helpers”, “application/hooks”, etc., which provide project-level settings and utility functions.
• Third-Party Libraries: The “application/third_party” directory includes PHPExcel (for spreadsheet operations) and additional libraries that support extended functionality.
• Database: Although not explicitly mentioned in the README, the presence of “project_management.sql” and “application/config/database.php” indicates a relational database (likely MySQL) that stores user, project, and progress data.
• File Uploads & Assets: Folders like “uploads”, “public/files”, “img”, “fonts” handle static asset serving and file management.
Their Relationships and Data Flow
• A user (through a browser) interacts with the frontend (HTML/CSS/JS). The request is sent to the web server where CodeIgniter’s index.php bootstraps the framework.
• The Router (in system/core/Router.php) directs requests to appropriate Controllers.
• Controllers use Models to perform business logic and data operations (e.g., fetching lecturer or student data from the database).
• Once the data is processed, Controllers load Views that render the final output (HTML), sending it back to the client.
• Additional utilities (helpers and libraries) are used throughout for common tasks such as form validation, session management, file uploads, and dealing with Excel spreadsheets via PHPExcel.
• External data integration (such as Excel file import/export) happens through the third-party PHPExcel library integrated in the application.
• Logging (in application/logs) helps track errors and system events.
• Configuration files (in application/config) ensure that settings (like auto-loading libraries or setting routing defaults) are maintained centrally.
Architectural Patterns and Technologies
• The MVC (Model-View-Controller) pattern is central to this project.
• Separation of concerns is maintained: controllers manage interactions, models abstract data, and views present the UI.
• Dependency injection and CodeIgniter’s internal Loader facilitate the flexible inclusion of libraries, helpers, and third-party integrations.
• PHPExcel: A significant third-party component integrated to handle Excel files.
• Standard CodeIgniter libraries (session, cache, email) as seen in “system/libraries” add robustness and common utility support.
• The database configuration indicates a relational DB, with multiple drivers available (MySQL, mysqli, etc.) showing flexibility in database support.