0% found this document useful (0 votes)
724 views36 pages

(PDF) Library Management Sytem

This document is a case study report on a library management system presented by students from Pragati College of Arts, Commerce, and Science. It provides an overview of the current manual system and its limitations. It then proposes developing an automated library management system with features such as book and member management, borrowing and returning books, and fine management. Entity relationship and data flow diagrams are included to model the system's data and processes.

Uploaded by

Harry Poter
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
724 views36 pages

(PDF) Library Management Sytem

This document is a case study report on a library management system presented by students from Pragati College of Arts, Commerce, and Science. It provides an overview of the current manual system and its limitations. It then proposes developing an automated library management system with features such as book and member management, borrowing and returning books, and fine management. Entity relationship and data flow diagrams are included to model the system's data and processes.

Uploaded by

Harry Poter
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 36

T.Z.A.S.P.

MANDAL’S

PRAGATI COLLEGE OF ARTS, COMMERCE, AND SCIENCE

A CASE STUDY REPORT ON

Library Management
System
PRESENTED ON:

ABLY GUIDED BY Madam Mrs.Rupali Patil

S.Y.B.Sc. (IT)

SUBMITTED BY

1. Ms. Ashwini Yaykole - Roll No. 14


2. Ms. Ashwini Godage - Roll No. 15
T.Z.A.S.P.MANDAL’S

PRAGATI COLLEC E OF ARTS, COMMERCE, AND SCIENCE

S.Y.B.Sc. (IT)

This is to certify that N.i. shwini Yaykole (Roll No. 14)


Ms.Ashwini Bedale{Roll Nu.IS).Hascompleted the case study ui
software engineering satisfactorily during academic year 2009-10.

Date: 19 NIar’2010

Professor-in-charge
(B.SC.IT)
INDEX

Sr. No. Contents Page No.


1. Organization Ov erview

2. Current Systern
3. Limitation ol Current System
4. Proposed System
• Advantages
• Feature s
• Limitalion
Entity-Relationship Diagram
6. Data Flow Di‹qy’am
• Context Level Diagram
• Context Analy sis Diagram
• Functional Decomposition
• DFD Fragmentation
7. System Flow Chart

Strrictui e Charl
9. Menu Tree
10. Table Listing
11. Report Listing

1 2. Form Layout
13. GNATT Char i
OR ANIZATION OVRVIEW

PROBLEM DEFINITION

This case study of library management system gives its the coiiiplete
infoi ination about the library. We chin enter the recoi d o1’ ihe new books & i eLl ieve the
details ol books available in the library. We can issue the books to the student &
maintain their records & can also check how many books are issue d & stock available
in the lil rary. In this case study, we can maintain the late line ol the student who returns
ihe issued books al’ter the due date.
Throughout thc case study, the locus has been on presenting iiiformittion
& comments in an easy & an intelligible manner. Thc case stutly is
very usclul lor ihose who want to know about libi ary iiianage intent
system.

CURRENT SYSTEM

All librarians currently operate all its administrations using h iBdwritien


lot me or slips stored in ‹irovei (files). The handwritten in formation iiiay also cause
some clashes in thc records such as missing a particular slip or maintaining the
records in large librarian. It is also di1’iicult to search a particular record from a bunch
of records. So to avoid thE problciii ai ises, we need an automated sy stem that keeps a
track of all the records & related iiil’oriuation.
DRAWBACKS OF CURR ENI’ SYSTEM

• Lack of immediate inlormation retrie 'al


• Lack of immediate inlorniation storage
Lack of prompt updating
• Lack o1 storing large inloriiiaiioo
• Redundancy information
• Fast report generation is not possible
• Tracing a book is different
• No central database can be
created, as inloriuation is
nor availablc in
database
PROPOSED SYSTEM

We want to develop library iiianagernent systcin a comprehensive library


management solution that is suitable lor both large &snah libraries which has flexible
clesign & which enables library management system to be installed in a range ol libi ary
organizations ranging lrom public libraries through to academic joint use & special
libi aries. Proposed system provides with lollowing solutions: -
It provities “better & eliicient” service to members.
• Reduce the wtirkload of employee.
• Master retrieval of information abotit the desired book.
o Proc ides facility lor proper monitoring reduce paper work & provide
data
sccurity.
• All details will be available on a click.

The system is to be developed is intended to


supptirt tlay-to-day
opei ations o1 library management sysiein by improving various processes such as
• Issue a book
• Return a book
Search a book and so on.
AIIVANTAC ES OF PROPOSED SYS’l’EM

• Imniedaitate‹l retrieval of information


• Better storage capacity
• Better sorting ol el ficient reports
• Quick sorting of information
• Preparation of e1 ficient reports
• Accuracy ol‘ data that is no redundant y hence no inconsistency
• Easy to uprlate the in formation

FEATURES OF THE PROPOSED SYSTEM

Library iiianagenient has been design to automate, manage, and look after
the overall processing or very large-scale libraiñ es. This soft ware is capable of
managing book issues returns, magazines or ne wspapcr subscription, calculating or
managing line and balances of payments due morn members.

Moreover, this software is lully compatible wiih baicodes based


management. Use of bar codes for library management eases the everyday tasks of big
libi ai ies, where the number of transaction exceeds several thoiis:iuds iii number.
The key features of system are-

• Book anal matter recorcJ inanageiiient with ihe help o1 barcodes


• Customizable grouping of members under various categories and
classes
• Customizable fine setting lor various categoi y tel members
• Meinbei s fine balance iiianapernent capacity
• Powerful search lñ cility for book anal member search based on
various
scarch crileria
• Magazine or ne wspaper subscripi ion laciCity
• Complete management ol records o1’ book donor, vcnder, publisher,
auihor, locations, subject, categories, rack shell etc.
• Book reservation facility
• Database backup and restore facility

LIMITATIONS OI PROPOSED SYSTEM

• The system will i tin under Wiiidows98 or later operating system


• Unix(Linux)Operating system is not supported
• All lunctioiis will be developcd in Turbo €++ as front-
end tool.
• SQL shoul‹i be installed lor database handling.
ENTITY RELATIONSHIP DIA RAM

The entity relay ionship model is a popular high-level c‹ineeptual data


model. It is a detailed, logical representation of data ‹ir an organization lor a business
area. Thc E-R model is vcry usetul f‹ir mapping ihe meanings and iiiteractitins ol real
worlcl enterpriscs onto a conceptual schema the E-R diagram drawn below shows thc
entities in libi ary inanageiiient systems, thc relationship aint›ng ihe entities and
attributes ol both entiiies and theii relationships

User name Password

SYSTEM
Name

STAFF Maintain

F-name Issue-d
ate Author
Keeps Issue
M-name

Reserve-date Publisher
Name BOOKS

Price

REDERS Reserve

ISBN
Title

Class Return

Return-date
DATA FLOW DIAC RAM (DFD)

The DCD represents how ihe data will how in the system when it is
build. In this iiiodeling, the major 1 unctions in the so1’tware are identificd. Diagram
shows how daia will how through ‹lil’lerent processes ter l’unctioiis. From the context
level d i a l am we examinc high-level functional requirements of the system so main
modules can be represented in level one of DFD tieing DFD notations. Thus, DFD is a
hierarchical graphical moclel of the system that show s different proce suing activities
of each processing iiiodule that the system performs and dicta is interchanged among
these l‘unctions. This whole unit is ieprcsentcd in the form of dif l’erent levels (such as
level 1, level 2, levle3.. .DFDsJ capturing the detailed structure oi’ the system as
perceived by the user.
Comm

nd
search

Student data Shore details


Reserv Reservation
Command data ati on

Modify Maintain
Student

Update
Issue
Issue

details Command
Return Issue BOOKS

LIBRARY STAFF
Due over

Command
10
Complete Executes
fine FINE SYSTEM

Show
Stored in

Command data
SYSTEM DISPLAY

Access
granted
Process

Access
denied
CON’l’EX’l’ LEVEL DISC RAM

The context level diagram is ihe most abstract data flow representation o1
system. It represents the entire system as a single bubble. The retain l‘unction ol the
system is mentioned in the bubble and the external entities with which this system
interacts is represented. The incoming data and outgoing data are represented as
airows. The context level diagram ioi library management sy stent includes six external
entities as shown in Iigure given below.

Reserve book Student receives


BOOKS

FINE SYSTEM
Search book

Maintain deader info


management Executes
Add/delete info SYSTEM DISPLAY

Authentication

Issue book
REPORTS
LIBRARY STAFF
CON’l’EX’l’ ANALYSIS DISC RAM

'ind bi›ti

LfB RARY
LIBRARY
SYS›TEM
Check iI 'ai l•I
3ilit

Permits the rescrvai itiii ul’ bot›k


CON’l’EX’l’ LOGICAL DISC RAM

STUDENT
MANAGEMENT

Request members
Send re
ip
art
Send etails
Reque t for report

Reouest for disco *mation MEMBERSHIP

MANGEMENT
Member is REPORT
MANAGEMENT

Infor ion Penalty


Member Pena t mount

Book issue
management

Book Issue etails Books

Issue ail
Retur boo
Reo st f r book

Se penalty report Book Issue

minder
STUDENT
FUNCTIONAL DECOMPOSITION

Each bubble in the DFD represents the iiiain function, we deetiiiipose it


furthei, and at every step, we derive the next level DFD as shown in diagram given
below
This process is also called e xplo‹1inp a bubble. This piocess
is carried
out until no further decomposing ol a
bubble is possible. This method helps in
keeping track o1 main piocesses and its sub piocesses. The main
processes have integer numbers I, 2, 3. . . .etc. When the bubble is
decomposed then the sub
LIBRAR
processes are numbered as 1.1, 1.1. 1, 1.1 .2. . .: ind so on.
Y

SEARCH REPORTS

BOOK ISSU FIN


E DATABAS D
E
TABSE
DFD FRAGMENT’S

Book

Search

Transaction pdate
Retarn

er

Book
Librarian
Produce Library
Reader
SYSJ’EM FLOW CHAR’I’S

loo wchart explain s how a system works using a diagram. The diagram shows ihe how
ol data through a sy stent. A systems llowchart shows the key inputs anal outputs
associated with the program. The shapes ol the sy nibols indicate the types oi input or
output devices. S y stern l4tiwL llitl*l s itlc a way of mlisplit }'inJ how data how s in a sy ste in
and how dec isions iii c made to c thai ol ct ents.The sy nibols are linked with directerl
lines (lines with anowe) showing the how of data through the system.

Reader
database
Reader REPORT
enters

TRANSACTION U pd
ate
CALCULATE
LIBRARY
FINE

SERVICES

REPORT
BOOKS
Fine

Book
detas
STRUCTURE CHA RJ’

Structui ed chart are not flow charts because ihere is no indication ol


proce suing sequence and it has no decision boxes. In shori, structured chart depicts
the structures of subroutine in the system anal data passed between routines can be
indicated on the ‹mcs connecting routine as shtiwn in figure.

The stricter chart is drawn by first drawing rite rout iuodulcs and the
modules that it invokes. Next one luiici ional component for the central ti ansform (i.e.
ihe remaining portion o1 D r D › u»d the allerent (i.e. logical lonii ol input data)
-und ci ferent (i.e. phy sical loom of’ inpul data) branches are added below ihe root
module. In the third step, the structure chart is further delinerl by adding sub functions
under each ol the I unctioniil components. Many ie vets are added under the 1 unctitins
and this process is called as laciorinu. The stricter chart for library management sy
stew is as shown in the ligiire given below:-

LIBRARY MANAGEMENT
SYSTEM

BOOkS STAFF

STUDENT TEACHERS OTHERS TEXT REFERENC LIBRARIAN OTHERS


NOVELS OTHERS
BOOKS E BOOKS

QUESTION
PAPERS MAGZINES
MENU TREE
ADD

STUDENT
DELET
E

ADD

TEACHER

VIE
W

LIBRARY SERVICES

PRINT
LABLES

ISSUE

TRANSACTIONS RETUR CHEC


N K
RESERVE CLEA
R

INFORMATION

BOOK ENTRY ADD

SEARCH
SEARCH IF ISS ED

ISSUE LIST OF ANY MEM BER

LIST OFCURRENT ISSUE

DOCUMENTS ISSUED ON

QUERIES DCCC M ENT5 RESERV ED ON

DOCUMENTS DUE AS ON

DOCUME NTB

OVERDUE FINE STATUS

LONG TERM ISSUE

ADD

ADMIN

OFFLIN
E

EXIT
TABLE LISTIN€i

Issue: Table

Sr. No. Ficld Name Data Type Sizc

1 Bno
2 ld inl

lssue date Date/true IU


4 Dtie date Date/iiine 1()
5 Copies_available int 2

Admin: Table

Sr. Nt›. Field Name Data Type Size

1 Name Char 25
2 Date int 10
3 Tinge int 20
4 Pass word Char 6
S Id ini 10
Student: Table

Sr. No. Field Name Data Type

Roll
no
Name Char

Char
Book issued 1
tJ
Char

Teachei . Table

Sr. No. rield Name Data Type Size


I Id int 3t)
2 Name Char 25
4 Book title Char 2ti
5 Book issued Char It)
Book: Table

Sr. No. Field Name Data Type Size


1 B_no int IU
2 ISBN int 1()
3 Subject Char 11)

4 Name Char
5 Authoi Char
fi Publisher Char
7 Editor int
8 Copie s int
9 Cost int

lssue return: Table

Sr. No. Field Name Data Type Size


1 Bono int 11
2 ld int 20
3 Issue date Daic/Time 1 t)
4 Due date Date/Time 10
5 Return date Date/time l()
b Fine int 3
7 Copies_available int 2
itEPORT LISTING

• Readers Report
• I sane-Return Report
• Search Category Repoi t
• Reaclers Record lor Issue-Return Book
• Fine Generation Report
READERS RFCORD

Nanic:

Div:

Roll No:

The Reader Name‹l Name of Reader having class (class and


division) and Reader_id (Reader id) issued (Numbei of books)
On IIssue date)

• Book I—
ISBN 1
• Book 2 — ISBN
2
• Book 3 — ISBN
3
HISTORY OF BOOKS ISSUED AND RETU ftNED BY BEADER

Name:

Div:

Roll No: Readei id:

History ol‘ Books Issued and Returned:

Sr. No. Book Name ISBN No. Issued on Reiui n


on

Long Term Issue:

Total Fine:
FINE C ENERAJ’ION REPORT

Name:

Div:

Roll No: Readei id:

Book Name:

Issued On: Due On:

Fine:

A reader Nat issued a btiok (Book Name) on (Isstie Date) but do


not return the book Return Date linesubmitterl by the student willbe
on Fine
RECORD OF TEACHEit

Readei_id:

Number of Book Issued:

List of Books:

Sr. No. Book Name ISBN No. Issued on

Teacher (Teachef name) line issued (Number of


Books) on t Issue Date).
RECORD OF BOOKS FOR A PARTIC ULAR CATEC ORY

Category:

Number of Books Present:

Having ISBN from: t


o
List o1 Books:

Sr. No. Book ISBN No. No. o1 Copies Cost Sheli No.
Nature

Thc libi ary has Numbei of Books Cate as listed above


GNATT CHART

Gantt charts have become a common technique ior representing the


phases and activities of a project work breakdown structure (WBS), so a wide
audience can understand them.

A Gantt chart is a type of bar chart that illustrates a project schedule.


Gantt charts illustrate the start and finish dates of the terminal elements and summary
elements of a project. Gantt charts can be used to show current schedule status using
percent-complete shadings and a vertical ”TODAY" line as shown here. A Gantt chart
is a graphical representation of the duration of tasks against the progression of time. A
Ciantt chart is a useful tool for planning and scheduling projects. A Gantt chart is
helpful when monitoring a project's progress.

System
Design

Data Prucess
and Modeling

Actual Date

d Date

Investigating
System
Requirement

Project

Search

OV Jan Mar
FORM LAYOUT

Reader Admin

check reservation
clear reservation
list reservation
Enter the occoıuıt Nıunber

Meınber id

Naıne

Class
Fiııe Details
Msx.issııe Delayed fine
Lost Fiııe
Issııe on Daıııaqe Fiııe
Dııe
on

Issııe Retuııı Refieslı Caııcel


Ents the string to be searched

CällCRÌ
Boak number

ISBN number

Subject
Tital

Cost

Update Delete Add Re&esh


Bibliography

4• http://www.scribd.com

4• http://www.braininass.com

• www.dotnetsgider.coro

•t• htto://www.crag vstems. co.uk/lTMUML/inde. . .

•t• How to draw Data Flow Dia ams

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy