How mavenzer/placement--management--system works
Project type and purpose
• Full-stack web application for coordinating campus recruitments.
• Provides three core portals (Student, Institute/HOD, Principal) and one Placement/Company portal.
• Two public homepages (“Master” and “Drives”) for visitors.
File structure
• Top-level directories map directly to modules/portals:
– SProfile → Student Portal
– HODProfile → Institute/HOD Portal
– PriProfile → Principal Portal
– PProfile & updation--companies → Placement/Company Portal
– Homepage & Drives → Public frontends
• Database folder holds two SQL schemas (“details” and “placement”).
• Static assets (CSS/JS/images) are local per‐module.
• Entry points are PHP scripts in each folder (e.g., index.php, login.php, mail.php).
Extract architectural hints from the README
• Monolithic PHP code, object-oriented DB access with mysqli.
• Two MySQL databases imported via Revised.sql / Skeleton Database.sql.
• Uses Bootstrap, jQuery, Ajax, Google Maps API and simple mail.php for notifications.
• Four “portals” with distinct responsibilities and shared underlying data models.
Main components
a. Clients (browsers/mobile) for:
– Public users (Master Homepage, Drives Homepage)
– Students (SProfile)
– Institutes/HODs (HODProfile)
– Principals (PriProfile)
– Placement/Companies (PProfile & updation--companies)
b. Web Server Layer
– Apache/PHP runtime hosting all .php entry scripts
– Shared libraries for database access, session management, authentication
c. Data Layer
– MySQL “details” DB holds student profiles, credentials, preferences
– MySQL “placement” DB holds companies, drives, eligibility, assignments
d. External Services
– SMTP/Mail service via mail.php
– Google Maps API for location-based features
e. Optional Shared Cache or Session Store (if introduced later)
Relationships & Data Flows
• Client → HTTPS → Apache/PHP → Business Logic
• Business Logic → SQL queries → MySQL
• Business Logic → External API calls (Mail, Google Maps)
• Responses flow back to client; modules communicate via shared tables.
Architectural patterns & principles
• Layered architecture: Presentation (PHP+HTML+CSS+JS) → Business logic (PHP classes) → Data access (mysqli) → Data store (MySQL).
• Module-based separation: each portal is a folder, but they share common DB schemas and styling frameworks.
• Notification pattern: mail.php invoked by portal controllers.
• Role-based access: authentication & session management per portal.