LIBRARY MANAGEMENT SYSTEM

PROJECT REPORT

Submitted to partial fulfillment of the requirement

For the award of the degree of

BY

1
 PREFACE

As a part of our computer Application we have to do this project.

No doubt practical knowledge is very much essential for computer
students, as there is a vast difference between theoretical and
practical knowledge. It is because that Computer Science is a
branch where everyday new technologies are coming up and new
ideas are developing.

The project has been discussed in detail in the following part this
report.

2
ACKNOWLEDGEMENT

3
 SOFTWARE REQUIREMENT SPECIFICATION

The customer requirements identified during the requirements

gathering and analysis activity are organized into a SRS document.
The important components of these documents of this document
are the functional requirements, the non-functional requirements
and the goals of implementation. The SRS document is written
using the end-user terminology. This makes the SRS document
understandable by the customer. The SRS document be received
and approved by the customer. The SRS document normally serves
as a contract between the development team and the customer.
SRS must be thoroughly understood by the developer team and
reviewed jointly with the customer. The analyst should be aware of
the desirable qualities that every good SRS document should
possess. Some of the identified desirable qualities of the SRS
documents are concise, structured, black box view, conceptual
integrity, and response to undesired events, verifiable.

4
 CONTENTS

1. INTRODUCTION Page no.

a. Introduction to the existing system 7
b. Limitation of the existing system 8
c. Introduction to the project 9
d. Objective of the project 10
e. Salient features 12
f. Advantages 12
g. Environment Used 13

2. SYSTEM ANALYSIS
a. Model Used 15
b. Feasibility Study 16
i. Objectives of the study
ii. Technical feasibility
iii. Economic Feasibility
iv. Legal Feasibility
v. Finding of Feasibility study
c. System Specification 19
i. Hardware Specification
ii. Database 19
iii. Programming Language 20

3.CODING 21

4. DESIGN 22

5.E-R DIAGRAM 23

6.DFD 24

7.ALL TABLE 31

5
8.SNAPSHOTS 34

10. PROGRAMMING CODE

12.TESTING
i. Unit testing
ii. Integration testing
iii.System testing

11. MAINTENANCE

12. ADVANTAGES OF MAKING THIS SYSTEM

13. LIMITATIONS AND DRAWBACKS
14.FURTHER ENHANCEMENT

15.CONCLUSION
16. BIBLIOGRAPHY

6
CHAPTER 1

INTRODUCTION:

• Introduction to the Existing System

• Limitation of the Existing System
• Introduction of the Project
• Objective of the Project
• Environment Used

INTRODUCTION TO THE EXISTING SYSTEM

Before developing any computerized system, it is imperative; to

examine initially the problem in the existing system and also

7
ascertain the basic needs that should be fulfilled by the proposed
system .The primary aspect of developing a full-fledged automated
system would be to learn the current procedure and the information
flow, to locate the problems in the existing system, to locate the
problems in the existing system, to identify what resources are
used and to discuss with the user and their authority as what
improvement must be made in the existing system.
Till now the entire procedure has been managed manually, but as
time changes and technology steps into the new generation a
computerized system is required which will remove the drawbacks,
and shall also support new technology.
The existing system has many drawbacks and limitation. Until
now if any student wanted to access the information he had to
check the database thoroughly and the system has to go through
many interdependencies between the various forms to get data
from student. That is very inconvenient and also time consuming.
A new way is required that will remove these drawbacks of the
existing system; if the student is already aware of the shelf then he
can save a lot of time.
Most important to the interface, it is not very student friendly, as
the existing system has to go through many data inter dependencies
between the various forms. It takes data from user in different
forms instead of only one form, which is much more economical in
time. So it is important to make an efficient and convenient system
that includes all the additional functionalities.

LIMITATION OF THE EXISTING

SYSTEM

8
The need for computer-based automation was felt because of the
limitations of the existing register based manual interface.

• First is the checking the dependency manually.

• Secondly, it doesn’t have user-friendly environment that’s
why it’s very inconvenient & time consuming in practice.
• A system was required which could facilitate the people in
accessing the data efficiently and quickly. This system has
been developed for need of a common library, which uses
manual system.
• Fast and Automatic system makes the system more economic
and attractive.
• Manual systems may cause data inconsistency, redundancy
and in security whereas automatic system shows error
messages in all wrong attempts.

INTRODUCTION TO THE
PRODUCT

9
 Before getting into the details of the project, here is a brief
introduction into what has been actually done. For effective
utilization of available resources, timely availability of accurate
information effectively, is required.

To achieve this objective ASP.NET & SQL SERVER has been

used. Managing information is an indispensable part of any
organization. In fact it’s very important for any developer, it stores
and processes huge amount of data. It will manage all kinds of
information of all books of the library and the student’s
information also. So we have to gather all information relating to
the current system so that no problem occurs during
implementation.

The interface is very simple and efficient. The various parts of he

software normally have different functions that are based on access
rights of the system.

Security of the information’s is maintained by preventing access

to unauthorized users with the help of the password option.

THE USER
Any student of the college, who wants to access any data item,
has to register himself/herself to the Administrator of the system

10
i.e. to the librarian of the college, their he or she get a user id. By
knowing it he or she can access the system.

THE FUNCTION OF THIS SYSTEM

 Member can see any information about himself or herself.
 Member can search book information
 Librarian can manipulate the data items.
 Librarian can issue/return books.
 Calculate the book penalty.

OBJECTIVE OF THE PROJECT

 To facilitate the students in retrieving and storing of data
items.
 To rebuild the old system old system- this provides a user-
friendlier environment.

11
SAILENT FEATURES
 User friendly.
 Efficient.
 Saves a lot of time.
 Easy movement through the different screens.
 Ease of sending request for any item, just by a click.
 Tremendous saving of time for both students and the
librarians.

ENVIRONMENT USED

HARDWARE SYSTEM
INTEL PENTIUM (P4 2.4) WITH 512MB RAM,

12
 40GB HDD

SOFTWARE SYSTEM
OS: Windows XP Professional
Language: ASP.Net
Database: SQL Server 2005

CHAPTER 2

SYSTEM ANALYSIS

• Model Used

13
 • Feasibility Study
• System Specification

MODEL USED
System Analysis and design are very important aspect of any
system development process. These two are the steps of SDLC.
SDLC stands for System Development of Life Cycle, which
represents the actual processes, happened during the development
of any system.

14
 I have followed the ‘Evolutionary Model’ in developing the
Library management System. The following figure shows the
SDLC of any system in Evolutionary of system development.

Rough requirement specification

Identification Core and other parts to be develop

incrementally

Develop core part using Iterative Waterfall Model

Collect customer feedback and modify requirements

Develop the next identified features using an iterative

Waterfall Model

Maintenance

Evolutionary Model of Software Development

FEASIBILITY STUDY
Objectives of the study:

15
 The objectives or main aims of this study are to ascertain if the
current can be improved in any way through any means.
The part of the system to be improved is the aspect
involve in the dealings of problems of users who may
be student or faculties or the librarian.

There are three type of feasibility study, they are:

 Technical feasibility
 Economical feasibility
 Behavioral feasibility

Technical feasibility:

In technical feasibility we will check the possibility of the

technology that support the required system and functions. In short
we will check that whether the system is technically possible.

In technical feasibility all the technical aspects of the project are

studied. Since my job was to develop a new system as the library
wanted to have a web-enable Library Management System, so that
it can serves its library and the users across the college. So I have
studied on the line that whether it is possible to develop such a
system.

The consideration that a normally associated with technical

feasibility include.

Development risk analysis:

16
 It was taken into consideration that whether the system element
can be design so that necessary functions and performance can be
achieved uncovered during analysis.

Resource availability:

It include, whether the components and resources are available

that are required to develop this report and what are the necessary
resource required to build the system?

Technology:

Has the relevant technology progress to a state that will support

the system?

Economic feasibility:

It includes an assessment of the economic justification for a

computer-based system. In economical feasibility all the
economical aspects of the project are studied. Since in this case
there was not any consideration of money as all the tools used in
this project work are already available here like PENTIUM PC
with windows 98/2000/xp as operating system, SQL Server 2005
as database and programming language like ASP.NET.

Behavioral feasibility: People are inherently resistance to change,

and computer has been known to facilitate change. Estimation

17
should be made of house strong is the reaction uses staff is likely
to have to words the development of a computerized system.

Finding of feasibility study:

Since we ware very much clear about the design of the system so
in the analysis of the development risks we found that it is quite
difficult to design the proposed system that it can support all the
functions desired by the Library in the system.

 All the resources necessary to develop the software ware

available to me, like software case tools, user manual or
book.
 The present state of technology support in this type of
system. In fact, there are already many such type of system
developed by the other commercial organization.
 There was not any problem in economic feasibility of this
project, as stated above that all the resources necessary for
this project ware available.
 Also this system does not produce any legal problems, as it
is not violating any law of our country. It also does not
violate any copyright of other legal or sub judiciary law.

18
DATABASE

SQL SERVER 2005

SQL SERVER is a Relational Database Management System.

The goal in a relational database is to build a database in which
only the data changes and not the underlying structure itself. It is
an excellent system that is used as back-end. The client, sometimes
called the presentation layer, is where information is displayed to
the user, and input is accepted for processing.

 The application layer is where all the processing is done

according to the logic being implemented by the system.
 The data layer, often called the back-end, plays a role in the
storage of information to satisfy requests placed by the
application layers.

The use of the database also aims at the commercial aspect of the
product since the product is planned to be implement at various
different installations in future and they all must have SQL
SERVER previously involved.

19
PROGRAMMING LANGUAGE

ASP.NET

Microsoft’s ASP.NET is a server-side scripting technology that

can be used to create dynamic and interactive Web applications.
An ASP.NET pages is an HTML page that contains server-side
scripts that are processed by a web server before being sent to the
user’s browser. You can combine ASP with Extensible Markup
Language (XML) and Hyper Text Markup Language (HTML) to
create powerful interactive Web Sites. ASP.NET coding is more
“compact” than ASP code; the scripts required to perform a given
function are shorter in ASP.NET than they are in ASP. Since the
server-side script is building a regular HTML page, it can be
served to almost any browser. An ASP.NET file can be created by
using any text editing tool, such as notepad. ASP.NET is built on
the Common Language Runtime (CLR), allowing programmers to
write ASP.NET code using any supported. NET language.

20
CODING:

Coding is understandable once the design phase is complete and

the design documents have been successfully reviewed. In the
coding phase, every module identified and specified in design
document is independently coded and unit tested. Testing a
software product is as much challenging as the initial development
activities such as specification, design and coding. Testing
involves a lot of creative thinking. The input to the coding phase is
the design document. The objective of the coding phase is to
transform the design of a system, as given by its module
specification, into a high-level language code and to unit test this
code. A coding standard gives a uniform appearance to the codes
written by different engineers. Code should be easy to understand
and well document.

21
DESIGN:

Design is a creative activity whose aim is to establish the multi-

faceted qualities of objects, processes, services and their systems in
whole life cycles. Therefore, design is the central factor of
innovative humanization of technologies and the crucial factor of
cultural and economic exchange. Design is the planning that lays
the basis for the making of every object or system. It can be used
both as a noun and as a verb and in a broader way, it means applied
arts and engineering. As a verb “to design” refers to the process of
originating and developing a plan for product, structure, system or
component with intention. As a noun, “a design” is used for either
the final plan or the result of sense no other limitations exist and
the final product can be anything from clothing to graphical user
interfaces to skyscrapers. The person designing is called a design.

22
 Author
Subject Year
Rack_no
Name Librarian_I
D Passwor
Available_no
Book_acc_no d
N N 1
Books Manage Librarian
s
1

Sear
ch Issue
/Retu Manag
rn es

M N
Book_acc_noo
Member_id MembersM

Status N
IS A

Teacher_i departmen
fine d t
Issue_dat Chec
e k
Issue_statu Return_date
Student Teacher
s
Stud_rol
l DOJ
name name
gender phone DOJ
address phone
course address
semester

E-R Diagram for Library Management System

DATA FLOW DIAGRAM

23
 Book query

Library Maintenance
Check
Status
Librarian
Member Managem
ent System Request for
Reply
report

Get Report

Context Diagram for Library

Management System

View
Status
Datastore

Subject
Member_id Book_info
Member
Log
In Search

24
 request

Librarian_id
information
Select type
Librarian
Log In Manipulate Issue/
Return

update

update
Data store

Level 1: DFD

Book
name
Search
by Book
Book
name

Information

Author Information
name
Search Book Database
by
Search 25
Author
by ID
 information

Id no.
Id no.

Level 2: DFD(Sub process of Search)

Info

Manipulate
Book
Update Database

Update
Database
Info
Database
Manipulate
Student

26
Info Update Database
Manipulate
Teacher

Level 2: DFD(Sub process of Manipulate)

Info Add
Book
Details Update Database

Update Database
Info Update Book Database
Book
Details
Delete
27
Book
Details
 Update Database
Info

Level 3: DFD(Sub process of Book Manipulation)

Info
Add
Student Update Database
Details

Update Database
Update
Delete Student Database
Student
Studen 28
tDetails
Details
Info

Update database

Info

Level 3: DFD(Sub process of Student Manipulation)

Info Add
Teacher Update Database
Details

Update Database
Info Update Teacher Database
Teacher
Details

Delete
Teache 29
r
Details
 Update Database
Info

Level 3: DFD(Sub process of Teacher Manipulation)

Table name:book

Attributes Data Type

book_acc_no varchar(10)
book_name varchar(MAX)
subject varchar(MAX)
author varchar(20)
year varchar(20)
rack_no varchar(10)
available_no int

Table name:book_status

Attributes Data Type

30
book_acc_no varchar(10)
book_status varchar(10)

Table name:department

Attributes Data Type

department_id nchar(10)
department_name nchar(10)
decipline nchar(10)
No_of_semester int

Table name:issue_status

Attributes Data Type

book_acc_no varchar(10)
member_id varchar(10)
issue_date datetime
due_date datetime
return_date datetime
fine int
issue_status varchar(10)

31
Table name:student

Attributes Data Type

stud_roll varchar(10)
stud_name varchar(20)
date_of_birth datetime
stud_gender varchar(10)
stud_course varchar(10)
stud_semester varchar(5)
stud_address varchar(MAX)
stud_phone bigint
year_of_join int

Table name:teacher

Attributes Data Type

teacher_id varchar(10)
teacher_name varchar(20)
date_of_join datetime
course varchar(10)
teacher_address varchar(MAX)
teacher_phone bigint
year int

32
SNAPSHOTS

33
STUDENT LOGIN

34
ADMIN OPTIONS

35
ISSUE BOOK

36
 RETURN BOOK

PROGRAMMING CODE
using System;
using System.Data;
using System.Configuration;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;

37
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;
using System.Data.SqlClient;

namespace LibrarySystem
{
public class Library
{
SqlConnection con;
SqlDataAdapter da;
DataSet ds ;
SqlDataReader dr;

public struct Teacher

{
public string teacher_id;
public string teacher_name;
public string department;
public long teacher_ph;
public string address;
public DateTime doj;
}

public struct Student

{
public string student_id;
public string name;
public DateTime dob;
public string gender;
public string course;
public string semester;
public string address;
public long phone_no;
public int join_year;
}

public struct bookissue

{
public string book_accno;
public string member_id;
public DateTime book_issueDate;
public DateTime dueDate;
public DateTime returnDate;
public int fine;
public string issueStatus; }

public struct books

{
public string book_Acc_no;

38
 public string book_name;
public string subject;
public string author;
public int year;
public int rack_no;
public int available_no;
}

public int DeleteBook(String bookid)

{
if (con.State == ConnectionState.Open)
{
con.Close();
}
con.Open();

da.DeleteCommand = new SqlCommand("delete from book where

book_acc_no=@book_acc_no",con);
da.DeleteCommand.Parameters.Add(new
SqlParameter("@book_acc_no", SqlDbType.VarChar)).Value = bookid;

return da.DeleteCommand.ExecuteNonQuery();

public int UpdateBooks(string book_id, books b)

{
if (con.State == ConnectionState.Open)

39
 {
con.Close();
}
con.Open();

da.UpdateCommand = new SqlCommand("update book set

book_name=@book_name,subject=@subject,author=@author,year=@year,price=@
price,edition=@edition where book_acc_no=@book_acc_no", con);

using (SqlCommand x = da.UpdateCommand )

{
x.Parameters.Add(new SqlParameter("@book_acc_no",
SqlDbType.VarChar)).Value = b.book_Acc_no.ToUpper();
x.Parameters.Add(new SqlParameter("@book_name",
SqlDbType.VarChar)).Value = b.book_name.ToUpper();
x.Parameters.Add(new SqlParameter("@subject",
SqlDbType.VarChar)).Value = b.subject;
x.Parameters.Add(new SqlParameter("@author",
SqlDbType.VarChar)).Value = b.author;
x.Parameters.Add(new SqlParameter("@year",
SqlDbType.Int)).Value = b.year;
x.Parameters.Add(new SqlParameter("@price",
SqlDbType.Int)).Value = b.price;
x.Parameters.Add(new SqlParameter("@edition",
SqlDbType.Int)).Value = b.edition;

return x.ExecuteNonQuery();
}

public int AddBook(books b)

{
if (con.State == ConnectionState.Open)

40
 {
con.Close();
}
con.Open();
da.InsertCommand = new SqlCommand("insert into book
values(@book_acc_no,@book_name,@subject,@author,@year,@price,@edition)"
, con);
using (SqlCommand x = da.InsertCommand)
{
x.Parameters.Add(new SqlParameter("@book_acc_no",
SqlDbType.VarChar)).Value = b.book_Acc_no.ToUpper();
x.Parameters.Add(new SqlParameter("@book_name",
SqlDbType.VarChar)).Value = b.book_name.ToUpper();
x.Parameters.Add(new SqlParameter("@subject",
SqlDbType.VarChar )).Value = b.subject ;
x.Parameters.Add(new SqlParameter("@author",
SqlDbType.VarChar )).Value = b.author ;
x.Parameters.Add(new SqlParameter("@year",
SqlDbType.Int)).Value = b.year ;
x.Parameters.Add(new SqlParameter("@price",
SqlDbType.Int)).Value = b.price;
x.Parameters.Add(new SqlParameter("@edition",
SqlDbType.Int )).Value = b.edition ;

return x.ExecuteNonQuery();
}

public int BookReturn(string member_id,string book_acc_no)

{
if (con.State == ConnectionState.Open)
{
con.Close();
}
con.Open();

da.UpdateCommand = new SqlCommand("update issue_status set

issue_status='RETURNED' where book_acc_no='" + book_acc_no + "' and
member_id='" + member_id + "'",con );

return ( da.UpdateCommand.ExecuteNonQuery());

public int BookIssue(bookissue b)

{

41
 if (con.State == ConnectionState.Open)
{
con.Close();
}
con.Open();

da.InsertCommand = new SqlCommand("insert into

issue_status(book_acc_no,member_id,issue_date,due_date,return_date,fine
,issue_status)" +
"values(@acc_no,@member_id,@issue_date,@due_date,@return_da
te,@fine,@issue_status)", con);

using (SqlCommand x=da.InsertCommand )

{
x.Parameters.Add(new SqlParameter("@acc_no",
SqlDbType.VarChar)).Value = b.book_accno.ToUpper();
x.Parameters.Add(new SqlParameter("@member_id",
SqlDbType.VarChar)).Value = b.member_id.ToUpper() ;
x.Parameters.Add(new SqlParameter("@issue_date",
SqlDbType.DateTime )).Value =b.book_issueDate ;
x.Parameters.Add(new SqlParameter("@due_date",
SqlDbType.DateTime )).Value = b.dueDate ;
x.Parameters.Add(new SqlParameter("@return_date",
SqlDbType.DateTime )).Value = System.Data.SqlTypes.SqlDateTime.MinValue;
x.Parameters.Add(new SqlParameter("@fine",
SqlDbType.Int )).Value = 0;
x.Parameters.Add(new SqlParameter("@issue_status",
SqlDbType.VarChar)).Value = b.issueStatus ;

return x.ExecuteNonQuery();
}
}

public int DeleteStudent(Student t)

{
if (con.State == ConnectionState.Open)
{
con.Close();
}
con.Open();

42
 da.DeleteCommand = new SqlCommand("delete from student
where stud_roll=@roll", con);
da.DeleteCommand.Parameters.Add(new SqlParameter("@roll",
SqlDbType.VarChar)).Value = t.student_id ;
return da.DeleteCommand.ExecuteNonQuery();

public int UpdateStudent(Student s)

{
if (con.State == ConnectionState.Open)
{
con.Close();
}
con.Open();

da.UpdateCommand = new SqlCommand("update student set

stud_name=@name,date_of_birth=@dob,stud_gender=@gender,stud_course=@cou
rse,stud_semester=@semester," +
"stud_address=@address,stud_phone=@phone,ye
ar_of_join=@yoj where stud_roll=@roll", con);

using (SqlCommand x = da.UpdateCommand )

{

x.Parameters.Add(new SqlParameter("@roll",
SqlDbType.VarChar)).Value = s.student_id;
x.Parameters.Add(new SqlParameter("@name",
SqlDbType.VarChar)).Value = s.name;
x.Parameters.Add(new SqlParameter("@dob",
SqlDbType.DateTime)).Value = s.dob;
x.Parameters.Add(new SqlParameter("@gender",
SqlDbType.VarChar)).Value = s.gender;
x.Parameters.Add(new SqlParameter("@course",
SqlDbType.VarChar)).Value = s.course;
x.Parameters.Add(new SqlParameter("@semester",
SqlDbType.VarChar)).Value = s.semester;
x.Parameters.Add(new SqlParameter("@address",
SqlDbType.VarChar)).Value = s.address;
x.Parameters.Add(new SqlParameter("@phone",
SqlDbType.BigInt)).Value = s.phone_no;
x.Parameters.Add(new SqlParameter("@yoj",
SqlDbType.Int)).Value = s.join_year;

return x.ExecuteNonQuery()
}
}
public int InsertStudent(Student s)
{
if (con.State == ConnectionState.Open)
{
con.Close();
}
con.Open();

43
 da.InsertCommand = new SqlCommand("insert into
student(stud_roll,stud_name,date_of_birth,stud_gender,stud_course,stud_
semester," +
"stud_address,stud_phone,year_of_join)value
s(@roll,@name,@dob,@gender,@course,@semester,@address,@phone,@yoj)",con
);

using (SqlCommand x=da.InsertCommand )

{

x.Parameters .Add(new SqlParameter("@roll",

SqlDbType.VarChar)).Value = s.student_id;
x.Parameters.Add(new SqlParameter("@name",
SqlDbType.VarChar)).Value = s.name;
x.Parameters.Add(new SqlParameter("@dob",
SqlDbType.DateTime)).Value = s.dob;
x.Parameters.Add(new SqlParameter("@gender",
SqlDbType.VarChar)).Value = s.gender;
x.Parameters.Add(new SqlParameter("@course",
SqlDbType.VarChar)).Value = s.course;
x.Parameters.Add(new SqlParameter("@semester",
SqlDbType.VarChar)).Value = s.semester;
x.Parameters.Add(new SqlParameter("@address",
SqlDbType.VarChar)).Value = s.address;
x.Parameters.Add(new SqlParameter("@phone",
SqlDbType.BigInt)).Value = s.phone_no;
x.Parameters.Add(new SqlParameter("@yoj",
SqlDbType.Int)).Value = s.join_year;

return x.ExecuteNonQuery();

}
}

public int deleteTeacher(Teacher t)

{
if (con.State == ConnectionState.Open)
{
con.Close();
}
con.Open();

44
 da.DeleteCommand = new SqlCommand("delete from teacher
where teacher_id=@teacher_id",con);

da.DeleteCommand.Parameters.Add(new
SqlParameter("@teacher_id", SqlDbType.VarChar)).Value = t.teacher_id;

return da.DeleteCommand.ExecuteNonQuery();

public int updateTeacher(Teacher t)

{
if (con.State == ConnectionState.Open)
{
con.Close();
}
con.Open();

da.UpdateCommand = new SqlCommand("update teacher set

teacher_name=@name , teacher_department=@department
,teacher_phone=@phone," +
"teacher_address=@address,date_of_join=@doj where
teacher_id=@teacher_id",con );
using (SqlCommand x=da.UpdateCommand )
{
x.Parameters.Add(new SqlParameter("@teacher_id",
SqlDbType.VarChar)).Value = t.teacher_id ;
x.Parameters.Add(new SqlParameter("@name",
SqlDbType.VarChar)).Value = t.teacher_name;
x.Parameters.Add(new SqlParameter("@department",
SqlDbType.VarChar)).Value = t.department ;
x.Parameters.Add(new SqlParameter("@phone",
SqlDbType.BigInt )).Value = t.teacher_ph ;
x.Parameters.Add(new SqlParameter("@address",
SqlDbType.VarChar)).Value = t.address ;
x.Parameters.Add(new SqlParameter("@doj",
SqlDbType.DateTime )).Value = t.doj ;

return x.ExecuteNonQuery();
}

public int InsertTeacher(Teacher t)

{
if (con.State==ConnectionState.Open )
{
con.Close();
}
con.Open();

45
 da.InsertCommand = new SqlCommand("insert into
teacher(teacher_id,teacher_name,teacher_department,teacher_phone,teache
r_address," +
"date_of_join,year)
values(@teacher_id,@teacher_name,@teacher_department,@teacher_phone,@te
acher_address,@date_of_join,@year) ", con);

using (SqlCommand cmd = da.InsertCommand)

{
cmd.Parameters.Add(new SqlParameter("@teacher_id",
SqlDbType.VarChar)).Value = t.teacher_id;
cmd.Parameters.Add(new SqlParameter("@teacher_name",
SqlDbType.VarChar)).Value = t.teacher_name ;
cmd.Parameters.Add(new
SqlParameter("@teacher_department", SqlDbType.VarChar)).Value =
t.department ;
cmd.Parameters.Add(new SqlParameter("@teacher_phone",
SqlDbType.BigInt )).Value = t.teacher_ph ;
cmd.Parameters.Add(new SqlParameter("@teacher_address",
SqlDbType.VarChar)).Value = t.address ;
cmd.Parameters.Add(new SqlParameter("@date_of_join",
SqlDbType.DateTime )).Value = t.doj ;
cmd.Parameters.Add(new SqlParameter("@year",
SqlDbType.Int )).Value = DateTime.Now.Year ;

return cmd.ExecuteNonQuery();

public Library()
{
con = new
SqlConnection(ConfigurationManager.ConnectionStrings["Lib"].ConnectionS
tring );
da=new SqlDataAdapter();
ds = new DataSet();
}

46
 public SqlDataReader ConnecReader(String ConnectStr)
{
if (con.State== ConnectionState.Open )
{
con.Close();
}
con.Open();

dr = new SqlCommand(ConnectStr , con).ExecuteReader() ;

return dr;
}
public DataSet ConnecReader2(String ConnectStr)
{
if (con.State == ConnectionState.Open)
{
con.Close();
}
con.Open();

da.SelectCommand = new SqlCommand(ConnectStr, con);

da.Fill(ds);
return ds;
}
}

CHAPTER 6

47
TESTING

Unit Testing
Integration Testing
System Testing
Alpha Testing
Beta Testing
Acceptance Testing

System testing is the stage of implementation, which is aimed at

ensuring that the system works accurately and efficiency before
live operation commences. The logical design and the physical
design is thoroughly and continually examined on paper to

48
ensure that they will work when implemented. Thus system
test in implementation was a confirmation that all is correct
and opportunity to show the users that the system works.
Testing of the Library Management System was performed in three stages:
• Unit Testing
• System Testing
• Acceptance Testing
The minimum requirement of all three stages is:
• Load the library management application software
• Create the necessary data structures and populate
the database with the respective sample
• Create the necessary user permission
• All the tests must be conducted in correct sequence
• Make the transaction data ready
• Ensure expected results are available for
verification purpose

Unit Testing

During the implementation phase each component of the design

is implementation as a program module, and each of these program

49
modules is unit tested. Unit testing is the testing of different units
or modules of a system in isolation.

Purpose:
• To test the field level validations
• To test whether the objects in the form like alerts and
prompts are working or not
• To test whether the form confirms to all the standards
• To test whether all the functions available on the form are
working or not

Testing Done By: Members of the development team

INTEGRATION TESTING

During the integration module of the system is integrated using

integration plan. The integration plan specifies the steps and the
order in which modules are combined to realize the full system.

50
Purpose:
• To testing whether the module performs its intended task
• Once all the modules have been integrated and tested
system testing can at art

Testing Done By: Members of development team

SYSTEM TESTING

System tests are designed to validate a fully developed system

with a view to assuring that it meets its requirements. There are
three types of system testing.

51
Alpha Testing: Alpha testing refers to the system testing that is
carried out by the testing within the organization.

Beta Testing: Beta testing is the system testing performed by a

select group of friendly customers.

Acceptance Testing: Acceptance testing is the system testing

performed by the customer to determine whether or not to the
delivery of the system.

Purpose:
• To test if the module interfaces with other modules of the
system
• To test if the module satisfies the requirement of the
library
• Or not
• To test if the report formats, queries are as per
requirement of library

Testing Done By: Member of development team

DIFFERENT METHODS OF TESTING

White Box Testing

52
 White box testing is a test case design method that uses the
control structure of the procedural design to derive test
cases. Using the white box testing methods, I derived test
cases that

 Guarantee that all independent paths within a module have

been exercised at least once
 Exercise all logical decisions on their true and false sides
 Execute all loops at their boundaries and their operational
bounds
 Exercise internal data structures to ensure their validity

Black Box Testing

Black box testing methods focus on the functional requirements

of the software. That is black box testing enabled us to derive sets
of input conditions that will fully exercise all functional
requirements for a program. Black Box testing is not an alternative
to white box techniques. Rather it is a complementary approach
that is likely to uncover a different class of errors than white box
methods. 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 and termination errors

CHAPTER 7

53
• Maintenance
• Advantages
• Limitations
• Further Enhancements

54
SOFTWARE MAINTENANCE

Maintenance is the enigma of system development.

Maintenance can be classified as corrective, adaptive and
perfective. Adaptive maintenance means changing the program
function. Perfective maintenance means enhancing the
performance or modifying the program to respond to the user’s
additional or changing needs. Maintenance covers a wide range of
activities, including correcting coding and design errors, updating
documentation and test data and upgrading user support.

Several MIS organizations have done to attack the ever-growing

problem of software maintenance through maintenance reduction-
plan that consists of three phases.

Maintenance management audit

Software system audit
Software modification

Maintenance management audit is done through interviews and

questionaries, evaluates the quality of maintenance effort.

Software system audit which entails an overall view of the system

documentation and an assessment of the quality of data files and
databases and system reliability and efficiency.

55
ADVANTAGES OF MAKING THE SYSTEM

 Only authorized user can use the system due to the user_id
protection.
 The entire task is to be done automatic, so lots of time will
save.
 Provides friendlier interface.

56
LIMITATIONS AND DRAWBACKS

Though it was planned for this system to be absolutely perfect

but everything as such has certain limitations, so does this system.

The main of the system was to keep the user as thin as possible so
that the forms are loaded very fast; the above case is because the
forms are static. They interact with the database; every time they
are loaded thus system tends to be bit slowly.

The user has no facility to change his password. All updates can
perform by system administrator.

57
FURTHER ENHANCEMENT

In this Library Management System, all requirements of user and

administrator are mostly covered by requirement analysis of user
and administrator. But if any further requirement will be required
for this system then the enhancement of this software will
performed again and again.

58
CONCLUSION

The last few months, in which we were involved in the project,

were full of good experiences and lot of learning too. We learn a
lot from this project forward to better our project if possible.

Our aim was to build Library management System that could

yield a good result. Every module needs a good Management of a
library.

59
 Bibliography

We are grateful to the authors of these

books and the founder of those websites,
for helped us a lot.

Reference Books:

Professional ASP.NET(3.5) -Wrox

Programming in c# -E.Balagurusamy
PL/SQL –Ivan Bayross
Software Engineering –Rajiv Mall

Reference Websites:

 www.google.co.in
 www.hit.net
 www.w3schools.com

60