28-07-2014, 03:55 PM
Online Library Management System
[attachment=66341]
Introduction
.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.
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 draw back of existing system (manual)
system.
[b]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.
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.
[attachment=66341]
Introduction
.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.
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 draw back of existing system (manual)
system.
[b]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.
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.