1

TABLE OF CONTENTS
Acknowledgement

Preface of
project..
Certificate
.
Introduction to
project
Project
objectives
Advantages

System development
lifecycle.
Feasibility
study
Drawback of the existing
system.
Project
plan
Development
tools..
Tables
used..

Modules
used.
E-R
diagram.
Front end
used.
Coding

reference of the project

ACKNOWLEDGEMENT
For most of all we express our indebt to the Almighty for
bestowing us with the favorable circumstances and keeping us in
high spirits.
No human endeavor can be accomplished without constant
guidance and support .I am very much pleased to bring out this
report in schedules time, for this credit a feeling of elevation
insists us on expressing our heartiest thanks and gratitude to our
coordinators and project guide Ms. Heena Karla of his valuable
guidance and constant encouragement during the course of
project of library management system and enabled us to reach
this stage. Without whose unique guidance and supervision along
with constructive critics and immense help, this project would
never have. I would like to express my gratitude and offer sincere
thanks to my friends.

Last but not list I would like to thank the parents without their
hearted support this project would have not been completed.

PREFACE OF THE PROJECT

Library management system as per now is a website that s going
to be used to manage the flow of books in a library. With the
intentions of having it as our software
. Its a very tedious, time consuming as well as error prone job
dealing with manual database will depend more on the
administrator. Its developed generally to help on the
management of books in a single library. A user can be able to
access books online. And can order them online and the delivery
can be done to their door steps.

CERTIFICATE
This is to certify management system embodies the original
work that is done by NICHOLAS SSELYAZI,NANZIRI CLARE and
BERNICE MUSANINKA during project submission as fulfillment
of the requirement for the system design project of Bachelors of
Computer Application(6th semester) of PUNJAB COLLEGE OF
TECHNICAL EDUCATION.

INTRODUCTION OF THE PROJECT

Library management system ensures the effective use of the
texts books that will be available in the book store. This
management can be able to record a number of texts books in the
data base. Unlike the file system. Where by the details were used
to be stored in files. And they could succumb to some problems
give like the termite, fire hazards, and rats, among others. This
can store any number of data because its storage is unlimited.

PROJECT OBJECTIVES
As all other projects, this project has its objectives that are being
followed as it is being developed.
To handle all primary information required to calculate
monthly statements. Separate database is maintained to
handle all the details required for correct statement
calculation and generation.
To introduce more user friendliness in the various activities
such as record updating and maintenance .
Similarly, record maintenance and updating can also be
accomplished by using the identification of the customer
with all details being automatically generated. These details
are also being promptly automatically updated in the master
file thus keeping the record absolutely up to date.
The system has maintained in the database or files and
however wants to retrieve cant retrieve unless authorized.
More security

For publicity purposes

Less time consuming
Proper database
Easy to use(user interface)
Work transforms from manual to automatic
Feedback
ADVANTAGES
I have designed the given proposed system in the Asp.Net to
automate the process of the book store/Library. This project is
useful for the authorities which keep track of all the users
registered.
The following steps that give the detailed information of the need
of proposed system are:

Performance: During past several decades, the records are

supposed to be manually handled for all activities. The manual
handling of the record is time consuming and highly prone to
error.

To improve the performance of the Library Management System,

the computerized system is to be undertaken. This project is fully
computerized and user friendly even that any of the members can
see the report and status of the company.

Efficiency: The basic need of this website is efficiency. The

website should be efficient so that whenever a new user submits
his/her details the website is updated automatically. This record
will be useful for other users instantly.

Control: The complete control of the project is under the hands

of authorized person who has the password to access this project
and illegal access is not supposed to deal with. All the control is
under the administrator and the other members have the rights to
just see the records not to change any transaction or entry.

Security: Security is the main criteria for the proposed system.

Since illegal access may corrupt the database. So security has to
be given in this project.

TOOLS/PLATFORM
This project is developed using the tools, which are most suited
for development of the application package. These tools are as
follows:
1. Asp.Net (for font end)
Advantages
It has a very good graphical user interface
It has online coding
Its compatible to sql database very well
It is user friendly
2. SQL SERVER (for database storage as back end)

HARDWARE AND SOFTWARE REQUIREMENTS

Minimum Hardware Requirements:
Processor:
Memory:

Intel Pentium IV
1GB

Hard disk:
Monitor:

4GB
VGA Color Monitor

Minimum Software Requirements:

Operating system: Windows XP onwards

Application software: Asp.Net (front end)
SQL SERVER (for database as back end)

System Study & Analysis

PRINCIPLES OF SYSTEM ANALYSIS
1. Understand the problem before you begin to create the
analysis model.
2. Develop prototypes that enable a user to understand how
human machine interaction will occur.
3. Record the origin of and the reason for every requirement.
4. Use multiple views of requirements like building data, function
and behavioral models.
5. Work to eliminate ambiguity.

SYSTEM DEVELOPMENT LIFECYCLE

This concept has 7 stages:

10

1.
2.
3.
4.
5.
6.
7.

Recognition of need
system analysis
system feasibility study
system design
code generation
implementation
post implementation

recognition of need
In recognition of need without a clear understanding in the
system, any further work done will lead to wastage of time
and effort at later stages. Hence various questions must be
posed identifying correct problem like.

what is the actual problem

cause of the problem
if it is important to solve problems or not.
Types of benefits expected after the problem is
solved.
The advantage of recognition of need in SDLC
(System Development Life Cycle) i.e. that it helps in
pinpointing the problem, setting proper system
goals, determining the boundaries of project by
taking into consideration the limitation of existing
systems. All the information of Lab inventory is
recorded manually.

System feasibility study

The feasibility study proposes one or more
conceptual solutions to the problem set for project.
The conceptual solution gives an idea of what the
new system will look like. Feasibility study defines
what will be done on computer.it is important to
consult the users to see if the computerized data
recording function satisfies users objectives and can
be fitted into current system operation. The major

11

outputs of this phase are technical feasibility report,

cost benefit analysis report, operational feasibility.
It consists of the following:
1. statement of the problem
2. Summary of the findings and recommendations
3. Details of findings
4. Recommendations and conclusions
5.
There are basically three types of feasibility are
addressed in the study:1. Technical feasibility
2. Economic feasibility
3. Behavioral feasibility

Technical feasibility
Technical feasibility ensures that the considered engineering
concept does not violate the laws of physics. For example, a
feasible device cannot deliver more energy or material than
is put into the device.

Behavioral feasibility
An estimate should be made of how strong a reaction the
user staff is likely to have towards the development of a
computerized system. It is common knowledge that the
computer installations have something to do with turnover,
transfers and changes in employee job status.

Economic feasibility
Analysis of a projects costs and revenues in an effort to
determine whether or not it is logical and possible to
complete.

System analysis
The proposed library management system will enable faster
information processing regarding various business processes
helping the staff to better serve their customer needs in

12

lesser time aimed at enriching the overall customer

experience. Introduction this project is aimed at building a
management information system using computer. It is not
preliminary study. It is a depth study of the end user
information needs that produces functional requirements
that are used as the basis for the design of a new
information system.
It extracting the requirements of the desired software
product is the first task in creating it. While customers
probably believe, they know what the software is to do. It
may require skill and experience in software engineering to
recognize incomplete, ambiguous or contradictory
requirements.
System involves detailed study of:

a.

The information needs of the organization and end user.

b.

The activities, resources and products of any present

information system.

c. The information system capabilities required to meet your

information needs.

System design
During the design phase, we focus on the operation of the
system. As in this phase we designed the architecture and
interface of website and decided and where to store data and how
I should flow. We decided to use ASP.Net based platform that
provides users flexible and extendable modules templates to
support integration of web pages.

1. Logical design phase

2. Physical design phase

13

LOGICAL DESIGN PHASE:

A data flow diagram shows the logical flow of the
system and defines the boundaries of the system. For a
candidate stem it describes the input (source), out bases and
procedure all in a format that meets the user requirement .

PHYSICAL DESIGN:
This produces the working system by defining the
design specification that tells programmers exactly what the
candidate system must do. In turn the programmer writes
the necessary programs or modify the software packages
that access input from user, performs the necessary
calculations, produces the reports on a hard copy or display
it on the screen.

Objectives
Successful completion of the design phase should comprise
Transformation of the requirements into detailed
specifications covering all aspects of the system.
Assessment and planning for security risks.
Approval to progress to development phase.

Goals
The purpose of the design phase is to transform the requirements
into complete and detailed system design specifications. Once the
design is approved, the development team begins the
development phase. System design can be viewed as the design
of user interface data, process and system specification.

14

System

User interface

design

design

Data

design

System

specification

Process design

Coding and Testing

When design is finished, coding will then begin. This phase is the
way of creating new system, it involves coding of computer
programs compilation and testing of program, link testing and
integration of web pages.
Good software development organizations normally require their
programmers to adhere to some well-defined and standard style
of coding called coding standards. Most software development

15

organizations formulate their own coding standards that suit them

most and require their engineers of an organization to adhere to a
standard style of coding is the following.
A coding standard gives a uniform appearance to the codes
written y different engineers.
It enhances code understanding.
It encourages goo programming practices.

Coding standards lists several rules to be followed during coding,

such as the way variables re to be named, the way the code is to
be named, the way the code is to be laid out error return
conventions, etc.
Coding standards and guidelines:Good software development organizations usually develop their
own coding standards and guidelines depending on what best
suits their organization and the type of products they develop.

The following are the representative coding standards:Rules for limiting the use of global: These rules list what type f
data can be declared global ad what cannot.
Contents of the headers preceding codes for different modules:
The information contained in the headers of different modules
should be standard for the organization. The exact format in
which the header can be specified. The following are some
standard header data:
Name of the module
Date on which the module was created

16

Authors name
Modification history
Synopsis of the module
Different functions supported along with their input/output
parameters
Global variables accessed/modified by module

Naming conventions for global variables, local

variables and constant identifiers: A possible naming
convention can be that global variable names start with
capital letter, local variable names are made of small letters
and constant names are always capital letters.

Error return conventions and exception handling

mechanisms: The way error conditions are reported by
different functions in a program are handled should be
standard within an organization. For example, different
functions while encountering an error condition should either
return 0 or 1 constantly.

The following are some representative coding guidelines

recommended by many software development organizations.

17

Do not use the coding style that is too clever or too

difficult to understand:
code should be easy to understand . many inexperienced
engineers actually take pride in writing cryptic and
incomprehensible code. Clever coding can obscure meaning
of the code and hamper understanding. It also makes
maintenance difficult.

Avoid obscure side effects: The side effects of function

call include modification of parameters passed by reference,
modification of global variables and I/O operations. An
obscure side effects make it difficult to understand a piece of
code. For example, if a global variable is changed obscurely
in called module or some file I/O is performed which is
difficult to infer from the functions name and header
information, it becomes difficult for anybody for anybody
trying to understand the code.

Do not use an identifier for multiple purposes:

Programmers often use the same identifier to denote several
temporary entities for example, some programmers use a
temporary loop variable for computing and storing final
result. The rationale that is usually given by these
programmers for such multiple uses of variables is memory
efficiency, e.g. three variables use up three memory
locations, whereas the same variable used in three different
ways uses just one memory location. However, there are
several things wrong with this approach and hence should be
avoided. Some of the problems caused by use of variables
for multiple purposes as follows:

18

Each variable should be given a descriptive name indicating

its purpose. This is not possible if an identifier is used for
multiple purposes. Use of variable for multiple purposes can
lead to confusion and make it difficult for somebody trying to
read and understand the code.
Use of variables for multiple purposes usually makes future
enhancements more difficult.

The code should be well documented: As rule of thumb,

there must be at least one comment line on the average for
every three source line.

The length of any function should not exceed 10

source lines: A function that is very lengthy is usually very
difficult to understand as it probably carries out many
different functions. For the same reason, lengthy functions
are likely to have disproportionately larger number of bugs.

Do not use go to statements: Use of go to statements

makes s program unstructured and makes it very difficult to
understand.

Testing

Similar to the system development lifecycle, testing also has

a lifecycle. As testing is a part of the SDLC, some of the
testing phases are combination of two different SDLC
phases. Testing lifecycle has three different phases viz. test

19

analysis phase, test planning/ test designing phase, test

execution phase.

Test analysis phase: In this phase, a tester needs get an

understanding about the project.

Test Design phase: In this phase, a tester needs to design

the test cases based on the requirements and use cases.

Tests Execution phase: In this phase, a tester needs to

execute the test cease written by him or her or any other
resource and raise the defects, if any.

Various testing techniques:-

Acceptance testing
Testing the system the system with the intent of
Confirming readinesss of the product and customer acceptance.

Adhoc testing:Testing without a formal test plan or outside of a test plan. With
some projects this type of testing is carried out as an adjunct to
formal testing .if carried out by a skilled tester, it can often find
problems that are not caught in regular testing. Sometimes, if
testing occurs very late in the development cycle, this will be only

20

kind of testing that can be performed. Sometimes ad hoc testing

is referred to as exploratory testing.

Alpha testing:Testing after code is mostly complete or contains most of the

functionality and prior to users being involved. Sometimes a
select group of are involved. More often this testing will be
performed in house or by an outside testing firm in close
cooperation with the software engineering department.
Automated testing:Software testing that utilizes a variety of tools to automate the
testing process and when the importance of having a person
manually testing is diminished. Automated testing still requires a
skilled quality assurance professional with knowledge of the
automation tool and software being tested to set up tests.

Beta testing:Testing after the product code complete. Betas are often widely
disputed or even distributed to the public at large in hopes they
will buy the final product when it is released.
Black box testing :Testing software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests.
As most other kinds of tests, must be written from a definitive
source document, such as specification or requirements
document.
Configuration testing:-

21

Testing of determine how well the product works with a broad

range of hardware/peripheral equipment configurations as well as
on different operating systems and software.
Compatibility testing:Testing used to determine whether other system software
components such as browsers, utilities and competing software
will conflict with software being tested.
Functional testing:Testing two or more modules together with the intent of finding
defects demonstrating that defects are not present, verifying that
the module performs its intended functions as stated in
specification and establishing confidence that a program does
what it is supposed to do.
Independent verification and validation:The process of exercising software with the intent of ensuring that
the software system meets its requirements and user
expectations and doesnt fall in an unacceptable manner.
Installation testing:Testing with the intent of determining if the product will install on
a variety of platforms and how easily it installs.
Integration testing:Testing two or more modules or functions together with the intent
of finding interface defects between the modules or functions.
Testing completed at as a part of unit or functional testing and
sometimes becomes its own standalone test phase. On a larger
level, integration testing can involve a putting together of groups
of modules and functions with the goal of completing and
verifying that the system meets the system requirements.(see
system testing).
Load testing:-

22

Testing with the intent of determining how well the product

handles competition for system resources. The competition may
come in form of network traffic, CPU utilization or memory
allocation.
Performance testing:Testing with the intent of determining how quickly a product
handles a variety of events. Automated test tools geared
specifically to test and fine tune performance are used oust often
for this type of testing.

Pilot testing:Testing that involves the users just before actual release to ensure
that users become familiar with the release contents and
ultimately accept it.
Regression testing:Testing with the intent of determining if bug fixes have been
successful and have not created any new problems. Also, this
type of testing is done to ensure that no degradation of baseline
functionality has occurred.
Security testing:Testing of database and network software in order to keep
company data and resources secure from mistaken/ accidental
users, hackers, and other malevolent attackers.
Software testing:The process of exercising software with the intent of ensuring
that software system meets its requirements and users
expectations and doesnt fail in an unacceptable manner.
Stress testing:-

23

Testing with the intent of determining how well a product

performs when a load is placed on the system resources that
nears then exceeds capacity.
System integration testing:Testing a specific hardware/software installation. This is typically
performed on a COTS system or any other system comprised of
disparate parts where custom configurations and /or unique
installations are the norms.
User acceptance testing:-see acceptance testing

Implementation
Here, the project team actually constructed and installed the
website base on users feedback and requirements. The next step
is to put all onto site finity and make the different changes to
meet the user requirements.

Its the realization of an application. Or execution of a plan idea,

model, design, specification, standard, algorithm, or policy.
Implementation is a stage where theory is converted into
practical. The implementation is vital step in ensuring the success
of new systems. Even a well-designed system can fail if it is not
properly implemented.

Post implementation and maintenance

Once a system if fully implemented and being operated and end
users, the maintenance function begins. Systems maintenance is

24

monitoring, evaluating and modifying of operational information

system to make desirable or necessary improvements.

THE MODEL USED IS WATERFALL MODEL

Waterfall model: is the simplest process modes, which states
that the phases are organized in a linear order. There are various
variation the waterfall models depending on the nature of
activities and flow of control between them.
Sometimes called the classic left cycle suggests a systematic
sequential approach to software development that begins with
customer specification of requirements and progresses through
planning modeling, construction and development in ongoing
support of the completed software.
Requirements

ANALYSIS

DESIGN

25

CODING

testing

Acceptance

Advantages of waterfall model:

1. It is simple model of software development which follow the
sequence approach.
2. The large and complex task of building a software broken
into smaller task.
3. Buggies and errors found in early stages is chapter in terms
of money efforts and time to fix then the some buggies
found later.
4. It also provides us with all the requirement at an early stage
to modification in requirement after the couching are less.
5. Waterfall models emphasis on making documents at every
stages of water models.
Disadvantages of waterfall model:
1. It is good for small projects.
2. Clint may not be aware of all the requirements in the starting
phase.
Each phase must be completed before moving the next phase.

26

E-R DIAGRAMS
An entity relationship diagram is a specialized graphic that
illustrates the relationship between entities in the database. E-R
diagram often use symbols to represent three different types of
information.

In software engineering, an entity relationship model (E-R model

in short) is an abstract way to describe a database. It usually
starts with a relational database, which stores the data in tables.

Some of the data in these tables point to the data in other tables
for instance, your entry in the database could point to several
entries for each of the phone numbers that are yours.

27

The ER model would say that you are an entity and each phone
number is an entity, and the relationship between you and the
phone numbers is has a phone number.

Diagrams created to design these entities and relationships are

called entity relationship diagrams or ER diagrams.
Symbols:Attribute:-ovals are used to represent attributes.

Entity:-boxes are commonly used to represent entities.

Relationship:- diamonds are normal uses to represent

relationship.

The entity relationship (ER) model

ER model forms the basis of an ER diagram.

28

ERD represents the conceptual database as viewed by end user.

ERDs depict the ER model three main.

Components:
Entities
Attributes
Relationships

Entities
Refers to the entity set and not a single entity occurrence.
Corresponds to a table and nor to row in the relational
environment
In both the Chen and Crow foot models an entity is
represented by by a rectangle containing the entity name.
Entity name, noun, is usually written in capital letters.

Attributes
Characteristics of entities.
In Chen model, attributes are represented by ovals and are
connected to the entity rectangle with a line.
Each oval contains the name of the attribute it resents.
In the Crow Foot models, the attributes are simply written in
the attribute box follow the entity rectangle.

29

DRAW BACKS OF THE PRESENT SYSTEM

1. Fast report generation is not possible.
2. Tracing a book is difficult.
3. Information about issue /return book are not properly
maintained.
4. No central data base can be created as information is not
available in the database.
5. Repetition of work.
6. Online access is not allowed.
7. Long time process

E-R DIAGRAMS

TABLES USED
ADMIN TABLE

30

FEEDBACK TABLE

GENERATE FINES TABLE

31

GENERATE ORDER TABLE

ISSUE TABLE

PENDING BOOKS

32

PURCHASE BOOKS TABLE

33

PURCHASE TABLE

RETURN BOOK TABLE

34

USER TABLE

NEW USER TABLE

35

CODING PART OF THE PROJECT

ADMIN

USER

36

ISSUE

GENERATE ORDER

37

PURCHASE

RETURN

38

GENERATE FINES

PENDING BOOKS

39

FEEDBACK

FRONT END OF THE PROJECT

40

ADMIN

USER

ISSUE

41

GENERATE ORDER

PURCHASE

42

RETURN

43

GENERATE FINES

PENDING BOOKS

44

FEEDBACK

REFFERENCES
1.http://www.librarymanagement.com
project lectures with Mrs. heena Karla
2.www.microsoftstore.com/in/visual studio
About.com/visual+studio+premium+2010
3.www.metachdata.com/Btrieve-to-MySQL
4. www.about.com/Data+Base+Programming