c

ccccccccccccccccccccccccc cccccccccccccccccccccc2 DEC 2010c

REPORT ON
9
c c


c

Prepared by :

Kalpesh Bhanshali
Amala Shah
Mohit Rijwani
Rushil Thaker
Navin Choubey
1
c
c
c

ccccccccccccccccccccccccc cccccccccccccccccccccc2 DEC 2010c


9cc   cc

Sr. No Particulars Page no.

1 Introduction 3

2 Information to be contained in the System 3

3 Interactions with the System 4

4 User Interface 6

5 DFD Level 0 and 1 8

6 ERD (Entity Relationship Diagram) 10

7 Conclusion 11

2
c
c
c

ccccccccccccccccccccccccc cccccccccccccccccccccc2 DEC 2010c

c

There are 2 users of the system: patrons and librarians. Librarians can also be patrons.
The objectives of the library system are to allow patrons to:

{c login/logout
{c withdraw and return books
{c search the library's books
{c pay overdue charges
{c put a book on hold

and librarians to:

{c login/logout
{c add/remove books to/from the library
{c move books from one shelf of the library to another one
{c activate manually the next-day function that updates the databases at the end of the day.

c
cccccc
c

1.c The system shall contain information about each valid patron of the system: À


   , unpaid s and the identity of each book the patron has
currently withdrawn.

2. The system shall contain information about each librarian: À
, 
 
and  . Librarians can be patrons.

3.c The system shall contain information about each book in the library:  number,
À,  (s),  (of publication), copy  , À, current  (on-loan,
on-shelf,), the date on which the book entered loan status. For books on loan the
system shall contain the À
 of the patron involved.

4.c The system shall contain information about each shelf in the library: À 

(the maximum number of books that the shelf can hold).

5.c Inf of about the location of the book in the library.

3
c
c
c

ccccccccccccccccccccccccc cccccccccccccccccccccc2 DEC 2010c

c
ccc
c

!" !c #c$%&c 'c

In order to perform the following interactions with the system, a user must login first
with a valid À
 and
 . If login is successful the user's À
 is returned by
the DBMS to the application program. All subsequent interactions are assumed to have
been initiated by that user until the session completes (the user logs out). Since À
 is
used to identify the user in these interactions, the application should retain À
 until
the end of the session, supplying it as a parameter when necessary to the DBMS. The
session is ended with logout, at which point the application can discard À
 and the
next interaction must be a new login.

mc(c$%'

The purpose of this interaction is to allow a patron to withdraw a book.

The  and copy  of the book to be withdrawn are supplied at the screen.

The interaction fails if:

{c The book is already withdrawn.

{c The book is not in the library's collection.
{c The patron has already withdrawn 5 books.

c(c$%'

The  and copy  of the book are supplied at the screen.

The purpose of this interaction is to allow a patron to return a book that he/she has
withdrawn. If the book is overdue, the patron's charge record is updated by an amount of
Rs.10 a day

The interaction fails if the book is not recorded as being withdrawn by that patron.

c(c$c%'

The purpose of this interaction is to allow a patron to search for a book in the library.

One or more of the following: À    are supplied at the screen. Either title or
author must be supplied, however the title need not be complete - a substring of the title
might be supplied - and only a single author can be supplied (even though books can
have multiple authors). A range of years can be specified. For example, the search ³lists
all books with the word `hiking' in the title written by Smith (there might be coauthors)

4
c
c
c

ccccccccccccccccccccccccc cccccccccccccccccccccc2 DEC 2010c

between 1995 and 2000. The title, author and year of all books that satisfy the search
criterion are output.

Ýc(c$%'

The amount of the payment is input at the screen.

The purpose of this interaction is to allow a patron to pay a fine. The amount of payment
is deducted from the balance owed.

Any excess is considered a donation to the library. The amount of fine remaining is
displayed on the screen.

)(c(c$ '

The purpose of this interaction is to allow a librarian to record the fact that another day
has passed. .

The interaction fails if the initiator is not a librarian. (One implementation of this is that
your interface ensures that only a librarian can initiate this interaction).

c(c$c '

 À    (s) and À (of the shelf on which the book is to be stored)
are supplied at the screen.

The purpose of this interaction is to allow a librarian to add a new book to the library's
books. Multiple copies of the same book can exist in the library's books. A new copy
number must be assigned to the book to be added.

The interaction fails if:

{c The initiator is not a librarian.

{c The shelf is full.
{c The book specifications conflict with a book already in the library's
collection (e.g., if there is a book in the library's collection with the same
isbn number but a different author, title, or year.)

*c(c$ '

 copy  and À (to identify the new shelf) are supplied.

The purpose of this interaction is to allow a librarian to move a book from one shelf to
another.

5
c
c
c

ccccccccccccccccccccccccc cccccccccccccccccccccc2 DEC 2010c

The interaction fails if:

{c The book is not in the library's books.

{c The shelf is full.
{c The initiator is not a librarian.

*c(c$c '

 and copy  are supplied at the screen.

The purpose of this interaction is to allow a librarian to remove a book from the library's
book.

The interaction fails if the book is not in the library's books or if the initiator is not a
librarian.
cc
c
+c cc
c
c
%cc

Ý !c,c

ccc

Ý ccc

-cc

c.c

/cc

6
c
c
c

ccccccccccccccccccccccccc cccccccccccccccccccccc2 DEC 2010c

%cc

Ý !c,c

ccc

Ý ccc

-cc

c.c

/cc

c
c
c
c
c
c
c
c
c
c
c
c

7
c
c
c

ccccccccccccccccccccccccc cccccccccccccccccccccc<
C <c

c

c9 ccc
c
c
c
c
c
c
c
c
c
c

c
c
c
c
c
c
c
c
c
c
c

c
c
c

ccccccccccccccccccccccccc cccccccccccccccccccccc2 DEC 2010c

c
c
c
c
,,c9* c0cc
c
c
c
c
c
ccccc

c
c
c

9
c
c
c

ccccccccccccccccccccccccc cccccccccccccccccccccc2 DEC 2010c

c
c
c
,c,!cc
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c

10
c
c
c

ccccccccccccccccccccccccc cccccccccccccccccccccc2 DEC 2010c

c
c

 c
c
The Library Management System is developed using Excel fully meets the objectives of the
system which it has been developed. The system has reached a steady state where all bugs have
been eliminated. The system is operated at a high level of efficiency and the entire user
associated with the system understands its advantage.

11
c