A PROJECT REPORT ON

“SCHOOL LIBRARY MANAGEMENT SYSTEM”

SUBMITTED FOR THE PARTIAL FULFILLMENT FOR THE REQUIREMENT
OF

BACHELOR OF COMPUTER APPLICATION (BCA) 6th SEMESTER

UNDER DIBRUGARH UNIVERSITY

SUBMITTED TO:

DEPARTMENT OF COMPUTER SCIENCE

SESSION: 2016-2019

NERIM GROUP OF INSTITUTIONS

WEBSITE: www.nerimindia.org

SUBMITTED BY: EXTERNAL GUIDE INTERNAL GUIDE:

BIPLAB ACHARJEE Mr. DEEP SINGH Dr. TARALI KALITA

ROLL NO: 31520006, CATLA IT & ENGG ASST. PROF,

REG. NO: 16320594, PVT. LTD. Dept. of Comp. Science

1
 CECRTIFICATE OF APPROVAL

This is to certify that the project work entitled “SCHOOL LIBRARY MANAGEMENT
SYSTEM” carried out by BIPLAB ACHARJEE bearing exam Roll No 31520006,
Registration No 16320594 under the guidance of DR. TARALI KALITA has been found
satisfactory and is hereby approved as a project work carried out and presented in a manner
required for its acceptance in partial fulfillment of minor project work of BCA 6th semester
under Dibrugarh University, Dibrugarh, Assam.

(________________) (_________________)

Internal Examiner External Examiner

Date: _____________ Date _____________

Place: NERIM Place: NERIM

2
 CERTIFICATE FROM HOD

This is to certify that the project work entitled “SCHOOL LIBRARY MANAGEMENT
SYSTEM” is carried out by BIPLAB ACHARJEE bearing exam roll no 31520006
registration no 16320594 of NERIM GROUP OF INSTITUTIONS under the guidance of
DR. TARALI KALITA in partial fulfillment of minor project work of 6th sem of 3 year
full time BCA course under Dibrugarh university, Dibrugarh, Assam is accepted by the
Department of Computer Science, NERIM, Guwahati.

DATE: ____________ (________________)

Dr. Hillol Kanti Bhattacharjee

HOD, Dept. of Computer Science,

NERIM

3
 CERTIFICATE FROM INTERNAL GUIDE

This is to certify that the project work entitled “SCHOOL LIBRARY MANAGEMENT
SYSTEM” is a bonafied work carried out by BIPLAB ACHARJEE bearing exam Roll No
31520006, Registration No 16320594 Of BCA 6th Sem of 3 Year full Time BCA course
under Dibrugarh University at NERIM GROUP OF INSTITUTIONS under my personal
supervision and guidance. The report is found worthy of acceptance for the partial
fulfillment of Major Project of BCA 6th Sem under 3 Year Full Time BCA program under
Dibrugarh University, Dibrugarh, Assam.

All helps received have been duly acknowledged and no part of this report has been
reproduced for any other degree or diploma.

DATE: _____________ (________________)

Dr. Tarali Kalita

Assistant Professor,

Department of Computer Science,

NERIM

4
 PROFORMA FOR SUBMISSION OF STUDENT PROJECT
PROPOSAL

Name and Address of Institution: NERIM Group of Institutions

Padma Nath Sarmah Bhawan
Tripura Road, Jayanagar, Khanapara,
Guwahati-22, Assam

1. Name and Address of the student: Biplab Acharjee

Room No. 504-s2
Bhardwaj Boy’s Hostel,NERIM

2. Title Of The Project: School Library Management System

3. Name of the Guide: Mr. Deep Singh

Director,
CATLA IT & ENGG. PVT. LTD.

4. Qualification of Guide: B.E, MBA

5. Working Experience of Guide: Since January 2012

CATLA IT & ENGG. PVT LTD.

Biplab Acharjee Mr. Deep Singh

Student Organizational Guide

Date: Date:

5
 ACKNOWLEDGEMENT

It is a great sense of satisfaction and a matter of privilege for me to do the project at

NERIM Group of Institutions as a BCA 6th semester trainee. I wish to express my heartily
thanks to the members of computer science department for providing me the opportunity to
undergo training in the esteemed organization. Under such a nice environment, systematic
work approach and target oriented task management of this division provide me with much
desired training experience needed for future as software professional.

I deeply express my sincere thanks to our head of the department Dr. Hillol Kanti
Bhattacharjee for encourage me. It is my sheer privilege to express my sincerest regards to
my internal project guide Dr. Tarali Kalita for her valuable inputs, able guidance,
encouragement, whole-hearted cooperation and constructive criticism throughout the
duration of my project.

I would like to take the opportunity to express my gratitude to all the teachers who have
directly or indirectly helped in my project.

I confess my gratitude to my friends for their cooperation and support.

Date: ___________ (________________)

Biplab Acharjee

BCA 6th semester

Roll No

6
 DECLARATION

This is to certify that I am a student of Bachelor of Computer Application (BCA) of

NERIM GROUP OF INSTITUTIONS and I have carried out my project entitled
“SCHOOL LIBRARY MNAGEMENT SYSTEM” in accordance with BCA course. This
project is not submitted to any university/institute for award of any other degree.

( ______________ )

Biplab Acharjee

BCA 6th semester,

Roll No. 31520006

7
 CONTENTS
CHAPTER 1: INTRODUCTION 10-13
1.1 Brief Description of the Organization
1.2 Title Of the project
1.3 Project definition
1.4 Drawbacks Of the Existing system
1.5 Proposed System and Objectives

CHAPTER 2: FEASIBILITY STUDY 14-16

2.1 Technical feasibility
2.2 Economic feasibility
2.3 Behavioral feasibility
2.4 Operational feasibility

CHAPTER 3: SOFTWARE REQUIREMENT GATHERING, ANALYSIS AND

SPECIFICATION 17-19
3.1 Functional requirements
3.2 Non-functional requirements

CHAPTER 4: HARDWARE AND SOFTWARE REQUIREMENTS 20-21

4.1 Hardware specification
4.2 Software specification

CHAPTER 5: SYSTEM ANALYSIS AND DESIGN 22-35

5.1 Data Flow Diagram (DFD)

5.2 ER Diagram
5.3 Data Dictionary
5.4 Module Description
5.5 Database Design

8
CHAPTER 6: FRONT END DESIGN 36-42
6.1 Input Design.

6.2 Output Design

CHAPTER 7: TESTING 43-48

7.1 Unit testing
7.2 Integration testing
7.3 System testing

CHAPTER 8: FUTURE SCOPE OF THE PROJECT 49-50

CONCLUSION 51

BIBLIOGRAPHY 52

9
CHAPTER 1:
INTRODUCTION

10
1.1 BRIEF DESCRIPTION OF THE ORGANISATION:-

Established in the year 2011, Catla IT & Engg. Co Pvt.ltd in

Khanapara, Guwahati is a top player in the category Internet Service Providers in the
Guwahati. This well-known establishment acts as a one-stop destination servicing
customers both local and from other parts of Guwahati. Over the course of its journey,
this business has established a firm foothold in its industry. The belief that customer
satisfaction is as important as their products and services have helped this establishment
garner a vast base of customers, which continues to grow by the day. This business
employs individuals that are dedicated towards their respective roles and put in a lot of
effort to achieve the common vision and larger goals of the company. In the near future,
this business aims to expand its line of products and services and cater to a larger client
base. In Guwahati, this establishment occupies a prominent location in Khanapara. It is
an effortless task in commuting to this establishment as there are various modes of
transport readily available. It is at Jaya Nagar Road, Six Mile, Opp. Sukapha Bhawan,
which makes it easy for first-time visitors in locating this establishment. It is known to
provide top service in the following categories: Internet Service Providers, Broadband
Internet Service Providers, Wifi Internet Service Providers.
Catla IT & Engg Co Pvt.ltd in Khanapara has a wide range of products and services to
cater to the varied requirements of their customers. The staffs at this establishment are
courteous and prompt at providing any assistance. They readily answer any queries or
questions that you may have. Pay for the product or service with ease by using any of
the available modes of payment, such as Cash, Master Card, Visa Card, Debit Cards,
Cheques, Credit Card

11
1.2 TITLE OF THE PROJECT:-

The tile of the project is “SCHOOL LIBRARY MANAGEMEN

SYSTEM”.

1.3 PROJECT DEFINITION:-

The project titled “School Library Management System” is Library management software
for monitoring and controlling the transactions of a library in a school. The project “School
Library Management System” is developed in Visual Basic 6.0, which mainly focuses on
basic operations in a library like adding new member, new books, and updating new
information, searching books and members and facility to borrow and return books.

“School Library Management System” is a windows application written for 32-bit

Windows operating systems, designed to help users maintain and organize library. Our
software is easy to use for both beginners and advanced users. It features a familiar and well
thought-out, an attractive user interface, combined with strong searching Insertion and
reporting capabilities. The report generation facility of library system helps to get a good
idea of which are the books borrowed by the members, makes users possible to generate
reports’ hard copy.

1.4 DRAWBACKS OF THE 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 or returning a book and also for searching
of members and books. Another major disadvantage is that to preparing the list of books
borrowed and the available books in the library will take more time, currently it is doing as
alone day process for verifying all records. So after conducting the feasibility study we
decided to make the manual Library management system to be computerized.

12
1.5 PROPOSED SYSTEM AND OBJECTIVES:-

The Proposed system is an automated Library Management System. Through the

software user can add members, add books, update information, edit information, issue and
return books in quick time. Our proposed system has the following objectives:-

 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.

13
CHAPTER 2:
FEASIBILTY
STUDY

14
 The initial investigation points to the question the project is feasible or not. A
feasibility study is conducted to identify the best system that meets all the requirements.
This includes an identification description, a valuation of the proposed system and selection
of the best feature for the system. Here the study is conducted in four ways such as
economic, technical, behavioral feasibility and operational feasibility.

2.1 ECONOMIC FEASIBILITY:-

Economic analysis is the most frequently used method for evaluating the effectiveness of
the candidate system. More commonly known as cost/benefit analysis, the procedure is to
be determining the benefits and savings that are expected from a system and compare them
with costs. The proposed system is economically feasible because the system is less time
consuming, the system will provide fast and secure environment thereby reducing the
chances of error. The system will also require very less man power thereby reducing costs
and increasing benefits.

2.2 TECHNICAL FEASIBILITY:-

Technical feasibility centers around the existing computer system(hardware and software
etc.) and to what extend it support the proposed addition. In this project, all the necessary
cautions have been taken care to make it technically feasible. Using a key the display of
text/object is very fast. Also, the tools, operating system and programming language used in
this localization process is compatible with the existing one.

15
2.3 BEHAVIORAL FEASIBILITY:-

People are inherently resistant to change, and computers have been known to facilitate
change. An estimate should be made of how strong a reaction the user staff is likely to have
toward the development of a computerized system. The software that is being developed is
user friendly and easy to learn. In this way, the developed software is truly efficient and can
work on any circumstances, tradition, locales.

2.4 OPERATIONAL FEASIBILITY:-

The main concern is to ensure operational feasibility of the system. The system that will be
developed will solve the problem that business encounters. The necessary solutions are
applied to the organization will be more at ease in their day to day operation. The
demanding tasks that are quite time consuming are minimized and lessen by applying
efficient methods with the use of the system.

16
CHAPTER 3:
SOFTWARE REQUIREMENT
GATHERING,ANALYSIS AND
SPECIFICATION

17
3.1 FUNCTIONAL REQUIREMENTS

The functional requirements specification documents the operations and activities that a
system must be able to perform. It is designed to be read a general audience. Readers should
be able to understand the system, but no particular technical knowledge should be required
to understand the document.

The main purpose of the system is to perform basic operations in a library like adding new
member, new books, and updating new information, and facility to issue and return books.
The system will allow admin to login and perform their own individual functions. Let us
study these functions in detail:

SERIAL REQUIREMENT REQUIREMENT PRIORITY

NUMBER NAME DESCRIPTION
1 Log in This function will enable Mandatory
the administrator to log in requirement
to the system by proving a
valid user-id and
password.

2 Add Members Admin can add members Mandatory

to the system requirement

3 Add Books Admin can add books to Mandatory

the system requirement
4 Update Members Admin can update the Mandatory
members information. requirement

5 Update Books Admin can update the Mandatory

books informations. requirement

6 Issue Books Admin can issue Books to Mandatory

the members requirement

18
7 Return Books Admin can approve return Mandatory
for books which are issued requirement
by the member.
8 Report generation Admin can view the Mandatory
details of all the requirement
members,books,issue
details,unreturned books
placed between two dates.

9 Log out The admin can logout Mandatory

from the system whenever requirement
he wants to.

3.2 NON-FUNCTIONAL REQUIREMENTS

The following are the non-functional requirements of the system:

1) The users must be able to access their account 24 hours a day, seven days a week.
2) Better component design to get better performance at peak time.
3) The system is supposed to take as less time as possible to respond to any event.
4) It should provide error message whenever any undesired event takes place.

19
CHAPTER 4:
HARDWARE AND
SOFTWARE
SPECIFICATIONS

20
4.1 HARDWARE SPECIFICATION OF THE CLIENT MACHINE
NEEDED:

Processor : Intel Dual Core 3 Ghz. or above

RAM : 1 G.B DDR-II or higher

HDD : 80 GB or higher

Monitor : SVGA COLOR

Keyboard : 108 keys

Mouse : 3 button Standard Mouse

4.2 SOFTWARE SPECIFICATION FOR DEVELOPING AND

IMPLEMENTING THE SYSTEM:

Operating System : Microsoft Windows 7 or above

Front End Used : Visual Basic 6.0

Back End Used : My SQL/ MS Access 2003

21
CHAPTER 5:
SYSTEM
ANALYSIS AND
DESIGN

22
System analysis is a detailed study of the various operation performed by a system and their
relationship within and outside the system. It is a systematic technique the refines goals and
objectives. The goal of the system development is to deliver the system in line user
requirement. And analysis is the heart of this process. One of the best approaches to the
system analysis is the structured analysis.

Structured analysis is a set of technique and graphical tools that allows us to develop new
kind of specification that is easily understandable to the developer. It is the detailed step by
step investigation of the related procedure to see what must be done and to determine the
best way of doing it. The objective is to build a system specification that provides the basis
for design and implementation.

The various tools used in developing the system are; -

 DATA FLOW DIAGRAM.

 ER DIAGRAM.

5.1 DATA FLOW DIAGRAM(DFD):-

DFDs show the flow of data from external entities into the system, showed how the data
moved from one process to another, as well as its logical storage. There are only four
symbols:

 Rectangle representing external entities, which are sources or destinations of data.

 Rounded circles representing processes.
 Arrows representing the data flows.
 One side Open-ended rectangles representing data stores.
 Snip single side rectangle represents output.

5.2 ER DIAGRAM:-

An entity relationship diagram (ERD), also known as an entity relationship model, is a

graphical representation of an information system that depicts the relationships among
people, objects, places, concepts or events within that system. An ERD is a data modeling

23
technique that can help define business processes and be used as the foundation for
a relational database.

SYMBOLS USED FOR DFD: -

EXTERNAL ENTITY

PROCESS

DATA FLOW

DATA STORE

OUTPUT

24
SYSMBOLS USED FOR E-R DIAGRAM: -

ENTITY

RELATION

ATTRIBUTE

KEY_ATTRIBUTE

25
CONTEXT DIAGRAM:-

Issue_info

Book_Entry
Member_entry
Login SLMS REPORT
ADMIN Acknowledgement

Return_Info 0

IssueDate

26
Level 1 DFD:-

Login_info User
Login

0.1

Book_info,member_info Books
Entry

0.2

Book_info,Member_info
Update
Member

0.3

Issue_info
Issue

Transactions
0.4

Return_info
Return

0.5

ReportGen

0.6

27
Level 2 DFD (For Entry):-

Book_info Book
Books
Entry

0.2.1

Member_info Member Member

Entry

0.2.2

Level 2 DFD (For Update):-

Book_info Book Books

Update

0.3.1

Member
Member_info
Update Member

0.3.2

28
 E-R Diagram:-
Publisher

Rdate
Idate Name Subject

ID Author
Issue / N Books
Return
Price
bDate
Borrowed NoofBooks
Name Age

M
ID Member Class

Section
mDate
Bookstatus Address

29
5.3 DATA DICTIONARY

SL No. FIELD NAME DATA TYPE SIZE DESCRIPTION

UserID Text 50 User id of the
administrator
password Text 50 Password of the
administrator
ID Text 50 User id of the member
Name Text 50 Name of the member
Age Text 50 Age of the member
Class Text 50 Class of the member
Section Text 50 Section of the member
Address Text 50 Address of the member
BookStatus Text 50 Book Status of the member
mDate Date/time Registration Date
ID Text 50 Unique ID of the book
Name Text 50 Name of the book
Publisher Text 50 Publisher info
Subject Text 50 Subject info
Author Text 50 Author info
NoofBooks Text 50 Number of books
Borrowed Number 50 No. of books issued
bdate Date/time 50 Issue date
ID AutoNumber 50 Transaction ID
MemberId Text 50 Unique Id of the member
BookId Text 50 Unique id of the book
Idate Date/time Issue date
Rdate Date/time Return Date
BReturn Yes/no Status of book return
Returndate Date/time Return date of the book.

30
5.4 MODULE DESCRIPTION

5.4.1 LOGIN MODULE:

This module starts when the admin logs in to the system by providing valid userid and
password.

5.4.2 ADD BOOKS MODULE:

This module starts when the admin wish to add a new books to the system. The admin can
add any new books by entering all the necessary and valid descriptions such as publisher,
book name, author, price and many more.

5.4.3 ADD MEMBER PRODUCT MODULE:

This module starts when the admin wish to add a new member to the system. The admin can
add any new member by entering all the necessary and valid descriptions such as class,
member name, class, section and many more.

5.4.4 ISSUE BOOK MODULE:

This module starts when a member issue a book and the admin needs to approve the
transaction. If the transaction is succesfull, appropriate message will be displayed.

5.4.5 RETURN BOOK MODULE:

This module starts when a member returns a book and the admin needs to approve the
transaction. If the transaction is succesfull, appropriate message will be displayed.

5.4.6 REPORT GENARATION MODULE:

This module starts when the admin wish to view all the reports such as member details.
Books details, books issue details, unreturned books details.

31
5.5 DATABASE DESIGN: -

FOR USER

Field Name Data Type Description

UserId Text Primary key
Password Text
CreationDate Date/time
CreatedBy Text
ModifiedDate Date/Time
ModifiedBy Text

FOR MEMBER

Field Name Data Type Description

Id text Primary key
Name text

Age text

Class text

Section text

Address text

Bookstatus text

MDate Date/time

32
FOR BOOKS

Field Name Data Type Description

Id text Primary Key
Name text

Publisher text

Subject text

Author text

Price text

Bdate text

Barowed number

NoofBook Date/time

FOR TRANSACTIONS

Field Name Data Type Description

Id autonumber Primary key
MemberID text Foreign key
Idate Date/Time Foreign key
Rdate Date/Time Foreign key
BReturn yes/no
ReturnDate Date/Time

33
5.6 NORMALIZATION

Normalization is the process by which we efficiently organize data to achieve the following
goals:

 Eliminating redundancy
 Ensuring data is stored in the correct table
 Eliminating need for restructuring database when data is added.

There are five levels of normal form but Third Normal Form is sufficient for most typical
database applications. The table in my system “School Library Management System” are
normalized. Let us study in details:

1. ADMIN TABLE
i. FIRST NORMAL FORM: It is in first normal form because the fields
“userid” and “password” have no repeating values and has only a single
value. There are no repeating or duplicate fields. Each record is unique.
ii. SECOND NORMAL FORM: It is second normal form because all they non
key fields i.e. “password” completely depends on the primary key i.e.
“userid”.

2. MEMBER TABLE
i. FIRST NORMAL FORM: It is in first normal form because the field “ID”
is atomic and cannot be divided further. It does not have repeating value.
Each record is unique.
ii. SECOND NORMAL FORM: It is in second normal form since there is no
partial dependency of any of the non-key column on the primary key “ID”.

34
3. BOOKS TABLE
i. FIRST NORMAL FORM: It is in first normal form because the field “ID”
is atomic and cannot be divided further. It does not have repeating value.
Each record is unique.
ii. SECOND NORMAL FORM: It is in second normal form since there is no
partial dependency of any of the non-key column on the primary key
“ID”.

4. TRANSACTION TABLE
i. FIRST NORMAL FORM: It is in first normal form because the field “ID”
is atomic and cannot be divided further. It does not have repeating value.
Each record is unique
ii. SECOND NORMAL FORM: It is in second normal form since there is no
partial dependency of any of the non-key column on the primary key “ID”.

35
CHAPTER 6:
FRONT END
DESIGN

36
 6. FRONT END DESIGN

6.1 INPUT DESIGN

1. Login

2. Add Books

37
3. Add Member

4. New Issue

38
5. Book Return

6. Update Books

39
7. Update Member

6.2 OUTPUT DESIGN

8. List of all books

40
9. List of all members

10. List of issued books

41
11. List of unreturned books

42
CHAPTER 7:
TESTING

43
7.1 UNIT TESTING: -
Unit testing emphasizes the verification effort on the smallest unit of software design i.e. a
software component or module. Unit testing is a dynamic method for verification, where
program is actually compiled and executed. Unit testing is performed in parallel with the
coding phase. Unit testing tests units or modules not the whole software.

The log in function will enable the administrator to log in to the system by proving a valid
user-id and password.

SERIAL TEST CASE ACTION

NUMBER
1 Empty userid There will be an echo
Empty password message “enter userid and
password”.
2 Empty userid There will be an echo
Entered password message “enter userid”.
3 Entered userid There will be an echo
Empty password message “enter password”.
4 Valid userid There will be an echo
Invalid password message “invalid password”.
5 Invalid userid There will be an echo
Valid password message “user doesn’t exist”.
6 Invalid userid There will be an echo
Invalid password message “invalid userid and
password”.
7 Valid userid The system will redirect to
Valid password the main interface

44
Through manage Books; admin can view the books that are already in the system.

SERIAL TEST CASE ACTION

NUMBER
1 Click on “manage books”. The list of books will be
shown.

Through delete Books, admin can delete the book.

SERIAL TEST CASE ACTION

NUMBER
1 Click on “delete”. The book will be deleted.

Through edit Books, Admin can update the book information.

SERIAL TEST CASE ACTION

NUMBER
1 Any field empty The book will not be
updated.
2 All the fields empty The book will not be
updated.
3 All the fields filled The book will be updated.

Through manage Members; admin can view the members that are already in the system.

SERIAL TEST CASE ACTION

NUMBER
1 Click on “manage members”. The list of members will be
shown.

45
Through delete member, admin can delete the member.

SERIAL TEST CASE ACTION

NUMBER
1 Click on “delete”. The member will be
deleted.

Through edit Member, Admin can update the book information.

SERIAL TEST CASE ACTION

NUMBER
1 Any field empty The product will not be
updated.
2 All the fields empty The product will not be
updated.
3 All the fields filled The product will be
updated.

46
7.2 INTEGRATION TESTING: -

Integration testing is the phase in software testing in which individual software modules are
combined and tested as a group. It occurs after unit testing and before validation testing.
The purpose of integration testing is to verify the functional, performance and reliability
between the modules that are integrated.

ADMIN

SERIAL MODULE 1 MODULE 2

NUMBER
1 If not logged in to the system Cannot go the main Interface
2 If not logged in to the system Cannot add books
3 If not logged in to the system Cannot add members
4 If not logged in to the system Cannot issue books
5 If not logged in to the system Cannot return books
6 While updating product Updating not successful
information, if any field left empty
7 When a product is deleted It is no longer available in the
system

47
7.3 SYSTEM TESTING

System testing is a level of the software testing where complete and integrated software is
tested. The purpose of this test is to evaluate the system’s compliance with the specified
requirements. It involves the external workings of the software from the user’s perspective.

After performing the above unit tests and integration tests, let us now test the system as a
whole in accordance with the test cases.

1) If the admin can login to the site, he/she will able to add books, view books, delete
books and update them as well. He/she will be also able to issue and generate issue
reports.
2) If the admin can login to the site, he/she will able to add members, view members,
delete members and update them as well.
3) The admin cannot issue without logging in to the system and will not be able to
access the main interface and view, add books and members to the system.

48
CHAPTER 8:
FUTURE SCOPE

49
 FUTURE SCOPE OF THE PROJECT

The future scope of the project includes that what all future enhancements can be done in
this system to make it more feasible to use. While developing the software, though we have
tried our best to fulfill all necessities of the organization, there is every possibility of some
drawbacks in the software. Those drawbacks can be overcome by further modifying in the
sphere of security and if a backup system is developed. Again rest of the need is to change
its appearance so that it becomes more users friendly.

We can add many new scopes and features to the system “School Library Management
System” in order to make it more reliable, secure and user friendly.

Some of the extensions which can be made later are:

i. Database for different class can be provided.

ii. Books quantity can be provided.
iii. Multilanguage support can be provided so that it can be understandable by the
person of any language.
iv. More graphics can be added to make it more users friendly and understandable.

50
 CONCLUSION

While developing the system a conscious effort have been made to create and
develop a software package, making use of available tools, techniques and resources
– that would generate a proper system.
While making the system, an eye has been kept on making it as user-friendly, as
cost-effective and as flexible as possible. As such one may hope that the system will
be acceptable to any user and will adequately meet his/her requirements.
Working on this project was a good experience. It taught how important every step
is in developing software, from collecting user requirements to planning and giving
proper coding to every design.

51
 BIBLIOGRAPHY

BOOKS REFERED:

Mastering Visual Basic 6.0

Visual Basic 6 complete

Fundamentals of Software Engineering

WEB SITES:
 https://www.w3schools.com
 https://www.scribd.com
 https://www.tutorialspoint.com

52