How anujakunniyarath/bbms_project works
Main components
• Client Browser (HTML/CSS/JS)
• Web Server (Apache + PHP runtime)
• Database Server (MySQL)
• Static Asset Store (CSS, HTML templates, JS files)
Break down the Web Server tier into functional modules
• Authentication Module
– loginpage.php → validates credentials → session management
• Donor Management Module
– donor_form.php → donor_submit.php → donor_details.php
• Patient Management Module
– patient_form.php → patient_process.php → patient_details.php
• Doctor Management Module
– doctor_details.php
• Blood Stock Module
– stock.php → updates/retrieves stock levels
• Search Module
– search.php → dynamic queries on donors/patients/doctors/stock
• Presentation Layer
– index.html → home page
– bbms_bbDetails.html
– CSS (style.css, loginstyle.css, bbms_bbDetails.css)
Relationships and data flows
– Browser issues HTTP(s) requests → Web Server (PHP scripts)
– PHP scripts read/write → MySQL database (CRUD operations)
– Responses rendered as HTML/CSS/JS and sent back → Browser
Architectural patterns
• Three‑Tier Architecture (Presentation, Business Logic, Data)
• Monolithic PHP application (no microservices)
• Server‑side rendering for all pages
• Logical MVC separation (controllers = .php scripts, views = HTML/CSS, model = MySQL)
Relevant technologies to annotate
• Apache HTTP Server + mod_php
• PHP 7.x/8.x
• MySQL 5.x/8.x
• HTML5/CSS3/Vanilla JS
Detail to capture
• Static assets served directly (CSS/HTML) vs dynamic pages (PHP scripts)
• Session management crossing between Authentication and other modules
• Data‑flow for key use cases: donor registration, patient lookup, stock update
• Search module hitting multiple tables