How abirhasankhan/capstone-management-webapp works
Main Components
• Frontend Components:
• Two primary view directories under “www”: one for Faculty (www/facultyView) and one for Students (www/studentView). These handle the presentation pages such as login, registration, profile, grading, and project status.
• Assets and resources: CSS files (located in www/css) for styling, JS files (in www/js) for interactive functionality, and static images for screenshots and design reference.
• Composer-related files in www (composer.json and composer.lock) hint at dependency management for PHP packages.
• Backend Components:
• The server directory (www/server) contains configuration files (e.g., config.php) that likely handle database connections and global settings.
• PHP scripts spread across the facultyView and studentView directories that implement business logic for user authentication, registration, grading, and viva management.
• Database:
• The capstonedatabase.sql file indicates the usage of a MySQL database for storing user data, project details, grading records, and scheduling information.
• External Services & Dependencies:
• The project uses PHPMailer for email verification.
• Bootstrap is used on the frontend for responsive design.
Understand the Relationships and Interactions
• The Frontend (client-side) interacts with the Backend PHP scripts through direct form submissions and page requests. Each view (facultyView/studentView) presents specific UI components that trigger server-side actions.
• The Backend (PHP scripts) processes these requests, performs business logic (e.g., registration, grade submission, login verification) and communicates with the MySQL database for data persistence.
• Email verification via PHPMailer is triggered during user registration, adding an external service dependency.
• The Admin interface (implied through the README) also plays a role, though not clearly separated in the file tree; it likely resides within some of these PHP pages that admin users can access.
Architectural Patterns and Design Principles
• The project is structured in a modular way, separating frontend views (by user role) from server-side configurations and business logic.
• Although not explicitly MVC, the directory separation (views in facultyView and studentView, server config separate) approximates a separation of concerns.
• The usage of Composer for dependency management and clear separation of static assets (css, js, images) marks adherence to modern web development design principles.
• Client (Browser) Layers: Student Interface and Faculty/Administrator Interface.
• Web Server Components: PHP Backend (segregated into role-specific controllers for login, registration, grading, etc.) and server configuration.
• Database Server: MySQL Database, with connections indicated by PHP scripts.
• External Email Service: PHPMailer (or a mail server) used for sending verification emails.
• Dependency/Package Manager: Composer managing third-party libraries.
• The client sends HTTP requests to the PHP scripts.
• PHP scripts interact with the MySQL database.
• PHPMailer is invoked for verification emails.