2 Book Bank Management System PDF
2 Book Bank Management System PDF
AIM
To develop a project of Book bank management system using Umbrello Tool and to
implement in Visual Basic.
The book bank management system is an software in which a member can register
themselves and then he can borrow books from the book bank. It mainly concentrates on
providing books for engineering students.
PROBLEM STATEMENT
The process of members registering and purchasing books from the book bank are
described sequentially through following steps:
First the member registers himself if he was new to the book bank.
Old members will directly select old member button.
They select their corresponding year.
After selecting the year they fill the necessary details and select the book and he
will be directed towards administrator
The administrator will verify the status and issue the book.
1 INTRODUCTION
2 OBJECTIVE
3 OVERVIEW
4 GLOSSARY
5 PURPOSE
6 SCOPE
7 FUNCTIONALITY
8 USABILITY
9 PERFORMANCE
10 RELIABILITY
1. INTRODUCTION
This system would be used by members who are students of any college to check the
availability of the books and borrow the books, and then the databases are updated. The
purpose of this document is to analyze and elaborate on the high-level needs and features of
the book bank management system. It also tells the usability, reliability defined in use case
specification.
2. OBJECTIVE
The main objective of the system was to design an online book-bank monitoring
system to enable a central monitoring mechanism of the book-bank be more faster and less
error prone. Apart from this,
To help the students acquire the right books for the syllabus at the right time.
To ensure availability of basic textbooks to students against limited funds
To develop students ability to handle property loaned to them
3. OVERVIEW
The overview of this project is to design a tool for book bank so that it can be used by
any book banks to lend their books as well as colleges.
4. GLOSSARY
TERMS DESCRIPTION
MEMBER The one who registers himself and purchase books from the
bank.
ADMINISTRATOR The one who verifies the availability of book and issue them
USER Member
5.PURPOSE
The purpose of the book bank management system is to reduce the manual
intervention .
The scope of this book bank management system is to act as a tool for book bank
administrator for quick reference, availability of the books.
7.FUNCTIONALITY
Many members will be waiting to take the book from the book bank at a single day.
To serve all the members
8.USABILITY
User interface makes the Recruitment system to be efficient. That is the system will
help the member to register easily and helps them to get their books easily. The system
should be user friendly.
9. PERFORMANCE
It describes the capability of the system to perform the recruitment process of the
applicant without any error and performing it efficiently.
10. RELIABILITY
The book bank management system should be able to serve the applicant with correct
information and day-to-day update of information.
Functional requirements are those refer to the functionality of the system. That is the
services that are provided to the member who borrows book.
SOFTWARE REQUIREMENTS
HARDWARE REQUIREMENTS
Processor : pentium 4.
RAM : 256 mb
Operating system : Microsoft windows xp
Free disk space : 1gb
The following UML diagrams describe the process involved in the online recruitment
system
• Use case diagram
• Class diagram
• Sequence diagram
• Collaboration diagram
• State chart diagram
• Activity diagram
• Component diagram
• Deployment diagram
• Package diagram
A use case is a methodology used in system analysis to identify, clarify, and organize
system requirements. The use case is made up of a set of possible sequences of interactions
between systems and users in a particular environment and related to a particular goal. It is
represented using ellipse. Actor is any external entity that makes use of the system being
modeled. It is represented using stick figure.
The actors in this use case diagram are member and database. The use cases are the
activities performed by actors.
• The member will register himself in the book bank.
• After registration he will select the year to which he belongs
• After selecting he will select books
• Database will verify the status of book and the books will be given.
CLASS DIAGRAM
A class diagram in the unified modeling language (UML) is a type of static structure
diagram that describes the structure of a system by showing the system's classes, their
attributes, and the relationships between the classes. It is represented using a rectangle with
three compartments. Top compartment have the class name, middle compartments the
attributes and the bottom compartment with operations.
Member details class- is the class name. Its attributes are name, father name, date of
birth, address, phone number, member id, college, degree, course and semester. Its operations
are registration, authentication, and year selection.
Administrator- is the class name. Its attributes are name, address, phone, mail id. Its
operations are authentication, verification and issue books.
Year-is the class name. Its attribute is year selection. Its operations are 1st year,2nd
year, 3rd year,4th year.
Issue for 1st year-is the class name. Its attributes are member code, member name,
book code, book name, and quantity. Its operation is issue.
Issue for 2nd year-is the class name. Its attributes are member code, member name,
book code, book name, and quantity. Its operation is issue
Issue for 3rd year-is the class name. Its attributes are member code, member name,
book code, book name, and quantity. Its operation is issue
SEQUENCE DIAGRAM
COLLABRATION DIAGRAM
The collaboration diagram is to show how the member registers himself and borrow
the book from the book bank. Here the sequence is numbered according to the flow of
execution.
This activity diagram flow of stepwise activities performed in book bank management
system.
• The member registers himself in book bank
• After that he will select the year.
• He will select the books.
• Database will update the status of book.
• Database will update the details
• Then the administrator will log in to his account.
• After authentication he will verify the availability of book.
• If available he will issue the book.
COMPONENT DIAGRAM
The main component in this component diagram is online book bank management
systems. And member details, issue for first year, issue for second year issue for third year
and issue for fourth year are components comes under the main component
DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the physical
deployment of artifacts on deployment targets. Deployment diagrams show "the allocation of
artifacts to nodes according to the Deployments defined between them. It is represented by 3-
dimentional box. Dependencies are represented by communication association.
The processor in this deployment diagram is the book bank which is the main part and
which are the some of the main activities performed in the system. And issue for first year,
issue for second year issue for third year and issue for fourth year are some activities
performed in this system.
PACKAGE DIAGRAM
• The User interface layer - consists of the web and member details. This layer
describes how the member goes to book bank and registers himself..
• The Domain layer – shows the activities that are performed in the book bank
management system. The activities are register and book issues..
• The Technical service layer - the member details and verification details are stored
in the database.
OUTPUT
FORM 1
FORM2
FORM11
Thus the project to develop book bank management system using Umbrello Tool and
to implement in Visual Basic was done successfully.