REPORT

Description OF PROJECT
LIBRARY MANAGEMENT SYSTEM
The project titled Library Management System is Library
management software for

monitoring

and controlling the

transactions in a library. The project Library Management System

is developed in C# Asp.Net, which mainly focuses on basic
operations in a library like adding new member, new books, and
updating new information, searching books and members and
facility to borrow and return books.
Library Management System is a windows application
written for 32-bit Windows operating systems, designed to help
users maintain and organize library. Our software is easy to use for
both beginners and advanced users. It features a familiar and well
thought-out, an attractive user interface, combined with strong
searching Insertion and reporting capabilities. The report generation
facility of library system helps to get a good idea of which are the
books borrowed by the members, makes users possible to generate
reports hard copy.

The software Library Management System has four main modules.

 Insertion to Database Module User friendly input screen

Extracting from Database module Attractive Output Screen
Report Generation module borrowed book list & Available book
list
Search Facility system search for books and members

PROJECT
CATEGORY
RDBMS stands for Relational Database Management System.
RDBMS data is structured in database tables, fields and records. Each
RDBMS table consists of database table rows. Each database table row
consists of one or more database table fields. RDBMS supports
systematic treatment of null values. It supports data definition, data
manipulation and transaction management, and integrity constraints. And
the information present in one database can be distributed to different
databases. Essentially, an RDBMS moves data into a database, stores the
data, and retrieves it so that it can be manipulated by applications.

RDBMS store the data into collection of tables, which might be

related by common fields (database table columns). RDBMS also provide
relational operators to manipulate the data stored into the database
tables. Most RDBMS use SQL as database query language.
The most popular RDBMS are MS SQL Server, DB2, Oracle and My SQL.

Features of RDBMS:

Uses OOPs concept

Access control

Conflict resolution

Backup / Recovery

Highly secured

Multiple users can access which is not possible in DBMS

Avoids data redundancy problems using NORMAL FORMS

It performs all DML operations which is not possible with

ordinary DBMS

Supports data Independence

Finally, it supports DBMS concepts too.

TOOLS & PLATFORM

HARDWARE AND SOFTWARE REQUIREMENT SPECIFICATIONS:

The installation of the software is very easy but it is to be ensured by the
user that the following hardware & software requirements are met at the
time of the installation.

1.Software Requirement Specification:

a) Software Tool
Front End: The languages used at front-end are Asp.Net, C#
The causes of selecting this language are:
Highly technical language.
User friendly environment of working.
Provide low cost solution to the project.
GUI feature.

Better designing aspects for developers.

Back End: The Database used is SQL Server 2012

Important features of SQL Server 2005 are:
It provides better security aspect to the System.
Better portability that enables user to be flexible on work
Can manage large amount of data.
It provides reliable system with better integrity and validity of data.

IDE Used:
The integrated Development Environment is Microsoft ASP.Net

b) Platform Used: Windows XP, Windows Vista, Windows 7 or

Above

2. Hardware Requirement Specification:

The required hardware combination for this project will be as following: -

Hardware Specification:
Requirements

Minimum

Preferred

Processor

Pentium 3

Pentium 4 or higher

Speed

850 MHz

2.8 GHz or greater

Main Memory

128 MB

256 or higher

HDD

2.2 GB

2.4 GB or higher

FDD

1.44 MB

1.44 MB

Monitor

15-inch SVGA colored

Advanced

Mouse

Normal mouse

PS2-Port

Scroll

Mouse/Optical Mouse
Printer

Normal Inkjet

Laser Printer

Key Board

101/102 keys keyboard

Multimedia Keyboard

FEASIBILITY STUDY
Before getting started on the new system it was important to
determine the feasibility involved in the developed system so that the new
system development could be develop. Feasibility is the determination of
whether or not a project is not worth doing. The project followed in making
this determination is called a feasibility study. This type of study
determines if a project can and should Be Taken. Once it has been
determined that project is feasible, the analyst can go ahead and the
prepare the project specification which finalizes project requirements.

Generally, feasibility studies are undertaken within tight time

constraints and Normally culminate in a written and feasibility report.
The developed system is started after considering the main three type of
feasibilities which are discussed below: 1)-Technical feasibility
2)-Operational feasibility
3)-Economic feasibility
Technical Feasibility: - As we know the technical feasibility is concerned
with specifying equipment and software that will successfully satisfy the
user requirement. The technical needs of the system may very
considerably, but might include:
The facility to produce outputs in a given time.
Response time under certain conditions.
Ability to process a certain volume of transaction at a particular
speed.
Facility to communicate data to distinct location.
operate and communicate smoothly.
Economic Feasibility: Economic analysis is the most frequently used technique for
evaluating the effectiveness of a proposed system. More commonly
known as cost/benefits analysis the procedure is to determine the
benefits and savings that are expected from a purposed system and
compare with costs.
If benefits outweigh cost, a decision is taken to design and
implement the system otherwise further justification or alternative in the

proposed system will have to be made if it is to have a chance of being

approved. This is an ongoing effort that improves in accuracy at each
phase of the system life cycle.

Operational Feasibility: Proposed projects are beneficial only if they can be turned into
information system that will meet the operating requirements of the
organization. This test of feasibility asks if the system will work when it
developed and installed. Are there major barriers to implementation?
Some of the important questions that are useful to test the operational
feasibility of a project are given below:
Is there sufficient support for the project from the implementation?
From user? If the present system is well liked and used to the extent
that persons will not be able to see reasons for change, there may
be resistance.
Are current business methods acceptable to the user? If they are
not, user may welcome a change that will bring about a more
operational and useful system.
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 performs 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.

Data Flow Diagram

(DFD)

DATA FLOW DIAGRAM ZERO LEVEL

Authorized

password

user name

Login P(0.0)

Authentication

Administrator
(Library teacher)

Data base
SQL Server 2012

DATA FLOW DIAGRAM ONE LEVEL

TRANSACTION
P(1.4)

ADMIN P(1.1)
ISSUE
BOOK

USER
MASTER

CHANGE
PASSWORD

TRANCTI0
ON
REPORT

Administrator
P(1.0)

HELP P(1.5)

BOOK P(1.2)
HELP

BOOK
MASTER

SEARCH
BOOK

MEMBER P(1.3)

BOOK
STATUS

MEMBER
MASTER

Data base
SQL Server
2012

SEARCH
MEMBER

E-R DIAGRAM
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
represent 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-tomany, and many-to-many. A one-to-one (1:1) relationship is when at most
one instance of an 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
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.

ENTITY RELATIONSHIP DIAGRAM

(ERD)

Author

publisher
Book
title

SQL Server
20012
Database

Add
books

Book

Book-id

Recei
ved
Transact
ion

keywor
d

category

Year
publ

Transaction
report
Member

Member

Received
Book

id

Receive
date

Book
issue
d

Detail
s

Member
name

BookId

BookName

Issue
Book

Book
name

MemId

Issue
date

Add
mem
ber

LibraryMember

Mobile

no

Email

Edition
Author

BookId

Return
Book

MemId

Edition

BookName
Author

title

Membe
r id

Name
Address

title

Book
nam