Library Management System

INTEGRAL UNIVERSITY

PROJECT ON

Library Management
Syatem

Submitted To- Submitted By-

Miss. Payal Gupta Mohd Saim

BCA 6th Sem

Computer Science

Enrollment No- 182DDE2178

 Library Management System
Globus College of IT & Management
DECLARATION

I hereby declare that this project report titled “Library

Management System” has been submitted by me for the award

of certificate of PROGRAM. This is result of original work carried

out by me. This report has not been submitted anywhere else for the

award of any other internship certificate.

Mohd Saim
BCA (6th Sem)
(2018-21)
 Library Management System
ACKNOWLEDGEMENT
The success and final outcome of this project required a lot of
guidance and assistance from many people and I am fortunate to have
got this all along the completion of my project work. Whatever I have
done is only due to such guidance and assistance. This has been a
great opportunity for me to undergo my Program.

I express my whole hearted thanks to our beloved Globus College of

IT & Management, who provided necessary facilities, guidance and
endless encouragement, which help me soundly. I wish to express my
gratitude and my supervisor to Miss. Payal Gupta for his cooperation,
care & support and all the faculty members of Globus College of IT &
Management.

I would like to thank my friends and family members for their

cooperation in completing my project successfully.
Mohd Saim
BCA (6th Sem)
(2018-21)
 Library Management System

Contents
Topic

1. Introduction ……………………………………………….
2. Objectives………………………………………………….
3. System Analysis……………………………………………
Requirement Analysis….……………………………
Preliminary Investigation……………………………
Feasibility Study…………………………………….
3.3.1 Technical Feasibility
3.3.2 Economical Feasibility
3.3.3 Operational Feasibility
4. Software Engineering Paradigms…………………………..
5. Software Requirement Specification……………………….
6. Additional Hardware/Software used
7. Design………………………………………………………
DFD………………………………………………….

ER………………………………………………………..

Input-Output Design…………………………………
Database Design……………………………………..
8. Code Efficiency…………………………………………….
9. Code Optimization………………………………………….
10. Validation Checks…………………………………………
11. Testing…………………………………………………….
12. Implementation……………………………………………
13. Evaluation………………………………………………….
14. Maintenance……………………………………………….
15. System Security……………………………………………
16. Cost Estimation……………………………………………
17. Future Scope Of Project…………………………………..
18. Bibliography……………………………………………….
 Library Management System

Introduction

Technology Used: SWING, MySQL

Language: Java

Model Type: Individual/Personal

College

Report format

 
Version: 1.0
Description: First Draft
 Library Management System
Introduction to the System:

 The Library Management System is designed & developed for a receipt and issuance
of books in the library along with the student’s details. The books received in the library are
entered in Books Entry form and the new student is entered in the student entry form.
When the student wants to get the desired book the same is issued on the availability basis
to the student. The issuance and due date for the returning of the book is also entered into
the Book Issue form under third menu Book Issue. The student has to pay the fine if any on
the basis of no. of days delayed deposit of the book in the library

Problem Definition:

In our existing system all the transaction of books are done manually, So taking

more time for a transaction like borrowing a book or returning a book and also

for searching of books. Another major disadvantage is that to preparing the list

of books borrowed and the available books in the library will take more time,

currently it is doing as a one day process for verifying all records.

Library management system is a project which aims in developing a

computerized system to maintain all the daily work of library . The “Library

Management System” mainly focuses on basic operations in a library like adding

new member, new books, and updating new information, searching books and

members and facility to borrow and return books. This project has many

features which are generally not available in normal library management

systems like facility of user login and a facility of teachers login . the user is able

to generate different kinds of reports like lists of students registered, list of

books, issue and return reports.  “Library Management System” is designed to

help users maintain and organize library. 

It is used by librarian to manage the library using a computerized system where

he/she can record various transactions like issue of books, return of books,

addition of new books, addition of new students etc. Proposed system is an

automated Library Management System. It also has a facility of admin login

through which the admin can monitor the whole system . Using this system
 Library Management System
student can login system online and after logging in their accounts can see list of

books issued and its issue date and return date. Through our software user can

add members, add books, search members, search books, update information,

edit information, borrow and return books in quick time. Using library

management system, students can also request the librarian to add new books

by filling the book request form. Using this system librarian can generate various

reports such as student report , issue report, teacher report and book report.

Books and student maintenance modules are also included in this system which

would keep track of the students using the library and also a detailed description

about the books a library contains.

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. With this computerized system there will be no loss of book

record or member record which generally happens when a non computerized 

All these modules are able to help librarian to manage the library with more

convenience and in a more efficient way as compared to library systems which

are not computerized

Aim:

“To Manage Library ”.

Objective:

 To perform a thorough analysis of working of the whole

System.
 To study the problems in the System through fact
finding techniques.
 To follow SDLC to develop the system.
 To develop conceptual, logical and physical model for
the system.
 Library Management System
 To develop Graphical User Interface (GUI) as per
convenience of the user.
 To implement the physical model, being tested as per
the standards.
 To document our efforts and analysis in a proper
comprehensible manner.

Goal:

 To make a responsive, easy to operate, fast and efficient

retrieval of information as per the user's convenience.
 To provide all information about Raw Material to User
and Maintain payments of supplier and buyer.
 To provide ease in the maintenance of different types of
Raw Material Requirement.
 To make a database that is consistent, reliable and
secure.
 To provide correct, complete, ongoing information.
 To develop a well-organized information storage system.
 To make good documentation so as to facilitate possible
future enhancements.

Need of the System:

The LIBRARY MANAGEMENT SYSTEM is a software application which

avoids more manual hours in taking the book, that need to spend in record keeping
and generating reports. Maintaining of user details is complex in manual system in
terms of agreements, royalty and activities. This all have to be maintained in ledgers
or books. Co-coordinators needs to verify each record for small information also.
Easy search of book in the online library.
Avoid the manual work.
User need not go to the library for Issue any kind of book, he can renewal.

 Purpose
 Project Scope
 Existing System
 Proposed System
 Library Management System
 System Overview

Purpose:
The goal of the system is to bring down the work load with the increased efficiency and to speed up
the activities. With this it is very easy to process course fee that is collected time to time from
students who are registered and studying at franchisees

Project Scope:

The project has a wide scope, as it is not intended to a particular

organization. This project is going to develop generic software, which can
be applied by any businesses organization. More over it provides facility to
its admin. This software is going to provide daily reports to legacy systems,
which are of greater utility to the business. Also the software is going to
provide a huge amount ofsummary data, which can be used for different
kind of market analysis.
Proposed System:
Establish a method of payment right off the bat and ensure your tenants pay the
rent on time. Don't allow them to pay late. If they do, speak up immediately. Be polite but
firm.

System Overview:

The key features required in the system are as follows:

 Library Management System
1) Admin User
2) Faculty
3) Book Detail
4) Issue Book
5) Return Book
6) Student
7) Search
8) Report

1) Admin User:
Admin are categorized into their respective infrastructure and no. of
Studnets that divide the Branch.

2) Student:
It shows the no. of Students available in the Library.

3) Faculty:
It is the feature that shows the facultyin Library.

4) Book Detail
This shows the providence of Book facility such as Library that are contains
extra features.

5) Guest: This shows the information of guest customers.

6) Issue Book: This shows the offline Book Issue of the Student and
Faculty.
7) Search:

This is provided the search options of the system that can

search any related information of the system.
 Library Management System
8) Report:

This shows the reports in different fields of the system.

System Analysis

System Analysis is the main feature of the software field. It can be said that it is a sole of any
of the system. The analysis needs an expert supervision & the person should be minimum
System Analyst with the experience of 5 to 7 yrs. One can use some of the different tools to
analyze the system.
System Analysis refers to the process of examining a business situation analytically with the
intent of improving it through alternate or new better procedures and methods. More
precisely, it is a management technique that help us in designing a new system or improves
an existing system. It was done keeping the following objectives in mind
Some of the tools we have used to analyse the problem is given below:

 Identify the Organization’s need

 Evaluate System Concept for Feasibility
 Perform Economic and Technical Feasibility
 Allocate functions to Hardware, Software, database and other System Elements
 Establish Cost and Schedule Constraints
ANALYSIS TOOL:

Data Collection Tools: We have collected the information regarding the current system & procedure

which are going on. This collection helps us to understand the old systems know how.

Charting Tools: The graphical representation of system & activities help us to understand the minor

problems and the flow procedures, which can become very helpful in analysis as well as to generate

the new system requirements.

Dictionary Tools: This tool help us to maintain & record the data & description of system element

through Data items, processes & data stores. After the use of tools we have to do the analysis of a

system through main factors:

 Library Management System
Current system: We study the working of current system , which help us to collect the benefits &

limitations of the current system.

Equipments: Then we collect the information about the hardware requirement.

Space: In this we collect the information about the storage space needed in the new system.

Procedure: Which type of procedures are going on, this study s being useful to analyze that if all

procedures are doing well or if there is a need for change.

Requirement Analysis

Requirement Analysis means studying or observing the current Business System to find how

it works and where improvement can be made. It may include ways of capturing or

processing data, producing information, or supporting management.

The First step of System Analysis is the identification of need. In this regard a series of

interviews were conducted with authorized person of the institution. This was essential so as

to know the processes that were being followed.

Requirements analysis is a software engineering task that bridges the gap between system level

software allocation and software design.

System
Engineering

Software
Requirements

Analysis

Software

Design
 Library Management System

Analysis and a bridge between system engineering and software

Software requirements analysis may be divided into five areas of effort:-

(a) Problem recognition.

(b) Evaluation and synthesis.

(c) Modeling.

(d) Specification.

(e) Review.

Initially, the analyst studies the system specification and the software project plan. Problem

evaluation and solution synthesis is the next major area of effort for analysis.

Upon evaluating current problems and desired information (input and output) the analyst begins to

synthesize one or more solutions.

During the evaluation and solution synthesis activity, the analyst creates models of the system in an

effort to better understand data and control flow, functional processing and behavioral operation,

and information content. The model serves as a foundation for software design and as the basis for

the creation of a specification for the software.

 Library Management System
Preliminary Investigation
After clearly defining the requirements of the firm during Requirement Analysis then next

step is the Preliminary Investigation that is done to determine the feasibility of the System.

The purpose of the Preliminary Investigation is to evaluate Project requests.

The Data during Preliminary investigation was gathered through three Primary methods

Reviewing Organization documents -

I reviewed the Organization Documents such as forms, records, Reports, Manuals, Transaction

detail etc. These Documents clearly defined the important steps involved in the working of the Firm.

I also had a talk with concerned Manager and other related People to get information about the

Firm.

On – Site Observation -

I observed the activities of the system directly. One purpose of On-Site observation is to get as

close as possible to the Real System. I closely observed the Firm’s Environment, Workload on the

System and the Users, the method of Work and the facilities provided by the Firm to the customer.

The Physical layout of the Current System, its location and the Workflow was also observed.

Questionnaires –

Questionnaires were prepared and the employees were asked to answer them. The Questions

were in the form of Multiple-Choice Questions and Open-ended Questions. This helped in getting an

overview of the current mode of working.

The Preliminary Investigation helped me in achieving the following –

1. To Obtain a detailed description of all the Records under Processing.

2. To Obtain a detailed description of Stored Data, their uses and inter-relationship between

the data.
 Library Management System
3. To differentiate each function within the System and identify Output Data Elements,

Input Data Elements and Processing steps.

4. To identify the system processes and other functions which could be automated.

Limitation of Existing System:

The following are the limitation of the current working system:

1. Manual wok consumes time and energy.

2. Large Number of calculation and human errors are generated.

3. Scope of limited.

4. No protection of data.

5. More Stationery is required

Proposed System Description:

The following points describe the requirement for the new system:

1. The working of the system will be fully Automated and online.

2. System should provide concrete security features by assigning login password, so that only

the authorized person should access the software.

3. Various types of reports associated with different modules should be generated.

4. The system should have daily backup and restore facility to allow complete protection of

data.

5. System should be able to handle extremely large volumes of data.

6. System will have a proper and convenient user interface.

7. The working of the system will be fully Automated and online.

8. System should provide concrete security features by assigning login password, so that only

the authorized person should access the software.

 Library Management System
9. Various types of reports associated with different modules should be generated.

10. The system should have daily backup and restore facility to allow complete protection of

data.

11. System should be able to handle extremely large volumes of data.

12. System will have a proper and convenient user interface.

 Library Management System
Feasibility Study

The feasibility of a project is being analyzed with in some framework. The most important
factor is that if a project is feasible & desirable then it include in the schedule of the
management that if the clearance should be give to it or not. Normally the assessment of
feasibility depends upon some main factors like Technical, Economical and Operational.
The assessment of the “Database Management System” has the following facts.

Operational Feasibility:

1.It seems that management is very much interested in the new system.

2.The management & the user of the system are normally the same so there is no problem

about confliction the management & users.

3.Since all the work is going manually that is why there is no liking for the old system.

4.The user and management both are ready to accept the new system, so they both show keen

interest in giving the facts.

Technical Feasibility:

The technology seems sufficient to run the new system. The data holding facility is also

seems sufficient because there is not enough transaction and it can be managed easily. It

is also analyzed the hardware technology can be expanded if the data increases.

Economical Feasibility:

It is analyzed that it will benefit the company in terms of time saving as well as cost. It is also

analyzed that cost of full system investigation is not much as it is not very much complex system.
 Library Management System
Software Engineering Paradigms

Software Process Models

To solve actual problems in an industry setting , a software engineer or a team of engineers must

incorporate a development strategy that encompasses the process , method and tools.

A process model for software engineering is chosen based on the nature of the project and

application , the methods and tools to be used , and the control and deliverables that are required.

Among the various available Software Process Models (Waterfall models , spiral model Prototyping

model, etc ) the best suited for this project is the Prototyping Model .

To develop the system Proto Type Modal is applied as the company wanted to see the

software development process and appearance of the software so that the idea of the

functionally of the system can be understood. The software developed in three phases in

first phase the dry proto type is developed in which after the analysis the screens are

designed and no validation are performed and also no database functionality is

incorporated. After the demonstration of dry proto type suggestions from the client are

noted and the development process is moved to the second phase i.e. wet prototype the

actual designed is incorporated, validations are performed and the software is submitted to

the user for acceptance and testing and then after final submission of the software is

produced with user manual.

Prototyping Model

Often, a customer defines a set of general objectives for software but does not identify detailed

input, processing or output requirements . In other cases the developer may be unsure of the

efficiency of an algorithm , the adaptability of an operating system , or the form that human –

machine interaction should take . in these and many other situations , prototyping paradigm may

offer the best approach .

 Library Management System
The prototype can serve as “the first system’’. It is true that both the customer and

developers like the prototyping paradigm . Users get a feel for the actual system and

developers get to build something immediately . Yet prototyping can also be problematic for

the following reasons:

1. The customer sees what appears to be a working version of the software that the

prototype is held together “with chewing gum and a baling wire’’ unaware that in the

rush to get it working we haven`t considered overall software quality or long term

maintainability . when informed that the product must be rebuild so high level of quality

can be maintained . Too often, software development management relents.

2. The developer often makes implementation compromises in order to get a prototype

working quickly. An inappropriate operating system or programming language may be

used simply because it is available and known , an efficient algorithm may become familiar

with these choices and forget all the reasons why they were inappropriate. The less than

ideal choice has now become an integral part of the system.

 Library Management System
Software Requirment Specification

The software requirements specification is produced at the culmination of the analysis task.

The function and performance allocated to software as a part of system engineering are

refined by establishing a complete information description a detailed functional and

behavioral description, a indications of performance requirements and design constraints,

appropriate validation criteria and other data pertinent to requirements. The National Bureau

of standard IEEE and the US Department of Defense have all proposed candidate formats for

software requirements specifications. For our purpose however the simplified outline

presented may be used as a framework for the specification.

S.R.S. Of Our Project

Introduction
It states the goals and objectives of the software descriptions it in the context of

the computer – based system actually, the introduction may be nothing more than the

software scope of the planning document.

Information description
It provides a detailed description of the problem that the software must solve information

contest and relationships, flow and structure are documented . Hardware, software and human

interfaces are described for external system elements and internal software function. The

Department of Administrative Reforms and Public Grievances aims to facilitate the pursuit of

excellence in governance. It gives the information about the citizen with grievances against

public a institution and government organization viz. central Government Ministries /

departments / Organizations / State Governments /UT Administrations and services to them.

It forward all the information to citizens with grievance to the concerned Government

organization within 15days under intimation to the petition.

Functional Description
 Library Management System
It present description of each function required to solve the problem. A processing narrative

is provided for each function, design constraints are stated and justified, performance

characteristics are stated, and one or more diagrams are included to graphically represent the

overall structure of the software and interplay among software function and other system

elements under this topic, the functional working of the various modules where give the

complete picture for the data flow from one location to other. There proper linking between

them. The department of Administrative Reforms and Public Grievance aims to facilitate the

pursuit of excellence in governance through promotion of:-

(1) Improvements in Auction structures and processes.

(2) Consumer friendly initiatives including redressal of grievances.
(3) Documentation, incubation and discrimination of best practices.
(4) Codification and simplification of procedures.
(5) Internet Based.

Behavioral Description
This section of the specification examiners the operation of the software as a

consequences of external events and internally generated control characteristics. In this topic

may project shows the event flow diagram which tells us at what step what will be the result.

Validation Criteria:-
Probably the most important section of a software requirements specification is

validation criteria. The specification of the validation criteria acts as an implicit view of all

other requirements. The tests must be conducted to validate function, performance and

constraints.

In this project I have try the various steps in testing the links and connectivity of the data.
 Library Management System
Design

A thorough analysis of Information System requirements helps in defining an effective design

of the information system. This is essential so as to meet the requirements of the system in an

efficient way. Thus, System Design can be described as the process of planning the new

business system.

Following points were kept in mind while the System was designed

 That it performs the Required job

 Presents information and instructions in an acceptable fashion

 Produces accurate results

 Provides an acceptable interface and method of interaction

 Is Perceived by the users as a Reliable system.

 The Cost of the maintenance of the system should be minimum subject to the

condition that it must satisfy all user requirements

 The System must be stable under all conditions and can be easily operated

 It Conforms to the Standards

 It should be modifiable depending upon the changing needs of the user

Elements of System Design

The components of the System described during requirement analysis are the focal point in

Design of the New System.

 Library Management System
Diagrams

Books

Student

Faculty
ADMIN SYSTEM

Search

Report

Use Case Diagram between USER and SYSTEM:

Guest

Issue

Search

Report
Faculty SYSTEM

Sequence Diagram For Administrator:-

 Library Management System
Login Application Database

Login
:Request

:Validate()
:executeQuery()

Administrator Response
Show Result

Success:hide()
Failed:show()

Sequence Diagram For User:-

Login Application Database

Login
:Request

:Validate()
:executeQuery()

User Response
Show Result

Success:hide()
Failed:show()
DFD
 Library Management System

ER Digram
 Library Management System
Forms Design

Different forms are used in order to interact with the users. A Standard form which is the

‘Home Page’ is used as the first Start up form. Firstly the user is asked to enter the password.

On the basis of which the Menu form is available. On selecting a particular option from the

menu form, the event to show the appropriate screen and the associated table is evoked

accordingly.

Screen Designs
The quality of screen design can have a direct impact on the performance of the user of the

system, and the designer needs to consider the format as well as the content of the screens on

which the dialogue or interaction between the user and the system is based. A number of

features of screen design are worth discussinghere:

 Text-Must be easily readable. In addition to choosing an appropriate font and size for

the characters, readability can be improve by using lower and upper case letters, rather than

the approach sometimes adapted in screen design of using all upper case evenly Space text,

with an unjustified right margin is easier to read than right justified text, which has spaces of

varying sizes between the words. The use of concise phase, familiar vocabulary and

appropriate abbreviations make it easier for the reader to understand the text. The most

visible section of the screen is the upper left-hand corner and it is a good idea to locate

important messages in this area. Again it is important that the designers understand that the

characteristic of the in user in order to deliver quality products. Beginners, who are usually

looking at their fingers, will noticed error messages which appear on the button line on the

screen, where as the top right corner of the screen is a more appropriate location for

experienced keyboard operators.

 Library Management System
 Colour-Another set of the design option is possible, in addition to those described

above, if the display is in colour. Text can be highlighted by being in a different colour to be

rest or being enclosed in a coloured box. Background colours can be changed or a design

convention can be used in which different types of information are displayed in different

colours. The consistent use of colours on screens within the same system is important, and

the designer must be wary of using too many colours or creating lurid combination as these

will work against the effectiveness of the screen design.

 Graphics-can be used to good effect for displaying information, especially trends in

numerical data. They can be coloured, solid, three dimensional or animated and the designer

must decided on what is appropriate to the purpose. Another use of graphics is as an integral

part of the structure of the dialogue-known as a graphical user interface (GUI).

 Animation- although this is little used in screen design, it can be powerful technique

for attracting the attention of the user, because the eye is always drawn to a moving object;

to mark the position of an object, for example, a blinking cursor can be used; or to

communicate a message, a clock with a moving hand, or an hourglass with moving sand,

indicate to the user that they have to wait while some processing is carried out by the

machine.
 Library Management System
Forms
1. Splash Screen
 Library Management System

2.Login Form
 Library Management System

3.Registration Form

3. Home Page
 Library Management System

4.Admin Menu
 Library Management System
5.View Student

6.View Faculty Detail

 Library Management System
7.View Book Menu
 Library Management System
8.Search Book By Id

9.Add,Update,Delete Book
 Library Management System

10.View And Add,Update,Delete Student

11.View Faculty,Update,Delete Faculty

 Library Management System

12.View All Member

13.Issue Book
 Library Management System

14.Return Book

15.View All Issue Books

 Library Management System

16.View All Return Books

 Library Management System

Database Table

Admin User
 Library Management System
2.Book Detail

3.Faculty
 Library Management System
4.Issue Book

5.Return Book
 Library Management System
6.Student
 Library Management System
Code Efficiency

In software project we must keep a balance between the language used & the area of the

application as well as database management system were actual data is being stores. There

must be provision for those situation s which w are not meeting at the time of making the

project for example the codes should be written keeping the aspect that software should

compatible with others database or data can be migrated from outside. The information

systems are designed with space & time complexity and cost saving in mind. The coding

systems are methods in which conditions, words, ideas or relationship are expressed by a

code. A code is an ordered collection of symbols designed to provide unique identification of

an entity or attribute. It may be brief number, title or symbol. The main purpose of codes is to

facilitate the identification and retrieval of times of information from the system.

There are many possible-coding structures. The main types of codes are described below:

Classification Code: Classification is the best described as the establishment of categories of entities,

types and attributes in away that brings like or similar items together according to pre-determined

relationships. A classification is by nature an order systematic structure. So the classification code

places separate entities like events, people, or object into distinct groups called classes. A code is

used to identify one class from another. Using the code the user classifies the event into one of

several possible categories and records the code.

Classification codes vastly simplify the input process because only a single-digit code is required. The

need for writing lengthy description or making judgments is eliminated.

Function Code: Function codes states the activities or work to be performed without spelling out all

of the details in narrative statement.

 Library Management System

It has been recognized that good coding style can overcome many of the deficiencies of a

primitive programming language, while poor styles can defeat the intent of an excellent

language. The goal of a good coding style is to provide easily understood, straight-forward

and elegant code. The guidelines for coding includes:

 Use of a few standard control constants.

 Use of unconditional branching (go to) in a disciplined manner.

 Introduction of user-defined data types to model entities in the problem domain.

 Hiding of data structures behind access functions.

 Providing standard documentation prologues for each subprogram and compilation

unit.

 Use of indentation, parenthesis, and blank spaces, blank lines, borders and comments

to enhance readability.

Code Optimization

The main purpose of the optimization of code is to reduce redundancy of code, for this user

has to write procedure function for repetitive. If in two situation the same type of interface

needed then only one interface should be created and it may be called by passing different

parameter.

The basic design model uses the analysis model as the framework for implementation. The

analysis model captures the logical information about the system, while the design model

must add details to support efficient information access.

During design optimization we must:

 Add redundant association to minimize access cost and maximize convenience.
 Library Management System
 Rearrange the computation for greater efficiency.

 Saved derived attributes to avoid re-computation of complicated expression.

 During report generation we used an optimization technique of rearranging execution

order for greater efficiency.

 Redundancy of data in the tables has been removed through Normalization technique.

All the tables are designed in normalized form.

 Explicit and Implicit locks are used where needed.

 Explicit update: In this each derived attribute is defined in terms of one or more

fundamental base object. We determined that which derived attributes are affected by each

change to a fundamental attribute and inserted code into the update operation on the base

object to explicitly update the derived attribute that depends on it.

 Optimization of Resource: During coding we have kept the strict vigil to use the same

function again by writing the code in a module, so it keeps our coding minimize.
 Library Management System
Validation Checks

In the complete project there are many validation and have been used in different forms in different

ways.

Following validation checks are there in this project which are to be checked in different

modules.

 User ID should be unique, its entry can not be repeated.

 Various fields in various forms should not be left blank.

 Product id and Category ID should be unique.

 Bid_id should be unique.

 The order report of customer will be generated only if its record exists.
 Library Management System
Testing

In this section we have tested our system in different modes.

Basically the testing is done on different level like Unit testing, Integration testing , System testing

and Acceptance testing. These different testing tests different types of faults.

We have tested in the following manner and whatever the fault we have got, fixed it immediately.

Clients Need Acceptance Testing

Requirements System Testing

Design Integration Testing

Code Unit Testing

LEVEL OF TESTING
 Library Management System
Implementation

A crucial phase in then systems life cycle is the successful implementation of the new system

design. Implementation means converting a new system design into operation. This creating

computer-compatible files, training the operating staff before the system is up and running. A

major factor in conversion is not disrupting the functioning of the organization.

The implementation phase of software development is also concerned with translating design

specification into source code. it is necessary to write source code and internal and

documentation so that conformance of the code to its specification can be easily verified, and

so that debugging, testing and modification are eased. This can be achieved by making the

source code as clear and straight forward as possible. The implementation team should

therefore be provided with-defined set of software requirements. An architectural design

specification and a detailed design description.

User training is another important area, which is responsible for minimizing resistance to

change and giving the new system a chance to provide it worth. Training aids, such as user-

friendly manuals, data dictionary, and job performance aids that communication information

about the new system; help screens provide the user with a good start on the new system.

Following conversion, it is desirable to review the performance of the system and to evaluate

it against established criteria. Software maintenance follows conversion, which includes

minor enhancements or corrections to problems that surface late in the system’s operating.

Conversion:

The objective of conversion is to put the system into operation while holding costs, risks and

personal problems to a minimum. It involves three major steps:

 Library Management System
 Creating computer-compatible files

 Training the operating staff

 Installing hardware/software

Procedures and documents are unique to the conversion phase. These are shown below:

 Conversion begins with a review of the project plan, the system test documentation, and

the implementation plan. The parties involve are the user, the project team, programmers and

operators.

 The conversion portion of the implementation plan is finalized and approved.

 Files are converted.

 Parallel processing between the existing and the new system is initiated.

 Results of computer runs and operators for the new system are logged on a special form.

 Assuming no problems, parallel processing is discounted. Implementation results are

documented for reference.

 Conversion is completed. Plans for the post-implementation review are prepared.

Following the review, the new subsystem is officially operational.

File Conversion :

File conversion involves capturing data and creating a computer file from existing files.

There can be problems like staff shortage for loading data. Also, specialized training

necessary tom prepares records in accordance with the new system specifications. In most

cases, an outside agency performs this function for a flat rate. If a computerized system

already exists, then copying existing files for a new system is a concern area. Program can be

written to copy files intact for the new system and test programs on both systems. A file

comparison program can be used for this purpose.

 Library Management System
Many systems are prone to errors because of insufficient attention given to data entry control

or protective features like audit control trails. These items must be part of the overall plan of

for conversion. Before a data entry operator starts working, a data entry validation program

can be written to keep track of wrong data entered.

At the time installation of the software it is required that oracle must be installed on the server of

the company and it must contain the data files related to the software before implementing the

developed system on all machines

Connected to the server. For this the exported data is imported to the client machine and the

database is checked that all tables are properly imported to the client machine or not as the

software is developed in oracle database and also going to be implemented in oracle is no

other conversion is required.

A good audit control trail is the key to detecting fraud and errors in data entry.

User Training
Analysis of user training focuses on two factors-user capabilities and the nature of the system

being installed. The requirements of the system also range from very simple tasks like using a

pocket calculator to complex tasks like learning to program a database system. Tasks that

require the user to follow a well-defined, concrete, step-by-step procedure-require limited

problem solving. For this, the training level and duration is basic and brief.

Hardware/Software Installation

Adequate time and resources for installation of software and hardware must be allotted in the

development schedule. User can be trained on the installation procedure. The detailed

instructions can be a part of the user manual.

 Library Management System
Evaluation

Evaluation of the system is performed to identify its strength and weaknesses. The actual
evaluation can occur along any of the following dimensions:

 Operational Evaluation : Assessment of the manner in which the system functions,

including ease of use, overall reliability and level of utilization.

 Organizational Impact: Identification and measurement of benefit to the organization in

such areas as financial concerns, operational efficiency and competitive impact.

 User Manager Assessment: Evaluation of attitudes of senior and user manager within the

organization as well as end users.

 Development Performance: Evaluation of the development process in accordance with such

yardsticks as overall development time and effort, conformance to budgets and standards

and other project management criteria.

 Library Management System
Maintainence

Software maintenance is used to describe the software engineering activities that occur

following delivery of a software product to the customer.

The maintenance of existing software can account for over 60% of all effort expanded by a

development organization, and the percentage continues to rise as more software is produced.

 Activities involved in maintenance of a software product include:

 Analysis activities
 Standards and guidelines
 Design activities
 Implementation activities
 Supporting documents
 Configuration management is concerned with tracking and controlling of the work
product that constitute a software product.
 Configuration management tools include:
 Configuration management databases
 Version control libraries
 Automated tools to support software maintenance include technical support tools and
managerial support tools.
 Other automated tools include

 Text editors
 Debugging aids
 Linkage editor
Computer Maintenance covers a wide range of activities. Many activities performed during

development of Airlines Reservation System for Global Airways to enhance the

maintainability of it are as follows-

o Analysis Activities The analysis phase of software development is concerned with

determining customer requirements and constraints and establishing feasibility of the product.
 Library Management System
From maintenance view point, the most important activities that occur during analysis are

establishing standards and guidelines for the project and the work products to ensure

uniformity of the products; setting of milestones to ensure that the work products are produce

on schedule; specifying quality assurance procedures to ensure development of high quality

documents; identifying product enhancements that will most likely occur following initial

delivery of the system; and estimating the response (personnel, equipment, floor space)

required to perform the maintenance activities.

o Standards and Guidelines Various types of standards and guidelines we developed to

enhance the maintainability of our software.

o Design Activities Design is concerned with developing the functional components,

conceptual data structures and interconnection in a software system. The most important

activity for enhancing maintainability during the design.

Automated tools to support software maintenance include technical support tools and

managerial support tools. Tolls to support the technical aspects of software maintenance

span the spectrum from analysis and design tools to implementation to debugging the

testing tools. Automated tolls include text editors debugging aids, cross-reference

generators, linkage editors, comparators, complexity metric calculators, and version

control system and configuration management databases. Text editors permit a rapid,

efficient modification of source programs, test data and supporting documents. Text

editors can be used to insert the replace segments of source code, internal comments, test

data and supporting documents; to systematically change the occurrences of an identifier

or other textual strings to locate all references to a given identifier or other string of text;

and to save both old and new version of a routine, test files or document. A syntax-
 Library Management System
directed text editor can ensure that all cross-references in the supporting documents are

correctly updated.

Debugging aid provide traps, and traces assertion checking and history file aid in locating the

causes of known errors. System-level-cross-reference generators provide cross-reference

listing of procedure calls, statements usages and data references. Cross-references directories

provide the calling structures of who calls whom and for where, and procedures names and

statements numbers where formal parameters local variables and global variables are defined,

set and used.

 Library Management System
System Security

System must provide built-in feature of security and integrity of data without sage guard against

unauthorized development access, fraud, even embezzlements, fire and natural disasters, a system

could be so well vulnerable as to threaten the survival of the organization.

To do an educated job on security a system analyst must analyse the risk exposure and cost

and specify measures such as password and encryption to provide protection. In addition

backup copy of the software and recovery restart procedure must be available when needed.

A disaster/recovery that has management support should also be prepared. Then no matter

that the disaster, the firm can recover.

The strength behind integrity and success is ethics and professional standards of behavior.

When ethics are compromised regardless of technology.

The main objective during the development of this system, which kept in mind, are

A. The various threats to system security and their defenses.

B. How to do risk analysis and specify measures

C. The importance of disaster recovery planning and how such a plan is initiated.

D. The meaning and importance of ethics in system development.

We also followed following methods for the development of this system for the security
reasons.

1. Recovery of table structure with detail of full of modification date and time.

2. Password feature support by the software.

 Library Management System
3. Detail of nomenclature of variable and acronyms use Assumption of system failure

and recovery.

4. No unauthorized user can use the software without providing correct login and

password.

5. The system should have daily backup and restore facility and restore facility to

complete protection to data.

 Library Management System
Cost Estimation

For a given set of requirement it is desirable to know how much it will cost to develop the software

to satisfy the given requirements & how much time development will take.

NEED:

For a given set of requirements it is desirable to know how much it will cost to develop the

software to satisfy the given requirements, and how much time development will take. These

estimates are needed before development is initiated. The primary reason for cost and

schedule estimation is to enable the client or developer to perform a cost benefit analysis and

for project monitoring and control. A more practical use of these estimates is in bidding for

software projects, where the developer must give cost estimates to a potential client for the

development contract.

The Cost of our project has been projected in the following manner-

As we know that cost estimation for a project is due to the requirements for software,

hardware resources and human resources. In hardware it includes computer time, terminal

time & memory required for the project. Besides it software development is due to the human

resources needed & the most cost estimation procedure focus on this aspect.

We have found that we should follow the “COCOMO MODEL” will suit the best of

calculation of estimation of our project.

We have also projected our cost on the basis of person /month on for all Cost Drivers and

Project Duration in months.

The COCOMO model defined for three classes of software projects are :-
 Library Management System
1) Organic Model: - Relatively small, simple projects in which small teams with good
application experience work to a set of les than rigid requirements.

2) Semidetached Model: - An intermediate (in size and complexity) software project

in which teams with mixed experience levels must meet a mix of rigid and less than
rigid requirements.

3) Embedded Model: - A software project that must developed within a set of tight
hardware, software and operational constraints.
The basic COCOMO equation takes the form-

E = ab KLOCbb

D = CbEdb

When E is the effort applied in person months, D is the development time in

chronological months, and KLOC is the estimated number of delivered lines of code for the
project.(Expressed in thousands). The coefficient ab and Cb
and the exponents bb and db where taken as.

This project is an organic project so :-

ab = 3.2
bb = 1.05
cb = 2.5
db = 0.38
LOC = 1555

KLOC = 1555/1000 = 1.555

E = 3.2 (KLOC)1.05
= 3.2 (1.555)1.05
= 3.84

= 4 person - months
 Library Management System
New calculate the D is the development time in chronological months
D = 2.5 E 0.35
= 2.5 (4) 0..35
= 4.06 months
= 4 months approximately
The computer project duration we use the effort estimated described above
N = E/D
= 4/4
= 1 person
Where N is the recommended number of people for the project.
_________________________________________________________
 Library Management System
Future Scope of the Project.

This software is made according to the requirement of organization but expansion of modules
can be easily included in the software.
This package can be used in internet environment that will make handling of different
customers easier..

Following features can be added for enhancement :

 This software can be used for B2B and B2C sites.

 A proper revenue model for the system can be defined.
 With slight modifications it can be made to work or to fit into any such organization.

Future expandability and interconnectivity are the features, which are considered for scope in

future.

Software Development

The total span of developing the Database Management System that I got was 3 months. During this

duration, I was involved in the different aspects of system development viz. System analysis, System

design and development.

In this limited period of time, it was impossible for me to devote as much time as I would have

wanted, on each of the phases.

Despite this limitation, the project gave me an opportunity to understand and learn about the

various phases of the Software development life cycle.

 Library Management System
It was a good opportunity for me to learn about the various phases of System development in depth,

by means of documents, System Study and interacting with System users and further clarifications of

doubts with the guide.

Since it was an individual activity, it helped me even more to strive harder to gain invaluable

experience and knowledge to handle a software development project.

Conclusion

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 MY SQL 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
 Library Management System
only improves the efficiency but will also reduce human stress thereby
indirectly improving human recourses.
 Library Management System
Bibliography

1. Software Engineering- A Practitioner’s Approach

–Roger S. Pressman.(Mc Graw Hill International Edition).

2. Core JAVA :Volume One

-by Martyn Hall and Larry Browrn(Person Publication)

3. Java Complete Reference

- by Herbert Schint.(Mc Graw Hill International Edition).

4. An integrated approach to software engineering

- by Pankaj Jalote.