T.Z.A.S.P.

MANDAL`S
PRAGATI COLLEGE OF ARTS, COMMERCE, AND SCIENCE

A CASE STUDY REPORT ON


PRESENTED ON:
ABLY GUIDED BY Madam Mrs.Rupali Patil
S.Y.B.Sc. (IT)
SUBMITTED BY
1. Ms. Ashwini Vaykole - Roll No. 14
2. Ms. Ashwini Godage - Roll No. 15



T.Z.A.S.P.MANDAL`S
PRAGATI COLLEGE OF ARTS, COMMERCE, AND SCIENCE
S.Y.B.Sc. (IT)




This is to certiIy that Ms. Ashwini Jaykole #oll No. 14)
Ms. Ashwini Codage #oll No. 15).Has completed the case study oI
soItware engineering satisIactorily during academic year 2009-10.


Date: 19 Mar`2010






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


#%A%


INDEX
Sr. No. Contents Page No.
1. Organization Overview
2. Current System
3. Limitation oI Current System
4. Proposed System
O Advantages
O Features
O Limitation
5. Entity-#elationship Diagram
6. Data Flow Diagram
O Context Level Diagram
O Context Analysis Diagram
O Functional Decomposition
O DFD Fragmentation
7. System Flow Chart
8. Structure Chart
9. Menu Tree
10. Table Listing
11. #eport Listing
12. Form Layout
13. GNATT Chart
ORGANIZATION OVRVIEW

PROBLEM DEFINITION

This case study oI library management system gives us the complete
inIormation about the library. We can enter the record oI the new books & retrieve
the details oI books available in the library. We can issue the books to the student
& maintain their records & can also check how many books are issued & stock
available in the library. In this case study, we can maintain the late Iine oI the
student who returns the issued books aIter the due date.
Throughout the case study, the Iocus has been on presenting
inIormation & comments in an easy & an intelligible manner. The case study is
very useIul Ior those who want to know about library management system.


CURRENT SYSTEM

All librarians currently operate all its administrations using handwritten
Iorms or slips stored in drover Iiles). The handwritten inIormation may also cause
some clashes in the records such as missing a particular slip or maintaining the
records in large librarian. It is also diIIicult to search a particular record Irom a
bunch oI records. So to avoid the problem arises, we need an automated system
that keeps a track oI all the records & related inIormation.




DRAWBACKS OF CURRENT SYSTEM

O Lack oI immediate inIormation retrieval
O Lack oI immediate inIormation storage
O Lack oI prompt updating
O Lack oI storing large inIormation
O #edundancy inIormation
O Fast report generation is not possible
O Tracing a book is diIIerent
O No central database can be created, as inIormation is not available in
database















PROPOSED SYSTEM

We want to develop library management system a comprehensive
library management solution that is suitable Ior both large &small libraries which
has Ilexible design & which enables library management system to be installed in a
range oI library organizations ranging Irom public libraries through to academic
joint use & special libraries. Proposed system provides with Iollowing solutions:-
O It provides 'better & eIIicient service to members.
O #educe the workload oI employee.
O Faster retrieval oI inIormation about the desired book.
O Provides Iacility Ior proper monitoring reduce paper work & provide data
security.
O All details will be available on a click.

The system is to be developed is intended to support day-to-day
operations oI library management system by improving various processes such as
O Issue a book
O #eturn a book
O Search a book and so on.







ADVANTAGES OF PROPOSED SYSTEM

O Immedaitated retrieval oI inIormation
O etter storage capacity
O etter sorting oI eIIicient reports
O "uick sorting oI inIormation
O Preparation oI eIIicient reports
O Accuracy oI data that is no redundancy hence no inconsistency
O Easy to update the inIormation


FEATURES OF THE PROPOSED SYSTEM

Library management system has been design to automate, manage, and look
aIter the overall processing oI very large-scale libraries. This soItware is capable oI
managing book issues returns, magazines or newspaper subscription, calculating or
managing Iine and balances oI payments due Irom members.

Moreover, this soItware is Iully compatible with barcodes based
management. Use oI bar codes Ior library management eases the everyday tasks oI
big libraries, where the number oI transaction exceeds several thousands in
number.



The key Ieatures oI system are-

O ook and reader record management with the help oI barcodes
O Customizable grouping oI members under various categories and classes
O Customizable Iine setting Ior various category oI members
O Members Iine balance management capacity
O PowerIul search Iacility Ior book and member search based on various
search criteria
O Magazine or newspaper subscription Iacility
O Complete management oI records oI book donor, vender, publisher, author,
locations, subject, categories, rack shelI etc.
O ook reservation Iacility
O Database backup and restore Iacility

LIMITATIONS OF PROPOSED SYSTEM
O The system will run under Windows98 or later operating system
O UnixLinux)Operating system is not supported
O All Iunctions will be developed in Turbo C as Iront-end tool.
O S"L should be installed Ior database handling.






ENTITY RELATIONSHIP DIAGRAM

The entity relationship model is a popular high-level conceptual data
model. It is a detailed, logical representation oI data or an organization Ior a
business area. The E-# model is very useIul Ior mapping the meanings and
interactions oI real world enterprises onto a conceptual schema the E-# diagram
drawn below shows the entities in library management system, the relationship
among the entities and attributes oI both entities and their relationships



















8eserve
8eservedaLe
MalnLaln
keeps
Lrack
ld
S1All
name
8LuL8S
ld name
lname
Lname
Mname
8ollno Class
hone no
Logln
Au1PL1lCA1lCn
S?S1LM
user name assword
8CCkS
AuLhor
ubllsher
S8 no
rlce
lS8n
1lLle
CaLegory
lssue
lssuedaLe

8eLurn
8eLurndaLe
DATA FLOW DIAGRAM (DFD)


The DFD represents how the data will Ilow in the system when it is
build. In this modeling, the major Iunctions in the soItware are identiIied. Diagram
shows how data will Ilow through diIIerent processes or Iunctions. From the
context level diagram we examine high-level Iunctional requirements oI the system
so main modules can be represented in level one oI DFD using DFD notations.
Thus, DFD is a hierarchical graphical model oI the system that shows diIIerent
processing activities oI each processing module that the system perIorms and data
is interchanged among these Iunctions. This whole unit is represented in the Iorm
oI diIIerent levels such as level 1, level 2, levle3.DFDs) capturing the detailed
structure oI the system as perceived by the user.









































SLored ln
llnL S?S1LM
2
Add

LxecuLes
S?S1LM ulSLA?
3
ueleLlon
4
rocess
password
3
Access
granLed
6
Access
denled
Command
Command
Command daLa
Show
ulsplay
ulsplay
valld
lnvalld
ueleLe from
Ll88A8? S1All
10
CompleLe
flne
8CCkS
7
lssue
9
8eLurn

8
ulsplay
sLaLus
updaLe
updaLe
Command
Command
uue over
CollecL
8eLurn
lssue
lssue
Pandle
deLalls
S1uuLn1
11
Modlfy
/lnserL
MalnLaln
SLudenL
1
8eserv
aLlon
8LC81S
13
ulsplay
sLaLus
SLore deLalls
8eservaLlon
ulsplay
12
8ook
search
Command
Command daLa
Command daLa
SLudenL daLa
Command daLa
CONTEXT LEVEL DIAGRAM

The context level diagram is the most abstract data Ilow representation
oI system. It represents the entire system as a single bubble. The main Iunction oI
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 arrows. The context level diagram Ior library management system
includes six external entities as shown in Iigure given below.














llnL S?S1LM
8LC81S
ulsplay
8CCkS
SLudenL recelves
ulsplay lnfo
S?S1LM ulSLA?
LxecuLes
Ll88A8? S1All
8eLurn book
lssue book
AuLhenLlcaLlon
Add/deleLe lnfo
MalnLaln reader lnfo
L|brary
management
system
Search book
S1uuLn1
8eserve book
CONTEXT ANALYSIS DIAGRAM


















LI#A#
8LAuL8

LI#A#
MANAGEMENT
SSTEM
Find book
Check availability
Ask book
Issue book
Ask Ior reserving books
Permits the reservation oI book
Show status
II present then show details
CONTEXT LOGICAL DIAGRAM





















8ook lssue
S1uuLn1
8ooks
Send dues
8equesL membershlp
S1uuLn1

MLM8L8SPl
MAnCLMLn1
Member deLalls
lnformaLlon
Member
Send penalLy reporL
8equesL for book
8ook lssue deLalls
8eLurn book
8emlnder
enalLy amounL
enalLy
MAnACLMLn1

8LC81
MAnACLMLn1
Send reporL
8equesL for reporL

8ook lssue
managemenL
lssue deLall
8ook deLalls
Send deLalls
8equesL for dlsconLlnuaLlon
FUNCTIONAL DECOMPOSITION

Each bubble in the DFD represents the main Iunction, we decompose
it Iurther, and at every step, we derive the next level DFD as shown in diagram
given below
This process is also called exploding a bubble. This process is carried
out until no Iurther decomposing oI a bubble is possible. This method helps in
keeping track oI main processes and its sub processes. The main processes have
integer numbers 1, 2, 3..etc. When the bubble is decomposed then the sub
processes are numbered as 1.1, 1.1.1, 1.1.2.and so on.












0
Ll88A8?
11
8CCk
12
8LAuL8
1
SLA8CP
2
18AnSAC1lCn
21
lSSuL
22
8L1u8n
3
uuA1L
32
8CCk
uA1A8SL
31
8LAuL8S
uA1A8AS
4
8LC81S
41
llnL
42
8CCk
DFD FRAGMENTS


















"uery
1
Search
ook
#eader
2
1ransacLlon
#eturn
Issue
Update
3
Update
ook
Updated ook
#eader
Updated #eader
4
Produce Library
#eport
Librarian
#eader
ook
SYSTEM FLOW CHARTS

System Ilow charts are very similar to data Ilow charts.A system
Ilowchart explains how a system works using a diagram. The diagram shows the
Ilow oI data through a system. A systems Ilowchart shows the key inputs and
outputs associated with the program. The shapes oI the symbols indicate the types
oI input or output devices. System Ilowcharts are a way oI displaying how data
Ilows in a system and how decisions are made to control events.The symbols are
linked with directed lines lines with arrows) showing the Ilow oI data through the
system.












8LAuL8
Ll88A8?
18AnSAC1lCn
SL8vlCLS
updaLe
updaLe
8CCkS
8ook
deLalls
8eader
daLabase
8eader
enLers
8LC81
CALCuLA1L
llnL
llne
8LC81
STRUCTURE CHART

Structured chart are not Ilow charts because there is no indication oI
processing sequence and it has no decision boxes. In short, structured chart depicts
the structures oI subroutine in the system and data passed between routines can be
indicated on the arcs connecting routine as shown in Iigure.
The stricter chart is drawn by Iirst drawing the root modules and the
modules that it invokes. Next one Iunctional component Ior the central transIorm
i.e. the remaining portion oI DFD) and the aIIerent i.e. logical Iorm oI input data)
and eIIerent i.e. physical Iorm oI input data) branches are added below the root
module. In the third step, the structure chart is Iurther deIined by adding sub
Iunctions under each oI the Iunctional components. Many levels are added under
the Iunctions and this process is called as Iactoring. The stricter chart Ior library
management system is as shown in the Iigure given below:-








Ll88A8? MAnACLMLn1
S?S1LM
8CCkS
S1All
C1PL8S
nLWS
AL8S
8LlL8LnCL
8CCkS
CuLS1lCn
AL8S
1Lx1
8CCkS
Ll88A8lAn
MACZlnLS
nCvLLS
8LAuL8
S1uuLn1 C1PL8S 1LACPL8S
C1PL8S
MENU TREE


















8ln1 8A8CCuLS
8ln1 LA8LLS
8LAuL8 uL1AlL
uLLL1L
vlLW
Auu
S1uuLn1
uLLL1L
vlLW
Auu
1LACPL8
uLLL1L
vlLW
Auu
C1PL8
Ll88A8? SL8vlCLS
uLLL1L
vlLW
Auu
MAln
LlS1
CLLA8
CPLCk
8LSL8vL
8L1u8n
lSSuL
18AnSAC1lCnS
lnlC8MA1lCn
SLA8CP
Auu 8CCk Ln18?



















A8Cu1
CllLlnL
CnLlnL
PLL
CuL8lLS
llnL S1A1uS
uCCuMLn1S CvL8uuL
uCCuMLn1S uuL AS Cn
uCCuMLn1S 8LSL8vLu Cn
uCCuMLn1S lSSuLu Cn
LlS1 ClCu88Ln1 lSSuL
lSSuL LlS1 Cl An? MLM8L8
SLA8CP ll lSSuLu
LCnC 1L8M lSSuL
Lxl1
AuMln
Auu
vlLW
uLLL1L
TABLE LISTING

Issue: Table

Sr. No. Field Name Data Type Size
1 no int 25
2 Id int 30
3 Issuedate Date/time 10
4 Duedate Date/time 10
5 Copiesavailable int 2

Admin: Table

Sr. No. Field Name Data Type Size
1 Name Char 25
2 Date int 10
3 Time int 20
4 Password Char 6
5 Id int 10


Student: Table







Teacher: Table









Sr. No. Field Name Data Type Size
1 Id int 30
2 #ollno int 3
3 Name Char 25
4 Class Char 20
5 ook issued Char 10
Sr. No. Field Name Data Type Size
1 Id int 30
2 Name Char 25
4 ook title Char 20
5 ook issued Char 10
ook: Table

Sr. No. Field Name Data Type Size
1 no int 10
2 ISN int 10
3 Subject Char 10
4 Name Char 25
5 Author Char 20
6 Publisher Char 20
7 Editor int 10
8 Copies int 2
9 Cost int 5


Issue return: Table

Sr. No. Field Name Data Type Size
1 no int 11
2 Id int 20
3 Issuedate Date/Time 10
4 Duedate Date/Time 10
5 #eturndate Date/time 10
6 Fine int 3
7 Copiesavailable int 2

REPORT LISTING

O #eaders #eport
O Issue-#eturn #eport
O Search Category #eport
O #eaders #ecord Ior Issue-#eturn ook
O Fine Generation #eport
















Name:
Class: Div:
#oll No: #eaderid:





The #eader Named Name oI #eader) having class class and
division) and #eaderid #eaderid) issued Number oI books)
On Issue date)



O ook 1 ISN 1
O ook 2 ISN 2
O ook 3 ISN 3




READERS RECORD
HISTORY OF BOOKS ISSUED AND RETURNED BY READER

Name:
Class: Div:
#oll No: #eaderid:

History oI ooks Issued and #eturned:
Sr. No. ook Name ISN No. Issued on #eturn on







Long Term Issue:
Total Fine:




FINE GENERATION REPORT

Name:
Class: Div:
#oll No: #eaderid:

ook Name:

Issued On: Due On:

Fine:




A reader Name) issued a book ook Name) on Issue Date) but do
not return the book on #eturn Date).The Iine submitted by the student will be
Fine).





RECORD OF TEACHER
Name:

#eaderid:

Number oI ook Issued:

List oI ooks:

Sr. No. ook Name ISN No. Issued on








Teacher Teacher name) has issued Number oI ooks)
on Issue Date).





RECORD OF BOOKS FOR A PARTICULAR CATEGORY

Category:
Number oI ooks Present:
Having ISN Irom: to .
List oI ooks:
Sr. No. ook Name ISN No. No. oI Copies Cost ShelI No.







The library has Number oI ooks) Ior Category) as listed above






GNATT CHART
Gantt charts have become a common technique Ior representing the
phases and activities oI a project work breakdown structure WS), so a wide
audience can understand them.
A Gantt chart is a type oI bar chart that illustrates a project schedule.
Gantt charts illustrate the start and Iinish dates oI the terminal elements and
summary elements oI a project. Gantt charts can be used to show current schedule
status using percent-complete shadings and a vertical "TODA" line as shown
here. A Gantt chart is a graphical representation oI the duration oI tasks against the
progression oI time. A Gantt chart is a useIul tool Ior planning and scheduling
projects. A Gantt chart is helpIul when monitoring a project's progress.










Project
Search
System
Design
Data Process
and Modeling
Investigating
System
#equirement
nov ues leb !an Mar
Planned Date
Actual Date

Extende
d Date


FORM LAYOUT



























Bibliography
http://www.scribd.com

http://www.brainmass.com

www.dotnetspider.com

http://www.cragsystems.co.uk/ITMUML/inde.

How to draw Data Flow Diagrams