Introduction To Project

LIBRARY AUTOMATION PROJECT
Introduction to project
This project of “library management” gives us the information about the library. In this
project enter the record new books and retrieve the details of books available in library this
project can issue the books to the students and maintain their records and can also check how
many books are issue and stock available in library.
Throughout the project the focus has been on presenting information on comments in an
intelligible manner. The project is very useful for those who want to know about library
management system.
AIM
In the existing system the We can automate the library processing of Issuing of Books,
returning of Books, Member issue etc.
1. Administrative Module
ADMINISTRATIVE MODULE
This module is the main module which performs all the main operations in the
system. The major operations in the system are:
 Member Details
 Issue Details
 Return Details
 Book Details
 Searching Books
 Book report
SYSTEM STUDY AND ANALISYS
SYSTEM ANALYSIS
System analysis is a process of gathering and interpreting facts, diagnosing problems and
the information to recommend improvements on the system. It is a problem solving activity that
requires intensive communication between the system users and system developers. System
analysis or study is an important phase of any system development process. The system is
studied to the minutest detail and analyzed. The system analyst plays the role of the interrogator
and dwells deep into the working of the present system. The system is viewed as a whole and the
input to the system are identified. The outputs from the organizations are traced to the various
processes. System analysis is concerned with becoming aware of the problem, identifying the
relevant and decisional variables, analyzing and synthesizing the various factors and determining
an optimal or at least a satisfactory solution or program of action.
A detailed study of the process must be made by various techniques like interviews,
questionnaires etc. The data collected by these sources must be scrutinized to arrive to a
conclusion. The conclusion is an understanding of how the system functions. This system is
called the existing system. Now the existing system is subjected to close study and problem areas
are identified. The designer now functions as a problem solver and tries to sort out the
difficulties that the enterprise faces. The solutions are given as proposals. The proposal is then
weighed with the existing system analytically and the best one is selected. The proposal is
presented to the user for an endorsement by the user. The proposal is reviewed on user request
and suitable changes are made. This is loop that ends as soon as the user is satisfied with
proposal.
Preliminary study is the process of gathering and interpreting facts, using the information for
further studies on the system. Preliminary study is problem solving activity that requires
intensive communication between the system users and system developers. It does various
feasibility studies. In these studies a rough figure of the system activities can be obtained, from
which the decision about the strategies to be followed for effective system study and analysis can
be taken.
EXISTING SYSTEM
In the existing system the transactions are done only manually but in proposed system
we have to computerize all the banking transaction using the software Banking system.
2. 1.1 PROBLEMS WITH EXISTING SYSTEM
 Lack of security of data.

 More man power.
 Time consuming.
 Consumes large volume of pare work.
 Needs manual calculations.
 No direct role for the higher officials.
 Damage of machines due to lack of attention.
To avoid all these limitations and make the working more accurately the system needs to be
computerized.
PROPOSED SYSTEM
The aim of proposed system is to develop a system of improved facilities. The proposed
system can overcome all the limitations of the existing system. The system provides proper
security and reduces the manual work.
2. 2. 1 ADVANTAGES OF THE PROPOSED SYSTEM
The system is very simple in design and to implement. The system requires very low system
resources and the system will work in almost all configurations. It has got following features
 Security of data.
 Ensure data accuracy’s.
 Proper control of the higher officials.
 Reduce the damages of the machines.
 Minimize manual data entry.
 Minimum time needed for the various processing.
 Greater efficiency.
 Better service.
 User friendliness and interactive.
 Minimum time required.
2.3. FEASIBILITY STUDY
Feasibility study is made to see if the project on completion will serve the purpose of the
organization for the amount of work, effort and the time that spend on it. Feasibility study lets
the developer foresee the future of the project and the usefulness. A feasibility study of a system
proposal is according to its workability, which is the impact on the organization, ability to meet
their user needs and effective use of resources. Thus when a new application is proposed it
normally goes through a feasibility study before it is approved for development.
The document provide the feasibility of the project that is being designed and lists various
areas that were considered very carefully during the feasibility study of this project such as
Technical, Economic and Operational feasibilities. The following are its features:
2.3.1. TECHNICAL FEASIBILITY
The system must be evaluated from the technical point of view first. The assessment of this
feasibility must be based on an outline design of the system requirement in the terms of input,
output, programs and procedures. Having identified an outline system, the investigation must go
on to suggest the type of equipment, required method developing the system, of running the
system once it has been designed.
Technical issues raised during the investigation are:
Does the existing technology sufficient for the suggested one?
Can the system expand if developed?
The project should be developed such that the necessary functions and performance are
achieved within the constraints. The project is developed within latest technology. Through the
technology may become obsolete after some period of time, due to the fact that never version of
same software supports older versions, the system may still be used. So there are minimal
constraints involved with this project. The system has been developed using Java the project is
technically feasible for development.
2.3.2. ECONOMIC FEASIBILITY
The developing system must be justified by cost and benefit. Criteria to ensure that effort is
concentrated on project, which will give best, return at the earliest. One of the factors, which
affect the development of a new system, is the cost it would require.
The following are some of the important financial questions asked during preliminary
investigation:
 The costs conduct a full system investigation.
 The cost of the hardware and software.
 The benefits in the form of reduced costs or fewer costly errors.
Since the system is developed as part of project work, there is no manual cost to spend for the
proposed system. Also all the resources are already available, it give an indication of the system
is economically possible for development.
2.3.3. BEHAVIORAL FEASIBILITY
This includes the following questions:
 Is there sufficient support for the users?

 Will the proposed system cause harm?
The project would be beneficial because it satisfies the objectives when developed and
installed. All behavioral aspects are considered carefully and conclude that the project is
behaviorally feasible.
SYSTEM DESIGN
3.1 INTRODUCTION
Design is the first step into the development phase for any engineered product or system.
Design is a creative process. A good design is the key to effective system. The term “design” is
defined as “the process of applying various techniques and principles for the purpose of defining
a process or a system in sufficient detail to permit its physical realization”. It may be defined as a
process of applying various techniques and principles for the purpose of defining a device, a
process or a system in sufficient detail to permit its physical realization. Software design sits at
the technical kernel of the software engineering process and is applied regardless of the
development paradigm that is used. The system design develops the architectural detail required
to build a system or product. As in the case of any systematic approach, this software too has
undergone the best possible design phase fine tuning all efficiency, performance and accuracy
levels. The design phase is a transition from a user oriented document to a document to the
programmers or database personnel. System design goes through two phases of development:
Logical and Physical Design.
LOGICAL DESIGN:
The logical flow of a system and define the boundaries of a system. It includes the following
steps:
 Reviews the current physical system – its data flows, file content, volumes , frequencies
etc.
 Prepares output specifications – that is, determines the format, content and frequency of
reports.
 Prepares input specifications – format, content and most of the input functions.
 Prepares edit, security and control specifications.
 Specifies the implementation plan.
 Prepares a logical design walk through of the information flow, output, input, controls
and implementation plan.
 Reviews benefits, costs, target dates and system constraints.
PHYSICAL DESIGN:
Physical system produces the working systems by define the design specifications that tell the
programmers exactly what the candidate system must do. It includes the following steps.
 Design the physical system.
 Specify input and output media.
 Design the database and specify backup procedures.
 Design physical information flow through the system and a physical design Walk
through.
 Plan system implementation.
 Prepare a conversion schedule and target date.
 Determine training procedures, courses and timetable.
 Devise a test and implementation plan and specify any new hardware/software.
 Update benefits , costs , conversion date and system constraints
Design/Specification activities:
 Concept formulation.
 Problem understanding.
 High level requirements proposals.
 Feasibility study.
 Requirements engineering.
 Architectural design.
MODULE DESIGN
Admin
The Administrator logs in using the admin login. In this module two operations are
done. During login the Login and Password is verified with that in the database
INPUT DESIGN
The design of input focuses on controlling the amount of input required, controlling the
errors, avoiding delay, avoiding extra steps and keeping the process simple. The input is
designed in such a way so that it provides security and ease of use with retaining the privacy.
Input Design considered the following things:
o What data should be given as input?

o How the data should be arranged or coded?
o The dialog to guide the operating personnel in providing input.
o Methods for preparing input validations and steps to follow when error occur.
OBJECTIVES
Input Design is the process of converting a user-oriented description of the input into a
computer-based system. This design is important to avoid errors in the data input process and
show the correct direction to the management for getting correct information from the
computerized system.
It is achieved by creating user-friendly screens for the data entry to handle large volume of data.
The goal of designing input is to make data entry easier and to be free from errors. The data entry
screen is designed in such a way that all the data manipulates can be performed. It also provides
record viewing facilities.
When the data is entered it will check for its validity. Data can be entered with the help of
screens. Appropriate messages are provided as when needed so that the user will not be in a
maize of instant. Thus the objective of input design is to create an input layout that is easy to
follow
OUTPUT DESIGN
A quality output is one, which meets the requirements of the end user and presents the
information clearly. In output design it is determined how the information is to be displaced for
immediate need and also the hard copy output. It is the most important and direct source
information to the user. Efficient and intelligent output design improves the system’s relationship
to help user decision-making.
Designing computer output should proceed in an organized, well thought out manner; the
right output must be developed while ensuring that each output element is designed so that
people will find the system can use easily and effectively. When analysis design computer
output, they should :
 Identify the specific output that is needed to meet the requirements.
 Select methods for presenting information.
 Create document, report, or other formats that contain information produced by the
system.
3.3 DATABASE DESIGN
A database is an organized mechanism that has the capability of storing information through
which a user can retrieve stored information in an effective and efficient manner. The data is the
purpose of any database and must be protected.
The database design is a two level process. In the first step, user requirements are gathered
together and a database is designed which will meet these requirements as clearly as possible.
This step is called Information Level Design and it is taken independent of any individual
DBMS.
In the second step, this Information level design is transferred into a design for the specific
DBMS that will be used to implement the system in question. This step is called Physical Level
Design, concerned with the characteristics of the specific DBMS that will be used. A database
design runs parallel with the system design. The organization of the data in the database is aimed
to achieve the following two major objectives.
 Data Integrity
 Data independence
Normalization is the process of decomposing the attributes in an application, which results in

a set of tables with very simple structure. The purpose of normalization is to make tables as
simple as possible. Normalization is carried out in this system for the following reasons.
 To structure the data so that there is no repetition of data , this helps in saving.
 To permit simple retrieval of data in response to query and report request.
 To simplify the maintenance of the data through updates, insertions, deletions.
 To reduce the need to restructure or reorganize data which new application requirements
arise.
RELATIONAL DATABASE MANAGEMENT SYSTEM (RDBMS):
A relational model represents the database as a collection of relations. Each relation

resembles a table of values or file of records. In formal relational model terminology, a row is
called a tuple, a column header is called an attribute and the table is called a relation. A relational
database consists of a collection of tables, each of which is assigned a unique name. A row in a
tale represents a set of related values.
RELATIONS, DOMAINS & ATTRIBUTES:
A table is a relation. The rows in a table are called tuples. A tuple is an ordered set of n
elements. Columns are referred to as attributes. Relationships have been set between every table
in the database. This ensures both Referential and Entity Relationship Integrity. A domain D is a
set of atomic values. A common method of specifying a domain is to specify a data type from
which the data values forming the domain are drawn. It is also useful to specify a name for the
domain to help in interpreting its values. Every value in a relation is atomic, that is not
decomposable.
RELATIONSHIPS:
Table relationships are established using Key. The two main keys of prime importance are
Primary Key & Foreign Key. Entity Integrity and Referential Integrity Relationships can be
established with these keys.Entity Integrity enforces that no Primary Key can have null
values.Referential Integrity enforces that no Primary Key can have null values.
Referential Integrity for each distinct Foreign Key value, there must exist a matching Primary
Key value in the same domain. Other key are Super Key and Candidate Keys.
Relationships have been set between every table in the database. This ensures both Referential
and Entity Relationship Integrity.
NORMALIZATION:
As the name implies, it denoted putting things in the normal form. The application developer via
normalization tries to achieve a sensible organization of data into proper tables and columns and
where names can be easily correlated to the data by the user. Normalization eliminates repeating
groups at data and thereby avoids data redundancy which proves to be a great burden on the
computer resources. These includes:
 Normalize the data.

 Choose proper names for the tables and columns.
 Choose the proper name for the data.
First Normal Form:
The First Normal Form states that the domain of an attribute must include only atomic values
and that the value of any attribute in a tuple must be a single value from the domain of that
attribute. In other words 1NF disallows “relations within relations” or “relations as attribute
values within tuples”. The only attribute values permitted by 1NF are single atomic or indivisible
values.
The first step is to put the data into First Normal Form. This can be donor by moving data
into separate tables where the data is of similar type in each table. Each table is given a Primary
Key or Foreign Key as per requirement of the project. In this we form new relations for each
nonatomic attribute or nested relation. This eliminated repeating groups of data.
A relation is said to be in first normal form if only if it satisfies the constraints that contain the
primary key only.
Second Normal Form:
According to Second Normal Form, For relations where primary key contains multiple
attributes, no non key attribute should be functionally dependent on a part of the primary key.
In this we decompose and setup a new relation for each partial key with its dependent
attributes. Make sure to keep a relation with the original primary key and any attributes that are
fully functionally dependent on it. This step helps in taking out data that is only dependant on
apart of the key.
A relation is said to be in second normal form if and only if it satisfies all the first normal form
conditions for the primary key and every non-primary key attributes of the relation is fully
dependent on its primary key alone.
Third Normal Form:
According to Third Normal Form, Relation should not have a non key attribute functionally
determined by another non key attribute or by a set of non key attributes. That is, there should be
no transitive dependency on the primary key.
In this we decompose and set up relation that includes the non key attributes that functionally
determines other non key attributes. This step is taken to get rid of anything that does not depend
entirely on the Primary Key.
A relation is said to be in third normal form if only if it is in second normal form and more
over the non key attributes of the relation should not be depend on other non key attribute.
TABLES STRUCTURE
SYSTEM DEVELOPEMENT
4.1 SYSTEM SPECIFICATION
HARDWARE REQUIREMENTS
Processor : X86 Compatible processor with 1.7 GHz Clock speed
RAM : 512 MB or more
Hard disk : 20 GB or more
Monitor : VGA/SVGA
Keyboard : 104 Keys
Mouse : 2 buttons/ 3 buttons
SOFTWARE REQUIREMENTS
Operating System : Windows 2000/XP

Front end : Visual Basic 6.0
Back end : MS Access
4.2 SOFTWARE ENVIRONMENT
The Control Properties

Before writing an event procedure for the control to response to a user's input, you have to set
certain properties for the control to determine its appearance and how it will work with the event
procedure. You can set the properties of the controls in the properties window or at runtime.
Handling some of the common controls
3.2.1 The Text Box

The text box is the standard control for accepting input from the user as well as to display
the output. It can handle string (text) and numeric data but not images or pictures. String in a text
box can be converted to a numeric data by using the function Val(text). The following example
illustrates a simple program that processes the input from the user.
Example 3.1
In this program, two text boxes are inserted into the form together with a few labels. The
two text boxes are used to accept inputs from the user and one of the labels will be used to
display the sum of two numbers that are entered into the two text boxes. Besides, a command
button is also programmed to calculate the sum of the two numbers using the plus operator. The
program use creates a variable sum to accept the summation of values from text box 1 and text
box 2.The procedure to calculate and to display the output on the label is shown below. The
output is shown in Figure 3.2
Private Sub Command1_Click()
‘To add the values in text box 1 and text box 2
Sum = Val(Text1.Text) + Val(Text2.Text)
‘To display the answer on label 1
Label1.Caption = Sum
End Sub
Figure 3.2
3.2.2 The Label

The label is a very useful control for Visual Basic, as it is not only used to provide
instructions and guides to the users, it can also be used to display outputs. One of its most
important properties is Caption. Using the syntax label.Caption, it can display text and numeric
data . You can change its caption in the properties window and also at runtime. Please refer to
Example 3.1 and Figure 3.1 for the usage of label.
3.2.3 The Command Button

The command button is one of the most important controls as it is used to execute
commands. It displays an illusion that the button is pressed when the user click on it. The most
common event associated with the command button is the Click event, and the syntax for the
procedure is
Private Sub Command1_Click ()
Statements
End Sub
3.2.4 The Picture Box

The Picture Box is one of the controls that is used to handle graphics. You can load a
picture at design phase by clicking on the picture item in the properties window and select the
picture from the selected folder. You can also load the picture at runtime using the LoadPicture
method. For example, the statement will load the picture grape.gif into the picture box.
Picture1.Picture=LoadPicture ("C:\VB program\Images\grape.gif")
You will learn more about the picture box in future lessons. The image in the picture box is not
resizable.
3.2.5 The Image Box

The Image Box is another control that handles images and pictures. It functions almost
identically to the picture box. However, there is one major difference, the image in an Image Box
is stretchable, which means it can be resized. This feature is not available in the Picture Box.
Similar to the Picture Box, it can also use the LoadPicture method to load the picture. For
example, the statement loads the picture grape.gif into the image box.
Image1.Picture=LoadPicture ("C:\VB program\Images\grape.gif")
3.2.6 The List Box

The function of the List Box is to present a list of items where the user can click and
select the items from the list. In order to add items to the list, we can use the AddItem method.
For example, if you wish to add a number of items to list box 1, you can key in the following
statements
Example 3.2
Private Sub Form_Load ( )
List1.AddItem “Lesson1”
End Sub
The items in the list box can be identified by the ListIndex property, the value of the ListIndex
for the first item is 0, the second item has a ListIndex 1, and the second item has a ListIndex 2
and so on
3.2.7 The Combo Box

The function of the Combo Box is also to present a list of items where the user can click
and select the items from the list. However, the user needs to click on the small arrowhead on the
right of the combo box to see the items which are presented in a drop-down list. In order to add
items to the list, you can also use the AddItem method. For example, if you wish to add a
number of items to Combo box 1, you can key in the following statements
Example 3.3
Private Sub Form_Load ( )
Combo1.AddItem “Item1”
End Sub
3.2.8 The Check Box
The Check Box control lets the user selects or unselects an option. When the Check Box
is checked, its value is set to 1 and when it is unchecked, the value is set to 0. You can include
the statements Check1.Value=1 to mark the Check Box and Check1.Value=0 to unmark the
Check Box, as well as use them to initiate certain actions. For example, the program will change
the background color of the form to red when the check box is unchecked and it will change to
blue when the check box is checked. You will learn about the conditional statement
If….Then….Elesif in later lesson. VbRed and vbBlue are color constants and BackColor is the
background color property of the form.
3.2.9 The Option Box
The Option Box control also lets the user selects one of the choices. However, two or
more Option Boxes must work together because as one of the Option Boxes is selected, the other
Option Boxes will be unselected. In fact, only one Option Box can be selected at one time. When
an option box is selected, its value is set to “True” and when it is unselected; its value is set to
“False”. In the following example, the shape control is placed in the form together with six
Option Boxes. When the user clicks on different option boxes, different shapes will appear. The
values of the shape control are 0, 1, and 2,3,4,5 which will make it appear as a rectangle, a
square, an oval shape, a rounded rectangle and a rounded square respectively.
Example 3.4
Private Sub Option1_Click ( )
Shape1.Shape = 0
End Sub
Private Sub Option2_Click()
Shape1.Shape = 1
End Sub
Shape1.Shape = 2
End Sub
Shape1.Shape = 3
End Sub
Shape1.Shape = 4
End Sub
Shape1.Shape = 5
End Sub
3.2.10 The Drive List Box
The Drive ListBox is for displaying a list of drives available in your computer. When you
place this control into the form and run the program, you will be able to select different drives
from your computer as shown in Figure 3.3
3.2.11 The Directory List Box

The Directory List Box is for displaying the list of directories or folders in a selected
drive. When you place this control into the form and run the program, you will be able to select
different directories from a selected drive in your computer as shown in Figure 3.4
3.2.12 The File List Box

The File List Box is for displaying the list of files in a selected directory or folder. When
you place this control into the form and run the program, you will be able to shown the list of
files in a selected directory as shown in Figure 3.5
You can coordinate the Drive List Box, the Directory List Box and the File List Box to search
for the files you want. The procedure will be discussed in later lessons.
Data Flow Diagram:-

Address
Name
Code
Member details Renewal

date
Fees
Book Details Rack no

Code
Name
Stock
Author Publisher
Issue details
M code B code
M
B name
name
I date R date
Quantity
SYSTEM IMPLEMENTATION AND TESTING
5.1 CODING
Form1.Hide
Form2.Show
Form2.Text1.Text = ""
End Sub

Form1.Hide
Form3.Show
End Sub

Form1.Hide
Form4.Show
Form4.Data1.RecordSource = "select * from Issue_mast"
Form4.Data1.Refresh
Form4.Text1.SetFocus
End Sub

d = InputBox("Enter the member code to delete the record", "Delete")
Data3.RecordSource = "select * from issue_mast where mem_code='" + d + "'"
Data3.Refresh
Do While Not Data3.Recordset.EOF
c=c+1
Data3.Recordset.MoveNext
Loop
If c <> 0 Then
MsgBox "The member has not returned the book", vbInformation, "Library"
Data3.Recordset.Close
Else
Data1.RecordSource = "select * from mem_mast"
Data1.Refresh
Form1.Hide
Form5.Show
End If
End Sub

r = InputBox("Enter your member code", "Book Return")
Data3.RecordSource = "select * from issue_mast where mem_code='" + r + "'"
Data3.Refresh
qty = Data3.Recordset.Fields(6)
Data3.Recordset.Delete
Data3.RecordSource = "select * from issue_mast"
Data3.Refresh
b = InputBox("Enter your book code", "Book Return")
Data2.RecordSource = "select * from book_mast where book_code='" + b + "'"
Data2.Refresh
Data2.Recordset.Edit
s = Data2.Recordset.Fields(4)
cs = s + qty
Data2.Recordset.Fields(4) = cs
Data2.Recordset.Update
End Sub

d = InputBox("Enter the book code to delete the book", "Delete")
Data3.RecordSource = "select * from issue_mast where book_code='" + d + "'"
Data3.Refresh
c=c+1
Loop
If c <> 0 Then
MsgBox "Don't Delete, we have issued this book", vbInformation, "Library"
Else
Data2.RecordSource = "select * from book_mast"
Data2.Refresh
Form1.Hide
Form6.Show
End If
End Sub

End
End Sub
Private Sub Form_Load()

If SSTab1.Tab = 0 Then
Data1.Refresh
Command1.Visible = True
Command2.Visible = False
End If
Data2.RecordSource = "select * from Book_mast"
Data2.Refresh
End If
Data3.RecordSource = "select * from Issue_mast"
Data3.Refresh
End If
End Sub
Private Sub SSTab1_Click(PreviousTab As Integer)

Data1.RecordSource = "select * from Mem_mast"
Data1.Refresh
ElseIf SSTab1.Tab = 1 Then
Data2.RecordSource = "select * from Book_mast"
Data2.Refresh
ElseIf SSTab1.Tab = 2 Then
Data3.RecordSource = "select * from Issue_mast"
Data3.Refresh
End If
End Sub
Data1.Refresh
Data1.Recordset.AddNew
Data1.Recordset.Fields(0) = Text1.Text
Data1.Recordset.Fields(3) = CInt(Text4.Text)
Data1.Recordset.Fields(4) = CDate(Text5.Text)
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
End Sub

Form1.Data1.RecordSource = "select * from mem_mast"
Form1.Data1.Refresh
Form2.Hide
Form1.Show
End Sub
Private Sub Text1_LostFocus()

On Error GoTo errorhandle
Data1.RecordSource = "select * from mem_mast where mem_code='" + Text1.Text + "'"
Data1.Refresh
c=c+1
Loop
If c <> 0 Then
MsgBox "Duplicate Code", vbExclamation, "Duplicate"
Text1.Text = " "
Text1.SetFocus
Else
Text2.SetFocus
End If
Exit Sub
errorhandle:
MsgBox "Error occurred!Wrong Member Code", vbInformation, "Error"
End
End Sub
Private Sub Text4_GotFocus()

Text4.Text = "500"
End Sub
Data1.RecordSource = "select * from book_mast"
Data1.Refresh
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
End Sub

Form1.Data2.RecordSource = "select * from book_mast"
Form1.Data2.Refresh
Form3.Hide
Form1.Show
End Sub

Data1.RecordSource = "select * from book_mast where book_code='" + Text1.Text + "'"
Data1.Refresh
c=c+1
Loop
If c <> 0 Then
MsgBox "Duplicate Code", vbExclamation, "Duplicate"
Text1.Text = " "
Text1.SetFocus
Else
Text2.SetFocus
End If
Exit Sub
errorhandle:
MsgBox "Error occurred!Wrong Book Code", vbInformation, "Error"
End
End Sub
Data1.RecordSource = "select * from issue_mast"
Data1.Refresh
Form1.Data2.RecordSource = "select * from book_mast where book_code='" + Text3.Text + "'"
Form1.Data2.Refresh
Form1.Data2.Recordset.Edit
Form4.Text8.Text = Form1.Data2.Recordset.Fields(4)
Text8.Text = Val(Text8.Text) - Val(Text7.Text)
Form1.Data2.Recordset.Fields(4) = Val(Text8.Text)
Form1.Data2.Recordset.Update
Form1.Data2.Recordset.Close
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
End Sub

Form1.Data3.RecordSource = "select * from issue_mast"
Form1.Data3.Refresh
Form4.Hide
Form1.Show
End Sub
Private Sub List1_Click()

Text4.Text = List1.Text
Form1.Data2.RecordSource = "select * from book_mast where book_name='" + List1.Text + "'"
Form1.Data2.Refresh
Do While Not Form1.Data2.Recordset.EOF
Form1.Data2.Recordset.MoveNext
Loop
End Sub

Data1.RecordSource = "select * from issue_mast where mem_code='" + Text1.Text + "'"
Data1.Refresh
c=c+1
Loop
If c <> 0 Then
MsgBox "Please return the book first", vbInformation, "Book Return"
Text1.Text = ""
Form4.Hide
Form1.Show
Else
Form1.Data1.RecordSource = "select * from mem_mast where mem_code='" + Text1.Text + "'"
Form1.Data1.Refresh
Form1.Data1.Recordset.Edit
Text2.Text = Form1.Data1.Recordset.Fields(1)
Form1.Data1.Recordset.Update
List1.Clear
Form1.Data2.Refresh
Do While Not Form1.Data2.Recordset.EOF
Form4.List1.AddItem (Form1.Data2.Recordset.Fields(1))
Form1.Data2.Recordset.MoveNext
Loop
End If
Exit Sub
errorhandle:
MsgBox "Error occured!Wrong Member Code", vbInformation, "Error"
End
End Sub
Private Sub Text5_GotFocus()

Text5.Text = Date
End Sub

If Val(Text8.Text) > Val(Text7.Text) Then
Text8.Text = Val(Text8.Text) - Val(Text7.Text)
Command1.SetFocus
Else
MsgBox ("Please check your stock")
Text7.Text = " "
End If
End Sub
Data1.Recordset.MoveFirst
Command1.Enabled = False
Command3.Enabled = True
End Sub

s = Data1.Recordset.RecordCount
If Data1.Recordset.AbsolutePosition = s - 1 Then
End If
End Sub

Data1.Recordset.MoveLast
End Sub

Data1.Recordset.MovePrevious
If Data1.Recordset.AbsolutePosition = s Then
End If
End Sub

If Data1.Recordset.EOF Then
Else
End If
End Sub

Form5.Hide
Form1.Show
Form1.Data1.RecordSource = "select * from mem_mast"
Form1.Data1.Refresh
End Sub
End Sub

If Data1.Recordset.AbsolutePosition = s - 1 Then
End If
End Sub

Data1.Recordset.MoveLast
End Sub

Data1.Recordset.MovePrevious
If Data1.Recordset.AbsolutePosition = s Then
End If
End Sub

If Data1.Recordset.EOF Then
Else
End If
End Sub

Form6.Hide
Form1.Show
Form1.Data2.Refresh
End Sub
5.2 SYSTEM IMPLEMENTATION AND TESTING
Implementation is the stage of the project where the theoretical design is turned into a
working system. It can be considered to be the most crucial stage in achieving a successful new
system gaining the users confidence that the new system will work and will be effective and
accurate. It is primarily concerned with user training and documentation. Conversion usually
takes place about the same time the user is being trained or later. Implementation simply means
convening a new system design into operation, which is the process of converting a new revised
system design into an operational one.
5.2.1. SYSTEM TESTING
Software Testing is the process of executing software in a controlled manner, in order to

answer the question - Does the software behave as specified?. Software testing is often used in
association with the terms verification and validation. Validation is the checking or testing of
items, includes software, for conformance and consistency with an associated specification.
Software testing is just one kind of verification, which also uses techniques such as reviews,
analysis, inspections, and walkthroughs. Validation is the process of checking that what has been
specified is what the user actually wanted.
Validation : Are we doing the right job?

Verification : Are we doing the job right?
Software testing should not be confused with debugging. Debugging is the process of
analyzing and localizing bugs when software does not behave as expected. Although the
identification of some bugs will be obvious from playing with the software, a methodical
approach to software testing is a much more thorough means for identifying bugs. Debugging is
therefore an activity which supports testing, but cannot replace testing.
Other activities which are often associated with software testing are static analysis and dynamic
analysis. Static analysis investigates the source code of software, looking for problems and
gathering metrics without actually executing the code. Dynamic analysis
looks at the behavior of software while it is executing, to provide information such as execution
traces, timing profiles, and test coverage information.
Testing is a set of activity that can be planned in advanced and conducted systematically.
Testing begins at the module level and work towards the integration of entire computers based
system. Nothing is complete without testing, as it vital success of the system testing objectives,
there are several rules that can serve as testing objectives. They are
Testing is a process of executing a program with the intend of finding an error.A good test case
is one that has high possibility of finding an undiscovered error.A successful test is one that
uncovers an undiscovered error.
If a testing is conducted successfully according to the objectives as stated above, it would

uncovered errors in the software also testing demonstrate that the software function appear to be
working according to the specification, that performance requirement appear to have been met.
There are three ways to test program.

 For correctness
 For implementation efficiency
 For computational complexity
Test for correctness are supposed to verify that a program does exactly what it was designed
to do. This is much more difficult than it may at first appear, especially for large programs.
TEST PLAN
A test plan implies a series of desired course of action to be followed in accomplishing

various testing methods. The Test Plan acts as a blue print for the action that is to be followed.
The software engineers create a computer program, its documentation and related data structures.
The software developers is always responsible for testing the individual units of the programs,
ensuring that each performs the function for which it was designed. There is an independent test
group (ITG) which is to remove the inherent problems associated with letting the builder to test
the thing that has been built. The specific objectives of testing should be stated in measurable
terms. So that the mean time to failure, the cost to find and fix the defects, remaining defect
density or frequency of occurrence and test work-hours per regression test all should be stated
within the test plan.
The levels of testing include:
 Unit testing
 Integration Testing
 Data validation Testing
 Output Testing
UNIT TESTING
Unit testing focuses verification effort on the smallest unit of software design – the software
component or module. Using the component level design description as a guide, important
control paths are tested to uncover errors within the boundary of the module. The relative
complexity of tests and uncovered scope established for unit testing. The unit testing is white-
box oriented, and step can be conducted in parallel for multiple components. The modular
interface is tested to ensure that information properly flows into and out of the program unit
under test. The local data structure is examined to ensure that data stored temporarily maintains
its integrity during all steps in an algorithm’s execution. Boundary conditions are tested to ensure
that all statements in a module have been executed at least once. Finally, all error handling paths
are tested.
Tests of data flow across a module interface are required before any other test is initiated. If
data do not enter and exit properly, all other tests are moot. Selective testing of execution paths is
an essential task during the unit test. Good design dictates that error conditions be anticipated
and error handling paths set up to reroute or cleanly terminate processing when an error does
occur. Boundary testing is the last task of unit testing step. Software often fails at its boundaries.
Unit testing was done in Sell-Soft System by treating each module as separate entity and
testing each one of them with a wide spectrum of test inputs. Some flaws in the internal logic of
the modules were found and were rectified.
INTEGRATION TESTING
Integration testing is systematic technique for constructing the program structure while at the
same time conducting tests to uncover errors associated with interfacing. The objective is to take
unit tested components and build a program structure that has been dictated by design. The entire
program is tested as whole. Correction is difficult because isolation of causes is complicated by
vast expanse of entire program. Once these errors are corrected, new ones appear and the process
continues in a seemingly endless loop.
After unit testing in Sell-Soft System all the modules were integrated to test for any
inconsistencies in the interfaces. Moreover differences in program structures were removed and a
unique program structure was evolved.
VALIDATION TESTING OR SYSTEM TESTING
This is the final step in testing. In this the entire system was tested as a whole with all forms,
code, modules and class modules. This form of testing is popularly known as Black Box testing
or System testing.
Black Box testing method focuses on the functional requirements of the software. That is,
Black Box testing enables the software engineer to derive sets of input conditions that will fully
exercise all functional requirements for a program.
Black Box testing attempts to find errors in the following categories; incorrect or missing
functions, interface errors, errors in data structures or external data access, performance errors
and initialization errors and termination errors.
OUTPUT TESTING OR USER ACCEPTANCE TESTING
The system considered is tested for user acceptance; here it should satisfy the firm’s need.
The software should keep in touch with perspective system; user at the time of developing and
making changes whenever required. This done with respect to the following points
 Input Screen Designs,

 Output Screen Designs,
 Online message to guide the user and the like.
The above testing is done taking various kinds of test data. Preparation of test data plays a vital
role in the system testing. After preparing the test data, the system under study is tested using
that test data. While testing the system by which test data errors are again uncovered and
corrected by using above testing steps and corrections are also noted for future use.
5.3. TRAINING
Once the system is successfully developed the next important step is to ensure that the
administrators are well trained to handle the system. This is because the success of a system
invariably depends on how they are operated and used. The implementation depends upon the
right people being at the right place at the right time. Education involves creating the right
atmosphere and motivating the user. The administrators are familiarized with the run procedures
of the system, working through the sequence of activities on an ongoing basis.
Implementation is the state in the project where the theoretical design is turned into a working
system. By this, the users get the confidence that the system will work effectively. The system
can be implemented only after through testing.
The systems personnel check the feasibility of the system. The actual data were inputted to
the system and the working of the system was closely monitored. The master option was selected
from the main menu and the actual data were input through the corresponding input screens. The
data movement was studied and found to be correct queries option was then selected and this
contains various reports. Utilities provide various data needed for inventory was input and the
module was test run. Satisfactory results were obtained. Reports related to these processes were
also successfully generated. Various input screen formats are listed in the appendix.
Implementation walkthroughs ensure that the completed system actually solves the original
problem. This walkthrough occurs just before the system goes into use, and it should include
careful review of all manuals, training materials and system documentation. Again, users, the
analyst and the members of the computer services staff may attend this meeting.
APPENDIX
SCREEN SHOTS
CONCLUSION
This software has been developed to overcome to
maintaining records manually through the ledgers; it keeps all
the library records and book details.
It is very easy for the college to maintain a library records
efficiently.
BIBLIOGRAPHY
BOOKS:
1. Charles Hampfed (2000) ‘Visual Basic’ University of

Toronto
2. Herbert Schildt (2000) ‘Visual Basic 6.0’ Tata McGraw Hill
3. John Zukowski (2000) ‘Visual Basic 6.0’ ‘BPB Publications
4. Jamie Jaworsky ‘Visual Basic 6.0’Techmedia
5. Stefen Denninger ‘Visual Basic 6.0’Author’s Press
6. Ian Somerville ‘Software engineering’
7. Rajeev mall ‘Software engineering’
8. Elmasri Navathe ‘Fundamentals of database systems’
ONLINE REFERENCE:
www.w3schools.com
www.theserverside.com
www.visual.com

Introduction To Project

Uploaded by

Copyright:

Available Formats

Introduction To Project

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

Introduction To Project

Uploaded by

Copyright:

Available Formats

LIBRARY AUTOMATION PROJECT

SYSTEM STUDY AND ANALISYS

2. 1.1 PROBLEMS WITH EXISTING SYSTEM

 Lack of security of data.

2. 2. 1 ADVANTAGES OF THE PROPOSED SYSTEM

2.3. FEASIBILITY STUDY

2.3.1. TECHNICAL FEASIBILITY

2.3.2. ECONOMIC FEASIBILITY

2.3.3. BEHAVIORAL FEASIBILITY

This includes the following questions:

 Is there sufficient support for the users?

o What data should be given as input?

3.3 DATABASE DESIGN

Normalization is the process of decomposing the attributes in an application, which results in

RELATIONAL DATABASE MANAGEMENT SYSTEM (RDBMS):

A relational model represents the database as a collection of relations. Each relation

RELATIONS, DOMAINS & ATTRIBUTES:

 Normalize the data.

First Normal Form:

Second Normal Form:

Third Normal Form:

4.1 SYSTEM SPECIFICATION

Processor : X86 Compatible processor with 1.7 GHz Clock speed

RAM : 512 MB or more

Hard disk : 20 GB or more

Keyboard : 104 Keys

Mouse : 2 buttons/ 3 buttons

Operating System : Windows 2000/XP

4.2 SOFTWARE ENVIRONMENT

The Control Properties

3.2.1 The Text Box

3.2.2 The Label

3.2.3 The Command Button

3.2.4 The Picture Box

3.2.5 The Image Box

3.2.6 The List Box

Private Sub Form_Load ( )

3.2.7 The Combo Box

3.2.8 The Check Box

3.2.9 The Option Box

3.2.10 The Drive List Box

3.2.11 The Directory List Box

3.2.12 The File List Box

Data Flow Diagram:-

Member details Renewal

Book Details Rack no

SYSTEM IMPLEMENTATION AND TESTING

Private Sub Command2_Click()

Private Sub Command3_Click()

Private Sub Command4_Click()

Private Sub Command5_Click()

Private Sub Command6_Click()

Private Sub Command7_Click()

Private Sub Form_Load()

Private Sub SSTab1_Click(PreviousTab As Integer)

Private Sub Command2_Click()

Private Sub Text1_LostFocus()

Private Sub Text4_GotFocus()

Private Sub Command2_Click()