LIBRARY MANAGEMENT SYSTEM

Introduction:Library management system is a project which aims in developing a computerized system

to maintain all the daily work of library .This project has many features which are
generally not availiable in normal library management systems like facility of user login
and a facility of teachers login .
It also has a facility of admin login through which the admin can monitor the whole
system .It also has facility of an online notice board where teachers can student can put
up information about workshops or seminars being held in our colleges or nearby
colleges and librarian after proper verification from the concerned institution organizing
the seminar can add it to the notice board .
It has also a facility where student after logging in their accounts can see list of books
issued and its issue date and return date and also the students can request the librarian to
add new books by filling the book request form.
The librarian after logging into his account ie admin account can generate various reports
such as student report , issue report, teacher report and book report .
Overall this project of ours is being developed to help the students as well as staff of
library to maintain the library in the best way possible and also reduce the human efforts.
Data Flow Diagram(DFD):In our DFD, we give name to data flows, processes and data stores. Although the name is
descriptive of the data, they do not give details. Sp the following DFD, our interest is to
build some structured place to keep details of the content of data flows, processes and
data store. A data dictionary is a structured repository of data about data. It is a set of
rigorous definition of all DFD data element and data structure.
DATA FLOW DIAGRAMS :Level 0

Level 1

Level 2

Context Level Diagram:-

E-R Diagram of Library management System

Testing

Testing is the process of evaluating a system or its component(s) with the intent to find
that whether it satisfies the specified requirements or not. This activity results in the
actual, expected and difference between their results. In simple words testing is executing
a system in order to identify any gaps, errors or missing requirements in contrary to the
actual desire or requirements.
Beta Testing
This test is performed after Alpha testing has been successfully performed. In beta testing
a sample of the intended audience tests the application. Beta testing is also known as prerelease testing. Beta test versions of software are ideally distributed to a wide audience on
the Web, partly to give the program a "real-world" test and partly to provide a preview of
the next release. In this phase the audience will be testing the following:
Users will install, run the application and send their feedback to the project team.
Typographical errors, confusing application flow, and even crashes.
Getting the feedback, the project team can fix the problems before releasing the
software to the actual users.
The more issues you fix that solve real user problems, the higher the quality of
your application will be.
Having a higher-quality application when you release to the general public will
increase customer satisfaction.

Documentation
Documentation is the technical manual, user manual or other instructional manual that
facilitate the use of a software product or services. Documentation includes source code,
instructional items, error code where ever required. It may exists in any formats like PDF,
Word or CDs.

Documentation can be classified into several parts like Requirement Documentation,

Architecture/Design Documentation, Technical, End User, Marketing Documentation.

Importance of Software Documentation:

1. Clarify your business goals, requirements and activities:With a proper

documentation, you can share the business goals and requirement with your
managers and team mates so that they have a clear vision and goals and the
activity they perform will be more towards the success.
2. Design and Specify your product: This comes in Architectural/Design

documents and it gives you complete overview of how your products look
like.
3. Everything is clearly explained: When you makes End User documentation

of the product of software, you have to explain each and everything about its
working.It describes each feature of the program, and assists the user in
realizing these features.
4. Any body can work on other's code: If you are a developer, it is not

sufficient to write good codes only but you also need to take cares about the
documentation part, which can be helpful to other developers while working
in a team.
5. Helpful in proper communication: A good software documentation is

helpful in proper communication. The written procedure helps you to make

interaction within several departments