Scribd
Upload
50 views15 pages

BAHrain Lib System

Uploaded by

bgtes123
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
50 views15 pages

BAHrain Lib System

Uploaded by

bgtes123
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 15

JSG JSV

Project Report On
“Online Library Management System”

Submitted By: Guided By:

1
ACKNOWLEDGEMENT:

We express our gratitude to Dr. Bharat, our project guide, for his invaluable
guidance, inspiration, and constructive suggestions which greatly aided us in the
completion of this project. Additionally, we extend our thanks to our colleagues
whose unwavering cooperation contributed to the successful outcome of the
project.

Table of Contents
1. Synopsis
2. Feasibility Study
3. Data Tables
4. Data Flow Diagrams
5. Entity Relationship Diagram
6. Screen Shots Of Form
7. Future Scope
8. Conclusion
9. Bibliography

2
Online Library Management System

1.) Introduction:-
1.1 Purpose:-
The purpose of this application are as follows :
• The software is for automation of library.
• It provides following facilities to
Operator :
• Can enter details related to a particular book.
• Can provide membership to members.
Admin :
• Can read and write information about any member.
• Can update, create, delete the record of membership as per
requirement and
implementation plants.

2.) 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.
• It can be used in offices and modifications can be easily done
according to requirements.

3.) Technology Used :


Front End : Servlets, HTML, Java script.
Back End : MS Access, Apache Tomcat server.

3
4.) Assumptions
• This application is used to convert the manual application to the
online application.
• Customized data will be used in this application.
• User does not have right to enter information about books.

5.) Overview :
The project pertains to library management, offering reading services to its
members, who may join by completing a designated form and borrowing books for
home use.

6.) Functionality :
• Online membership.
• Keeps the track of issues and submission of books .

Feasibility Study
In feasibility study phase we had undergone through various steps which are
describe as under :
1. Identify the origin of the information at different level.
2. Identify the expectation of user from computerized system.
3. Analyze the drawback of existing system (manual) system.

4
WORKING OF PRESENT MANUAL SYSTEM

The staffs of library are involved in the following tasks.


1. Membership process : person have to fill membership form and
they are provided with member id.

DRAWBACKS OF PRESENT SYSTEM

Some of the problems being faced in manual system are as follows:


1. Fast report generation is not possible.
2. Tracing a book is difficult.
3. Information about issue/return of the books are not properly maintained.
4. No central database can be created as information is not available in
database.

5
PROPOSED SYSTEM
There will be three major components :
1. Stock maintenance.
2. Transaction entry.
3. Reports.

Proposed system provides with following solutions :


1. It provides "better and efficient" service to members.
2. Reduce the workload of employee.
3. Faster retrieval of information about the desired book.
4. Provide facility for proper monitoring reduce paper work and provide data
security.
5. All details will be available on a click.

6
E-R DIGRAM

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.

7
DATA FLOW DIAGRAM

8
E- R Diagram

DATA DICTIONARIES:

9
Master Table : Members [ members detail ]

Master Table : Books [ books details ]

Table : Issue [ book issue record ]

10
SCREEN SHOT OF DESIGN VIEW OF SYSTEM.
1). MAIN MENU

11
2). MEMBERSHIP LOGIN/SIGNUP

3). BOOKS INVENTORY

12
4). BOOK-ISSUE/RETURN RECORD

13
Future Scope
FUTURE SCOPE OF APPLICATION :
This application possesses the capability to be seamlessly integrated across a
range of scenarios, with the ability to incorporate additional features as needed.
The potential for reusability within this application is evident, allowing for
flexibility within all modules.
SOFTWARE SCOPE:
• 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.

14
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.

15

You might also like