1bg19cs021 Chocolate Ordering Bhavana Converted by Abcdpdf

VISVESVARAYA TECHNOLOGICAL UNIVERSITY
JNANASANGAMA, BELAGAVI - 590018
Mini Project
Report On
CHOCOLATE ORDERING
MANAGEMENT SYSTEM
Submitted in partial fulfillment for the award of degree of
Bachelor of Engineering
In
Computer Science and Engineering
Submitted by
BHAVANA V
(1BG19CS021)
VidyayaAmruthamAshnuthe
B.N.M. Institute of Technology

(Approved by AICTE, Affiliated to VTU, Accredited as grade A Institution by NAAC)
All UG branches – CSE,ECE,ISE & Mech.E. accredited by NBA for academic years 2018-19 to 2020-21 & validupto30.06.2021
Post box no. 7087, 27th cross, 12th Main, Banashankari 2nd Stage, Bengaluru-560070, INDIA
Ph: 91-80- 26711780/81/82 Email: principal@bnmit.in, www. bnmit.org
Department of Computer Science and Engineering

2021-22
B.N.M. Institute of Technology
(Approved by AICTE, Affiliated to VTU, Accredited as grade A Institution by NAAC)
All UG branches – CSE ,ECE, ISE & Mech. E. accredited by NBA for academic years 2018-19 to 2020-21 & valid upto
30.06.2021
Post box no. 7087, 27th cross, 12th Main, Banashankari 2nd Stage, Bengaluru-560070, INDIA
Ph: 91-80- 26711780/81/82 Email: principal@bnmit.in, www. bnmit.org
Department of Computer Science and Engineering
VidyayaAmruthamAshnuthe
CERTIFICATE
Certified that the Mini Project entitled CHOCOLATE ORDERING MANAGEMENT

SYSTEM carried out by Ms. Bhavana V USN 1BG19CS021 a bonafide student of V
Semester B.E., B.N.M Institute of Technology in partial fulfillment for the Bachelor of
Engineering in COMPUTER SCIENCE AND ENGINEERING of the Visvesvaraya
Technological University, Belagavi during the year 2021-2022. It is certified that all
corrections / suggestions indicated for Internal Assessment have been incorporated in the
report. The Project report has been approved as it satisfies the academic requirements in
respect of Database Management System with Mini Project Laboratory prescribed for the
said Degree.
Dr. Sreevidya RC Dr. Sahana D. Gowda

Assistant Professor & Lab-Incharge Professor & HOD
Department of CSE Department of BNMIT,
BNMIT, Bengaluru BNMIT, Bengaluru
Name & Signature
Examiner 1:
Examiner 2:
ABSTRACT
The entitled project “CHOCOLATES ORDERING MANAGEMENT SYSTEM” is
made keeping in mindall the aspects of the chocolates. The system allows only registered
users to login and newusers are allowed to register on the application. The system allows
the users to login and buy a chocolates from other the website and view the chocolates.
The user is also given a choice of making the payment in online or cash on delivery. The
software is very easy to use and it is very beneficial to those peoplewho don’t have
time to go and purchase offline and to get things done in a faster way, as this system
helps the users to compare the details of the chocolates, it gives a clarity to them to make
a best choice out of all the choices available. Since all the work that is to be done by this
software can also be done manually, but this consumes time, man power and energy. So,
this software will be a relief to those who want to save time and energy.
I
ACKNOWLEDGEMENT
The success and final outcome of the entitled project “Chocolate ordering Management
System” required a lot of guidance and assistance from many people and I am extremely
privileged to have got this all along the completion of my project.
I would like to thank Shri. Narayan Rao R Maanay, Secretary, BNMIT, Bengaluru for
providing excellent academic environment in the college.
I would like to sincerely thank Prof. T J Rama Murthy, Director, BNMIT, Bengaluru
for having extended his support and encouragement during the course of the work.
I would like to express my gratitude to Prof. Eishwar N Maanay, Dean, BNMIT,

Bengaluru for his relentless support, guidance and assistance.
I would like to thank Dr. Krishnamurthy G N, Principal, BNMIT, Bengaluru for his
constant encouragement.
I would like to thank, Dr. Sahana D Gowda, Professor and Head of the Department of
Computer Science and Engineering who has shared her opinions and thoughts which
helped me in giving my presentation successfully.
I extend my heartfelt gratitude to Dr. Sreevidya RC, Assistant Professor in the

Department ofComputer Science and Engineering, BNMIT, Bengaluru, for completion of
the project.
Finally, I would like to thank all the faculty members of Department of

ComputerScience and Engineering, BNMIT, Bengaluru, for their support. I would like to
thank myfamily and friends for their unfailing moral support and encouragement.
II
BHAVANA V
1BG19CS021
II
TABLE OF CONTENTS
Page no.
CONTENT
ABSTRACT I
ACKNOWLDEGEMENT II
1. INTRODUCTION 1
1.1 Overview of Database Management Systems 1

1.2 Problem statement 2
1.3 Objectives 2
1.4 Dataset Description 3
2. SYSTEM REQUIREMENTS 4
2.1 Software 4
2.2 Hardware 4
3. SYSTEM DESIGN 5
3.1 E R Diagram 5
3.2 Schema Diagram 7
3.3 Overview of GUI 8
3.4 Normalization 10
4. IMPLEMENTATION 12
4.1 Table creation 12

4.2 Description of Table 16
4.3 Populated Tables 19
4.4 SQL Triggers & Stored Procedures 23
4.5 Database connectivity 26
5. RESULTS 27
6. MODULES
CONCLUSION 39
FUTURE ENHANCEMENTS 40
Figure no. Figure name page No
3.1 E R diagram of Chocolate ordering Management System 6
3.2 Schema diagram of Chocolate ordering Management System 7
4.1 customer description 16
4.2 contact table description 16
4.3 chocolate table description 17
4.4 manager table description 17
4.5 order table description 18
4.6 restaurant(outlet) table description 18
4.7 customer Data 19
4.8 contact data 19
4.9 chocolate data 21
4.10 manager Data 21
4.11 Restaurant data 22
4.12 triggers 23
4.13 stored procedure 24
5.1 Home page 27
5.2 About us page 28
5.3 Login page 29
5.4 New User Registration page 30
5.5 Chocolate details page 31
5.6 Add new chocolate page 33
5.7 Delete chocolate page 34
5.8 Edit chocolate page 35
5.9 Cart page 35

5.10 Payment option page 36
5.11 Cash on delivery page 36
5.12 Pay online page 37

Chapter 1
INTRODUCTION
1.1 Overview of Database Management System

A Database is a collection of related data organized in a way that data can be easily accessed,
managed and updated and various operations can be performed on it. By Data, we mean
known facts that can be recorded and that have implicit meaning. A DBMS is a collection of
programs that enables users to create and maintain a database. The DBMS is a general-
purpose software system that facilitates the processes of defining, constructing, manipulating,
and sharing databases among various users and applications. DBMS also provides protection
and security to database. It maintains data consistency in case of multiple users. Here are
some examples of popular DBMS, MySQL, Oracle, Sybase, Microsoft Access and IBM DB2
etc. The database system can be divided into four components:
 The database system can be divided into System developer and End users.
 Database application: Database application may be Personal, Departmental,

Enterprise and Internal
 DBMS: Software that allow users to define, create and manages database access, Ex:
MySQL, Oracle etc.
 Database: Collection of logical data.
Functions of database management system:
 Provides Recovery services

 Provides utility
 Provides data Independence
 Provides a clear and logical view of the process that manipulates data
Advantages of DBMS:
 Segregation of application program

 Minimal data duplicity and Easy retrieval of data
BE, Dept. of CSE/BNMIT Page 1 2021-2022

Chocolate Ordering Management System
1.2 Problem Statement

The aim of this project is to design a Chocolate ordering Management System where
the users canview the chocolates and buy the chocolates. In the database, we store
varioustypes of chocolates, price and description of chocolates .
The chocolate ordering management system allows the users to help them compare
various typesof chocolates and compare them with one another and make a better choice.
Upon the selectionof the chocolate which a user wants to buys, they are required to make
payment. The users are also provided with an opportunity to make the payments in online or
cash on delivery
1.3 Objectives
The main objective of the Project on Online chocolate Ordering System is to manage the details
of chocolate Item, Category, Customer, Order, Confirm Order. It manages all the information
about chocolate Item, Payment, Confirm Order, chocolate Item. The project is totally built at
administrative end and thus only the administrator is guaranteed the access. The purpose of the
project is to build an application program to reduce the manual work for managing the chocolate
Item, Category, Payment, Customer. It tracks all the details about the Customer,
Order,ConfirmOrder.
1 Provides the searching facilities based on various factors. Such as chocolate Item,
Customer, Order, Confirm Order
2 Online chocolate Ordering System also manage the Payment details online for Order details,
Confirm Order details, chocolate Item.
3 It tracks all the information of Category, Payment, Order etc
4 Manage the information of Category etc
5 Shows the information and description of the chocolate Item, Customer
6 To increase efficiency of managing the chocolate Item, Category
7 It deals with monitoring the information and transactions of Order.

7.1 Dataset Description

Given below are the entities along with its attributes and relations present in the database of
this application that are used to retrieve information from the database as per requirement of
user.
 The entity Contact is created with the attributes name, email, mobile, subject,
message. The attribute name is the key attribute which isalso known as the primary
key
 The Entity Customer is created with username, fullname, email, contact, address,
password. The primary key is username .
 The Entity Chocolate is created with attributes f_id, name, price, description, r_id and
image_path where primary key is f_id and r_id
 The entity Manager is created with the attributes username, fullname, email, contact,
address and password where primary key is username
 The entity Orders is created with the attributes order_id, f_id, chocolate_name, price,
quantity,order_date and username where primary key is order_id
 The entity restaurant(outlet) is created with the attributes r_id, name, email, contact,
address and M_id. r_id the primary key


Chapter 5
SYSTEM REQUIREMENTS
To be used efficiently, all computer software needs certain hardware components or
other software resources to be present on a computer. These prerequisites are known as
(computer) system requirements and are often used as a guideline as opposed to an absolute
rule. Most software defines two sets of system requirements: minimum and recommended.
With increasing demand for higher processing power and resources in newer versions of
software, system requirements tend to increase over time.
2.1 Software Requirements
 Operating System : Windows 7 or higher
 Front End : HTML5/CSS/JavaScript
 Back end : MySQL
 Server : Apache 2.0
 Browser : Google Chrome
 Application software : XAMPP
 Server side language : PHP
2.2 Hardware Requirements
 Processor : Pentium III or higher
 RAM : 2GB or above
 Hard Disk : 20 GB or More

Chapter 6
SYSTEM DESIGN
3.1 Entity Relationship Diagram
An Entity Relationship Diagram describes interrelated things of interest in a specific

domain of knowledge. A basic ER model is composed of entity types and specifies
relationships that can exist between instances of those entity types. In software
engineering, an ER model is commonly formed to represent things that a business needs
to remember in order to perform business processes. Consequently, the ER model
becomes an abstract data model that defines a data or information structure which can
be implemented in a database, typically a relational database.

Chocolate ordering Management System
Figure 3.1: E R diagram of Chocolate ordering Management System.

3.2 Schema Diagram

A database schema is the skeleton structure that represents the logical view of the entire
database. It formulates all the constraints that are to be applied on the data. A database
schema defines its entities and the relationship among them. It contains a descriptive detail of
the database, which can be depicted by means of schema diagrams.
Figure 3.2: Schema diagram of chocolate ordering Management

System

3.3 Overview of Graphical User Interface

GUI is program interface that takes advantages of the computer’s graphics capabilities
to make the program easier to user. Well-designed graphical user interfaces can free the user
from learning complex command language. On the other hand, many users find that they
work more efficiently with a command-driven interface, especially if they already know the
command language.
Hypertext Markup Language (HTML) is the standard markup language for creating web
pages and web applications. With Cascading Style Sheets (CSS) and JavaScript it forms a
triad of cornerstone technologies for the World Wide Web. Web browsers receive HTML
documents from a web server or from local storage and render them into multimedia web
pages. HTML describes the structure of a web page semantically and originally included cues
for the appearance of the document.
Cascading Style Sheets (CSS) is a style sheet language used for describing the
presentation of a document written in a markup language. Although most often used to set the
visual style of web pages and user interfaces written in HTML and XHTML, the language
can be applied to any XML document and is applicable to rendering in speech, or on other
media. CSS is a cornerstone technology used by most websites to create visually engaging
webpages, user interfaces for web applications, and user interfaces for many mobile
applications.
The graphic elements are windows, menus, icons, and links that are selected while
working with a software application. The following buttons have been used in this project.
Login Page:


Register Page
Navigation bar page

3.4 Normalization
Normalization is a process of analyzing the given relation schema based on theirfunctional
dependencies and primary key to achieve desirable properties of minimizing redundancy and
minimizing insert, delete, update anomaly. The normalization process takes arelation schema
through a series of tests to certify whether it satisfies a certain normal form The normal form
of a relation refers to the highest normal form condition that it meets, and hence the degree to
which it has been normalized. There are two goals of the normalization process: eliminating
redundant data (for example, storing the same data in more than one table)and ensuring data
dependencies make sense (only storing related data in a table). Both of theseare worthy goals
as it reduces the amount of space a database consumes and ensure that data islogically stored.
Normalization rule are divided into following normal form.
 First Normal Form

1NF Rules:
• Each table cell should contain a single value.
• Each record needs to be unique The table below is in 1NF:
 Second Normal Form

2NF Rules:
• Should be in 1NF
• Single column primary key
 Third Normal Form

3NF Rules:
• Should be in 2NF
• Has no transitive functional dependencies
A transitive functional dependency is when changing a non-key column, might cause

any of the other non-key columns to change.

Consider the relations shown above here all the relations are in 2NF as all the nonprime attributes are
fully functionally dependent on the set of prime attributes. Hence the relations are in 2N

CHAPTER 4
4.1 Table Creation

Contact
CREATE TABLE `contact` (
`Name` varchar(250) NOT NULL,
Èmail` varchar(250) NOT NULL,
`Mobile` varchar(250) NOT NULL,
`Subject` varchar(250) NOT NULL,
`Message` varchar(250) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
Customer
CREATE TABLE `customer` (
ùsername` varchar(30) NOT NULL,
`fullname` varchar(30) NOT NULL,
èmail` varchar(30) NOT NULL,
`contact` varchar(30) NOT NULL,
àddress` varchar(50) NOT NULL,
`password` varchar(30) NOT NULL
chocolate
CREATE TABLE `chocolate` (

`F_ID` int(30) NOT NULL,
`name` varchar(30) NOT NULL,
`price` int(30) NOT NULL,
`description` varchar(200) NOT NULL,
`R_ID` int(30) NOT NULL,
ìmages_path` varchar(200) NOT NULL,

òptions` varchar(10) NOT NULL DEFAULT 'ENABLE'
Manager
CREATE TABLE `manager` (
ùsername` varchar(30) NOT NULL,
`fullname` varchar(30) NOT NULL,
`password` varchar(30) NOT NULL
orders
create table
orders(
order_id int(30) not null,
f_id int(30) not null,
foodname varchar(30) not null,
price int(30) not null,
quantity int(30) not null,
order_date date not null,
username varchar(30) not null,
r_id int(30) not null
)

RESTAURANTS(OUTLETS)
CREATE TABLE `restaurants` (

`R_ID` int(30) NOT NULL,
`name` varchar(30) NOT NULL,
`M_ID` varchar(30) NOT NULL
)
ALTER TABLE `customer`

ADD PRIMARY KEY (ùsername`);
ALTER TABLE `chocolate`

ADD PRIMARY KEY (`F_ID`,`R_ID`),
ADD KEY `R_ID` (`R_ID`);
ALTER TABLE `manager`

ADD PRIMARY KEY (ùsername`);
ALTER TABLE òrders`

ADD PRIMARY KEY (òrder_ID`),
ADD KEY `F_ID` (`F_ID`),
ADD KEY ùsername` (ùsername`),
ADD KEY `R_ID` (`R_ID`);
ALTER TABLE `restaurants`

ADD PRIMARY KEY (`R_ID`),
ADD UNIQUE KEY `M_ID_2` (`M_ID`),
ADD KEY `M_ID` (`M_ID`);
ALTER TABLE `food`

MODIFY `F_ID` int(30) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=80;

MODIFY òrder_ID` int(30) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=69;


MODIFY `R_ID` int(30) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=7;
ALTER TABLE `food`

ADD CONSTRAINT `food_ibfk_1` FOREIGN KEY (`R_ID`) REFERENCES
`restaurants` (`R_ID`);

ADD CONSTRAINT òrders_ibfk_1` FOREIGN KEY (`F_ID`) REFERENCES `food`
(`F_ID`),
ADD CONSTRAINT òrders_ibfk_2` FOREIGN KEY (ùsername`) REFERENCES
`customer` (ùsername`),
ADD CONSTRAINT òrders_ibfk_3` FOREIGN KEY (`R_ID`) REFERENCES
`restaurants` (`R_ID`);

ADD CONSTRAINT `restaurants_ibfk_1` FOREIGN KEY (`M_ID`) REFERENCES
`manager` (ùsername’)

4.2 Description of Tables

Customer
Figure 4.1 customer description
Contact
Figure 4.2 contact table description

Chocolate
Figure 4.3 chocolate Table description
Manager
Figure 4.4 Manager table description

Orders
Figure 4.5 Orders Table description

Restaurant(Outlet)
Figure 4.6 resturant(outlet) table description

4.3Populated Tables
Figure 4.7 customer table data
Figure 4.8 contact table data


Figure 4.9 chocolate data
Figure 4.10 manager data

Figure 4.12 restaurant data

4.4 SQL Triggers & Stored Procedures

Triggers
A database trigger is procedural code that is automatically executed in response to certain
events on a table or view in a database. The trigger is mostly used for maintaining the
integrity of the information on the database.
triggers

Stored Procedure
A stored procedure is a set of Structured Query Language (SQL) statements with an assigned name,
which are stored in a relational database management system as a group. So if a query has to be
written over and over again, instead of having to write that query each time, it can be saved as a
stored product and can be executed just by calling the procedure. In addition, parameters can also be
passed to the stored procedure. So depending on the need, the stored procedure can act accordingly
Stored procedure


4.5 Database Connectivity

In computer science, a database connection is the means by which a database server and its
client software communicate with each other. The term is used whether the client and the
server are on different machines. The client uses a database connection to send commands to
and receive replies from the server. A database is stored as a file or a set of files on magnetic
disk or tape, optical disk, or some other secondary storage device. The code is given below:
const mysql = require("mysql");
const dbConfig = require("../config/db.config.js");
// Create a connection to the database
const connection =
mysql.createConnection({ host:
dbConfig.HOST,
user: dbConfig.USER,
password: dbConfig.PASSWORD,
database: dbConfig.DB
});
// open the MySQL connection

connection.connect(error =>
{ if (error) throw error;
console.log("Successfully connected to the database.");
});
module.exports = connection;

CHAPTER 5 RESULTS
HOME PAGE
Figure 5.1 Home page

About us:
Figure 5.2 About us page
Contact page

User Login
Figure 5.3 Login page

New user registration
Figure 5.4 User Registration page

Chocolate Details


Figure 5.5 My property page
Add new chocolate

Figure 5.6 Add property page
Delete chocolate details
Figure 5.7 delete chocolate page

Edit chocolates details
Figure 5.8 Edit chocolates page
Cart details
Figure 5.9 Buy property page

Payment option
Figure 5.10 Payment option page
Cash on delivery
Figure 5.11 Cash on delivery page

Pay Online details
Figure 5.12 Pay Online page

MODULES
The below flowchart explains how the system runs in the real world. The system can be
easily implemented under various situations. Reusability is possible as and when
required in this application. There is flexibility in all the modules which makes the task
of the user easier. The system consists of Manager account and user account. The first
time users are required to register to this site else the user will not be able to access the
features of the site. After successful registration, the user can log in to his account and
view the Chocolates and place orders. The user cart is implemented using cookies.
Cookies is a nice way of implementing cart because any time a user wishes to add items
into his cart, hitting database each time for temporary purposes makes multiple
transactions which can be costly. Cookies reduce these wasteful transactions. If the user
adds items to his cart, only then he will be able to place an order else not. Once order is
placed the bill is generated for the user. The manager can update the chocolate and price
as and when required and these updates will be shown simultaneously in the user's side
too. The manager can update the contents, price, quantity, description and also delete
some of the items as his wish.

CONCLUSION
The chocolate ordering management system is designed to make it easier for the users
to view and buy the chocolates. The main aim of maintaining the chocolate data has been
achieved in this system. It has been developed in HTML, CSS, Bootstrap, Javascript
keepingin mind the specification of the system. For designing the system,
HTML/CSS/Javascript/Bootstrap is being used as the front end and the application can be run
using xampp server. To connect thebackend with the frontend, Phpmyadmin is used to make
API calls. The user can create an accountby providing all the essential details like their
username, fullname, Address, contact,email,password. After registering the account, the user
can view and buy the chocolates.The application takes care of all the requirements and is
capable to provide easy and effectivestorage of information related to chocolates
The application is built using suitable back-end and front-end which has made the
project more efficient and user-friendly. . Overall the project teaches us the essential skills
like understanding the database handling and query processing, implement, analyze and
evaluate the project developed for an application, demonstrate the working of different
concepts of DBMS.

FUTURE ENHANCEMENT
This project is easy to implement and also enhances the application as per future
requirements. The table normalized in appropriate manner, so there will not be any ambiguity
as the data increases. Hence, this application can be enhanced to meet the growing demands
of the market. The future enhancements may include:
• The application can be updated as an online application
• Once it is updated as an application, the users can be able to find the chocolates in
any part of the country.
• Payment validation and security can be done when the application is ready to be used
in real-time.
• Enabling users to have a conversation on the application.
• Tracking of the order can be enhanced

1bg19cs021 Chocolate Ordering Bhavana Converted by Abcdpdf

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1bg19cs021 Chocolate Ordering Bhavana Converted by Abcdpdf

Uploaded by

Copyright:

Available Formats

VISVESVARAYA TECHNOLOGICAL UNIVERSITY

JNANASANGAMA, BELAGAVI - 590018

B.N.M. Institute of Technology

Department of Computer Science and Engineering

Department of Computer Science and Engineering

Certified that the Mini Project entitled CHOCOLATE ORDERING MANAGEMENT

Dr. Sreevidya RC Dr. Sahana D. Gowda

Name & Signature

I would like to express my gratitude to Prof. Eishwar N Maanay, Dean, BNMIT,

I extend my heartfelt gratitude to Dr. Sreevidya RC, Assistant Professor in the

Finally, I would like to thank all the faculty members of Department of

1.1 Overview of Database Management Systems 1

4.1 Table creation 12

3.2 Schema diagram of Chocolate ordering Management System 7

4.1 customer description 16

4.2 contact table description 16

4.3 chocolate table description 17

4.4 manager table description 17

4.5 order table description 18

4.6 restaurant(outlet) table description 18

4.7 customer Data 19

4.8 contact data 19

4.9 chocolate data 21

4.10 manager Data 21

4.11 Restaurant data 22

4.13 stored procedure 24

5.1 Home page 27

5.2 About us page 28

5.3 Login page 29

5.4 New User Registration page 30

5.5 Chocolate details page 31

5.6 Add new chocolate page 33

5.7 Delete chocolate page 34

5.8 Edit chocolate page 35

5.9 Cart page 35

5.11 Cash on delivery page 36

5.12 Pay online page 37

1.1 Overview of Database Management System

 Database application: Database application may be Personal, Departmental,

Functions of database management system:

 Provides Recovery services

 Segregation of application program

BE, Dept. of CSE/BNMIT Page 1 2021-2022

1.2 Problem Statement

BE, Dept. of CSE/BNMIT Page 2 2021-2022

7.1 Dataset Description

BE, Dept. of CSE/BNMIT Page 3 2021-2022

BE, Dept. of CSE/BNMIT Page 4 2021-2022

2.1 Software Requirements

 Operating System : Windows 7 or higher

 Front End : HTML5/CSS/JavaScript

 Back end : MySQL

 Server : Apache 2.0

 Browser : Google Chrome

 Application software : XAMPP

 Server side language : PHP

2.2 Hardware Requirements

 Processor : Pentium III or higher

 RAM : 2GB or above

 Hard Disk : 20 GB or More

BE, Dept. of CSE/BNMIT Page 5 2020-2021

An Entity Relationship Diagram describes interrelated things of interest in a specific

BE, Dept. of CSE/BNMIT Page 6 2020-2021