A

PROJECT REPORT

ON

“CLASS MANAGEMENT SYSTEM”

BY

Miss. SRUSHTI P. MALPEKAR

Miss. SHRUSHTI S. SINGH

TOWARDS THE PARTIAL FULFILLMENT OF

Bachelor of Computer Application III(Sem-VI)

Tilak Maharashtra Vidyapeeth (Pune)

(2023-2024)

UNDER GUIDANCE OF

Prof. R. H. Gohel

SHAILENDRA EDUCATION SOCIETY’S

COMPUTER CENTER (SESCOM)

 SHAILENDRA EDUCATION SOCIETY’S

COMPUTER CENTER (SESCOM)

CERTIFICATE

This is certify that the project entitled

“CLASS MANAGEMENT SYSTEM”

Has been successfully competed in the academic year 2023-2024 by

Name :- Miss SRUSHTI P. MALPEKAR & SHRUSHTI S. SINGH

Exam SeatNo .____________________

Towards the partial fulfillment of the B.C.A-III (Sem-VI)

as prescribed by Tilak Maharashtra Vidyapeeth(Pune).

Prof. R. H. Gohel Mr. Bhushan Pimple

Guide Examiner Head of Department
 DECLARATION

To,

Co-Ordinator,

Shailendra Education Society IT College

Respected Sir,

We, the undersigned student of B.C.A. III (Bachelor in Computer

Application) hereby declare the project report entitled “ClASS MANAGEMENT
SYSTEM” written and submitted by us. The empirical binding in this report is based on
the data collected by us, while preparing this project report.

From: Srushti Malpekar Signature1 ________________

Shrushti Singh Signature2_________________

 ACKNOWLEDGMENT

Every project is always a scheduled, guided & coordinated team effort aimed at achieving
common minimum goals. This minimum goal cannot be achieved without the guidance of guide.

We hereby, express our heartily thanks to those persons who helped us and spend their
valuable time and efforts to guide us for the project work. Without their guidance and co-
operation the project work would not have been successful.

This is the opportunity for us to express our honest thanks to them we would like to
thanks to our Head of Computer Science Department, HOD Bhushan Pimple for encouraging
us to prepare this project work.

We have no words to express thanks to our project guide Hemchandra Kumbhar and

R .H. Gohel for their guidance, co-operation and interest to complete this project work.

Finally, we express our deep gratitude towards our family for their model support,
encouragement. Also we are thankful to our friends for their co-operation and helping nature
during this period.
 INDEX

Sr. Title Page

No. No.
1 Introduction

1.1 Purpose Of The Project

1.2 Problem In The Existing System
1.3 Solution Of These Problems
2 System Analysis

2.1 Introduction
2.2 Analysis Model
2.3 Study Of The System
2.4 Hardware & Software Specifications
2.5 Proposed System
3 Feasibility Report

3.1 Technical Feasibility

3.2 Operational Feasibility
3.3 Economic Feasibility
4 System Design

4.1 Introduction
4.2 E-R Diagram
4.3 DATA Flow Diagrams
4.4 Context Diagram
4.5 Data Dictionary
4.6 Unified Modeling Language
4.7 Class Diagram
4.8 Sequence Diagram
 Introduction

In today's fast-paced educational landscape, efficiency and organization are paramount.

As we navigate through the complexities of managing classes and tuitions, the need for a robust
management system becomes increasingly apparent. It is with great enthusiasm that I introduce
our comprehensive project report on the development and implementation of a cutting-edge
Class Management System.

Education is not merely about disseminating information; it's about creating an

environment where learning flourishes. However, the administrative tasks associated with
managing classes often become a bottleneck, hindering the smooth functioning of educational
institutions. Recognizing this challenge, our team embarked on a journey to design a holistic
solution that caters to the diverse needs of educators, students, and administrators alike.

This software project is a classes/tuition management system. It consists of all the data
management and storage facilities that are required for effectively managing a class or tuition
teaching multiple courses and subjects. It consists of multiple teachers and faculty accounts
along with their payment status. The system helps in effectively managing and scheduling
batches of students as per their courses and exam priorities. The class management system
allows the administrator to view and edit data as required. Administrator is notified of various
events . All this functionality ensures no errors and effective management of Class.

This Application uses html, css and javascript as a front-end and php and mysql as the back-end.

Objectives:

Our primary objective is to revolutionize the way classes and tuitions are managed,
leveraging technology to streamline processes and enhance productivity. Key objectives of our
project include:

1. Efficiency Enhancement: Simplifying administrative tasks such as scheduling, attendance

tracking, and resource management to optimize operational efficiency.

2. User-Centric Design: Developing an intuitive interface that caters to the unique

 requirements of educators, students, and administrators, ensuring seamless user
experience.

3. Data-driven Insights: Implementing analytics tools to derive actionable insights from

class performance data, facilitating informed decision-making.

4. Accessibility and Scalability: Creating a system that is accessible across devices and
scalable to accommodate the evolving needs of educational institutions of varying sizes.

Features:

Our Class Management System boasts a plethora of features designed to streamline every
aspect of educational administration:

1. Scheduling Module: Intuitive scheduling tools for effortless timetable creation, with
options for recurring classes, holidays, and special events.

2. Attendance Tracking: Real-time attendance tracking through biometric or digital sign-in

systems, with automated notifications for absenteeism.

3. Resource Management: Centralized management of resources such as classrooms,

equipment, and teaching materials, ensuring optimal utilization.

4. Communication Hub: Integrated communication channels for seamless interaction

between educators, students, and parents, fostering collaboration and transparency.

5. Performance Analytics: Comprehensive analytics dashboard providing insights into class

performance, student progress, and resource utilization, facilitating data-driven decision-
making.

6. Security and Privacy: Robust security measures to safeguard sensitive data, with role-
based access controls to ensure data privacy and confidentiality.

Implementation Strategy: Our implementation strategy emphasizes collaboration and iterative

development, ensuring that the system is tailored to the unique requirements of our stakeholders.
Key phases of our implementation process include:
 1. Requirement Analysis: Conducting thorough stakeholder interviews and needs
assessments to identify key requirements and pain points.

2. Prototyping and Testing: Iteratively prototyping the system based on user feedback,
ensuring usability and functionality are aligned with stakeholder expectations.

3. Deployment and Training: Seamless deployment of the system, accompanied by

comprehensive training sessions for educators, students, and administrators to facilitate
smooth transition and adoption.

4. Monitoring and Evaluation: Continuous monitoring of system performance and user

feedback, with regular evaluations to identify areas for improvement and enhancement.

Admin Module

1. Home: In this section, admin can briefly view the total new booking, approved booking,
Cancelled Booking, Total Registered users, total read enquires and total unread enquires.

2. Room Category: In this section, admin can manage category (add/delete).

3. New Room: In this section, admin can manage rooms(add/update).

4. Page: In this section, admin can manage about us and contact us pages..

5. Booking: In this section, admin can view new, approved, canceled bookings and also give a
remark.

6. Reg Users:In this section, admin can view the detail of registered users.

7. Enquiry: In this section, admin can view and maintain the enquiry.

8. Search: In this section, admin can search enquiry and booking details with the help of his/her
mobile number and booking number respectively.

9. Reports: In this section admin can view the enquiry details and check booking details in a
particular period.
Admin can also update his profile, change the password and recover the password.

Admin link:-http://localhost/hbms/admin/login.php

User Module

1. Home: It is a welcome page for users.

2. About: It is a about us page of website.

3. Services: In this section, users can view services provided by organization.

4. Room: In this section, user can view details of room which is available in the hotel.

5. Gallery: In this section, user can view gallery of hotel.

6. Book Room: In this section, user can book the hotel room by registered himself with hotels.

7. Contact: It is a contact us page where users can send the queries to hotel.

8. Sign Up: Users can register through sign uppage.

9.Login: It is login page.

10. My Account: After registration user can have their own account where he/she can update
profile, change password, recover password and view booking details of hotel room.
Features of the system:

 Admin login: Admin has an account in the system from where he

administers all the information and different faculty accounts.
 Faculty information: The system contains all the updated information of
the faculty like their personal details, salary details, lectures details and so
on.
 Scheduling classes: The system also maintains timetable of all the lectures
being conducted every day.
 Student's payment details: The system contains a student account where it
maintains the payment status of all the students in the class such as their
dues, fines, reservation category charges and so on.
 Notifications: The system regularly notifies the admin about payment dues,
faculty contract renewal, fees date, student or batch fees payment date
and other useful events.

Advantages:
 The project overcomes all the manual approach of maintaining class information on paper
by automating.
 As the system is fully automated, it does not require human efforts in calculating and
maintaining faculty and student's fees details.
 Also it maintains records of all the employees along with their salary information so there
would be systematic way of payment.
 Saves efforts and time and it is cost-effective.

Disadvantages:
 Requires large database.
 The admin has to manually keep updating the information by entering the details of the
faculty and staff in the system.
Requirement Specification

Hardware Configuration:

Client Side:

RAM 512 MB

Hard disk 10 GB

Processor 1.0 GHz

Server side:

RAM 8 GB

Hard disk 20 GB

Processor 3.00 GHz

Software Requirement:

Client Side:

Web Browser Google Chrome or any compatible browser

Operating System
Windows or any equivalent OS

5
Server Side:

Web Server APACHE

Server side Language PHP5.6 or above version

Database Server MYSQL

Web Browser Google Chrome or any compatible browser

Operating System Windows or any equivalent OS

APACHE

The Apache HTTP Server Project is an effort to develop and maintain an open-source HTTP
server for modern operating systems including UNIX and Windows. The goal of this project is to
provide a secure, efficient and extensible server that provides HTTP services in sync with the
current HTTP standards.

The Apache HTTP Server ("httpd") was launched in 1995 and it has been the most popular web
server on the Internet since April 1996. It has celebrated its 20th birthday as a project in February
2015.

PHP

• PHP stands for PHP: Hypertext Preprocessor.

• PHP is a server-side scripting language, like ASP.
• PHP scripts are executed on the server.
• PHP supports many databases (MYSQL, Informix, Oracle, Sybase, Solid, Generic
ODBC, etc.).
• PHP is an open source software .
• PHP is free to download and use.

MYSQL

• MYSQL is a database server

• MYSQL is ideal for both small and large applications
• MYSQL supports standard SQL
• MYSQL compiles on a number of platforms
• MYSQL is free to download and use
 CHAPTER 2
System Analysis

2.1. INTRODUCTION
After analyzing the requirements of the task to be performed, the next step is to analyze
the problem and understand its context. The first activity in the phase is studying the existing
system and other is to understand the requirements and domain of the new system. Both the
activities are equally important, but the first activity serves as a basis of giving the functional
specifications and then successful design of the proposed system. Understanding the properties
and requirements of a new system is more difficult and requires creative thinking and
understanding of existing running system is also difficult, improper understanding of present
system can lead diversion from solution.

2.2. ANALYSIS MODEL

The model that is basically being followed is the WATER FALL MODEL, which states
that the phases are organized in a linear order. First of all the feasibility study is done. Once that
part is over the requirement analysis and project planning begins. If system exists one and
modification and addition of new module is needed, analysis of present system can be used as
basic model

The design starts after the requirement analysis is complete and the coding begins after
the design is complete. Once the programming is completed, the testing is done. In this model
the sequence of activities performed in a software development project are:-

 Requirement Analysis
 Project Planning
 System design
 Detail design
 coding
 Unit testing
 System integration & testing
2.3 Project Analysis:
The present scenario offers manual data entry. A lot of time is wasted in creating the
reports as well as maintaining them. In case, if any query arises to get the information about the
client, the whole report is re-typed or Xeroxed. This seriously affects the authentication of the
system. This Client Management System is totally outdated and involves high risk of ambiguity
and redundancy.

Disadvantage of present system:

• Not user friendly: The present system not user friendly because data is not stored in
structure and proper format.
• Manual Control: All report calculation is done manually so there is a chance of error.
• Lots of paper work: Visitors maintain in the register so lots of paper require storing
details.
• Time consuming

2.4 SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)

Software Development Life Cycle (SDLC) is a process used by the software industry to
design, develop and test high quality software. The SDLC aims to produce a high-
quality software that meets or exceeds customer expectations, reaches completion
within times and cost estimates.

• SDLC is the acronym of Software Development Life Cycle.

• It is also called as Software Development Process.
• SDLC is a framework defining tasks performed at each step in the software
development process.
• ISO/IEC 12207 is an international standard for software life-cycle processes.
It aims to be the standard that defines all the tasks required for developing and
maintaining software. SDLC is a process followed for a software project, within a
software organization. It consists of a detailed plan describing how to develop,
 maintain, replace and alter or enhance specific software. The life cycle defines a
methodology for improving the quality of software and the overall development
process.

The following figure is a graphical representation of the various stages of a typical SDLC.

A typical Software Development Life Cycle consists of the following stages

2.4.1 STAGE 1: PLANNING AND REQUIREMENT ANALYSIS

Requirement analysis is the most important and fundamental stage in SDLC. It

is performed by the senior members of the team with inputs from the customer, the
sales department, market surveys and domain experts in the industry. This information
is then used to plan the basic project approach and to conduct product feasibility study
in the economical, operational and technical areas.

Planning for the quality assurance requirements and identification of the risks
associated with the project is also done in the planning stage. The outcome of the
technical feasibility study is to define the various technical approaches that can be
followed to implement the project successfully with minimum risks.

2.4.2 STAGE 2: DEFINING REQUIREMENTS

Once the requirement analysis is done the next step is to clearly define and
document the product requirements and get them approved from the customer or the
market analysts. This is done through an SRS (Software Requirement Specification)
document which consists of all the product requirements to be designed and developed
during the project life cycle.

2.4.3 STAGE 3: DESIGNING THE PRODUCT ARCHITECTURE

SRS is the reference for product architects to come out with the best architecture
for the product to be developed. Based on the requirements specified in SRS, usually
more than one design approach for the product architecture is proposed and
documented in a DDS - Design Document Specification.

This DDS is reviewed by all the important stakeholders and based on various
parameters as risk assessment, product robustness, design modularity, budget and time
constraints, the best design approach is selected for the product.

A design approach clearly defines all the architectural modules of the product
along with its communication and data flow representation with the external and third-
party modules (if any). The internal design of all the modules of the proposed
architecture should be clearly defined with the minutest of the details in DDS.

2.4.4 STAGE 4: BUILDING OR DEVELOPING THE PRODUCT

In this stage of SDLC the actual development starts and the product is built. The
programming code is generated as per DDS during this stage. If the design is performed
in a detailed and organized manner, code generation can be accomplished without much
hassle.

Developers must follow the coding guidelines defined by their organization and
programming tools like compilers, interpreters, debuggers, etc. are used to generate the
code. Different high-level programming languages such as C, C++, Pascal, Java and
PHP are used for coding. The programming language is chosen with respect to the type
of software being developed.

2.4.5 STAGE 5: TESTING THE PRODUCT

This stage is usually a subset of all the stages as in the modern SDLC models, the
testing activities are mostly involved in all the stages of SDLC. However, this stage refers
to the testing only stage of the product where product defects are reported, tracked, fixed
and retested, until the product reaches the quality standards defined in the SRS.

2.4.6 STAGE 6: DEPLOYMENT IN THE MARKET AND MAINTENANCE

Once the product is tested and ready to be deployed it is released formally in the
appropriate market. Sometimes product deployment happens in stages as per the
business strategy of that organization. The product may first be released in a limited
segment and tested in the real business environment (UAT- User acceptance testing).

Then based on the feedback, the product may be released as it is or with

suggested enhancements in the targeting market segment. After the product is released
in the market, its maintenance is done for the existing customer base.

2.4.7 SDLC MODELS

There are various software development life cycle models defined and designed
which are followed during the software development process. These models are also
referred as Software Development Process Models". Each process model follows a
Series of steps unique to its type to ensure success in the process of software
development.

Following are the most important and popular SDLC models followed in the industry
−

1. Waterfall Model
2. Iterative Model
3. Spiral Model
4. V-Model
5. Big Bang Model

Other related methodologies are Agile Model, RAD Model, Rapid Application
Development and Prototyping Models.
 CHAPTER 3
SYSTEM DESIGN

3.1. INTRODUCTION
 Software design sits at the technical kernel of the software engineering process and in
applied regardless of the development paradigm and area of application. Design is the first step
in the development phase for any engineered product or system. The designer's goal is to produce
a model or representation of an entity that will later be built. Beginning, once system
requirement have been specified and analyzed, system design is the first of the three technical
activities design, code and test that is required to build and verify software.

The importance can be stated with a single word "Quality". Design is the place where
quality is fostered in software development. Design provides us with representations of software
that can assess for quality. Design is the only way that we can accurately translate a customer's
view into a finished software product or system. Software design serves as a foundation for all
the software engineering steps that follow. Without a strong design we risk building an unstable
system one that will be difficult to test, one whose quality cannot be assessed until the last stage.

During design, progressive refinement of data structure, program structure, and

procedural details are developed reviewed and documented. System design can be viewed from
either technical or project management perspective. From the technical point of view, design is
comprised of four activities architectural design, data structure design, interface design and
procedural design.

3.2 Design Introduction:

Design is the first step in the development phase for any techniques and principles for the
purpose of defining a device, a process or system in sufficient detail to permit its physical
realization.

Once the software requirements have been analyzed and specified the software design
involves three technical activities - design, coding, implementation and testing that are required
to build and verify the software.

The design activities are of main importance in this phase, because in this activity, decisions
ultimately affecting the success of the software implementation and its ease of maintenance are
made. These decisions have the final bearing upon reliability and maintainability of the system.
Design is the only way to accurately translate the customer’s requirements into finished software
or a system.

Design is the place where quality is fostered in development. Software design is a process
through which requirements are translated into a representation of software. Software design is
conducted in two steps. Preliminary design is concerned with the transformation of requirements
into data

3.3 UML Diagrams:

Actor:
A coherent set of roles that users of use cases play when interacting with the use `cases.

Use case: A description of sequence of actions, including variants, that a system performs that
yields an observable result of value of an actor.

UML stands for Unified Modeling Language. UML is a language for specifying, visualizing and
documenting the system. This is the step while developing any product after analysis. The goal
from this is to produce a model of the entities involved in the project which later need to be built.
The representation of the entities that are to be used in the product being developed need to be
designed.

3.3.1 USECASE DIAGRAMS:

Use case diagrams model behavior within a system and helps the developers understand of what
the user require. The stick man represents what’s called an actor.

Use case diagram can be useful for getting an overall view of the system and clarifying who can
do and more importantly what they can’t do.

Use case diagram consists of use cases and actors and shows the interaction between the use case
and actors.

• The purpose is to show the interactions between the use case and actor.
• To represent the system requirements from user’s perspective.
• An actor could be the end-user of the system or an external system.
•
A Use case is a description of set of sequence of actions. Graphically it is rendered as an
ellipse with solid line including only its name. Use case diagram is a behavioral diagram that
shows a set of use cases and actors and their relationship. It is an association between the use
cases and actors. An actor represents a real-world object. Primary Actor – Sender, Secondary
Actor Receiver.

Sign in

Use Case Diagrams:

Admin Home

Add Room Category

Manage Room Category

(delete)
Users
Sign Up

Login

Dashboard
Class Diagram:

A description of set of objects that share the same attributes operations, relationships, and
semantics
 14

ER Diagram:

The Entity-Relationship (ER) model was originally proposed by Peter in 1976 [Chen76] as a way
to unify the network and relational database views. Simply stated the ER model is a conceptual
data model that views the real world as entities and relationships. A basic component of the
model is the Entity-Relationship diagram which is used to visually represent data objects. Since
Chen wrote his paper the model has been extended and today it is commonly used for database
design for the database designer, the utility of the ER model is:

• It maps well to the relational model. The constructs used in the ER model can easily be
transformed into relational tables.

• It is simple and easy to understand with a minimum of training. Therefore, the model can
be used by the database designer to communicate the design to the end user.

• In addition, the model can be used as a design plan by the database developer to
implement a data model in specific database management software.

ER Notation

There is no standard for representing data objects in ER diagrams. Each modeling methodology
uses its own notation. The original notation used by Chen is widely used in academics texts and
journals but rarely seen in either CASE tools or publications by non-academics. Today, there are
a number of notations used; among the more common are Bachman, crow's foot, and IDEFIX.

All notational styles represent entities as rectangular boxes and relationships as lines connecting
boxes. Each style uses a special set of symbols to represent the cardinality of a connection. The
notation used in this document is from Martin. The symbols used for the basic ER constructs are:

• Entities are represented by labeled rectangles. The label is the name of the entity. Entity
names should be singular nouns.
15
• Relationships are represented by a solid line connecting two entities. The name of the
relationship is written above the line. Relationship names should be verbs

• Attributes, when included, are listed inside the entity rectangle. Attributes which are
identifiers are underlined. Attribute names should be singular nouns.
 • Cardinality of many is represented by a line ending in a crow's foot. If the crow's foot is
omitted, the cardinality is one.

Existence is represented by placing a circle or a perpendicular bar on the line. Mandatory

existence is shown by the bar (looks like a 1) next to the entity for an instance is required.
Optional existence is shown by placing a circle next to the entity that is optional.

ER Diagram
MySQL Data Tables:
Admin Table :(Table name is admin)

This store admin personal and login details.

18

BookingTable (Table name is tblbooking)

This store the detail of room booking

Room Category Table: (Table name is tblcategory)

This store the room category detail

19
Contact Table: (Table name is tblcontact)

This table stores the data of contact person

Facility Table: (Table name is tblfacility)

This table stores the data of facility which is available by hotels.

20
Page Table: (Table name is tblpage)

This table stores the about us and contact us details of hotels.

Room Table: (Table name is tblroom)

This table stores the details of hotel rooms.

21
User Table: (Table name is tblroom)

This table stores the details of registered users.

Implementation and System Testing

After all phase have been perfectly done, the system will be implemented to the server and the
system can be used.

System Testing

The goal of the system testing process was to determine all faults in our project .
The program was subjected to a set of test inputs and many explanations were
made and based on these explanations it will be decided whether the program
behaves as expected or not. Our Project went through two levels of testing

1. Unit testing
UNIT TESTING

Unit testing is commenced when a unit has been created and effectively reviewed .In order to
test a single module we need to provide a complete environment i.e. besides the section we
would require

• The procedures belonging to other units that the unit under test calls

• Non local data structures that module accesses

• A procedure to call the functions of the unit under test with appropriate
parameters

1. Test for the admin module

• Testing admin login form-This form is used for log in of administrator of the system. In
this form we enter the username and password if both are correct administration page will
open otherwise if any of data is wrong it will get redirected back to the login page and
again ask the details

• Report Generation: admin can generate report from the main database.

INTEGRATION TESTING
In the Integration testing we test various combination of the project module by providing the
input.

The primary objective is to test the module interfaces in order to confirm that no errors are
occurring when one module invokes the other module.

EVALUATION

Project URL: http://localhost/hbms

Home Page
User Login Page

Sign Up
About Us
Contact us
29
Profile

30
Change Password
 31

View All Booking Detail

ViewSingleBookingDetail

33
Invoice

34
Book Room

35
View Rooms Detail
36

Services
37

Forgot Password
 38

Admin Login Page

How to access MySQL: http://localhost/phpmyadmin/

Dashboard
39

Admin Profile
40

Change Password
41

Add Category
42

Manage Category
43

Add Facility
44

Manage Facility
 45

Add Room
46

Manage Rooms
47
Update Room
 48

Update Room Image

 49

About Us Page
50

Contact Us
51

All Booking
 52

New Booking
View New Booking Details

53
 54

Approved Booking
View Approved Booking Details

56
Cancelled Booking

57
View Cancelled Booking Detail
 58

Registered Users
 59

Read Enquiry
 60

View Read Enquiry

 62

Unread Enquiry
63

View unread Enquiry

 64

Search Enquiry
Search Booking
Enquiry Report
Detail of Enquiry Report
Booking Report
Detail of Booking Report
Forgot Password
 FUTURE DEVELOPMENT

 Mobile Application
 Enchance Communication Features
 Gamification Elements
 AI Integration
 Quick And Responsive User Support
 CONCLUSION:

In conclusion, our Class Management System represents a paradigm shift in educational

administration, harnessing the power of technology to simplify processes, enhance
communication, and empower educators and students alike. With its user-centric design,
comprehensive features, and robust implementation strategy, we are confident that our system
will revolutionize the way classes and tuitions are managed, setting new standards for efficiency
and excellence in education.

• Automation of the entire system improves the productivity.

• It provides a friendly graphical user interface which proves to be better when
compared to the existing system.
• It gives appropriate access to the authorized users depending on their permissions.
• It effectively overcomes the delay in communications.
• Updating of information becomes so easier.
• System security, data security and reliability are the striking features.
• The System has adequate scope for modification in future if it is necessary.
 References

•https://www.w3schools.com/php/default.asp

•https://www.sitepoint.com/php/

•https://www.php.net/

•https://www.mysql.com/
•http://www.mysqltutorial.org
•https://www.apachefriends.org/download.html
•https://www.youtube.com