Download Final Report LMS

Library Management System
CONTENTS
Library Management System
Library Management System
PAGE NO
1. INTRODUCTION
2. SYSTEM ANALYSIS
2.1 PRESENT SYSTEM
2.2 PROPOSED SYSTEM
2.3 FEASIBILITY STUDY
3. MODULE DESCRIPTION
3.1 STOCK MAINTENANCE
3.2 MEMBERSHIP
3.3 ISSUE OF BOOKS
3.4 RETURN OF BOOKS
3.5 REPORT
4. SYSTEM REQUIREMENTS
4.1 SOFTWARE REQUIREMENTS
4.2 HARDWARE REQUIREMENTS
5. LITERATURE SURVEY
6. SYSTEM DESIGN
6.1 DATA FLOW DIAGRAM
6.2 ER-DIAGRAM
6.3 DATABASE TABLES
7. TESTING
8. IMPLEMENTATION
9. CONCLUSION
10. BIBILOGRAPHY
Library Management System
Library Management System
1.
INTRODUCTION
Library Management System
Library Management System
The aim of the project is to computerize the library information
System in the college.
This project contains the following modules
1. BOOK DETAILS
2. BOOK ISSUES
3. BOOK RETURNS
The details module contains all the information regards the
available books that in the library. It is interconnected to the book issues
and Book return modules.
The issue module contains all the information regarding
The books which have been issued
The returns module contains all the information regarding
The books, which have been returned. The information will be updated
In the details module
As we mentioned earlier, the aim of the project is to
computerize the Library information system in the college
The library has many features i.e. they have many
functions. They are storing the details, issuing books return of books and
The information regarding its updated normally, if a library is run without
computerizing, i.e. manually, it would be very hectic for the librarians. To
keep track of the details &information. So simplify their task.
The
computerization of library has been developed. By using their librarian can
nearly work more efficiently.
Library Management System
Library Management System
2. SYSTEM
ANALYSIS
Library Management System
Library Management System
2.1 Present System:
WORKING OF PRESENT MANUAL SYSTEM:
The staffs of library are involved in the following tasks.
Membership process :
Person has 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.
Library Management System
Library Management System
2.2 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.
2.3 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)
Library Management System
System.
Library Management System
3. MODULE
DESCRIPTION
Library Management System
Library Management System
MODULE DESCRIPTION
The
list
of
modules
incorporated
with
“Library
Management
System” is
 Stock Maintenance
 Membership
 Issue of Books
 Return of Books
 Reports
This module deals with the management of
the
Particular member
information such as the Stock Maintenance,membership,issue of books,
Return of books and report etc.,
Importance of modules in any software development side is we can easily
understand what the system we are developing and what its main uses are.
At the time of project we may create many modules and finally we combine
them to form a system.
3.1 Stock Maintenance:
This module deals with the management of the Stock
Maintenance information such as the personal Book name, Book code, Author,
Price, Date of Arrival, No. Of Books, Rack No, Subject Code etc., Importance of
modules in any software development side is we can easily understand what the
system we are developing and what its main uses are. At the time of project we
may create many modules and finally we combine them to form a system.
Library Management System
Library Management System
3.2 Membership:
This module deals with the management of
the
Membership
information such as the Id No,Name,Address,Date of issue, Amount etc.,
Importance of modules in any software development side is we
can easily understand what the system we are developing and what its main
uses are. At the time of project we may create many modules and finally we
combine them to form a system. Person, so that it can be easily added to
the database with any duplication of the data.
3.3 Issue of Books:
This module deals with the Issue of Books In the library
Management information such as the
Id No, Book name, Date of Issue,
Date of Expiry etc.
3.4 Return of Books:
This module deals with the Return of Books In the library
Management
information such as the
Id No, Book name, Date of Issue,
Date of Expiry etc.
3.5 Report:
This module deals with the Report in Library Management System
Which Contain Information Such as Id No, Name etc..
Library Management System
Library Management System
4.SYSTEM
REQUIREMENT
Library Management System
Library Management System
HARDWARE AND SOFTWARE REQUIREMENTS
4.1 Hard ware Specification:
Processor
Processor Speed
:
:
Intel Pentium Dual-Core insideTM
795MHz to 1.99Gb RAM
RAM
:
2GB
Hard Disk
:
160GB
Key Board
:
104 keys
4.2 Software Specification
Language
:
JDK 1.4
Database
:
MySQL 5.1
Operating System
:
Windows XP
Library Management System
Library Management System
5.
LITERATURE
SURVEY
Library Management System
Library Management System
JAVA
Java was conceived by James Gosling, Patrick Naught on,
Chris Wrath, Ed Frank and Mike Sheridan at Sun Microsystems Inc.in 1991.
It took 18 months to develop the first working version. This language was
initially called “Oak” but was renamed as “Java” in 1995. Between the initial
implementation of Oak in the fall of 1992 and the public announcement of
Java in the spring of 1995, many more people contributed to the design and
evolution of the language.
The main properties of the Java, which made Java so popular, are as
follows:
1. Simple
2. Secure
3. Portable
4. Object-Oriented
5. Robust
6. Multithreaded
7. Architecture-Neutral
8. Interpreted
9. High performance
10. Distributed
11. Dynamic
Library Management System
Library Management System
THE KEY FEATURES OF JAVA IS BYTE CODE:
The key that allows Java to solve both the security and the
portability problems just described is that the output of a Java compiler is
not executable code. Rather, it is Byte code. Byte code is a highly optimized
set of instructions designed to be executed by the Java runtime systems,
which is called the Java Virtual Machine (JVM). That is, in its standard form,
the JVM is an interpreter for Byte code. This may come has a bit of surprise.
Translating a Java program into a byte code helps and makes it
much easier to run a program in a wide variety of environments. The reason
is straightforward only the JVM needs to be implemented for each platform.
Once the runtime package exists for a given system, any Java program can
run on it. Remember, although the details of the JVM will differ from
platform to platform, all interpret the same Java Byte code.
JAVA ENVIRONMENT:
Java environment includes a large number of development tools
and hundreds of classes and methods. The development tools are the part of
the system known as Java Development Kit (JDK) and the classes are
methods are part of the Java standard library (JSL), also known as the
Application Programming Interface (API).
Library Management System
Library Management System
JAVA DEVELOPMENT KIT:
The Java development kit comes with a collection of tools that are used for
developing and running Java programs. They include:
1. Applet Viewer (for viewing Java Applets)
2. Javac (Java Compiler)
3. Java (Java interpreter)
4. Javap (Java Disassembler)
5. Javah (for C header files)
6. Javadoc (for creating HTML documents)
7. Jdb (Java Debugger)
APPLICATION PROGRAMMING INTERFACE:
The Java standard library includes hundreds of classes and
methods grouped into several functional packages. Most commonly used
packages are:
 Language support package: A collection of classes and methods
required for implementing basic features of java.
 Utilities package: A collection of classes to provide utility functions
such as date and time functions.
Library Management System
Library Management System
 Input/output package: A collection of classes required for input &
output manipulations.
 Networking package: A collection of classes for communication with
other computers via Internet.
 AWT package: The abstract window toolkit package contains classes
that implements platform independent graphical user interface.
 Applet package: This includes a set of classes that allows us to create
Java applets.
JAVA DATABASE CONNECTIVITY (JDBC)
The
Java
database
connectivity
Application
Programming
Interface (API) is an API currently being designed by Sun Microsystems that
provides a Java language interface with SQL Call Level Interface standard.
This standard provides a DBMS independent interface to relational databases
that defines a generic SQL database access framework.
The most visible implementation of the SQL CLI is Microsoft’s
ODBC (Open Database Connectivity). This API defines a common SQL syntax
and function calls that can be used by developers to send SQL commands to
and retrieve data from SQL databases. ODBC - enabled applications make
use of database drivers (similar to other device drivers) installed on the
system that allows applications to talk to a vendor’s database. Using this
methodology, all of the DBMS specific code is placed inside the ODBC driver
and the application developer is shielded from implementation specific
Library Management System
Library Management System
problems in theory. Practically speaking, it is sometimes difficult to
completely remove vendor’s specific syntax from all ODBC operations, but in
most cases, it is relatively simple task to port ODBC to run on a new
database server.
ODBC’s primary drawback is that it is written in C. Because of
the limitations inherent in the use of native methods, the JDBC designers
have designed the JDBC specification to most easily use ODBC in short-term,
but they have provided the capability long-term for JDBC to be implemented
in other ways.
The JDBC API is expressed as a series of abstract Java interfaces
within the java.sql package. Here are the most commonly used interfaces:

java.sql.DriverManager – manages the loading and unloading of
database drivers from the underlying systems.

java.sql.Connection – Handles the connections to a specific database.

java.sql.Statement – contains an SQL statement to be passed to the
database: two sub-types in this interface are the PreparedStatement
(for
executing
a
Pre-Compiled
SQL
statement)
and
the
CallableStatement (for executing a database stored procedure).

java.sql.ResultSet – contains the record result set from the SQL
statement passed to the database.
Library Management System
Library Management System
STEPS REQUIRED TO ACCESS A JDBC DATABASE
The steps required to access a JDBC database should be familiar.
JDBC uses the concept of a “Connection” handle to manage a
program’s connection to a database.
ESTABLISING A CONNECTION
The first thing we need to do is establish a connection with the DBMS
you want to use. This involves two steps :
1. Loading the driver: If, we want to use the JDBC-ODBC bridge driver,
the following code will load it :
Class.forName ("sun.jdbc.odbc.JdbcOdbcDrive”)
Our driver documentation will give us the class name to use. For instance, if
the class name is jdbc.Driverxyz, you would load the driver with the
following line of code:
Class.forName (“jdbc.Driverxyz”);
2. Making the connection:
the second step in establishing a
connection is to have the appropriate driver connect to the DBMS.
Library Management System
Library Management System
The following line of code illustrates the general
Syntax:
Class.forName ("sun.jdbc.odbc.JdbcOdbcDrive
Connection
con=DriverManager.getConnection
("Jdbc:
Odbc:
hrmsdsn");
CREATING A STATEMENT
A
statement needs to be created so that it can be passed to the database
for processing. This is done by calling the connection class createStatement
() method.
Syntax:
Java.sql.Statement st=connection.createStatement ();
RETREIVING VALUES FROM RESULT SET
JDBC returns results in a ResultSet object, so we need to declare
in instance of the class ResultSet to hold our result. The following code
demonstrates declaring the ResultSet object RS and assigning the results to
query:
ResultSet
rs=st.executeQuery
user_name='"+user_name+"'");
Library Management System
("select
*
from
EMPDEATILS
where
Library Management System
DATABASE
A database is a set of data, organized for easy access. The
database is an actual data; it is the database that you will be accessing
when you need to retrieve data.
DATA DICTIONARY
The data dictionary is a set of tables MySQL uses to maintain information
about the database. The data dictionary contains information about tables,
indexes, clusters and so on.
DBA (DATABASE ADMINISTRATOR)
The DBA is the person responsible for the operation, configuration
and performance of the database.
The DBA is charged with keeping the
database operating smoothly, ensuring that backups are done on regular
basis (and that backups work), and installing new software. Other
responsibilities might include planning for future expansion and disk space
needs, creating databases and table spaces, adding users and maintaining
security, and monitoring the database and retuning it as necessary. Large
installations might have teams of DBA’s to keep the system running
smoothly; alternatively, the task might be segmented among the DBA’s.
Library Management System
Library Management System
MySQL
MySQL is a free yet full-featured relational database. MySQL was
developed in the 1990s to fill the ever-growing need for computers to
manage information intelligently.
The original core MySQL developers were trying to solve their needs
for a database by using mSQL, a small and simple database. It
become clear that mSQLcouldn’t solve all the problems they wanted it
to, so they created a more robust database that turned into MySQL.
MySQL supports several different database engines. Database engines
determine how MySQL handles the actual storage and querying of the
data. Because of that, each Storage engine has its own set of abilities
and strengths.
Over time, the database engines available are
becoming more advanced and faster.
The current production release of MySQL is the 5.0x version. MySQL
5.0 provides Performance that is comparable to any of the much more
expensive enterprise databases such as Oracle, Informix, DB2 (IBM),
and SQL Server (Microsoft). The developers have achieved this level of
performance
by
leveraging
the
talents
of
many
open
source
developers, along with community testing. For general web-driven
database tasks, the default MyISAM database engine works perfectly
fine.
Library Management System
Library Management System
The Main Features of MySQL:
The following list describes some of the important characteristics of MySQL.
Internals and Portability:
 Written
in
C
and
C++.
The SQL parser uses yacc and a home-
brewed lexer.
 No memory leaks. MySQL has been tested with Purify, a commercial
memory leakage detector.
 Works on many different platforms. Including Linux, Macos..
 Fully multi-threaded using kernel threads. This means it can easily use
Multiple CPUs if available.
 A very fast thread-based memory allocation system.
 In-memory hash tables which are used as temporary tables.
 SQL functions are implemented through a highly optimised class
library and should be as fast as possible! Usually there isn't any
memory allocation at all after query initialization.
Library Management System
Library Management System
Column Types:
 Many column types: signed/unsigned integers 1, 2, 3, 4, and 8 bytes
long, FLOAT, DOUBLE, CHAR, VARCHAR, TEXT, BLOB, DATE, TIME,
DATETIME, TIMESTAMP, YEAR, SET, and ENUM types.
 Fixed-length and variable-length records.
Security:
 A privilege and password system that is very flexible and secure, and
allows Host-based Verification. Passwords are secure because all
password Traffic is encrypted when you connect to a server.
Scalability and Limits:
 Handles large databases. We are using MySQL with some databases
that Contain 50,000,000 records and we know of users that use
MySQL with 60,000 tables and about 5,000,000,000 rows.
 Up to 32 indexes per table are allowed. Each index may consist of 1 to
16 Columns or parts of columns. The maximum index width is 500
bytes.
Library Management System
Library Management System
Connectivity:
 Clients may connect to the MySQL server using TCP/IP Sockets, Unix
Sockets (UNIX), or Named Pipes (NT).
 ODBC (Open-Database-Connectivity) support for Win32 (with
source).All ODBC 2.5 functions and many others. For example, you
can use MS Access to connect to your MySQL server.
Clients and Tools:
 All MySQL programs can be invoked with the --help or -? options to
obtain online assistance.
 Includes myisamchk, a very fast utility for table checking,
optimisation, and repair. All of the functionality of myisamchk is also
available through the SQL interface as well.
Library Management System
Library Management System
6. SYSTEM DESIGN
Library Management System
Library Management System
System Design encompasses certain steps review appropriate
data determine requirements for a new system and design the
new system. Within the framework, the creative talents of the
systems analyst can be employed to the fullest.
The design is last phase that indicates the final system and
process of the designed system. In the design ph ase, we design
the database tables, input screen design and the output reports
etc.
The
data
dictionaries/database
tables
are
designed
by
analyzing various functions involved in the system and format of
the fields are designed.
Computer software design changes continually as new
methods
better
analysis
and
broader
understanding
evolve.
Software design is at a relatively early stage in its evolution.
Therefore,
software
design
methodology
lacks
the
depth,
flexibility and quantitative nature that a re normally associated
with more classical engineering design disciplines. Once software
requirements have been analyzed and specified, software design
is the first to the three technical activities - design, code and test.
The importance of sof tware design can be stated with a
single word quality. Design is the place where quality is fostered
in
software
development.
Design
provides
us
with
the
representation of the software that can be accessed for quality.
Design is the only way th at we can accurately translate a
customer’s requirements into a finished software product of a
system. Without design, we risk building an unstable system one
Library Management System
Library Management System
that will fail when small changes are made, one that may be
difficult to test:

Data Design:
The data design transforms the information domain model
during analysis into the data structures that will be required to
implement the software.

Architectural Design:
The architectural design defines the relationship among
major structural components of the program.

Procedural Design:
The procedural design transforms structural components
into a procedural description of the software. Source code is
generated and testing is conducted to integrate and validate the
software.
Thus, system study is a solution, “How to!” approach to
the access effects of the new system. The social feasibility is
done along side technical feasibility to job. It entails looking into
the duplication of the efforts, bottlenecks; inefficient e xisting
procedures are ports of the existing system would be candidates
for computerization.
The design is concerned with system development. The
new system design must be based on the facts obtained in the
system analysis phase and must lie wit hin the framework of the
Library Management System
Library Management System
system
project.
Further,
the
selected
must
be
within
the
constraints of the new system designed.
The system implementation stage builds upon the system
analysis,
system
design
devising
programs,
and
methods
equipment
and
selection
procedures
phases
recruiting
by
and
training qualified personnel, installing the equipment and putting
the new system into operation.
The System Analyst has to understand the process logic.
He
has
to
then
verify
with
the
management
re quirements
properly. If necessary, corrections are to be made. Once the
understanding is clear, the system analyst has to explain this
process to the programmer. The programmer then builds this
process logic in the specified program. In our software we hav e
an MDI form with menus & toolbar.
Library Management System
Library Management System
DATA FLOW
DIAGRAMS
Library Management System
Library Management System
DATA FLOW DIAGRAMS
A graphical tool used to describe and analyze the movement of data through
a system manual or automated including the process, stores of data, and
delays in the system. Data Flow Diagrams are the central tool and the basis
from which other components are developed.
The transformation of data
from input to output, through processes, may be described logically and
independently of the physical components associated with the system. The
DFD is also know as a data flow graph or a bubble chart.
TYPES OF DATA FLOW DIAGRAMS:
Data Flow Diagrams are of two types as follows:
(a) Physical DFD
(b) Logical DFD
1. PHYSICAL DFD:
Structured analysis states that the current system should be first
understand correctly. The physical DFD is the model of the current system
and is used to ensure that the current system has been clearly understood.
Physical DFDs shows actual devices, departments, and people etc., involved
in the current system.
Library Management System
Library Management System
2. LOGICAL DFD:
Logical DFDs are the model of the proposed system. They clearly should
show the requirements on which the new system should be built. Later
during design activity this is taken as the basis for drawing the system’s
structure charts.
BASIC NOTATION:
The Basic Notation used to create a DFD’s are as follows:
DATAFLOW: Data move in a specific direction from an origin to a destination.
PROCESS: People, procedures, or devices that use or produce (Transform)
Data. The physical component is not identified.
SOURCE:
External sources or destination of data, which may be People,
programs, organizations or other entities.
DATA STORE: Here data are stored or referenced by a process in the System
Library Management System
Library Management System
DESIGN:
Design is the first step in moving from problem domain to the solution
domain. Design is essentially the bridge between requirements specification
and the final solution.
The goal of design process is to produce a model or representation of a
system, which can be used later to build that system. The produced model
is called the “Design of the System”.
system.
Library Management System
It is a plan for a solution for the
Library Management System
DATA FLOW DIAGRAM:
Requesting For Membership
Requestinntg Student Details
Student
Sending Student details
Sending Membership Card
Membership
Management
For Member
Request for penalty
Book Issue Details
Student
Request for Books
Return Book
Book Issue
Penalty paid
Student
Management
Books
Send Penalty
Book Issue
Library Management System
Library Management System
ER-Diagram
Library Management System
Library Management System
An ERD is a model that identifies the concepts or entities that exist in
a system and the relationships between those entities. An ERD is often used
as a way to visualize a relational database: each entity represents a
database table, and the relationship lines represent the keys in one table
that point to specific records in related tables.
ERDs may also be more
abstract, not necessarily capturing every table needed within a database,
but serving to diagram the major concepts and relationships.
The ERD presents a visual representation of e-resource management
concepts and the relationships between them
Understanding the Model:
There are several different modeling systems for entity relationship
diagramming. This ERD is presented in the “Information Engineering” style.
Those unfamiliar with entity relationship diagramming or unfamiliar with this
style of notation may wish to consult the following section to clarify the
diagramming symbology.
Entities:
Entities are concepts within the data model. Each entity is represented by a
box within the ERD. Entities are abstract concepts, each representing one or
more instances of the concept in question. An entity might be considered a
container that holds all of the instances of a particular thing in a system.
Entities are equivalent to database tables in a relational database, with each
row of the table representing an instance of that entity.
Remember that each entity represents a container for instances of the thing
in question. The diagram below has an entity for “student” and another for
Library Management System
Library Management System
“school.” This indicates that the system being modeled may contain one or
more students and one or more schools.
STUDENT
SCHOOL
So far, no relationship between students and schools has been indicated.
Relationships:
Relationships are represented by lines between entities.
Relationship lines
indicate that each instance of an entity may have a relationship with
instances of the connected entity, and vice versa.
STUDENT
SCHOOL
The diagram above now indicates that students may have some relationship
with schools.
More specifically, there may be a relationship between a
particular student (an instance of the student entity) and a particular school
(an instance of the school entity).
Library Management System
Library Management System
Library
Contains
Book Name
Subject code
Book Code
No of Books
Books
Author
Rack No
Date of Arrival
Price
Issues
ID No
Status of Ms
Name
Type of Ms
Membership
Address
Amount
Date of Issue
Date of Expiry
Issues
Returns
Date of Issue
ID No
Book
Name
Date of
Issue
Issue of
Books
Date of
Expity
Library Management System
Status Of
Return
ID No
Date of
Expiry
Book Name
Library Management System
Database Table
Library Management System
Library Management System
MEMBERSHIP:
NAME
TYPE
ID NO
NAME
ADDRESS
DATE OF ISSUE
DATE OF EXPIRY
STATUS OF MS
TYPE OF MS
AMOUNT
INTEGER
VARCHAR
VARCHAR
DATE
DATE
VARCHAR
VARCHAR
INTEGER
SIZE
KEY
------15
25
------------15
15
-------
PRIMARY KEY
NOT NULL
-------------------------------------
TYPE
VARCHAR
INTEGER
VARCHAR
DATE
INTEGER
INTEGER
INTEGER
INTEGER
SIZE
20
------25
-------------------------------
KEY
NOT NULL
-------------------------------------------
TYPE
INTEGER
VARCHAR
DATE
DATE
SIZE
-----15
-------------
KEY
PRIMARY KEY
NOT NULL
---------
STOCK MAINATAINCE:
NAME
BOOK NAME
BOOK CODE
AUTHOR
DATE OF ARRIVAL
RACK NO
PRICE
NO OF BOOKS
SUBJECT CODE
ISSUE OF BOOKS:
NAME
ID NO
BOOK NAME
DATE OF ISSUE
DATE OF EXPIRY
Library Management System
Library Management System
RETURN OF BOOKS
NAME
ID NO
BOOK NAME
DATE OF ISSUE
DATE OF EXPIRY
TYPE
INTEGER
VARCHAR
DATE
DATE
SIZE
----20
---------
KEY
PRIMARY KEY
NOT NULL
-----------
TYPE
INTEGER
VARCHAR
SIZE
-----20
KEY
PRIMARY KEY
NOT NULL
REPORT
NAME
ID NO
NAME
Library Management System
Library Management System
7. TESTING
Library Management System
Library Management System
TESTING PHASE
The completion of a system is achieved only after it has been
thoroughly tested. Though this gives a feel the project is completed, there
cannot be any project without going through this stage. Hence in this stage
it is decided whether the project can undergo the real time environment
execution without any break downs, therefore a package can be rejected
even at this stage.
 SYSTEM TESTING
Testing is a set of activities that can be planned in advance and
conducted systematically. The proposed system is tested in parallel with the
software that consists of its own phases of analysis, implementation, testing
and maintenance. Following are the tests conducted on the system.
 UNIT TESTING
During the implementation of the system each module of the
system was tested separately to uncover errors with in its boundaries. User
interface was used as a guide in the process.
 MODULE TESTING
A module is composed of various programs related to that
module. Module testing is done to check the module functionality and
interaction between units within a module.
It checks the functionality of each program with relation to other
programs within the same module. It then tests the overall functionality of
each module.
Library Management System
Library Management System
 INTEGRATION TESTING
Integration testing is a systematic technique for constructing the
program structure while conducting tests to uncover errors associated with
interfacing. The objective is to take unit-tested module and build a program
structure that has been dictated by design.
 ACCEPTANCE TESTING
The software has been tested with the realistic data given by the client
and produced fruitful results. The client satisfying all the requirements
specified by them has also developed the software within the time limitation
specified. A demonstration has been given to the client and the end-user
giving all the operational features.
Library Management System
Library Management System
Test plan:
Test plan is general document for the entire project. That defines the
scope approach to be taken and schedule of testing as well as identifies the test
items for the entire testing process and personnel responsibility for the different
activities of testing. The test plan can be done well before the actual testing
commences and can be done in parallel with the coding and design activity .the
input for forming that test plan are :
1) Project plan.
2) Requirement documents.
3) System design document.
The project plan is needed to make sure that test plan is consistent
with the overall quality plan for the project and testing schedule matches that of
the project
plan.
The test plan should contain the following:

Test unit specification.

Features to be tested.

Approach for testing.

Test deliverables.

Schedule and task allocation.
Test unit it is a set of one or more modules together with associated
data, that are form single computer program and that are the object of testing. A
test unit may be a module, few modules, or complete system.diffrent units are
usually specified for unit, integration and system testing.
Library Management System
Library Management System
The identification of test unit establishes the different level of testing
that will be performed in the project. Generally, number of test units are
formed during testing, starting from the lower level modules, which have to
be unit tested .the basic idea behind forming test units is to make sure that
testing is being performed incrementally ,with each increment including only
a few aspects that need to be tested. A unit should be such that it can be
easily tested in other words, it should be possible to form meaningful test
cases and execute the unit without much effort with these test cases.
Features
to
be
tested
include
all
software
features
and
combination of features that should be tested. A software feature is software
characteristics specified or implied by requirement or design document these
may include functionality, performance, design constraints and attribute.
The approach for testing specifies the overall approach to be
followed in the current project .the technique that will be used to judge the
testing effort should also be specified. This is sometime called the testing
criterion or the criterion for evaluating the set of test cases used in testing.
Testing deliverables should be specified in the test plan before
the actual testing begins. Deliverable could be a list of test cases that were
used, detailed result of testing including the list of defects found, test
summery report ,and a list of defects should always be specified as
deliverables.
Library Management System
Library Management System
The test plan, if it is a document separate from the project
management plan, typically also specifies the schedule and effort to be spent
on different activities of testing. This schedule is consistent with the overall
Project schedule .For detailed planning and execution, the different tasks in
the test plan should be enumerated and allocated to test resources that are
responsible for performing them. Many large products have separate testing
terms and therefore a separate test plan .A smaller project may include the
test plan as part of its quality plan in the project management plan.
Library Management System
Library Management System
8. IMPLEMENTATION
Library Management System
Library Management System
IMPLEMENTATION PHASE
The implementation is the final and important phase. It involves
User training, system testing and successful running of the developed
system. The users test the developed system when changes are made
according to the needs. The testing phase involves the testing of the
developed system using various kinds of data. An elaborate testing of data is
prepared and system is tested using the tests data.
Implementation is the stage where theoretical design turned into a
working system. Implementation is planed carefully to propose system to
avoid unanticipated problems. Many preparations involved before and during
the implementation of proposed system. The system needed to be plugged
in to the organization’s network then it could be accessed from anywhere,
after a user logins into the portal. The tasks that had to be done to
implement the system were to create the database tables in the organization
database domain. Then the administrator was granted his role so that the
system could be accessed.
The next phase in the implementation was to educate the system. A
demonstration of all the functions that can be carried out by the system was
given to examination department person, who will make extensive use of the
system.
Library Management System
Library Management System
9. CONCLUSION
Library Management System
Library Management System
After we have completed the project we are sure the problems in the
existing
system
would
overcome.
The “LIBRARY
MANAGEMENT
SYSTEM” process made computerized to reduce human errors and to
increase the efficiency. The main focus of this project is to lessen human
efforts. The maintenance of the records is made efficient, as all the records
are stored in the ACCESS database, through which data can be retrieved
easily. The navigation control is provided in all the forms to navigate through
the large amount of records. If the numbers of records are very large then
user has to just type in the search string and user gets the results
immediately. The editing is also made simpler. The user has to just type in
the required field and press the update button to update the desired field.
The Books and Students are given a particular unique id no. So that they
can be accessed correctly and without errors. Our main aim of the project is
to get the correct information about a particular student and books available
in the library.
The problems, which existed in the earlier system, have been removed to a
large extent. And it is expected that this project will go a long way in
satisfying
users’
requirements.
The
computerization
of
the
Library
Management will not only improves the efficiency but will also reduce human
stress thereby indirectly improving human recourses.
Library Management System
Library Management System
10.
BIBLIOGRAPHY
Library Management System
Library Management System
BOOKS REFERRED
The following books were used extensively for the project development and
implementation.
1.”The Complete Reference Java2” Tata McGraw-Hill publishing Company
Limited. By Herbert Schildt.
2. “Software Engineering, A Practitioner’s Approach” Tata McGraw-Hill
Publishing Company Limited. By Roger S. Pressman.
3. “PL/SQL”. By Ivan Bayross.
WEBSITES REFERRED
The following links were searched and exploited extensively for the project
development and implementation.
1. http://www.java.sun.com/products\java
2. http://www.jakarta.apache.org
3. http://www.javaworld.com/
4. http://www.java2s.com/
Library Management System