1

Online Result Management System

A project report submitted to

Rajiv Gandhi Proudyogiki Vishwavidhyalaya, Bhopal

in partial fulfilment for the award of the degree of

Bachelor of Engineering

in

Information Technology

PROJECT GUIDE SUBMITTED BY

Ms. Namrata Bhatt Hriday Kagalkar(0829IT201016)

DEPARTMENT OF INFORMATION TECHNOLOGY

SUSHILA DEVI BANSAL COLLEGE OF TECHNOLOGY
INDORE- 453331
Jul-Dec 2022
2

Online Result Management System

A project report submitted to

Rajiv Gandhi Proudyogiki Vishwavidhyalaya, Bhopal

in partial fulfilment for the award of the degree of

Bachelor of Engineering

in

Information Technology

PROJECT GUIDE SUBMITTED BY

Ms. Namrata Bhatt Hriday Kagalkar(0829IT201016)

DEPARTMENT OF INFORMATION TECHNOLOGY

SUSHILA DEVI BANSAL COLLEGE OF TECHNOLOGY
INDORE- 453331
Jul-Dec 2022
3

ACKNOWLEDGEMENT

Words are poor to substitute to express ones feeling adequately when delighted with emotion.
First, we would like to convey us gratitude our honourable Director P. S. Chauhan Sir and
our HOD, Prof. Namrata Bhatt for their valuable time and guidance. We would like to convey
our regards & thanks to our coordinator and project guide Prof. Namrata Bhatt for guiding
and supporting us throughout the project.

Hriday Kagalkar (0829IT201016)

4

SUSHILA DEVI BANSAL COLLEGE OF TECHNOLOGY

INDORE, 453331

CERTIFICATE

This is to certify that HRIDAY KAGALKAR (0829IT201016) have completed

their project work, titled “ONLINE RESULT MANAGEMENT SYSTEM” as
per the syllabus and have submitted a satisfactory report on this project as a part
of fulfilment towards the degree of “BACHELOR OF TECHNOLOGY”
(Information Technology) from RAJIV GANDHI PROUDYOGIKI
VISHWAVIDHYALAYA, BHOPAL.

HEAD OF THE DEPARTMENT PROJECT GUIDE

DIRECTOR
5

SUSHILA DEVI BANSAL COLLEGE OF TECHNOLOGY

INDORE, 453331

CERTIFICATE

This is to certify that HRIDAY KAGALKAR (0829IT201016) have completed

their project work, titled “ONLINE RESULT MANAGEMENT SYSTEM” as
per the syllabus and have submitted a satisfactory report on this project as a part
of fulfilment towards the degree of “BACHELOR OF TECHNOLOGY”
(Information Technology) from RAJIV GANDHI PROUDYOGIKI
VISHWAVIDHYALAYA, BHOPAL.

INTERNAL EXAMINER EXTERNAL EXAMINER

6

TABLE OF CONTENTS
TITLE PAGE NO.

ABSTRACT 9
LIST OF TABLES 10
LIST OF FIGURES 11

1. Introduction
1.1. Purpose of the project
1.2. Scope
1.3. Problem in existing system
1.4. Statement of Problem

2. System Requirement Analysis

2.1 Introduction
2.1.1 Purpose of SRS
2.1.2 Intended Audience and Reading Suggestions
2.1.3 Product Scope
2.2 Overall Description
2.2.1 Product Perspective
2.2.2 Product Functions
2.2.3 User Classes and Characteristics
2.2.4 Operating Environment
2.3 External Interface Requirements
2.3.1 User Interfaces
2.3.2 Hardware Interfaces
2.3.3 Software Interfaces
2.3.4 Communications Interfaces
2.4 Functional Requirement (description of product functions)
2.4.1 System Feature 1
2.4.2 System Feature 2 (and so on)
2.5 Non - functional Requirements (any two)
7

2.5.1 Performance Requirements

2.5.2 Safety Requirements
2.5.3 Security Requirements
2.5.4 Availability Requirements
2.6 Project Plan
2.6.1 Team Members
2.6.2 Division of Work
2.6.3 Time Schedule (Show with the help of gantt chart)

3. Analysis
3.1 Methodology Used ( Object Oriented)
3.2 Use Case Diagrams (Also include use case specifications)
3.3 Activity Diagram
3.4 Sequence Diagram
3.5 Class Diagram (Description of Identified Classes, Identified Attributes, Identified
Methods, Identified Relationships)

4. Design
4.1 Architectural Design
4.1.1. System Architecture Diagram
4.1.2. Description Of Architectural Design
4.2 Database Design
4.2.1. Normalization
4.3 Interface Design
4.3.1. Screenshots

5. Implementation
5.1 Language and database system used for the implementation
5.2 Features of language and database used for the project
5.3 Description of third party tools used (If any)
8

6. Testing (Theory of testing is not required. Only write how u have tested the system)
6.1 White Box Testing (Basis path testing) Test Case-n i. Purpose ii. Inputs iii. Expected
Outputs & Actual Outputs
6.2 Black Box Testing
6.2.1 Interface testing

7. Conclusion

8. Reference (include references of the project in IEEE format)

9

 ABSTRACT.
As the word “Online” means required Internet connection to access & avail
these web services. Web Application allows to control & manage information
from anywhere in the World by using Internet. As we know that Internet is the
second largest network in the World having millions of devices connected &
sharing information. The proposed system is based on Client-Server
Architecture where Server Application is designed using latest technologies like
PHP & MySQL with Apache Server. This Web Application will help students
& teachers reducing efforts & saves time. After all it will be a smart application
to make things better.
10

 LIST OF TABLES
S. No Content Page No.
1. Use Case Diagram 17
2. Use Case Specification 18 - 20
3. Activity Diagram 21
4. Faculty Registration 22
Sequence Diagram
5. Faculty Login Sequence 22
Diagram
6. Add Subjects Sequence 23
Diagram
7. Add Marks Sequence 23
Diagram
8. Change Password Sequence 24
Diagram
9. View Users Sequence 24
Diagram
10. Delete Records Sequence 25
Diagram
11. Student Registration 25
Sequence Diagram
12. View Result Sequence 25
Diagram
13. Class Diagram 26 - 27
14. ER Diagram 28
15. Architectural Diagram 29
11

Chapter 1 - Introduction
1.1. Purpose of the project
The Online Exam Result System is a management information system for education
establishments to manage student data & their results. Online Exam Result provide
capabilities for generating particular result for exam and generate the report automatically,
build student details, student-related data needs in a college. Using the latest PHP technology
completely built in HTML, CSS, PHP & MySQL our system is a complete result
management and staff interaction system with built-in features proofing that easily supports
Integration with the latest student exam result system providers. A Online Exam Result
System is an automatic result generation system that provides the proper result to the students
as well as parents as per the tags like Good, Better & Best. Download Student Exam Result
Report online. The provision may as well have a database of survey which can be given to the
understudies following a secured. In the existing system teachers need to process result
manually. By this process teachers can update marks in online system without wasting time
in writing. This system is designed to be simple to use, simple to understand and easy to
implement and configure to fit. After successful entry of marks in respective subjects of
students, the percentage will automatically processed & stored permanently.

1.2. Scope
I have developed Online Result System to provide results in an easy way. This is the main
disadvantage of the existing system for giving results about the student’s exam and viewing
report of students manually. Student Performance Result on exams is an essential element in
quality assurance. Here we aimed to design online web application for issuing the exam
resultsof students, this is named as Online Exam Result System. Online Report Card
generation will be easy for students. They just need to enter their roll no. or enrolment no. in
order to see their results. Since they are the best tool, we currently have for collecting
objective, detailed and reasonably systematic information, which Informs the parents about
student’s performance in terms of percentage. Online Exam Result provide result in an easy
and quick manner. Results are stored in MySQL database.
12

1.3. Problem in existing system

System Analysis is a detailed study of the various operations performed by a system and their
relationships within and outside of the system. Here the key question iswhat all problems
exist in the present system? What must be done to solve the problem? Analysis begins when a
user or manager begins a study of the program using existing system. During analysis, data
collected on the various files, decision points and transactions handled by the present system.
Training, experience and common sense are required for collection of relevant information
needed to develop the system. The success of the system depends largely on how clearly the
problem is defined, thoroughly investigated and properly carried out through the choice of
solution. A good analysis model should provide not only the mechanisms of problem
understanding but also the frame work of the solution. Thus, it should be studied thoroughly
by collecting data about the system. Then the proposed system should be analysed thoroughly
in accordance with the needs. System analysis can be categorized into four parts:

 Paper Work
 Manual processing of student results
 Time taking work to analyze results
 No digital platform
13

Chapter 2 - System Requirement Analysis

2.1. Introduction
2.1.1. Purpose of SRS
This document is the software requirement specification (SRS) for the Online Result
Management System for any institution. The purpose of this document is to describe the
functional and non-functional requirement, and general interface of the online result
management system.
2.1.2. Intended Audience and Reading Suggestions
The intended audience for this Online Result Management System document is the internal
guides of the organization. Further modifications and reviewing will be done by the
organization and deliver a last version. The last version of this document is reviewed by the
Internal Guides and Head of the Department of the college.
2.1.3. Project Scope
Our Online Result Management System can be used in any institution.

2.2. Overall Description

2.2.1. Product Perspective
The proposed Online Result management System is an on-line system.

2.2.2. Product Function

 System Actors (Users)
 Teacher/Faculty
 Student
 Teacher/Faculty Features
 Faculty Registration
 Faculty Login
 Faculty can add subjects
 Faculty can submit marks
 Faculty can view registered users
 Faculty can change password
 Faculty can logout
14

 Student Features
 Student Registration
 Enter Roll No.
 View Result
 Exit

2.2.3. User Classes and Characteristics

The user class for this project is the students and faculties of the particular organization.
2.2.4. Operating Environment · Hardware requirement: -
• Processor: 1 GHz processor
• RAM: 1 GB (Minimum)
• Hard Disk: 20 GB (Minimum)
• Monitor
• Keyboard.
Software requirement: - On the client side the required software product is Internet explorer
supporting at least Wamp server enabled, MY SQL 8.0 and any operating system that can run
the browsers.

2.3. External Interface Requirements

2.3.1. User Interfaces
The Online Result Management System is a web application must supply a user interface.
The interfaces will involve check boxes, combo boxes, text boxes and radio buttons. The
combo boxes and the radio buttons will be prevented user from entering wrong type of
information. They will also enable fast data entry. Text boxes will be controlled for avoiding
invalid and inconsistent data.

2.3.2. Hardware Interfaces

No external hardware is required.
2.3.3. Software Interfaces
No external software is required.

2.3.4. Communication Interfaces

This project is a Web application so it supports on all type of browsers.
15

2.4. Functional Requirement (Description of product functions)

2.4.1. System Feature
 Faculty Registration
 Faculty Login
 Faculty can add subjects
 Faculty can submit marks
 Faculty can view registered users
 Faculty can change password
 Faculty can logout
 Student Registration
 Enter Roll No.
 View Result
 Exit

2.5. Non – functional Requirements

Non - functional Requirements (NFRs) define system attributes that serve as constraints or
restrictions on the design of the system across the different backlogs.
2.5.1. Safety Requirements
By incorporating a robust and proven MYSQL into the system, reliable performance and
integrity of data is ensured.
2.5.2. Security Requirements
There shall be a strong security mechanism should be place in the server side of the system to
keep unwanted users to hack or damage the system. However, all users of the system give
and store the details of privacy related to personal information and many other. However, our
system can be accessed online so we need very secured system as far as security is
concerned.
16

2.6. Project plan

2.6.1. Team Members
I am the only one in my team: Hriday Kagalkar
2.6.2. Division of Work
• Information gathering: Hriday Kagalkar
• Information analysis: Hriday Kagalkar
• Project Planning and description: Hriday Kagalkar
• Functional and Non-Functional requirement: Hriday Kagalkar
• Analysis and Design: Hriday Kagalkar
• Implementation: Hriday Kagalkar
• Testing: Hriday Kagalkar
17

Chapter 3 - Analysis
3.1. Methodology Used (Object Oriented)
The object-oriented programming is basically a computer programming design philosophy or
methodology that organizes/ models software design around data, or objects rather than
functions and logic.
An object is referred to as a data field that has unique attributes and behavior. Everything in
OOP is grouped as self-sustainable objects.
It is the most popular programming model among developers. It is well suited for programs
that are large, complex, and actively updated or maintained.
The major concepts of object-oriented programming are:
• Abstraction
• Encapsulation
• Inheritance
• Polymorphism

3.2. Use Case Diagram

18

Use Case Specification:-

 For Faculty
Registration
Brief Faculty needs to enter his / her details to use the system
Description:
Primary Actor : Faculty
Pre - Condition : As he opens the application for the first time
Post - Condition Faculty will move to Faculty login page
Primary Flow : As he registered his detail, he will move to login page
Alternate Flow : If he left any required field empty, he would never proceed to the next
page.

Login
Brief Faculty needs to enter the Name and password to login into the system.
Description:
Primary Actor : Faculty
Pre - Condition : After registration or open the application (if he/she already registered)
then he can login to the system.
Post - Condition Faculty will move to Faculty Home page.
Primary Flow : If username and password are valid, then he will proceed to Home via
Login button
Alternate Flow : If he left any required field empty, he would never proceed to the next
page.

Add Subjects
Brief Faculty needs to enter the subjects
Description:
Primary Actor : Faculty
Pre - Condition : Faculty is on Faculty Home page.
Post - Condition Faculty will move to Enter Subjects page.
Primary Flow : The faculty add the name of the subjects that gets added in the records
Alternate Flow : None.

Submit Marks
Brief Faculty needs to enter the marks of the respective subjects of the given
Description: roll number
Primary Actor : Faculty
Pre - Condition : Faculty is on Faculty Home page.
Post - Condition Faculty will move to Enter Marks Page.
Primary Flow : The marks will be entered to the respective subjects for a given roll
19

number.
Alternate Flow : None.

View Records
Brief Faculty can access the student details and can make changes in it.
Description:
Primary Actor : Faculty
Pre - Condition : Faculty is on faculty home page.
Post - Condition Faculty will move to View Records Page.
Primary Flow : Faculty can view the student records.
Alternate Flow : None.

Change Password
Brief Faculty can change its current password
Description:
Primary Actor : Faculty
Pre - Condition : Faculty is on faculty home page.
Post - Condition Faculty will move to Change Password page
Primary Flow : Faculty can update its current password
Alternate Flow : None.

Delete Records
Brief Faculty can delete the students details if entered wrong mistakenly.
Description:
Primary Actor : Faculty
Pre - Condition : Faculty is on Home Page.
Post - Condition Faculty will move to View Records Page.
Primary Flow : Faculty can delete the students details if entered wrong mistakenly.
Alternate Flow : If he does not want to delete details he can close the window.
20

 For Student
Registration
Brief Student needs to enter his / her details to use the system
Description:
Primary Actor : Student
Pre - Condition : As he opens the application for the first time
Post - Condition Student will move to View Result (login) page
Primary Flow : As he registered his detail, he will move to view result (login) page
Alternate Flow : If he left any required field empty, he would never proceed to the next
page.

View Result
Brief Student needs to enter his roll number to view results
Description:
Primary Actor : Student
Pre - Condition : As he opens the application for the first time
Post - Condition Student will move to View Result page
Primary Flow : As student enter his roll number his detailed result of all subject will be
displayed.
Alternate Flow : If he left any required field empty, he would never proceed to the next
page.
21

3.3. Activity Diagram :

22

3.4. Sequence Diagram

1. Faculty Registration Sequence Diagram

23

2. Faculty Login Sequence Diagram

3. Add Subject Sequence Diagram (Faculty)

4. Add Marks sequence diagram (Faculty)

24

5. Change Password sequence diagram (Faculty)

6. View Users sequence diagram (Faculty)

25

7. Delete Records sequence diagram

8. Student Registration sequence diagram

26

9. View Result sequence diagram (Student)

3.5. Class Diagram

27
28
29

3.5. E.R. Diagram

 Faculty ER – Diagram

 Student ER – Diagram
30

Chapter 4 - Design
4.1. Architectural Design
4.1.1. System Architecture Diagram:

4.1.2 Description of architecture design

A system architecture is the conceptual model that defines the structure, behaviour, and more
views of a system. An architecture description is a formal description and representation of a
system, organized in a way that supports reasoning about the structures and behaviours of the
system. A system architecture can consist of system components and the sub-systems
developed, that will work together to implement the overall system. There have been efforts
to formalize languages to describe system architecture, collectively these are called
architecture description language.

4.2. Database Design

4.2.1. Normalization is the process of organizing data in a database. This includes creating
tables and establishing relationships between those tables according to rules designed both to
protect the data and to make the database more flexible by eliminating redundancy and
inconsistent dependency.
31

4.2.2. Database Screenshot

4.3. Interface Design

4.3.1. Screenshots
 Screenshot – 1 : View Result
32

 Screenshot – 2 : Result Display

 Screenshot – 3 : Student Registration

33

 Screenshot – 4 : Faculty/Teacher Registration

 Screenshot – 5 : Faculty Login

34

 Screenshot – 6 : Faculty Home Page

 Screenshot – 7 : Add Subjects

35

 Screenshot – 8 : View Users/Students

 Screenshot – 9 : Submit Marks

36

 Screenshot – 10 : Change Password

37

Chapter 5 - Implementation

5.1.Language and database system used for the implementation

 Software Used
 Apache HTTP Server 2
 PHP 5.6
 MySQL 5
 WAMP Server
 Implementation Tools
 Sublime Text Editor 3
 Front End
 HTML& CSS
 Back End
 PHP& MySQL

5.2. Features of language and database used for the project

PHP
PHP is a server-side scripting language designed for web development but also used
as a general-purpose programming language. Originally created by Rasmus Lerdorf in 1994,
the PHP reference implementation is now produced by The PHP Group. PHP originally stood
for Personal Home Page, but it now stands for the recursive backronym PHP: Hypertext
Preprocessor.
PHP code may be embedded into HTML code, or it can be used in combination with
various web template systems, web content management system and web frameworks. PHP
code is usually processed by a PHP interpreter implemented as a module in the web server or
as a Common Gateway Interface (CGI) executable. The web server combines the results of
the interpreted and executed PHP code, which may be any type of data, including images,
with the generated web page. PHP code may also be executed with a command-line interface
(CLI) and can be used to implement standalone graphical applications.
The standard PHP interpreter, powered by the Zend Engine, is free software released
under the PHP License. PHP has been widely ported and can be deployed on most web
servers on almost every operating system and platform, free of charge.
38

The PHP language evolved without a written formal specification or standard until
2014, leaving the canonical PHP interpreter as a de facto standard. Since 2014 work has gone
on to create a formal PHP specification.

MySQL
MySQL (officially pronounced as /maɪ ˌɛskjuːˈɛl/ "My S-Q-L", is an open-source
relational database management system (RDBMS); in July 2013, it was the world's second
most[a] widely used RDBMS, and the most widely used open-source client–server model
RDBMS.[9] It is named after Michael Widenius' (who is a co-founder of MySQL) daughter,
My, while "SQL" stands as the abbreviation for Structured Query Language. The MySQL
development project has made its source code available under the terms of the GNU General
Public License, as well as under a variety of proprietary agreements. MySQL was owned and
sponsored by a single for-profit firm, the Swedish company MySQL AB, now owned by
Oracle Corporation. For proprietary use, several paid editions are available, and offer
additional functionality.
MySQL is a popular choice of database for use in web applications, and is a central
component of the widely used LAMP open-source web application software stack (and other
"AMP" stacks). LAMP is an acronym for "Linux, Apache, MySQL, Perl/PHP/Python". Free-
software open-source projects that require a full-featured database management system often
use MySQL. Applications that use the MySQL database include: TYPO3, MODx, Joomla,
WordPress, phpBB, MyBB, Drupal and other software. MySQL is also used in many high-
profile, large-scale websites, including Google (though not for searches), Facebook, Twitter,
Flickr, and YouTube.
On all platforms except Windows, MySQL ships with no GUI tools to administer
MySQL databases or manage data contained within the databases. Users may use the
included command line tools, or install MySQL Workbench via a separate download. Many
third party GUI tools are also available.

HTML
HyperText Markup Language, commonly abbreviated as HTML, is the standard
markup language used to create web pages. Along with CSS, and JavaScript, HTML is a
cornerstone technology used to create web pages, as well as to create user interfaces for
mobile and web applications. Web browsers can read HTML files and render them into
visible or audible web pages. HTML describes the structure of a website semantically and,
39

before the advent of Cascading Style Sheets (CSS), included cues for the presentation or
appearance of the document (web page), making it a markup language, rather than a
programming language.
HTML elements form the building blocks of HTML pages. HTML allows images and
other objects to be embedded and it can be used to create interactive forms. It provides a
means to create structured documents by denoting structural semantics for text such as
headings, paragraphs, lists, links, quotes and other items. HTML elements are delineated by
tags, written using angle brackets. Tags such as <img /> and <input /> introduce content into
the page directly. Others such as <p>...</p> surround and provide information about
document text and may include other tags as sub-elements. Browsers do not display the
HTML tags, but use them to interpret the content of the page.
HTML can embed scripts written in languages such as JavaScript which affect the
behavior of HTML web pages. HTML markup can also refer the browser to Cascading Style
Sheets (CSS) to define the look and layout of text and other material. The World Wide Web
Consortium (W3C), maintainer of both the HTML and the CSS standards, has encouraged the
use of CSS over explicit presentational HTML since 1997.

CSS

Cascading Style Sheets (CSS) is a style sheet language used for describing the presentation of
a document written in a markup language such as HTML or XML (including XML dialects
such as SVG, MathML or XHTML). CSS is a cornerstone technology of the World Wide
Web, alongside HTML and JavaScript.

CSS is designed to enable the separation of content and presentation, including layout, colors,
and fonts. This separation can improve content accessibility; provide more flexibility and
control in the specification of presentation characteristics; enable multiple web pages to share
formatting by specifying the relevant CSS in a separate .css file, which reduces complexity
and repetition in the structural content; and enable the .css file to be cached to improve the
page load speed between the pages that share the file and its formatting.

Separation of formatting and content also makes it feasible to present the same markup page
in different styles for different rendering methods, such as on-screen, in print, by voice (via
speech-based browser or screen reader), and on Braille-based tactile devices. CSS also has
rules for alternate formatting if the content is accessed on a mobile device.
40

APACHE HTTP SERVER

The Apache HTTP Server, colloquially called Apache (/əˈpætʃiː/ ə-PA-chee), is the
world's most used web server software. Originally based on the NCSA HTTPd server,
development of Apache began in early 1995 after work on the NCSA code stalled. Apache
played a key role in the initial growth of the World Wide Web, quickly overtaking NCSA
HTTPd as the dominant HTTP server, and has remained most popular since April 1996. In
2009, it became the first web server software to serve more than 100 million websites.
Apache is developed and maintained by an open community of developers under the
auspices of the Apache Software Foundation. Most commonly used on a Unix-like system
(usually Linux), the software is available for a wide variety of operating systems besides
Unix, including eComStation, Microsoft Windows, NetWare, OpenVMS, OS/2, and TPF.
Released under the Apache License, Apache is free and open-source software.
As of November 2015, Apache was estimated to serve 50% of all active websites and
37% of the top servers across all domains.
41

Chapter 6 - Testing
6.1.White Box Testing
White box testing is a testing technique, that examines the program structure and derives test
data from the program logic/code. The other names of glass box testing are clear box testing,
open box testing, logic driven testing or path driven testing or structural testing.
White Box Testing Techniques:
• Statement Coverage - This technique is aimed at exercising all programming statements
with minimal tests.
• Branch Coverage - This technique is running a series of tests to ensure that all branches are
tested at least once.
• Path Coverage - This technique corresponds to testing all possible paths which means that
each statement and branch is covered.

6.2. Black Box Testing

Black Box Testing is a software testing method in which the functionalities of software
applications are tested without having knowledge of internal code structure, implementation
details and internal paths.
Black Box Testing mainly focuses on input and output of software applications and it is
entirely based on software requirements and specifications. It is also known as Behavioural
Testing.
There are many types of Black Box Testing but the following are the prominent ones –
• Functional testing – This black box testing type is related to the functional requirements of
a system; it is done by software testers.
• Non-functional testing – This type of black box testing is not related to testing of specific
functionality, but non-functional requirements such as performance, scalability, usability.
• Regression testing – Regression Testing is done after code fixes, upgrades or any other
system maintenance to check the new code has not affected the existing code.
42

Chapter 7- Conclusion
With Online Result Management System it helps most institutions to increase efficiency on
information as reducing man power, paperwork and manual activities subsequently improve
productivity. Faculties can efficiently keep a track record of the marks of the students. And
Students can easily view their marks. It saves time. With this computerized system, people
which have multiple skills can be used more efficiently.

Chapter 8 - Reference
➢Google for problem solving

➢https://www.stackoverflow.com

➢https://www.geeksforgeeks.com

➢https://www.youtube.com

➢https://www.javatpoint.com