How subhasis-sahoo/final_project works
Project type and purpose
• This is a monolithic, role-based, full-stack PHP web application for digital exam registration and admit-card generation.
• It serves five main user roles (students, exam cell, accounts dept, faculty, dean) each with its own PHP module and UI pages.
File structure
• Top-level PHP modules:
• accounts_dept/ (dashboard.php, sidebar.php)
• dean/
• exam_cell/ (functions.php, multiple scheduling & registration pages + JS/CSS subfolders)
• faculty/
• students/ (functions.php, scripts/, styles/, registration & history pages)
• Shared resources:
• generate_random_string.php, header.php
• utilities/ (common JS/CSS for header, sidebar, loader, dashboard)
• public/assets & public/sql (static assets and database dump scripts)
• No separate frontend framework; Bootstrap-based HTML/CSS/JS.
README
• Tech stack: PHP on Apache (via XAMPP), MySQL (database model linked).
• Core use cases: student self-service registration; exam-cell scheduling; administrative dashboards; admit-card PDF/web view.
Main components
a. Client Tier (Web Browser)
• Students, Exam-cell staff, Accounts staff, Faculty, Dean each access via HTTP/HTTPS.
• UI pages built with PHP-generated HTML, Bootstrap CSS, JavaScript.
b. Web Server Tier
• Apache + PHP interpreter
• Monolithic codebase, organized into role-based modules (accounts_dept/, dean/, exam_cell/, faculty/, students/)
• Shared libraries (generate_random_string.php, header.php) and utilities for common UI elements.
c. Data Tier
• MySQL database (tables defined in public/sql/project_x*.sql)
• Core entities: Users, Students, Exams, Registrations, AdmitCards, Fees, Departments, Schedules
d. Static Asset Service
• Served from public/assets (images, CSS/JS libraries not tied to a module)
Relationships and interactions
• Client → Web Server: HTTP requests for pages and AJAX calls (scripts/*.js)
• Web Server → Database: PHP MySQL queries (via functions.php in each module)
• Data flow:
• Student requests registration form → server validates → writes to Registration table → returns confirmation.
• Exam-cell schedules exams → writes to Schedule table → notifications back to students.
• Admit-card generation → server composes data from multiple tables (Registrations, Students) → renders printable view.
• Accounts/faculty/dean dashboards query aggregated data.
Important architectural patterns and design principles
• Modular separation by user role (folder-based “sub-applications”)
• Shared utilities for cross-cutting concerns (UI layout, random string generation)
• Layered approach: Presentation (PHP + HTML/JS/CSS) → Business logic (PHP functions) → Persistence (MySQL)
Detail without overcomplicating
• Both synchronous page loads and asynchronous JS calls
• How shared utilities and header.php tie into each module’s control flow
• Public/sql scripts as part of your Data Tier deployment/development process