Relational Database Management System

Assignment -3

Library Management System

Submitted to – Mr. Prabin Rout
Asst. Prof
NIFT Bhubaneswar

Submitted by-

Kaustab Brahmchari

Ojasvi Mahajan

Vibhav Shernagat

Yashaswini Raj
 Project Overview Statement
As we know, that a library is a collection of books in any institute. Librarian’s
responsibility is to manage all the records issued and also returned manually.

A library is a collection of organized information and resources which is made

accessible to a well-defined community for borrowing or for reference sale. The
collection of resources and information are provided in digital or physical format
in either a building/room or in a virtual space or even both. Library’s collection
may include newspapers, books, tapes, videotapes, microforms etc. The main aim
of the system is to develop a new programmed system that will be conveying ever
lasting solution to the manual base operations and to make available a channel
through a staff which can maintain and record data easily and customers can
access data and information about the library at whatever place they might find
themselves.

Library Management system allows the user to store the book details and the
customer details. The system is strong enough to withstand regressive yearly
operations under conditions where the database is maintained and cleared over a
certain span of time. The implementation of the system in the organization will
considerably reduce data entry, time and also provide readily calculated reports.
 OBJECTIVE
It keeps track of all the information about the books in the library, their cost,
status and total number of books available in the library. The user will find it easy
in this automated system rather than using the manual writing system. The
system contains a database where all the information will be stored safely.

The goals of this project are: –

 Security – The user has to provide password in order to enter. Hence it

provides security.
 Easiness – The user simply has to follow series of instruction which makes
project very simple to use.
 Speedup result processing – While manually it may take time to search for
books but it helps to speed up processing. And also issue and return processes
are easy. Also database for students and books help in speeding up work of
management of library
 Library management system is software for automating the manual library
system of a college.
 Functionalities of active library like issuing of books, returning of books and
query processing.
 The Books and Students are given a particular unique id no. So that they can
be accessed correctly and without errors. Our main aim of the project is to get
the correct information about a particular student and books available in the
library
 Library management system is standalone in nature.
 Keep the record of updated books & students database.
 The project is implemented to bring a simpler interface for the users and
provide them with easy search and access methods.
 ACKNOWLEDGEMENT
Credits for completing a document like this goes not to a single person but each
and everyone involved. We would like to express our sincere gratitude and
thankfulness to our faculty, friends and teachers who made this study a success.

We would also like to thank the academic system of our college; National
Institute of Fashion Technology for incorporating such a subject in our curriculum
that helps the student to know about the various computer based skills that are
required for one to work in an organization.

We are very thankful to our subject faculty Mr.Prabin Rout and our course
coordinator Mr.Sumit Kumar for their continuous and deliberate discussions on
how to understand the subject better and compile a sensible document on the
same.
 Data Flow Diagram
A data flow diagram (DFD) maps out the flow of information for any process or
system. It uses defined symbols like rectangles, circles and arrows, plus short text
labels, to show data inputs, outputs, storage points and the routes between each
destination. Data flowcharts can range from simple, even hand-drawn process
overviews, to in-depth, multi-level DFDs that dig progressively deeper into how
the data is handled.

They can be used to analyze an existing system or model a new one. Like all the
best diagrams and charts, a DFD can often visually “say” things that would be hard
to explain in words, and they work for both technical and nontechnical audiences,
from developer to CEO. That’s why DFDs remain so popular after all these years.
While they work well for data flow software and systems, they are less applicable
nowadays to visualizing interactive, real-time or database-oriented software or
systems. Following are the rules:

 Each process should have at least one input and an output.

 Each data store should have at least one data flow in and one data flow
out.

 Data stored in a system must go through a process.

 All processes in a DFD go to another process or a data store.

The goals of this project are: –

 Security – The user has to provide password in order to enter. Hence it

provides security.
 Easiness – The user simply has to follow series of instruction which makes
project very simple to use.
 Speedup result processing – While manually it may take time to search for
books but it helps to speed up processing. And also issue and return processes
are easy. Also database for students and books help in speeding up work of
management of library
 Library management system is software for automating the manual library
system of a college.
 Functionalities of active library like issuing of books, returning of books and
query processing.
 The Books and Students are given a particular unique id no. So that they can
be accessed correctly and without errors. Our main aim of the project is to get
the correct information about a particular student and books available in the
library
 Library management system is standalone in nature.
 Keep the record of updated books & students database.
 The project is implemented to bring a simpler interface for the users and
provide them with easy search and access methods.
SYSTEM REQUIREMENTS

Software Requirement
1. Microsoft Windows 2000 or above.
2. .Net platform
3. Microsoft Access.
Other Requirements
1. Internet connection for online help
Diagrams:
 E-R Diagram

 Data Flow Diagram

 Activity Diagram
 Database Tables
 CONCLUSION
 Project in fully complete and running with every aspect of coding
and connectivity with the database.
 We have tried our best to present the simple interface to the user
and remove the complexity of using a manual library like searching
and fine calculation.
 LIMITATIONS
 The project is designed to run on a single machine, no option to run
on a network of computers ( LAN etc).
 The designing of project is not up to the level of software market, it
has a lot of scope to improve.
 There is no option for reader if he/she forgot password. If he or she
forgets his or her password they need to sign up again.
 The reader or the administrator can use this one at a time, that
means only one transaction can be processed at one time that may
be issue, return or any other.
 The database is not vast.
 There is no option for the payment receipt of the fine submission.
 NEED ANALYSIS
With the advancement of Computers and its Technologies brought a
revolution in the world, it hit every aspect of life. Nowadays every field
and its working are computerized.

It is very beneficial as our paper work is reduced to a minimum. So it is

essential that we have a library that is computerized and equipped to
deal with the daily transactions in an efficient way so that maximum
work is done and the performance increased. So there is a need to
develop software that can cope up with all these requirements and that
is cost as well as time effective. We have developed such a project that
can cope with the daily needs of a library that includes transactions like
issue a book, return a book, search a book.

Now, with computerized Library Management System we aim to

present users with much more better and easier interface and search
options and side by side provide other options like details of books and
readers and options like fine management which includes calculation
work. One may encounter the difficulties of finding the required
product or the same process might be very hectic on many website.
 SUGGESTIONS FOR FUTURE VISION
 Project can be further enhanced with the facility to run project on
multiple machines (LAN) so that more than one library for the same
institution can be connected through same database and controlled
by same mechanism.
 In depth details regarding every the security aspects of the project
needs to prepared and then taken steps taken or functionality
included to preserve security.
 Enhancements can be made to provide user with option that if one
forgets his/her password then it can be changed or retrieved.
 New option like option for the payment receipt of the fine
submission can be included.
 Tables
A table is a collection of related data held in a structured format within
a database. It consists of columns, and rows.
In relational databases, and flat file databases, a table is a set of data
elements (values) using a model of vertical columns (identifiable by
name) and horizontal rows, the cell being the unit where a row and
column intersect. A table has a specified number of columns, but can
have any number of rows. Each row is identified by one or more values
appearing in a particular column subset. A specific choice of columns
which uniquely identify rows is called the primary key.
"Table" is another term for "relation"; although there is the
difference in that a table is usually a multi set (bag) of rows where a
relation is a set and does not allow duplicates. Besides the actual data
rows, tables generally have associated with them some metadata, such
as constraints on the table or on the values within particular columns.
In terms of the relational model of databases, a table can be
considered a convenient representation of a relation, but the two are
not strictly equivalent. For instance, an SQL table can potentially
contain duplicate rows, whereas a true relation cannot contain
duplicate tuples. Similarly, representation as a table implies a particular
ordering to the rows and columns, whereas a relation is explicitly
unordered.
An equally valid representation of a relation is as an n-
dimensional chart, where n is the number of attributes (a table's
columns). For example, a relation with two attributes and three values
can be represented as a table with two columns and three rows, or as a
two-dimensional graph with three points. The table and graph
representations are only equivalent if the ordering of rows is not
significant, and the table has no duplicate rows.
 How to create tables in access ?
1. To create tables in Access using “Design View,” click the “Create”
tab in the Ribbon.
2. Then click the “Table Design” button in the “Tables” group.
3. A new table then appears in the tabbed documents area.
4. Type the name of a field into the “Field Name” column.
5. Then press “Tab” on your keyboard to move to the next column to
the right.
6. Then use the drop-down menu in the “Data Type” column to
assign the field a data type.
7. Press “Tab” on your keyboard to move to the “Description”
column.
8. If desired, type a description of the data stored in this field.
9. Then press “Tab” on your keyboard to move down to the next
row.
10. Repeat steps 4 through 9 until you have created all of the
necessary table fields.
11. Click the row selector at the left end of the row that
contains the field you want to set as the “primary key” for the
table.
12. Click the “Design” tab within the “Table Tools” contextual
tab in the Ribbon.
13. Then click the “Primary Key” button in “Tools” group.
14. Click the “Save” button in the Quick Access toolbar.
15. Then type a name for the new table into the dialog box that
appears.
16. Then click the “OK” button.

The following tables have been illustrated in the following screenshots

that we have added in the library management system.
 ACKNOWLEDGMENT
We would like to first thanks our premiere institution NIFT
BHUBANESWAR for providing us with the golden opportunity for doing
this project. Then, we would like to thanks our faculty Mr. Prabin Rout
for being always there and helping us in doing this project that not only
helped us to increase our knowledge but also our communication skills.
We are thankful to all the teachers and friends who have been there
with us while we were doing this project.
 MS ACCESS
Microsoft Access is a database management system (DBMS) from Microsoft that
combines the relational Microsoft Jet Database Engine with a graphical user
interface and software-development tools. It is a member of the Microsoft
Office suite of applications, included in the Professional and higher editions or
sold separately.
Microsoft Access stores data in its own format based on the Access Jet
Database Engine. It can also import or link directly to data stored in other
applications and databases.
Software developers, data architects and power users can use Microsoft
Access to develop application software. Like other Microsoft Office applications,
Access is supported by Visual Basic for Applications (VBA), an object-
based programming language that can reference a variety of objects including
DAO (Data Access Objects), ActiveX Data Objects, and many other ActiveX
components. Visual objects used in forms and reports expose their methods and
properties in the VBA programming environment, and VBA code modules may
declare and call Windows operating system operations.
 How to create Report in Ms Access?
1. Open the Navigation pane.
2. Click the table or query on which you want to base your report.
3. Activate the Create tab.
4. Click the Report button in the Reports group. Access creates your report and
displays your report in Layout view. You can modify the report.

How to create form in Ms Access?

1. To create a form with no controls or preformatted elements: On
the Create tab, click Blank Form. Access opens a blank form in Layout view,
and displays the Field List pane.
2. In the Field List pane, click the plus sign (+) next to the table or tables that
contain the fields that you want to see on the form.
3. To add a field to the form, double-click it or drag it onto the form. To add
several fields at once, hold down CTRL and click several fields, and then
drag them onto the form at the same time.
4. Use the tools in the Controls group on the Form Layout Tools tab to add a
logo, title, page numbers, or the date and time to the form.
5. If you want to add a wider variety of controls to the form, click Design and
use the tools in the Controls group.
FORMS
 These are the different tables and forms that we have made in the Library
Management System. All of them contain different information that are necessary
for the effective working of the library system and satisfy all the clients and their
demands.
 ACTIVITY DIAGRAMS
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.

The basic purpose of activity diagrams is similar to other four diagrams. It

captures the dynamic behavior of the system. Other four diagrams are used to
show the message flow from one object to another but activity diagram is used
to show message flow from one activity to another.

Activity is a particular operation of the system. Activity diagrams are not only
used for visualizing the dynamic nature of a system, but they are also used to
construct the executable system by using forward and reverse engineering
techniques. The only missing thing in the activity diagram is the message part.

It does not show any message flow from one activity to another. Activity diagram
is sometimes considered as the flowchart. Although the diagrams look like a
flowchart, they are not. It shows different flows such as parallel, branched,
concurrent, and single.
 Schema Diagram
A schema is the structure behind data organization. It is a visual
representation of how different table relationships enable the schema’s
underlying mission business rules for which the database is created.
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. It's the database designers who design
the schema to help programmers understand the database and make it
useful.

Schema diagrams have an important function because they force

database developers to transpose ideas to paper. This provides an
overview of the entire database, while facilitating future database
administrator work. For example: It has been shown in the following
diagram.
 Entity – Relationship Diagrams

Entity Relationship Diagram is used in modern database software

engineering to illustrate logical structure of database. It is a relational
schema database modeling method used to Model a system and
approach. This approach commonly used in database design. The
diagram created using this method is called ER-diagram.

The ER-diagram depicts the various relationships among entities,

considering each object as entity. Entity is represented as rectangle
shape and relationship represented as diamond shape. It depicts the
relationship between data object. The ER-diagram is the notation that
is used to conduct the data modeling activity.