ABSTRACT

Library is place where all kind of books are available. Intranet Library Management
system is a web based application. This system contains list of all the books and can be accessed
by remote users concurrently from any where in the campus. But for that users must be
registered user. This system is three tier architecture.

Client sends requests, on receiving the request the server processes it and extracts the
data from database and sends the result back to the client. This system provides separate
interface and login for librarian, students and faculties. Librarian can modify database.

Users can search for books and renewal books online. They can recommend for new
books by just sending messages to the librarian from any where in the college. They can view
the issue and return dates of any book and due they have to pay. This system generates reports
that can be used in analyzing the library performance. Thus the management can take
appropriate steps to improve the facilities.
 INDEX

S. N CONTENTS

1. INTRODUCTION
2. ANALYSIS
2.1 SYSTEM ANALYSIS
2.2 SYSTEM SPECIFICATIONS
3. DESIGN APPROACH
3.1 INTRODUCTION TO DESIGN
3.2 UML DIAGRAMS
3.3 DATA FLOW DIAGRAMS
3.4 E-R DIAGRAMS
4. PROJECT MODULES
5. IMPLEMENTATION
6. OUTPUT SCREENS
7. CONCLUSION
8. FUTURE ENHANCEMENTS
9. BIBILIOGRAPHY
INTRODUCTION:

Library Management System consists of list of records about the management of the
details of the students and the issues going on and also about some books and all. This is a web-
based application. The project has three modules namely- User, Registration, Librarian.
According to the Modules the Distributor and Sub Distributors can manage and do their
activities in easy manner.

As the modern organizations are automated and computers are working as per the
instructions, it becomes essential for the coordination of human beings, commodity and
computers in a modern organization. This information helps the distributors to purchase or sale
the products very efficiently.

The administrators and all the others can communicate with the system through this
project, thus facilitating effective implementation and monitoring of various activities of the
distributor of a supermarket.
 SYSTEM ANALYSIS:
1. Existing System
. Various problems of physical system are described below :-
 If one is not very careful then there is a possibility of issuing more than one
book to a user.
 There is a possibility of issuing a book to a user, whose membership is not there.
 When a user requests for the a book, one has to physically check for the
presence of a book in the library
 Answering management query is a time consuming process.
 Daily keeping a manual record of changes taking place in the library such as book
being issued, book being returned etc can become cumbersome if the Library size is bigger.

2. Proposed System

The LIBRARY MANAGEMENT SYSTEM is a software application which avoids more

manual hours in taking the book, that need to spend in record keeping and generating reports.
Maintaining of user details is complex in manual system in terms of agreements, royalty and
activities. This all have to be maintained in ledgers or books. Co-coordinators needs to verify
each record for small information also.
 Easy search of book in the online library.
 Avoid the manual work.
 User need not go to the library for Issue any kind of book, he can renewal the book online.

3. Objective of the System

The goal of the system is to bring down the work load with the increased efficiency and
to speed up the activities. With this it is very easy to process course fee that is collected time to
time from students who are registered and studying at franchisees.
System Specifications

Hardware Requirements:-
 Pentium-IV(Processor).
 256 MB Ram
 512 KB Cache Memory
 Hard disk 10 GB
 Microsoft Compatible 101 or more Key Board

Software Requirements: -
 Operating System : Windows 7/8/8.1/10/11 with MS-office
 Programming language : PYTHON(PyQt5)
 Back-End : MYSQL
INTRODUCTION:
 Design is the first step in the development phase for any techniques and
principles for the purpose of defining a device, a process or system in sufficient detail to permit
its physical realization.

Once the software requirements have been analyzed and specified the
software design involves three technical activities - design, coding, implementation and testing
that are required to build and verify the software.

The design activities are of main importance in this phase, because in

this activity, decisions ultimately affecting the success of the software implementation and its
ease of maintenance are made. These decisions have the final bearing upon reliability and
maintainability of the system. Design is the only way to accurately translate the customer’s
requirements into finished software or a system.

Design is the place where quality is fostered in development.

Software design is a process through which requirements are translated into a representation of
software. Software design is conducted in two steps. Preliminary design is concerned with the
transformation of requirements into data.

UML Diagrams:
Actor:
A coherent set of roles that users of use cases play when interacting with the use `cases.

Use case:
A description of sequence of actions, including variants, that a system
performs that yields an observable result of value of an actor.

UML stands for Unified Modeling Language. UML is a language for specifying, visualizing and
documenting the system. This is the step while developing any product after analysis. The goal
from this is to produce a model of the entities involved in the project which later need to be
built. The representation of the entities that are to be used in the product being developed need
to be designed.
There are various kinds of methods in software design:
They are as follows:
 Use case Diagram
 Sequence Diagram
 Collaboration Diagram
 Activity Diagram
 State chat Diagram

USECASE DIAGRAMS:

Use case diagrams model behavior within a system and helps the developers understand
of what the user require. The stick man represents what’s called an actor.
Use case diagram can be useful for getting an overall view of the system and
clarifying who can do and more importantly what they can’t do.
Use case diagram consists of use cases and actors and shows the interaction
between the use case and actors.

 The purpose is to show the interactions between the use case and actor.
 To represent the system requirements from user’s perspective.
 An actor could be the end-user of the system or an external system.

USECASE DIAGRAM:
 A Use case is a description of set of sequence of actions. Graphically it is rendered as an
ellipse with solid line including only its name. Use case diagram is a behavioral diagram that
shows a set of use cases and actors and their relationship. It is an association between the use
cases and actors. An actor represents a real-world object. Primary Actor – Sender, Secondary
ActorReceiver.

.
SEQUENCE DIAGRAM:
Sequence diagram and collaboration diagram are called INTERACTION DIAGRAMS.
An interaction diagram shows an interaction, consisting of set of objects and their relationship
including the messages that may be dispatched among them.
A sequence diagram is an introduction that empathizes the time ordering of messages.
Graphically a sequence diagram is a table that shows objects arranged along the X-axis and
messages ordered in increasing time along the Y-axis
State Chart Diagram

user registration

user validation

not validuser checkingforvaliduse

valid user

Library

DATA FLOW DIAGRAMS:

 The DFD takes an input-process-output view of a system i.e. data objects flow into the
software, are transformed by processing elements, and resultant data objects flow out of the
software.

Data objects represented by labeled arrows and transformation are represented

by circles also called as bubbles. DFD is presented in a hierarchical fashion i.e. the first data
flow model represents the system as a whole. Subsequent DFD refine the context diagram (level
0 DFD), providing increasing details with each subsequent level.

The DFD enables the software engineer to develop models of the information
domain & functional domain at the same time. As the DFD is refined into greater levels of
details, the analyst perform an implicit functional decomposition of the system. At the same
time, the DFD refinement results in a corresponding refinement of the data as it moves through
the process that embody the applications.

A context-level DFD for the system the primary external entities produce
information for use by the system and consume information generated by the system. The
labeled arrow represents data objects or object hierarchy.

RULES FOR DFD:

 Fix the scope of the system by means of context diagrams.

 Organize the DFD so that the main sequence of the actions
 Reads left to right and top to bottom.
 Identify all inputs and outputs.
 Identify and label each process internal to the system with Rounded circles.
 A process is required for all the data transformation and Transfers. Therefore, never
connect a data store to a data Source or the destinations or another data store with just
a Data flow arrow.
 Do not indicate hardware and ignore control information.
 Make sure the names of the processes accurately convey everything the process is
done.
 There must not be unnamed process.
 Indicate external sources and destinations of the data, with Squares.
 Number each occurrence of repeated external entities.
 Identify all data flows for each process step, except simple Record retrievals.
 Label data flow on each arrow.
 Use details flow on each arrow.
 Use the details flow arrow to indicate data movements.

E-R Diagrams:
 The Entity-Relationship (ER) model was originally proposed by Peter in 1976 [Chen76] as a way to
unify the network and relational database views. Simply stated the ER model is a conceptual data model
that views the real world as entities and relationships. A basic component of the model is the Entity-
Relationship diagram which is used to visually represents data objects. Since Chen wrote his paper the
model has been extended and today it is commonly used for database design For the database designer,
the utility of the ER model is:

 it maps well to the relational model. The constructs used in the ER model can easily be
transformed into relational tables.
 it is simple and easy to understand with a minimum of training. Therefore, the model can
be used by the database designer to communicate the design to the end user.
 In addition, the model can be used as a design plan by the database developer to
implement a data model in a specific database management software.

Connectivity and Cardinality

The basic types of connectivity for relations are: one-to-one, one-to-many, and many-to-many. A
one-to-one (1:1) relationship is when at most one instance of a entity A is associated with one instance of
entity B. For example, "employees in the company are each assigned their own office. For each employee
there exists a unique office and for each office there exists a unique employee.

A one-to-many (1:N) relationships is when for one instance of entity A, there are zero, one, or
many instances of entity B, but for one instance of entity B, there is only one instance of entity
A. An example of a 1:N relationships is a department has many employees each employee is
assigned to one department.

A many-to-many (M:N) relationship, sometimes called non-specific, is when for one instance of entity A,
there are zero, one, or many instances of entity B and for one instance of entity B there are zero, one, or
many instances of entity A. The connectivity of a relationship describes the mapping of associated

ER Notation

There is no standard for representing data objects in ER diagrams. Each modeling methodology
uses its own notation. The original notation used by Chen is widely used in academics texts and journals
but rarely seen in either CASE tools or publications by non-academics. Today, there are a number of
notations used, among the more common are Bachman, crow's foot, and IDEFIX.

All notational styles represent entities as rectangular boxes and relationships as lines connecting
boxes. Each style uses a special set of symbols to represent the cardinality of a connection. The notation
used in this document is from Martin. The symbols used for the basic ER constructs are:

 entities are represented by labeled rectangles. The label is the name of the entity. Entity
names should be singular nouns.
 relationships are represented by a solid line connecting two entities. The name of the
relationship is written above the line. Relationship names should be verbs
 attributes, when included, are listed inside the entity rectangle. Attributes which are
identifiers are underlined. Attribute names should be singular nouns.
 cardinality of many is represented by a line ending in a crow's foot. If the crow's foot is
omitted, the cardinality is one.
 existence is represented by placing a circle or a perpendicular bar on the line. Mandatory
existence is shown by the bar (looks like a 1) next to the entity for an instance is required.
Optional existence is shown by placing a circle next to the entity that is optional
PROJECT MODULES
 MODULES USED:-
The proposed system categories and follows these modules to implement

Login component
1. Librarian

Librarian Manager Component

1. Librarian Manager

Student Component
1. Books Details
2. Issue Details

MODULES DESCRIPSTION:-
User: Using login id and password user can the use Library online where users can
search for books and renewal books online. They can recommend for new books by just sending
messages to the librarian from any where in the college. They can view the issue and return
dates of any book and due they have to pay.
Registration: In the Registration module, user has to register himself by supplying his
personal information which gets store in data base which are using as backend. By registering
himself user will get his login id and Password so that he can access Library online. Separate
Register form should be designed for separate user
(Student, Faculty, Librarian) and separate login has to provided for each user. For example if the
users are students then student id should be SH001.

Librarian: Librarian is a person who manages the Library. Librarian has the
permission that he can access the database. There are some tasks which are performed by the
Librarian like:
 Addition of a new book.
 Modification of the book.
 Deletion of the book.
 Searching of the book.
 Issue book
 Return book

OVERVIEW OF TECHNOLOGIES USED

 Front End Technology
Python 3

Python is a popular programming language. It was created by Guido

van Rossum, and released in 1991.

It is used for:

 web development (server-side),

 software development,
 mathematics,
 system scripting.

What can Python do?

 Python can be used on a server to create web applications.
 Python can be used alongside software to create workflows.
 Python can connect to database systems. It can also read and
modify files.
 Python can be used to handle big data and perform complex
mathematics.
 Python can be used for rapid prototyping, or for production-ready
software development.

Why Python?
 Python works on different platforms (Windows, Mac, Linux,
Raspberry Pi, etc).
 Python has a simple syntax similar to the English language.
 Python has syntax that allows developers to write programs with
fewer lines than some other programming languages.
 Python runs on an interpreter system, meaning that code can be
executed as soon as it is written. This means that prototyping can be very
quick.
 Python can be treated in a procedural way, an object-oriented way
or a functional way.

Good to know
 The most recent major version of Python is Python 3, which we shall
be using in this tutorial. However, Python 2, although not being updated with
anything other than security updates, is still quite popular.
 In this tutorial Python will be written in a text editor. It is possible to
write Python in an Integrated Development Environment, such as Thonny,
Pycharm, Netbeans or Eclipse which are particularly useful when managing
larger collections of Python files.
 BACK END TECHNOLOGY:

About Microsoft SQL Server 2000

Microsoft SQL Server is a Structured Query Language (SQL) based, client/server relational
database. Each of these terms describes a fundamental part of the architecture of SQL Server.

Database
A database is similar to a data file in that it is a storage place for data. Like a data file, a database
does not present information directly to a user; the user runs an application that accesses data
from the database and presents it to the user in an understandable format.

A database typically has two components: the files holding the physical database and the
database management system (DBMS) software that applications use to access

data. The DBMS is responsible for enforcing the database structure, including:

 Maintaining the relationships between data in the database.

 Ensuring that data is stored correctly and that the rules defining data relationships are not
violated.
 Recovering all data to a point of known consistency in case of system failures.

Relational Database
There are different ways to organize data in a database but relational databases are one of
the most effective. Relational database systems are an application of mathematical set theory to
the problem of effectively organizing data. In a relational database, data is collected into tables
(called relations in relational theory).

When organizing data into tables, you can usually find many different ways to define
tables. Relational database theory defines a process, normalization, which ensures that the set of
tables you define will organize your data effectively.

Client/Server:-
 In a client/server system, the server is a relatively large computer in a central location
that manages a resource used by many people. When individuals need to use the resource, they
connect over the network from their computers, or clients, to the server.
Examples of servers are: In a client/server database architecture, the database files and
DBMS software reside on a server. A communications component is provided so applications
can run on separate clients and communicate to the database server over a network. The SQL
Server communication component also allows communication between an application running
on the server and SQL Server.
Server applications are usually capable of working with several clients at the same time.
SQL Server can work with thousands of client applications simultaneously. The server has
features to prevent the logical problems that occur if a user tries to read or modify data currently
being used by others.
While SQL Server is designed to work as a server in a client/server network, it is also
capable of working as a stand-alone database directly on the client. The scalability and ease-of-
use features of SQL Server allow it to work efficiently on a client without consuming too many
resources.

Structured Query Language (SQL):-

To work with data in a database, you must use a set of commands and statements
(language) defined by the DBMS software. There are several different languages that can be
used with relational databases; the most common is SQL. Both the American National Standards
Institute (ANSI) and the International Standards Organization (ISO) have defined standards for
SQL. Most modern DBMS products support the Entry Level of SQL-92, the latest SQL standard
(published in 1992).

SQL Server Features

Microsoft SQL Server supports a set of features that result in the following benefits:

Ease of installation, deployment, and use

SQL Server includes a set of administrative and development tools that improve your ability to
install, deploy, manage, and use SQL Server across several sites.
Scalability
The same database engine can be used across platforms ranging from laptop computers running
Microsoft Windows® 95/98 to large, multiprocessor servers running Microsoft Windows NT®,
Enterprise Edition.

Data warehousing
SQL Server includes tools for extracting and analyzing summary data for online analytical
processing (OLAP). SQL Server also includes tools for visually designing databases and
analyzing data using English-based questions.

System integration with other server software

SQL Server integrates with e-mail, the Internet, and Windows.

Databases
A database in Microsoft SQL Server consists of a collection of tables that contain data, and other
objects, such as views, indexes, stored procedures, and triggers, defined to support activities
performed with the data. The data stored in a database is usually related to a particular subject or
process, such as inventory information for a manufacturing warehouse.

SQL Server can support many databases, and each database can store either interrelated data or
data unrelated to that in the other databases. For example, a server can have one database that
stores personnel data and another that stores product-related data. Alternatively, one database
can store current customer order data, and another; related database can store historical customer
orders that are used for yearly reporting. Before you create a database, it is

important to understand the parts of a database and how to design these parts to ensure that the
database performs well after it is implemented.

Normalization theory:
Relations are to be normalized to avoid anomalies. In insert, update and delete operations.
Normalization theory is built around the concept of normal forms. A relation is said to be in a
particular form if it satisfies a certain specified set if constraints. To decide a suitable logical
structure for given database design the concept of normalization, which are briefly described
below.
1. 1 st Normal Form (1 N.F): A relation is said to be in 1 NF is and only if all
unaligned domains contain values only. That is the fields of an n-set should have no group items
and no repeating groups.
2. 2 nd Normal Form (2 N.F) : A relation is said to be in 2 NF is and only if it is in 1
NF and every non key attribute is fully dependent on primary key. This normal takes care of
functional dependencies on non-key attributes.
3. 3 rd Normal Form (3 N.F) : A relation is said to be in 3 NF is and only if it is in 2 NF and every
non key attribute is non transitively dependent on the primary key. This normal form avoids the
transitive dependencies on the primary key.
4. Boyce code Normal Form (BCNF) : This is a stronger definition than that of NF.
A relation is said to be in BCNF if and only if every determinant is a Candidate key.
5. 4 th Normal Form (4 NF) : A relation is said to be in 4 NF if and only if whenever there exists a
multi valued dependency in a relation say A->->B then all of the relation are also functionally
dependent on A(i.e. A->X for all attributes x of the relation.).
6. 5 th Normal Form (5 NF) OR Projection Join Normal Form (PJNF): A relation R is in 5 NF .if
and only if every join dependency in R is implied by the candidate key on R . A relation can’t be
non-loss split into two tables but can be split into three tables. This is called Join Dependency.
Implementation:

Implementation is the stage where the theoretical design is turned into a working system.
The most crucial stage in achieving a new successful system and in giving confidence on the
new system for the users that it will work efficiently and effectively.

The system can be implemented only after thorough testing is done and if it is found to work
according to the specification.

It involves careful planning, investigation of the current system and its constraints on
implementation, design of methods to achieve the change over and an evaluation of change over
methods a part from planning. Two major tasks of preparing the implementation are education
and training of the users and testing of the system.

The more complex the system being implemented, the more involved will be the systems
analysis and design effort required just for implementation.

The implementation phase comprises of several activities. The required hardware and
software acquisition is carried out. The system may require some software to be developed. For
this, programs are written and tested. The user then changes over to his new fully tested system
and the old system is discontinued.

TESTING:

The testing phase is an important part of software development. It is the puterized system
will help in automate process of finding errors and missing operations and also a complete
verification to determine whether the objectives are met and the user requirements are satisfied.

Software testing is carried out in three steps:

1. The first includes unit testing, where in each module is tested to provide its
correctness, validity and also determine any missing operations and to verify whether the
objectives have been met. Errors are noted down and corrected immediately. Unit testing is the
important and major part of the project. So errors are rectified easily in particular module and
program clarity is increased. In this project entire system is divided into several modules and is
developed individually. So unit testing is conducted to individual modules.

2. The second step includes Integration testing. It need not be the case, the software
whose modules when run individually and showing perfect results, will also show perfect results
when run as a whole. The individual modules are clipped under this major module and tested
again and verified the results. This is due to poor interfacing, which may results in data being
lost across an interface. A module can have inadvertent, adverse effect on any other or on the
global data structures, causing serious problems.

3. The final step involves validation and testing which determines which the
software functions as the user expected. Here also some modifications were. In the completion
of the project it is satisfied fully by the end user.
Login

Sign in
Add member

Edit member
Delete book
WEBSITES:
www.google.com
www.microsoft.com