VB Final Auto Saved)

Published on February 2017 | Categories: Documents | Downloads: 31 | Comments: 0 | Views: 276
of 61
Download PDF   Embed   Report

Comments

Content


1

A
PRO1ECT
REPORT
ON
VISUAL BASIC
~LIBRARY MANAGEMENT SYSTEM¨
SUBMITTED FOR THE PARTIAL FULLFILMENT FOR THE AWARD OF DEGREE OF POST
GRADUATE DIPLOMA IN MANAGEMET
SU8MI11LD 8¥
ABHISHEK BANERJEE
IT201002
PGDM (IT)
SU8MI11LD 1C
MR.Pardipta Sarangi


AÞLLIA¥ INS1I1U1L CI 1LCnNCLCG¥
GkLA1Lk NCIDA (UÞ)
2010Ŵ12


DLCLAkA1ICN
I hereby declare that the Project Report made on ~LIBRARY MANAGEMENT SYSTEM¨
Under the guidance oI Mr. Pardipta Sarangi Submitted in partial IulIilment oI the requirements
Ior the Post Graduate Diploma In Management, submitted at Apeejay Institute of
Technology, Greater Noida, is my original work and the same has not been submitted Ior the
award oI any other Degree/diploma/Iellowship or other similar titles or prizes.


A8nISnLk 8ANLkILL
I1201002











ACkNCWLLGLMLN1

A report is never the sole product oI a person whose name has appeared on the cover. Even the
best eIIort may not prove successIul without proper guidance. For a best project one needs
proper time, energy, eIIorts, patience, and knowledge and how to use all these things. But
without any guidance it remains unsuccessIul. I have done this report with the best oI my ability
and hope that it will serve its purpose.
It was really a great learning experience and I would really express my special and proIound
gratitude to my guide Mr. Pardipta Sarangi who not only helped me in the successIul
completion oI this report but also spread his precious and valuable time in expanding my
knowledge base, I take immense pleasure in thanking them Ior supporting at all stages oI this
report.
AIter the completion oI this Report I Ieel myselI as a well aware person about the Research
Procedure and the complexities that can arose during the process. Finally, I am also grateIul to
all those personalities who have helped me directly or indirectly in bringing up this report, my
Iriends.




Abh|shek 8aner[ee
I120100



1ab|e of Content

SrŦ NoŦ 1op|cs Þage NoŦ
1Ŧ Introduction
Ŧ System Requirement 1
Ŧ System Analysis 1
Ŧ Process Description
3Ŧ Data Flow
Ŧ Coding
7Ŧ Conclusion & Future Scope







3






CHAPTER 1
INTRODUCTION













Intoduction:
About Visual Basic
Visual Basic (VB) is the third-generation event-driven programming language and integrated
development environment (IDE) Irom MicrosoIt Ior its COM programming model. Visual Basic
is relatively easy to learn and use.
Visual Basic was derived Irom BASIC and enables the rapid application development (RAD) oI
graphical user interIace (GUI) applications, access to databases using Data Access Objects,
Remote Data Objects, or ActiveX Data Objects, and creation oI ActiveX controls and objects.
Scripting languages such as VBA and VBScript are syntactically similar to Visual Basic, but
perIorm diIIerently.
A programmer can put together an application using the components provided with Visual Basic
itselI. Programs written in Visual Basic can also use the Windows API, but doing so requires
external Iunction declarations.
The Iinal release was version 6 in 1998. MicrosoIt's extended support ended in March 2008 and
the designated successor was Visual Basic .NET (now known simply as Visual Basic).

Language features
O ike the BASIC programming language, Visual Basic was designed to be easily learned
and used by beginner programmers. The language not only allows programmers to create
simple GUI applications, but can also develop complex applications. Programming in VB
is a combination oI visually arranging components or controls on a Iorm, speciIying
attributes and actions oI those components, and writing additional lines oI code Ior more
Iunctionality. Since deIault attributes and actions are deIined Ior the components, a
simple program can be created without the programmer having to write many lines oI
code. PerIormance problems were experienced by earlier versions, but with Iaster
computers and native code compilation this has become less oI an issue.

O Although programs can be compiled into native code executables Irom version 5
onwards, they still require the presence oI runtime libraries oI approximately 1 MB in
size. This runtime is included by deIault in Windows 2000 and later, but Ior earlier
versions oI Windows like 95/98/NT it must be distributed together with the executable

7

O Although programs can be compiled into native code executables Irom version 5 onwards, they
still require the presence oI runtime libraries oI approximately 1 MB in size. This runtime is
included by deIault in Windows 2000 and later, but Ior earlier versions oI Windows like
95/98/NT it must be distributed together with the executable

O Forms are created using drag-and-drop techniques. A tool is used to place controls (e.g., text
boxes, buttons, etc.) on the Iorm (window). Controls have attributes and event handlers associated
with them. DeIault values are provided when the control is created, but may be changed by the
programmer. Many attribute values can be modiIied during run time based on user actions or
changes in the environment, providing a dynamic application. For example, code can be inserted
into the Iorm resize event handler to reposition a control so that it remains centered on the Iorm,
expands to Iill up the Iorm, etc. By inserting code into the event handler Ior a keypress in a text
box, the program can automatically translate the case oI the text being entered, or even prevent
certain characters Irom being inserted.

O Visual Basic can create executables (EXE Iiles), ActiveX controls, or D Iiles, but is primarily
used to develop Windows applications and to interIace database systems. Dialog boxes with less
Iunctionality can be used to provide pop-up capabilities. Controls provide the basic Iunctionality
oI the application, while programmers can insert additional logic within the appropriate event
handlers. For example, a drop-down combination box will automatically display its list and allow
the user to select any element. An event handler is called when an item is selected, which can then
execute additional code created by the programmer to perIorm some action based on which
element was selected, such as populating a related list

O Alternatively, a Visual Basic component can have no user interIace, and instead provide
ActiveX objects to other programs via Component Object Model (COM). This allows Ior
server-side processing or an add-in module.
O The language is garbage collected using reIerence counting, has a large library oI utility
objects, and has basic object oriented support. Since the more common components are
included in the deIault project template, the programmer seldom needs to speciIy additional
libraries. Unlike many other programming languages, Visual Basic is generally not case
sensitive, although it will transIorm keywords into a standard case conIiguration and Iorce the
case oI variable names to conIorm to the case oI the entry within the symbol table. String
comparisons are case sensitive by deIault, but can be made case insensitive iI so desired.




Characteristics of Visual Basic:
Visual Basic has the Iollowing traits which diIIer Irom C-derived languages:
O Multiple assignment available in C language is not possible. A ÷ B ÷ C does not imply
that the values oI A, B and C are equal. The boolean result oI "Is B ÷ C?" is stored in A.
The result stored in A would thereIore be either Ialse or true.
O Boolean constant True has numeric value 1.
|4|
This is because the Boolean data type is
stored as a 16-bit signed integer. In this construct 1 evaluates to 16 binary 1s (the
Boolean value True), and 0 as 16 0s (the Boolean value False). This is apparent when
perIorming a Not operation on a 16 bit signed integer value 0 which will return the
integer value 1, in other words True = Not False. This inherent Iunctionality
becomes especially useIul when perIorming logical operations on the individual bits oI an
integer such as And, Jr, Xor and Not.
|5|
This deIinition oI True is also consistent with
BASIC since the early 1970s MicrosoIt BASIC implementation and is also related to the
characteristics oI CPU instructions at the time.
O ogical and bitwise operators are uniIied. This is unlike some C-derived languages (such
as Perl), which have separate logical and bitwise operators. This again is a traditional
Ieature oI BASIC.
O Variable array base. Arrays are declared by speciIying the upper and lower bounds in a
way similar to Pascal and Fortran. It is also possible to use the Option Base statement to
set the deIault lower bound. Use oI the Option Base statement can lead to conIusion when
reading Visual Basic code and is best avoided by always explicitly speciIying the lower
bound oI the array. This lower bound is not limited to 0 or 1, because it can also be set by
declaration. In this way, both the lower and upper bounds are programmable. In more
subscript-limited languages, the lower bound oI the array is not variable. This uncommon
trait does exist in Visual Basic .NET but not in VBScript.
JPTIJN BASE was introduced by ANSI, with the standard Ior ANSI Minimal BASIC
in the late 1970s.
O Relatively strong integration with the Windows operating system and the Component
Object Model. The native types Ior strings and arrays are the dedicated COM types,
BSTR and SAFEARRAY.
O Banker's rounding as the deIault behavior when converting real numbers to integers with
the #ound Iunction. . #ound(2.5, 0) gives 2, . #ound(3.5, 0) gives 4.
O Integers are automatically promoted to reals in expressions involving the normal division
operator () so that division oI one integer by another produces the intuitively correct
result. There is a speciIic integer divide operator () which does truncate.
O By deIault, iI a variable has not been declared or iI no type declaration character is
speciIied, the variable is oI type 'ariant. However this can be changed with DeItype
statements such as DefInt, DefBool, Def'ar, DefJbj, DefStr. There are 12
Deftype statements in total oIIered by Visual Basic 6.0. The deIault type may be
overridden Ior a speciIic declaration by using a special suIIix character on the variable
name (# Ior Double, ! Ior Single, & Ior ong, % Ior Integer, $ Ior String, and @ Ior


Currency) or using the key phrase As (type). VB can also be set in a mode that only
explicitly declared variables can be used with the command Jption Explicit.



DATA TYPE SUMMARY
Visual Basic recognize Iollowing six types oI variables as Numeric, String, Boolean, Date,
Object, Variant.

ike other Programming anguage Visual Basic provide Numeric Variables. They are:-
Integers, Single, double, Byte, ong, Currency
Integer Variables are used Ior the Non Fractional Values. It stores values in the range Irom
32768 to 32767. ong Data type is used Ior the range 2147483648 to 2147483647. Single
Data Type is used Ior Fractional Values Irom 3.402 e 38 to 1.40 e 45. Double Precision
Floating Point Numbers is capable oI containing values Irom 1.797 e 308 to 4.940 e 324 and
positive numbers. Currency is used Ior Iixed-point numbers with Iour decimal digits. It can
1

represent numbers in the range 922377203685477.5808 to 922377203685477.5807. Byte data
type is used Ior representing numbers Irom 0 to 255. String variables are used to store string type
data.
BOOLEAN
Boolean Data Type stores True/ False values. Boolean variables are used in testing conditions.
DATE
Date and Time variables are stored internally in a special Iormat, but you don`t need to know the
exact Iormat. Date variables are declared by Iollowing statements.
OB1ECT
An object variable is used to reIer any object in the application they are declared by the object
data type and aIter that they are set to any oI the object in the applications with set command.
VARIANT
Special Types oI Variables declare without any data type treated as variant they are capable oI
containing any type oI value. II one can skidata type in variable declaration statement then
variable will treated as a variant











11










CHAPTER 2
SYSTEM REQUIREMENT








1

REQUIREMENT SPECIFICATION

The Iollowing inIormation is kept in mind beIore designing the system:

Operational information
O Check whether the speciIied book is available or not
O Updating the database oI books and members as and when the book is returned or
issued
O To ensure that the member can take a book only iI no. oI books issued previously is
less that 2.

2 Tactical information
O How many members have not returned the books beIore due date
O Member ship renewal
O How many members have yet to pay the Iine
O To check the condition oI the books
O New memberships

Strategic information
O New books to be ordered
O Increase in membership Iees, number oI books issued, Iine policies etc.

FEASIBILITY ANALYSIS

The direct costs are:
O Cost oI a PC÷ approx. RS 40000/-
O No extra space required
O Recurring costs- electricity, maintenance
The system can be implemented by a programmer within 2 months which includes
system design, implementation, testing and trial runs.



1

Immediate benefits:
O ots oI time will be saved as searching will become more easier.
O Issuing, renewal oI books will be quicker.
O Better service & student satisIaction.
O Accurate, reliable and up-to-date strategic, tactical, & operational inIormation
which insures better management & thereby increase proIits.

The direct beneIits i.e. delay in collecting Iines, saving due to increasing volume oI work with
the same human resources will repay the cost oI installing the computer within Iour months.


HARDWARE AND SOFTWARE REQUIREMENTS
Hardware
O Pentium II
O 128 MB RAM
O 20 GB
O Writable CD ROM Ior backup
O 1.44 MB Iloppy drive


Software
O Windows NT
O Visual Basic 6
O MS OIIice





1







CHAPTER
SYSTEM ANALYSIS











13

REQUIREMENT DETERMINATION

The library is interest in updating its present computer system. Issues and receipts oI the book to
the members is the subsystem oI this.
The problem Iaced by the issue section, members and the librarian are:
O A member doesn`t know iI a particular book can be currently issued or not.
O What books are held by the given members
O Who are the members having the books Ior more than speciIied time
O Unpaid Iines

Hence the developed system should meet all these requirements

REQUIREMENT SPECIFICATION

The Iollowing inIormation is kept in mind beIore designing the system:

4 Operational information
O Check whether the speciIied book is available or not
O Updating the database oI books and members as and when the book is
returned or issued
O To ensure that the member can take a book only iI no. oI books issued
previously is less that 2.

Tactical information
O How many members have not returned the books beIore due date
O Member ship renewal
O How many members have yet to pay the Iine
O To check the condition oI the books
O New memberships

Strategic information
1

O New books to be ordered
O Increase in membership Iees, number oI books issued, Iine policies etc.

FEASIBILITY ANALYSIS

The direct costs are:
O Cost oI a PC÷ approx. RS 19000/-
O No extra space required
O Recurring costs- electricity, maintenance
The system can be implemented by a programmer within 2 months which includes
system design, implementation, testing and trial runs.
Immediate benefits:
O ots oI time will be saved as searching will become more easier.
O Issuing, renewal oI books will be quicker.
O Better service & student satisIaction.
O Accurate, reliable and up-to-date strategic, tactical, & operational inIormation
which insures better management & thereby increase proIits.
The direct beneIits i.e. delay in collecting Iines, saving due to increasing volume oI work with
the same human resources will repay the cost oI installing the computer within Iour months.
DATA DICTIONARY

Book Record:
Book ID, Book name, Publisher name, author, place oI publication, copyright year,
purchase price, pages.

Member/Employee Record:
Employee ID, member ID, name, address, tel. no., email, date oI joining, date oI
expire, books in hand, Iine balance.



17

SYSTEM DESIGN

Database Design
Books database
Book ID, Book name, Publisher name, author, place oI publication, copyright year,
purchase price, pages.
Member Database
Employee ID, member ID, name, address, tel. no., email, date oI joining, date oI
expire, books in hand, Iine balance.
Books Issued Database
Member ID, member name, books in hand, book1 ID, book2 ID, date oI return1, date
oI return2.
Administration Database
Name, password.

DATA INPUT & OUTPUT METHOD
Input Method
The data entering process is online as the data is entered at the time oI transaction. Any
change in either oI the Iorms is directly updated in the database.
The computer prompts the data entry operator (here the librarian) with menu,
commands, and forms which is displayed on the VDU.
As the project is run the login Iorm is displayed.
When the correct password is entered along with the login name, the menu Iorm gets
loaded and according to the task that has to be perIormed, diIIerent templates related
to the books or member inIormation can be opened.
All the Iorm layouts can be seen in the Iollowing pages.


1

Output Method

The student, books or staII details can be directly printed Irom the database or can be
viewed on the screen.

PROCEDURE DESCRIPTION
The member searches Ior a particular book and brings it to the librarian. To know whether a
particular book is available or not, issued or not the librarian can be consulted.
When a particular book is Iound by the member, the librarian checks the various details oI the
members Irom the database. The book ID and the date oI returning is entered into it and the
status oI the book is automatically updated in the books` database.
II the member returns the book aIter the date oI expiry, the Iine is to be paid and the
Iine report is generated.




TEST PLAN
Here, we used the details Irom the procedure description to evolve a test plan.
O Enter wrong author, call ID or book title and see the response.
O Enter the correct details oI the above and see the response.
O Try to issue a book which is not available at present.
O Enter a wrong member id to issue a book and see the response.






1

PROCESS SPECIFICATION

Structured English

While the member record is existing do
If the book is available at present
For issuing book
Search member database using member id
If the no. oI book ·÷ 2 then
Issue the book
Makes changes in member and books database
exit
else
Write¨book cant be issued¨
End if
End if
End while









Decision table














CondlLlon 1ť member record
exlsL
CondlLlon ť book ls avallable
ln Lhe llbrary aL presenL
CondlLlon ť noŦ of booksƼƹ
8ule 1 8ule 8ule 8ule
?es no ?es ?es

?es ŴŴŴ no ?es


AcLlon 1ť book ls lssued
1









CHAPTER 4
PROCESS DESCRIPTION















Process Description
The ibrary Management System is designed & developed Ior a receipt and issuance oI books in
the library along with the student`s details. The books received in the library are entered in
Books Entry Iorm and the new student is entered in the student entry Iorm. When the student
wants to get the desired book the same is issued on the availability basis to the student. The
issuance and due date Ior the returning oI the book is also entered into the Book Issue Iorm under
third menu Book Issue. The student has to pay the Iine iI any on the basis oI no. oI days delayed
deposit oI the book in the library.

Project Details
In this project a login screen appears which ask the user/liberian to enter the username and
password aIter success oI correct username and password a MDI Iorm appears which has many
drop down menus which you can select the diIIerent options as per the use or requirement oI the
user.

Project Working
The whole project is divided into diIIerent sections and these sections are Iurther in diIIerent
subparts each oI which perIorm some speciIic Iunctions.
These parts are the Iorms which require some inIormation Irom the user most oI the time and
maintain a record in database in background.
These sections are shown and explained below.Sequentially they maintain the Iollwing sequence
in the project.
.Login Form
2.MDI Form
.Catalogue
(a)Search





4.Database
(a)Members
(b)Employees
(c)Options
.Transaction
(a)Issue
(b)PayIine
.Reports
(a)Fine paid reports
7.UserMaster
8.Exit
et us elaborate each section one by one.For more schematic view screenshots has been used so
that report can be more realistic.














.Login Form
This is the token oI entry in the project or we can say only authorised like liberian who can make
changes can enter in the project system.It contains two Iields username and password
embedded with OK and CANCE button.II login is successIul a prompt screen appears which
prompts 'Login Success¨.
The screenshot oI such login screen is shown below




3

2.MDI Form: AIter successIul completion oI login process you will be automatically redirected
to MDI Iorm section with a heading 'Apeejay ibrary Welcomes You¨.You can see here many
drop down menus with headings like drag-drop menus.You can select diIIerent options as per the
requirement.







.Catalogue
This is Iirst category which is located in MDI Iorm .It consist oI only one option.It signiIies the
books avilable in the library.It has one option only named as Search.
(aSEARCH
This search option contain a drop down where you can select the search option i.e. how search
has been perIormed.It has three options search by ID,search by Title and search by Author and
you can search as per your need.


4.Database
The database has been given such that the user can create,update,edit or delete enteries Irom the
table oI the database.The work on database has been done speciIically Ior diIIerent types oI
people so we maintain diIIerent subsections which is made to operate on the database enteries oI
that speciIic type oI people.
These subsections are:
(a)Members
(b)Employees
(c)Options
7

(aMembers:- This option Iaclitate the user to create,edit,update and delete the data oI members
specially students in this context.


(bEmployees:- Employees are the intereem part oI a institution.From Director to Peon all are
employees thereIore they can borrow the books Irom library too.There records are maintained
seprately.The enteries can be created,updated,edited or deleted through add,edit,delete ,close
buttons.
The screenshots can be seen on next page:



(cOptions:-This is the special utility Ior librarian which reminds him the constraints Ior a
employee/member like maximum no. book can be issued,Max duration Ior a book,Maxmium
card renewal Iees etc.



.Transactions:-This section deals with all the transactions which occur in the library
system.This includes Irom issuing the book to paying Iine when the books are not returned in
schduled time.It contains two Ieatures:
(a)Issue
(b)PayIine
(aIssue:This subsection allows user to issue book to members and also to return and renew the
book.It also tells about about any upholding Iine.








(bPayfine:-
This section is use to pay Iines oI members and employers collectively.It has Iew Iields like
existing member id.Member InIormation covers Member name,Fine balance and books in hand.
The Ior has embedded buttons exit and payIine which can be used as per your choice.











1

.Usermaster:-Usermaster is like user control panel which use give power to user to add new
members and delete existing members via username and passwords.

7.Exit:- This is used to exit Irom the whole project























CHAPTER 5
DATA FLOW













Data flow diagram:-
A data flow diagram (DFD) is a graphical representation oI the "Ilow" oI data through an
inIormation system, modelling its process aspects. OIten they are a preliminary step used to
create an overview oI the system which can later be elaborated. DFDs can also be used Ior the
visualization oI data processing (structured design).
A DFD shows what kinds oI data will be input to and output Irom the system, where the data will
come Irom and go to, and where the data will be stored. It does not show inIormation about the
timing oI processes, or inIormation about whether processes will operate in sequence or in
parallel (which is shown on a Ilowchart).
Characterst|cs of DIDťŴ
O It is common practice to draw the context-level data Ilow diagram Iirst, which shows the
interaction between the system and external agents which act as data sources and data
sinks. On the context diagram the system's interactions with the outside world are
modelled purely in terms oI data Ilows across the system boundary. The context diagram
shows the entire system as a single process, and gives no clues as to its internal
organization.
O This context-level DFD is next "exploded", to produce a evel 0 DFD that shows some
oI the detail oI the system being modeled. The evel 0 DFD shows how the system is
divided into sub-systems (processes), each oI which deals with one or more oI the data
Ilows to or Irom an external agent, and which together provide all oI the Iunctionality oI
the system as a whole. It also identiIies internal data stores that must be present in order
Ior the system to do its job, and shows the Ilow oI data between the various parts oI the
system.
O Data Ilow diagrams were proposed by arry Constantine, the original developer oI
structured design, based on Martin and Estrin's "data Ilow graph" model oI computation.
O Data Ilow diagrams (DFDs) are one oI the three essential perspectives oI the structured-
systems analysis and design method SSADM. The sponsor oI a project and the end users
will need to be brieIed and consulted throughout all stages oI a system's evolution. With a
data Ilow diagram, users are able to visualize how the system will operate, what the
system will accomplish, and how the system will be implemented. The old system's
dataIlow diagrams can be drawn up and compared with the new system's data Ilow
diagrams to draw comparisons to implement a more eIIicient system. Data Ilow diagrams
can be used to provide the end user with a physical idea oI where the data they input
ultimately has an eIIect upon the structure oI the whole system Irom order to dispatch to
report. How any system is developed can be determined through a data Ilow diagram.
O In the course oI developing a set oI levelled data Ilow diagrams the analyst/designers is
Iorced to address how the system may be decomposed into component sub-systems, and
to identiIy the transaction data in the data model.
O There are diIIerent notations to draw data Ilow diagrams (Yourdon & Coad and Gane &
Sarson), deIining diIIerent visual representations Ior processes, data stores, data Ilow, and
external entities.




3





DATA FLOW DIAGRAM OF LIBRARY MANAGEMENT SYSTEM

Llbrarlan
8ooks
Members/SLaff
Members/SLaff
lssues book only
lf avallable Ǝ
checks wheLher
member can
Lake Lhe book or
noL
8ooks
8ook
Sllp

Llbrary
1lckeLs
PhysicaI DFD
Logical DFD
7


Member
8CCkS

lSSuL 1
SLaff
8lLLlnC

S?S1LM
AuMlnlSŴ
18A1lCn

Llbrarlan
8eLurns books
8eLurns books
lssues books lssues books
lf
avallable
paymenLs
llne
Lo
be
pald
lf books noL reLurned
aL proper Llme
verlflcaLlon of flne pald
noLlfles Lhe
pendlng flne
Membershlp fees for
renewal/new membershlp
new members
upgradaLlon of books



Member
8CCkS

lSSuL 1
SLaff
8lLLlnC

S?S1LM
AuMlnlSŴ
18A1lCn

Llbrarlan
8eLurns books
8eLurns books
lssues books lssues books
lf
avallable
paymenLs
llne
Lo
be
pald
lf books noL reLurned
aL proper Llme
verlflcaLlon of flne pald
noLlfles Lhe
pendlng flne
Membershlp fees for
renewal/new membershlp
new members
upgradaLlon of books



Llbrarlan

Members
Ll88A8?

MAnACLMLn1

SLaff
noLlfles
order of
new books
by
members/
sLaff
uaLa of
membersţ
books and
sLaff
noLlfles new
members
lssues
books
flnes
8eLurns
paymenLs
lssues 8eLurns
%%
DIAGRAM


ENTITY RELATIONSHIP DIAGRAM:In soItware engineering, an entity-
relationship model (ERM) is an abstract and conceptual representation oI data. Entity-
relationship modeling is a database modeling method, used to produce a type oI conceptual
schema or semantic data model oI a system, oIten a relational database, and its requirements in a
top-down Iashion. Diagrams created by this process are called entity-relationship diagrams,
ER diagrams, or ERDs.


8ooks
Member/SLaff
8eLur
ned

lssue
8ook luţ LlLleţ
auLhorţ name Ǝ
place of publlsherţ
pages Ǝ prlce
8ook luţ
Member
luţ uaLe of
8eLurn
8ook luţ
Member
luţ noŦ of
8ooks
Member luţ
nameţ Addressţ
1elŦ noŦţ eŴmall
39i9y-reIa9io3ship diagram
1

PROCESS FLOW DIAGRAM:-

LCGIN ICkM

InputťUsername

Þassword (Unmatched)



(Matched)












LCGIN ICkM

MDI ICkM
LkkCk
8ack 1o Log|n
MDI ICkM
Cata|ogue Database
1ransact|on
keports Cata|ogue
LxlL

O username should be unlque
O 9assword should conLaln
aLleasL one speclal
characLer




CA1ALCGUL MCDULL
OR
CaLalogue
Search
Search by
lu
Search by
AuLhor
Search by
1lLle
Search
uslng
Sllder












DA1A8ASL MCDULL
W Members
Member lu
name
Inputs
8ooks ln Pand
llne
uaLabase
Members Lmployees
CpLlons
Members
Constra|nts
WMember lu should be Alphanumerlc
Wname should be of 1 CharacLesŦ
Wllne fleld musL be numerlcŦ
CuLpuL
uaLa
added
uaLabase












O LMÞLC¥LLS
W CperaLlons performed on uaLabase
Lmployees
uaLabase
Add
LdlL
ueleLe
Save
llrsL name
Lmp lu
LasL name
Inputs
Constra|ntsť
WLmpID shou|d be a|pha
numer|c
uaLa added Lo
Lmployee
Database
1able 1



3



1kANSAC1ICN MCDULL

1ransacLlons
W Member`s Information
Inputs
W Book Information
lSSuL
WMember lu
WMember name
W8ooks ln hand
Wllne
W1lLle
W8ooklu
W8eLurn uaLe
Constra|ntsť
WMember lu should be
alphanumerlc
W8ook lu should numerlc
W8eLurn daLe ln dd/mm/yy formaL
8ook lssued
uaLabase
1able 1




9ay llne Module
W lnpuLs
Þay I|ne Modu|e
Þay I|ne
WMember ID
WMember Name
WI|ne 8a|ance
W8ooks In nand
ConsLralnLsť
WMember lu should be alphanumerlc
Wllne 8alance numerlc
uaLabase
1able 1

llne 9ald 8eporLs
ConsLralnLs
W 8eporL should be ln MS Lxcel lormaL
8eporLs
llne 9ald
reporLs
Cpen daLa
reporL
uaLabase
8eporL

7

userMasLer
W I|e|ds
userMasLer
username
9assword
LdlL
updaLe
LxlL

ConsLralnLsť
O username should be unlqueŦ
O 9assword Alphanumerlc
uaLabase


LxlL
LxlL
1ermlnaLe Lhe
program






















CHAPTER
CODING









3

GENRAL
Option Explicit
Dim con As ADODB.Connection
Dim rs As ADODB.Recordset
Private Sub Adodc1¸WillMove(ByVal adReason As ADODB.EventReasonEnum, adStatus As
ADODB.EventStatusEnum, ByVal pRecordset As ADODB.Recordset)

End Sub
Command
Private Sub Command1¸Click()
Unload Me
End Sub
LOGIN PAGE
Set con ÷ CreateObject("Adodb.connection")
con.Provider ÷ "MicrosoIt.jet.oledb.4.0"
con.Open App.Path & "\DB1.mdb"

Dim strsql As String
strsql ÷ "Select * Irom USERMAST"
Set rs ÷ New ADODB.Recordset
rs.Open strsql, con, adOpenForwardOnly, adockOptimistic
Dim chkPassword

While Not rs.EOF
II txtusername ÷ rs.Fields("NAME") And txtpassword ÷ rs.Fields("PASSWORD") Then
chkPassword ÷ "PASSWORD"
31

rs.MoveNext
Wend

II chkPassword ÷ "PASSWORD" Then
MDIForm1.Show
Unload Me
con.Close



Else
MsgBox "Invalid Password, try again!", , "PCI ogin"
SendKeys "¦Home}¹¦End}"
End II
End Sub
MDI FORM>CATALOGUE>SEARCH
Private Sub mnuauthor¸Click()
search.Show
End Sub
SEARCH:-
Private Sub search¸Click()
II Not Adodc1.Recordset.EOF And Not Adodc1.Recordset.BOF Then
Adodc1.Recordset.MoveFirst
While Not Adodc1.Recordset.EOF
II Combo1.Text ÷ "ID NO" Then
3

II Val(Text1.Text) ÷ Adodc1.Recordset.Fields("id") Then
MsgBox ("record Iound")
GoTo X
Else
Adodc1.Recordset.MoveNext
End II

ElseII Combo1.Text ÷ "Title" Then
str1 ÷ Case(Trim(Text1.Text))
str2 ÷ Case(Trim(Adodc1.Recordset.Fields("Title")))
II InStr(1, str2, str1, vbBinaryCompare) ~ 0 Then
MsgBox ("record Iound")
GoTo X
Else
Adodc1.Recordset.MoveNext
End II

Else
Combo1.Text ÷ "author"
str1 ÷ Case(Trim(Text1.Text))
str2 ÷ Case(Trim(Adodc1.Recordset.Fields("author")))
II InStr(1, str2, str1, vbBinaryCompare) ~ 0 Then
MsgBox ("record Iound")
GoTo X
Else
3

Adodc1.Recordset.MoveNext
End II

End II
Wend
End II

MsgBox ("record not Iound")
Adodc1.ReIresh

X:
End Sub

MDI FORM>DATABASE>MEMBER>Add
Private Sub Command1¸Click()
II Command1.Caption ÷ "&Add" Then
Adodc1.Recordset.AddNew
For i ÷ 0 To 8 Step 1
txtFields(i).ocked ÷ False
Next
Command1.Caption ÷ "&Save"
Else
II Not IsDate(txtFields(3)) Then
MsgBox "invalid date oI joining entered"
GoTo X
3

End II
Adodc1.Recordset.Update
Adodc2.Recordset.AddNew
Adodc2.Recordset.Fields("member¸id") ÷ Val(txtFields(0).Text)
Adodc2.Recordset.Update
For i ÷ 0 To 8 Step 1
txtFields(i).ocked ÷ False
Next

Command1.Caption ÷ "&Add"
End II
X:
End Sub
MDI FORM>DATABASE>MEMBER>Edit
Private Sub Command2¸Click()
II Command2.Caption ÷ "&Edit" Then
For i ÷ 0 To 8 Step 1
txtFields(i).ocked ÷ False
Next
Command2.Caption ÷ "&Save"
Else
II Not IsDate(txtFields(3)) Then
MsgBox "invalid date oI joining entered"
GoTo X
End II
33


Adodc1.Recordset.Update
For i ÷ 0 To 8 Step 1
txtFields(i).ocked ÷ False
Next
Command2.Caption ÷ "&Edit"
End II
X:

End Sub



MDI FORM>DATABASE>MEMBER>Delete
Private Sub Command3¸Click()
Adodc1.Recordset.Delete
End Sub
MDI FORM>DATABASE>EMPLOYEE>Add
Private Sub cmdAdd¸Click()
Adodc1.Recordset.AddNew
End Sub
MDI FORM>DATABASE>EMPLOYEE>Edit
Private Sub cmdEdit¸Click()
Adodc1.Recordset.Update
End Sub
3

MDI FORM>DATABASE>EMPLOYEE>Delete
Private Sub cmdDelete¸Click()
Adodc1.Recordset.Delete
End Sub
MDI FORM>DATABASE>EMPLOYEE>Save
Private Sub cmdsave¸Click()
Adodc1.Recordset.Save
End Sub

MDI FORM>TRANSACTION>ISSUE>Issue
II Adodc2.Recordset.Fields("status") ÷ "na" Then
MsgBox "book not available"
GoTo Q
End II
II Text10.Text ÷ "" Then
Text10.Text ÷ Combo2.Text
Text8.Text ÷ Text4.Text
Text2.Text ÷ Val(Text2.Text) ¹ 1
Adodc1.Recordset.Fields("bookinhand") ÷ Val(Text2.Text)
Adodc3.Recordset.Fields("bookid1") ÷ Val(Text10.Text)
Adodc3.Recordset.Fields("ret¸date1") ÷ DateValue(Text8.Text)
Adodc2.Recordset.Fields("status") ÷ "na"
Adodc3.Recordset.Update
Adodc1.Recordset.Update
MsgBox Adodc2.Recordset.Fields("id")
37

Adodc2.Recordset.Update
ElseII Text9.Text ÷ "" Then
Text9.Text ÷ Combo2.Text
Text7.Text ÷ Text4.Text
Text2.Text ÷ Val(Text2.Text) ¹ 1
Adodc1.Recordset.Fields("Bookinhand") ÷ Val(Text2.Text)
Adodc3.Recordset.Fields("bookid2") ÷ Val(Text9.Text)
Adodc3.Recordset.Fields("ret¸date2") ÷ DateValue(Text7.Text)
Adodc3.Recordset.Update
Adodc1.Recordset.Update
End II

Q:
End Sub
MDI FORM>TRANSACTION>ISSUE>Return
II Combo2.Text ÷ Adodc3.Recordset.Fields("bookid1") Then
Text10.Text ÷ ""
Text8.Text ÷ ""
Text2.Text ÷ Val(Text2.Text) - 1
Adodc1.Recordset.Fields("bookinhand") ÷ Val(Text2.Text)
Adodc3.Recordset.Fields("bookid1") ÷ ""
Adodc3.Recordset.Fields("ret¸date1") ÷ ""

Adodc2.Recordset.Fields("status") ÷ "available"
Adodc3.Recordset.Update
3

Adodc1.Recordset.Update
MsgBox Adodc2.Recordset.Fields("id")
Adodc2.Recordset.Update
ElseII Combo2.Text ÷ Adodc3.Recordset.Fields("bookid2") Then
Text9.Text ÷ ""
Text7.Text ÷ ""
Text2.Text ÷ Val(Text2.Text) - 1
Adodc1.Recordset.Fields("bookinhand") ÷ Val(Text2.Text)
Adodc3.Recordset.Fields("bookid2") ÷ Text9.Text
Adodc2.Recordset.Fields("status") ÷ "available"
Adodc3.Recordset.Update
Adodc1.Recordset.Update
MsgBox Adodc2.Recordset.Fields("id")
Adodc2.Recordset.Update
Else
MsgBox "invalid book id"
End II
End Sub

MDI FORM>TRANSACTION>ISSUE>Renew
Private Sub Command3¸Click()
II Combo2.Text ÷ Adodc3.Recordset.Fields("bookid1") Then
Text8.Text ÷ DateValue(Text4.Text)
Else
Text8.Text ÷ DateValue(Text4.Text)
3

End II
End Sub
MDI FORM>REPORTS>Fine paid reports
Private Sub mnuIpr¸Click()
oad DataReport1
DataReport1.Show
End Sub
MDI FORM>USERMASTER
Private Sub mnuusermaster¸Click()
usermaster.Show
End Sub

MDI FORM>EXIT
Private Sub exit¸Click()
Unload Me
End Sub



























CHAPTER 7
CONCLUSION
&
FUTURE SCOPE



1




CONCLUSION:
From a proper analysis oI positive points and constraints on the component, it can be saIely
concluded that the product is a highly eIIicient GUI based component. This application is
working properly and meeting to all user requirements. This component can be easily plugged in
many other systems

Future Scope

FUTURE SCOPE OF APPLICATION :
This application can be easily implemented under various situations.We can add new Ieatures as
and when we require. Reusability ispossible as and when require in this application. There is
Ilexibilityin all the modules.

SOFTWARE SCOPE:
· Extensibility: This soItware is extendable in ways that its originaldevelopers may not expect.
The Iollowing principles enhancesextensibility like hide data structure, avoid traversing multiple
links or methods, avoid case statements on object type anddistinguish public and private
operations.
· Reusability: Reusability is possible as and when require in thisapplication. We can update it
next version. Reusable soItwarereduces design, coding and testing cost by amortizing eIIort
over several designs. Reducing the amount oI code alsosimpliIies understanding, which increases
the likelihood that the code is correct. We Iollow up both types oI reusability: Sharing oI newly
written code within a project and reuse oI previously written code on new projects.
· Understandability: A method is understandable iI someone other than the creator oI the
method can understand the code (as well as the creator aIter a time lapse). We use the method,
which small and coherent helps to accomplish this.
· Cost-effectiveness: Its cost is under the budget and make within given time period. It is
desirable to aim Ior a system with a minimum cost subject to the condition that it must satisIy the
entire requirement.
Scope oI this document is to put down the requirements, clearly identiIying the inIormation
needed by the user, the source oI the inIormation and outputs expected Irom the system.

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close