ONLINE LIBRARY MANAGEMENT SYSTEM

SUBMITTED BY-1. POULAMEE CHATTOPADHYAY (1005102)2. SIDDHARTH SHANKAR (1005185)3. SUMAN DAS (1005206)4. VARSHA SRAKAR (1005221)

INTRODUCTION 1.1 METHODOLOGY

A software development methodology engineering is a framework that is used to structure, plan, and

control the process of developing an information system. A software development process also known as

software development life-cycle (SDLC), is a structure imposed on the development of a software

product. The main idea of the SDLC has been to pursue the development of information systems in a very

deliberate, structured and methodical way, requiring each stage of the life cycle from inception of the idea

to delivery of the final system, to be carried out rigidly and sequentially within the context of the

framework being applied.

 

As a noun, a software development methodology is a framework that is used to structure, plan, and

control the process of developing an information system - this includes pre-definition of specific

deliverables and artifacts that are created and completed by a project team to develop or maintain an

application. Specific software development methodologies include:

· Rational Unified Process (RUP , IBM) since 1998

· Agile Unified Process (AUP) since 2005 by Scott Ambler

 

Every software development methodology approach acts as a basis for applying

specific frameworks to develop and maintain software. Several software development

approaches have been used since the origin of information technology. These are:

• Waterfall: a linear framework

• Prototyping: an iterative framework

• Evolutionary: a combined linear iterative framework

• Spiral: a combined linear framework

• Rapid application development (RAD): an iterative framework

• Extreme Programming

Purpose of ONLINE MANAGEMENT SYSTEM project -

The purpose of this application are as follows :

• The software is for automation of library work

• It provides following facilities to

1) Librarian: • Can enter details related to a particular book. • Can provide membership to members and update as required. 2) Member: • Can request for issue, return book and check for any existing fine by asking the librarian. • Can pay his fine and the details are updated accordingly by the librarian.

SCOPE

The different areas where we can use this application are :

• Any education institute can make use of it for providing information about

author, content of the available books in its library.

• Modifications can be easily done according to requirements as and when

necessary.

REQUIREMENT SPECIFICATION

Functional Requirements :

• Librarian Login: Librarian can login and access the required information.

• Security: No normal user should be able to login except the librarian

• Update member information: Librarian can update the bill for payment

of fine, the number of books issued ,any change in personal details.

• Update book details: Librarian can add new book details and also change

the status of the book (whether available or not available).

Non-Functional Requirements :

• Secure access of confidential data (user’s details).  

• Better component design to get better performance at peak time

• Flexible service based architecture will be highly desirable for future

extension.

System Requirements :Hardware Requirements :

To develop or implement this project we need different types of hardware

configuration for server and client. 

The Client Machines: -

The Server Machines: -

Processor RAM Hard Disk

Intel Pentium III or AMD-800 MHz

128 MB 100 MB

Processor RAM Hard Disk

Intel Pentium III or AMD-800 MHz

512 MB 300 MB

Software Requirements :

Front End:

 • Client on Internet: Web Browser, Operating System (any)• Client on Intranet: Web Browser, Operating System (any)

 

 

Back End:

• JSP,CSS• Web Server: Apache Tomcat• Database Server: MSAccess• Operating System: Any (preferably Linux)

 

Communication Interface

• Students on Internet will be using HTTP/HTTPS protocol.

• Admin on Internet will be using HTTP/HTTPS protocol.   

Constraints: 

• Not more than 3 books can be issued by any member at a time.

• The librarian cannot go back to the login page after he signs in unless he

logs out.

• User name of librarian has to be unique.

HTML :Hypertext Markup Language is used for creating web pages and other information that can be displayed in a web browser.

JAVA SERVER PAGES : It is a technology that helps software developers create dynamically generated web pages based on HTML, XML, or other document types. To deploy and run Java Server Pages, a compatible web server with a servlet container, such as Apache Tomcat is required.

MS ACCESS: It is a database management tool from Microsoft which combines Relational Microsoft Jet Database Graphical User Interface and software development tools. APACHE TOMCAT SERVER : Apache Tomcat is an open source web server and servlet container developed by the Apache Software Foundation (ASF). Tomcat implements the Java Servlet and the Java Server Pages (JSP) and provides a "pure Java" HTTP web server environment for Java code to run in.

OVERVIEW

Project is related to library management which provides reading

services to its members. Any person can become a member of the

library by filling a prescribed form. They can get the book issued,

so that they can take home and return them.

PROPOSED SYSTEMThere will be three major components :

1. Stock maintenance.

2. Transaction entry.

3. Reports.

Proposed system provides with following solutions :

1. It provides efficient service to members.

2. Reduces the workload of employee.

3. Fast retrieval of information about the desired book.

4. Provides facility for proper monitoring reduce paper work and provide data security.

5. All details will be available on a click.

DATA TABLES

S.No. Column Name Data Type Length Description

1 MemberId Text 50 Unique identification of members

2 Name Text 70 Name of Members

3 Address Text 70 Location of Members

4 DateOfMembership

Date/Time Date of Registration

5 Status Text 50 Temporary/Permanent

1.TABLE : MemberRecord

2.TABLE :Books

S.No Column Name Data Type Description

1 BookID Text Book identification number

2 Name Text Title of the book

3 Author Text Author of books

4 Status Text Whether book is available or not

5 Price Text Cost of books

6 Rack_no Text Location of book

7 No of Books Number Quantity of books

3.TABLE : Transaction

S.No. Column Name Data Type Description

1 TransactionId Text Unique identification of transaction type and number

2 MemberId Text User identification number

3 DateOfIssue Date/Time Date on which book was issued

4 Due_Date Date/Time Due date on which book is to be returned

5 BookId Text Unique identification number of book

4.Table:Librarian

S.No Column Name Data Type Description

1 Name Text Name of the librarian

2 Password Password Login Password of the librarian

USE CASE DIAGRAM

CLASS DIAGRAM

Activity diagram for issuing book in library

Activity diagram for returning book in library

Sequence diagram for issuing book

Sequence diagram for returning book

E-R DIAGRAM

It is clear that the physical objects from the previous section – the member, books,

library – correspond to entities in the Entity-Relationship model, and the operations

to be done on those entities – holds, checkouts, and so on – correspond to

relationships. However, a good design will minimize redundancy and attempt to

store all the required information in as small a space as possible.

:Screenshots:1. LIBRARIAN LOGIN PAGE

2. LIBRARIAN HOME PAGE

3. BOOK ISSUE FORM

4. Book Issued

5.BOOK RETURN FORM 1

6.BOOK RETURN FORM 2

7.BOOK RETURNED FORM

8.BOOK ADD FORM

9.BOOK ADDED

10.ISSUE STATUS PAGE

11.BOOK ISSUED

12.ADD MEMBER

13.MEMBER ADDED

Future Scope

This application can be easily implemented under various situations.

We can add new features as and when we require. Reusability is possible as and when require in

this application. There is flexibility in all the modules.

• Extensibility:

This software is extendable in ways that its original developers may not expect. The following

principles enhances extensibility like hide data structure, avoid traversing multiple links or

methods, avoid case statements on object type and distinguish public and private operations.

•Reusability:

Reusability is possible as and when require in this application. We can update it next version.

Reusable software reduces design, coding and testing cost by amortizing effort over several

designs. Reducing the amount of code also simplifies understanding, which increases the

likelihood that the code is correct. We follow up both types of reusability: Sharing of newly

written code within a project and reuse of previously written code on new projects.

• Understandability:

A method is understandable if someone other than the creator of the method can understand the code

(as well as the creator after a time lapse). We use the method, which small and coherent helps to

accomplish this.

• Cost-effectiveness:

Its cost is under the budget and make within given time period. It is desirable to aim for a system with

a minimum cost subject to the condition that it must satisfy the entire requirement.Scope of this

document is to put down the requirements, clearly identifying the information needed by the user, the

source of the information and outputs expected from the system.

Conclusion

From a proper analysis of positive points and constraints on the component, it

can be safely concluded that the product is a highly efficient GUI based

component. This application is working properly and meeting to all user

requirements. This component can be easily plugged in many other systems.