DIGITAL LIBRARY SYSTEM

A project work report submitted to the

Department of Computer Applications
in partial fulfillment of the requirements for the award of the degree of
BACHELOR OF COMPUTER APPLICATIONS

Submitted in December 2021 by

L. AASHIKA - 2019UCA01
V. RAMYA - 2019UCA12
V. SANGEETHA - 2019UCA14

Under the Guidance of

(Smt).P.LOGAMBAL.M.E.,
Assistant Professor, Department of Computer Applications
SRI SARADA COLLEGE FOR WOMEN
(An Autonomous Institution)
(Affiliated to Manonmaniam Sundaranar University, Tirunelveli-627012)
Institution recognized u/s 2(f) and 12(B) of UGC & Re- accredited with ‘A’ Grade by NAAC
(A Branch of Sri Ramakrishna Tapovanam, Tirupparaithurai)
Ariyakulam, Maharaja Nagar Post, Thoothukudi NH,
TIRUNELVELI-627 011, TAMIL NADU, INDIA.
 CERTIFICATE

This is to certify that this project work titled “DIGITAL LIBRARY SYSTEM” is a

bonafide work of L.AASHIKA, V.RAMYA and V.SANGEETHA of Final Computer

Applications, Sri Sarada College for Women (Autonomous), Tirunelveli -627011 in partial

fulfillment of the requirements for the award of degree of BACHELOR OF COMPUTER

APPLICATIONS during the academic year 2021 - 22.

PRINCIPAL HEAD OF THE DEPARTMENT INTERNAL GUIDE

EXTERNAL EXAMINER
 DECLARATION

We do hereby declare that this project work titled “DIGITAL LIBRARY SYSTEM”

was carried out by all of us jointly for the award of the degree of BACHELOR OF

COMPUTER APPLICATIONS is our original work.

(L. AASHIKA) (V. RAMYA) (V. SANGEETHA)

Signature of the Internal Guide

ACKNOWLEDGEMENT
 We express our deep gratitude to our Secretary Yatiswari Saravanabhavapriya Amba’s

blessings. We wish to convey our respect to our Principal Dr.(Smt)Kamala, M.Com., M.Phil.,

B.Ed., PGDCA., Ph.D., for her ceaseless support.

With deep sense of respect, we profusely thank Smt.P.Anusha.,MCA.,M.Phil.,DGT.,

Assistant Professor & Head, Department of Computer Applications for her constant

encouragement.

We all submit our honest and humble reverence to our guide (Smt).P.Logambal.,M.E.,

for her consistent review, constructive suggestion and critical interpretation throughout the work

which enabled us to complete this project harmoniously and successfully.

We further acknowledge the inquisitive interactions of faculty members at the

department, our beloved parents and siblings at home and our classmates and contemporary

graduate friends who have rendered their help and time directly and indirectly.

TABLE OF CONTENTS
S.NO DESCRIPTION PAGE NO

1 SYNOPSIS
2 SYSTEM SPECIFICATION
2.1 Hardware Specification
2.2 Software Specificationn
2.3 Software Description

3 SYSTEM ANALYSIS
3.1 Existing System
3.2 Proposed System
3.3 Need For Computerized

4 SYSTEM DESIGN
4.1 Input Design
4.2 Output Design
4.3 Database Design

5 SYSTEM DEVELOPMENT
5.1 Project Description

6 FUTURE ENHANCCEMENT
7 CONCLUSION
8 BIBLIOGRAPHY
9 ANNEXURE
9.1 Data Flow Diagram
9.2 Screen Design
9.3 Source Code
9.4 Reports
SYNOPSIS

SYNOPSIS
 Library is a collection of sources of information and similar resources, made
accessible to a defined community for references or browsing. The process of handling the
activities of Library System provides a comprehensive way to lessen physical labor, to reduce
complexity of the manual system. This project aims to design and implement a Digital library
system. Digital Library System (DLS) is a software system that is based on a defined architecture
and provides all functionality. It is a generic software system that provides the infrastructure to
produce and administer a Digital Library. Digital library System project is used to maintain
books stock, book issue details, return of book details, penalty details for late renewal. Digital
Library System which is used to computerized the library system, so that all the transactions
become fast and efficient. The Digital Library System will help the librarians in simplifying the
manual work. The student and librarian benefit from the system, which allows them to keep track
of all of the books available in the library. It allows both the administrator and the student to look
for the book they want. The design of the digital library system assumes that there will be many
indexes and catalogues that can be searched to discover information before retrieving it from a
repository. These indexes may be independently managed. Simulation of Digital Library System
project is being developed to help the end users as well as staff to maintain the library. This is the
best possible way and it reduces the time complexity.
 SYSTEM SPECIFICATION

SYSTEM SPECIFICATION

HARDWARE SPECIFICATION
Processor : AMD PRO A4-4350B R4, 5 COMPUTE CORES 2C+3G 2.50 GHz

RAM : 4.00GB

SOFTWARE SPECIFICATION

Server Side Programming : ASP.NET 2.0

Middleware Programming : C#

Operating System : Windows 10

Web Server : Internet Information Server 7.0

Client Script : HTML, CSS and Java Script

Data Base : SQL-Server 2008 R2 Express

SOFTWARE DESCRIPTION

ASP.NET FRAME WORK

 The Microsoft ASP.NET framework is a software framework that can be
installed on computer running Microsoft Window operating system. It includes a virtual machine
that manages the execution of programs written specifically for the framework.

The framework’s base class library provides a large range of features

including user interface, data and data access, data base connectivity, cryptography, web
application development, numerical algorithms and network communications. The class library
is used by programmers, who combine it with their own code to produce applications.

Programs written for the ASP.NET framework execute in a software

environment that manages the program’s runtime requirement. Also part of the ASP.NET
framework, this runtime environment is known as the Common Language Runtime (CLR). The
CLR provides the appearance of an application virtual machine so that programmers need not
consider the capabilities of the specific CPU that will execute the program. The CLR also
provide other important services such as security, memory management and exception handling.
The class library and CLR together constitute the ASP.NET framework.

ASP.NET, the next version of ASP is a programming framework used to

create enterprises class web applications. These applications are accessible on a global basis
leading to efficient information management. The advantage ASP.NET offers is more than just
the next version of ASP.

SCRIPTING LIMITATIONS

ASP applications relay on VBScript which suffers from a number of

limitations. To overcome these problems, developers usually need to add separately developed
components, which add a new layer of complexity. In ASP.NET, web pages are designed in a
modern .NET language, not a scripting language.

ADVANTAGES USING ASP.NET

 ASP.NET drastically reduces the amount of code required to build large applications.
 ASP.NET makes development simpler and easier to maintain with an event-driven,
server-side programming model.
 ASP.NET pages are easy to write and maintain because the source code and HTML are
together.
 The source code is compiled the first time the page is requested. Execution is fast as the
web server compiles the pages first time it is requested. The server saves the compiled
version of the page first for use next time the page is requested.
 The source code is executed on the server. The pages have lots of power and flexibility
by this approach.
 The HTML produced by the ASP.NET pages is sent back to the browser. The application
source code we write is not sent and is not easily stolen.
 ASP.NET makes for easy deployment. There is no need to register components, because
configuration information is build-in.
 The web server continuously monitors the pages, components and applications running
on it. If it notices memory leaks, infinite loops, other illegal software or activities, it
seamlessly kills those activities and restarts itself`
 ASP.NET validates information entered by the user without writing the single line of
code.
 ASP.NET easily works with ADO.NET using data binding and page formatting features.
 ASP.NET applications run after and counter large volumes if user without performance
problems.

VALIDATION CONTROLS
 A validation controls enables as to validate an input and display and error
message if necessary. It is very much like other server-side controls with certain additional
methods and properties. First, the server treats it is an invisible control. After the user has entered
erroneous data, it becomes visible. This is powerful rapid applications development feature;
however, a developer needs to understand its behavior and the methods thoroughly before we
can appreciate it. There are certain rough edges in the beta 2 version, which hopefully will be
polished in the final product. The best strategy to learn the family if controls is to learn them one
at a time, and finally to apply the summary validation.

Various types of validation controls are as follows:

Required Field Validation: Validation succeeds as long as the input control does not contain an
empty string.

Range Validation: Validation succeeds if the input control contains a value within a specific
numeric, alphabetic, or data range.

Compare Validation: Validation succeeds if the input control contains a value that matches the
value in another, specified input control.

Regular Expression Validation: Validation succeeds if the value in an input control matches a
specified regular expression.

Custom Validation: Validation is performed by a user-defined function.

SQL SERVER
 SQL is a fourth generation relational database management system. In general, a
Relational database management system (RDBMS) must be able to reliably manage a large
amount of data in a multi-user environment so that many users can concurrently access the same
data. All this must be accomplished while delivering high performance to the users of the
database. A RDBMS must also be secure from unauthorized access and provide efficient
solutions for failure recovery. The SQL Server provides efficient and effective solutions for the
major database features.

FEATURES

 Content Management for the Internet

Everything necessary to transform data into powerful Internet applications and content-
driven Web sites is included with SQL. It provides a Web development environment that
allows software developers to easily build dynamic, data-driven Web sites with a
standard Web browser and the SQL database.
 Data Warehousing and Very Large Data Bases (VLDB)
SQL offers many new features and enhancements for the data warehousing and VLDB
environment. The performance of queries is dramatically increased by materialized views
and summary management, which allow frequently requested summaries to be stored and
maintained.
DATABASE FEATURES
The SQL database server provides a new extensibility framework, making it easier for
ISVs and other developers to extend the database to meet their needs. Many object relational
enhancements have been incorporated into this release, and this functionality has been extended
to all SQL product configurations.
 Partitioning Enhancements
 System Management
 SQL Parallel Server
 Distributed Systems
 Networking, Security, and SQL Advanced Security

ADVANTAGES OF SQL
ATOMICITTY
That is Results of a transaction's execution are either all committed or all rolled back. 

CONSISTENCY
The database is transformed from one valid state to another valid state. Illegal transactions
aren't allowed and, if an integrity constraint can't be satisfied then the transaction is rolled back. 

ISOLATION
The results of a transaction are invisible to other transactions until the transaction is
complete thus increasing the security on data.

DURABILITY

Once committed (completed), the results of a transaction are permanent and survive
future system and media failures and thus ensuring maintenance and protection of data.

 Efficient recovery from human errors 

 Faster database recovery 
 Helps in simplifying the management and administration processes
SYSTEM ANALYSIS

SYSTEM ANALYSIS
EXISTING SYSTEM

In our existing system all the transaction of books are done manually, so taking more
time for a transaction like borrowing a book and also for searching of members and books.
Another major disadvantage is that to prepare 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. So after conducting the feasibility study we decided to make the manual library system
to be computerized.

PROPOSED SYSTEM

Proposed system is a Manual Digital Library System. Through our software, librarian can
add publication, add books, add branch of study, add student, issue book, and return book and
penalty. Also, students can view their account, penalty report, book report in quick time. Our
proposed system has the following advantages.

 User friendly interface

 Fast access to database
 Less error
 More storage capacity
 Search facility
 Look and feel environment
 Quick transaction
All the manual difficulties in managing the library have been rectified by implementing
computerization.

NEED FOR COMPUTERIZATION

It is hard to keep all the records safely if it is in the paper format. When we use
this Digital Library System all the records are in the database. To reduce the manual
calculation also we use this system, because there is a possibility to from mistakes. The
calculation is very accurate.

SYSTEM DESIGN
INTRODUCTION
 System design is the process or art of defining the architecture, components,
modules, interface, and data for a system to satisfy specified requirements. One could see it as
the application of systems theory to product development. Design is the first phase in
development phase for any engineer’s product system. Design is the creative process. It deals
with the creating ability of the programmer. A good design is the key to effective system. The
term “design” is defined as “the process of applying various techniques and principles for the
purpose of defining a process or a system in sufficient details to permit is physical realization.

INPUT DESIGN
The user interface design is very important for any application. The interface design
describes how software communicated with in itself, to system that interpreted with it and with
humans who use it. The interface is a packing for computer software if the interface is easy to
learn simple to use. If the interface design is very good, the user will fall into an interactive
software application.
The input design is the process of converting the user-oriented inputs into the
computer-based format. Error entered by data entry operations can be controlled by input design.
The data is fed into the system using simple interactive forms. The forms have been supplied
with messages so that user can enter data without facing any difficulty. The data is validated
wherever it requires in the projects. This ensures that only the correct data have been
incorporated into the system. The goal for designing input data is to make data entry as easy,
logical and free from errors.

The objectives of input design are:

 To produce a cast effective method of input
 To make the input forms understandable to the user
 To ensure the validation of data
 To achieve the highest position level of accuracy

The various activities to be performed for the overall input processors are:
 Data recording at its source.
  Data transfer into input form.
 Data conversation to computer acceptable mode
 Data validation.
 Data flow control.
 Data correction if necessary.
In the proposed system, the user is provided with respective forms to input the required data.
OUTPUT DESIGN
The system output is the most important and direct source of information to the
user. So intelligible output design improves the relationship with user and helps in decision-
making. Outputs from the computer system are required primarily to communicate the result of
processing to users. They are also used to provide a permanent copy of those results for later
consultation.
A major form of output is a hard copy obtained from the printer. These printouts are
designed to include the exact requirement of the user. The outputs required by the end-user are
defined during the logical design stages.
Output specification output definition takes into account the type of output contents,
its frequency and its volume. The appropriate output media is chosen, the detail specification of
output documents are carried out. The nature of output required from the proposed system is
determined during the logical design stage itself. Physical design stage take the outline of the
output from the logical design and produce the output as specified during the logical design
phase. The necessary reports are generated which provide the complete information required by
the user.
The objectives of output design are:
 Design output to serve the indented purpose.
 Provide output on time
 Assume that output is where it is needed

Design outputs to fit the output screens in this project are:

 Creditor
  Debtor
 Booking

DATABASE DESIGN
Database provides the architecture for storing the data and has benefit as well. We can
create table. The overall objective in the development of database technology has been to treat
data as an organizational resource and as integrated whole. DBMS allows data to be protected
and organized separately from other resource. Database is an integrated collection of data. The
most on direct significant of data as seen by the programs and data as stored on the direct access
storage devices. This is the difference between logical and physical data.

The organization of data in a database aims to achieve three major objectives:

 Data integration
 Data integrity
 Data independent
The databases are implemented using a DBMS package. Each particular DBMS characteristics
and general techniques for database design.
SYSTEM DEVELOPMENT
 SYSTEM DEVELOPMENT

INTRODUCTION

In the system development phase in which the computer based information is

developed to confirm the requirement prepared in design phase. There are system development
strategies.

 The system development life cycle

 System analysis method
 Prototype method

THE SYSTEM DEVELOPMENT LIFE METHOD

The analyst and designer are carry out to develop implement an information system
includes the preliminary investigation, collection of data and determination of requirements,
design of a system, development of software, system testing and implementation of several of
these activities may vary in their degree of completion.

SYSTEM ANALYSIS METHOD

This is the method for modeling the components of the system using graphical
representation. In preparing this model the analyst emphasizes how it is accomplished. Thus the
flows are logical rather than physical aspects of the system.

PROTOTYPE METHOD

Prototype is an appropriate development strategy when predicting the user

requirement is not possible. A prototyping is the version of an information system having an
essential feature but not all the details of the user interfaces. The prototype may ultimately
become the actual working system
PROJECT DESCRIPTION
 PROJECT DESCRIPTION

LOGIN REGISTRATION

This project has two main parts like Librarian and Student. The librarian has the
permission to access all the modules of this project. Student has the permission to view all those
details which are entered by the Librarian.

LIBRARIAN MODULE

The Librarian has a username and password to access the system. After login, he has
to first add publication detail into the system and then enter all the details of book stock. In our
system, librarian can register all students with valid personal detail and generate username and
password for each student for login into system. Librarian can make entry of student who is the
members of our system. Librarian can issue books to the registered student and get details of
book return from them. He has rights to make a penalty for late return book.

 Add Publication
 Add Book
 Book Report
 Add Branch
 Add Student
 Student Report
 Issue Report
 Return Book
 Penalty
 Logout

ADD PUBLICATION
 Add Publication is used to add the publication name of the books. The librarian can
add, delete and edit the publication details. After adding publication details, it displays the grid
view. The grid view has two buttons such as edit and delete. After clicking the edit button,
relevant information is displayed on the respective controls. One can click the edit button to edit
the records. If you want to delete any row click the delete button to delete a row.

ADD BOOK

Add Book is used to add a new book in a library. In this module, the librarian can
add book name, details about the book, author of the book, publication, branch, price, quantity
and also the image of the book. On clicking the add book button, it will add the book in the
library.

BOOK REPORT

This report shows all the book details. In this module, the librarian can view the book
by selecting the branch and publication. After selecting the book details it displays on the grid
view. The grid view contains the details of the book and it contains the view button. On clicking
the view button, it displays the image and book details.

ADD BRANCH

Add Branch is used to add the new branch name. The librarian can add, delete and
edit the branch details. After adding branch details, it displays on the grid view. The grid view
has two buttons such as edit and delete. After clicking the edit button, relevant information is
displayed on the respective controls. One can click the edit button to edit the records. If you want
to delete any row, click the delete button to delete a row.

ADD STUDENT

This module deals with student information such as student name, branch, gender,
date of birth, mobile, address, city, pincode, photo, email, and password. The date of birth is
loaded into drop down list. On clicking add student button the student details will be added.

STUDENT REPORT
 This report shows all the details of the student. In this module, the librarian can view
the details of the student by selecting the branch and student name. After selecting the student
details, it displays on the grid view. The grid view contains the details of the student and it
contains the view button. On clicking the view button will display the student details.

ISSUE BOOK

This module is helps us to issue book such as, book name, author, and publication,
price of the book, total quantity, available quantity, rent quantity, book details, branch, student
details, and number of days remaining for returning the book. By selecting publication and book,
the book details will be viewed. On clicking the book issue button, the book will be issued.

ISSUE REPORT

This report shows all the details of the book, which are issued. In this module, the
librarian can view the details of the issued book by selecting the branch of the student and name
of the student. After selecting the book details, it displays on the grid view. The grid view
contains the details of the book, issue date and days.

RETURN BOOK

This module deals with the book issue such as book name, book image, author,
publication, branch of the student, price of the book, student name, days, issue date, penalty
status. By selecting student details and book, the book details and student details will be viewed.
On clicking the return book button, the book will be returned.

PENALTY

This module deals with the penalty such as book name, author, publication, branch,
price of the book, student name, days, issue date, penalty status, penalty amount, reason for
penalty. By selecting student for penalty and book, the book details and student details will be
viewed. By clicking the pay now button, the penalty amount will be initiated.

LOGOUT
 This module is used to log out. At that time of logout, the session will be cleared.

STUDENT MODULE

The Student is a registered member of library system. All students have unique
username and password to access his account. After login, student can access his account detail,
they can see the borrowed book reports and penalty reports.

 My Account
 My Report
 Book Report
 Logout

MY ACCOUNT

This module deals with the student account. The account details such as view
account, edit account, change password. On clicking the view account button, name of the
student, mobile number, address, city, pin code, and email will be displayed. The edit account
view contains the name of the student, mobile number, address, city, pin code, and email which
we want to edit. On clicking the update button the changes of the student account will be
updated. In change password view, the new password and the confirm password will be
displayed for changing our password.

MY REPORT

My report module contains the details such as borrow book list and return book list.
The borrow book list and return book list are viewed in the grid view. The borrow book grid
view contains the details of the book name, issue date and number of days to return the book.
The return book grid view contains the details such as book name, issue date, number days and
return date.

PENALTY REPORT
 This module deals with book name, price of the book, penalty amount for late renewal,
detail/reason for penalty, and date.

BOOK REPORT

This report shows all the book details that are picking-up in library. In this module, the
student can view their book by selecting the branch and publication. After selecting the book
details it displays on the grid view. The grid view contains the details of the book and it contains
the view button. On clicking the view button, it displays the image and book details.

LOGOUT

This module is used to log out. At that time of logout, the session will be cleared.

DATABASE MAINTENANCE

Database Name:LibrarySystem

Table Name: dbo.AdminMst

S.No Field Name Datatype

1 Aid Int
2 Name Nvarchar(256)
3 Username Nvarchar(256)
4 Password Nvarchar(256)
5 EntryDate Datetime

Table Name: dbo.BookMst

 S.No Field Name Datatype
1 BookID Int
2 BookName Nvarchar(256)
3 Author Nvarchar(256)
4 Detail Nvarchar(256)
5 Price Float
6 Publication Nvarchar(256)
7 Branch Nvarchar(256)
8 Quantities Int
9 Available Int
10 RentQnt Int
11 Image Nvarchar(1000)
12 EntryDate Datetime

Table Name: dbo.BranchMst

S.No Field Name Datatype

1 BranchId Int

2 BranchName Nvarchar(256)

Table Name: dbo.PenaltyMst

 S.No Field Name Datatype
1 PID Int
2 SID Int
3 BookName Nvarchar(256)
4 Price Numeric(18,0)
5 Penalty Numeric(18,0)
6 Detail Nvarchar(500)
7 EntryDate DateTime

Table Name: dbo.PublicationMst

S.No Field Name Datatype

1 PID Int
2 Publication Nvarchar(256)
3 EntryDate DateTime

Table Name: dbo.RentMst

S.No Field Name Datatype

1 RID Int
2 BookName Nvarchar(256)
3 SID Int
4 IssueDate DateTime
5 ReturnDate DateTime
6 Status Int

Table Name: dbo.StudentMst

S.No Field Name Datatype
1 SID Nvarchar(256)
2 StudentName Nvarchar(256)
3 BranchName Nvarchar(256)
4 Mobile Nvarchar(256)
5 Address Nvarchar(256)
6 City Nvarchar(256)
7 Pincode Nvarchar(256)
8 DOB DateTime
9 Gender Gender
10 Email Nvarchar(256)
11 Password Nvarchar(256)
12 Image Nvarchar(256)
13 EntryDate DateTime
FUTURE ENHANCEMENT

FUTURE ENHANCEMENT
 Digital Library System has complex requirements and must be flexible. Some of the
future enhancements that can be done to these systems are:

 Penalty can be paid by the student through online.

 Newspaper, journals, paper presentation can be uploaded/ downloaded.
 Sub-admin module can be added.
 Make an online chat facility for client and developer interaction.
 The user will able to search for books all over the cities and nearby
areas.
CONCLUSION
 CONCLUSION

The DIGITAL LIBRARY SYSTEM needs to be computerized to reduce time

complexity and to increase the efficiency. The proposed Digital Library System in this proposal
will be computerized library system developed to maintain in all the daily work of library.
Digital Library System is designed to store all the information about books and students. The
main focus of our project is to lessen human effort and encourage efficient record keeping. We
are making an offline version.
 BIBLIOGRAPHY

BIBLIOGRAPHY
FOR .NET INSTALLATION
  www.support.mircosoft.com

FOR SQL
 www.msdn.microsoft.com

FOR ASP.NET
 www.msdn.microsoft.com/net/quickstart/aspplus/default.com

 www.asp.net

 www.fmexpense.com/quickstart/aspplus/default.com

 www.asptoday.com

 www.aspfree.com

WEB REFERENCES

 www.asp.net/gridview

 www.google.co.in/library system

 www.erenthub.com

 www.makkan.com

 www.indianproperty.com

 www.ebay.com

 www.c-sharpcorner.com

BOOK REFERENCE
1. “Professional ASP.NET MVC 5(WROX)” by Jon Galloway and Brad Wilson
2. “ASP.NET:The Complete Reference” by Matthew Macdonald
3. “C# and ASP.NET Projects” by Shivprasad Koirala and Rajesh Pillai
4. Learn Professional Programming in .NET Using C#,Visual Basic, and
ASP.NET by Adalat Khan
5. Programming ASP.NET AJAX by Christian Wenz
ANNEXURE

ANNEXURE
DATA FLOW DIAGRAM (DFDs)

A data flow diagram is graphical tool used to describe and analyze movement of data
through a system. These are the central tool and the basis from which the other components are
developed. The transformation of data from input to output, through processed, may be
described logically and independently of physical components associated with the system. These
are known as the logical data flow diagrams. The physical data flow diagrams show the actual
implements and movement of data between people, departments and workstations. A full
description of a system actually consists of a set of data flow diagrams. Using two familiar
notations Yourdon, Gane and Sarson notation develops the data flow diagrams. Each component
in a DFD is labeled with a descriptive name. Process is further identified with a number that will
be used for identification purpose. The development of DFD’S is done in several levels. Each
process in lower level diagrams can be broken down into a more detailed DFD in the next level.
The lop-level diagram is often called context diagram. It consists a single process bit, which
plays vital role in studying the current system. The process in the context level diagram is
exploded into other process at the first level DFD.

The idea behind the explosion of a process into more process is that understanding at
one level of detail is exploded into greater detail at the next level. This is done until further
explosion is necessary and an adequate amount of detail is described for analyst to understand
the process.

Larry Constantine first developed the DFD as a way of expressing system requirements
in a graphical from, this lead to the modular design.

A DFD is also known as a “bubble Chart” has the purpose of clarifying system
requirements and identifying major transformations that will become programs in system design.
So it is the starting point of the design to the lowest level of detail. A DFD consists of a series of
bubbles joined by data flows in the system.

CONSTRUCTING A DFD
Several rules of thumb are used in drawing DFD’S:

1. Process should be named and numbered for an easy reference. Each name should be
representative of the process.
2. The direction of flow is from top to bottom and from left to right. Data traditionally flow
from source to the destination although they may flow back to the source. One way to
indicate this is to draw long flow line back to a source. An alternative way is to repeat the
source symbol as a destination. Since it is used more than once in the DFD it is marked with
a short diagonal.
3. When a process is exploded into lower level details, they are numbered.
4. The names of data stores and destinations are written in capital letters. Process and dataflow
names have the first letter of each work capitalized
A DFD typically shows the minimum contents of data store. Each data store should
contain all the data elements that flow in and out.
Questionnaires should contain all the data elements that flow in and out. Missing
interfaces redundancies and like is then accounted for often through interviews.

SAILENT FEATURES OF DFD’S

1. The DFD shows flow of data, not of control loops and decision are controlled considerations
do not appear on a DFD.
2. The DFD does not indicate the time factor involved in any process whether the dataflow take
place daily, weekly, monthly or yearly.
3. The sequence of events is not brought out on the DFD.

TYPES OF DATA FLOW DIAGRAMS

1. Current Physical
2. Current Logical
3. New Logical
4. New Physical

CURRENT PHYSICAL
 In Current Physical DFD process label include the name of people or their positions or
the names of computer systems that might provide some of the overall system-processing label
includes an identification of the technology used to process the data. Similarly data flows and
data stores are often labels with the names of the actual physical media on which data are stored
such as file folders, computer files, business forms or computer tapes.

CURRENT LOGICAL

The physical aspects at the system are removed as much as possible so that the current
system is reduced to its essence to the data and the processors that transform them regardless of
actual physical form.

NEW LOGICAL

This is exactly like a current logical model if the user were completely happy with he
user were completely happy with the functionality of the current system but had problems with
how it was implemented typically through the new logical model will differ from current logical
model while having additional functions, absolute function removal and inefficient flows
recognized.

NEW PHYSICAL

The new physical represents only the physical implementation of the new system.

RULES GOVERNING THE DFD’S

PROCESS
1) No process can have only outputs.
2) No process can have only inputs. If an object has only inputs than it must be a sink.
3) A process has a verb phrase label.
DATA STORE

1) Data cannot move directly from one data store to another data store, a process must move
data.
2) Data cannot move directly from an outside source to a data store, a process, which receives,
must move data from the source and place the data into data store
3) A data store has a noun phrase label.

SOURCE OR SINK

The origin and/or destination of data.

1) Data cannot move direly from a source to sink it must be moved by a process
2) A source and /or sink has a noun phrase land

DATA FLOW
1) A Data Flow has only one direction of flow between symbols. It may flow in both directions
between a process and a data store to show a read before an update. The later is usually
indicated however by two separate arrows since these happen at different type.
2) A join in DFD means that exactly the same data comes from any of two or more different
processes data store or sink to a common location.
3) A data flow cannot go directly back to the same process it leads. There must be atleast one
other process that handles the data flow produce some other data flow returns the original
data into the beginning process.
4) A Data flow to a data store means update (delete or change).
5) A data Flow from a data store means retrieve or use. A data flow has a noun phrase label
more than one data flow noun phrase can appear on a single arrow as long as all of the flows
on the same arrow move together as one package.
DATAFLOW DIAGRAM
 DATA FLOW DIAGRAM

LEVEL:0

Request

LIBRARIAN STUDENT

Response
LEVEL:1

LIBRARIAN

Login detail

Login Admin
System

Manage Branch
Branch

Manage Student
Student

Manage Books
Books

Reports Reports

Penalty Penalty
LEVEL:1.0.1

Librarian

Login Detail

Login Admin Master

Add Branch Branch Master

Modify Branch
Branch Master

LEVEL: 1.0.2

Librarian

Login Detail

Login Admin Master

Add Student Student Master

Modify Student
Student Master
LEVEL: 1.0.3

LIBRARIAN

Login detail

Login Admin Master

ADD Books Master

Books

Modify Book Master

Books

Add/delete
Quantities
Book Master

Issue
Book Rent Master

Return
Book Rent Master
LEVEL: 2

Student

Login detail

Login Student Master

System

My Student Master
Account

My
Report
Student Master

Penalty
Report
Student Master

Book
Report Student Master

Logout
SOURCE CODE
 SOURCE CODE:
ADD BOOK

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

public partial class Addbook : System.Web.UI.Page

{
DS_BRANCH.BRANCH_SELECTDataTable BDT = new
DS_BRANCH.BRANCH_SELECTDataTable();
DS_BRANCHTableAdapters.BRANCH_SELECTTableAdapter BAdapter = new
DS_BRANCHTableAdapters.BRANCH_SELECTTableAdapter();

DS_BOOK.BOOK_SELECTDataTable BookDT = new

DS_BOOK.BOOK_SELECTDataTable();
DS_BOOKTableAdapters.BOOK_SELECTTableAdapter BookAdapter = new
DS_BOOKTableAdapters.BOOK_SELECTTableAdapter();
DS_PUBLICATION.PUBLICATION_SELECTDataTable PubDT = new
DS_PUBLICATION.PUBLICATION_SELECTDataTable();
DS_PUBLICATIONTableAdapters.PUBLICATION_SELECTTableAdapter PubAdapter =
new DS_PUBLICATIONTableAdapters.PUBLICATION_SELECTTableAdapter();

protected void Page_Load(object sender, EventArgs e)

{
lblmsg.Text = "";
if (Page.IsPostBack == false)
{

BDT = BAdapter.SelectBranch();
//drpbranch.DataSource = BDT;
//drpbranch.DataTextField = "Branchname";
//drpbranch.DataValueField = "Branchid";
//drpbranch.DataBind();
//drpbranch.Items.Insert(0, "SELECT");

CheckBoxList1.DataSource = BDT;
CheckBoxList1.DataTextField = "Branchname";
CheckBoxList1.DataValueField = "branchid";
CheckBoxList1.DataBind();
 PubDT = PubAdapter.Select();
drppublication.DataSource = PubDT;
drppublication.DataTextField = "Publication";
drppublication.DataValueField = "pid";
drppublication.DataBind();
drppublication.Items.Insert(0, "SELECT");
}
}
protected void btnadd_Click(object sender, EventArgs e)
{
if (FileUpload1.HasFile)
{

FileUpload1.SaveAs(Server.MapPath("~/Book/") + FileUpload1.FileName);

int a = 0;
for (int i = 0; i < CheckBoxList1.Items.Count; i++)
{
if (CheckBoxList1.Items[i].Selected == true)
{
BookAdapter.Insert(txtbname.Text, txtauthor.Text, txtdetail.Text,
Convert.ToDouble(txtprice.Text), drppublication.SelectedItem.Text,
CheckBoxList1.Items[i].Text, Convert.ToInt32(txtqnt.Text), Convert.ToInt32(txtqnt.Text), 0,
"~/Book/" + FileUpload1.FileName.ToString());
a = 1;
}

}
if (a == 0)
{
lblmsg.Text = "Please, Select branch";
}
else
{
lblmsg.Text = "Book Added";
txtauthor.Text = "";
txtbname.Text = "";
txtdetail.Text = "";
txtprice.Text = "";
txtqnt.Text = "";
// drpbranch.SelectedIndex = 0;
drppublication.SelectedIndex = 0;
txtbname.Focus();
}
}
else
{
 lblmsg.Text = "Please, Select Book Photo";
}
}
}

ISSUE BOOK

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

public partial class BookIssue : System.Web.UI.Page

{
DS_BRANCH.BRANCH_SELECTDataTable BDT = new
DS_BRANCH.BRANCH_SELECTDataTable();
DS_BRANCHTableAdapters.BRANCH_SELECTTableAdapter BAdapter = new
DS_BRANCHTableAdapters.BRANCH_SELECTTableAdapter();
DS_PUBLICATION.PUBLICATION_SELECTDataTable PubDT = new
DS_PUBLICATION.PUBLICATION_SELECTDataTable();
DS_PUBLICATIONTableAdapters.PUBLICATION_SELECTTableAdapter PubAdapter =
new DS_PUBLICATIONTableAdapters.PUBLICATION_SELECTTableAdapter();
DS_BOOK.BOOK_SELECTDataTable BookDT = new
DS_BOOK.BOOK_SELECTDataTable();
DS_BOOKTableAdapters.BOOK_SELECTTableAdapter BookAdapter = new
DS_BOOKTableAdapters.BOOK_SELECTTableAdapter();
DS_STUDENT.STUDENT_SELECTDataTable SDT = new
DS_STUDENT.STUDENT_SELECTDataTable();
DS_STUDENTTableAdapters.STUDENT_SELECTTableAdapter SAdapter = new
DS_STUDENTTableAdapters.STUDENT_SELECTTableAdapter();
DS_RENT.RENT_SELECTDataTable RDT = new DS_RENT.RENT_SELECTDataTable();
DS_RENTTableAdapters.RENT_SELECTTableAdapter RAdapter = new
DS_RENTTableAdapters.RENT_SELECTTableAdapter();

protected void Page_Load(object sender, EventArgs e)

{
lblissue.Text = "";
lblmsg.Text = "";
if (Page.IsPostBack == false)
{
BDT = BAdapter.SelectBranch();
drpbranch.DataSource = BDT;
drpbranch.DataTextField = "Branchname";
drpbranch.DataValueField = "Branchid";
 drpbranch.DataBind();
drpbranch.Items.Insert(0, "SELECT");

PubDT = PubAdapter.Select();
drppublication.DataSource = PubDT;
drppublication.DataTextField = "Publication";
drppublication.DataValueField = "pid";
drppublication.DataBind();
drppublication.Items.Insert(0, "SELECT");
drpbook.Items.Insert(0, "SELECT");
}
}
protected void drppublication_SelectedIndexChanged(object sender, EventArgs e)
{
BookDT = BookAdapter.Select_By_Publication(drppublication.SelectedItem.Text);
drpbook.DataSource = BookDT;
drpbook.DataTextField = "Bookname";
drpbook.DataValueField = "Bookid";
drpbook.DataBind();
drpbook.Items.Insert(0, "SELECT");
}
protected void Button12_Click(object sender, EventArgs e)
{
if (drppublication.SelectedIndex == 0)
{

lblmsg.Text = "Select Publication";

lblmsg.ForeColor = System.Drawing.Color.Red; MultiView1.ActiveViewIndex = -1;
}
else if (drpbook.SelectedIndex == 0)
{
lblmsg.Text = "Select Book";
lblmsg.ForeColor = System.Drawing.Color.Red; MultiView1.ActiveViewIndex = -1;
}
else
{
MultiView1.ActiveViewIndex = 0;
BookDT = BookAdapter.Select_By_BNAM(drpbook.SelectedItem.Text);
ViewState["BBID"] = BookDT.Rows[0]["BookID"].ToString();
lblbname.Text = BookDT.Rows[0]["Bookname"].ToString();
lblauthor.Text = BookDT.Rows[0]["author"].ToString();
lblbran.Text = BookDT.Rows[0]["branch"].ToString();
lblpub.Text = BookDT.Rows[0]["publication"].ToString();
lblprice.Text = BookDT.Rows[0]["price"].ToString();
lblqnt.Text = BookDT.Rows[0]["Quantities"].ToString();
lblaqnt.Text = BookDT.Rows[0]["availableqnt"].ToString();
 lblrqnt.Text = BookDT.Rows[0]["rentqnt"].ToString();
lbldetail.Text = BookDT.Rows[0]["Detail"].ToString();
Image2.ImageUrl = BookDT.Rows[0]["Image"].ToString();

drpstudent.Items.Clear();
drpstudent.Items.Insert(0, "SELECT");
}
}
protected void btnissue_Click(object sender, EventArgs e)
{
try
{
if (TextBox1.Text == "")
{
lblissue.Text = "Enter Days";
}
else
{
if (Convert.ToInt32(lblaqnt.Text) == 0)
{
lblissue.Text = "Book Stock Empty";
}
else
{
RDT = RAdapter.Select_SID_BName_Status(lblbname.Text,
Convert.ToInt32(drpstudent.SelectedValue), 0);

if (RDT.Rows.Count != 0)
{
lblissue.Text = "Student can't get copies of same book !!";
}
else
{

RDT =
RAdapter.Select_by_Status_and_SID(Convert.ToInt32(drpstudent.SelectedValue), 0);
if (RDT.Rows.Count == 3)
{
lblissue.Text = "A student has maximum 3 books";
}
else
{
RAdapter.Insert(lblbname.Text, Convert.ToInt32(drpstudent.SelectedValue),
Convert.ToInt32(TextBox1.Text));
BookAdapter.BOOK_ISSUE_TO_STUDENT(Convert.ToInt32(ViewState["BBID"].ToString())
);
lblissue.Text = "Book Issued to " + drpstudent.SelectedItem.Text;

BookDT =
BookAdapter.Select_BY_BID(Convert.ToInt32(ViewState["BBID"]));
ViewState["BBID"] = BookDT.Rows[0]["BookID"].ToString();
lblbname.Text = BookDT.Rows[0]["Bookname"].ToString();
lblauthor.Text = BookDT.Rows[0]["author"].ToString();
lblbran.Text = BookDT.Rows[0]["branch"].ToString();
lblpub.Text = BookDT.Rows[0]["publication"].ToString();
lblprice.Text = BookDT.Rows[0]["price"].ToString();
lblqnt.Text = BookDT.Rows[0]["Quantities"].ToString();
lblaqnt.Text = BookDT.Rows[0]["availableqnt"].ToString();
lblrqnt.Text = BookDT.Rows[0]["rentqnt"].ToString();
lbldetail.Text = BookDT.Rows[0]["Detail"].ToString();
Image2.ImageUrl = BookDT.Rows[0]["Image"].ToString();

TextBox1.Text = "";
drpstudent.Items.Clear();
drpstudent.Items.Insert(0, "SELECT");
BDT = BAdapter.SelectBranch();
drpbranch.DataSource = BDT;
drpbranch.DataTextField = "Branchname";
drpbranch.DataValueField = "Branchid";
drpbranch.DataBind();
drpbranch.Items.Insert(0, "SELECT");
}
}
}
}
}
catch {
lblissue.Text = "Sorry !!! Error !!!";
}
}
protected void drpbranch_SelectedIndexChanged(object sender, EventArgs e)
{
SDT = SAdapter.Select_By_Branch(drpbranch.SelectedItem.Text);
drpstudent.DataSource = SDT;
drpstudent.DataTextField = "Studentname";
drpstudent.DataValueField = "sid";
drpstudent.DataBind();
drpstudent.Items.Insert(0, "SELECT");
}
}

PENALTY

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

public partial class Panalty : System.Web.UI.Page

{
DS_RENT.RENT_SELECTDataTable RDT = new DS_RENT.RENT_SELECTDataTable();
DS_RENTTableAdapters.RENT_SELECTTableAdapter RAdapter = new
DS_RENTTableAdapters.RENT_SELECTTableAdapter();

DS_PANALTY.PENALTY_SELECTDataTable PDT = new

DS_PANALTY.PENALTY_SELECTDataTable();
DS_PANALTYTableAdapters.PENALTY_SELECTTableAdapter PAdapter = new
DS_PANALTYTableAdapters.PENALTY_SELECTTableAdapter();

DS_STUDENT.STUDENT_SELECTDataTable SDT = new

DS_STUDENT.STUDENT_SELECTDataTable();
DS_STUDENTTableAdapters.STUDENT_SELECTTableAdapter SAdapter = new
DS_STUDENTTableAdapters.STUDENT_SELECTTableAdapter();
DS_BOOK.BOOK_SELECTDataTable BookDT = new
DS_BOOK.BOOK_SELECTDataTable();
DS_BOOKTableAdapters.BOOK_SELECTTableAdapter BookAdapter = new
DS_BOOKTableAdapters.BOOK_SELECTTableAdapter();

protected void Page_Load(object sender, EventArgs e)

{
lblmsg.Text = "";
lblpay.Text = "";
if (Page.IsPostBack == false)
{
SDT = SAdapter.Select_Student_for_panalty();
drpstudent.DataSource = SDT;
drpstudent.DataTextField = "StudentName";
drpstudent.DataValueField = "sid";
drpstudent.DataBind();
drpstudent.Items.Insert(0, "SELECT");
}
}
protected void Button12_Click(object sender, EventArgs e)
 {
if (drpstudent.SelectedIndex == 0)
{

lblmsg.Text = "Select Student";

lblmsg.ForeColor = System.Drawing.Color.Red; MultiView1.ActiveViewIndex = -1;
}
else if (drpbook.SelectedIndex == 0)
{
lblmsg.Text = "Select Book";
lblmsg.ForeColor = System.Drawing.Color.Red; MultiView1.ActiveViewIndex = -1;
}
else
{
MultiView1.ActiveViewIndex = 0;
BookDT = BookAdapter.Select_By_BNAM(drpbook.SelectedItem.Text);
ViewState["BBID"] = BookDT.Rows[0]["BookID"].ToString();
lblbname.Text = BookDT.Rows[0]["Bookname"].ToString();
lblauthor.Text = BookDT.Rows[0]["author"].ToString();
lblbran.Text = BookDT.Rows[0]["branch"].ToString();
lblpub.Text = BookDT.Rows[0]["publication"].ToString();
lblprice.Text = BookDT.Rows[0]["price"].ToString();

Image2.ImageUrl = BookDT.Rows[0]["Image"].ToString();

SDT = SAdapter.Select_By_SID(Convert.ToInt32(drpstudent.SelectedValue));
lblstudent.Text = SDT.Rows[0]["Studentname"].ToString();

RDT = RAdapter.Select_SID_BName_Status(drpbook.SelectedItem.Text,
Convert.ToInt32(drpstudent.SelectedValue), 0);
lbldays.Text = RDT.Rows[0]["Days"].ToString();
lblidate.Text = RDT.Rows[0]["IssueDate"].ToString();
ViewState["RRID"] = RDT.Rows[0]["rid"].ToString();

int iday = Convert.ToDateTime(RDT.Rows[0]["IssueDate"].ToString()).Day;

int rday = System.DateTime.Now.Day;

int pday = rday - iday;

if (pday > Convert.ToInt32(lbldays.Text))
{
lblpanalty.Text = "Yes";
}
else
{
lblpanalty.Text = "NO";
}
 }
}
protected void drpstudent_SelectedIndexChanged(object sender, EventArgs e)
{
PDT = PAdapter.Select_by_SID_Panalty_0(Convert.ToInt32(drpstudent.SelectedValue));
drpbook.DataSource = PDT;
drpbook.DataTextField = "bookname";
drpbook.DataValueField = "pid";
drpbook.DataBind();
drpbook.Items.Insert(0, "SELECT");

}
protected void btnpaypanalty_Click(object sender, EventArgs e)
{
if (txtpanalty.Text == "")
{
lblpay.Text = "Enter amount";
}
else if (txtdetail.Text == "")
{
lblpay.Text = "Enter detail";
}
else
{
PAdapter.PENALTY_PAY_NOW(Convert.ToDouble(txtpanalty.Text), txtdetail.Text,
Convert.ToInt32(drpbook.SelectedValue));
lblmsg.Text = "Amount paid successfully";
RAdapter.RENT_SELECT_RETURN(Convert.ToInt32(ViewState["RRID"].ToString()),
1, Convert.ToInt32(ViewState["BBID"].ToString()));
txtdetail.Text = "";
txtpanalty.Text = "";
MultiView1.ActiveViewIndex = -1;
SDT = SAdapter.Select_Student_for_panalty();
drpstudent.DataSource = SDT;
drpstudent.DataTextField = "StudentName";
drpstudent.DataValueField = "sid";
drpstudent.DataBind();
drpstudent.Items.Insert(0, "SELECT");
drpbook.Items.Clear();
drpbook.Items.Insert(0, "SELECT");
}
}
 SCREEN DESIGN

LIBRARIAN LOGIN
ADD BOOK

ADD STUDENT
ISSUE BOOK

BOOK REPORT
RETURN BOOK

PENALTY
STUDENT LOGIN
MY ACCOUNT
BOOK REPORT

STUDENT PENALTY

REPORTS
 Database Name:LibrarySystem

Table Name: dbo.AdminMst

S.No Field Name Datatype

1 Aid Int
2 Name Nvarchar(256)
3 Username Nvarchar(256)
4 Password Nvarchar(256)
5 EntryDate Datetime

Table Name: dbo.BookMst

S.No Field Name Datatype

1 BookID Int
2 BookName Nvarchar(256)
3 Author Nvarchar(256)
4 Detail Nvarchar(256)
5 Price Float
6 Publication Nvarchar(256)
7 Branch Nvarchar(256)
8 Quantities Int
9 Available Int
10 RentQnt Int
11 Image Nvarchar(1000)
12 EntryDate Datetime

Table Name: dbo.BranchMst

S.No Field Name Datatype

 1 BranchId Int

2 BranchName Nvarchar(256)

Table Name: dbo.PenaltyMst

S.No Field Name Datatype

1 PID Int
2 SID Int
3 BookName Nvarchar(256)
4 Price Numeric(18,0)
5 Penalty Numeric(18,0)
6 Detail Nvarchar(500)
7 EntryDate DateTime

Table Name: dbo.PublicationMst

S.No Field Name Datatype

1 PID Int
2 Publication Nvarchar(256)
3 EntryDate DateTime

Table Name: dbo.RentMst

 S.No Field Name Datatype
1 RID Int
2 BookName Nvarchar(256)
3 SID Int
4 IssueDate DateTime
5 ReturnDate DateTime
6 Status Int

Table Name: dbo.StudentMst

S.No Field Name Datatype

1 SID Nvarchar(256)
2 StudentName Nvarchar(256)
3 BranchName Nvarchar(256)
4 Mobile Nvarchar(256)
5 Address Nvarchar(256)
6 City Nvarchar(256)
7 Pincode Nvarchar(256)
8 DOB DateTime
9 Gender Gender
10 Email Nvarchar(256)
11 Password Nvarchar(256)
12 Image Nvarchar(256)
13 EntryDate DateTime