PROFORMA FOR THE APPROVAL PROJECT PROPOSAL

(Note: All entries of the proforma of approval should be filled up with appropriate and
complete information. Incomplete proforma of approval in any respect will be
summarily rejected.)

PNR No : …………………… Roll No: 347

1. Name of the Student

Shaikh Mohammed Zaid Abdul Khaliq
1. Title of the Project

College Enquiry Chatbots

2. Name of the Guide

Saima Shaikh

3. Teaching experience of the Guide

4. Is this your first submission? Yes No

Signature of the Student Signature of the Guide

Date: ………………… Date: …………………….

Signature of the Coordinator

Date: …………………
 College Enquiry Chatbots
A Project Report

Submitted in partial fulfillment of the

Requirements for the award of the Degree of

BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY)

By

Shaikh Mohammed Zaid

Seat No- 347

Under the esteemed guidance of

Mrs. SAIMA SHAIKH
HEAD OF IT AND CS DEPARTM ENT

DEPART M ENT OF INFORM AT IONT ECHNOLOG Y

M AHARASHTRA COLLEG E OF ARTS SCIENCE AND
COM M ERCE
(Affilia ted to U niversity of M u m ba i)
M UM BAI-M AHARASHT RA-40 0 0 11
 CERTIFICATE

This is to certify that the project entitled, "College Enquiry Chatbots", is bonafied work of Shaikh
Mohammed Zaid Abdul Khaliq bearing Seat No: 347 submitted in partial fulfillment of the
requirements for the award of degree of BACHELOR OF SCIENCE in INFORMATION
TECHNOLOGY from
University of Mumbai.

Internal Guide Coordinator

External Examiner

Date: College Seal

 ABSTRACT
A chatbot is a computer program which conducts a conversation
through auditory or textual methods. A chatbot has a information
stored in its database to identify the sentences and making a
decision itself as a response to answer to a given question. A
College enquiry chatbot will be built using algorithms that analyses
queries and understand user’s message. This will become a web
application which provides answer to the students’ questions
effectively. Students just have to put their question in the chatbot
which is used for chatting. The system will use sentence algorithms
to answer for the given question very appropriately and legibly. If
the answer is found invalid, then there is a system to declare the
answer as invalid. These invalid answers can be deleted or modified
by the administrator of the College or the system provided in the
particular College . In this chatbot we can find the information
related to the available faculty, we can also enter into the websites
of particular College we are going to search .We can also interact
with the respective faculty whom we want to and we can also
search for the results.
SR.N TITLE
1. Introduction –
1.1 Background
Objective
1.2
Purpose AndScope
1.3
Purpose
1.3.1 Scope
1.3.2 Technology Used
1.3.3
2. System Analysis–
2.1 Existing System Proposed
2.2 System Requirement
Analysis Hardware
2.3
Requirement Software
2.4 Requirement
2.5 Justification Of Selection Of Technology Gantt
2.6 Chart
2.7
3. System Design–
3.1 Module Division
Data Dictionary
3.2
ER Diagram
3.3
UsecaseDiagram
3.4 Dataflow Diagram
3.5 Activity Diagram
3.6
 4. Implementation And Testing –
4.1 Code
4.2 User Interface Desgin
4.3.1 Testing Approach
4.3.2 Unit Testing
Integration System
4.3.3
System Testing
4.3.4
5 CONCLUSION
5.1 BIBLIOGRAPHY
 INTRODUCTION
A chatbot is software that simulates human-like conversations with users via text
messages on chat. Its key task is to help users by providing answers to their
questions. This could be a text based (typed) conversation, a spoken
conversation or even a non-verbal conversation. Chat bot is typically perceived
as engaging software entity which humans can talk to. It can be interesting,
inspiring and intriguing. It appears everywhere, from old ancient HTML pages to
modern advanced social networking.
College Enquiry Chatbot uses machine learning concepts to have conversations
with humans. The purpose of developing this project is based on an intellectual
chat-bot system which will deal with the academic activities like admission
enquiry, fees structure, scholarship details, time-table of every department,
details of the documents required to attach etc. With this chat-bot system it will
be easy for the student to directly clear their queries in lesser time. Chat bots
typically provide a text-based user interface, allowing the user to type
commands and receive text in order to resolve the query. The Chatbot has
information stored in its dataset to identify the sentences and making a decision
itself as response to answer a given question. The program analyzes the user’s
query then the bot responds to the query.
1.1 Ba ck g rou nd

Intoda y' s dig ita l a g e,w here technolog y perm ea tes every a spect of ou r lives,the edu ca tiona l
sector is no exception. As the nu m ber of stu dents pu rsu ing hig her edu ca tioncontinu es to rise
g loba lly,Colleg e s a nd u niversities fa ce the cha lleng e of efficiently m a na g ing the influ x of
inqu iries from prospective stu dents. Tra ditiona lly,this process involved m a nu a lm ethods su ch
a s phone ca lls,em a ils,or in-personvisits to the a dm issionoffice. How ever,these m ethods a re
not only tim e-consu m ing bu t a lso prone to errors a nd inconsistencies.

The em erg ence of cha tbot technolog y presents a revolu tiona ry solu tion to this problem .
Cha tbots,pow ered by a rtificia l intellig ence a nd na tu ra l la ng u a g e processing a lg orithm s,ca n
eng a g e w ith u sers inrea l-tim e conversa tions,providing a ccu ra te a nd persona lized responses
to their qu eries. This technolog y ha s the potentia l to tra nsform the w a y Colleg e s ha ndle
inqu iries,m a k ing the process m ore efficient,a ccessible,a nd u ser-friendly.

Objective:
The primary objective of this project is to harness the power of chatbot technology to
develop a robust College inquiry system. By leveraging artificial intelligence and natural
language understanding capabilities, the system aims to provide prospective students with
timely and accurate information about College admissions, programs, facilities, and other
relevant details. Through seamless interaction and personalized responses, the chatbot
system aims to enhance the overall experience of prospective students and streamline the
inquiry process for College administrators.

Purpose
The purpose of the College inquiry chatbot system is multifaceted. Firstly, it aims to
automate and streamline the process of handling inquiries, reducing the reliance on manual
intervention and administrative overhead. By deploying a chatbot interface, College s can
ensure prompt and consistent responses to inquiries, regardless of the time or volume of
requests received. Additionally, the system aims to enhance the accessibility and
convenience of obtaining information about College admissions, programs, and facilities,
catering to the diverse needs of prospective students.

Scope:
The scope of the project encompasses the development of a comprehensive
chatbot system capable of addressing a wide range of inquiries related to
College admissions. This includes providing information about admission
procedures, eligibility criteria, program offerings, campus facilities,
extracurricular activities, and other relevant details. The chatbot system will
be designed to engage users in natural language conversations, understand
their queries accurately, and provide relevant responses in a timely manner.
Furthermore, the system will incorporate features such as user authentication,
data storage, analytics, and reporting to ensure seamless operation and
effective management of inquiries.

Technology Used

The development of the College inquiry chatbot system will rely on a

sophisticated technology stack comprising several key components. At its
core, the system will leverage natural language processing (NLP) algorithms
to analyze and interpret user queries in real-time. These NLP algorithms will
enable the chatbot to understand the context, intent, and semantics of user
inputs, allowing for more accurate and meaningful responses. Additionally,
the system will utilize a backend database to store and retrieve information
related to College admissions, programs, and facilities. This database will
serve as the knowledge base for the chatbot, enabling it to access relevant
information and provide timely responses to inquiries. Finally, the system will
feature a web-based interface for user interaction, allowing prospective
students to engage with the chatbot seamlessly through their preferred devices
such as smartphones, tablets, or computers. This interface will be designed
with a focus on usability, accessibility, and responsiveness, ensuring a
positive user experience for all stakeholders involved.

By harnessing the power of advanced technologies such as artificial

intelligence, natural language processing, and web development, the College
inquiry chatbot system aims to revolutionize the way inquiries are handled in
the educational sector. Through its automation, efficiency, and user-centric
design, the system has the potential to redefine the standards of customer
service and information accessibility in College admissions.
LITERATURE REVIEW:

Eliza is considered as the first Chatbot, which works on the pattern

matching system. It is developed by Joseph Weizenbaum in 1964.
ELIZA was one of the first chatterbots and one of the first programs
capable of attempting the Turing test. ELIZA's creator, Weizenbaum,
regarded the program as a method to show the superficiality of
communication between man and machine, but was surprised by the
number of individuals who attributed human-like feelings to the
computer program, including Weizenbaum’s secretary.[1]

A.L.I.C.E. (Artificial Linguistic Internet Computer Entity), also referred

to as Alicebot, or simply Alice, is a natural language processing chatterbot
—a program that engages in a conversation with a human by applying
some heuristical pattern matching rules to the human's input. It was
inspired by Weizenbaum’s classical ELIZA program. The program is
unable to pass the Turing test, as even the casual user will often expose its
mechanistic aspects in short conversations. ALICE was implemented by
Richard Wallace in 1995.[5]

Cleverbot is a chatterbot web application that uses an artificial

intelligence (AI) algorithm to have conversations with humans. It was
created by British AI scientist Rollo Carpenter. Unlike some other
chatterbot. Cleverbot's responses are not pre-programmed. Instead, it
learns from human input: Human’s type into the box below the Cleverbot
logo and the system finds all keywords or an exact phrase matching the
input. After searching through its saved conversations, it responds to the
input by finding how a human responded to that input when it was asked,
in part or in full, by Cleverbot.[2]

Kuki, formerly known as Mitsuku, is a chatbot created from Pandorabots

AIML technology by Steve Worswick. It is a five-time winner of a
Turing Test competition. Kuki claims to be an 18-year-old female
chatbot from the Metaverse. It contains all of Alice AIML files, with
many additions from user generated conversations, and is always a work
in progress.[3]

PARRY was written in 1972 by psychiatrist Kenneth Colby, then at

Stanford University. Parry is natural language program that simulates
the thinking of a paranoid individual. This program was the first to pass
the “Turing Test”.[4]
 SYSTEM ANALYSIS
Existing System

The traditional methods employed in handling College inquiries involve a manual approach, where
prospective students reach out to College s via phone calls, emails, or in-person visits to the
admission office. While these methods have served their purpose, they come with inherent
limitations.

Firstly, the manual handling of inquiries is time-consuming and resource-intensive. College staff
members are required to dedicate significant time and effort to respond to inquiries promptly, which
may result in delays and inefficiencies, especially during peak admission seasons. Moreover, the
reliance on human operators increases the likelihood of errors and inconsistencies in the information
provided to prospective students. Additionally, the manual system may struggle to cope with
fluctuations in inquiry volume, leading to delays and disruptions in service.

Proposed System

In contrast to the limitations of the existing system, the proposed College inquiry chatbot system
offers a modern and efficient solution to handle inquiries effectively. By leveraging chatbot
technology, the system provides users with a seamless and intuitive platform to interact with the
College and obtain relevant information.

The chatbot interface serves as a virtual assistant, capable of engaging users in real-time
conversations and providing accurate responses to their inquiries. Through the use of artificial
intelligence and natural language processing algorithms, the chatbot can understand the intent and
context of user queries, enabling it to deliver personalized and contextually relevant information.
This not only enhances the user experience but also ensures consistency and accuracy in the
information provided.
Moreover, the chatbot system operates 24/7, allowing users to access information at their
convenience without being restricted by office hours or time zones. This significantly improves
accessibility and responsiveness, catering to the diverse needs of prospective students from around
the world.

Requirement Analysis

Before embarking on the development of the chatbot system, it is essential to conduct a thorough
analysis of the requirements, encompassing both hardware and software components.
TOOL

Star UML

Star UML is a UML tool by MK Lab. This software is very useful to draw the diagram
like class diagram, activity diagram, and use case diagram in the project.
Features of Star UML

• Supports most of the diagrams specified in UML 2.0.

• Very rich features set and formatting options.
• Ability to generate source code from the UML diagram.
• Supported languages: Java, C, C#.
• Fast load time / execution time compared with other UML Tools.
• Supports exporting diagrams into JPG format.

Operational Feasibility

Operational feasibility for the Event Management System project is ascertained by

engaging with system users to ensure that the proposed solution aligns with their
requirements. Fortunately, there is no resistance from employees or users, as the new
system proves to be highly beneficial.
In contrast to the existing manual system, the new system is entirely computerized and
exceptionally user-friendly, enhancing the overall user experience. The success of the
proposed system relies on the collaboration between three key user roles:
Admin:
Admins possess the authority to add and remove event organizers and events.
They have the capability to oversee and manage the entire event management process,
ensuring smooth operations.

Economic Feasibility

The Constructive Cost Model (COCOMO) is a productive software cost estimation

model developed by Barry W. Boehm. The model parameter are driver from fitting a
regression formula using data from historical projects (16 projects for COCOMO 81
and 163 projects for COCOMO II).
Basic COCOMO compute software development effort (and cost) as a function of
program size.
Program size is expressed in estimated thousands of source lines of code (SLOC,
KLOC).
COCOMO applies to three classes of software projects:
• Relatively small, simple software projects.
• Small teams with good application experience work to a set of less than rigid
requirements.
• Similar to the previously developed projects.
• Relatively small and requires little innovations.
• Developed in familiar, stable environment.

While considering economic feasibility it is checked in points like performance,

information and outputs from the system. MySQL is a free software available and also
compatible foe almost all versions of windows operating system. Thus, the cost
incurred to develop the system is less and does not affect the cost to the project
development process. This justifies economic feasibility of the system.
Organic Model

C=2.4
Size=5.8 KLOC
Effort Estimate:
Effort = 2.4 * (KLOC) ^ 1.05
Effort = 2.4 * (5.8) ^ 1.05
Effort ≈ 15.1988 person-months
Chapter 3
Requirements Analysis

3.1 Problem Definition :

- Identify the need for an AI College information bot to provide reliable College information and
guidance to users.
- Recognize the limitations of traditional methods for accessing College information, such as
searching online or consulting medical professionals.
- Understand the importance of accessibility and affordability of healthcare services, particularly in
rural areas or underserved communities.
- Acknowledge the potential of AI-powered solutions to bridge the gap in healthcare accessibility
and provide instant support and information to users.
- Define the scope of the problem, including the target audience, key objectives, and expected
outcomes of implementing the AI College information bot.

Proposed Statements:

• The project aims to address the need for a reliable and accessible AI College information bot
that provides accurate health-related information to users.
• The bot will assist users in obtaining information on symptoms, conditions, treatments, and
healthy habits without offering medical diagnoses or advice.
• Emphasis will be placed on promoting user awareness about healthcare topics and connecting
users with credible resources for further information or professional assistance.
• The project seeks to bridge the gap in healthcare accessibility, particularly in rural areas, by
providing an AI-powered solution that can deliver instant and reliable information.

3.2 Requirements Specification

• Functional Requirements:
 • Natural language understanding and processing capabilities for interpreting
user queries.
• Access to a comprehensive knowledge base of College information for
providing accurate responses.
• Guidance through a symptom assessment process without offering medical
diagnoses.
• Personalized recommendations for promoting healthy habits based on user
interactions and preferences.
• Connectivity with external APIs or databases to fetch additional information
or resources.
• Non-Functional Requirements:
• Accuracy: Ensuring the bot's responses are reliable and backed by credible
sources.
• Responsiveness: Providing quick and timely responses to user queries to
enhance user experience.
• Privacy and Security: Implementing measures to protect user data and
maintain confidentiality.
• Scalability: Designing the system to handle a growing user base and
increasing query loads.
• Ethical Considerations: Incorporating disclaimers, ensuring user consent,
and avoiding biases in information dissemination
3.3 Planning and Scheduling
Planning and scheduling are distinct but inseparable aspects of managing the successful project. The process of
planning primarily deals with selecting the appropriate policies and procedures in order to achieve the objectives of
the project. Scheduling converts the project action plans for scope, time, cost and quality into an operating timetable.
The translating of the project criteria for scope, time, cost, and quality and the requirements for human resources,
communications, risk and procurement into workable
“machinery” for the project team a critical interface juncture for the project team. Taken together with the project
plan and budget, the schedule becomes the major tool for the management of projects. In addition, the integrated
cost-time schedule serves as the fundamental basis for monitoring and controlling project activity throughout its life
cycle.
3.3.1 GANTT chart
A Gantt chart, or harmonogram, is a type of bar chart that illustrates a project schedule. This chart lists the tasks to be
performed on the vertical axis, and time intervals on the horizontal axis. The width of the horizontal bars in the graph
shows the duration of each activity.
 What the various activities are
 When each activity begins and ends
 How long each activity is scheduled to last
 Where activities overlap with other activities, and by how much
 The start and end date of the whole project
3.3.2 PERT chart

A Pert chart is a project management tool used to schedule, organize, and coordinate tasks within a project. PERT
stands for program Evaluation review Technique, a methodology developed by U.S. Navy in 19540s to manage the
Polaris submarine missile program. A similar methodology, the Critical Path Method (CPM) was developed for
project management in the private sector at about the same time.
• Numbered rectangles are notes and represent events or milestones.
• Directional arrows directions indicate possible concurrent tasks.
Dotted lines indicate dependent tasks that do not require resources.
3.4 Software and Hardware Requirements

Hardware Requirements:

The hardware components required for building the AI healthcare chatbot system using python.
o RAM- minimum 4gb/Above
o Processor-minimum intel i5 core/Above
o Windows- 7/Above

Software Requirements:
The software components required for building the AI healthcare chat bot system using python language.
o Good Internet speed
o Java script enabled browser
o Programming Language Python
o Python Libraries & Packages
o Tensor flow Keras
o NLTK
o Pickle
o Algorithm – Architecture RNN - LSTM (Deep Neural Networks)
By using above all these components we will make chatbot for overall project view.
3.5 Conceptual Models

ER Diagram :

An entity relationship diagram (ERD) shows the relationships of entity sets stored in a database. An entity in this
context is a component of data. In other words, ER diagrams illustrate the logical structure of databases.
Entity:
An entity is an object in the real world that is distinguishable from other objects. Examples: The address of the
manager of the institution, a Person with unique name etc. It is often useful to identify a collection of similar entities.
Such a collection is called as “Entity set”. Note that entity set need not be disjoint.
Attributes:
An entity is described using a set of attributes. All entities in a given entity set have the same attributes; this
essentially what we mean by similar. Our choice of attributed reflects the level of detail at which we wish to
represent information in crisis. For e.g. In this case we will store the name, registry umber, the course enrolled of the
student and not his/her address or the gender.
Relationships:
A Relationship describes relations between entities. There are 4 relationships of relational database and they are:
One to One: This type of relationship is rarely seen in real world.

One to Many: It reflects business rule that one entity is associated with many number of same entity. For example,
one student can enrol for many courses, but one course will have one Student.
Many to One: It reflects business rule that many entities can be associated with just one entity. For example, Student
enrols for only one Course but a Course can have many Students.
Many to Many: For example, many students can enrol for more than one course.
Class Diagram

A class diagram is an illustration of the relationships and source code dependencies among classes in the Unified
Modelling Language (UML). In this context, a class defines the methods and variables in an object, which is a
specific entity in a program or the unit of code representing that entity. Class diagrams are useful in all forms of
object-oriented programming (OOP). The concept is several years old but has been refined as OOP modelling
paradigms have evolved.
In a class diagram, the classes are arranged in groups that share common characteristics. A class diagram resembles a
flowchart in which classes are portrayed as boxes, each box having three rectangles inside. The top rectangle contains
the name of the class; the middle rectangle contains the attributes of the class; the lower rectangle contains the
methods, also called operations, of the class. Lines, which may have arrows at one or both ends, connect the boxes.
These lines define the relationships, also called associations, between the classes.
Activity Diagram

Activity diagram is another important diagram in UML to describe the dynamic aspects of the system. Activity
diagram is basically a flowchart to represent the flow from one activity to another activity. The activity can be
described as an operation of the system.
The control flow is drawn from one operation to another. This flow can be sequential, branched, or concurrent.
Activity diagrams deal with all type of flow control by using different elements such as fork, join, etc.

Initial State or Start Point:

A small filled circle followed by an arrow represents the initial action state or the start point for any activity diagram.

Activity or Action State: An action state represents the non-interruptible action of objects.

Action Flow:

Action flows, also called edges and paths, illustrate the transitions from one action state to another. They are usually
drawn with an arrowed line.

Object Flow:
Object flow refers to the creation and modification of objects by activities. An object flow arrow from an action to an
object means that the action creates or influences the object. An object flow arrow from an object to an action
indicates that the action state uses the object.

Decisions and Branching:

A diamond represents a decision with alternate paths. When an activity requires a decision prior to moving on to the
next activity, add a diamond between the two activities. The outgoing alternates should be labeled with a condition or
guard expression. You can also label one of the paths "else."

Synchronization:
A fork node is used to split a single incoming flow into multiple concurrent flows. It is represented as a straight,
slightly thicker line in an activity diagram.
A join node joins multiple concurrent flows back into a single outgoing flow.
A fork and join mode used together are often referred to as synchronization.
Use Case Diagram

Use case diagrams are usually referred to as behavior diagrams used to describe a set of actions (use cases) that some
system or can perform in collaboration with one or more external user of the system (actors). Each use case should
provide some observable and valuable result to the actors or other stakeholders of the system.
Use case diagrams are in fact twofold - they are both behavior diagrams, because they describe behavior of the
system, and they are also structure diagrams - as a special case of class diagrams where classifiers are restricted to be
either actors or use cases related to each other with associations.
Sequence Diagram

A sequence diagram shows object interactions arranged in time sequence. It depicts the objects and classes involved
in the scenario and the sequence of messages exchanged between the objects needed to carry out the functionality of
the scenario. Sequence diagrams are typically associated with use case realizations in the Logical View of the system
under development. Sequence diagrams are sometimes called event diagrams or event scenarios.
A sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects that live
simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order in which they occur.
This allows the specification of simple runtime scenarios in a graphical manner
.
 Chapter 4
Implementation And Testing

4.1 Basic Module :

1. User Interface Module:
• Design and development of the user interface for the AI College bot application.
• Includes features such as chat window, input field for user queries, and display area for bot responses.
• Implementation of user-friendly interactions to ensure smooth communication between users and the
bot.
2. Natural Language Processing (NLP) Module:
• Utilization of NLP techniques to analyze and understand user queries.
• Processing of natural language input to extract relevant information and intents.
• Integration of NLP libraries and tools such as NLTK (Natural Language Toolkit) for text analysis and
processing.
3. Knowledge Base Module:
• Creation and maintenance of a comprehensive knowledge base containing health-related information.
• Storage of medical facts, symptoms, treatments, and other relevant data in a structured format.
• Utilization of databases or other storage mechanisms to efficiently retrieve information during user
interactions.
4. Response Generation Module:
• Generation of appropriate responses based on user queries and extracted intents.
• Implementation of algorithms to formulate relevant and accurate responses from the knowledge base.
• Incorporation of dynamic response generation techniques to handle diverse user queries effectively.
5. Security Module:
• Integration of security measures to protect user data and ensure privacy during interactions.
• Implementation of encryption techniques for sensitive information transmission.
• Compliance with data protection regulations and standards to maintain user trust and confidence.
6. Scalability and Performance Module:
• Designing the system architecture to accommodate scalability requirements and handle increasing user
loads.
• Optimization of algorithms and data structures for efficient performance and response times.
• Testing and benchmarking to ensure system reliability and performance under different usage
scenarios..
4.2 User Interface design
4.2 Code :
4.3 Code :

Index.html
{% extends "base.html" %} {% block head %}
<title>college Chatbots </title>
{% endblock head %} {% block hero %}

<section id="hero" class="hero d-flex align-items-center">

<div class="container">
<div class="row">
<div class="col-lg-6 d-flex flex-column justify-content-center">
<h1 data-aos="fade-up">What is College CHatbots </h1>
<h2 data-aos="fade-up" data-aos-delay="400" style="text-align: justify;">
The healthcare industry is continuously looking for ways to improve patient experience and outcomes.
One way to achieve this is by leveraging artificial intelligence (AI) to provide personalized recommendations and
predictions based on patients symptoms and medical history. In this project, we propose the development of a
hospital recommendation and disease prediction chatbot. The chatbot will be able to recognize symptoms and
provide personalized recommendations for hospitals based on medical needs.

</h2>
<div data-aos="fade-up" data-aos-delay="600">
<div class="text-center text-lg-start">
<a href="#about" class="btn-get-started scrollto d-inline-flex align-items-center justify-content-center
align-self-center">
<span>Get Started</span>
<i class="bi bi-arrow-right"></i>
</a>
</div>
</div>
</div>
<div class="col-lg-6 hero-img" data-aos="zoom-out" data-aos-delay="200">
<img src="{{ url_for('static',filename='custom/hero-main.png') }}" class="img-fluid" alt="">
</div>
</div>
</div>
</section>

{% endblock hero %} {% block main %}

<!-- ======= About Section ======= -->

<section id="about" class="about">

<div class="container" data-aos="fade-up">

<div class="row gx-0">
 <div class="col-lg-6 d-flex flex-column justify-content-center" data-aos="fade-up" data-aos-delay="200">
<div class="content">
<h3>BMI</h3>
<h2>The body mass index (BMI) is that the metric currently in use for outlining anthropometric height
and weight
characteristics in adults and for classifying them into groups.</h2>
<div class="text-center text-lg-start">
<a href="login" class="btn-read-more d-inline-flex align-items-center justify-content-center align-
self-center">
<span>Check BMI</span>
<i class="bi bi-arrow-right"></i>
</a>
</div>
</div>
</div>

<div class="col-lg-6 d-flex align-items-center" data-aos="zoom-out" data-aos-delay="200">

<img src="{{ url_for('static',filename='custom/about.png') }}" class="img-fluid" alt="">
</div>

</div>
</div>

</section>
<!-- End About Section -->

<!-- ======= Features Section ======= -->

<section id="features" class="features">

<div class="container" data-aos="fade-up">

<header class="section-header">
<h2>Features</h2>
<p>What makes our website unique?</p>
</header>

<div class="row">

<div class="col-lg-6">
<img src="{{ url_for('static',filename='img/features.png') }}" class="img-fluid" alt="">
</div>

<div class="col-lg-6 mt-5 mt-lg-0 d-flex">

<div class="row align-self-center gy-4">

<div class="col-md-6" data-aos="zoom-out" data-aos-delay="200">

<div class="feature-box d-flex align-items-center">
<i class="bi bi-check"></i>
<h3>Faster analysis</h3>
 </div>
</div>

<div class="col-md-6" data-aos="zoom-out" data-aos-delay="300">

<div class="feature-box d-flex align-items-center">
<i class="bi bi-check"></i>
<h3>Easy to use</h3>
</div>
</div>

<div class="col-md-6" data-aos="zoom-out" data-aos-delay="400">

<div class="feature-box d-flex align-items-center">
<i class="bi bi-check"></i>
<h3>Personalized meal plans</h3>
</div>
</div>

<div class="col-md-6" data-aos="zoom-out" data-aos-delay="500">

<div class="feature-box d-flex align-items-center">
<i class="bi bi-check"></i>
<h3>College tips</h3>
</div>
</div>

<div class="col-md-6" data-aos="zoom-out" data-aos-delay="600">

<div class="feature-box d-flex align-items-center">
<i class="bi bi-check"></i>
<h3>Easy to share</h3>
</div>
</div>

<div class="col-md-6" data-aos="zoom-out" data-aos-delay="700">

<div class="feature-box d-flex align-items-center">
<i class="bi bi-check"></i>
<h3>Accurate results</h3>
</div>
</div>

</div>
</div>

</div>
<!-- / row -->

</div>

</section>
<!-- End Features Section -->

<!-- ======= Team Section ======= -->

<section id="team" class="team">

<div class="container" data-aos="fade-up">

<header class="section-header">
<h2>Team</h2>
<p>Our hard working team</p>
</header>

<div class="row gy-4">

<div class="col-lg-4 col-md-6 d-flex align-items-stretch" data-aos="fade-up" data-aos-delay="100">

<div class="member">
<div class="member-img">
<img src="{{ url_for('static',filename='img/team/team-1.jpg') }}" class="img-fluid" alt="">
<div class="social">
<a href=""><i class="bi bi-twitter"></i></a>
<a href=""><i class="bi bi-facebook"></i></a>
<a href=""><i class="bi bi-instagram"></i></a>
<a href=""><i class="bi bi-linkedin"></i></a>
</div>
</div>
<div class="member-info">
<h4>Student Name</h4>
<span>18BCE2113</span>
</div>
</div>
</div>

<div class="col-lg-4 col-md-6 d-flex align-items-stretch" data-aos="fade-up" data-aos-delay="200">

<div class="member">
<div class="member-img">
<img src="{{ url_for('static',filename='img/team/team-2.jpg') }}" class="img-fluid" alt="">
<div class="social">
<a href=""><i class="bi bi-twitter"></i></a>
<a href=""><i class="bi bi-facebook"></i></a>
<a href=""><i class="bi bi-instagram"></i></a>
<a href=""><i class="bi bi-linkedin"></i></a>
</div>
</div>
<div class="member-info">
<h4>Student Name</h4>
<span>18BCE2517</span>
</div>
</div>
</div>

<div class="col-lg-4 col-md-6 d-flex align-items-stretch" data-aos="fade-up" data-aos-delay="300">

<div class="member">
<div class="member-img">
 <img src="{{ url_for('static',filename='img/team/team-3.jpg') }}" class="img-fluid" alt="">
<div class="social">
<a href=""><i class="bi bi-twitter"></i></a>
<a href=""><i class="bi bi-facebook"></i></a>
<a href=""><i class="bi bi-instagram"></i></a>
<a href=""><i class="bi bi-linkedin"></i></a>
</div>
</div>
<div class="member-info">
<h4>Student Name</h4>
<span>18BCE2513</span>
</div>
</div>
</div>

</div>

</div>

</section>
<!-- End Team Section -->

{% endblock main %}

Register.html

{% extends "base.html" %} {% block head %}

<title>Register | FakeFlipper</title>

<link rel="stylesheet" type="text/css" href="{{ url_for('static',filename='vendor2/bootstrap/css/bootstrap.min.css')

}}">
<link rel="stylesheet" type="text/css" href="{{ url_for('static',filename='fonts/font-awesome-4.7.0/css/font-
awesome.min.css') }}">
<link rel="stylesheet" type="text/css" href="{{ url_for('static',filename='vendor2/animate/animate.css') }}">
<link rel="stylesheet" type="text/css" href="{{ url_for('static',filename='vendor2/css-
hamburgers/hamburgers.min.css') }}">
<link rel="stylesheet" type="text/css" href="{{ url_for('static',filename='vendor2/select2/select2.min.css') }}">

<link rel="stylesheet" type="text/css" href="{{ url_for('static',filename='css/login_util.css') }}">

<link rel="stylesheet" type="text/css" href="{{ url_for('static',filename='css/login.css') }}"> {% endblock head %}
{% block main %}
<div class="limiter">
<div class="container-login100">
<div class="wrap-login100">
<div class="login100-pic js-tilt" data-tilt>
<img src="{{ url_for('static',filename='custom/img-01.png') }}" alt="IMG">
</div>

<form class="login100-form validate-form" method="POST">

<span class="login100-form-title">
 SIGN UP
</span>

<!-- USERNAME -->

<div class="wrap-input100 validate-input" data-validate="Valid username is required: ex@abc.xyz">
<input class="input100" type="text" name="uname" id="uname" placeholder="Username">
<span class="focus-input100"></span>
<span class="symbol-input100">
<i class="fa fa-envelope" aria-hidden="true"></i>
</span>
</div>

<!-- E-MAIL -->

<div class="wrap-input100 validate-input" data-validate="Valid e-mail is required">
<input class="input100" type="email" name="mail" id="mail" placeholder="E-Mail">
<span class="focus-input100"></span>
<span class="symbol-input100">
<i class="fa fa-envelope" aria-hidden="true"></i>
</span>
</div>

<!-- PASSWORD -->

<div class="wrap-input100 validate-input" data-validate="Password is required">
<input class="input100" type="password" name="passw" id="passw" placeholder="Password">
<span class="focus-input100"></span>
<span class="symbol-input100">
<i class="fa fa-lock" aria-hidden="true"></i>
</span>
</div>
<div class="container-login100-form-btn">
<button type="submit" class="login100-form-btn">
Register
</button>
</div>

<div class="text-center p-t-90">

Already Registered?
<a class="txt3" href="login">
Login here.
</a>
</div>
</form>
</div>
</div>
</div>

<script src="{{ url_for('static',filename='vendor2/jquery/jquery-3.2.1.min.js') }}"></script>

<script src="{{ url_for('static',filename='vendor2/bootstrap/js/popper.js') }}"></script>
<script src="{{ url_for('static',filename='vendor2/bootstrap/js/bootstrap.min.js') }}"></script>
<script src="{{ url_for('static',filename='vendor2/select2/select2.min.js') }}"></script>
<script src="{{ url_for('static',filename='vendor2/tilt/tilt.jquery.min.js') }}"></script>
<script>
$('.js-tilt').tilt({
scale: 1.1
})
</script>

<script src="{{ url_for('static',filename='js/login.js') }}"></script>

{% endblock main %}

Login .html

{% extends "base.html" %} {% block head %}

<title>Log In | FakeFlipper</title>

<link rel="stylesheet" type="text/css" href="{{ url_for('static',filename='vendor2/bootstrap/css/bootstrap.min.css')

}}">
<link rel="stylesheet" type="text/css" href="{{ url_for('static',filename='fonts/font-awesome-4.7.0/css/font-
awesome.min.css') }}">
<link rel="stylesheet" type="text/css" href="{{ url_for('static',filename='vendor2/animate/animate.css') }}">
<link rel="stylesheet" type="text/css" href="{{ url_for('static',filename='vendor2/css-
hamburgers/hamburgers.min.css') }}">
<link rel="stylesheet" type="text/css" href="{{ url_for('static',filename='vendor2/select2/select2.min.css') }}">

<link rel="stylesheet" type="text/css" href="{{ url_for('static',filename='css/login_util.css') }}">

<link rel="stylesheet" type="text/css" href="{{ url_for('static',filename='css/login.css') }}"> {% endblock head %}
{% block main %}
<div class="limiter">
<div class="container-login100">
<div class="wrap-login100">
<div class="login100-pic js-tilt" data-tilt>
<img src="{{ url_for('static',filename='custom/img-01.png') }}" alt="IMG">
</div>

<form class="login100-form validate-form" method="POST">

<span class="login100-form-title">
 LOG IN
</span>

<!-- USERNAME -->

<div class="wrap-input100 validate-input" data-validate="Valid email is required: ex@abc.xyz">
<input class="input100" type="text" name="uname" id="uname" placeholder="Username">
<span class="focus-input100"></span>
<span class="symbol-input100">
<i class="fa fa-envelope" aria-hidden="true"></i>
</span>
</div>

<!-- PASSWORD -->

<div class="wrap-input100 validate-input" data-validate="Password is required">
<input class="input100" type="password" name="passw" id="passw" placeholder="Password">
<span class="focus-input100"></span>
<span class="symbol-input100">
<i class="fa fa-lock" aria-hidden="true"></i>
</span>
</div>

<div class="container-login100-form-btn">
<button type="submit" class="login100-form-btn">
Login
</button>
</div>

<div class="text-center p-t-90">

Don't have an account?
<a class="txt3" href="register">
Register now.
</a>
</div>
 </form>
</div>
</div>
</div>

<script src="{{ url_for('static',filename='vendor2/jquery/jquery-3.2.1.min.js') }}"></script>

<script src="{{ url_for('static',filename='vendor2/bootstrap/js/popper.js') }}"></script>
<script src="{{ url_for('static',filename='vendor2/bootstrap/js/bootstrap.min.js') }}"></script>
<script src="{{ url_for('static',filename='vendor2/select2/select2.min.js') }}"></script>
<script src="{{ url_for('static',filename='vendor2/tilt/tilt.jquery.min.js') }}"></script>
<script>
$('.js-tilt').tilt({
scale: 1.1
})
</script>

<script src="{{ url_for('static',filename='js/login.js') }}"></script>

4.4 Security Issues :
➢ Security Question

A security question is a form of shared secret used as in authenticator. It is commonly used by banks cable companies
and wireless provider as in extra security layer. Financial institution have used questions to authenticate customers
since at least the early 20th century. In 1906 speech at a meeting of section of the American bankers’ associations,
Baltimore banker Willian m. Hayden described his institutions use of security questions as a supplement to a
customer signature record the described the signature cards used in opening new account which had spaces for the
customers birth place, residence, mother’s maiden name, occupation and age.
Due to the common place nature of social media many of the traditional security questions are no longer useful or
secured. It is important to remember that a security question is just another password. Therefore, a security question
should not be shared with anyone else or include any information readily available on social media websites, while
remaining simpler, memorable, difficult to guess, and constant over time. It is important for the user to remember the
security questions if the forgot the password. Security questions can help them to recover their account (if the user
remembers the answer they had set to their security questions.)

4.6 Test cases design

System testing is designed to uncover the weaknesses that were not found in earlier test. In the testing phase, the
program is executed with the explicit intention of finding errors. This includes forced system failures and validation
of the system, as its user in the operational environment will implement it. For this purpose, test cases are developed.
When a new system replaces the old one, such as in the present case, the organization can extract data from the old
system to test them on the new. Such data usually exist in sufficient volume to provide sample listings and they can
create a realistic environment that ensures eventual system success. Regardless of the source of test data, the
programmers and analyst will eventually conduct four different types of tests.

➢ Integration Testing

The integration is the next important concept that highlights in the testing scenario. Integration testing can be
performed in different strategies. One of them is the Big Bang testing in which one could first test all of a system’s
modules separately and then whole systems at once. But here we proceed abruptly from the module testing and the
integration testing disappears. Another alternative is the Incremental Testing.
With the Incremental testing there are many advantages. We can start the integration as soon as reasonable subsets of
modules have been developed. It is easier to localize errors incrementally. The partial aggressions of modules often
constitute important subsystems that can have autonomy with these testing. The need for stubs and drivers can be
reduced.
There are two approaches to the Incremental Testing. They include Bottom-up and Top-down aggregations. The
former means starting aggregation and testing from leaves of the module charts. The latter means starting from the
top-level modules and substitute for higher-level modules. In our project we have used the top-down approach of
incremental testing.
Top-down integration is an incremental approach to the construction of programs structure. Modules are integrated
by moving downward through the control hierarchy, beginning with the main control module that is the basic
connectivity module in our project. Test is done on each module.

➢ System Testing
The system testing deals with the process of testing the system as a whole. This is done after the integration process.
Moving through each module from top to bottom tests the entire system. The verification and validation process are
then carried out. The errors that occur the testing phase are eliminated and a well-functioning system is developed.
Test case design focuses on a set of techniques, which meets all testing objectives, which are mentioned below.

Testing is a process of executing a program with the intent of finding an error.

A successful test is one that uncovers an as yet undiscovered error.

Testing demonstrates that software functions work according to specifications. In addition data collected from testing
provides a good indication of software reliability and some indication of software quality as a whole. Testing results
in the deduction in the numbers of errors. Critical modules are tested as early as possible.
Various Testing Methods:

Unit testing focuses verification efforts on the smallest unit of the software design, the module. This is also known as
Module Testing. The modules are tested separately. This testing is carried out during programming stage itself.
 Validation Testing:
Validation testing can be defined in many ways but a simple definition is that validation succeeds when the software
functions in a manner that can be reasonably expected by the users.
After validation test has been conducted one of the two possible conditions exists

1. The function or the performance characteristics confirm to specification and are accepted.
2. A deviation from specification is uncovered and a deficiency list is created.

 Output Testing:
After performing the validation testing the next step is output testing of the proposed system since no system is useful
if it does not produce the required output in the specific format. The outputs generated or displayed by the system
under consideration are tested by asking the users about the formats required by them.
  User Acceptance Testing:
User acceptance of a system is a key factor for the success of any system. The system under consideration is tested
for user acceptance by constantly keeping in touch with prospective system users at the time development and
making changes whenever required.
 Quality Assurance Methodologies:
Quality assurance is a planned and systematic of all actions necessary to provide adequate confidence that the item or
product confirms to established technical requirements. The purpose of software quality assurance group is to
provide assurances that the procedures, tools and techniques used during product development and modification and
adequate to provide desired level of confidence in the work products. Often, software quality assurance personnel are
organizationally distinct from software development group. Preparation of a Software Quality Assurance Plan for
each software products is primary responsibility of software quality assurance group. Quality assurances personnel
are sometimes are charge of arrangements for walkthroughs, inspections and major milestones reviews.
In addition, quality assurance personnel often conduct the project post mortem, write project legacy document and
provide long term retention of the project records.
Typically, the quality assurance group will work with the development group to derive Source Code Test Plan. A test
plan for the source code specifies the objectives of testing; the test plan for source code specifies the objectives of
testing, the test completion criteria, the system integration plan, and methods to be used on particular test inputs
expected outcomes. There are four types of tests that the source code must satisfy: function tests, performance tests,
stress test and structural test.
 System verification and validation:
System verification and validation is done to check the quality of the software in simulated and live environment. A
number of different transactions are used to perform verification. Validation is the process of demonstrating that the
implemented software does satisfy the system requirements. One aspect of software validation is to statistically
analyse the program without resorting to actual execution. The system validation is done in such a way that the
system response time will not cause any hardship to the user.

Login Verification
Username admin

Password admin123

Expected Output Login Successful

Actual Output Login Successful

Remark OK

Username admin

Password MaharashtraCollege

Expected
Password Login Successful
Actual Output Login Successful

Remark Not OK
 CONCLUSION
In conclusion, the development of the AI College bot project represents a significant step forward in
leveraging technology to improve access to healthcare information and support. By harnessing the
power of artificial intelligence, natural language processing, and deep learning algorithms, this
project aims to address the growing need for reliable health-related assistance and guidance in
today's digital age.

Through the creation of an interactive chatbot interface, users can access a wealth of College
information, receive personalized recommendations, and connect with relevant resources
seamlessly. The project emphasizes the importance of user empowerment, enabling individuals to
make informed decisions about their College and well-being.

Moreover, the project underscores the ethical considerations inherent in deploying AI technologies
in the healthcare domain. By prioritizing user privacy, data security, and transparency, the AI
College bot ensures that users can trust the information and support provided by the system.

Looking ahead, the project sets the stage for ongoing learning and adaptation, with future iterations
focused on continuous improvement based on user feedback and advancements in AI and healthcare
technology. By remaining responsive to user needs and evolving trends, the AI College bot strives to
remain a valuable asset in promoting College awareness and accessibility for individuals worldwide.

In summary, the AI College bot project represents a promising endeavor to harness technology for
the betterment of healthcare, offering a glimpse into a future where personalized, reliable College
support is just a conversation away.
 BIBLIOGRAPHY
• Sophia, J. J., Kumar, D. A., Arutselvan, M., & Ram, S. B. (2020). A survey on chatbot implementation in
College care using NLTK. Int. J. Comput. Sci. Mob. Comput,
• Hwang, T. H., Lee, J., Hyun, S. M., & Lee, K. (2020, October). Implementation of interactive healthcare
advisor model using chatbot and visualization. In 2020
• International Conference on Information and Communication Technology Convergence (ICTC) (pp. 452-
455). IEEE
• Sivaraj, K., Jeyabalasuntharam, K., Ganeshan, H., Nagendran, K., Alosious, J., & Tharmaseelan, J. Medibot:
End to end voice based AI medical chatbot with a smart watch.
• Madhu, D., Jain, C. N., Sebastain, E., Shaji, S., & Ajayakumar, A. (2017, March). A novel approach for
medical assistance using trained chatbot. In 2017 international conference on inventive communication and
computational technologies (ICICCT) (pp. 243-246). IEEE.