Vidya Pratishthan’s

ARTS, SCIENCE AND COMMERCE COLLEGE

Baramati, Dist-Pune-413133

A PROJECT REPORT ON

““BLOOD BANK MANAGEMENT SYSTEM”

FOR
Vidya Pratishthan’s

ARTS, SCIENCE AND COMMERCE COLLEGE, BARAMATI.

SUBMITTED TO
UNIVERSITY OF PUNE

BY
GOLANDE PRASHANT VIJAY.

YEAR 2020-21
 CERTIFICATE

This is certify that Golande Prashant Vijay of class S.Y. B.Sc.(CS) has
successfully completed the project “BLOOD BANK MANAGEMENT

SYSTEM” forVidya Pratishthan’s ARTS, SCIENCE AND COMMERCE

COLLEGE, BARAMATI as a part of practical fulfillment of lab course

according to Savitribai Phule Pune University during academic year 2020-

21.

Mrs. Rode R.S Prof. Gajanan Joshi

Project Guide HOD

 INDEX

Sr. No. Topic

1 Introduction of the system
2 Suitable process model for the system.
3 H/W and S/W Requirements ( Front End and Back End S/W’s)
4 Feasibility Study
5 Fact finding techniques
6 UML Diagrams:

1. Use case

2. Class Diagram

3. Activity diagram

4. Sequence diagram

5. Component diagram

6. E-R Diagram
 Introduction to the System:

BLOOD BANK management system is a desktop based application on Java. The purpose of this project was
to develop a blood management information system to assist in the management of blood donor records and
sells record. This project includes mainly two modules i.e. login and main page.
The current system is manual and it is time-consuming. It is also cost-ineffective, and the average return is
low and diminishing.

Objective:

This software helps to easy management of records such as management of blood donors, sells and no. of
blood packets available etc.

Scope:
The project is basically targeted at those people who would like offline management software. To make a
database that is consistent, reliable and secure. To provide correct, complete, ongoing information. To
develop a well-organized information storage system. To make good documentation so as to facilitate
possible future enhancements
 SUITABLE PROCESS MODEL FOR THE SYSTEM

1. Waterfall Model

Advantages

• Easy to understand and implement.

• Testing in each phase.

Documentation Available after each phase.

Most Suitable for single projects where work products are well defined and their

functioning is understood.

Disadvantages

Once detecting error at any face it may be required that the precede subsidy faces may
change.

Very difficult to manage changes b/w the phases there are possibility of blocking which can
slow down the productivity and efficiency of the process.

• Risk is not addressed in this model.

Purpose:

The purpose of this project is to provide a way to manage the quantity of available blood packets, donor and buyer
information, and also provide a easy interface for management.

Project Scope:

The project has a wide scope, as it is not intended to a particular organization. This
project is going to develop generic software, which can be applied by any businesses
organization. More over it provides facility to its users. Also the software is going to
provide a huge amount of summary data.

Proposed System:

The blood bank management system is available in the market that can serve blood
bank owners to easily manage records.
 HARDWARE AND SOFTWARE REQUIREMENTS

1. HARDWARE REQUIREMENTS
a. Processor – 2.0 GHz or above.
b. RAM – 2GB
c. Hard Disk – 160 GB Hard Disk Drive or more.

2. SOFTWARE REQUIREMENTS
a. Operating System – Windows 7/8/10 etc.
b. Programming Language (Front End) – Java
c. Database ( Back End) -Mysql
 FACT FINDING TECHNIQUES

There are different fact finding techniques are available in software engineering to
find the fact of system.
1) Interview
2) Questionnaires
3) Record Review
4) Observation

In our project we use two techniques to find the fact of project.

1) Interview

Interview technique is used to collect information from individuals or from groups.

This method helps to find the areas of misunderstanding, unrealistic, expectations
and future problems of the proposed system. This method is time consuming and
can be very costly if the number of respondent is large and widely distributed.

In our system we take interviews of different stakeholders of the system i.e.

College principal, clerks of college to find out the existing work of the system,
type of leaves, their duration, limit of leaves, which staff uses these leaves.
Who and how these leave records are maintained and stored. Who are the user
of this system and which functions and features they required from the
system.

We have find out the view points of different users, customers involved in the
system.

We have taken a both types of interview – 1) structured and 2) unstructured

interviews.

This technique helps us to find the facts and problems related to the system.
 2) Record Review

Record review provides very valuable information to the analyst about the system
organization and various procedures rules.

We have to use record review technique to find out information about the system.
We study the records like different registers for different staff. Different manually
generated reports daily, weekly, monthly, yearly and the leave forms used by the
staff to take leaves and their leave applications. We also study the UGC rules for
all types of leaves their duration. UGC terms and conditions are also checked.

This technique gives very essential and important information about how it
manages the system.

Note: In our system only two techniques are sufficient to find the fact of system.
Therefore we are not using Questionnaire and Observation techniques.
 FEASIBILTY STUDY
In feasibility study we evaluate cost and benefits of proposed system and on the
basis of study the decision is taken on whether to proceed or postpone the project
or to cancel the project.

1) Technical Feasibility

In technical feasibility we determine available hardware, software and computer

with its configuration i.e. printer, RAM, HD, Database, Operating system and
Programming languages etc.

In existing system we have required computer with configuration (i.e. 512 MB

RAM, 40 GB Hard Disk) Printer, Operating System are already exist and for the
required software (i.e. Database-MySql, Programming Language- Java)
organization is ready to provide that software. Therefore our system is technically
feasible.

2) Operational Feasibility

It find out weather the new technology or proposed system will be suitable using
three types of aspects.
a) Human
b) Organizational
c) Political

Because our system is too large so we only consider human aspects.

Proposed system is user friendly and any user cal easily handles this
system fluently.

Only two hours are sufficient to introduce the system. Therefore no extra training
is required. User manual is also provided. So, our system is operationally
feasible.
 3) Economical Feasibility

Economical Feasibility:
As the necessary hardware and software are available in the market at a low cost, the initial
investment is the only cost incurred and does not need any further enhancements. Hence it is
economically feasible.
 UML DIAGRAMS
USE CASE

Use Case Diagram:

 Use case diagram consists of use cases and actors and shows the interaction between them. The key
points are:

 The main purpose is to show the interaction between the use cases and the actor.

 To represent the system requirement from user’s perspective.

 The use cases are the functions that are to be performed in the module.
2.Class Diagram
3. Activity Diagram
4.Sequence Diagram
5.Component Diagram
6.E-R Diagram