Report Mini

VISVESVARAYATECHNOLOGICALUNIVERSITY
"Jnana Sangama", Belagavi - 590 018
A Mini -Project Work on
“DANCE WORKSHOP MANAGEMENT SYSTEM”

A Dissertation work submitted in partial fulfilment of the requirement
for the award of the degree
Bachelor of Engineering
In
Information Science & Engineering
Submitted by
Anushree G L 1AY21IS019
Kavya V Goudar 1AY21IS044
Under the guidance of

Prof. Pankaj Kumar
Assistant Professor
DEPARTMENTOFINFORMATIONSCIENCE&ENGINEERING
ACHARYAINSTITUTEOFTECHNOLOGY
(AFFILIATED TO VISVESVARAYA TECHNOLOGICAL UNIVERSITY, BELAGAVI.APPROVED BY AICTE, NEW DELHI,
ACCREDITED BY NAAC, NEW DELHI)
Acharya Dr. Sarvepalli Radhakrishnan Road, Soldevanahalli, Bengaluru-560107

2023-24
DEPARTMENTOFINFORMATIONSCIENCE&ENGINEERING
ACHARYAINSTITUTEOFTECHNOLOGY
(AFFILIATED TO VISVESVARAYA TECHNOLOGICAL UNIVERSITY, BELAGAVI.APPROVED BY AICTE, NEW DELHI, ACCREDITED BY
NAAC, NEW DELHI)
Acharya Dr. Sarvepalli Radhakrishnan Road, Soldevanahalli, Bengaluru-560107
Certificate
This is to Certify that the Database Management System Laboratory(21CSL55) Mini-
Project work entitled “Dance Workshop Management System” is a bonafide work
carried out by Kavya V Goudar(1AY21IS044) and Anushree GL
(1AY21IS019) in partial fulfillment for the award of the degree of Bachelor of
Engineering in Information Science and Engineering of the Visvesvaraya
Technological University, Belagavi during the year 2023-24. It is certified that all
corrections/suggestions indicated for Internal Assessment have been incorporated in
the Report deposited in the departmental library. The Project has been approved as it
satisfies the academic requirements in respect of Project work prescribed for the
Bachelor of Engineering Degree.
Prof. Pankaj Kumar Dr. Kala Venugopal

Signature of Guide Signature of HOD
Name of the Examiners Signature with date

1.
2.
ACKNOWLEDGEMENT
The satisfaction that accompanies the successful completion of this mini-project would
be incomplete without the mention of the people who made it possible through constant
guidance and encouragement.
We would take this opportunity to express our heartfelt gratitude to Sri. B.

Premnath Reddy, Chairman, Acharya Institutes, and Dr. Rajath Hegde M M, Principal,
Acharya Institute of Technology for providing the necessary infrastructure to complete
this mini-project.
We wish to express our deepest gratitude and thanks to Dr. Kala Venugopal,
Head of the Department, Information Science and Engineering.
We wish to express sincere thanks to my guide Prof. Pankaj Kumar, Assistant

Professor, Department of Information Science and Engineering for helping us throughout
and guiding us from time to time.
A warm thanks to all the faculty of the Department of Information Science and
Engineering, who have helped us with their views and encouraging ideas.
Kavya V Goudar(1AY21IS019)
R.Kalaivani Indira(1AY21IS044)
ABSTRACT
TABLEOFCONTENTS
Acknowledgement i
Abstract ii
1. Introduction 1
1.1 Introduction to DBMS 1
1.1.1 Why DBMS? 2
1.1.2 Database applications 2
1.1.3 Advantages of DBMS 3
1.1.4 Components of DBMS 4
1.1.5 Three-Schema architecture 5
2. System Requirements 6
2.1 Hardware Requirements 6
2.2 Software Requirements 6
3. Design 7
3.1 ER Diagram 7
3.2 Schema Diagram 8
4. Implementation 9
4.1 Tables 9
4.1.1 USER 9
4.1.2 BOOK DETAILS 9
4.1.3 MESSAGE 10
4.1.4 RECOMMENDATIONS 10
4.1.5 RECORD 11
4.1.6 RENEW 11
4.1.7 RETURN 12
4.1.8 AUTHOR 12
5. Snapshots 13
6. Triggers 23
Conclusion & Future Enhancements 24
Bibliography 25
TABLEOFFIGURES
1.1 Components of Database Management System 4

1.2 Architecture of database system 5
3.1 Entity Relationship Diagram 7
3.2 Schema Diagram 8
5.1 Snapshot of sign in/ sign up page 13
5. 2 Snapshot of home page/index page 14
5.3 Snapshot of all books page 15
5.4 Snapshot of recommend a book page 16
5.5 Snapshot of currently issued books 17
5.6 Snapshot of messages page 18
5.7 Snapshot of previously borrowed books page 19
5.8 Snapshot of send messages page 20
5.9 Snapshot of add a book page 21
5.10 Snapshot of requests page 22
Library management system DBMS Mini-Project
CHAPTER 1
INTRODUCTION
In today’s busy world it is difficult to find bookings for planes, hotels and get offers at
the same time.EasyGo is a site that helps people to book modes of transport and even the place
of stay, based on a roundtrip or one-way trip. Even cancel the booking and get exciting offers.
1.1 Introduction to DBMS

DBMS stands for Database Management System. We can break it like this DBMS = Database
+ Management System. The database is a collection of data and a Management System is a set
of programs to store and retrieve those data. Basically, DBMS is a software tool to organize
(create, retrieve, update and manage) data in a database.
The main aim of a DBMS is to supply a way to store up and retrieve database
information that is both convenient and efficient. By data, we mean known facts that can be
recorded and that have embedded meaning. Normally people use software such as DBASE IV
or V, Microsoft ACCESS, or EXCEL to store data in the form of a database. A datum is a unit
of data. Meaningful data combined to form information. Hence, information is interpreted data
– data provided with semantics. MS. ACCESS is one of the most common examples of
database management software.
Database systems are meant to handle large collections of information. Management of

data involves both defining structures for the storage of information and providing mechanisms
that can do the manipulation of those stored information. Moreover, the database system must
ensure the safety of the information stored, despite system crashes or attempts at unauthorized
access.
1.1.1 Why DBMS?

● To develop software applications in less time.
● Data Independence and efficient use of data.
● For uniform data administration.
● For data integrity and security.
AIT/ISE/2022- 23 1
● For concurrent access of data, and data recovery from crashes.

● To use user-friendly declarative query language.
1.1.2 Database applications

● Telecom: There is a database to keep track of the information regarding calls made,
network usage, customer details, etc. Without the database systems, it is hard to
maintain that huge amount of data that keeps updating every millisecond.
● Industry: Where it is a manufacturing unit, warehouse, or distribution center, each one

needs a database to keep the records of ins and outs. For example, distribution centers
should keep a track of the product units that are supplied into the centre as well as the
products that got delivered out from the distribution centre on each day; this is where
DBMS comes into the picture.
● Education sector: Database systems are frequently used in schools and colleges to store
and retrieve the data regarding student details, staff details, course details, exam details,
payroll data, attendance details, fees details etc. There is a hell lot of interrelated data
that needs to be stored and retrieved efficiently.
● Online shopping: You must be aware of the online shopping websites such as Amazon,
Flipkart etc. These sites store the product information, your addresses and preferences,
credit details and provide you the relevant list of products based on your query. All this
involves a Database management system.
● Banking system: For storing customer info, tracking day to day credit and debit
transactions, generating bank statements etc. All this work has been done with the help
of Database management systems.
1.1.3 Advantages of DBMS

A DBMS manages data and has many advantages.
AIT/ISE/2022- 23 2
● Data Independence: Application programs should be as free or independent as possible

from details of data representation and storage. DBMS can supply an abstract view of
the data for insulating application code from such facts.
● Efficient data access: DBMS utilizes a mixture of sophisticated concepts and

techniques for storing and retrieving data competently and this feature becomes
important in cases where the data is stored on external storage devices.
● Data integrity and security: If data is accessed through the DBMS, the DBMS can
enforce integrity constraints on the data.
● Data administration: When several users share the data, integrating the administration
of data can offer major improvements. Experienced professionals understand the nature
of the data being managed and can be responsible for organizing the data representation
to reduce redundancy and make the data to retrieve efficiently.
● Providing backup and recovery: A DBMS must provide facilities for recovering from
hardware or software failures. The backup and recovery subsystem of the DBMS is
responsible for recovery.
● Permitting inferencing and actions using rules: Some database systems provide
capabilities for defining deduction rules for inferencing new information from the stored
database facts.
AIT/ISE/2022- 23 3
1.1.4 Components of DBMS
Fig-1.1: Components of a Database Management System
● Users: Users may be of any kind such as DB administrator, System developer or

database users.
● Database application: Database application may be Departmental, Personal,

organization’s and / or Internal.
● DBMS: Software that allows users to create and manipulate database access.
● Database: Collection of logical data as a single unit.
● Database access language: This is used to access the data to and from the database, to
enter new data, update existing data, or retrieve required data from databases. The user
writes a set of appropriate commands in a database access language, submits these to the
DBMS, which then processes the data and generates and displays a set of results into a
user readable form.
AIT/ISE/2022- 23 4
1.1.5 Three-Schema architecture
Fig-1.2: Architecture of database system
The levels form a three-level architecture that includes an external, a conceptual, and an
internal level. The way users recognize the data is called the external level. The way the DBMS
and the operating system distinguish the data is the internal level, where the data is actually
stored using the data structures and file. The conceptual level offers both the mapping and the
desired independence between the external and internal levels.
CHAPTER 2
SYSTEMREQUIREMENTS
2.1 Hardware Requirements

● Processor: Intel Core2 Quad @ 2.4Ghz on Windows® Vista 64-Bit / Windows® 7 64-
Bit / Windows® 8 64-Bit / Windows® 11 64-Bit.
● RAM: 6GB of RAM
● Memory: 256GB Hard drive
AIT/ISE/2022- 23 5
● Keyboard: MS-compatible keyboard

● Mouse: MS-compatible mouse
2.2 Software Requirements

● Operating system: Windows® Vista 64-Bit / Windows® 7 64-Bit / Windows® 8 64-Bit
/ Windows® 11 64-Bit.
● Front end: HTML, BOOTSTRAP, JAVASCRIPT,CSS
● Back end: PHP
● IDE: MySQL workbench
CHAPTER 3
DESIGN
3.1 ER
Diagram
AIT/ISE/2022- 23 6
Fig-3.1: Entity Relationship Diagram
N:M
● Any number of users can renew any number of books in the library. (N:M).
● Any number of books can be returned by any number of users(N:M).
1: N
● One user can receive any number of messages.
● One user can give N number of recommendations.
● One book can be associated with N number of records.
● One book can be written by N number of authors.
● One user can create N number of records.
AIT/ISE/2022- 23 7
3.2 Schema Diagram
USER
Rollno
Mobno
Name type college Email-id
BOOK
Title Publisher Year Availability Bookid
AIT/ISE/2022- 23 8
MESSAGE
M_id Rollno Msg Date Time
RECOMMENDATIONS
R_id Book_name Description Rollno
RECORD
Renewals_lef
Rollno Bookid Date_of_issue Due_date Date_of_return Dues time
t
RENEW
Rollno Bookid
RETURN
Rollno Bookid
AUTHOR
Author Bookid
Fig-3.2: Schema Diagram

CHAPTER 4
AIT/ISE/2022- 23 9
IMPLEMENTATION
4.1 Tables
4.1.1 USER
Entity name ATTRIBUTES CONSTRAINTS
USER RollNo Primary key , not null
Name Not null
Type Not null
Email-id Not null
MobNo Not null
password Not null

4.1.2 BOOK DETAILS
Entity ATTRIBUTES CONSTRAINTS
BookId Primary key,not null
Title Not null
BOOK Publisher Not null
Year Not null
Availability Not null

4.1.3 MESSAGE
M_id Primary key,not null
RollNo Not null
msg Not null
AIT/ISE/2022- 23 10
MESSAGE Date Not null
Time Not null

4.1.4 RECOMMENDATIONS
R_ID Primary key,auto increment
Recommendations Book_Name Not null
Description Not null
RollNo Foreign key

4.1.5 RECORD
BookId Foreign key
RollNO Foreign key
Date_of_Issue Not null
RECORD Due_Date Not null
Date_of_Return Not null
Dues Not null
Renewals_left Not null
Time Not Null

4.1.6 RENEW

RENEW BookId Foreign key
RollNO Foreign key

4.1.7 RETURN
AIT/ISE/2022- 23 11
RETURN BookId Foreign key
RollNO Foreign key

4.1.8 AUTHOR
AUTHOR BookId Foreign key
Author Not null

CHAPTER 5
SNAPSHOTS
The following snapshot contains the sign in/sign up page.
Fig-5.1: Snapshot of sign in / sign up page

1. The welcome screen contains links for -
● Sign in
● Sign up
2. User can enter his roll no and password for login
3. User can also sign up if he does not have an existing account.
4. User can select his college name and provide his email_id,phone number during sign up
AIT/ISE/2022- 23 12
Validators Given:
1. The given blanks can not be null.
2. Here also there is an option to for Sign Up if the User has not registered yet.
3. While creating a password the no. Of characters must be greater than 6.
4. To view his home page user must sign up or sign in.
5. A user will be able to sign in only when he has been registered.
6. After the completion of the Sign in and Sign up the user will be redirected to the home
or the index page .
Fig-5.2: Snapshot of home page/ index page
The above snapshot is seen as soon as the user logs in through this page he will start his library
journey
● User can select and search for books he wants.
● User can see messages that he has received.
● The user can also recommend new books and give descriptions to the books that he is
recommending.
● The currently issued books and the date in which it was issued or returned.
AIT/ISE/2022- 23 13
● If the user has borrowed any books previously then it will be showed in the previously
borrowed books.
● If the user wants to log out he can click the navigation bar and click log out or he can
click the logout in the left side toggle bar.
Validators given:
1. The following page will not be rendered if the user is not successfully logged in .
Fig-5.3: Snapshot of all book page
● It shows the books their availability.

● User can just select details to view the book details
● If user is interested in a book he can raise a request for book issue.
Validators given:
1. The following page will not be rendered if the user has not successfully logged in.
AIT/ISE/2022- 23 14
Fig-5.4: Snapshot of recommend a book page
The is a snapshot of recommend a book page.

● When a user wants a book that is not there in the library he can recommend the book by
giving title of the book and its description.
Validators given
1. The following page will not render if the user has not successfully logged in .
2. The user can not submit an empty response with no title or description.
AIT/ISE/2022- 23 15
Fig-5.5: Snapshot of currently issued books
The is a snapshot of currently issued books page

● When a user selects the currently issued books tab he can see the books that he has is
currently issued with.
● It shows the name of the book, book id,its issue date and due date.
● User can just select renew to renew the book.
● If user wishes to return the book he raise a return request by clicking return.
Validators given:
1. The following page will not be rendered if the user has not successfully logged in.
2. The user can not raise return request for the same book twice.
3. The user can not raise a renewal request for a book that has crossed its due date.
AIT/ISE/2022- 23 16
Fig-5.6: Snapshot of the messages page
The is a snapshot of the messages page .

● When a user selects the messages page he can see all the messages that were sent to him
by the admin.
● It shows the message content , date and time the message was sent.
Validators given:
1. The following page will not be rendered if the user has not successfully registered.
AIT/ISE/2022- 23 17
Fig-5.7: Snapshot of previously borrowed books page
This is a snapshot of the previously borrowed books page.

● When a user selects the previously borrowed books page he can see the books that were
previously borrowed and returned by him.
● It shows the train name of the book , book id, issue date and return date.
● User can not see the books if he has not returned the books yet.
Validators given:
AIT/ISE/2022- 23 18
Fig-5.8: Snapshot of send a message (admin) page
The is a snapshot of the send a message page.

● When the admin wants to send a message to the user he can type the roll no and contents
of the message and send.
● It shows that the message was sent successfully after the message has been sent
Validators given:
2. The admin can not send a message to a roll no that is not available in the database.
3. The admin can not send an empty message.
AIT/ISE/2022- 23 19
Fig-5.9 : Snapshot of add a book (admin) page

The is a snapshot of the add a book page.
● This page allows the admin to add books to the library.
● The user can enter book title , author, publisher name,year and availability of the book.
Validators given:
1. The following page can not be submitted if the given fields are not entered
2. The admin can not render this page if he has not successfully logged in.
AIT/ISE/2022- 23 20
Fig-5.10: Snapshot of requests page(admin)
The following snapshot of requests page in the admin login.

● The admin can view and approve requests made by the users using this page.
● He can either accept of reject requests made by the user .
Validators given:
1. The admin can not render this page if he has not successfully logged in.
TRIGGERS
Trigger for the records table.
CREATE TRIGGER `renew` AFTER INSERT ON `record`
FOR EACH ROW DELETE FROM renew WHERE
rollno=new.rollno;
Trigger to send message to admin for every recommendation.

CREATE TRIGGER `msgpop` AFTER INSERT ON `recommendations`
FOR EACH ROW insert into message (Msg,RollNo) VALUES
('u have new recommendations','admin')
AIT/ISE/2022- 23 21
PROCEDURES
Procedure for retrieving all books details.
CREATE DEFINER=`root`@`localhost` PROCEDURE `getbook`()
select * from book$$
DELIMITER ;
Procedure for retrieving details of user who have raised renew request.
DELIMITER $$
CREATE DEFINER=`root`@`localhost` PROCEDURE
`renew_requests`() select * from user
where rollno in( select rollno from renew )$$
DELIMITER ;
CONCLUSION&FUTUREENHANCEMENT
Conclusion
This project is a digital library that makes it easy for users to see availability, recommend and
borrow books online. This project aims at small libraries both public and private. This project
can be used in today's situation where going out has become a fear, it lets the user sit at home or
anywhere to renew or return books. This project also makes it easy for the admin or the library
manager to maintain a database on who has taken books, when the books were taken and other
details of the borrower. This project also makes it easy for the individual to search for books
and know their availability and raise a issue request. The library admin can send messages to
the borrowers related to issues in books or notify the borrower on returns and fines /dues that
he will have to pay when he returns the book late. It makes entire process online where student
can search books, admin can generate reports on transactions. It also has a facility for student
login where student can login and can see status of books issued as well request for book or
give some suggestions. This is a user friendly design as it makes it easy for remote users also to
use the website.
AIT/ISE/2022- 23 22
Future Enhancement
In a nutshell, it can be summarized that the future scope of the project circles around
maintaining information regarding:
● Going through library books and their availability as and where we are.
● Reading a book online can be added.
● The platform can be hosted on the online servers to make it accessible worldwide.
● Integrate multiple load balancers to distribute the loads of the system.
● Implement a backup mechanism for taking backup of database on regular basis on
different servers.
The above mentioned points are the enhancements which can be done to increase the
applicability and usage of this project.
BIBLIOGRAPHY
Web References
1. https://www.w3schools.in/dbms/intro/
2. https://www.youtube.com/
3. https://getbootstrap.com/
4. https://developer.mozilla.org/en-US/
5. https://www.erdplus.com/
6. https://www.google.com/
7. Https://mysql.com/
Book References
1. Fundamentals of Database Systems, RamezElmasri and Shamkant B. Navathe, 7th Edition,
2017, Pearson
AIT/ISE/2022- 23 23

Report Mini

Uploaded by

Document Information

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

Report Mini

Uploaded by

Copyright:

Available Formats

VISVESVARAYATECHNOLOGICALUNIVERSITY

"Jnana Sangama", Belagavi - 590 018

A Mini -Project Work on

“DANCE WORKSHOP MANAGEMENT SYSTEM”

Under the guidance of

Acharya Dr. Sarvepalli Radhakrishnan Road, Soldevanahalli, Bengaluru-560107

Prof. Pankaj Kumar Dr. Kala Venugopal

Name of the Examiners Signature with date

We would take this opportunity to express our heartfelt gratitude to Sri. B.

We wish to express sincere thanks to my guide Prof. Pankaj Kumar, Assistant

1.1 Components of Database Management System 4

1.1 Introduction to DBMS

Database systems are meant to handle large collections of information. Management of

1.1.1 Why DBMS?

● For concurrent access of data, and data recovery from crashes.

1.1.2 Database applications

● Industry: Where it is a manufacturing unit, warehouse, or distribution center, each one

1.1.3 Advantages of DBMS

● Data Independence: Application programs should be as free or independent as possible

● Efficient data access: DBMS utilizes a mixture of sophisticated concepts and

1.1.4 Components of DBMS

Fig-1.1: Components of a Database Management System

● Users: Users may be of any kind such as DB administrator, System developer or

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

● Database: Collection of logical data as a single unit.

1.1.5 Three-Schema architecture

Fig-1.2: Architecture of database system

2.1 Hardware Requirements

● Keyboard: MS-compatible keyboard

2.2 Software Requirements

Fig-3.1: Entity Relationship Diagram

● One user can create N number of records.

3.2 Schema Diagram

Name type college Email-id

Title Publisher Year Availability Bookid

M_id Rollno Msg Date Time

R_id Book_name Description Rollno

Fig-3.2: Schema Diagram

Entity name ATTRIBUTES CONSTRAINTS

USER RollNo Primary key , not null

Name Not null

Type Not null

Email-id Not null

MobNo Not null

password Not null

Entity ATTRIBUTES CONSTRAINTS

BookId Primary key,not null

Title Not null

BOOK Publisher Not null

Year Not null

Availability Not null

Entity ATTRIBUTES CONSTRAINTS

M_id Primary key,not null

RollNo Not null

msg Not null

MESSAGE Date Not null

Time Not null

Entity ATTRIBUTES CONSTRAINTS

R_ID Primary key,auto increment

Recommendations Book_Name Not null

Description Not null

RollNo Foreign key

Entity ATTRIBUTES CONSTRAINTS

BookId Foreign key