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)

CERTIFICATE

This is to certify that Ms. Ashwini Vaykole (Roll No. 14)

Ms. Ashwini Godage (Roll No. 15).Has completed the case study of
software engineering satisfactorily during academic year 2009-10.

Date: 19 Mar’2010

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

Sr. No. Contents Page No.

1. Organization Overview
2. Current System
3. Limitation of Current System
4. Proposed System
 Advantages
 Features
 Limitation
5. Entity-Relationship Diagram
6. Data Flow Diagram
 Context Level Diagram
 Context Analysis Diagram
 Functional Decomposition
 DFD Fragmentation
7. System Flow Chart
8. Structure Chart
9. Menu Tree
10. Table Listing
11. Report Listing
12. Form Layout
13. GNATT Chart
ORGANIZATION OVRVIEW

PROBLEM DEFINITION

This case study of library management system gives us the complete

information about the library. We can enter the record of the new books & retrieve
the details of 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 fine of the
student who returns the issued books after the due date.
Throughout the case study, the focus has been on presenting
information & comments in an easy & an intelligible manner. The case study is
very useful for those who want to know about library management system.

CURRENT SYSTEM

All librarians currently operate all its administrations using handwritten

forms or slips stored in drover (files). The handwritten information may also cause
some clashes in the records such as missing a particular slip or maintaining the
records in large librarian. It is also difficult to search a particular record from a
bunch of records. So to avoid the problem arises, we need an automated system
that keeps a track of all the records & related information.

DRAWBACKS OF CURRENT SYSTEM

 Lack of immediate information retrieval

 Lack of immediate information storage
 Lack of prompt updating
 Lack of storing large information
 Redundancy information
  Fast report generation is not possible
 Tracing a book is different
 No central database can be created, as information is not available in
database

PROPOSED SYSTEM

We want to develop library management system a comprehensive

library management solution that is suitable for both large &small libraries which
has flexible design & which enables library management system to be installed in a
range of library organizations ranging from public libraries through to academic
joint use & special libraries. Proposed system provides with following solutions:-
 It provides “better & efficient” service to members.
  Reduce the workload of employee.
 Faster retrieval of information about the desired book.
 Provides facility for proper monitoring reduce paper work & provide data
security.
 All details will be available on a click.

The system is to be developed is intended to support day-to-day

operations of library management system by improving various processes such as
 Issue a book
 Return a book
 Search a book and so on.

ADVANTAGES OF PROPOSED SYSTEM

 Immedaitated retrieval of information

 Better storage capacity
 Better sorting of efficient reports
 Quick sorting of information
 Preparation of efficient reports
 Accuracy of data that is no redundancy hence no inconsistency
  Easy to update the information

FEATURES OF THE PROPOSED SYSTEM

Library management system has been design to automate, manage, and look
after the overall processing of very large-scale libraries. This software is capable of
managing book issues returns, magazines or newspaper subscription, calculating or
managing fine and balances of payments due from members.

Moreover, this software is fully compatible with barcodes based

management. Use of bar codes for library management eases the everyday tasks of
big libraries, where the number of transaction exceeds several thousands in
number.

The key features of system are-

 Book and reader record management with the help of barcodes

 Customizable grouping of members under various categories and classes
 Customizable fine setting for various category of members
 Members fine balance management capacity
 Powerful search facility for book and member search based on various
search criteria
 Magazine or newspaper subscription facility
  Complete management of records of book donor, vender, publisher, author,
locations, subject, categories, rack shelf etc.
 Book reservation facility
 Database backup and restore facility

LIMITATIONS OF PROPOSED SYSTEM

 The system will run under Windows98 or later operating system

 Unix(Linux)Operating system is not supported
 All functions will be developed in Turbo C++ as front-end tool.
 SQL should be installed for database handling.

ENTITY RELATIONSHIP DIAGRAM

The entity relationship model is a popular high-level conceptual data

model. It is a detailed, logical representation of data or an organization for a
business area. The E-R model is very useful for mapping the meanings and
interactions of real world enterprises onto a conceptual schema the E-R diagram
drawn below shows the entities in library management system, the relationship
among the entities and attributes of both entities and their relationships

User name Password

AUTHETICATION SYSTEM
Login
Name Id
 STAFF Maintain

F-name Issue-date
Author
Keeps track SR no
Issue
M-name

Reserve-date Publisher
Name Id
BOOKS
Price
L-name
REDERS Reserve Category
ISBN
Phone no Title

Class Roll-no Return

Return-date

DATA FLOW DIAGRAM (DFD)

The DFD represents how the data will flow in the system when it is
build. In this modeling, the major functions in the software are identified. Diagram
shows how data will flow through different processes or functions. From the
context level diagram we examine high-level functional requirements of the system
so main modules can be represented in level one of DFD using DFD notations.
Thus, DFD is a hierarchical graphical model of the system that shows different
 processing activities of each processing module that the system performs and data
is interchanged among these functions. This whole unit is represented in the form
of different levels (such as level 1, level 2, levle3…DFDs) capturing the detailed
structure of the system as perceived by the user.

12
Command Book search Display
STUDENT REPORTS

Student data
1 13
Command data Reservation Store details Display status
Reservation
Command data
11
Modify/insert
Maintain
Student 8
Display status
7 Update
Issue Issue
Collect
Command data Handle details
Command 9
Return Update Return BOOKS
Issue

LIBRARY STAFF Command

Due over
 Complete fine
2 Executes
Add FINE SYSTEM

Command
Show
3 Stored in
Deletion
Delete from
Command data
SYSTEM DISPLAY
5
Access granted Display
4 Valid
Process password

6
Access denied
Invalid Display

CONTEXT LEVEL DIAGRAM

The context level diagram is the most abstract data flow representation
of system. It represents the entire system as a single bubble. The main function of
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 for library management system
includes six external entities as shown in figure given below.
 Reserve book Student receives
STUDENT BOOKS

Display info
FINE SYSTEM
Search book Library management system
Maintain reader info
Executes
Add/delete info SYSTEM DISPLAY

Authentication

Issue book Display

REPORTS
LIBRARY STAFF
Return book

CONTEXT ANALYSIS DIAGRAM

Ask book Find book

Show status
Issue bookLIBRARY MANAGEMENT SYSTEM
LIBRARY
READER
Ask for reserving books Check availability

Permits the reservation of book If present then show details

 CONTEXT LOGICAL DIAGRAM

STUDENT
MANAGEMENT
Send dues

Request membership
Send report
Send details
Request for report

MEMBERSHIP MANGEMENT
Request for discontinuation

REPORT MANAGEMENT
Member details

Information Penalty

Member Penalty amount

 Book details

Book Issue details Books

Issue detail
Return book
Request for book
Send penalty report Book Issue

Reminder
STUDENT

FUNCTIONAL DECOMPOSITION

Each bubble in the DFD represents the main function, we decompose

it further, 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 further decomposing of a bubble is possible. This method helps in
keeping track of 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
LIBRARY

1 2 3 4
SEARCH TRANSACTION UPDATE REPORTS

1.1 1.2 2.1 2.2 3.1 READERS DATABASE

3.2 BOOK DATABSE 4.1 4.2
BOOK READER ISSUE RETURN FINE BOOK

DFD FRAGMENTS

1 Book
Query Search
Reader

2
Issue Transaction
Update
Return
 3 Updated Book
Book Update

Reader Updated Reader

Book 4
Produce Library Report
Librarian

Reader

SYSTEM FLOW CHARTS

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

Reader database

Reader enters REPORT

READER

TRANSACTION Update
CALCULATE FINE
LIBRARY

SERVICES Update

REPORT BOOKS
Fine

Book details

STRUCTURE CHART

Structured chart are not flow charts because there is no indication of

processing sequence and it has no decision boxes. In short, structured chart depicts
the structures of subroutine in the system and data passed between routines can be
indicated on the arcs connecting routine as shown in figure.
 The stricter chart is drawn by first drawing the root modules and the
modules that it invokes. Next one functional component for the central transform
(i.e. the remaining portion of DFD) and the afferent (i.e. logical form of input data)
and efferent (i.e. physical form of input data) branches are added below the root
module. In the third step, the structure chart is further defined by adding sub
functions under each of the functional components. Many levels are added under
the functions and this process is called as factoring. The stricter chart for library
management system is as shown in the figure given below:-

LIBRARY MANAGEMENT
SYSTEM

READER BOOKS STAFF

READER TEACHERS OTHERS TEXT REFERENCE LIBRARIAN OTHERS

NOVELS OTHERS
BOOKS BOOKS

QUESTION NEWS
PAPERS PAPERS MAGZINES

MENU TREE
ADD

STUDENT VIEW

DELETE

ADD

READER DETAIL TEACHER VIEW

DELETE

ADD

OTHER VIEW

DELETE
 MAIN LIBRARY SERVICES VIEW

DELETE

PRINT LABLES

PRINT BARCODES

ISSUE

TRANSACTIONS RETURN CHECK

RESERVE CLEAR

LIST

INFORMATION

BOOK ENTRY ADD

SEARCH

SEARCH IF ISSUED

ISSUE LIST OF ANY MEMBER

LIST OFCURRENT ISSUE

DOCUMENTS ISSUED ON

QUERIES DOCUMENTS RESERVED ON

DOCUMENTS DUE AS ON

DOCUMENTS OVERDUE

FINE STATUS

LONG TERM ISSUE

ADD
 DELETE

ONLINE

HELP OFFLINE

ABOUT

EXIT

TABLE LISTING

Issue: Table
 Sr. No.  Field Name Data Type Size
1 Bno int 25
2 Id int 30
3 Issue_date Date/time 10
4 Due_date Date/time 10
5 Copies_available 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

Sr. No.  Field Name Data Type Size

1 Id int 30
2 Roll_no int 3
3 Name Char 25
4 Class Char 20
5 Book issued Char 10
Teacher: Table

Sr. No.  Field Name Data Type Size

1 Id int 30
2 Name Char 25
4 Book title Char 20
5 Book issued Char 10

Book: Table

Sr. No.  Field Name Data Type Size

1 B_no int 10
 2 ISBN 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 B_no int 11
2 Id int 20
3 Issue_date Date/Time 10
4 Due_date Date/Time 10
5 Return_date Date/time 10
6 Fine int 3
7 Copies_available int 2

REPORT LISTING

 Readers Report
 Issue-Return Report
 Search Category Report
 Readers Record for Issue-Return Book
 Fine Generation Report

READERS RECORD
Name:

Class: Div:

Roll No: Reader_id:

The Reader Named (Name of Reader) having class (class and

division) and Reader_id (Reader_id) issued (Number of books)
On (Issue date)

 Book 1 – ISBN 1
 Book 2 – ISBN 2
 Book 3 – ISBN 3

HISTORY OF BOOKS ISSUED AND RETURNED BY READER

Name:
Class: Div:

Roll No: Reader_id:

History of Books Issued and Returned:

Sr. No. Book Name ISBN No. Issued on Return on

Long Term Issue:

Total Fine:

FINE GENERATION REPORT

Name:

Class: Div:

Roll No: Reader_id:

Book Name:

Issued On: Due On:

Fine:

A reader (Name) issued a book (Book Name) on (Issue Date) but do

not return the book on (Return Date).The fine submitted by the student will be
(Fine).

RECORD OF TEACHER

Name:

Reader_id:

Number of Book Issued:

List of Books:

Sr. No. Book Name ISBN No. Issued on

Teacher (Teacher name) has issued (Number of Books)

on (Issue Date).

RECORD OF BOOKS FOR A PARTICULAR CATEGORY

Category:

Number of Books Present:

Having ISBN from: to .

List of Books:
Sr. No. Book Name ISBN No. No. of Copies Cost Shelf No.

The library has (Number of Books) for (Category) as listed above

GNATT CHART

Gantt charts have become a common technique for 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 Gantt chart is a useful tool for planning and scheduling
projects. A Gantt chart is helpful when monitoring a project's progress.

System Design

Data Process and Modeling Planned Date

Actual Date

Extended Date

Investigating System Requirements

Project Search

FORM LAYOUT
Nov Des Jan Feb Mar
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