Professional Documents
Culture Documents
College Library Management
College Library Management
net/publication/274311464
CITATIONS READS
0 83,204
3 authors, including:
Avijit Mathur
Intel
24 PUBLICATIONS 128 CITATIONS
SEE PROFILE
Some of the authors of this publication are also working on these related projects:
All content following this page was uploaded by Avijit Mathur on 17 June 2019.
Project Overview
This year the summer training project titled ‘College Library Management’ is a vast
one with the usage of numerous resources and popular software like the Microsoft
Visual Studio 2008 and SQL server management to build a website for the easiness of
the library staff.
The project’s main aim is to build a management system more like a website which
Not up-to-date
Requires management
Has its components value very high in the education department
That’s when I came up with a plan to create a website ‘College Library Management’
by doing an internship in Rhydo technologies, where I learned
Visual C#
Using Microsoft Visual Studio
Using SQL server management
1
Embedding graphic CSS templates in my website
Various dynamics of creating web pages and connecting them in order to get a
website
Before going into any details I would like to explain exactly what this website does
and why is it important
Views
Functionality
Purpose
The following web pages constitute the ‘College Library Management’ website
Main Page
o Consisting of the WELCOME and REGISTRAION columns
Login Page
o Includes an interface to Login both for users and administrator
o A forgot password facility
Admin Page
o Includes links to other pages: ‘Add Books’, ‘Remove Books’,
‘Manage Users’
2
o Has a welcome page with profile options
o A Log out tab
User Page
o Includes links to other pages: ‘Issue Books’, ‘Account’, ‘Return
Books’
o And a welcome page with profile options
o A Log out tab
o
All these pages are interlinked using Microsoft visual studio 2008 and the coding
which it uses is that of C#. The data is held in databases managed by the SQL server
management 2005 which gives the facility to connect the database to the website so
that the data can be viewed, updated or removed as required.
Product Functions
The College Library System provides College real time information about the books
available in the Library and the user information. The functions of the system include
the system providing different type of services based on the type of users
[Member/Admin].
3
The admin is provided with interfaces to add/delete the books
available in the book catalog.
User characteristics
The users of the system are members and the administrator who maintains the system.
The member is assumed to have basic knowledge of the computers and Internet
browsing. The administrator of the system has more knowledge of the internals of the
system and is able to rectify the small problems that may arise due to disk crashes,
power failures and other catastrophes to maintain the system. The proper user
interface, user’s manual, College help and the guide to install and maintain the system
must be sufficient to educate the users on how to use the system without any
problems.
Constraints
4
Document Conventions
The following are the list of conventions and acronyms used in this document and the
project as well:
ASP: Active Server Pages: A Web Page formatted on the server and delivered to the
browser.
User Interface Layer: The section of the assignment referring to what the user
interacts with directly.
Application Logic Layer: The section of the assignment referring to the Web
Server. This is where all computations are completed.
Data Storage Layer: The section of the assignment referring to where all data is
recorded.
Use Case: A broad level diagram of the project showing a basic overview
5
FEASIBILITY STUDY
Feasibility study:
In order to make sure that the project is feasible, following feasibility studies have
been conducted: -
It is possible to develop the system using simple platform. All the functions of a
project for communication can be implemented in the new system. Hence the system
is technically feasible.
Since the project needs no copyright, patenting, and doesn’t intent to have any
relation with anybody else’s intellectual property rights, it can be considered as a
legally feasible project.
As it has been more probable (as per the requirements, functions, and performance
specifications of the system) that the project can be completed within the given time
6
frame, it is considered that the undertaking this project is feasible in the context of
time.
Project planning:
During Planning all the activities that are to be performed to create the system are
planned. Following are some of the issues that are well devised so that proper
monitoring and controlling of the project could be easily done: -
Project development:
To avoid being stuck in dilemma during the development of project, one need to be
sure that the process model he’s using is right for the project. Since all the
requirements about the problem can’t be easily understood and may not be stable
during the development of the system.
Quality Planning:
To ensure that the final software for-“College library management system” is of high
quality, some quality control activities should be decided /planned in advance to
perform them throughout the development of the software.
Following is a list of quality control activities that are used to identify and remove
defects from the software, hence making it a high quality controlled system: -
Requirements Review
Design Reviews
Code Reviews
Testing
7
Risk control planning:
A risk is a probabilistic event – it may or may not occur. The aim of risk control
planning is to minimize the impact of risks (if they occur) in the project.
Following are some known risks that might occur and their mitigation plan: -
Unclear project requirements ~> Keep in touch with the faculty in charge.
Data loss ~> Use CD’s and/or pen drives to have some extra backups of the data.
Project delays ~> Use proper scheduling of the project as soon as possible so that the
project could be completed.
It has been taken into account that there are some functions in project that are
indispensable .And these should not be excluded from project .Such functions
/modules are like login, Sign up, admin add, admin remove, add user, remove user. So
there are at least a minimum number of modules that have to be there in project.
Project scheduling:
During early stages of project planning, a kind of macroscopic schedule was already
planned which gave a rough idea about activities that should be carried out for
developing the project .In project scheduling , those sets of activities are refined into a
detailed schedule.
8
OVERALL DESCRIPTION
Product Perspective:
College library management system is a product which does not intent to have any
relation with any other product. It is a complete system in itself. It is an exclusive
product which is to be concerned with the optimization.
Product Features: The project mainly use the concepts of .Net, simple tools of
programming and SQL server for database storage
There are number of functions that the system/product is supposed to perform which
is as follows: -
Issue books
Remove books
Admin login
User login
Add books
Welcome page
New user
The user of this product need not be computer expert. Even a naïve user can also
operate the system. The user interfaces are to be made so simple that anybody can be
comfortable in working with the system in just a few minutes. The basic things which
are required in a user are:
9
Operating Environment:
Only that person can operate the system’s who knows the ID and Password
of the valid user of the system.
In case admin does not remembers his/her ID/Password then system won’t
consider him/her as a valid user for College library management system.
10
PERFORMANCE REQUIREMENT
Static Requirements:
Project College library management system is to support many users at a time. All
necessary operations shall have been carried out with the help of many clients and a
server.
Dynamic Requirements:
All the information should be stored in separate databases. These databases should be
categorized and maintained in a logical manner. For example:-
Design Constraints
.NET will have to be operated on Windows XP, VISTA, or 7. It will require at least
512MB of RAM, and few Megabytes of Hard Disk. As the security feature included
in the system, no one except the administrator and member can access the system.
11
SOFTWARE SYSTEM ATTRIBUTES
Following are some of the basic attributes that the project should have:-
Reliability: - The system should be reliable in the sense that there should be no room
for mistakes. Every activity/ function of project should be indefectible.
Security: - The system is to be secure in the sense that nobody except the
authenticated users can login and use the system.
Portability: - The project should be made such that there are as less operating system
dependencies as possible, or the software should be portable with only few
modifications.
Maintainability: - The system should be maintainable in the sense that if any error
occurs, it should be easily rectified and the cost incurred in maintenance should be as
low as possible.
There are some requirements of the system that are indispensable while the others are
lesser. Following is the organization of specific requirements in descending order of
their importance: -
12
Description
Criticality
This issue is essential to the overall system. All the modules provided with the
software must fit into this graphical user interface and accomplish to the standard
defined.
Technical issues
In order to satisfy this requirement the design should be simple and all the different
interfaces should follow a standard template. There will be the possibility of changing
colors and images, plus switching between interfaces with the minimum impact for
the users.
Risks
To reduce the circumstances under which this requirement might not able to be
satisfied, all the designers must have been developed web sites previously and they
must be aware of html restriction and cross browsers implementations before starting
the designing. In order to reduce the probability of this occurrence the entire design
team will be trained in basic html development and macromedia fireworks, this tool
will be used instead of Photoshop.
13
METHODOLOGY ADOPATED
To make sure that the project ‘College library management system faces no
probabilities of being disorganized, unsystematic, and/ or having undesirable
consequences, a clear perspective has been defined by consenting to use a model for
this project. The model that is chosen is called ‘Spiral Model’.
1. Communication Phase
2. Planning Phase
3. Modeling Phase
4. Construction Phase
5. Deployment Phase
The project has been following this methodology because all the requirements about
the problem can’t be easily understood and may not be stable.
14
Representation of Spiral Model
15
Communication Phase: -
Before the requirements can be analyzed, modeled, or specified they must be gathered
through a communication activity.
Under this phase, all kinds of information have been gathered to successfully make
the project of the desired specifications.
It includes: -
On-site Observations.
Informal Meetings
Personal discussions
Reviews of Information Domains
o Admin Report
o User Report
Planning Phase: -
The planning activity encompasses a set of management and technical practices that
enable the software team to define a road map as it travels toward its strategic goal
and tactical objectives. It includes the issues like: -
16
Modeling Phase: -
Construction Phase: -
The construction activity encompasses a set of coding and testing tasks that lead to
operational software that is ready for delivery to the customer or end-user.
Coding
o The Creation of Programs/Database Using codes and Statements in C#
and SQL.
Testing
o After The Programs Get Created, They Are Tested With The Intent Of
Finding Any Error That Was Left Undetected During the Coding
Phase. The Basic Tests That Have Been Done Are: -
Unit Testing
Integration Testing
System testing
Alpha Testing
Beta Testing
Acceptance Testing
Deployment Phase: -
17
HARDWARE DETAILS
A hard disk is part of a unit, often called a “disk drive”, “hard drive”, or “hard disk
drive”, that stores and provides relatively quick access to large amounts of data on an
electromagnetically charged surface or a set of surfaces. A hard disk is really a set of
stacked “disks”, each of which, like phonograph records, has data recorded electro-
magnetically in concentric circles or “tracks” on the disk. A “head” writes or reads the
information on the tracks. Two heads, one on each side of a disk, read or write the
data as the disk spins. A hard disk/drive unit comes with a set rotation speed varying
from 4500 to 7200 the physical location can be identified with the cylinder, track, and
sector locations, these are actually mapped to a Logical Block Address (LBA) that
works with the larger address range on today’s hard disks.
When people talk about computer memory, they usually mean the volatile RAM
memory. Physically, this memory consists of some integrated circuit
Chips (IC chips) either on the motherboard or on a small circuit board attached to the
motherboard. A computer’s motherboard is designed in a manner that its memory
capacity can be enhanced by adding more memory chips. Hence, if you decide to have
18
more memory than your computer currently has, you can buy more memory chips,
and plug them in the empty memory slots on the motherboard. This job is normally
done by the service engineers.
Monitor: LCD
A liquid crystal display (LCD) is a flat panel display, electronic visual display, or
video display that uses the light modulating properties of liquid crystals (LCs). LCs
do not emit light directly.
Keyboard: Multimedia
The multimedia keyboard is a kind of keyboard that gives you a superior level of
desktop freedom to work anywhere, on almost any surface. The Multimedia Keyboard
provides complete workspace freedom. Easily navigate to the web, check your email,
control your audio or access documents with the touch of a button on the multimedia
keyboard. It features time saving multimedia and internet shortcut buttons including
back, forward, stop, refresh, web and search buttons for the internet as well as play
controls, volume controls on Windows operating systems. The multimedia keyboard
is compatible with almost all PC models
Mouse: Optical
19
SOFTWARE DETAILS
Microsoft Corporation
Releases
Succeeded by Windows 8
20
Front End: - ASP.NET 2.0 with C#
As such, it needs to control concurrent access to shared data, to ensure integrity- when
multiple clients update the same data, or clients attempt to read that is in the process
of being changed by another client.
21
COST & BENEFITS ANALYSIS
COST
1. Hardware Cost
a. Computer purchase
2. Facility Cost
a. Proper lightning.
b. Air Conditioning
3. Operating Cost
a. Consumption of electricity
4. Supply Cost
22
BENEFITS
1. Improved performance
a. Accuracy improvement.
b. Time Saving.
2. Decreased Supply cost
a. No use of registers.
3. Decreased personnel cost
a. Fewer staff.
b. Fewer payments.
Most of the costs that have been incurred in developing the system are onetime costs.
While all the benefits that we would get are not for one time only, they shall be
obtained on a regular basis. In this way, benefits will exceed costs by a substantial
margin, hence this project can be considered as cost effective.
23
DETIALED LIFECYCLE OF PROJECT
The term “PROJECT LIFE CYCLE” refers to a sequence of pre-planned stages for
taking a project from beginning to the end.
Just like any other project, this project also has a lifecycle which is broadly
categorized into following five stages, viz.:
Conceptualization
Determining the need for developing Website for Multiplex theatres and conducting
Technical, Economical, Legal, Operational, and social/Behavioral Feasibility Studies
for the project.
Definition /Planning
Defining the operations, Performance Parameters, And Planning for costs, schedules,
and programming tools.
Design
Designing the data structure, database architecture and User Interface for the
software.
Implementation
Implementing the system at the user end and getting feedback for the same. making
subtle Modifications In The System(If necessary).
Conversion
Modifications at the higher level will be done in future if is required so. (E.g.
Modifications could be to introduce new modules into the system).
24
PROCESS INVOLVED
The various processes involved in making the software successfully running and
documenting the project are as follows: -
Preliminary Investigation
System Requirement
o Gathering the information about the need to build the project
System Design
o Designing Data Flow Diagrams (DFD’s), data dictionary,
databases schemas, user interfaces.
System Development
o Developing Databases, Creating Forms, Coding of software, and
integrating the components.
System Testing
o Testing Individual Units of the software as and when they are
created.
o Testing the integration of units of the software.
o Testing the whole functioning of the software.
o Testing the software at the developer’s end.
o Testing informally the software with general people.
o Testing the software at the client’s end.
25
Implementation
o Installing the software at the user’s side. Direct conversion
approach has been taken.
o Getting feedback from the user.
26
DRAWBACKS OF PRESENT SYSTEM
Automated System
27
DATA FLOW DIAGRAM
28
ER DIAGRAM
29
SOFTWARE REQUIREMENTS SPECIFICATION
Purpose
The main objective of this document is to illustrate the requirements of the Library
Management system. The document gives the detailed description of both functional
and non functional requirements proposed. It describes the external behavior of the
College Library System. Requirements Specification defines and describes the
operations, interfaces, performance, and quality assurance requirements of the College
Library System. The document also describes the nonfunctional requirements such as
the user interfaces. It also describes the design constraints that are to be considered
when the system is to be designed, and other factors necessary to provide a complete
and comprehensive description of the requirements for the software. The Software
Requirements Specification (SRS) captures the complete software requirements for
the system, or a portion of the system.
Scope
The product provides the members with College adding and removal of
books capabilities
The system provides logon facility to the users.
The system provides the members with the option to check their
account and/or change their options like password and profile picture
of the account whenever needed all through the day during the library
hours.
30
The system lets the administrator to check which all members have
borrowed which all books
The system allows the Librarian to create the books catalog, add/delete
books and maintain the books catalog.
The system updates the system as and when the member borrows or
returns a book.
The features that are described in this document are used in the future phases
of the software development cycle. The features described here meet the needs
of all the users. The success criterion for the system is based in the level up to
which the features described in this document are implemented in the system.
Specific Requirements
This section describes in detail all the functional requirements.
Functionality
Logon Capabilities
The system shall provide the users with logon capabilities.
Catalog
Usability
The system shall allow the users to access the system from a browser using
HTML or it’s derivative technologies.
Since all users are familiar with the general usage of browsers, no specific
training is required.
The system is user friendly and self-explanatory.
31
Reliability
The system has to be very reliable due to the importance of data and the
damages incorrect or incomplete data can do.
Availability
The system is available 100% for the user and is used 24 hrs a day and 365
days a year. The system shall be operational 24 hours a day and 7 days a week.
Even if the system fails, the system will be recovered back up within an hour
or less.
Accuracy
The accuracy of the system is limited by the accuracy of the speed at which
the employees of the library and users of the library use the system.
Not specified.
Access Reliability
The system shall provide 100% access reliability.
Performance
Response Time
The Information page should be able to be downloaded within a minute. The
system shall respond to the member in not less than two seconds from the time
of the request submittal. The system shall be allowed to take more time when
doing large processing jobs.
Administrator/Librarian Response
The system shall take as less time as possible to provide service to the
administrator or the librarian.
32
Throughput
Capacity
The system is capable of handling many users.
Resource Utilization
The resources are modified according the user requirements and also
according to the books requested by the users.
33
WEBSITE CONTENTS
Home Page
34
Login Page
35
User Welcome Page
Links and tabs for easy access of certain features for users
Name of the user in orange color
36
Issue Books Section
37
Account Section
38
Return Books Section
39
Admin Welcome Page
40
Add Books Section (admin)
41
Remove Books Section
42
Manage Users (admin)
43
WORKING
CLASS
A class has been created for ease of use in the following pages to come.
/// <summary>
/// Summary description for Class1
/// </summary>
public class lib
{
public lib()
{
44
con.Close();
}
con.Open();
return con;
}
cmd.CommandType = CommandType.Text;
cmd.CommandText = cmdtext;
cmd.ExecuteNonQuery();
return "1";
}
45
cmd.CommandType = CommandType.StoredProcedure;
cmd.CommandText = procname;
cmd.ExecuteNonQuery();
return "1";
}
cmd.CommandType = CommandType.Text;
cmd.CommandText = fetchcmd;
ad.SelectCommand = cmd;
dt = new DataTable();
ad.Fill(dt);
return dt;
}
}
46
HOME PAGE WORKING
Master Page
Content Page
The master page allows a consistent layout for the web page to be integrated into the
website making it easier to safeguard the main layout without accidently editing it
along with the contents that one needs to display.
A master page is an ASP.NET file with the extension .master (for example,
library.master) with a predefined layout that can include static text, HTML elements,
and server controls. The master page is identified by a special @Master directive that
replaces the @Page directive that is used for ordinary .aspx pages. The directive looks
like the following.
The content page is used to display the content that the programmer wants the user to
usually interact with or manipulate accordingly.
You define the content for the master page's placeholder controls by creating
individual content pages, which are ASP.NET pages (.aspx files and, optionally, code-
behind files) that are bound to a specific master page. The binding is established in the
content page's @ Page directive by including a MasterPageFile attribute that points to
the master page to be used. For example, a content page might have the
following @ Page directive, which binds it to the library.master page.
47
Process:
<li><a href="reg.aspx">Home</a></li>
<li class="selected"><a href="login1.aspx">Sign In</a></li>
In the content page text fields, labels and buttons were added in this fashion
FIG 1
Use of validators
48
I. Required field validator (the red *): Used to check whether a field is non-
empty. The ControlToValidate property is set to the textfield to be checked.
II. Compare Validator (the ‘passwords don’t match’): Used to compare two pre
specified fields and give a pre set result.The ControlToValidate property is
used to set the first textfield and the ControlToCompare is used to set to the
field to which the value is to be compared. Type property is used to set the
type of the values to be compared (in this case: string).
III. Regular Expression Validator( the ‘invalid email’): The ControlToValidate
property is set to the textfield to be checked. The ValidationExpression
property is set to the desired type of expression (‘Internet e-mail address’ in
this case) and the ErrorMessage property to display the string.
obj.cmd.Parameters.AddWithValue("@uname", uname.Text);
obj.cmd.Parameters.AddWithValue("@pwd", pwd.Text);
obj.cmd.Parameters.AddWithValue("@email", email.Text);
obj.cmd.Parameters.AddWithValue("@question", question.Text);
obj.cmd.Parameters.AddWithValue("@answer", answer.Text);
string s = obj.excproc("register");
49
if (s == "1")
{
Response.Redirect("login1.aspx");
}
else
{
Response.Write("Failure");
}
}
}
}
<div id="menubar">
<ul id="menu">
<!-- class="selected" is put in the li tag for the selected page - to highlight
which page you're on -->
<li class="selected"><a href="reg.aspx">Home</a></li>
<li><a href="login1.aspx">Sign In</a></li>
</ul>
</div>
50
LOGIN PAGE WORKING
if (TextBox1.Text == "Administrator")
{
obj.gettable("select pwd from admin1 where pwd = '" + TextBox2.Text + "' ");
if (obj.dt.Rows.Count > 0)
{
Session["Name"] = "Administrator";
Response.Redirect("welcome_admin.aspx");
}
else
{
Label4.Visible = true;
Label4.Text = "Unauthorized Access";
}
}
else
{
obj.gettable("select uname, pwd from avi where uname = '" + TextBox1.Text
+ "' and pwd = '" + TextBox2.Text + "'");
if (obj.dt.Rows.Count > 0)
{
51
Session["Name"] = obj.dt.Rows[0][0].ToString();
Response.Redirect("welcome.aspx");
}
else
{
Label4.Visible = true;
Label4.Text = "Invalid Username / Password";
}
}
}
protected void Button2_Click(object sender, EventArgs e)
{
MailMessage mail = new MailMessage();
obj.gettable("select email, pwd from avi where uname = '" + TextBox1.Text + "'
");
mail.To.Add(obj.dt.Rows[0][0].ToString());
mail.From = new MailAddress("aviiandevil@gmail.com");
mail.Subject = "Password Recovery";
mail.Body = obj.dt.Rows[0][1].ToString();
mail.IsBodyHtml = true;
52
}
protected void admin_Click(object sender, EventArgs e)
{
TextBox1.Text = "Administrator";
}
53
ISSUE BOOKS WORKING
TextBox2.Visible = true;
obj.gettable("select * from account where uname = '" + Label4.Text + "' and bid
= " + TextBox1.Text + " ");
if(obj.dt.Rows.Count > 0)
{
TextBox2.Text = "You cannot Issue a copy of the same book again";
}
else
{
54
obj.gettable("select bname, quantity from book where bid = "+TextBox1.Text+"
and status = 'Available' ");
if (obj.dt.Rows.Count > 0)
{
TextBox2.Text = obj.dt.Rows[0][0].ToString() + " " + "ISSUED";
TextBox3.Text = obj.dt.Rows[0][1].ToString() ;
obj.excquery("insert into account values('" + Label4.Text + "', " +
TextBox1.Text + ", '" +System.DateTime.Now.ToLongDateString()+ "')");
}
else
TextBox2.Text = "NOT AVAILABLE";
}
55
}
protected void Button2_Click(object sender, EventArgs e)
{
Session.Abandon();
Response.Redirect("login1.aspx");
}
}
56
RETURN BOOKS WORKING
57
{
obj.excquery("delete from book where bid = " + TextBox1.Text + " ");
obj.excquery("delete from account where bid = " + TextBox1.Text + "
");
}
}
GridView1.DataBind();
GridView2.DataBind();
}}
else
{
TextBox2.Text = "Book Not Found";
}
}}
58
ACCOUNT WORKING
}
protected void Button1_Click(object sender, EventArgs e)
{
obj.gettable("select ImageUrl from pic where uname = '" + Label1.Text + "'");
if (obj.dt.Rows.Count > 0)
{
obj.excquery("delete from pic where uname = '" + Label1.Text + "'");
}
59
if (FileUpload1.HasFile)
{
string fn = Path.GetFileName(FileUpload1.FileName);
FileUpload1.SaveAs(Server.MapPath("./" + fn));
Image1.ImageUrl = FileUpload1.PostedFile.FileName;
obj.excquery("insert into pic values('" + Label1.Text + "', '" +
Image1.ImageUrl + "')");
}
}
protected void Button2_Click(object sender, EventArgs e)
{
obj.gettable("select pwd from avi where uname = '" + Session["Name"] + "' and
pwd = '" + oldpwd.Text + "' ");
if (obj.dt.Rows.Count > 0)
{
obj.excquery("update avi set pwd = '" + chpwd.Text + "' where uname = '" +
Session["Name"] + "' ");
TextBox1.Visible = true;
TextBox1.Text = "Password Updated!";
}
else
{
TextBox1.Visible = true;
TextBox1.Text = "Old Password Invalid!";
}
}
}
60
MANAGE USERS WORKING
GridView1.DataBind();
GridView2.DataBind();
GridView3.DataBind();
}
}
61
ADD BOOKS
obj.gettable("select quantity from book where bid = " + bookid.Text + " ");
if (obj.dt.Rows.Count > 0)
{
if (obj.dt.Rows[0][0].ToString() == "0")
{
obj.excquery("update book set status = 'Available' where bid = " +
bookid.Text + " ");
}
}
else
{
Response.Write("No Such Book Record Exists. Please try Option 2");
}
}
protected void Button2_Click(object sender, EventArgs e)
{
obj.gettable("select * from book where bid = "+bookid2.Text+" ");
if (obj.dt.Rows.Count > 0)
{
62
Response.Write("Try option 1 or another BOOKID. A book with same
BookID already exists!");
}
else
{
obj.excquery("insert into book values(" + bookid2.Text + ", '" +
bookname.Text + "', 'Available', " + quantity2.Text + ")");
}
bookid2.Text = " ";
bookname.Text = " ";
quantity2.Text = " ";
GridView1.DataBind();
}
}
63
REMOVE BOOKS
64
obj.excquery("delete from book where bid = " + TextBox1.Text + " ");
obj.excquery("delete from account where bid = " + TextBox1.Text + "
");
}
}
GridView1.DataBind();
GridView2.DataBind();
}
}
else
{
TextBox2.Text = "Book Not Found";
}
}
}
65
SERVER MANAGEMENT STUDIO
66
Stored Procedure and Tables
Register
USE [Avijit]
GO
/****** Object: StoredProcedure [dbo].[register] Script Date: 03/30/2012 08:39:30
******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
ALTER procedure [dbo].[register]( @uname varchar(50), @pwd varchar(50), @email
varchar(50), @question varchar(50), @answer varchar(50) )
as
insert into avi values( @uname, @pwd, @email, @question, @answer)
Account Table
67
Admin1 Table
It is responsible for taking care of the administrator login details
CREATE TABLE [dbo].[admin1](
[uname] [varchar](50) NULL,
[pwd] [varchar](50) NULL
)
Avi Table
Book Table
68
Pic Table
Holds the location of the profile pictures of the users and the admin
69
Connecting to the database
70
CONCLUSION
After we completed the project we were sure the problems in the existing system are
overcome. The “LIBRARY MANAGEMENT SYSTEM” process made
computerized to reduce human errors and to increase the efficiency. The main focus
of this project is to lessen human efforts. The maintenance of the records is made
efficient, as all the records are stored in the ACCESS database, through which data
can be retrieved easily. The editing is also made simpler. The user has to just type in
the required field and update the desired field.
Our main aim of the project is to get the correct information about a particular
student and books available in the library.
The problems, which existed, have been removed to a large extent. And it is expected
that this project will go a long way in satisfying user’s requirements. The
computerization of the Library Management will not only improve the efficiency but
will also reduce human stress thereby indirectly improving human recourses
71
REFERENCES
72