lms

Library Management System

CONTENTS

CHAPTERS PAGES1. INTRODUCTION

1.1. INTRODUCTION

1.2 OBJECTIVE OF THE PROJECT

1.3 PERSONAL OBJECTIVES

2. METHODOLOGY 2.1 WHAT IS A METHODOLOGY

2.2 SELECTION OF A METHODOLOGY

2.3 PHASES OF SSADM

3. DESCRIPTION ABOUT THE ORGANIZATION 4. SOFTWARE PROCESS MODEL 5. REQUIREMENT ANALYSIS

4.1 PRELIMINARY SURVEY

4.2 REQUIREMENT SPECIFICATIONS

4.3 PERFORMANCE CRITERIA

VOLUME OF TRANSACTION (DATA HANDLING)

CONTROL ASPECTS

TIMELINESS

ARCHIVAL

4.4 SYSTEM HARDWARE & SOFTWARE REQUIRED

6. FEASIBILITY STUDY 5.1 TECHNICAL FEASIBILITY

5.2 ECONOMICAL FEASIBILITY

5.3 OPERATIONAL FEASIBILITY

7. SYSTEM ANALYSIS 6.1 SYSTEM ANALYSIS

6.2 STRUCTURED ANALYSIS

8. SYSTEM DESIGN 7.1 INTRODUCTION


7.2 INPUT DESIGN

7.3 OUTPUT DESIGN

7.4 FORM DESIGN

7.5 DATABASE DESIGN

9. SYSTEM TESTING & IMPLEMENTATION 8. 1 INTRODUCTION.

8. 2 CODING

8.3. SYSTEM TESTING & IMPLEMENTATION

10. USER MANUAL11. CONCLUSION 12. ANNEXURE 55 – 5614. BIBLIOGRAPHY 60 – 61


Chapter 1

Introduction

Objective of the Project

Personal Objective


1.1 IntroductionThe Library Management System is designed & developed for a receipt and issuance of

books in the library along with the student’s details. The books received in the library

are entered in Books Entry form and the new student is entered in the student entry

form. When the student wants to get the desired book the same is issued on the

availability basis to the student. The issuance and due date for the returning of the book

is also entered into the Book Issue form under third menu Book Issue. The student has

to pay the fine if any on the basis of no. of days delayed deposit of the book in the

library.

1.2 Objectives:The objective of the project is to deliver a working system which solves the problem

regarding library system. Here we are going to design a standalone Library

Management System which provides the following facilities:

Create and maintain category, course etc

Entered details about book, librarian, student etc.

Issue book.

Find book outstanding.

Find book over due.

1.3 Personal objectives Gaining experience in project management a software life cycle form start to

finish.

To apply knowledge acquired over the duration of the degree course.

To gain reward from the developing a system of my invention and creation.


Chapter 2

WHAT IS A METHODOLOGY SELECTION OF A METHODOLOGY PHASES OF SSADM


2.1 What is a Methodology?

A method is an integrated set of procedures and techniques which, when applied in a

certain sequence, result in the specification or generation of an information system.

2.1 Selection of a MethodologyMany methodologies are available for systems development, but it is not a simple task

to choose the best of the ‘lot’ for a project. A methodology which worked well for one

organization may not necessarily work for some other organization. This is so, because,

methodologies are strong in some aspects and weak in others. For example, Soft

System Methodology (SSM) has more relevance to a project where the problem

situation is ill structured and there is no clear vision of the problem area.SSM covers

mainly the analysis stage of the systems life cycle, and may be used with some other

methodology to complete the design and implementation stage, for example Structured

System Analysis Design Methodology (SSADM) or Information Engineering (IE).

The organization which requested the development of this project, has well known, clear

problem areas to be analyzed. Therefore, SSM is eliminated in the very outset. The

choice has to be made between SSADM and IE. The methodology has to be one which

has the ability to depict all the design information in a clear and consistent way. It also

needs to have facilities which could deal with graphical user interfaces, because these

are important part of my system. The methodology has to suit the programming

language I am using which is ASP.net.It also needs the ability to refine design

information without losing any information through the various models and stages. It has

to be easy to make amendments as I come up with new ideas for the system. The

methodology also needs to cater equally for technical documents and graphical


representations, and most importantly, it has to be easy to understand. Having analyzed

the principles, advantages and disadvantages of methodologies available, SSADM is

selected for this project.

The reasons for this decision are:

The methodology is more structured, which means it is easy to follow from one

stage to another.

Following the methodological form of SSADM, the goals and objectives of the

system can be easily determined.

SSADM suggests the use of three major conceptual tools for constructing the

system models: data flow diagrams (DFDs), a data dictionary (DD) and

structured English, which are the most appropriate tools for this project as the

problem areas of the organization are well defined and clear.

SSADM allows the use various techniques which check the integrity of each

other.

SSADM suggests the specification of the requirements of the system by having

continuous user involvement throughout the project.

SSADM is not only a very popular methodology but also proved its success in

many information systems analysis and design cases.

2.3 Phases of SSADM

The six phase of the methodology have been classified into two areas, three phases of

system analysis and three phases of system design. Sometimes systems analysts not

following a methodology like SSADM might find it difficult to decide on the level of detail

being sought when reviewing the current system. This can cause ‘paralysis by analysis’,

where vast amount of information can be gathered but no conclusion ever reached. By

separating the system analysis activities from the system design activities, SSADM

makes it easier to judge the proportion of time spent on analysis.


Stage 1 – Feasibility study and analysis of the system.

Stage 2 – Specification of the required system.

Stage 3 – User selection of the service levels, including technical options.

Stage 4 – Detailed data design

Stage 5 – Detailed Procedure design

Stage 6 – Physical design control

The above mentioned six phases are implemented in various ways, so as to satisfy both

the requirements and the complexity of the realization process of the requirements.

According to these ways we have various process models. The next chapter deals with

the selection of the process model for this project.


Chapter 3


DESCRIPTION ABOUT THE ORGANIZATION

The University Law College library, with a collection of 7,752 Text Books, 830 Journals

and periodicals and 916 reference Books, is a prime source for legal research for both

the faculty as well as the students. The library with adequate reading room facility offers

a fully integrated, dynamic environment for conducting legal and law-related research.

Housed in the southern corner of the RCC building of the College, the library provides

an optimum study environment wherein students can conduct their research and study

in solitude and comfort. A student can borrow two books at a time as per Borrower’s

Card system. In addition to the College Library, the students are also entitled to use the

university library which is known as K.K.H. Library, and the library of Post Graduate

Department of Law as per terms and conditions as laid down by the University from time

to time.


Chapter 4


SOFTWARE PROCESS MODEL

A software process model is a development strategy we incorporate to describe how a

set of activities (the six phases of SSADM) must be performed and in which order to get

the desired output. We already have a few process models defined and described.

These are:

1. Code and Fix Model

2. Waterfall Model

3. Evolutionary Model

4. Transformation Model

5. Spiral Model

The Code and Fix Model can actually be considered no model at all as there is nothing

rigid and the developer has to follow his inspirations.

The Evolutionary model is increment driven and a kind of trial and error method.

The Transformation model can be called specification driven, as the development

process occurs through iterative refinement of formal specifications.

Spiral model is a met model that may be called risk driven.

Although, the Waterfall model has its share of disadvantages like being not flexible and

monolithic, yet for a small and quite simple project like this, the model’s rigid and

documentation driven approach is best suited. Also, since there is already a manual

system available, the requirements are clear. For such a situation, the Waterfall model

is the best choice.


Chapter 5

PRELIMINARY SURVEY REQUIREMENT SPECIFICATIONS PERFORMANCE CRITERIA

VOLUME OF TRANSACTION (DATA HANDLING) CONTROL ASPECTS TIMELINESS ARCHIVAL

SYSTEM HARDWARE & SOFTWARE REQUIRED


4.1 Preliminary SurveyThe problem forwarded by the client is actually to upgrade their already existing Library

Management System. The client already had a set system which was computerized.

This computerized system was although efficient, but very time consuming. Also, the

different modules were not fully integrated and needed an absolute understanding of the

whole system to give the desired results. The main problems found out were

bottlenecks at the user end because of slow data flow rate in that system. So, a

preliminary survey was done to check whether any simple modification could actually

stimulate the system.

The only problem is the development of software which is both feasible and efficient.

This proves to be a good scope to implement my knowledge and develop a worthy final

semester project.

4.2 Requirement Specifications After the preliminary survey and listening to the client’s requirements following

requirements were listed:

Create and maintain different accounts like saving account, current

account etc.

Maintaining deposit and withdraw of each account securely.

Balance Enquiry

Proper help to be provided as and when requested by the user.

Enables the user to successfully log in to the system.

Enables to add new user, branch, create account, modify account, deposit

and withdrawal amount, etc to the database.

Enables users to check transaction status.

Make a provision of tracking of each user who is log in to the system.

Enables user to log out of the system.

4.3 Performance CriteriaAfter the initial investigation of the present system and the client’s requirements some

performance criteria were deduced.


Chapter 7

SYSTEM ANALYSIS

STRUCTURED ANALYSIS


6.1 System AnalysisSystem analysis is a detailed study of the various operations performed by a system

and their relationships within and outside of the system. This involves gathering

information and using structured tools for analysis. One aspect of analysis is defining

the boundaries of the system and whether or not a candidate system should consider

other related systems. During analysis, data are collected on the available files, decision

points and transactions handled by the present system. Once analysis is completed, the

analyst has a firm understanding of what is to be done. The next step is to decide how

the problem might be solved.

6.2 STRUCTURED ANALYSISStructured analysis is a set of techniques and graphical tools that allow the analyst to

develop a new kind of system specifications that are easily understandable to the user.

The basic tools for structured analysis are:-

a) Context diagram

b) Data flow diagram

c) Data dictionary

d) Decision tree

e) Decision table

CONTEXT DIAGRAM:-The context diagram is the starting point of this analysis and is

used to show the highest level in the model of the system. They are used to pictorially

represent the scope as well as the boundaries of the system.

DATA FLOW DIAGRAM: - A DFD has the purpose of clarifying the system

requirements and identifying major transformations that will be become programs in

system design. So it is the starting point of the design phase that functionally

decomposes the requirements specifications down to the lowest level of detail.

Moreover, DFD is a graphical representation of the system that shows data flows to,

from and within the system, processing functions that change the data in the same

manner and the storage of this data. They are constructed using the context diagram as

a top level guide. Data can be organized in several ways:

1. stored in data repositories


2. flow in data flows

In the DFD, there are four symbols

1. A square defines a source or destination of system data.

2. An arrow identifies data flow- data in motion. It is a pipeline through

which information flows.

3. A circle represents a process that transforms incoming data flows

into outgoing data flows.

4. An open rectangle is a data store- data at rest, or a temporary

repository of data. A DFD describes what data flow rather than how

they are processed, so it does not depend on hardware, software, data

structure or file organization.

Following are the basic elements of a DFD which are used in the DFD of the project:

Library Management

System0

Student Book info

Request book

Issue book

Book Details

Context Diagram or O level DFD


StudentMembershipManagement

1

Member

Book IssueManagement

2

Request for Membership

Send Membership Details

Request for non continuing

Send No Dues

Member Details

StudentRequest for book issue

Book issue DetailsReturn book/Penalty Rpt

Reminder for book returnWith penalty

BookDetails and status of Book

PenaltyPenalty Amount

ReportManagement

3

Issue Details

Management

Req for report

Send Report

1st level DFD for Library Management System


Chapter 8

INTRODUCTION INPUT DESIGN OUTPUT DESIGN FORM DESIGN DATABASE DESIGN


SYSTEM DESIGN7.1 INTRODUCTIONSystem design deals with the detailed concentration on the technical and the other

specifications that will make the new system operational. A major step in the design is

the preparation of input and the design of output reports in a form acceptable to the

user. System design provides the necessary understanding and the procedural details

needed to implement the system as recommended by the feasibility study.

System design goes through the following phases:-

1) Logical design phase

2) Physical design phase, which consists of the following

7.2 INPUT DESIGNThe goal of designing input data is to make data entry as easy, logical, and free from

errors as possible, in entering data, operators need to know the following:

1) The allocated space for each field.

2) Field sequence, which must match that in the source document

3) The format in which data fields are entered

7.3 OUTPUT DESIGNComputer output is the most important and direct source of information to the user.

Efficient, intelligible output design should improve the system’s relationships with the

user and help in decision making. A major form of output is a hard copy from the printer.

Printouts should be designed around the output requirements of the user.

7.4 FORM DESIGNForm is the physical carrier of data-of information. People read from forms, write on

forms, and spend billions of hours handling forms and filing forms. The data the forms

carry come from people, and the informational output of the system goes to people. So,

the form is a tool with a message. With this in mind, it is hard to imagine a business

operating without using forms.


Requirements of Forms Design:-

Forms design follows analyzing forms, evaluating present documents, and creating new

and improved forms. Since the purpose of a form is to communicate effectively through

forms design, there are several major requirements:-

1) Identification and wording: - The form title must clearly identify its purpose. Columns

and rows should label to avoid confusion.

2) Maximum readability and use:-The form should be easy to use and fill out. It should

be legible, intelligible, and uncomplicated. Ample writing space must provide for

inserting data.

3) Physical factors:-The form’s composition, color, layout and paper stock should lead

them to easy reading. Pages should be numbered when multiple reports are being

generated for the user.

7.5 DATABASE DESIGN

Database systems are designed to manage large amount of information. The

management includes both the definition of the structures for the storage of information

and provision for mechanism for the manipulation of information.

In addition it provides safety to the data stored in the database.

In database design, several specific objectives are considered:-

1) Controlled redundancy: - Redundant data occupies space and, therefore, is wasteful.

If versions of the same data are in different phases of updating, the system often gives

conflicting information. A unique aspect of database design is storing data only once,

which controls redundancy and improves system performance.

2) Data independence: - An important data base objective is changing hardware and

storage procedures or adding new data without having to rewrite application programs.

The database should be “tunable”to improve performance without rewriting programs.

3) More information at low cost: - Using, storing, and modifying data at low cost are

important. Although hardware prices are falling, software and programming costs are on


the rise. This means that programming and software enhancements should be kept

simple and easy to update.

4) Accuracy and integrity: - The accuracy of a database ensures that data quality and

content remain constant. Integrity controls detect data inaccuracies where they occur.

5) Recovery from failure: - With multi-user access to a database, the system must

recover quickly after it is down with no loss of transaction.


Books

Book NO

ISBN

AUTHOR

Book TITLE

CATEGORYINDEX

Price

Qty Year of Published

Date_ Arrived

Barrowed

Address

Data modify

Student

St_IdName

City

Date Add

State

Pin

Phone

Course

Status of Book

Book No

Issue Date

Re_date

Delayed

Fine

Delayed

ER Diagram for Library System

Library

Contains

Issued_to


Chapter 9

Introduction. Coding System testing and implementation


8.1 INTRODUCTIONA system should be thoroughly tested before implementation. The purpose of system

testing is to identify and correct errors in the candidate system. In system testing,

performance and acceptance standards are developed. Substandard performance or

service interruptions that result in system failure are checked during the test.

8.2 CODINGSample coding: -ADD BOOK FORMS

Imports System.Data.SqlClientPublic Class FrmAddBooks Dim conn As New SqlConnection(str) Private Sub CmdCancel_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles CmdCancel.Click Me.Close() End Sub

Private Sub FrmAddBooks_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load Category() txtbookNo.Text = BookNo() End Sub Public Function Category() conn.Close() Dim strSql As String strSql = "SELECT Category_Name FROM Category" Dim cmdSql As New SqlCommand(strSql, conn) Dim drTable As SqlDataReader conn.Open() drTable = cmdSql.ExecuteReader() While (drTable.Read()) cbcategory.Items.Add(drTable.GetString(0)) End While conn.Close() Return 0 End Function

Private Sub CmdSave_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles CmdSave.Click


Dim sql As String = "insert into BOOKS (BOOK_NO,ISBN,AUTHOR,BOOK_TITLE,CATEGORYINDEX,YEARPUBLISHED,DATEARRIVED,PRICE,QTY,BARROWED,ADDEDBY,DATEADD,MODIFY_BY,DATEMODIFY) Values('" & txtbookNo.Text & "','" & UCase(txtISBN.Text) & "','" & UCase(TxtAuthor.Text) & "','" & UCase(TxtBooktitle.Text) & "','" & UCase(cbcategory.Text) & "','" & UCase(TxtPublished.Text) & "','" & UCase(dtparrived.Text) & "','" & UCase(txtprice.Text) & "','" & UCase(txtqty.Text) & "','', '" & UCase(Txtuserid.Text) & "','" & Now.Date & "','','')" If conn.State = ConnectionState.Closed Then conn.Open() End If If txtbookNo.Text = "" Or txtISBN.Text = "" Or TxtAuthor.Text = "" Or TxtBooktitle.Text = "" Or cbcategory.Text = "" Or TxtPublished.Text = "" Or txtprice.Text = "" Or txtqty.Text = "" Then MsgBox("Please Enter All the Filds", MsgBoxStyle.Information) Exit Sub End If Dim com As New SqlCommand com = New SqlCommand(sql, conn) com.ExecuteNonQuery() MsgBox("Book Details added Successfully", MsgBoxStyle.Information) Call clear() txtbookNo.Text = BookNo() End Sub

Function clear() txtbookNo.Text = "" txtISBN.Text = "" TxtAuthor.Text = "" TxtBooktitle.Text = "" TxtPublished.Text = "" txtprice.Text = "" txtqty.Text = "" Return 0 End Function

Public Function BookNo() As String conn.Close() Dim strSql As String strSql = "SELECT count(*),max(BOOK_NO) FROM BOOKS" Dim cmdSql As New SqlCommand(strSql, conn) Dim drTable As SqlDataReader conn.Open() drTable = cmdSql.ExecuteReader() drTable.Read() If drTable.GetInt32(0) = 0 Then BookNo = (10000) Else BookNo = drTable.GetString(1) + 1 End If conn.Close() End Function

Private Sub txtbookNo_LostFocus(ByVal sender As Object, ByVal e As System.EventArgs) Handles txtbookNo.LostFocus


Dim querystring As String = "select ISBN,AUTHOR,BOOK_TITLE,CATEGORYINDEX,YEARPUBLISHED,DATEARRIVED,PRICE,QTY,BARROWED from BOOKS WHERE BOOK_NO='" & txtbookNo.Text & "'" Dim cmd As New SqlCommand(querystring, conn) Dim dr As SqlDataReader conn.Close() conn.Open() dr = cmd.ExecuteReader() If dr.Read <> 0 Then txtISBN.Text = dr.GetValue(0).ToString TxtAuthor.Text = dr.GetValue(1).ToString TxtBooktitle.Text = dr.GetValue(2).ToString cbcategory.Text = dr.GetValue(3).ToString TxtPublished.Text = dr.GetValue(4).ToString ' dtparrived.Text = CDate(dr.GetValue(5).ToString) txtprice.Text = dr.GetValue(6).ToString txtqty.Text = dr.GetValue(7).ToString dr.Close() conn.Close() Else MsgBox("Record Not Found", MsgBoxStyle.Information) Exit Sub End If End Sub

Private Sub CmdUpdate_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles CmdUpdate.Click conn.Close() conn.Open() Dim command As New SqlCommand() With command .Connection = conn .CommandText = "UPDATE BOOKS SET [ISBN]='" & txtISBN.Text & "',[AUTHOR]='" & TxtAuthor.Text & "',[BOOK_TITLE]='" & TxtBooktitle.Text & "',[CATEGORYINDEX]='" & cbcategory.Text & "',[YEARPUBLISHED]='" & TxtPublished.Text & "',[DATEARRIVED]='" & dtparrived.Text & "',[PRICE]='" & txtprice.Text & "',[QTY]='" & txtqty.Text & "',[MODIFY_BY]='" & UCase(Txtuserid.Text) & "',[DATEMODIFY]='" & Now.Date & "' WHERE BOOK_NO='" & txtbookNo.Text & "'" .ExecuteNonQuery() End With conn.Close() MsgBox("Record Updated Successfully", MsgBoxStyle.Information) clear() End SubEnd Class

8.3 SYSTEM TESTING AND IMPLEMENTATION

System testing is designed to uncover weaknesses that were not found in

earlier tests. This includes forced system failure and validation of the total system as it

will be implemented by its users in the operational environment. Generally, it begins

with low volumes of transactions based on live data. The volume is increased until the


maximum level for each transaction type is reached. The total system is also tested for

recovery and fallback after various major failures to ensure that no data are lost during

the emergency. All this is done with the old system still in operation. After the candidate

system passes the test, the old system is discontinued.

System testing consists of the following steps:-

1. Program testing: - A program represents the logical elements of a system. For a

program to run satisfactorily, it must compile and test data correctly and tie in

properly with other programs. Achieving an error-free program is the

responsibility of the programmer. Program testing checks for two types of errors:-

syntax and logic. A syntax error is a program statement that violates one or more

of the rules of the language in which it is written. A logic error, on the other hand,

deals with incorrect data fields, out-of-range items, and invalid combinations.

2. When a program tested, the actual output is compared with expected output.

When there is a discrepancy, the sequence of instructions must be tested to

determine the problem. The process is facilitated by breaking the program down

into self-contained portions, each of which can be checked at certain key points.

3. String testing: - Programs are invariably related to one another and interact in a

total system. Each program is tested to see whether it conforms to related

programs in the system. Each portion of the system is tested against the entire

module with both test and live data before the entire system is ready to be tested.

4. User Acceptance testing: - This is the last stage of system testing. An

acceptance test has the objective of selling the user on the validity and the

reliability of the system. It verifies that the system’s procedures operate to system

specifications and that the integrity of the integrity of vital data is maintained.

Performance of an acceptance test is actually the user’s show. User motivation

and knowledge are critical for the successful performance of the system.

5. System Implementation:-After a thorough testing of different aspects of the

system as described above the system is ready for implementation. The system


is to be run in parallel with the manual system for few days until the concerned

authority become fully confident of the computer- based system.

Chapter 10


Aim and objectives of the User Manual:

Enables the user to successfully log in to the system.

Create and maintain category, course etc

Entered details about book, librarian, student etc.

Issue book.

Find book outstanding.

Find book over due.

Maintaining transaction with up to date information.

Crating different reports.

Enables users to check transaction status.

Enables user to login under different permissions.

Enables user to log out of the system.

The Library Management System a computerized system from which the functions and

operations of the business are run and data captured and stored. The system runs

within the operating system Win98 or Win XP. The Library Management System works

with the same combination of a mouse with the ‘’point click principles. The user

interface has been designed to make selections, choices and data entry as easy and

efficient as possible.

Installation of the software from the CD:

Insert the LibrarySystem software CD into the drive.


By double clicking on the LibrarySystem Installer Package which is display the following

screen:

Click on the Next > button. Following window comes automatically .Then browse the

folder for installation. Make the path as C:\ LibrarySystem…


By clicking the next button following window come.


Operational Manual:

1. On running the Library Management System the user will first see the

following flash screen.


Fig: splash screen

2. Login Screen will appear after a while as follows. This is first level of

authentication form. A user can enter into the system by providing valid user

Id and password. Default userid and password is admin

3. By providing valid user_id and password user have to press “Login” button. Then he

will be in the following main form. This is MDI Form designed for selection of the

different Menus. Following menu options have been provided in this Main Form:-

1. Master Entry

a) Category

b) Course

c) Book


d) Student

e) Librarian

2. Transaction

a) Issue book

b) Due Book

c) Return book.

3. View

a. Book

b. Student

c. Librarian

4. Reports

a) Book

b) Student

c) Librarian

4. For running this software user have to first enter the master entry part. First user has

to enter category name and description in the category form with the following form. In


addition to above different Update, Delete, Save, Search, and Cancel command buttons

have been provided in the form.

5. For entering course name and description user have to use the following form. In

addition to above different Update, Delete, Save, Search, and Cancel command buttons

have been provided in the form.


6. By clicking the Book Entry Menu of the MDI form this form can be displayed for the

entry of new books in the library. Following Text Boxes have been provided for the entry

of the books related information:-

1. Book number.

2. ISBN.

3. Author Name.

4 Book title

5. Category

6. Year Publisher

7. Date Arrived

8. Price

9. Quantity.

In addition to above different Update, Delete, Add, Search, Refresh and Exit

command buttons have been provided in the form.

6. By clicking the Student Entry Menu of the MDI form this form can be displayed

for the entry of new students books in the school. This form automatically create

student ID.


In addition to above different Update, Delete, Add, Search, Refresh and Exit

command buttons have been provided in the form.

7. By clicking the Librarian Entry Menu of the MDI form this form can be displayed

for the entry of new Librarian in the school. This form automatically creates Librarian

ID.As Librarian is the official user in the system so he have to create password for

operating the system. This form provides this facility.


9.

This form can be obtained by clicking the “Issues of Books” under the third menu

“Transaction” for issuing a particular book available in the library along with the issue

and due date. The following text boxes have been provided for entry of Issuance of the

Book.

1. Book No.

2. Student ID


3. Current No. of Copies Available

4. Issue Date

5. Due Date

In addition to above different Update, Delete, Add, Search, Refresh and Exit command

buttons have been provided in the form.

10. The Librarian can view all the due books with the following form.

11.


This form can be obtained by clicking the “Books Return” under the third menu “Issues

of Books” for returning a particular book issued to user from the library along with the

issue, due date and return date with fine if any. The following text boxes have been

provided for entry of return of the Books.

6. Book No.

7. Student ID

8. Current No. of Copies Available

9. Issue Date

10. Due Date

11. Return Date

12. Fine, if any

In addition to above different Update, Delete, Add, Search, Refresh and Exit command

buttons have been provided in the form.

12. There is different view in this software.


13. There are several reports are also generated through this software which are as

follows.


Fig: Record Delete Operation

5. For deposit amount user has to follow the following form. For each new

transaction the user have to press new button first. Then transaction ID will

automatically create.


CONCLUSION

It is difficult to summarize the multitudinous knowledge that has been acquired

throughout the life of this project, but hopefully this report and conclusion has attempted

to give the reader a full appreciation of the vast scale of learning that has been

achieved.

Many new things were learnt and full revision of what has been covered to date in the

course was also attained, resulting in a feeling of confidence for the future, and any

other project that may come my way.

My understanding of what the project was supposed to manifest was that a great deal

can be learnt through practical experience and making mistakes. I would now know

what to change if I were to repeat the same project, and where my focus of

concentration should lie. This may not have been possible simply from reading a book.

A sound awareness of the importance of hands on experience and the inevitability of

oversight and learning from them was gained and has, I believe academic improved my

all round abilities, especially relating to computing.


Fundamentals of Software Engineering. -----------------Prentice Hall IndiaBy Rajib Mall.

System Analysis and Design ----------------------------Galgotia Publications.By Elias M.Awad

Fundamental of Database System ------------------------Pearson Education.By Elamasari Navathe.

VB.NET programming -------------------------------Black Book PublicationsBy Steven Holzner.

Google.co.in

lms

Documents