Online Library Management System

(OLMS)

PROJECT OVERVIEW
Online Library Management System is a comprehensive library information management system developed from the ground up to fulfill the needs of library as they instruct their students.The integrated information management system connects daily operations in the Library environment ranging from Membership and Book Issue to Business Development. This reduces data error and ensures that information is always up-to-date throughout the Library.

It provides a single source of data repository for streamlining your business processes and reporting purposes. It has a simple user interface and is intuitive. This insures that the users spend less time in learning the system and hence, increase their productivity. Efficient security features provide data privacy and maintains data integrity

BENEFITS OF OLMS
The overall objective can be summarized as follows: 1. Automation of the membership registration system. 3. Automation of the book issue and return system. 4. Easy handling of the library information system. 5. Viewing about the books and books detail. 6. Easy handling of fees of membership.

ANALYSIS OF THE SYSTEM

System analysis is an activity that comes as follows 1. FEASIBILITY STUDY 2. SOFTWARE DESIGN 3.SYSTEM SPECIFICATION 4.SYSTEM ANALYSIS 5.SYSTEM DESIGN 6.CODING AND TESTING 7.DEBUGGING 8.SYSTEM IMPLEMENTATION 9.SOFTWARE MAINTENANCE

FEASIBILITY STUDY
Feasibility Study is the likelihood the system will be useful to the organization. After studying the requirements, whether the proposed project is feasible or not, is determined by checking the various feasibilities.

SOFTWARE DESIGN
The system uses. Net with VB Technology. The main modules involved in this system are: Login Forms

SYSTEM SPECIFICATION
The system specification tells us the requirement of the project. The second task of the project planning is estimation of resource required to accomplish the software development effort.

SYSTEM ANALYSIS
Analysis is the process of studying to find the best solution to that problem. System Analysis is the process by which we learn about the existing problems, define objects and requirements and evaluates the solutions. System Analysis gives the target for design and development. System analysis is a term used to describe the process of collecting and analysing facts with respect to existing operation of system so that an effective system may be designed and implemented if proved feasible.

SYSTEM DESIGN
System design is a detailed concentration on the technical and other specification that will make the system operational. It is the most crucial stage in the system development lifecycle. It focuses on the detailed implementation of the system recommended in the feasibility study. Emphasis is on translating the performance requirements into design specification. The phase is a trasition from user oriented document to a document oriented to the programmers or database personal.

CODING AND TESTING

CODING:
The objective of the coding phase is to transform the design of a system into code in a high level language, and then unit test this code. The software development organizations formulate their own coding standard that suits them the most.

TESTING: The aim of program testing is to identify all defects in program .No software can be ever perfect. The communication and instruction between the client and the server is no always complete. Due to many reasons there is chance to remain some errors within the software. The errors must be eliminated before the software is ready to use.

DEBUGGING
Debugging occurs as a consequence of successful testing. When a test case uncovers an error, debugging is the process that results in the removal of error. Although debugging can and should be orderly process, it is still very much an art. A software engineer, evaluating the result of a test, is often confronted with a symptomatic identification of a software problem.

SYSTEM IMPLEMENTATION
An important aspect of a system analysis job is to make sure that the new design is implemented to an established standard. The term implementation has different meaning, ranging from conversion of basic application to a complete replacement of a computer system.

SOFTWARE MAINTENANCE
Software maintenance traditionally denotes the process of modifying a software product after it has been delivered to the customer. Maintenance is inevitable for almost any kind of product. Most of the software products need maintenance on account of the following three main reasons: 1.Corrective: Corrective maintenance of a software product may be necessary either to rectify some bugs observed while the system is in use, or to enhance the performance of the system.

2.Adaptive: A software product might need maintenance when the customer need the product to run on new platforms, on new operating systems, or when they need the product to interface with new hardware or software. 3.Prefecture: A software product needs maintenance to support the new feature that the users want or to change different functionalities of the system according to customer demands.

DATAFLOW DIAGRAMS
Data flow diagram is a pictorial representation of the system in which flow of data from one process to another process is described. Data flow diagrams illustrate how data is processed by a system in terms of inputs and outputs. Data Flow Diagram for the system is as follows:

student

Send no dues

Member rqst

managment
member detail Membership Managment send request

Discontinue request

member details Penalty amnt

Report rqst

Member

Penalty

Report Managemen t

book details

issue details

Book Issue Managment

Books

issue details penalty report

Book Issue
Reqst for issue

return book

student
Penalty remind

E-R DIAGRAMS:
E-R Diagrams represents the relationship between the entities. An E-R diagram is composed of Entity is shown by rectangle. Attribute is shown by oval. Relationships with rhombus. Optional is shown by circle. Compulsory with dash. Primary key with underscore. The E-R diagram of the system is as follows:

admin_addr admin_name e-mail

administrator

id

issue

grant

quantity Date_issue

amount

Date_expire price

address

book

issue

member

author edition

type

name

Book_name

Book_no.

status

id

Fig:E-R Diagram

Database Tables
Table Name:bookentry Primary Key:bno Foreign Key:NIL Field Name Bno Bname Author Edition Price Quantity Language Entrydate Data Type Varchar2 Varchar2 Varchar2 Varchar2 int Int Varchar2 Date DESCRIPTION Book Number Book Name Author of The book Edition of the book Price of the book Amount of book Book language Mark entry Date Size 20 30 20 10 10 10 12 15

Table Name: btransaction Primary Key: mid Foreign Key: bno Field Name Mid bno bname trantype trandate DATA TYPE Int Int Varchar Varchar Varchar DESCRIPTION Member Identity Book Number Book Name Transaction Type Transaction Date Size 20 20 30 15 15

CONCLUSION
Any work may not be always perfect there may be some error or some defect in this work. We have taken enough care to make the project user friendly. We hope that our software should be useful to user. We hope the application will provide a boon for people. We are computing our project work with the blessings of our guide and all group members.

WITH THANKS

Atowar Rahman(Roll No:o1) Kalpajyoti Saikia(Roll No:12)