Library Management System-Enterprise Applicatio Development-Lecture Handout, Exercises for Software Development. Indian Institute of Space Science and Technology
pankti
pankti19 July 2012

Library Management System-Enterprise Applicatio Development-Lecture Handout, Exercises for Software Development. Indian Institute of Space Science and Technology

PDF (537 KB)
12 pages
24Number of download
1000+Number of visits
Description
This lecture handout was provided by Sir Aabher Dutt at Indian Institute of Space Science and Technology for Enterprise Application Development course. It includes: Library, Management, System, Software, Requirement, Spe...
20 points
Download points needed to download
this document
Download the document
Preview3 pages / 12

This is only a preview

3 shown on 12 pages

Download the document

This is only a preview

3 shown on 12 pages

Download the document

This is only a preview

3 shown on 12 pages

Download the document

This is only a preview

3 shown on 12 pages

Download the document
CFD-Based Estimation of Probability of Collision between Fine Solid Particles and Bubbles having Intermediate

1 Introduction

This Software Requirement Specification (SRS) document describes the system

specifications of Library Management System. The system can be used by the students

and the faculty members to search and borrow books. The library staff can also use this

system to administer the library system i.e. entering for the new arrivals, issuing a book,

registering a new staff member etc.

2 Purpose

The purpose of this SRS document is to describe the Library Management System.

Requirements Specification defines and describes functional and non functional

requirements of the library system. The nonfunctional requirements such as the user

interfaces are also described. It also describes the design constraints that are to be

considered when the system is to be designed, and other factors necessary to provide a

complete and comprehensive description of the requirements for the software.

3 Intended Audience

The intended audience consists of

 Software Project Managers

 Software Engineers

 Software Developers

 Library Organizer

4 LMS Description

The library management system can be used by the user to search for a book and then

borrow it. The users include students, faculty members and library staff. The librarian

also administrates the system to enter new record upon a new arrival, to update the

position of the books, track records for borrowed books etc. The library management

system will also be available on a web based online portal.

docsity.com

2

Figure 1 Working of Library System

4.1 Requirement Types

This section gives the list of Functional and non-functional requirements that are

applicable to the Library Management system.

4.1.1 Functional Requirements

Librarian

 Add a New Book

New entries must be entered in database upon arrival.

 Update a Book

Any changes in books record should be updated like updating the position of book

 Delete a Book

Wrong entry must be removed from system like entries of fake books.

 Check for Members

Inquiry all current enrolled members to view their details

docsity.com

3

 Check for Borrowed Books

Inquiry all database books that had been borrowed

 Check out Book

To issue any book must be checked out

 Check in Book

After receiving any article system will reenter article by Checking

 Reserve Book

To reserve a book that cannot be issued i.e. reference books.

 Set user Permission

Librarian can give permission to the users and can also disable that permission.

Member

 Authentication

User must authenticate before accessing system by providing user name and password.

 Search a Book

User can search any book.

 Request Book

After successful searching member mark this book as requested book.

 Check Account

This use case is used to check account details like how many more books he can issue at

a particular session.

Guest

 Register user

User must full fill all application form for registration

4.1.2 Non-Functional Requirement

Safety Requirements

It is required to take the database backup after a set amount of time. Because of database

failures and crashes i.e. by some sort of viruses.

docsity.com

4

Security Requirements

It deals with the rights like the librarian has administrative rights so that he can modify

the data, delete, append etc. All other users other than library staff only have the rights to

retrieve the information about database.

Software Quality Attributes

It will have graphical user interfaces to promote user friendliness. The Quality of the

database is maintained in such a way so that it can be very user friendly to all the users of

the database.

Software Constraints

The application can be built using environment like .net or JRE(Java runtime

environment)

Hardware Specifications

Processor: Pentium Processor of at least 3.0 GHz.

RAM: 512 Mb or more

Hard Drive: 40 GB or more.

Software Specifications

Oracle database 11g

Microsoft Visual Studio 2010.

4.2 UML Use Case diagrams

4.2.1 Use Case Actors

 Librarian

 Assistant Librarian

 User

 Guest

docsity.com

5

4.2.2 Use Case Diagram - 1

Figure 2 Librarian

A librarian can log-in to library management system as an administrator. He can Manage

Member Permission like registering a new user to the database or entering a new book.

He can also Manage Inquiry Related Member e.g. he can check a user has issued how

many books. He can Manage Inquiry Related Books like position of book. He can also

issue a book if a request for the book is made.

docsity.com

6

4.2.3 Use Case Diagram – 2

Figure 3 User

The user of system will be a student or a faculty member. A user can search a book after

logging in to library system as a limited user rights account. He can also request for

issuing the book. Moreover he can check his library account status i.e. how many books

he has been issued.

4.2.4 Use Case Diagram – 3

Figure 4 Guest

docsity.com

7

The guest is sort of a new user. He request for registration by filling an application form.

4.3 Petri Nets

4.3.1 Petri Net 1 – Book Issue Process

Figure 5 Book Issue Process (a)

A user is validated and is logged in. A user starts searching.

Figure 6 Book Issue Process (b)

docsity.com

8

As the book is available after searching. The user requests for the issuance of the book.

Figure 7 Book Issue Process (c)

The book is issued and the user gets the book.

Figure 8 Book Issue Process (d)

The whole process is repeated for the new user that wants to get a book issued.

docsity.com

9

4.3.2 Petri Net 2 – New Entry Arrival

New books are purchased and needed to be entered in the database.

Figure 9 New Entry Arrival (a)

With the arrival of a new book, the librarian logs in to the system.

Figure 10 New Entry Arrival (b)

Now the librarian is ready to enter the new record.

docsity.com

10

Figure 11 New Entry Arrival (c)

After the record for the newly arrived book is entered the librarian is ready to update the

database.

Figure 12 New Entry Arrival (d)

docsity.com

11

After the data base is updated the librarian goes into the wait state until a new book

arrives.

Figure 13 New Entry Arrival (e)

To enter the record of another new arrival, the transitions are fired in the same manner as

before.

docsity.com

12

References

1. http://www.scribd.com/doc/24051771/UML-DIAGRAM-OF-LIBRARY-

MANAGEMENT-SYSTEM.

2. http://www.scribd.com/doc/21960811/Library-Management-System.

3. http://www.scribd.com/doc/13850152/Library-Management-System.

4. http://www.scribd.com/doc/17337071/Srs-Library-Management-System.

5. All the use cases were made at gliffy.com.

6. All the Petri nets were made in Pipe 3.0 software.

docsity.com

comments (0)

no comments were posted

be the one to write the first!

This is only a preview

3 shown on 12 pages

Download the document