BOOK BANK MANGEMENT SYSTEM

PREPARED BY STUDENTS OF CSE (AI&ML)-B

1) HARASHITHA – (227Z1A6679)
2) NIKSHITHA – (227Z1A6676)
3) VIJAY – (227Z1A6677)
4) MAHESH – (227Z1A6678)

SUBMITTED TO :

MS. BABINA ELANGBAM

ASSISTANT PROFESSOR

SIGNATURE
EX NO:
DATE:

BOOK BANK MANAGEMENT SYSTEM

AIM
To develop a project of Book bank management system using Rational Rose
Software and to implement the software in Visual Basic.

PROBLEM ANALYSIS AND PROJECT DESIGN

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.

SOFTWARE REQUIREMENT SPECIFICATION

S.NO CONTENTS
1 INTRODUCTION
.
2 OBJECTIVE
.
3 OVERVIEW
.
4 GLOSSARY
.
5 PURPOSE
.
6 SCOPE
.
7 FUNCTIONALITY
.
 8 USABILITY
.
9 PERFORMANCE
.
1 RELIABILITY
0
FUNCTIONAL REQUIREMENTS
1 EXTERNAL
1 INTERFACE
.
REQUREMENT

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 are 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 and
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.
DATABASE Database is used to store the details
of
members and books.
ADMINISTRATOR The one who verifies the availability
of
book and issue them
USER Member

SOFTWARE This software specification documents

full
REQUIREMENT set of features and function for online

SPECIFICATION recruitment system that is performed in

company website.

5. PURPOSE
The purpose of the book bank management system is to reduce the manual
intervention .
6. SCOPE
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
 withcorrect information and day-to-day update of information.
11. FUNCTIONAL REQUIREMENTS
Functional requirements are those refer to the functionality of the system.
That is the services that are provided to the member who borrows book.

12. EXTERNAL INTERFACE REQUIREMANTS

SOFTWARE REQUIREMENTS
Front end: IBM rational rose enterprise edition.
Back end: visual basic 8.0.
HARDWARE REQUIREMENTS
Processor : pentium 4.
RAM : 256 mb
Operating syatem : Microsoft windows xp.
Free disk space : 1gb

UML DIAGRAMS
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

USE CASE 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.

registratio
n

student1
year selection

select books

databas e1

updatio
n

authentic ations

adminis trators
verific ation

iss ues

DOCUMENTATION OF USE CASE DIAGRAM

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.

DOCUMENTATION OF CLASS DIAGRAM

This class diagram has 8 classes:
• 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.
st nd
• Year-is the class name. Its attribute is year selection. Its operations are 1 year,2
rd th
year, 3 year,4 year.
st
• Issue for 1 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
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction
diagram that shows how processes operate with one another and in what order. It is a
construct of a Message Sequence Chart. There are two dimensions.
1. Veritcal dimension-represent time.
2. Horizontal dimension-represent different objects.

student
student dattaba
da abasse
e admi ni s trators

regi s trat ion

year s el ec ti on

book s elec t ion

updation

authentication

verification

issue the book

DOCUMENTATION OF SEQUENCE DIAGRAM

The sequence diagram describes the sequence of steps to show

• The member registers himself in book bank
• He will select the year
• He select the books given and the database will update the status of book.
• Then administrator will log in and verify the status of books.
• If the book is available he will issue the book.

COLLABRATION DIAGRAM
A collaboration diagram, also called a communication diagram or interaction
diagram,. A sophisticated modeling tool can easily convert a collaboration diagram into a
sequence diagram and the vice versa. A collaboration diagram resembles a flowchart that
portrays the roles, functionality and behavior of individual objects as well as the overall
operation of the system in real time
2: y ear select ion

s
t udent admi ni s
t r ators

1: regi st rat
i on
3: book s elec
t i on

4: updat ion

dat abas
e

DOCUMENTATION OF COLLABORATION 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.

STATE CHART DIAGRAM

The purpose of state chart diagram is to understand the algorithm involved in
performing a method. It is also called as state diagram. A state is represented as a round box,
which may contain one or more compartments. An initial state is represented as small dot. An
final state is represented as circle surrounding a small dot.
DOCUMENTATION OF STATE CHART DIAGRAM
This state diagram describes the behavior of the system.
• In the first state the member registers himself in book bank
• After that he will select the year in next state.
• In the next state he will select the books.
• In the next state database will update the status of book.
• In the next state administrator will log in.
• After authentication he will verify the availability of book.
• If available he will issue the book.

ACTIVITY DIAGRAM
Activity diagrams are graphical representations of workflows of stepwise activities and
actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step-by-step
workflows of components in a system. An activity diagram shows the overall flow of control.
An activity is shown as an rounded box containing the name of the operation.

registration
issue book

year verification
selection

select updation authent ic at

books ion
DOCUMENTATION OF ACTIVITY DIAGRAM
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 component diagram's main purpose is to show the structural relationships between the
components of a system. It is represented by boxed figure. Dependencies are represented by
communication association

book bank
managem... issue for
member 4th year
details

issue for issue for

2nd year 3rd year
1st year
DOCUMENTATION OF 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.

BOOK BANK

issue for issue for issue for issue for member

1st year 2nd year 3rd year 4th year details
DOCUMENTATION OF DEPLOYMENT
DIAGRAM
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
A package diagram in unified modeling language that depicts the dependencies
between the packages that make up a model. A Package Diagram (PD) shows a grouping
of elements in the OO model, and is a Cradle extension to UML. PDs can be used to
show groups of classes in Class Diagrams (CDs), groups of components or processes in
Component Diagrams (CPDs), or groups of processors in Deployment Diagrams (DPDs).
There are three types of layer. They
are

user
interface
layer

web
member details

domain
layer
register book issues

t ec hnica
l lay er

authent ic ation verific at ion databas e

DOCUMENTATION OF PACKAGE DIAGRAM

The three layers in the online recruitment system are
• 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.
RESULT

Thus the project to develop book bank management system using Rational
Rose Software and to implement the software in Visual Basic was done successfully.