A

PROJECT REPORT ON
“Library Management System”

A Project Report Submitted As A Partial Fulfillment Of The Requirement For

The Degree Of Bachelor Of Computer Application Under Gauhati University

Internal Guide Submitted By

Karabi Choudhury Jagjivan Kumar Sharma

BCA Department BCA Department
Dispur College Dispur College
Roll No:

(Signature of the Guide) (Signature of the Student)

1
 PREFACE
Projects are indispensible part of management education. They enlighten us
with the facts and provide us a valuable knowledge about the topic under the
study. In professional courses like BCA, we are familiar with strong theoretical
knowledge about various computer application objects through classroom
techniques. But this project is such project which makes us work on the area of
our interest or specialization and help us gain much valuable knowledge on the
topic of study.

I did my grand project on the topic “Library Management System” in

order to make the date manner. Where ever possible, tables and figures have
been incorporated, recommendations have been made on the basis of finding
herein.

Jagjivan Kumar Sharma

Course: BCA

Roll No:

Date: Registration No: A/F

Place: BCA Department

2
 CERTIFICATE OF ORIGINALITY FROM THE
GUIDE

This is to certify that the project report entitled “Library Management

System”submitted to Gauhati University in partial fulfillment of the
requirement for the award of the BCA is an original work carried by Jagjivan
Kumar Sharma, Roll No: , under the supervision of Karabi Choudhury, Head
of the BCA Department, Dispur College.

The matter embodied in this project is a genuine work done by the student
and has not been submitted either to this University or to any other
University/Institute for the fulfillment of the requirement of any course of study.

External Examiner

(Signature of the Guide)

Karabi Choudhury
BCA Department
Dispur College
Gauhati University

Date:

Place:

3
 ACKNOWLEDGEMENT

I take this opportunity to thank all those persons, whose constant guidance,
support and help have appreciated me to see the face of the completion of this
project. Preparing a project is a tedious task and was fortunate enough to get
support from a large number of persons to whom, I shall always remain
grateful.

I feel immense pleasure in expressing my sincere thanks and gratitude to my

project guide by Dr. Laba Kumar Thakuria, HOD of BCA Department for his
valuable guidance and constant encouragement throughout the entire project
work entitled “Book busket.in” without which this study would have never been
possible.

I also express my sincere thanks and gratitude to Dr. Amar Saikia, Principal
of Dispur College, for giving me the chance to complete my BCA under
Gauhati University. I am also thankful to Mrs. Bijoyata Saha and Mrs. Korobi
Choudhury, Assistant Professors of Dispur College, for their kind cooperation
and help to successfully complete my project. At last I also express my thanks
to all of my friends who gave me the constant inspiration for fulfillment of my
project.

Partha Pratim Baishya

Course: BCA

Roll No:

Date: Registration No: A/F

Place: BCA Department

4
 SELF DECLARATION

I hereby declare that the project entitled “Book busket.in” has been carried out
by me and is submitted in the partial fulfillment for the BCA in Dispur College
under Gauhati University.

I also declare that, any or all contents incorporated in this dissertation, has
not been submitted in any form for the award of any other degree to any
Institute or University.

Partha Pratim Baishya

Course: BCA

Roll No:

Date: Registration No: A/F

Place: BCA Department

5
 TO WHOM IT MAY CONCERN

This is to certify that the project entitled “Book busket.in” is bonfire work done
by Partha Pratim Baishya of BCA 4th Semester having Roll No: and
Registration No: A/F of 2017-18.

In partial fulfillment of the requirement for the award of BCA and have
been carried out my direct supervision and guidance. This report or a similar
report on the topic have not been submitted for any other examination and does
not form part of any course undergone by the candidate.

Internal Guide
(Dr. Laba Kumar Thakuria)
HOD
BCA Department
Dispur College

6
 PROJECT OUTLINES

1. TITLE OF THE PROJECT: Book busket.in

for Dispur College

2. AIM OF THE PROJECT: To release the difficulty of

searching the great books.

3. PURPOSE: Gauhati University mini

project required for the
partial fulfillment for the
award of BCA

4. DURATION OF THE PROJECT: 1 months approximately

5. PLACE OF THE PROJECT: Dispur College

6. PROJECT DONE BY: Partha Pratim Baishya

7. GUIDED BY: Dr. Laba Kumar Thakuria

HOD (BCA Department)

7
 PROJECT REQUIREMENTS

Software Used:

Operating System: Microsoft Windows 7

Front End: HTML, CSS

Hardware Used:

Processor: Intel Pentium

Hard Disk: 300GB

RAM: 3GB

8
 CONTENTS

Chapter 1: Introduction to “Book busket.in”

1.1: Introduction of books

1.2: Overview of books
1.3: Why we should read books
1.4: Existing Systems

Chapter 2: Objectives and Limitations of the Project

2.1: Objectives of the Study
2.2: Purpose of the Study
2.3: Limitations of the Study
2.4: Language and Software
2.4.1: Hardware Used
2.4.2: Software Used
2.4.3: Language Used
2.4.3.1: CSS
2.4.3.2: HTML

2.5: Problem Definition

2.5.1: Introduction
2.5.2: User Login
Chapter 3: Data Flow Diagram and ER Diagram
3.1: DFD
3.1.1: Introduction
3.1.2: Objectives of DFD
3.1.3: Level 0 DFD of the website “Book busket.in”
3.1.4: Level 1 DFD of the website “Book busket.in”

9
 3.1.5: Level 2 DFD of the website “Book busket.in”
3.2: ENTITY RELATIONSHIP DIAGRAM
3.2.1: Introduction
3.2.2: Entity
3.2.3: Data Attributes
3.2.4: Relationships
3.2.5: ER Diagram of the website “Books busket.in”
Chapter 4: Testing Procedures
4.1: Introduction
4.2: Testing Principles
4.3: Definition of Testing
4.4: Types of Testing
4.5: Conclusion
Chapter 5: Output and Source Code
5.1: Home Page
5.2: Category Page
5.2.1: Book storage page
5.2.2: Best selling books of month page
5.2.3: 30% off page

5.3: Contact Us Page

5.4: Comment page
5.5: Register page
Chapter 6: Conclusion and Future Scope
6.1: Conclusion
6.2: Future Scope
Bibliography

CHAPTER 1: INTRODUCTION TO

10
 “Books buslet.in”

1.1: Introduction

Books are good as well as great for peoples. There are many types of books
available. Every book is unique in there own way and gives us something
different experiance-
 Books improve imagination.
 Books teach them right from wrong.
 Books develop critical thinking skills.
 Reading books are fun.

1.2: Overview of Books

A great book is greatest friend of a human. Because books helps people to

develop personality get knowledge and improve thinking process. Every people
should read books atleast for one hour to relax his mind or to get knowledge.
There are many types of books like romantic, story , general knowledge,
thriller. Various types of books helps us in various way.

1.3: Why we should read books

Books are useful because of the following reasons. Some of them are given
below:
1. Books shows us how to handle problems.
2. It builds emotional resiliency.
3. It gives us a common language to communicate.
4. It crosses cultural boundaries.
5. It teaches story and lessons.
6. It develops imagination.

1.4: Existing Systems

Currently there are many books available in the market written by the great
authors. People go to book stores and buy them on depending on whether the
book stall owner keep that book or not. This system is not effective and not
serving most of the peoples.

1.5: Limitations of the Existing Systems

11
The existing systems have the following limitations:
1. They don’t have the connection to provide customer every books that are
available in the market.
2. Even they don’t have the feedback option which allows the users to share
their thoughts and ideas with the administrator of books.

1.6: Proposed System

The website “Book busket.in” aims at selling books facility where the readers
can read and also buy all the books in one time only. This website makes it
easier to readers to buy books and read them.

This website contains all the books which the readers can use for
themselves which make them feel excited. It also contains pictures of the books.

After reading the boks,the readers have also the facility of giving feedbacks
about the website and can also contact on the numbers given in the website.

CHAPTER 2: OBJECTIVES AND LIMITATIONS

OF THE PROJECT
12
2.1: Objectives of the Study

 The main objective of creating this website is that it can reduce the
difficulty of buying the books.
 Another objective is that it can make the readers to save time in book
shoping
 Here, also customers can buy the books of their choice.

2.2: Purpose of the Study

 This website is created to allow the users to buy the books from anywhere
and anytime.
 It reduce the difficulty of readers to find a book online and save time of
the buyers.

2.3: Limitations of the Study

 This website doesn’t have the download option which in turn doesn’t
allow the users to read the books.
 Even this website doesn’t summery of the books. They have to buy the
books to read it.

2.4: Languages and Software

To create this website the following software, hardware and languages are used
which are described in details below.

2.4.1: Hardware Used

Processor: Intel Pentium

Hard Disk: 300GB

RAM: 3GB

2.4.2: Software Used

Operating System: Microsoft Windows 7

13
Web Browser: Mozilla Firefox, Google Chrome

2.4.3: Languages Used

The following languages are used to create this website are described below.

2.4.3.1: CSS

Cascading Style Sheets (CSS) is a style sheet language used for describing
the presentation of a document written in a markup language.[1] 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,
including plain XML, SVG and XUL, and is applicable to rendering in speech,
or on other media. Along with HTML and JavaScript, 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.

CSS is designed primarily to enable the separation of presentation and

content, including aspects such as the layout, colors, and fonts.[3] This
separation can improve content accessibility, provide more flexibility and
control in the specification of presentation characteristics, enable multiple
HTML pages to share formatting by specifying the relevant CSS in a separate
.css file, and reduce complexity and repetition in the structural content.

Separation of formatting and content makes it possible to present the same

markup page in different styles for different rendering methods, such as on-
screen, in print, by voice (via speech-based browser or screen reader), and
on Braille-based tactile devices. It can also display the web page differently
depending on the screen size or viewing device. Readers can also specify a
different style sheet, such as a CSS file stored on their own computer, to
override the one the author specified.
Changes to the graphic design of a document (or hundreds of documents)
can be applied quickly and easily, by editing a few lines in the CSS file they
use, rather than by changing markup in the documents.

The CSS specification describes a priority scheme to determine which style

rules apply if more than one rule matches against a particular element. In this
so-called cascade, priorities (or weights) are calculated and assigned to rules, so
that the results are predictable.

2.4.3.2: HTML
14
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 webserver 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.

HTML elements are the building blocks of HTML pages. With HTML
constructs, images and other objects, such as interactive forms, may be
embedded into the rendered page. It provides a means to create structured
documents by denoting structural semantics for text such as headings,
paragraphs, lists, links, quotes and other items. HTML elements are delineated
by tags , written using angle brackets. Tags such <input>...</input>as introduce
content into the page directly. Others such as <p>.....</p> surround and provide
information about document text and may include other tags as sub-elements.
Browsers do not display the HTML tags, but use them to interpret the content of
the page.

HTML can embed programs written in a scripting language such

as JavaScript which affect the behavior and content of web pages. Inclusion of
CSS defines the look and layout of content. The World Wide Web
Consortium (W3C), maintainer of both the HTML and the CSS standards, has
encouraged the use of CSS over explicit presentational HTML since 1997.

2.5: Problem Definition

2.5.1: Introduction

The website “Book busket.in” has been designed with the motive to buy the
books in one time only.
This website will help in following ways:

 The users need not to search different fairy tales in different websites as
this website contains a list of all the books.
 It also helps the user to buy the books according to their choice.
 Even this website has the option of getting feedbacks so that if any users
have to comment about the website, we will take it positively and try to
make it more improved one.
 This website also contains the contacts if users have any problem in
shipment and tracking of their order.

15
  2.5.2: User Login

1. The users can view all the books to know the. And
2. They can buy the books according to their choices and their personal
details will be securely saved in our database.

CHAPTER 3: DATA FLOW DIAGRAMS AND ER

DIAGRAM

3.1: DFD

3.1.1: Introduction

The data flow diagrams are the diagrams that depict the data sources, data sinks,
data storage and process performed on data as nodes and logical flow of data as
links between the nodes. DFD allows software development team to depict flow
of data from one or more processes to another.

3.1.2: Objectives of DFD

1. Represents system data in hierarchical manner and with required level of

details.
2. Depicts processes according to defined user requirements and software
scope.

The four basic notations of DFD are:

1. Entity: Represents the source or destination of data within the system.

Each external entity is identified with a meaning and unique name.
2. Data Flow: Represents the moment of data from its source to destination
within the system.
3. Data Store: Indicates the place for storing information within the system.
4. Process: Shows a transformation or manipulation of data within the
system.

There are several levels of DFD which provide details about the input,
processes and output of a system. The level of detail of process increases with
increase in levels.

1. Level 0 DFD: Shows an overall view of the system.

16
 2. Level 1 DFD: Elaborates level 0 DFD and splits the process into a
detailed form.
3. Level 2 DFD: Elaborates level 1 DFD and displays the process in a more
detailed form.
4. Level 3 DFD: Elaborates level 2 DFD and displays the process in a more
detailed form.

3.1.3: Level 0 DFD Of The Website “Book busket.in”

Website
Admin Database

information reply

17
3.1.4: Level 1 DFD Of The Website “Book busket.in”

1. Information
Home
Admin

2 List of Books
Category

3 Comments
Feedback

4
Contact
Us
Contacts

5
Order Details of the
Details Order

6
Confirmation
Confirmation
User Report Message

18
3.1.5: Level 2 DFD Of The Website “Book busket.in”

User’s
Informati-
on

Tracking
User Details Database

Shipment
Details

19
3.2: ENTITY RELATIONSHIP DIAGRAM

3.2.1: Introduction

Entity Relationship Diagram is a diagram that depicts a set of real world entities
and the logical relationships among them. This diagram depicts entities, the
relationships between them, and the attributes pictorially in order to provide a
high level description of conceptual data models. ER Diagram is used in
different phases of software development. ER Diagram comprises of data
objects and entities, data attributes, relationships and cardinality and modality.

3.2.2: Entity

An entity is the data that stores information about the system in a database.
Example of an entity includes real world objects, transactions and persons.

3.2.3: Data Attributes

It describes the properties of a data object. Attributes that identify entities are
known as key attributes. On the other hand, attributes that describe an entity is
known as non-key attributes.

3.2.4: Relationships

The link or connection of data objects or entities with each other is known as
relationship. Three types of relationships exist among entities. These
relationships are listed below:

1. One to one relationship (1:1): It indicates that one instance of an entity is

related only to another instance of another entity. For example: in a
database of users in a bank, each user is related to only one account
number.

2. One to many relationship (1:M): It indicates that one instance of an

entity is related to several instances of another entity. For example: one
user can have many accounts in different banks.

3. Many to many relationship (M:N): It indicates that many instances of an

entity are related to several instances of another entity. For example:
many users can have their accounts in many banks.

20
 3.2.5: ER Diagram of the website “Book busket.in”

First Last Name

Name Country State
Name Price

M N
Choose
Customer Books

Pin code Email

Image Description

Phone
M
Has

Payment Type
Order Details Book Selection

21
 CHAPTER 4: TESTING PROCEDURES

4.1: Introduction

The purpose of system testing is to identify and correct errors in the candidate
system. A system should always be tested thoroughly before implementing it, as
regards its individual programs, the system as a whole user acceptance, etc. This
is because implementing a new system is a major job, which enquires a lot of
man, hour and lot of other resources, so an error not detected before
implementation may cost a lot. Effective testing early in the process translates
directly into long term cost saving from reduce number of errors.

4.2: Testing Principles

 All tests should be traceable to customer requirements.

 Test should be planned long before testing begins. Test planning can
begin as soon as requirements module is completed.
 Testing should begin “in small” and progress towards testing “in large”.
 Exhaustibly testing is not possible. The number of path permutations for
even a moderately sized program is exceptionally large. For this reason, it
is possible to execute every combination of path during testing. It is
possible however, to adequately cover program, logic program and
ensures that all conditions in the procedural design have been exercised.

After a test plan has been developed, system testing y testing program
modules separately, followed by testing “bundled” modules as a unit. A
program module may function perfectly in isolation but failed when interfaced
with other modules. The approach is tool test each entity with successively
larger ones, up to the system test level.

4.3: Definition of Testing

The system should always be tested thoroughly before implementation of it as

regard to the individual programs, the system as a whole, user acceptance etc.
This is because implementing a new system is a major job that requires a lot of
man, hour and a lot of other resources, so an error not detected before
implementation may cost a lot. Effectively testing early in the process translates
directly into long term cost saving from a reduced number of errors. The
purpose of system testing is to consider all the likely variations to which it will
be subjected and then push the system to its limits. It is a tedious but necessary
step in system development.

22
4.4: Types of Testing

The different types of testing techniques that are used during the development
of the system under consideration are as follows:

1. Module Testing: It must be carried out during the programming stage

itself. Here individual program testing must be carried out during the
coding itself and the required changes are to be made on the module to
ensure the smooth and satisfactory execution of the module in the form of
an individual program and the generation of the output in the required
form.

2. String Testing: Programs are invariably related to one another and

interact in a tool system. Each program is tested to see whether it
conforms to related programs in the system or not. Each portion of the
system is tested against the entire module with both test and leave data
before the entire system is ready to test.

3. Unit Testing: It is to make changes in an existing or a new program. It is

necessary for the verification of the code that would be produce during
the code phase. It is mainly to test the internal logic of the module.

4. Integration Testing: In integration testing, many unit tested modules are

combined with sub systems, which would be then tested. The objective of
this testing is to see if the modules can be integrated properly. That is, the
prime emphasis is on testing the interfaces between the modules.

5. System Testing: The purpose of system testing is to identify and correct

errors in the system. As important as this phase is, it is one that is
frequently compromised. In this testing, performance and acceptance
standards are developed.

6. Output Testing: No system could be useful if it does not produce

required format. It includes asking the user about the required format of
the output that would be displayed on the screen or in a printed form.

7. User Acceptance Testing: It verifies that the system’s procedures

operate to system specifications and that the integrity of the vital data is
maintained, performance of an acceptance test is actually the user’s show.
User motivation and knowledge are critical for the successful
performance of the system.

23
4.5: Conclusion

The objective of system testing is to uncover the errors. To fulfill these

objectives a series of test steps are planned and executed.

Each test step is accomplished through a series of systematic test techniques

that assist in the design of test cases. With each testing step, the level of
abstraction with which software is considered is broadened. The various tests
mentioned above are performed successfully. This assures the effectiveness of
the system.

24
 CHAPTER 5: OUTPUT

The website “Book busket.in” contains many webpages. It contains five menus:

5.1: Home Page: The homepage of the website is given below:

25
The coding of the homepage is given below:

26
27
28
The coding of CSS Page used in Homepage is given below:

29
30
5.2: Book storage Page: The category page of the website is given below:

31
The coding of the category page is given below:

32
33
5.3: My account Page: The My account page is given below:

The coding of the My account page is given below:

34
5.4: Register Page: The Register page is given below:

35
The coding of the register page is given below:

36
37
5.5: Comment Page: The comment page is given below:

The coding of the comment page is given below:

38
CHAPTER 6: CONCLUSION AND FUTURE
SCOPE

6.1: Conclusion

The website “Book buskt.n” has been developed using HTML, CSS, which
fulfills the basic objectives of the system for which it has been developed. The
system has reached a steady state as far as the basic framework is concerned.
The system is operated at a high level of efficiency and its advantage is quite
understood.

This web application provides the facility to buy online books at any time
and from everywhere. It saves time as it allows the users to buy books of their
choice and releases the effort of searching different books in different stores.
This is because this website contains a list of books. It is automatically
generated by the server.

Administrator has the privilege to create, modify and delete webpages so

that the users can get the website updated. Users can buy the books of their
choice and have to give their personal information so that they can get the book
at their places where they want.

6.2: Future Scope

If time and resource constraints are eliminated, this website can be adapted to a
full-fledged knowledge portal, wherein a personalized environment for each
user who is a part of it can be created.

39
 BIBLIOGRAPHY

 PHP written by Laura Thomson and Luke Welling, published by

Addison-Wesley Professional on September 2016.
 Software Engineering: A Practitioner's Approach, written by Roger S.
Pressman, published by McGraw-Hill Science/Engineering/Math on 1st
March 2004.
 Head First HTML with CSS & XHTML, written by Elisabeth
Robson, Eric Freeman, Kathy Sierra and Rich Gibson, published by
O'Reilly Media on 1st December 2005

40