Student Record

Management System

Submitted by:
Ayesha Hafeez

Session: 2023-2025

Department of Computer Science

Informatics College Kamalia
affiliated with
Khwaja Fareed University of Engineering & Information Technology
Rahim Yar Khan
 Declaration

We hereby declare that this project report is based on our original work except for citations and
quotations which have been duly acknowledged. We also declare that it has not been previously and
concurrently submitted for any other degree or award at Khwaja Fareed University of engineering &
Information Technology or other institutions.

Reg. No. : INFBCOSC231104017

Name: Ayesha Hafeez

Signature:

Date:
 Approval for Submission

I certify that this project report entitled Student Record Management was prepared by Ayesha
Hafeez has met the required standard for submission in partial fulfillment of the requirements for the
award of Bachelor of Science in Computer Science (Lateral Entry) at Khwaja Fareed University of
Engineering & Information Technology.
Approved by:

Signature: _________________________

Supervisor: Muaz ul Hassan

Date : _________________________
Meeting Logs

Date Meeting Logs Signature

 Acknowledgement

First and foremost, we would like to express my sincere gratitude to Almighty Allah for giving us the
strength, knowledge, and ability to complete this project successfully.

We are deeply thankful to my supervisor, Muhammad Asif, for his valuable guidance, continuous
support, and encouragement throughout the duration of this project. His insightful feedback and
suggestions were instrumental in shaping the final outcome.

Special thanks to our family and friends for their unwavering support, patience, and motivation,
without which this journey would have been much more difficult.

Finally, we would like to acknowledge everyone who contributed to this project directly or indirectly.
Your help and encouragement are greatly appreciated.
 Abstract

A Student Record Management System is a software application designed to manage and

maintain student information in an organized and efficient manner. The main purpose of this
system is to replace the traditional manual record-keeping system with a computerized
solution. It helps educational institutions store, update, and retrieve student records easily and
accurately.

This system manages important student data such as student personal details, admission
information, academic records, attendance, and results. All data is stored in a centralized
database, which reduces paperwork and saves time. The system also improves data security
by allowing only authorized users such as administrators and teachers to access or modify
records.

The Student Record Management System provides features like adding new student records,
updating existing information, searching student details, and generating reports. It reduces
human errors, improves efficiency, and ensures quick access to student information whenever
needed. Overall, this system helps institutions manage student records smoothly, improves
administrative work, and supports better decision-making.
CHAPTER 1: INTRODUCTION

1.1 Background of the Project

In the contemporary educational landscape, the management of information is as critical as

the delivery of education itself. Educational institutions, ranging from primary schools to
large universities, generate massive volumes of data on a daily basis. This data encompasses
student personal details, academic records, attendance logs, and enrollment histories.
Historically, the management of this data has been a manual process, reliant on physical
paper files, ledgers, and filing cabinets. While this method served its purpose in an era of
smaller student populations, the exponential growth in enrollment numbers has rendered
manual record-keeping obsolete, inefficient, and prone to catastrophic errors.

The advent of Information Technology (IT) has revolutionized how organizations handle
data. Database Management Systems (DBMS) have emerged as the backbone of modern
administration, allowing for the storage, retrieval, and manipulation of data in ways that were
previously unimaginable. The Student Record Management System (SRMS) proposed in this
project is a direct response to the need for modernization. It represents a shift from the
physical to the digital, leveraging the power of web technologies to create a centralized,
secure, and efficient platform for managing student lifecycles.

1.2 The Problem Statement

The reliance on manual systems for student record management presents a multitude of
challenges that hinder the operational efficiency of educational institutions. The primary issue
is data redundancy. In a manual system, the same student's name and details might be
written in the admission register, the library register, the examination log, and the attendance
sheet. If a student changes their address, a clerk must manually update four or five different
physical locations. This not only consumes valuable administrative time but also leads to
inconsistencies where data is updated in one place but not another.

Furthermore, data retrieval in a manual system is notoriously slow. Searching for a specific
student's academic history from five years ago requires physical access to dusty storage
rooms and sifting through piles of paper. This latency in information retrieval delays
decision-making and frustrates stakeholders, including parents and faculty.
Security is another glaring vulnerability. Physical records are susceptible to environmental
damage—such as fire, water, or pests—and are easily misplaced or stolen. There is no audit
trail to determine who accessed a physical file or if a page was removed. Consequently, the
integrity of academic records, which determine a student’s future career prospects, is
constantly at risk in a manual environment.

1.3 Objectives of the Project

The primary objective of this project is to design and develop a web-based Student Record
Management System using HTML, CSS, PHP, and MySQL. The specific objectives are as
follows:

 To Centralize Data: To create a single, unified database where all student

information is stored. This ensures that data is entered once and is available across the
system, eliminating redundancy.
 To Enhance Data Integrity: To implement constraints and validation checks during
data entry (e.g., ensuring email addresses are valid, preventing duplicate Roll
Numbers) to ensure that the data stored is accurate and reliable.
 To Improve Accessibility: To provide a web-based interface that allows authorized
administrators to access records from any computer connected to the local network,
breaking the dependence on a specific physical location.
 To Secure Information: To implement authentication mechanisms, such as a secure
Admin Login, ensuring that only authorized personnel can view or modify sensitive
student data.
 To Streamline Operations: To automate the calculation of results and the generation
of lists, thereby reducing the manual workload on staff and freeing them to focus on
more critical educational tasks.

1.4 Scope of the Project

The scope of this project is defined by the requirements of a typical educational institution.
The system is designed to handle the core administrative functions related to student
management.
 Administrator Scope: The administrator is the super-user of the system. Their scope
includes the ability to add new student records, update existing information (such as a
change of address or phone number), delete obsolete records, and manage academic
results.
 Student Scope: The system includes a student-facing module where students can
retrieve their result status by entering their unique Roll Number. This allows for self-
service and reduces the traffic to the administration office.
 Technical Scope: The system is built as a web application running on a local server
(localhost) using XAMPP. It utilizes a Relational Database (MySQL) for backend
storage and PHP for server-side processing.
CHAPTER 2: SYSTEM ANALYSIS

2.1 Analysis of the Existing System (Manual Approach) Before the development of the
computerized system, a thorough analysis of the existing manual workflow was conducted.
Currently, the institution operates on a paper-based model. When a student is admitted, they
fill out a physical form. This form is filed in a "Student Folder." When exams are conducted,
teachers write marks on paper sheets, which are then physically carried to the data entry room
or the principal's office. These marks are manually transcribed into a "Master Ledger."

This existing system is fraught with inefficiencies. The physical storage of these files requires
significant space. Over time, paper degrades, ink fades, and handwriting becomes illegible.
Furthermore, generating reports is a nightmare. If the principal asks for a list of "All students
who failed Mathematics," a staff member must manually check every single row in the ledger
and write down the names. This process can take days. The existing system also lacks
concurrent access; only one person can read the ledger at a time, creating a bottleneck during
peak periods like admission or result declaration.

2.2 Analysis of the Proposed System (Automated Approach) The proposed Student
Record Management System is designed to address the shortcomings of the manual approach
through automation and digitization. The proposed system is a web-based application,
meaning it runs in a web browser. This eliminates the need to install specific software on
every computer; as long as the computer has a browser (like Chrome or Firefox), the system
is accessible.

In the proposed system, data storage is digital. The physical space required to store thousands
of student records is reduced to a few megabytes on a hard drive. Backups can be automated,
ensuring that data is never lost, even in the event of hardware failure. Reporting becomes
instantaneous. The query that took days in the manual system ("List failing students") takes
milliseconds in the proposed system using a simple SQL command. Additionally, the system
supports multi-user access (if deployed on a network), allowing multiple staff members to
work simultaneously without waiting for a physical file.

2.3 Feasibility Study A feasibility study was conducted to determine if the project is viable.
The study focused on three key areas:
  Technical Feasibility: This assesses whether the necessary technology exists and if
the team has the skills to use it. The project uses HTML, CSS, PHP, and MySQL.
These are open-source, mature, and widely documented technologies. They run
efficiently on standard hardware (a basic laptop or desktop) without requiring
expensive servers. Therefore, the project is technically highly feasible.
 Operational Feasibility: This assesses if the users will accept the system. Since the
User Interface (UI) is built with simple HTML forms that resemble paper forms, the
learning curve for the staff is minimal. No advanced technical training is required to
use the system—only basic computer literacy. This ensures high operational
feasibility.
 Economic Feasibility: This assesses the cost-benefit ratio. The cost of developing
this project is primarily time, as the software tools (VS Code, XAMPP, Web
Browsers) are free. Compared to the cost of buying paper, printing forms, and
maintaining physical storage cabinets, the digital system offers significant long-term
cost savings. Thus, the project is economically viable.

2.4 Hardware and Software Requirements To implement and run the Student Record
Management System, the following configurations were utilized:

 Hardware: A computer system with an Intel Core i3 processor (or equivalent) was
used for development. A minimum of 4GB RAM is recommended to run the local
server (Apache) and the database (MySQL) smoothly. The storage requirement is
minimal, with the application taking up less than 100MB, though 50GB is
recommended for the operating system and future data growth.
 Software: The operating system used was Windows 10. The development
environment was set up using XAMPP, a software stack that bundles Apache (Web
Server), MySQL (Database), and PHP. The code was written using Visual Studio
Code, a lightweight text editor with syntax highlighting. Google Chrome was used as
the primary web browser for testing the interface.
CHAPTER 3: SYSTEM DESIGN

3.1 System Architecture The architecture of the Student Record Management System
follows the classic Client-Server model, specifically the Three-Tier Architecture.

1. Presentation Tier (Client): This is the topmost level of the application. The user
interface is displayed here. It is built using HTML to structure the content and CSS to
style it. This tier runs in the user's web browser. It collects user input (e.g., username,
password, student details) and sends it to the server.
2. Application Tier (Server): This logic tier controls the application's functionality by
performing detailed processing. It is built using PHP. When the client sends a request
(e.g., "Add this student"), the PHP script processes this request, validates the data, and
decides what to do next. It acts as the bridge between the user and the database.
3. Data Tier (Database): This tier consists of the database storage system, which is
MySQL. Here, information is stored and retrieved. The Application Tier
communicates with this tier using SQL (Structured Query Language) queries.

3.2 Database Design and Schema The database is the heart of the SRMS. A database named
srms_db was created to store all project data. The design adheres to the principles of
Normalization to reduce redundancy. The database consists of several interrelated tables.

Table 1: The Administrator Table (admin_login) This table is crucial for security. It stores
the credentials of the system administrators. It contains columns for a unique ID, the
username, and the password. To enhance security, in a production environment, passwords
should be hashed (encrypted) rather than stored in plain text.

Table 2: The Student Details Table (students) This is the primary repository of student
data. The Primary Key is id (Auto-Increment), but the functional unique key is roll_no, as
no two students can have the same Roll Number.

 name: Varchar(100) - Stores the full name.

 email: Varchar(100) - Stores contact email.
 class: Varchar(20) - Stores the grade/class level.
 dob: Date - Stores the date of birth for age verification.
Table 3: The Academic Results Table (results) This table stores the marks obtained by
students. It is linked to the students table via a Foreign Key (roll_no). This relationship
ensures "Referential Integrity"—meaning you cannot enter a result for a Roll Number that
does not exist in the student table.

 subject: Varchar(50) - The name of the course/subject.

 marks: Integer - The score obtained.

3.3 User Interface (UI) Design The design philosophy for the UI was "Simplicity and
Clarity."

 Color Scheme: A professional color palette was chosen (e.g., Blue and White) to
convey trust and calmness.
 Layout: A sidebar layout was used for the Admin Dashboard to allow easy
navigation between different modules (Dashboard, Add Student, Manage Result,
Logout).
 Forms: Input forms were designed with clear labels and placeholders. HTML5
validation attributes (like required) were used to provide immediate feedback to the
user if a field was missed.
CHAPTER 4: IMPLEMENTATION

4.1 Introduction

This chapter describes the implementation and testing of the Student Record Management
System. Implementation refers to the process of converting the system design into a working
software application. Testing is performed to ensure that the system works correctly,
efficiently, and according to the requirements.

The Student Record Management System has been developed to manage student information
in a computerized environment. The system allows administrators to add, update, delete, and
view student records easily. It reduces manual work, saves time, and improves data accuracy.

This chapter explains the tools and technologies used, system architecture, database design,
module implementation, and testing methods. Different types of testing have been performed
to verify that the system is reliable and user-friendly.

4.2 System Implementation Overview

System implementation is the most important phase of software development. In this phase,
the system design is converted into actual code using selected programming languages and
tools. The Student Record Management System has been implemented as a web-based
application.

The system follows a modular approach, where each function is divided into separate
modules. This makes the system easy to understand, maintain, and upgrade in the future.

4.3 Tools and Technologies Used

The following tools and technologies were used for implementing the Student Record
Management System:

4.3.1 Programming Languages

 PHP (Hypertext Preprocessor):

PHP is used as the server-side scripting language. It handles business logic, form
processing, and database communication.
  HTML (HyperText Markup Language):
HTML is used to design the structure of web pages.
 CSS (Cascading Style Sheets):
CSS is used for styling and improving the appearance of web pages.
 JavaScript:
JavaScript is used for client-side validation and interactive features.

4.3.2 Database

 MySQL:
MySQL is used as the backend database to store student records securely.

4.3.3 Software Tools

 XAMPP Server:
XAMPP is used as a local server environment that includes Apache, PHP, and
MySQL.
 Web Browser:
Google Chrome is used to test and run the system.
 Code Editor:
Visual Studio Code is used for writing and managing source code.

4.4 System Architecture

The Student Record Management System follows a three-tier architecture:

1. Presentation Layer
This layer contains the user interface. It includes HTML forms and web pages that
users interact with.
2. Application Layer
This layer contains PHP scripts that process user requests, apply business rules, and
communicate with the database.
3. Database Layer
This layer stores student data in MySQL tables.

This architecture improves system performance, security, and scalability.

4.5 Database Implementation

4.5.1 Database Design

The database is designed to store student information in a structured format. Each table
represents a specific entity.

4.5.2 Student Table

Each record is uniquely identified using Student ID as the primary key.

4.5.3 Admin Table

The user table stores login credentials for system users such as administrators.

Fields include:

 User ID
 Username
 Password
 User Role

Passwords are stored in encrypted form to ensure security.

4.6 Module Implementation

The system is divided into the following modules:

4.6.1 Login Module

The login module provides authentication for system users. Only authorized users can access
the system.

Features

 Username and password validation

 Error message for invalid login
 Secure access control

Implementation

The login form collects user credentials. PHP verifies these credentials from the database. If
the data is correct, the user is redirected to the dashboard.

4.6.2 Admin Dashboard Module

The dashboard provides an overview of system activities.

Features

 Total number of students

 Quick access to system modules
 Navigation menu

The dashboard improves usability and provides easy access to all functions.
4.6.3 Add Student Module
This module allows administrators to add new student records.
Features

 Student registration form

 Data validation
 Record insertion into database

Implementation

The form collects student details. PHP validates the data and inserts it into the student table.

4.6.4 View Student Module

This module displays student records.

Features

 List of students
 Search functionality
 View detailed student profile

Data is fetched from the database and displayed in tabular format.

4.6.5 Update Student Module

This module allows administrators to modify existing student records.

Features

 Edit student details

 Update database records
 Confirmation messages

This module ensures data remains up to date.

4.6.6 Delete Student Module

This module allows administrators to remove student records.

Features

 Delete confirmation
 Secure record deletion

This helps manage outdated or incorrect records.

4.6.7 Search Module

The search module allows quick retrieval of student information.

Features

 Search by name or registration number

 Fast results

This improves system efficiency.

4.7 Security Implementation

Security is an important part of the system.

4.7.1 Authentication

Only registered users can log in.

4.7.2 Authorization

Access rights are based on user roles.

4.7.3 Data Validation

Input validation prevents invalid or harmful data.

4.7.4 Database Security

Prepared statements are used to prevent SQL injection.

4.8 Testing Overview

Testing ensures that the system works correctly and meets user requirements. Various testing
techniques were applied during development.

4.9 Types of Testing Performed

4.9.1 Unit Testing

Unit testing checks individual modules separately.

Tested Modules

 Login module
 Add student module
 Search module

Each module produced correct output for valid input.

4.9.2 Integration Testing

Integration testing checks communication between modules.

Examples

 Login → Dashboard
 Add Student → View Student

All modules integrated smoothly.

4.9.3 System Testing

System testing verifies the complete system.

Test Cases

 User login
 Student record management
  Data retrieval

The system passed all tests successfully.

4.9.4 Functional Testing

Functional testing ensures all functions work according to requirements.

Results

 Add, update, delete operations worked correctly

 Search functionality returned accurate results

4.9.5 User Acceptance Testing

User acceptance testing was conducted by potential users.

Feedback

 System is easy to use

 Interface is clear
 Performance is satisfactory

4.10 Test Case Examples

Test Case 1: Login Functionality

 Input: Valid username and password

 Expected Result: Successful login
 Actual Result: Login successful
 Status: Passed

Test Case 2: Add Student

 Input: Complete student details

 Expected Result: Record added
 Actual Result: Record added successfully
  Status: Passed

Test Case 3: Search Student

 Input: Student name

 Expected Result: Correct record displayed
 Actual Result: Correct record displayed
 Status: Passed

4.11 Error Handling

The system handles errors gracefully.

Examples

 Invalid login credentials

 Empty form fields
 Duplicate entries

User-friendly error messages are displayed.

4.12 Performance Testing

Performance testing checks system speed and responsiveness.

Results

 Fast page loading

 Quick database queries
 No system crashes during testing

4.13 Limitations During Testing

Some limitations were observed:

 Internet dependency
 Limited concurrent users
  Basic user roles

These limitations can be improved in future versions.

4.14 Summary

This chapter explained the implementation and testing of the Student Record Management
System. The system was implemented using PHP, MySQL, HTML, CSS, and JavaScript. All
modules were developed and tested successfully.

Testing confirmed that the system is reliable, secure, and user-friendly. The Student Record
Management System fulfills its objectives and provides an efficient solution for managing
student records.
Chapter 6: Development Phase
5.1 Development Environment

The development environment of the Hostel Management System (CMS) plays a crucial role
in ensuring the system’s efficiency, reliability, scalability, and maintainability. The selection
of appropriate tools and technologies was guided by factors such as ease of development, cost
effectiveness, compatibility, security, and widespread industry usage. The CMS is developed
as a web-based application using open-source technologies, making it accessible, flexible,
and suitable for organizational use.

Programming Language: PHP

The server-side development of the Hostel Management System is carried out using PHP
(Hypertext Preprocessor). PHP is a widely used, open-source scripting language
specifically designed for web application development. It is well known for its simplicity,
flexibility, and strong integration with database systems such as MySQL. PHP processes user
requests, executes business logic, handles authentication, validates user inputs, and
communicates with the database.

One of the major advantages of using PHP is its compatibility with various web servers and
operating systems. PHP allows dynamic content generation, which is essential for features
such as Hostel submission, real-time status updates, and administrative dashboards. It also
supports session management, which is used to maintain secure user login sessions for
students and administrators. Due to its extensive documentation and community support,
PHP enables faster development and easier troubleshooting, making it an ideal choice for this
project.

Database: MySQL

The database component of the Hostel Management System is implemented using MySQL, a
powerful and reliable relational database management system. MySQL is used to store and
manage all system data, including user accounts, student details, room information, fee
records, Hostel details, and administrative actions. The database is designed using relational
principles to ensure data consistency, integrity, and efficient storage.
MySQL supports structured query language (SQL), which allows the system to perform
operations such as inserting new Hostels, updating Hostel statuses, retrieving Hostel history,
and generating reports. Relationships between tables are maintained using primary keys and
foreign keys, which helps reduce data redundancy and improves accuracy. Additionally,
MySQL provides strong security features such as user privileges and access control, ensuring
that sensitive data is protected from unauthorized access.

Front-End Technologies: HTML, CSS, and JavaScript

The front-end of the Hostel Management System is developed using HTML, CSS, and
JavaScript, which together create an interactive and user-friendly interface.

HTML (HyperText Markup Language) is used to structure the web pages and define the
layout of system components such as forms, buttons, tables, and navigation menus. It
provides the basic framework through which users interact with the system.

CSS (Cascading Style Sheets) is used to enhance the visual appearance of the system. It
controls the design aspects such as colors, fonts, spacing, alignment, and responsiveness. CSS
ensures that the system interface is visually appealing, consistent, and easy to use across
different devices and screen sizes.

JavaScript is used to add interactivity and improve user experience. It enables client-side
validation of input fields, such as ensuring required fields are filled before Hostel submission.
JavaScript also helps in dynamic content updates without refreshing the entire page, making
the system more responsive and efficient.

Together, these front-end technologies ensure that the Hostel Management System is
intuitive, accessible, and user-friendly for both students and administrators.

Web Server: Apache

The Hostel Management System is deployed on an Apache web server, which is one of the
most popular and widely used web servers worldwide. Apache is responsible for handling
incoming HTTP requests from users’ web browsers and delivering the appropriate web pages
and responses.
Apache works seamlessly with PHP through server modules, enabling the execution of PHP
scripts on the server. It provides a stable and secure environment for hosting web applications
and supports various security features such as authentication, authorization, and encrypted
communication. Apache’s flexibility allows easy configuration and integration with MySQL,
making it suitable for the CMS.

The use of Apache also supports scalability, allowing the system to handle multiple users
accessing the system simultaneously without performance degradation.

Integrated Development Environment

For development and testing purposes, the system can be deployed using a local server
environment such as XAMPP or WAMP, which includes Apache, MySQL, and PHP in a
single package. This setup simplifies development and debugging and allows developers to
test system functionalities before deployment. Once tested, the system can be hosted on a live
server for real-world use.

5.2 Module Description

Each module of the system is developed separately and integrated to form the complete
application.
CHAPTER 6: SYSTEM TESTING

6.1 Testing Methodology Testing is a critical phase in the Software Development Life Cycle
(SDLC). For this project, a combination of Unit Testing and System Testing was employed.

 Unit Testing: This involved testing individual modules in isolation. For example, the
"Database Connection" file was tested independently to ensure it could successfully
ping the MySQL server before it was included in other files.
 Black Box Testing: This method was used to test the functionality without looking at
the internal code structure. We acted as an end-user, inputting various data sets to see
if the system behaved as expected (e.g., entering text into a "Marks" field to see if the
system rejected it).

6.2 Test Cases and Results A specific set of test cases was designed to validate the system
features.

Test Case 1: Login Verification

 Input: Username: "admin", Password: "wrongpassword"

 Expected Output: System should deny access and show "Invalid Credentials."
 Actual Output: System denied access and displayed the error message.
 Result: PASS.

Test Case 2: Data Persistence

 Input: Add a new student "John Doe", Roll No: "101".

 Action: Click "Save" and then check the MySQL Database (PHPMyAdmin).
 Expected Output: A new row should appear in the students table.
 Actual Output: The row was successfully created.
 Result: PASS.

Test Case 3: Duplicate Entry Prevention

 Input: Try to register another student with Roll No "101".

 Expected Output: System should throw an error saying "Duplicate Key" or "Student
already exists."
 Actual Output: The database rejected the query due to the PRIMARY KEY
constraint.
 Result: PASS.
CHAPTER 7: CONCLUSION AND FUTURE SCOPE

7.1 Conclusion The development of the Student Record Management System has been a
successful endeavor in understanding the practical applications of web technologies. The
project successfully met its primary objectives: it provides a secure, efficient, and user-
friendly platform for managing student data. By utilizing PHP and MySQL, the system
eliminates the redundancy and physical limitations of paper-based records. The project
demonstrates that even a lightweight web application can significantly improve
administrative efficiency in an educational setting. It bridges the gap between traditional
administration and modern digital management.

7.2 Limitations While the system is functional, it operates with certain limitations:

1. Local Hosting: Currently, the system runs on a localhost server (XAMPP). It is not
accessible over the public internet.
2. Basic Security: While it uses login authentication, advanced security features like
Two-Factor Authentication (2FA) and SSL encryption are not yet implemented.
3. Reporting: The system displays data on the screen, but it lacks a built-in feature to
export these reports to PDF or Excel formats for printing.

7.3 Future Scope There is significant potential for enhancing this system in future iterations:

1. Cloud Deployment: The application can be hosted on a live web server (using a
hosting provider) to allow access from anywhere in the world.
2. Parent Module: A specific login module for parents could be added, allowing them
to view their child's attendance and remarks from teachers.
3. SMS/Email Integration: The system could be upgraded to automatically send email
notifications to students when their results are declared.
4. Attendance System: Integrating a biometric or digital attendance module would
make this a complete School Management ERP (Enterprise Resource Planning)
solution.
References
1. Pressman, R. S., & Maxim, B. R. (2019). Software Engineering: A Practitioner’s
Approach (9th ed.). McGraw-Hill Education.
2. Sommerville, I. (2016). Software Engineering (10th ed.). Pearson Education.
3. Welling, L., & Thomson, L. (2017). PHP and MySQL Web Development (5th ed.).
Addison-Wesley.
4. Silberschatz, A., Korth, H. F., & Sudarshan, S. (2020). Database System Concepts
(7th ed.). McGraw-Hill Education.
5. MySQL Documentation. (2024). MySQL 8.0 Reference Manual. Oracle Corporation.
6. PHP Documentation. (2024). PHP Manual. The PHP Group