Library Management System: Asutosh College

LIBRARY MANAGEMENT SYSTEM
By
Rintu Mondal, Sayan Sen, Debasish Kayal,

Manoj Chowhan, Sutanu Das
Supervisor: Mr. Rishi Bhattacharya
Asutosh College
Second Campus
Bachelor Of Vocational,
Software Development.
Declaration
The project submitted herewith is a result of our own efforts in totality and in every aspects
of the project works. All information that has been obtained from other sources had been
fully acknowledged. We understand that any plagiarism, cheating or collusion or any sorts
constitutes a breach of College rules and regulations and would be subjected to disciplinary
actions.
Acknowledgements
After complete this Project, We would like to take this chance to express my sincere gratitude
to my project supervisor which is Mr. Rishi Bhattacharya who has guided us a lot throughout
the project development. When We still doing nothing while project due date is getting close,
he give us some pressure to complete the system. Without him, We think We can’t finish the
system on time. In addition, while We meet some logic problem or design problem, Mr.
Bhattacharya always the one give us useful and logic answer.
We would like to thanks Mr . Rishi Bhattacharya for one more time because he share his
experience with us so that we can get more logic understanding on how to develop a software
which suitable for the current society.
Table of Contents
Chapter 1 :................................... System Planning.
Chapter 2:.................................... Require Analysis.
Chapter 3:.................................... System Design.
Chapter 4: ....................................Programming.
Chapter 5: ....................................System Testing.

Chapter 6:.................................... Conclusion.
Chapter 7:.................................... Reference.
Chapter 1
System Planning
• System Planning
The developing process of the Library Management System will be carried out in this
chapter as well as the system objectives, scope and schedules.
• Project Aims and Objectives

The project aims and objectives that will be achieved after completion of the system were
carried out in this sub chapter. The succession of the system also will be evaluated through
this sub chapter.
The project objectives are:
• To eliminate the paper-work in library
• To record every transaction in computerized system so that problem such as
record file missing won’t happen again
• To implement BarCode, SMS technologies into the system
• To design a user friendly graphical user interface which suit the users
• To complete the system according to project schedule
• To produce technical report that documents the phases, tasks and deliverables in
the project
• Background of Project
Library Management System is an application refer to other library system and it is suitable
to use by small and medium size library. It is use by librarian and library admin to manage
the library using a computerized system. The system was developed and designed to help
librarian record every book transaction so that the problem such as file missing or record
missing will not happened again.
Barcode reader is equipped in this system so that users can enjoy the convenience without
need to key in the barcode of the book themselves. It is convenience and time saving as the
users can direct scan in the book’s barcode id when the members borrows few books in one
time.
Book and member maintenance module also included in Library Management System. Users
can register or edit the member or book in the system. With this computerized maintenance,
library will not lost the book record or member record which always happen when no
computerized system bring used.
In addition, report module is also included in Library Management System. If user’s position
is Admin, the user is able to view different kind of report. First type of report are rental and
return report, user can check the rental, return transaction which happen on particular day.
Besides that, user can check the Top10 books which borrow by the member in a day, month
or year based on category. Moreover, activity log report also provided by system so that
admin can check what process has been carried out such as register new book, edit member
information as well as login, logout information.
All these modules are able to help librarian to manage the library more convenience and
efficiency compare to those library without computerized system.
• Project Scope
In this sub chapter, project scope will carried out what modules were contains inside
the Library Management System.
For Library Management System, it is divided into online web site and library system.
For my part, We was responsible for library system while the online web site was carried
out by my friend Koh Yee Keat.
At here, We will describe my own part which is library system which used by librarian.
Library system
• Authorization and Authentication Module
Authorization and Authentication

ID / Password Password
Checking Recovery
This module is used by user which means librarian in the library. They need to
login to the system using their id and password. In order to distinguish the user’s
level, user can access to different module when successfully login. For example,
only admin level users are able to access the report module.
• Book Maintenance Module
Book Module can access by any user from all levels. This module can used to
maintain the book inventory record such as search, add and edit. In addition,
we can generate the barcode for particular book and print it out so that
librarian can stick the barcode on the book cover.
• Outline of approach / Methodology used
The software used to develop Library Management System is Microsoft Visual Studio
2010 and SQL Server 2008 R2 as the database. On the other hand, the methodology We
used to develop this system is waterfall model.
Waterfall model is one of a system development life cycle(SDLC) model. Users proceed
to next phase if and only if current phase is complete. Users are not allowed go back to
previous phases if there are any mistake so they named it waterfall model, just like the
water is always fall down from the waterfall and not flow upward.
In Royce's original waterfall model, the waterfall model originally consists of 7 phases
which is Requirement Specification, Design, Construction, Integration, Testing and
Debugging, Installation and Maintenance.
Firstly, we collect the requirement for the library system, and then we analyzed it. After
analyzed the requirement, we proceed to design stage. In the design phase, We design
not only the user interface, but also the database design. The next phase in waterfall
model after design phase is Construction phase. Construction phase is an important
phase in waterfall model and it is a time consuming phase depends on programmer’s
ability. In Library Management System development, construction phase is using C#
coding to write the program. IT is very time consuming if the programmer don’t
understand the logic or still fresh to the coding. After done the coding phase, we will
proceed to integration phase. In this phase, online web site and library system will share
a same database to make integration between two applications. The next phase after
integration is the testing and debugging phase. For testing module, it is separated into
few types which are module testing, system testing, unit testing and user acceptance test.
Once there is a bug founded, it will be solve immediately before the system is launched
to ensure the system launched is bug free.
Lastly, it is installation and maintenance phase. In this phase, the system will be installed
at user side. After installed the system, maintenance is compulsory needed to
ensure the system is always-on and up to date with latest technologies or latest business
process.
In my opinion, the time spent on earlier phases of SDLC can lead to greater economy in
later stages. It is because in the earlier phase, a bug can be fixed in short time, less cost
and less effort compared to later phases.
• Development Environment
Software
Operating system: Window 10

• Database: Microsoft SQL Server 2008 R2
Development tools and programming language: Microsoft Visual Studio 2010

and C# We would like to use Microsoft Visual Studio 2010 as our developing
software. Visual Studio 2010 is powerful and flexible developing software, it
allows us to build a good design application with an easy-use drag and drop
controls on our form. We can see the user-friendliness of our application once we
finished drop the control on form.
Chapter 1: Conclusion
In chapter 1, we discussed about the project background, project schedule, project scope,
methodology used and the developing environment and operating environment.
We have faced few problems during system planning. Firstly, the biggest different with other
group is my group didn’t make system for targeted company. We create the system which
contains the library management basic function and the library system can be used by any
library especially those not yet implement the computerized system. In this case, we are not
able to ask about the user requirement from the end user. Thus, we seek the library system
requirement from internet and ask the opinion from supervisor and friends.
On the other hand, we meet some problem in the project schedule. Originally we plan to start
the development process at July 2010, but during internship we didn’t have much time to
process our FYP and delay until end of internship. This make us waste a lot of time and we
need to finish a module in a week on time while other people are having a month to complete
a module.
The methodology used by us is waterfall model. We need to complete the current stage
before we can proceed to next stages. In this case, we need to design the interface before
proceed to coding problem. These cause us a big problem because the interface we designed
causes some problem during coding stages. The way We solve this problem is write come
linkage coding while designing the interface. This process can let us imagine the process flow
while designing the interface and ease my work during coding stage.
In this chapter, We have learn that during when using one methodology, we must not
followed the steps blindly but make some necessary changes that will ease our job while
minimize the error.
Chapter 2
Requirement Analysis
• Requirement Analysis
In this chapter, we will discuss and analyses about the developing process of Library
Management System including Software Requirement Specification (SRS) and Data
Flow Diagram (DFD).The functional and non-functional requirements is included in SRS
part to provide complete description and overview of system requirement before the
developing process is carried out. Besides that, DFD provides a view of how the system
or business flows that able to increase the efficiency and effectiveness to achieve system
objectives.
• Software Requirement Specification (SRS)

• General Description
Product Description
Library Management System is a computerized system which can helps user (librarian)
to manage the library daily activity in electronic format. It reduces the risk of paper work
such as file lost, file damaged and time-consuming. It can help user to manage the
transaction or record more effectively and time-saving.
Problem Statement
The problem occurred before having computerized system includes:
• File lost
When no computerizes system is implemented, the file always lost because of
human and environment. Sometimes librarian didn’t keep the record to its
original place because of a lot member queue up to borrow books. After that the
file was missing due to messy environment.
• File damaged
In the other possibility, the file/record will be damaged due to accident. For
example the librarian accidentally hit a glass of drink and pours onto the paper
file. The record will be damaged. Besides this, natural disaster such as flood also
will cause damage to the file record.
• Difficult to search record

Without computerized system, when member wants to borrow a book, librarian
hard to search for the member’s record. It will cause time-consuming when a lot
member are waiting to borrow the books.
• Space-consuming
After long operation time of the library, the records are getting more and more.
Finally, the physical record was space-consuming and no place to keep the file.
• Difficult to view reports

Report need to generate manually without computerizes system. Admin need to
get the book transaction record and find the information based on the time period.
It is time consuming to generate one report.
• Cost consuming
Paper is needed to add every new record. After a long period of time, the cost to
buy a paper can be high. On the other hand, library needs to employ more staff to
solve the long queue problem. If the library only has one staff, it is not enough
time to process the book transaction.
• System objectives
• Improvement in control and performance
The system was developed to overcome the current problem occurred in library.
The system must be able to validate the user, store the record and bug free.
• Save cost
After implementing the computerized library system, library can only hire 1 or 2
staff to handle the book transaction process. With the aids of computerized
system, library can save the cost of hire employee and also save the paper-cost.
• Save time
Librarian is able to search the record in short time by pressing only few keys.
Compare to previous time before implementing the system, librarian can save a
lot time.
• System Requirements
• Non-functional Requirements
• Products Requirements
Efficiency requirements
With the library management system, librarian should be able to process faster
when they process book transaction. In addition, with the use of bar code scanner,
librarian can avoid to type the book id one by one, bar code scanner enable
librarian to scan the book id instantly.
Reliability requirements
The system must perform accurately towards member request. For example, when
the librarian saves the edited profile detail, after they review their detail, the
details must be change according to the latest details that they have updated.
When member return the book after the expired date, the fine should be calculate
accurately. Besides that, in the registration form, it will have validity check to
check the input to prevent wrong data type.
Usability requirements
This system must be designed with user-friendly and easy to use by the staff so
that the user can perform their job nicely. It must have a clear instruction to guide
user through the system. Besides that, the description of error message should be
clear.
• Organizational Requirements
Implementation requirements
In implementing the system, it uses the vb.net as the main programming language
and tools. Besides that, the SQL language will be use to maintain the information
in the database. On the other hand, SQL Server 2010 needs to be installed.
Delivery requirements
The whole system is estimate to be done around 6 months time and the
documentation will be done in 2 months. The full system will be delivers in a
softcopy method while the documentation will be delivers in hardcopy and
softcopy.
• External Requirements
Legislative requirements
The information that use must be acknowledge by the authorized people so that it
has no violating the law. This information is copyrighted and protected by the
law. Besides that, when visitors wants to become the member of the library, he or
she must agree with the rules stated in the system.
Security requirements
This system must be highly secure in the login part. It is because the report can
only view by admin level. Staff can perform most of the process except viewing
report module and log file module.
• Functional Requirements
• Normal User
• User Login
Description of Feature
This feature used by the user (librarian / library admin) to login into the system.
They are required to key in the user id and password before they are allows entering
the system. The user id and password will be verified and invalid id is not allowed
to enter the system.
Stimulus / Response Sequences

Stimulus : User runs the system.
Response : System request for user id and password.
Stimulus : User enters user id and password at the textbox provided.
Response : System verifies the user id and password with the data inside database.
If the user id is invalid or password not matches, message box will be prompt out to
notify the user. If valid, user successfully login to the Library Management System.
Functional Requirements
• User id is provided when they register as staff.
• The system must only allow the user with valid id and password to enter
the system.
• The system must be able to perform authorization process which

decides what the user’s level can access to.
• The user must able to logout after they finished using the system.
• Register New book
This feature can be performing by all users to register new book to the library.

Stimulus : User press Register new book.
Response : System prompts Add Book form.
Stimulus : User types the book ISBN number and key in the related information.
User chooses a quantity of how many new books were bought and the purchase
price.
Response : System will validate the information entered such as ISBN length, price
entered whether in correct format. If all the information was entered correctly,
system will add the book into [Book] table and [BookInfo] table. The row entered
into [bookcopy] is depends on how many book purchased. After enter into database,
system will prompts a message box stated that the book was enter successfully.
• System must be able to verify the information.
• System must enter the correct copies quantity into book copies table.
• The repeated ISBN number should not be allowed to enter into
database.
• Search Book
This feature is found at book maintenance part. The event is using KeyUp. User can
search the book based on book title, category or publisher. Once user key in a
character into the Search textbox, system will filter and show out the books which
fulfil the search criteria.
• System must be able to search the database based on selected search
type ( book title , etc)
• System must able to filter the book based on the keyword entered.
• System must able to show out the filtered book in listview.
• Member Maintenance
This feature can be performing by all users to register, edit information of a
member.

Stimulus : User press Member Registration.
Response : System prompts Member Registration form.
Stimulus : To add a new member, user clicks ‘Add’ and enters the information.
The member id is generated automatically. On the other hand, if the user wants to
change the member information, they need to select a member, and click ’Edit’, the
textbox will become enable so that they are able to change the data. Click ‘Member
Renewal’ will add 1 years more valid status for member.
Response : System will store the latest information into database.
• System must able to auto generate the member id.
• System must not generate the same member id.
• When user click the member on listview, system should show out the
member information on textbox provided.
• System should not allow MemberID to be change when user clicks
‘Edit’.
• System should be able to validate the ic, email and other info before
insert into database.
2.2 Data Flow Diagram
2.2.1 Context Diagram
Figure 1.3 Context Diagram for Library Management System
Library Management System : Requirement Analysis
Figure 1.4 Level 0 DFD diagram for Library Management

3
5
2.2.3 Level 1DFD (Lower – Level Diagram)
• Member Registration
Figure 1.5 Level 1 DFD for Member Registration Module
• Return book
Figure 1.7 Level 1 DFD for Return Book Module
2.3 Chapter 2 Conclusion
In this chapter, We do research about system objectives and system requirements. Besides
that, We need to construct the Level 0 Data Flow Diagram (DFD) as well as Level 1
DFD/
In this chapter, We meet a lot problem during construction of DFD diagram. The main
reason is because the DFD diagram construction if study during Diploma level and We
have forget how to draw it. When We refer to senior’s final report, my brain is blank
about how to construct.
After seek help from few friends, We found that they unable to help us because all of
them also meet the situation like us. Thus, We have to study back the DFD on my own.
We found back my Diploma study material, course System Analysis Design. We study
again the DFD chapter and finally We could construct the DFD for my Library
Management System.
The lesson We learn in this chapter is we must try not to forget what we have learn in the
college because in future we might need it in future. In addition, We found the Level 0
DFD is very useful because it can let next programmer or user to understand how to
system works.
Chapter 3
System Design
• System Design
This chapter will discuss about System Design phase which is one of the SDLC
phase. The GUI design, database design will be carried out in this chapter.
• External Interface Requirements
• User Interfaces
Library Management System is used by librarian and admin so it just simply

designed and not colorful. The interface is user friendly and easy to use. This
can be proving when user can know what the button’s function is when he/she
looks at the button. It is because the button’s text is clear and easy to
understand. For example when want to delete a record, We use ‘Delete’ as
button’s text and not ‘Destroy’ or ‘Eliminate’.
Library Management System (application used by librarian)

Normal level user
• Login Page
This is the login page for librarian and admin. The form is designed without colorful
interface because it is used by librarian and admin which can be considered as backend.
The login interface is simply design with ID and password textbox.
In figure 1.2, the ‘Forget Password’ label will show when user focused on password
textbox.
• Main Page
Figure 2.1 is the main page for library system. In is the form where book transaction
module was carried out. The top left side got the menu and top right part show the current
time. In this form, the color and word is default setting by Visual Studio 2010. There is
no necessary to design the form colorful because member didn’t make use of this system.
Figure 2.2 is the control which shown member’s transaction detail and also transaction
history.
• Book Maintenance Form
This is the book maintenance form. It will show all books in library when the form is
loaded. When user selects one of the books, its details will be shown at right part.
Search function is provided so that user can easily found the book if there are hundreds
of book in the library.
Figure 3.2 is a sub module under book maintenance which is Book Registration. The
form is provided with few textbox to insert the book information. We used a picture box
to let user select the picture so that user can preview the photo after select a file.
Figure 3.4 is a book report under book maintenance module. We used crystal report
viewer to let user preview the report before they print out.
Bar Code Generator sub module enable user to print the barcode. The bar code
generated based on the book copy that selected by user.
Search function is provided in book maintenance so that user can search the book easily
if the library is having more than hundred books. We provide a drop down list for user so
that user can select other search category.
• Member Maintenance Form
This is the form for member maintenance. It is almost similar to book maintenance form.
The developer put the listview at left side so that user can view the information at right
side. It is more users friendly.
There are few functions can be done in member maintenance such as add new member, edit
member information. Membership renewal, print ID card and also View all member Report.
Figure 4.2 shows the member registration form. The form only contains the few fields
which user need to insert when register the member. A proper control has been used so
that user can use the system easily.
Figure 4.2 shows the outlook of Member maintenance form when librarian presses
‘Edit’. Librarian is only allows to edit some information such as name, ic, phone, email
and address. The member id is not allowed to change because it uniquely identified a
member. Some control is disabled in edit mode to avoid the functional error.
This sub module is used to generate member ID card. Each member will have their own
ID card after they register as member. Print Preview enable user to preview the member
card before print it out. If the user is not able to preview, they need to re print and waste
the paper.
• Publisher Maintenance Form

Figure above shows Publisher maintenance forms. The form is only contains 2
information which is publisher ID and publisher name. It is be because this is additional
module used when user wants to ad a book.
• Book Transaction Report (Rental / Return)
This is the report list view that shows all the book transaction happens on particular date.
It is a shortcut way to view the report without need to print out the report.
• Library Detail Form
This form will be shown when admin user login for first time. The library detail must be
entered to avoid some functional error. The form is small and full with the field needed.
Most of the real system also designed in this way because the user is not member.
• Entity Relationship Diagram (ERD)

Figure 15.1 Entity Relationship Diagram for Library Management System
• Data Dictionary
Table Name: Admin

Description : store the information of user who used the library system
Null/Not Default
Fields Data Type Rules
Null Value
ID varchar(50) Not null - -
User_Name varchar(50) Not null - -
Password varchar(50) Not null - -
Field Example Data

Admin_ID 1
User_Name Admin
Password 1234
Table 3.4.2 Data Dictionary for Admin table
Table Name: Book

Description : store the information of the books
Null/Not Default
Null Value
ID nvarchar(50) Not null - -
Book_name nvarchar(50) Not null - -
Author_name nvarchar(50) Not null - -
Publication_name nvarchar(50) Not null - -
Book_qty nvarchar(50) Not null - -
Book_available nvarchar(50) Not null - -
Purchase_date nvarchar(50) Not null - -
Field Example Data

ID 6
Book_name ASP.NET
Author_name Devin Reader
Publication_name Wrox
Book_qty 40
Book_available 10
Purchase_date Friday, September 07, 2018
Table 3.4.3 Data Dictionary for Book table
Table Name: Student
Description : to store the information of the member
Null/Not Default
Null Value
ID Char(10) Not null - -
Name varchar(50) Not null - -
Roll varchar(50) Not null - -
Address varchar(50) Not null - -
Contact Char(5) Not null - -
Class varchar(50) Not null - -
Stream varchar(50) Not null - -
Email varchar(50) Not null - -
Profile_pic nvarchar(MAX) Not null - -
Enrollment varchar(50) Not null - -
Field Example Data

ID 3
Name Sayan
Address Lakegarden
Roll 94
Contact 7272016059
Class 3rd Year
Stream B.Voc
Email sayansanu30@gmail.com
Profile_pic NULL
Enrollment st/001
Table 3.4.7 Data Dictionary for Student table
• Chapter 3 Conclusion
In Chapter 3 System Design, we had done about user interface design, database design,
normalization and Entity Relationship Diagram.
Due to the user of library system is staff and admin staff, the interface does not need to
colorful but need to maintain the user friendliness. The interface designed is using system
default color. The button also designed in suitable size so that the interface won’t be
messy. Suitable control has been used to ensure users can easily using the library system.
One of the problems We meet in interface design is the report interface. We don’t know
how to design a common report which can be used by most of the library. With the aids
from my supervisor, We design one more form to let user key in the library detail. The
library detail will be used as report header. In this way, every library who used our library
system can print the report with different library details.
Next, We meet a big problem when doing normalization. This is because we have already
designed the database before doing the documentation. The database we designed is
actually a 3rd normalization form. Thus, we need to de-normalize the database back to 1st
normalization format. Besides that, We have forgotten how to do the normalization
because normalization is learning during Diploma level study. We find back the study
material for Database Management subject and refer how to normalize the database.
After completed this chapter, the lesson We learn is we must design a good user interface
for the system. It is because the system is used for ease human work. If the user interface
is not users friendly, user can’t enjoy the benefits of the system and they will not likely to
use the system. Thus, we must learn how to design a good user interface to bring the
maximize benefits to users.
Chapter 4
Programing
• Programming
This chapter will discuss about the programming coding of the Library Management
System. Different logic thinking and coding is required at development of the system. A
lot research has been done to enhance the efficiency when writing coding. Following
would discuss the sample programming coding of C#.
• Coding
Login Form:
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Threading;
using System.Windows.Forms;
using System.Data.SqlClient;
namespace Library_Management_System
{
public partial class Login_Form : Form
{
SqlConnection con = new SqlConnection(@"Data Source=.;Initial
Catalog=LMS;Integrated Security=True");
public Login_Form()
{
Thread trd = new Thread(new ThreadStart(strat_app));
trd.Start();
Thread.Sleep(5000);
InitializeComponent();
trd.Abort();
}
private void login_Click(object sender, EventArgs e)
{
con.Open();
SqlCommand cmd = new SqlCommand("select count(*) from admin_login where
username='" + username.Text + "' and password='" + password.Text + "'", con);
int temp = Convert.ToInt32(cmd.ExecuteScalar().ToString());
if (temp == 0)
{
MessageBox.Show("You have enter invalid username or password");
}
else
{
this.Hide();
mdi_admin ma = new mdi_admin();
ma.Show();
}
con.Close();
}
private void username_TextChanged(object sender, EventArgs e)

{
}
public void strat_app()
{
Application.Run(new loader());
}
}
}
Dshboard:
using System;
using System.Data;
using System.Linq;
using System.Text;
{
public partial class mdi_admin : Form
{
private int childFormNumber = 0;
public mdi_admin()
{
}
private void ShowNewForm(object sender, EventArgs e)

{
Form childForm = new Form();
childForm.MdiParent = this;
childForm.Text = "Window " + childFormNumber++;
childForm.Show();
}
private void OpenFile(object sender, EventArgs e)
{
OpenFileDialog openFileDialog = new OpenFileDialog();
openFileDialog.InitialDirectory =
Environment.GetFolderPath(Environment.SpecialFolder.Personal);
openFileDialog.Filter = "Text Files (*.txt)|*.txt|All Files (*.*)|*.*";
if (openFileDialog.ShowDialog(this) == DialogResult.OK)
{
string FileName = openFileDialog.FileName;
}
}
private void SaveAsToolStripMenuItem_Click(object sender, EventArgs e)

{
SaveFileDialog saveFileDialog = new SaveFileDialog();
saveFileDialog.InitialDirectory =
Environment.GetFolderPath(Environment.SpecialFolder.Personal);
saveFileDialog.Filter = "Text Files (*.txt)|*.txt|All Files (*.*)|*.*";
if (saveFileDialog.ShowDialog(this) == DialogResult.OK)
{
string FileName = saveFileDialog.FileName;
}
}
private void ExitToolsStripMenuItem_Click(object sender, EventArgs e)

{
this.Close();
}
private void CascadeToolStripMenuItem_Click(object sender, EventArgs e)

{
LayoutMdi(MdiLayout.Cascade);
}
private void TileVerticalToolStripMenuItem_Click(object sender, EventArgs e)

{
LayoutMdi(MdiLayout.TileVertical);
}
private void TileHorizontalToolStripMenuItem_Click(object sender, EventArgs e)
{
LayoutMdi(MdiLayout.TileHorizontal);
}
private void ArrangeIconsToolStripMenuItem_Click(object sender, EventArgs e)

{
LayoutMdi(MdiLayout.ArrangeIcons);
}
private void CloseAllToolStripMenuItem_Click(object sender, EventArgs e)

{
foreach (Form childForm in MdiChildren)
{
childForm.Close();
}
}
private void addNewBooksToolStripMenuItem_Click(object sender, EventArgs e)

{
Add_books ad = new Add_books();
ad.ShowDialog();
}
private void bookListsToolStripMenuItem_Click(object sender, EventArgs e)

{
view_book vb = new view_book();
vb.ShowDialog();
}
private void addStudentToolStripMenuItem_Click(object sender, EventArgs e)

{
add_student ads = new add_student();
ads.ShowDialog();
}
private void studentDetailToolStripMenuItem_Click(object sender, EventArgs e)

{
student_details sd = new student_details();
sd.ShowDialog();
}
private void issueBookToolStripMenuItem_Click(object sender, EventArgs e)

{
Issue_Book ib = new Issue_Book();
ib.ShowDialog();
}
private void showAllIssuedBooksToolStripMenuItem_Click(object sender, EventArgs

e)
{
List_of_issued_book loib = new List_of_issued_book();
loib.ShowDialog();
}
private void allReturnedBooksToolStripMenuItem_Click(object sender, EventArgs e)

{
return_books rb = new return_books();
rb.ShowDialog();
}
private void sendMailToolStripMenuItem_Click(object sender, EventArgs e)

{
send_mail sm = new send_mail();
sm.ShowDialog();
}
private void menuStrip_ItemClicked(object sender, ToolStripItemClickedEventArgs

e)
{
}
}
}
Add Books:
using System;
using System.Data;
using System.Linq;
using System.Text;
{
public partial class Add_books : Form
{
public Add_books()
{
}
private void button1_Click(object sender, EventArgs e)

{
con.Open();
SqlCommand cmd =
new SqlCommand("insert into add_books
(book_name,author_name,publication_name,purchase_date,book_qty,book_available) values ('"
+ textBox1.Text + "','" + textBox2.Text + "','" + textBox3.Text + "','" +
dateTimePicker1.Text + "'," + textBox5.Text + "," + textBox5.Text + ")", con);
cmd.ExecuteNonQuery();
MessageBox.Show("New Book Inserted Successfully");
textBox1.Focus();
con.Close();
textBox1.Text = "";
textBox2.Text = "";
textBox3.Text = "";
textBox5.Text = "";
}
}
}
View Books:
using System;
using System.Data;
using System.Linq;
using System.Text;
{
public partial class view_book : Form
{
public view_book()
{
}
private void view_book_Load(object sender, EventArgs e)

{
show_book_detail();
}
private void textBox1_KeyUp(object sender, KeyEventArgs e)

{
int i = 0;
try
{
con.Open();
SqlCommand cmd = new SqlCommand("select * from add_books where book_name
like ('%"+textBox1.Text+"%')", con);
DataTable dt = new DataTable();
SqlDataAdapter adp = new SqlDataAdapter(cmd);
adp.Fill(dt);
i = Convert.ToInt32(dt.Rows.Count.ToString());
dataGridView1.DataSource = dt;
con.Close();
if (i == 0)
{
MessageBox.Show("invalid book name");
}
}
catch (Exception ex)
{
MessageBox.Show(ex.Message);
}
}
private void panel2_Paint(object sender, PaintEventArgs e)

{

{
int i = 0;
try
{
con.Open();
SqlCommand cmd = new SqlCommand("select * from add_books where
author_name like ('%" + textBox2.Text + "%')", con);
adp.Fill(dt);
con.Close();
if (i == 0)
{
MessageBox.Show("invalid author name");
}
}
{
}
}
private void update_book_Click(object sender, EventArgs e)

{
int i;
i = Convert.ToInt32(dataGridView1.SelectedCells[0].Value.ToString());
try
{
con.Open();
SqlCommand cmd = new SqlCommand("update add_books set book_name='" +
bookname.Text + "',author_name='" + authorname.Text + "',publication_name='" +
publishername.Text + "',purchase_date='" + purchasedate.Text + "',book_qty='" +
quantity.Text + "' where id="+i+"", con);
con.Close();
MessageBox.Show("Record updated successfully");
panel3.Visible = false;
show_book_detail();
}
{
}
private void dataGridView1_CellClick(object sender, DataGridViewCellEventArgs e)

{
panel3.Visible = true;
int i;
try
{
con.Open();
SqlCommand cmd = new SqlCommand("select * from add_books where id="+i+"",
con);
adp.Fill(dt);
con.Close();
foreach (DataRow dr in dt.Rows)

{
bookname.Text = dr["book_name"].ToString();
authorname.Text = dr["author_name"].ToString();
publishername.Text = dr["publication_name"].ToString();
purchasedate.Text = dr["purchase_date"].ToString();
quantity.Text = dr["book_qty"].ToString();
}
}
{
}
}
public void show_book_detail()
{
con.Open();
SqlCommand cmd = new SqlCommand("select * from add_books", con);
adp.Fill(dt);
con.Close();
}
}
}
Issue Books:
using System;
using System.Data;
using System.Linq;
using System.Text;
{
public partial class Issue_Book : Form
{
public Issue_Book()
{
}

{
search_student();
}
public void search_student()

{
int i,j;
try
{
con.Open();
SqlCommand check_student_status = new SqlCommand("select * from
issue_book where student_enrollment='" + textBox1.Text + "' and return_date is null",
con);
SqlDataAdapter adp1 = new SqlDataAdapter(check_student_status);
DataTable dt1=new DataTable();
adp1.Fill(dt1);
j = Convert.ToInt32(dt1.Rows.Count.ToString());
if (j == 1)
{
MessageBox.Show("This student has not returned the previous book");
}
else
{
SqlCommand cmd = new SqlCommand("select * from add_student where
Enrollment='" + textBox1.Text + "'", con);
adp.Fill(dt);
if (i == 0)
{
MessageBox.Show("Invalid student's enrollment");
}
else
{
{
student_name.Text = dr["Name"].ToString();
student_roll.Text = dr["Roll"].ToString();
student_class.Text = dr["Class"].ToString();
stream.Text = dr["Stream"].ToString();
email.Text = dr["Email"].ToString();
student_enrollment.Text = dr["Enrollment"].ToString();
issue_date.Text = DateTime.Now.ToString();
}
}
}
con.Close();
}
{
}
}
private void Issue_Book_Load(object sender, EventArgs e)

{
}
private void issued_book_keyUp(object sender, KeyEventArgs e)

{
int count = 0;
if (e.KeyCode != Keys.Enter)
{
listBox1.Items.Clear();
SqlCommand cmd = new SqlCommand("select * from add_books where book_name
like ('%" + issued_book.Text + "%')", con);
adp.Fill(dt);
count = Convert.ToInt32(dt.Rows.Count.ToString());
if (count > 0)
{
listBox1.Visible = true;
{
listBox1.Items.Add(dr["book_name"].ToString());
}
}
}
}
private void issued_book_keyDown(object sender, KeyEventArgs e)

{
if (e.KeyCode == Keys.Down)
{
listBox1.Focus();
listBox1.SelectedIndex = 0;
}
}
private void listBox1_keyDown(object sender, KeyEventArgs e)

{
if (e.KeyCode == Keys.Enter)
{
issued_book.Text = listBox1.SelectedItem.ToString();
listBox1.Visible = false;
}
}
private void listBox1_MouseClick(object sender, MouseEventArgs e)

{
issued_book.Text = listBox1.SelectedItem.ToString();
listBox1.Visible = false;
}

{
try
{
con.Open();
SqlCommand search_availability = new SqlCommand("select
book_available from add_books where book_name='" + issued_book.Text + "'", con);
int check =
Convert.ToInt32(search_availability.ExecuteScalar().ToString());
con.Close();
if (check <= 0)
{
MessageBox.Show("Sorry,this book is out of stock now");
}
else
{
con.Open();
SqlCommand cmd = new SqlCommand("insert into issue_book
(student_name,student_roll,student_email,issue_date,Class,Stream,book_name,student_enroll
ment) values('" + student_name.Text + "','" + student_roll.Text + "','" + email.Text +
"','" + issue_date.Text + "','" + student_class.Text + "','" + stream.Text + "','" +
issued_book.Text + "','" + student_enrollment.Text + "')", con);
SqlCommand desc_availability = new SqlCommand("update add_books
set book_available=book_available-1 where book_name='" + issued_book.Text + "'", con);
desc_availability.ExecuteNonQuery();
con.Close();
MessageBox.Show("Book issued successfully");
student_name.Text = "";
student_roll.Text = "";
student_class.Text = "";
stream.Text = "";
email.Text = "";
issue_date.Text = "";
issued_book.Text = "";
textBox1.Text = "";
}
}
{
}
}
private void panel1_Paint(object sender, PaintEventArgs e)

{
private void label6_Click(object sender, EventArgs e)

{
private void stream_TextChanged(object sender, EventArgs e)

{
private void label5_Click(object sender, EventArgs e)

{
private void email_TextChanged(object sender, EventArgs e)

{
}
}
}
List Of Issued Books:
using System;
using System.Data;
using System.Linq;
using System.Text;
using System.Net;
using System.Net.Mail;
{
public partial class List_of_issued_book : Form
{
public List_of_issued_book()
{
}
private void List_of_issued_book_Load(object sender, EventArgs e)

{
show_issue_book();
}
private void enrollment_KeyUp(object sender, KeyEventArgs e)

{
try
{
con.Open();
SqlCommand cmd = new SqlCommand("select * from issue_book where
student_enrollment like('%" + enrollment.Text + "%')", con);
adp.Fill(dt);
con.Close();
}
{
}
}

{
int i = Convert.ToInt32(dataGridView1.SelectedCells[0].Value.ToString());
try
{
con.Open();
SqlCommand cmd = new SqlCommand("select * from issue_book where id='" + i
+ "'", con);
adp.Fill(dt);

{
student_enroll.Text = dr["student_enrollment"].ToString();
book_name.Text = dr["book_name"].ToString();
return_date.Text = DateTime.Now.ToString();
}
con.Close();
}
{
}
}

{
try
{
con.Open();
SqlCommand cmd = new SqlCommand("update issue_book set return_date='" +
return_date.Text + "' where student_enrollment='" + student_enroll.Text + "' and
book_name='" + book_name.Text + "'", con);
SqlCommand increase_book_availability = new SqlCommand("update add_books
set book_available=book_available+1 where book_name='" + book_name.Text + "'", con);
increase_book_availability.ExecuteNonQuery();
con.Close();
//send_mail();
MessageBox.Show("Book return successfully");
show_issue_book();
}
{
}
}
public void show_issue_book()
{
try
{
con.Open();

return_date is null", con);
adp.Fill(dt);
con.Close();
}
{
}
}
public void send_mail()
{
try
{
MailMessage msg = new MailMessage();

msg.From = new MailAddress("sayansanu30@gmail.com");
msg.To.Add("sayansanu30@gmail.com");
msg.Subject = "test sending mail";
msg.Body = "return successfully";
SmtpClient smt = new SmtpClient();

smt.Host = "smtp.gmail.com";
System.Net.NetworkCredential ntcd = new NetworkCredential();
ntcd.UserName = "sayansanu30@gmail.com";
ntcd.Password = "susmitasen";
smt.Credentials = ntcd;
smt.EnableSsl = true;
smt.Port = 587;
smt.Send(msg);
MessageBox.Show("Your Mail is sended");
}
{
}
}
}
}
Return Books:
using System;
using System.Data;
using System.Linq;
using System.Text;
{
public partial class return_books : Form
{
public return_books()
{
}
private void return_books_Load(object sender, EventArgs e)

{
show_returned_books();
}
public void show_returned_books()
{
try
{
con.Open();
return_date is not null", con);
adp.Fill(dt);
con.Close();
}
{
}
}

{
try
{
con.Open();
student_enrollment like('%" + textBox1.Text + "%')", con);
adp.Fill(dt);
con.Close();
}
{
}
}
}
}
Add Students:
using System;
using System.Data;
using System.Linq;
using System.Text;
using System.Drawing.Imaging;
using System.IO;
{
public partial class add_student : Form
{
MemoryStream ms;
byte[] photo_aray;
SqlCommand cmd;
public add_student()
{
}

{
string imglocation;
try
{
OpenFileDialog dialog = new OpenFileDialog();
dialog.Filter = "jpg files(*.jpg)|*.jpg|PNG files(*.png)|*.png|All
files(*.*)|*.*";
if (dialog.ShowDialog() == DialogResult.OK)
{
imglocation = dialog.FileName.ToString();
pictureBox1.ImageLocation = imglocation;
}
}
catch (Exception)
{
MessageBox.Show("An error occured", "Error", MessageBoxButtons.OK,
MessageBoxIcon.Error);
}

{
con.Open();
SqlCommand cmd = new SqlCommand("insert into add_student
(Name,Roll,Address,Contact,Class,Stream,Email,Enrollment) values ('" + textBox1.Text +
"','" + textBox2.Text + "','" + textBox3.Text + "','" + textBox4.Text + "','" +
textBox8.Text + "','" + textBox9.Text + "','" + textBox5.Text + "','" + textBox6.Text +
"')", con);
con.Close();
MessageBox.Show("Student added successfully");
textBox1.Text = "";
textBox2.Text = "";
textBox3.Text = "";
textBox4.Text = "";
textBox8.Text = "";
textBox9.Text = "";
}
}
}
}
Student Details:
using System;
using System.Data;
using System.Linq;
using System.Text;
{
public partial class student_details : Form
{
public student_details()
{
}
private void dataGridView1_CellContentClick(object sender,

DataGridViewCellEventArgs e)
{
private void student_details_Load(object sender, EventArgs e)

{
show_student();
}

{
int i;
try
{
con.Open();

Enrollment like ('%" + textBox1.Text + "%')", con);
DataTable dt=new DataTable();
adp.Fill(dt);
con.Close();
if (i == 0)
{
MessageBox.Show("Invalid Name");
}
}
catch(Exception ex)
{
}
}

{
int i;
try
{
con.Open();
SqlCommand cmd = new SqlCommand("update add_student set
Name='"+textBox3.Text+"',Roll='"+textBox4.Text+"',Address='"+textBox5.Text+"',Contact='"+
textBox6.Text+"',Class='"+textBox7.Text+"',Stream='"+textBox8.Text+"' where id='"+i+"'",
con);
MessageBox.Show("Record updated successfully");
con.Close();
show_student();
}
catch(Exception ex)
{
}
}
public void show_student()
{
try
{
con.Open();
SqlCommand cmd = new SqlCommand("select * from add_student", con);
adp.Fill(dt);
con.Close();
}
{
}
}

{
try
{
con.Open();

id='"+i+"'", con);
adp.Fill(dt);
con.Close();
{
textBox3.Text = dr["Name"].ToString();
textBox4.Text = dr["Roll"].ToString();
textBox5.Text = dr["Address"].ToString();
textBox6.Text = dr["Contact"].ToString();
textBox7.Text = dr["Class"].ToString();
textBox8.Text = dr["Stream"].ToString();
}
}
{
}
}

{
try
{
con.Open();
SqlCommand cmd = new SqlCommand("delete from add_student where id='" + i
+ "'",con);
con.Close();
MessageBox.Show("Record deleted successfully");
show_student();
}
catch(Exception ex)
{
}
}
}
}
• Chapter 4 conclusion
Chapter 4 is programming chapter which include the important coding used in the
system. By referring to the chapter 4, user can roughly know how the system process.
In programming stages, the problem We faced is to write some coding which We never
learn before such as DrawString and DrawImage. These two methods are used to print
out the string or an image. When We try to do the print member card module, We search
Google for the Drawstring and DrawImage method to produce the member card. The
coding include a lot of X and Y-axis to defined the location of the string.
After few hours on research, finally We can generate the member card with the desirable
outlook.
The lesson We learnt in this chapter is the most difficult part of programming is not
coding but logic. Each business has their owns business logic and business flow process.
We need to have clear understanding of how an organization works to create a system
which desirable for them. Besides that, whenever we meet some coding difficulties, we
can always seek help from Google. From this project, We knew that every coding have
the sample or solution on the web. We should not keep complain that the coding is
difficult but we should improve our knowledge on the logic business process.
Chapter 5
System
Testing
• System Testing
This chapter will show the test plan which programmer used to test the system.
System Testing is an important phase in SDLC to ensure the system is bug free. If
the system hasn’t been test properly, user will meet a lot problem when using the
system.
• Test Plan
Tester Name : Rintu

Module Name : login
UserName: Rintu Password 12345
Expected Result:
Invalid User Name

Comments from Supervisor / Moderator : none
Tester Name : Rintu

Module Name : login module
UserName: Admin Password 111
Expected Result:
Invalid Password
Tester Name : Rintu

Module Name : login module
UserName: Admin Password 1234
Expected Result:
Success login to system

If library detail is nothing, user are prompt to insert library detail
• Chapter 5 Conclusion
System testing phase made us understand the important of bug free system. If one system
contains bugs, users will be frustrated and meet some problems. Computerized system
should be creating to help user reduce the work so it is very importance so ensure the
system is bug free.
In system testing, the problem We meet is time limitation. After complete the system, We
only left few day due to wasting too much time at earlier stages. With the helps of my
friend, We done the module test and debug on it.
Chapter 6
Conclusion
• Conclusion
• Introduction
In this final chapter, the final evaluation and conclusion will be performed on the testing
and analyzing process that done in previous chapter including seminar linkage, strengths,
weakness and future enhancement of the Library Management System. In addition,
personal reflection also include in final part of this chapter.
• Evaluation of Project Objectives

Objectives Function / Module Status
Eliminate paper work Book Transaction Achieved
Module
To eliminate record Book Maintenance Achieved
missing problem Module

Table 6.1 Table of Evaluation Project Objectives
• Project Management Issues
During the development process of Library Management system, there are a lot issues
encountered. Firstly, We don’t have much knowledge about how library process the book
transaction and the business logic in the library. Thus, a lot research has been done to
refer and to get more understanding about the library management.
For the coding part, We meet some problem in bar code generator. That is because We
can’t found the bar code font. We have found few types of bar code font such as EAN 13.
Although it looks like a standard bar code, but my bar code scanner is still fail to scan it.
And finally with the help of my friend We successfully found the font which is
IDAutomationHC39M.
Besides the bar code font issue, We have met some problem regarding the member id
generator module. In that module, We need to print out the member details such as name,
id and also photo. In this case, We never learn how to print the detail in A4 size paper.
With the help of Google and my friend, finally We know the method to use is DrawString
and DrawImage.
On the other hand, We met problem of constructing the DFD and ERD due to the less
understanding of the diagram such as entity and relationship. With the help of Diploma
studies materials, finally We successful construct the ERD and DFD diagrams.
Finally, the biggest problem We met is the documentation format. Although We have
been provided with the document guidelines, but the instruction and guide is too much to
follow especially the Reference part.
• Evaluation of Projects Strengths and Weaknesses
Strengths
• System response is fast after user press a button to perform some actions.
• User interface is considered user friendly and ease of use.
• Validation has been done to avoid some functional error in later time.
• Some listview control has been included to allow user view the history or
some important data without print out the report.
Weakness
• The reservation that make by member online unable to update the database
immediately.
• The member id generated is in A4 format. Not in proper Member card size.
• System didn’t implement smart card technology.
• Suggestion for Future Enhancement

For future enhancement, there are few suggestions to improve the system abilities.
Firstly, the library system should implement smart card technology which will log in the
member by scanning the smart card. The smart card can act as a unique identifier of a
member. The smart card technology is more advanced and is able to store all the
information inside the chips. By implements this, the book transaction process will be
enhanced and save time.
Chapter 7
References
Appendix We : Project Specification
• Company Background
This system is developed for common library. We created the system which suits small
size library. Most of the function we refer to other library system.
• Project Objectives
The purpose we creating this project are to let common library have an electronic library
management system. A lot small size library was using paper-based management system.
But followed by the increase of visitors and member, librarian was suffered because there
are a lot of records. When need to search for particular member record, the librarian need
a lot of time.
In addition, they are suffered from a lot paper-based problem such as lost of member’s
record. Some record was missing because they failed to take good care of it. For example,
the librarians forget to put back the record into cupboard when they are busy.
Since my last visit to that library, We found that they need a computer management
system so We think of this idea to developing a system for small size library. This is to
avoid some paper-based problem such as lost of record and etc.
Appendix II : User Manual
• Login Page
Purpose : To provide authentication and authorization for
user. User : All users
Figure 1.1 Print Screens for Login Form
Section 1 is the textbox to enter the user id. User ID is unique for each user.
Authorization is controlled based on this user ID. If the login ID is admin
user, the user will be loaded into the system with admin control.
Section 2 is a label which will pop up when user focus on password textbox.
If user forgets their password, they can press the control. Email will be sent to
user’s registered email address.
Section 3 is the login button which performs authentication checking. Only
the authenticated users are allow to login to the Library System.
• Login Form
Purpose: To perform book transaction module and act as a main form of Library
System. User : Normal User
Main Form:
Figure 2.1 Print Screen for Main Form
Section 6 shows the renting history and current renting status of the logged
in user.
• Book Add
Figure 3.1 Add Books
Book Lists:
.
Issue Book:
Add Stusents:
Stusent List:
THANK YOU

Library Management System: Asutosh College

Uploaded by

Copyright:

Available Formats

Library Management System: Asutosh College

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Library Management System: Asutosh College

Uploaded by

Copyright:

Available Formats

LIBRARY MANAGEMENT SYSTEM

Rintu Mondal, Sayan Sen, Debasish Kayal,

Supervisor: Mr. Rishi Bhattacharya

Chapter 1 :................................... System Planning.

Chapter 2:.................................... Require Analysis.

Chapter 3:.................................... System Design.

Chapter 5: ....................................System Testing.

Chapter 7:.................................... Reference.

• Project Aims and Objectives

Authorization and Authentication

• Book Maintenance Module

• Outline of approach / Methodology used

Operating system: Window 10

Development tools and programming language: Microsoft Visual Studio 2010

• Software Requirement Specification (SRS)

• Difficult to search record

• Difficult to view reports

Stimulus / Response Sequences

• The system must be able to perform authorization process which

• Register New book

Stimulus / Response Sequences

Stimulus / Response Sequences

2.2.1 Context Diagram

Figure 1.3 Context Diagram for Library Management System

Library Management System : Requirement Analysis

Figure 1.4 Level 0 DFD diagram for Library Management

2.2.3 Level 1DFD (Lower – Level Diagram)

Figure 1.5 Level 1 DFD for Member Registration Module

2.3 Chapter 2 Conclusion

Library Management System is used by librarian and admin so it just simply

Library Management System (application used by librarian)

• Book Maintenance Form

• Publisher Maintenance Form

• Book Transaction Report (Rental / Return)

• Library Detail Form

• Entity Relationship Diagram (ERD)

Table Name: Admin

Field Example Data

Table Name: Book

Field Example Data

Field Example Data

Table 3.4.7 Data Dictionary for Student table

private void username_TextChanged(object sender, EventArgs e)

private void ShowNewForm(object sender, EventArgs e)

private void SaveAsToolStripMenuItem_Click(object sender, EventArgs e)

private void ExitToolsStripMenuItem_Click(object sender, EventArgs e)

private void CascadeToolStripMenuItem_Click(object sender, EventArgs e)

private void TileVerticalToolStripMenuItem_Click(object sender, EventArgs e)

private void ArrangeIconsToolStripMenuItem_Click(object sender, EventArgs e)

private void CloseAllToolStripMenuItem_Click(object sender, EventArgs e)

private void addNewBooksToolStripMenuItem_Click(object sender, EventArgs e)

private void bookListsToolStripMenuItem_Click(object sender, EventArgs e)

private void addStudentToolStripMenuItem_Click(object sender, EventArgs e)

private void studentDetailToolStripMenuItem_Click(object sender, EventArgs e)

private void issueBookToolStripMenuItem_Click(object sender, EventArgs e)

private void showAllIssuedBooksToolStripMenuItem_Click(object sender, EventArgs

private void allReturnedBooksToolStripMenuItem_Click(object sender, EventArgs e)

private void sendMailToolStripMenuItem_Click(object sender, EventArgs e)

private void menuStrip_ItemClicked(object sender, ToolStripItemClickedEventArgs