A

MINI PROJECT(BCC-351)

REPORT
ON
LIBRARY MANAGEMENT SYSTEM

A project report submitted in partial fulfillment of the requirement for the

Award of Degree of

BACHELOR OF TECHNOLOGY
In
COMPUTER SCIENCE AND ENGINEERING

Submittedby:

Anjali (2400960100012)
Aarti (2400960100001)

Guidedby:

Ms Tanu Sharma([Link] CSE)

Department of Computer Science & Engineering,

Vishveshwarya Group of Institutions, Greater Noida,
Gautam Budh Nagar, Uttar Pradesh
 CERTIFICATE

This is to certify that the project work entitled “Library Management System”, which is being submitted by Anjali

Roll no. 2400960100012 and Aarti Roll no. 2400960100001 in partial fulfillment of the requirements for award of

the degree of B-TECH (BACHELOR OF TECHNOLOGY) to the Vishveshwarya Group of Institutions, Greater Noida is

an authentic work carried out by the student under my guidance. The matter embodied in this project work has

not been submitted earlier for award of any degree or diploma to the best of my knowledge and belief.

Asst. Prof. Tanu Sharma Signature of

Dept. Of Computer Science Supervisor:
VGI Greater Noida
 ACKNOWLEDGEMENT

The entire journey from the very idea of this research to reality would not have been
possible without the guidance and support of many experienced people.

I would like to thank Ms Tanu Sharma for assistance in completion of this Project
Report.

I would also like to thanks to Professor and Dean, Dept. of Comp. Sc., V.G.I. Greater
Noida and Dr. Waseem Ahmad, Professor and head, Dept. of Comp. Sc., V.G.I. Greater
Noida and Project Guide By Prof. Manoj Rajora, Dept. Of Comp. Sc., V.G.I. Greater
Noida.

A heartfelt thanks to the respondents surveyed whose ideas, critical insights and
suggestions have been invaluable in the preparation of this report.

Last but not the leave a very warm thanks to all the faculty members of Vishveshwarya
Group Institution, Greater Noida for providing me guide lines in project report.

A heartfelt thanks to the respondents surveyed whose ideas, critical insights and
suggestions have been invaluable in the preparation of this report.

Last but not the leave a very warm thanks to all the faculty members of Vishveshwarya
Group Institution,Greater Noida for providing me guide lines in project report.

Anjali
Aarti

[Link] III SEM, 2025

Dept. Of Computer Science And Engineering.
V.G.I. Greater Noida
 Library Management System in Python

The library management system in python which we are going to build

will look something like this
 ABSTRACT

Project Name is: “Library Management System”

The project is very flexible and it can be modified if the need arises. This is a web based Library
Management System application. I hope the user will find this project work quite pleasing in its output as general
sample designing has been done to enhance the view and simple programming statement and commands have
been made use of, so that the user had no problem in understanding the listing of the project.

The project “Library Management System” is aimed to maintain the state of registration, updating or deletion of
users and books, tracking users, creating book alerts and much more. The main objectives of this project is to
provide a web based portal that is used by librarians and students to post the book and apply for a book
respectively.

Idea behind Library Management System is that “We normally go to the number of companies to get a better book
option. But no guarantees to get book opportunities. So that we provide this platform to post books and apply
books worldwide. After that we can get book opportunities on the go. It’s simple to apply for a better book. Just
sign up and book will appear on the basis of your educational details or by your custom book search criteria.
Online Library Management System is a web application built in JAVA Struts2.3 technology. It provides the
students, ability to register to this application and search for books, manage their accounts. Each student will have
an account with their own home page. On the other hand, Librarians those are willing to publish the books for
their library to students, can register to the Library Management System and get their own account created and
can post books to portal's database. Registered Librarians can add or remove books and these books can be seen
by various students and they can contact the concern person for the book. Main aim of this web application is to
make a user friendly platform, where applicant can search books easily and is accessible to everyone who are
interested.

The Purpose of the application is to provide Library Management System for Students, to submit their CV
and apply for book, where Librarian can select best Employees from available student profile.
ADVANTAGES

1. Multi-User capabilities.
2. Can maintain User with user-definable access right as well as set of default values for
easy navigation & user-access control of the application.
3. Facilitate the information access all over the organization through highly integrated and
4. informative modules.
5. Image and photograph handling resulting in the” No Paperwork” concept.
6. Messages can be sent and received through User mail option to have an effective and
paper-less communication between the application User.
7. Different security levels at User.
The project can be divided in to four main modules.

1. Registration/Login module
2. Student section (Student Module)
3. Librarian section (Library & Administration Module as well as Book Module)
4. Admin Module
a. Not necessary but added: College Module (only for listing the colleges to portal)

Module 1:

Registration / Login module, which is further sub-divided into:-

1. Registration.
2. Change Password.
3. Forget Password.
4. Login.

Module 2:

Student section, which is further sub-divided into: -

1. Resume Upload / Download
2. Resume Generate
3. Search for Book according to his skill set.
4. Expert Guidance through online helpdesk
5. Save / Delete Book
6. Apply / Cancel Book

Module 3:

Librarian section, which is further sub-divided into four sub-sections: -

1. Register Book Record.

2. Update Book Record.
3. Check Book Status.
Module 4:

Admin section which is further sub-divided into two sub-sections: -

1. Ban User
2. Release User
3. Search User

Site Working:-

Case AStudent Administration:-

1. Student has to register himself with the site.
2. This is a free site for Student.
3. After success full Log in Student can register his resume.
4. Student Register his Bio Data in a particular Book Record Category.
5. He can also update his resume.
6. He can search for Book Record according to his skill set and can apply for a book

Case BLibrarian Administration:-

1. Library has to register itself.
2. After success full Login Library can register Book Record.
3. Registration for Book Record will generate Book Record Id.
4. Library can update a Book Record.
 LIST OF FIGURES

FIGURES OF DATABASE TABLES ARE:

1. Student (Student) Module
a) tblCandAlert
b) tblCandAppliedBook
c) tblCandCareer
d) tblCandCertificate
e) tblCandExp
f) tblCandInfo
g) tblCandLang
h) tblCandPhoto
i) tblCandProject
j) tblCandQualification
k) tblCandResume
l) tblCandSavedBook
2. Registration / Login Module
a) tblLogin
b) tblState
c) tblCityState
d) tblIndustry
e) tblFunctionalArea
f) faq
g) topics
3. Librarian Section (Library, Administration and Book Module)
a) tblCompContact
b) tblConsContact
c) tblBook
4. Admin Module
a) tblLog
FIGURES OF OUTPUTS ARE:
1. Home Page (Index)
2. Registration
3. Login
4. Change Password
5. Forget Password
6. Dashboard
a) Student
b) Library
c) Administration
d) College
e) Admin
7. Edit Profile
a) Student
I. Information (About)
II. Certificate Details
III. Education Details

V. Applied Book
VI. Saved Book
VII. Desired Career
Experience
VIII. Details
IX. Language Known
X. Photo Upload
XI. Project Details

b) Library
c) Administration
d) College
8. Post Book
9. View Book
10. View Library
11. Search Book
12. HelpDesk
LIST OF SYMBOLS, ABBREVIATIONS ANDNOMENCLATURE

Symbols
1. Using Font Awesome
2. Glyph-icons.

Ex:

fa fa-edit

glyphiconglyphicon-home.
 INTRODUCTION

The purpose of this document is to present a detailed description of the “Library Management System”. It
will explain the purpose and features of the system, the interfaces of the system, what the system will do, the
constraints under which it must operate and how the system will react to external stimuli. This document is
intended for both the users and the developers of the system.

Scope of Project

Idea behind Library Management System is that “We normally go to the number of companies to get a
better book option. But no guarantees to get book opportunities. So that we provide this platform to post books
and apply books worldwide. After that we can get book opportunities on the go. It’s simple to apply for a better
book. Just sign up and book will appear on the basis of your educational details or by your custom book search
criteria.

1. Reusability:
Reusability is possible as and when we 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.
2. Extensibility:
This software is extended in ways that its original developers may not expect. The
following principles enhance extensibility like Hide data structure, avoid traversing multiple
links or methods, Avoid case statements on object type and distinguish public and private
operations.

3. Robustness:
 Its method is robust if it does not fail even if it receives improper parameters. There are
some facilities like Protect against errors, Optimize after the program runs, validating arguments
and Avoid predefined limits.

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

5. 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 all the requirements.
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.

Objectives

Objective of doing this project is to provide cost effective solutions to customers.

Some of the client requirement and objectives of this site is as under:-
To increase the business of Client.
To make it Global.
To facilitate advance search.

To facilitate User so that it can search for best available options

to help Users to get a good options.
To act as a middle men connecting different parties
 Parties can search for different options available.
Parties can do on-line interaction etc.

Parties can use search to look for different options.

User can download different forms etc.

This system tends to replace the existing manual system for the recruitment process
which is a time consuming, less interactive and highly expensive.
The main features of this system will be creating vacancies, storing Applicants data,
Interview process initiation for the applicant and finally Hiring of the applicant.
“Library Management System” is a web-based application, which helps end user to find a book with
searching criteria like preferred skill and location and work profile.

It also helpful to “post book” and “search student” based on bookseeker profile. Book provider can
download resume of student.
Book provider can make discussion with studentand also send mail to student.

It is developed in order to reduce the gap between Industry and Industry needed
resources.
One can post his/her details on this portal with all relative information.

Conclusion: It’s a great start in area of local search engine. It will be highly beneficial
forclient/user to get any types of information rapidly and accurately.
 FEASIBILITY STUDY

Feasibility study is made to see if the project on completion will serve the purpose of the
organization for the amount of work, effort and the time that spend on it. Feasibility study lets
the developer foresee the future of the project and the usefulness. A feasibility study of a system
proposal is according to its workability, which is the impact on the organization, ability to meet
their user needs and effective use of resources. Thus when a new application is proposed it
normally goes through a feasibility study before it is approved for development.

The document provide the feasibility of the project that is being designed and lists various
areas that were considered very carefully during the feasibility study of this project such as
Technical, Economic and Behavioral feasibilities. The following are its features:

 TECHNICAL FEASIBILITY: -
The system must be evaluated from the technical point of view first. The
assessment of this feasibility must be based on an outline design of the system
requirement in the terms of input, output, programs and procedures. Having identified an
outline system, the investigation must go on to suggest the type of equipment, required
method developing the system, of running the system once it has been designed.

Technical issues raised during the investigation are:

 Does the existing technology sufficient for the suggested one?
 Can the system expand if developed?
The project should be developed such that the necessary functions and
performance are achieved within the constraints. The project is developed within latest
technology. Through the technology may become obsolete after some period of time,
due to the fact that never version of same software supports older versions, the system
may still be used. So there are minimal constraints involved with this project. The system
has been developed using Java the project is technically feasible for development.

 ECONOMIC FEASIBILITY: -

The developing system must be justified by cost and benefit. Criteria to ensure
that effort is concentrated on project, which will give best, return at the earliest. One of
the factors, which affect the development of a new system, is the cost it would require.

The following are some of the important financial questions asked during preliminary
investigation:
1. The costs conduct a full system investigation.
2. The cost of the hardware and software.
3. The benefits in the form of reduced costs or fewer costly errors.
Since the system is developed as part of project work, there is no manual cost to
spend for the proposed system. Also all the resources are already available, it give an
indication of the system is economically possible for development.

 BEHAVIORAL FEASIBILITY

This includes the following questions:

1. Is there sufficient support for the users?
2. Will the proposed system cause harm?
The project would be beneficial because it satisfies the objectives when developed
and installed. All behavioral aspects are considered carefully and conclude that the
project is behaviorally feasible.
 SYSTEM ANALYSIS

System analysis is a process of gathering and interpreting facts, diagnosing problems and
the information to recommend improvements on the system. It is a problem solving activity that
requires intensive communication between the system users and system developers. System
analysis or study is an important phase of any system development process. The system is
studied to the minutest detail and analyzed. The system analyst plays the role of the interrogator
and dwells deep into the working of the present system. The system is viewed as a whole and the
input to the system are identified. The outputs from the organizations are traced to the various
processes. System analysis is concerned with becoming aware of the problem, identifying the
relevant and decisional variables, analyzing and synthesizing the various factors and determining
an optimal or at least a satisfactory solution or program of action.
A detailed study of the process must be made by various techniques like interviews,
questionnaires etc. The data collected by these sources must be scrutinized to arrive to a
conclusion. The conclusion is an understanding of how the system functions. This system is
called the existing system. Now the existing system is subjected to close study and problem areas
are identified. The designer now functions as a problem solver and tries to sort out the
difficulties that the enterprise faces. The solutions are given as proposals. The proposal is then
weighed with the existing system analytically and the best one is selected. The proposal is
presented to the
user for an endorsement by the user. The proposal is reviewed on user request and suitable
changes are made. This is loop that ends as soon as the user is satisfied with proposal.

Preliminary study is the process of gathering and interpreting facts, using the information
for further studies on the system. Preliminary study is problem solving activity that requires
intensive communication between the system users and system developers. It does various
feasibility studies. In these studies a rough figure of the system activities can be obtained, from
which the decision about the strategies to be followed for effective system study and analysis can
be taken.

A detailed study of existing system is carried along with all the steps in system analysis. An idea
for creating a better project was carried and the next steps were followed.

Existing System

In the existing system only we can see the details of particular information about the
College in our state, the existing system has more workload. But, in case of proposed
system, the admin can use my system to maintain different types of work.
Drawback of Existing System
1. More man power
2. Time consuming
3. Consuming large volume of pare work
4. Need Manual Calculation
5. Damage of machines due to lack of attentions

To avoid all these limitation and the makethe working more accurately the system need to
be computerized.

Proposed System

The aim of proposed system is to develop a system of improved facilities. The proposed
system can overcome all the limitations of the existing system. The system provides
proper security and reduces the manual work. The existing system has several
disadvantages and many more difficulties to work well. The proposed system tries to
eliminate or reduce these difficulties up to some extent. The proposed system will help the user to reduce
the workload and mental conflict. The proposed system helps the user to work user friendly and he can
easily do his books without time lagging.

 Expected advantages of Proposed System

The System is very simple in design to implement. The system requires very low system
resources and the system will work in almost all configurations. It has got following
features
1. Ensure data accuracy’s.
2. Reduce the damagesof the machines.
3. Minimize manual data entry.
4. Minimum time needed for the various processing.
5. Greater efficiency.
6. Better service.
7. User friendliness and interactive.
 SPECIFIC REQUIREMENTS

 Hardware Specification (minimum)

Pentium IV / AMD
Processor : Processor

RAM : 2 GB

Hard disk : 100 GB

Monitor : 15 inch

Mouse : 3 Button scroll

CD Drive : Not Necessary

Keyboard : 108 keys

 Software Specification (minimum)

Win7 / Win8 / Win10 / MAC / LINUX /

Operating System : UNIX

Languages : Java

Front End : Struts 2.3

Platform : JAVA (JRE)

Backend : MySQL
MySQL Workbench 6.3 CE and Net Beans
Supporting Software : 8.2
 EXTERNAL INTERFACE REQUIREMENTS

USER INTERFACES
1. Front-end software: Struts 2.3
2. Back-end software: MySQL

HARDWARE INTERFACES
1. Windows 8.1
2. Intel Core i3 with 4 GB RAM
3. Browser which supports HTML & JavaScript.

SOFTWARE INTERFACES
Software used Description

Operating system We have chosen Windows 8 operating system for its best support.

Database To save the records, we have chosen MySQL database.

To implement the project we have chosen Java language for its

more interactive
Net Beans 8.2 support.

Communications Protocol(s)
This project supports all types of web browsers

We use one major communication protocol to verify user registration. That protocol is SMTP.

SMTP is simple mail transfer protocol i.e. used for sending mail. We use [Link] API to
sendmail to the registered user when they perform registration on PraiseU.
SOFTWARE SYSTEM ATTRIBUTE

Compatibility

Usability

Correctness

Customizability

Effectiveness

Fault-tolerant design

Maintainability

Modifiability

Modular programming

Operability

Recoverability

Reusability

Scalability

Safety

DATABASE REQUIREMENT(S)

MySQL version 5.0 or above.

Database should be properly backup while going to deploy this project.

Some procedure are there in database. We must have to backup them also to change the location
of the database in future or deploy this project.
 DESIGN

Design is the first step into the development phase for any engineered product or system.
Design is a creative process. A good design is the key to effective system. The term “design” is
defined as “the process of applying various techniques and principles for the purpose of defining
a process or a system in sufficient detail to permit its physical realization”. It may be defined as a
process of applying various techniques and principles for the purpose of defining a device, a
process or a system in sufficient detail to permit its physical realization. Software design sits at
the technical kernel of the software engineering process and is applied regardless of the
development paradigm that is used. The system design develops the architectural detail required
to build a system or product. As in the case of any systematic approach, this software too has
undergone the best possible design phase fine tuning all efficiency, performance and accuracy
levels. The design phase is a transition from a user oriented document to a document to the
programmers or database personnel. System design goes through two phases of development:
Logical and Physical Design.

LOGICAL DESIGN:
The logical flow of a system and define the boundaries of a system. It includes the
following steps:
 
1. Reviews the current physical system – its data flows, file content, volumes, Frequencies
etc.
2. Prepares output specifications – that is, determines the format, content and Frequency of
reports.
3. Prepares input specifications – format, content and most of the input functions.
4. Prepares edit, security and control specifications.
5. Specifies the implementation plan.
6. Prepares a logical design walk through of the information flow, output, input, Controls
and implementation plan.

7. Reviews benefits, costs, target dates and system constraints.

PHYSICAL DESIGN:
Physical system produces the working systems by define the design specifications that tell the programmers
exactly what the student system must do. It includes the following steps.
1. Design the physical system.
2. Specify input and output media.
3. Design the database and specify backup procedures.
4. Design physical information flow through the system and a physical design
5. Plan system implementation.
6. Prepare a conversion schedule and target date.
7. Determine training procedures, courses and timetable.
8. Devise a test and implementation plan and specify any new hardware/software.
9. Update benefits ,costs , conversion date and system constraints

Design Specification activities:

1. Concept formulation.
2. Problem understanding.
 3. High level requirements proposals.
4. Feasibility study.
5. Requirements engineering.
6. Architectural design.

INPUT DESIGN:
The input design is the link between the information system and the user. It comprises the
developing specification and procedures for data preparation and those steps are necessary to put
transaction data in to a usable form for processing can be achieved by inspecting the computer to
read data from a written or printed document or it can occur by having people keying the data
directly into the system. The design of input focuses on controlling the amount of input required,
controlling the errors, avoiding delay, avoiding extra steps and keeping the process simple. The input
is designed in such a way so that it provides security and ease of use with retaining the privacy. Input
Design considered the following things:
1. What data should be given as input?
2. How the data should be arranged or coded?
3. The dialog to guide the operating personnel in providing input.
4. Methods for preparing input validations and steps to follow when error occur.

OBJECTIVES
1. Input Design is the process of converting a user-oriented description of the input into a
computer-based system. This design is important to avoid errors in the data input
processand show the correct direction to the management for getting correct information
from the computerized system.
2. It is achieved by creating user-friendly screens for the data entry to handle large volume
of data. The goal of designing input is to make data entry easier and to be free from
[Link] data entry screen is designed in such a way that all the data manipulates can be
performed. It also provides record viewing facilities.
 3. When the data is entered it will check for its validity. Data can be entered with the help of
screens. Appropriate messages are provided as when needed so that the user will notbe in
maize of instant. Thus the objective of input design is to create an input layout that is
easy to follow.

OUTPUT DESIGN
A quality output is one, which meets the requirements of the end user and presents
the information clearly. In any system results of processing are communicated to the users and to
other system through outputs. In output design it is determined how the information is to be
displaced for immediate need and also the hard copy output. It is the most important and direct
source information to the user. Efficient and intelligent output design improves the system’s
relationship to help user decision-making.

Designing computer output should proceed in an organized, well thought out manner; the
right output must be developed while ensuring that each output element is designed so
that people will find the system can use easily and effectively. When analysis design
computer output, they should Identify the specific output that is needed to meet the
requirements.
Select methods for presenting information.

Create document, report, or other formats that contain information produced by the
system.

The output form of an information system should accomplish one or more of the following
objectives.

1. Convey information about past activities, current status or projections of the Future
2. Signal important events, opportunities, problems, or warnings.
3. Trigger an action.
4. Confirm an action.
 Database Design

A database is an organized mechanism that has the capability of storing information

through which a user can retrieve stored information in an effective and efficient manner. The
data is the purpose of any database and must be protected.

The database design is a two level process. In the first step, user requirements are
gathered together and a database is designed which will meet these requirements as clearly as
possible. This step is called Information Level Design and it is taken independent of any
individual DBMS.

In the second step, this Information level design is transferred into a design for the
specific DBMS that will be used to implement the system in question. This step is called
Physical Level Design, concerned with the characteristics of the specific DBMS that will be
used. A database design runs parallel with the system design. The organization of the data in the
database is aimed to achieve the following two major objectives.

Data Integrity
Data independence

Normalization is the process of decomposing the attributes in an application, which results

in a set of tables with very simple structure. The purpose of normalization is to make tables as
simple as possible. Normalization is carried out in this system for the following reasons.

To structure the data so that there is no repetition of data, this helps in saving.
To permit simple retrieval of data in response to query and report request.

To simplify the maintenance of the data through updates, insertions, Deletions.

To reduce the need to restructure or reorganize data which new application
Requirements arise.
RELATIONAL DATABASE MANAGEMENT SYSTEM (RDBMS):
A relational model represents the database as a collection of relations. Each relation resembles a
table of values or file of records. In formal relational model terminology, a row is called a tuple,
a column header is called an attribute and the table is called a relation. A relational database
consists of a collection of tables, each of which is assigned a unique name. A row in a tale
represents a set of related values.

RELATIONS, DOMAINS & ATTRIBUTES:

A table is a relation. The rows in a table are called tuples. A tuple is an ordered set of n
elements. Columns are referred to as attributes. Relationships have been set between
every table in the database. This ensures both Referential and Entity Relationship
Integrity. A domain D is a set of atomic values. A common method of specifying a
domain is to specify a data type from which the data values forming the domain are
drawn. It is also useful to specify a name for the domain to help in interpreting its values.
Every value in a relation is atomic, that is not decomposable.

RELATIONSHIPS:

1. Table relationships are established using Key. The two main keys of prime importance
are Primary Key & Foreign Key. Entity Integrity and Referential Integrity
Relationshipscan be established with these keys.
2. Entity Integrity enforces that no Primary Key can have null values.
3. Referential Integrity enforces that no Primary Key can have null values.
4. Referential Integrity for each distinct Foreign Key value, there must exist a matching Primary Key value in
the same domain. Other keyare Super Key and Student Keys.
5. Relationships have been set between every table in the database. This ensures both
Referential and Entity Relationship Integrity.
NORMALIZATION:

As the name implies, it denoted putting things in the normal form. The application
developer via normalization tries to achieve a sensible organization of data into proper
tables and columns and where names can be easily correlated to the data by the user.
Normalization eliminates repeating groups at data and thereby avoids data redundancy
which proves to be a great burden on the computer resources. These include:
a. Normalize the data.
b. Choose proper names for the tables and columns.
c. Choose the proper name for the data.

1. First Normal Form:

The First Normal Form states that the domain of an attribute must include only
atomic values and that the value of any attribute in a tuple must be a single value
from the domain of that attribute. In other words 1NF disallows “relations within
relations” or “relations as attribute values within tuples”. The only attribute values
permitted by 1NF are single atomic or indivisible values.

The first step is to put the data into First Normal Form. This can be donor by
moving data into separate tables where the data is of similar type in each table. Each
table is given a Primary Key or Foreign Key as per requirement of the project. In this
we form new relations for each non atomic attribute or nested relation. This
eliminated repeating groups of data.

A relation is said to be in first normal form if only if it satisfies the constraints

that contain the primary key only.

2. Second Normal Form:

According to Second Normal Form, for relations where primary key contains
multiple attributes, no non key attribute should be functionally dependent on a part of
the primary key.
 In this we decompose and setup a new relation for each partial key with its
dependent attributes. Make sure to keep a relation with the original primary key and
any attributes that are fully functionally dependent on it. This step helps in taking out
data that is only dependent on a part of the key.

A relation is said to be in second normal form if and only if it satisfies all the first
normal form conditions for the primary key and every non-primary key attributes of
the relation is fully dependent on its primary key alone.

3. Third Normal Form:

According to Third Normal Form, Relation should not have a non-key attribute
functionally determined by another non-key attribute or by a set of non-key attributes.
That is, there should be no transitive dependency on the primary key.

In this we decompose and set up relation that includes the non-key attributes that
functionally determines other non-key attributes. This step is taken to get rid of
anything that does not depend entirely on the Primary Key.

A relation is said to be in third normal form if only if it is in second normal form

and more over the non key attributes of the relation should not be depend on other
non-key attribute.
 CODING

The purpose of coding is to facilitate the identification, retrieval of the items and
information. A code is an oriented collection of symbols design to provide unique identification
of an entry or attribute. Code is built with manually exclusive features. Codes in all cases specify
object which are physical or on performance characteristics. They are used to give optimal
distraction and other information. Codes are used for identifying, accessing, storing and
matching records. The codes insure that only one value of the code with a single meaning is
correctly applied to give entity or attribute as described in various ways. Code can also be design
in a manner easily understood and applied by the user.
 TESTING

Software Testing is the process of executing software in a controlled manner, in order to

answer the question - Does the software behave as specified? Software testing is often used in
association with the terms verification and validation. Validation is the checking or testing of
items, includes software, for conformance and consistency with an associated specification.
Software testing is just one kind of verification, which also uses techniques such as reviews,
analysis, inspections, and walkthroughs. Validation is the process of checking that what has been
specified is what the user actually wanted.

Validation : Are we doing the right book?

Verification : Are we doing the book right?

Software testing should not be confused with debugging. Debugging is the process of
analyzing and localizing bugs when software does not behave as expected. Although the
identification of some bugs will be obvious from playing with the software, a methodical
approach to software testing is a much more thorough means for identifying bugs. Debugging is
therefore an activity which supports testing, but cannot replace testing.

Other activities which are often associated with software testing are static analysis and dynamic
analysis. Static analysis investigates the source code of software, looking for problems and gathering
metrics without actually executing the code. Dynamic analysis looks at the behavior of
software while it is executing, to provide information such as execution traces, timing profiles,
and test coverage information.

Testing is a set of activity that can be planned in advanced and conducted systematically.
Testing begins at the module level and work towards the integration of entire computers based
system. Nothing is complete without testing, as itvital success of the system testing objectives,
there are several rules that can serve as testing objectives. They are

Testing is a process of executing a program with intend of finding an error.

A good test case is one that has high possibility of finding an undiscovered error.
A successful test is one that uncovers an undiscovered error.

If a testing is conducted successfully according to the objectives as stated above, it would

uncovered errors in the software also testing demonstrate that the software function appear to be
working according to the specification, that performance requirement appear to have been met.

There are three ways to test program.

For correctness

For implementation efficiency

For computational complexity

Test for correctness are supposed to verify that a program does exactly what it was designed to
do. This is much more difficult than it may at first appear, especially for large programs.

TEST PLAN: -A test plan implies a series of desired course of action to be followed
inaccomplishing various testing methods. The Test Plan acts as a blue print for the action that is
to be followed. The software engineers create a computer program, its documentation and related
data structures. The software developers is always responsible for testing the individual units of
the programs, ensuring that each performs the function for which it was designed. There is an
independent test group (ITG) which is to remove the inherent problems associated with letting
the builder to test the thing that has been built. The specific objectives of testing should be stated
in measurable terms. So that the mean time to failure, the cost to find and fix the defects,

remaining defect density or frequency of occurrence and test work-hours per regression test all
should be stated within the test plan.
 The levels of testing include:
a. Unit testing
b. Integration Testing
c. Data validation Testing
d. Output Testing

1. UNIT TESTING: - Unit testing focuses verification effort on the smallest unit
of softwaredesign – the software component or module. Using the component level
design
description as a guide, important control paths are tested to uncover errors within the
boundary of the module. The relative complexity of tests and uncovered scope
established for unit testing. The unit testing is white-box oriented, and step can be
conducted in parallel for multiple components. The modular interface is tested to ensure
that information properly flows into and out of the program unit under test. The local data
structure is examined to ensure that data stored temporarily maintains its integrity during
all steps in an algorithm’s execution. Boundary conditions are tested to ensure that all
statements in a module have been executed at least once. Finally, all error handling paths
are tested.

Tests of data flow across a module interface are required before any other test is
initiated. If data do not enter and exit properly, all other tests are moot. Selective testing
of execution paths is an essential task during the unit test. Good design dictates that error
conditions be anticipated and error handling paths set up to reroute or cleanly terminate
processing when an error does occur. Boundary testing is the last task of unit testing step.
Software often fails at its boundaries.

Unit testing was done in Sell-Soft System by treating each module as separate
entity and testing each one of them with a wide spectrum of test inputs. Some flaws in the
internal logic of the modules were found and were rectified.
2. INTEGRATION TESTING: -Integration testing is systematic technique
for constructing theprogram structure while at the same time conducting tests to uncover
errors associated

with interfacing. The objective is to take unit tested components and build a program
structure that has been dictated by design. The entire program is tested as whole.
Correction is difficult because isolation of causes is complicated by vast expanse of entire
program. Once these errors are corrected, new ones appear and the process continues in a
seemingly endless loop.

After unit testing in Sell-Soft System all the modules were integrated to test for
any inconsistencies in the interfaces. Moreover differences in program structures were
removed and a unique program structure was evolved.

3. VALIDATION TESTING OR SYSTEM TESTING: -This is the final

step in testing. In this theentire system was tested as a whole with all forms, code,
modules and class modules.
This form of testing is popularly known as Black Box testing or System tests.
Black Box testing method focuses on the functional requirements of the software.
That is, Black Box testing enables the software engineer to derive sets of input conditions
that will fully exercise all functional requirements for a program.
Black Box testing attempts to find errors in the following categories; incorrect or
missing functions, interface errors, errors in data structures or external data access,
performance errors and initialization errors and termination errors.

4. OUTPUT TESTING OR USER ACCEPTANCE TESTING: -The system

considered is tested foruser acceptance; here it should satisfy the firm’s need. The software
should keep in touchwith perspective system; user at the time of developing and making
changes whenever required. This done with respect to the following points
 1. Input Screen Designs,
2. Output Screen Designs,
3. Online message to guide the user and the like.
The above testing is done taking various kinds of test data. Preparation of test data
plays a vital role in the system testing. After preparing the test data, the system under
study is tested using that test data. While testing the system by which test data errors are
again uncovered and corrected by using above testing steps and corrections are also noted
for future use.

VALIDATION CHECKING

At the culmination of integration testing, software is completely assembled as a package; interfacing

errors have been uncovered and corrected, and a final series of software test-validation checks may
begin. Validation can be defined in many ways, but a simple definition (Albeit Harsh) is that
validation succeeds when software functions in a manner that can be reasonably expected by a
customer. Software validation is achieved through a series of black-box tests to be conducted and a
test procedure defines specific test cases that will be used in attempt to uncover errors in conformity
with requirements. Both the plan and procedure are designed to ensure that all functional
requirements are satisfied; all performance requirements are achieved; documentation is correct and
human –Engineered and other requirements are met. Once the application was made free of all
logical and interface errors, inputting dummy data to ensure that the software developed satisfied all
the requirements of the user did validation checks .However, the data are created with the intent of
determining whether the system will process them correctly.

s
 VISHVESHWARYA GROUP OF INSTITUTIONS
GREATER NOIDA (U.P.)

IMPLEMENTATION

Implementation is the stage of the project where the theoretical design is turned into a
working system. It can be considered to be the most crucial stage in achieving a successful new
system gaining the users confidence that the new system will work and will be effective and
accurate. It is primarily concerned with user training and documentation. Conversion usually
takes place about the same time the user is being trained or later. Implementation simply means
convening a new system design into operation, which is the process of converting a new revised
system design into an operational one.

Implementation is the stage of the project where the theoretical design is tuned into a
working system. At this stage the main work load, the greatest upheaval and the major impact on
the existing system shifts to the user department.

Implementation includes all those activities that take place to convert from the existing
system to the new system. The new system may be a totally new, replacing an existing manual or
automated system or it may be a modification to an existing system. Proper implementation is
essential to provide a reliable system to meet organization requirements. The process of putting
the developed system in actual use is called system implementation. This includes all those
activities that take place to convert from the old system to the new system. The system can be
implemented only after through testing is done and if it is found to be working according
to the specifications. The system personnel check the feasibility of the system. The more
complex the system being implemented, the more involved will be the system analysis and
design effort required to implement the three main aspects: education and training, system testing
and changeover. The implementation state involves the following tasks:

1. Careful planning.
2. Investigation of system and constraints.
3. Design of methods to achieve the changeover. Training
of the staff in the changeover phase.

Implementation Procedures: -Implementation of software refers to the final installation of

thepackage in its real environment, to the satisfaction of the intended uses and the operation of
the system. In many organizations someone who will not be operating it, will commission the
software development project. In the initial stage people doubt about the software but we have to
ensure that the resistance does not build up, as one has to make sure that

1. The active user must be aware of the benefits of using the new system. Their
confidence in the software is built up.
2. Proper guidance is imparted to the user so that he is comfortable in using the application.

Before going ahead and viewing the system, the user must know that for viewing the
result, the server program should be running in the server. If the server object is not up running
on the server, the actual process won’t take place.

User Training: -User training is designed to prepare the user for testing and converting
thesystem. To achieve the objective and benefits expected from computer based system, it is
essential for the people who will be involved to be confident of their role in the new system. As
system becomes more complex, the need for training is more important. By user training the user
comes to know how to enter data, respond to error messages, interrogate the database and call up
routine that will produce reports and perform other necessary functions.
Training on the Application Software:-After providing the necessary basic training on
computerawareness the user will have to be trained on the new application software. This will
give the underlying philosophy of the use of the new system such as the screen flow, screen
design type of help on the screen, type of errors while entering the data, the corresponding
validation check at each entry and the ways to correct the date entered. It should then cover
information needed by the specific user/ group to use the system or part of the system while
imparting the training of the program on the application. This training may be different across
different user groups and across different levels of hierarchy.

Operational Document: -Once the implementation plan is decided, it is essential that the
user ofthe system is made familiar and comfortable with the environment. Education involves
right atmosphere and motivating the user. A documentation providing the whole operations of
the system is being developed in such a way that the user can work with it in well consistent
way. The system is developed user friendly so that the user can work the system from the tips
given in the application itself. Useful tip and guidance is given inside the application itself to
help the user.

System Maintenance: -Maintenance is the enigma of system development. The

maintenancephase of the software cycle is the time in which a software product performs useful
work. After a system is successfully implemented, it should be maintained in a proper manner.
System maintenance is an important aspect in the software development life cycle. The need for
system maintenance is for it to make adaptable to the changes in the system environment.
Software maintenance is of course, far more than "Finding Mistakes". Maintenance may be
defined by describing four activities that are undertaken after a program is released for use.
 MAINTENANCE

Software maintenance is the last phase in the software Engineering process that eliminates errors
in the working system during its work span and to tune the system to any variations in its
working environment. The system requires maintenance as there may be changes and
requirements in the organizational needs, government policies, hardware and software
environment etc. often small system deficiencies are found as a system is brought into operation
and changes are made to remove them. System requirements may be revised as a result of system
usage or changing operational needs. Perhaps oversight that occurred during the development
process needs to be corrected. Often the maintenance need arises to capture additional data for
storage in a database or in transaction files or perhaps it may be necessary to add error detection
features to prevent system users from in adversely taking an unwanted action.

Maintenance of the system after it is installed is concerned with an additional factor in

hardware. Once the system is delivered and installed there is a brief warranty period during
which time the vendor is responsible for maintenance. This is a typically a 90 day period after
that time the purchaser has the option of acquiring maintenance from various sources.
Maintenance sourceexceptingvendor is also available from companies specializing in providing
the service, called third party maintenance companies.
 When the system is installed, it is generally used for long period. The average life of
system is 4-6 years, with the eldest applications often is used for over 10 years. The need for
debugging and correcting errors or failure on an emergency basic is comparatively low: less than
20% of the task of correction. System and organization are in constant state of flux, therefore, the
maintenance of the system also involved adoptions for earlier version of software.

Approximately 20% of all maintenance work is performed to accommodate changes in

report, files and database. The greatest amount of maintenance work is for user enhancement,
improved documentation and recording system components or greater efficiency. About 60% of
all maintenance is for this purposed.

Following table summarized the broad classes of maintenance found in development of [Link]

CATEGORY ACTIVITY

Corrective Emergency fixes, routine debugging.

Adaptive Accommodation of changes to data and to hardware
And software, Changes in the external environment.

Pre effective User enhancement, improved documentation recording

Of computational efficiency, user recommendations for

New capabilities.

Preventive Routine service of cleaning and adjusting the equipment

To prevent breakdowns, future maintainability reliability

Enhancement, recovering design information to improve

The overall quality.

 Maintainable Design
The points to reduce the needs for maintenance are:

1. More accurately defining the user’s requirements during the system development
assembling better system documentation.

2. Using more effective methods for designing process logic and communicating it
to project team members.

3. Making better use of existing tools and techniques.

4. Managing the system engineering process effectively.

The maintenance for Integrated Advertising System was performed with the above-mentioned
points as the underlying principles and according to the demands of the users.
 CONCLUSION

The project titled as “Library Management System” is a web-based application. This website provides facility
for posting and applyingbook freely on the web. This website is developed with scalability in mind. Additional
modules can be easily added when necessary. The website is developed with modular approach. All modules in the
system have been tested with valid data and invalid data and everything work successfully. Thus the system has
fulfilled all the objectives identified and is able to replace the existing system. The extra tools are provided in this
website like tooltip to identify the work “what to do with this website”.

The project has been completed successfully with the maximum satisfaction of the
organization. The constraints are met and overcome successfully. The system is designed as like
it was decided in the design phase. The project gives good idea on developing a full-fledged
application satisfying the user requirements.

The system is very flexible and versatile. This website has a user-friendly screen that enables
the user to use without any inconvenience. Validation checks induced have greatly reduced
errors. Provisions have been made to upgrade the website. The application has been tested with
live data and has provided a successful result. Hence the website has proved to work efficiently.
 FUTURE SCOPE

In future we add extra feature like messaging, chatting and rating to enhance the website
and to capture the crowed on the website. In the proposed system the user is provided with a
choice of data screen, which are similar in formats to the source documents. Data entry errors
can be minimized through validity checks. After the verification only the data areplaced the
permanent database. High speed, accuracy and non-redundant data are the main advantages
of the proposed system. The software can be developed further to include a lot of modules
because the proposed system is developed onthe view of future. This proposed system is
fully designed with require database. If extra database is required by administrator then we
can develop. In sort, we can deploy new release with more database, more efficiency, more
graphic design and more simplicity.

In future this project can be treated as product according to specification and needs of any
organization.
Since Bookseeker plays key role in any organization; thus, success over a long period of time and reliance of
organization over recruitment is going to be one of the most considered topic for any organization. Therefore
Books seeker Process will be of great help in carrying out recruitment process smoothly and effectively.

At present days every organization is using web technology for their proper functioning, so this
web based project is all in all important from market aspects.
Furthermore if this project will be uploaded, it can be used as Books site and any organization can register
their self on the site to carry out their recruitment process making this site as Books seeker.