Abstract

Blood is a saver of all existing lives in case of emergency needs. The task of “Save Life” is to receive blood
from various donors, to monitor the blood groups database and to send the required blood during the need
to the hospital in case of emergencies.

The problem is not insufficient number of donors, but finding a willing donor at the right time. We want to
build a network of people who can help each other during an emergency. This application timely updates
the information regarding the donors where the administrator accesses the whole information about blood
bank management system. Donor will be prompted to enter an individual's details, like name, phone
number, and blood group and other credentials.

In the urgent time of a blood requirement, you can quickly check for blood donors matching a particular or
related blood group and reach out to them through the App. Save Life App provides list of blood donors in
area.

A large number of blood donors are attracted using an Android application. Since almost everyone carries
a mobile phone with them, it ensures instant location tracking and communication. Only a registered person,
with willingness to donate blood, will be able to access the service.

This application provides two way communication where in both the hospital blood bank incharge and the
donor both can communicate with each other.

Keywords: Blood bank, Android, Database, Donors, Acceptors, Administrator.

INTRODUCTION
This project acts as an important role in saving life of human beings and which is also its main aim.
The project Android Save Life system is developed so that Hospital can view the information about
registered blood donors such as name, address, and other personal information along with their details
of blood group and other medical information of donor.
The project has a login page where in the user is required to register and only then can view the
requirement as well as they can donate the blood.
This project requires internet access and thus there is a disadvantage of internet failure.
Thus this application helps to select the right donor online instantly using medical details along with
the blood group.
The main aim of developing this application is to reduce the time to a great extent that is spent in
searching for the right donor and the availability of blood required.
Thus this application provides the required information in no time and also helps in quicker decision
making.
LITERATURE SURVEY
In The Optimization of Blood Donor Information and Management System have proposed an efficient and
reliable blood donor information and management system based on android mobile application.

The service provided by the proposed system is needed and valuable to health sector where a quality of the
blood is considered for the safety of the patient through a systematic process by the blood management
system.

This system will be the solution for the problems such as wrong information of donors, misuse by third
parties and updating the donated blood by the donor which replaces the older systems.

The proposed system is an android application helps us to reduce the human mistakes which are done in
the existing system. The wireless internet technique enables the flow of data to work more rapidly and
conveniently . Have proposed the system that will link all registered hospital and donors. The system will
help control a blood requirement and donation service and create a database to hold data on donors of blood
in each area as data on donors in each city.

Users will be able to register as donors and thus receive request from hospitals who needs blood to donate
blood in cases of need.The application sends periodically actual location information of available donors to
main system and the blood requests to the donors. In this way, it provides an uninterrupted communication
between the hospital and donors. The distance of the donors to the hospital is an important criterion in the
determination of the donors. Therefore an optimization is also realized on this process.
PROPOSED SYSTEM
The user has to first download the application. He/She will be provided with two options: Login and sign
in. If the person has already registered, then he/she has to login. If not, he/she has to create an account
providing basic details like name, address, contact, date of birth, blood group, email id etc.
The proposed system, updates and uploads automatically and does not need anyone to do so. Also it is
easily available due to its speed and programming part and using it is quite an easy task and well as due to
its speed the information which will be available by one or two clicks.
The details of the blood banks, hospitals etc. will be saved in database and only the admin will have access
to database. Private and confidential data of the users can only be viewed by administrator. This system
promises very less paperwork and also provides help to blood banks and donors also.
Modules:
• User login: This module helps the donor to insert all the necessary details that is personal
information and medical information plus the blood group which together helps to select a donor.
• Hospital login : This module helps the hospital to insert all the necessary details that is hospital
information and requirements of blood group.
• Admin login : This module keeps the record of both user module and hospital module.

Advantages:

• This project has a login page which allows only the registered user to login and thereby
preventing unauthorized access.
• This system can be used to view all the donor details and accordingly select the right donor.
• The android mobile user will be able make quick decision in selecting a donor.
• Usage of this application will greatly reduce time in selecting the right donor.

Disadvantages:
• The android mobile user will not be able to insert or view details if the server goes down. Thus
there is disadvantage of single point failure.
BACKGROUND STUDY
1.1 Tool and Technology Used

1.1.1 Android Studio:

Android Studio is the official IDE for Android application development. Android Studio provides
a number of improvements to assist you in debugging and improving the performance of your
code, including an improved virtual device management, inline debugging, and performance
analysis tools. Android Studio provides a memory and CPU monitor view so you can more easily
monitor your app's performance and memory usage to track CPU usage, find reallocated objects,
locate memory leaks, and track the amount of memory the connected device is using.

Features of the Android Studio:

 Customize, configure, and extend the build process.

 Create multiple APKs for your app with different features using the same project and
modules.
 Reuse code and resources across source sets.

1.1.2 Java Development Kit:

The Java Development Kit (JDK) is an implementation of either one of the Java SE, Java EE or
Java ME platforms released by Oracle Corporation in the form of a binary product aimed at Java
developers on Solaris, Linux, Mac OS or Windows. The JDK includes a private JVM and a few
other resources to finish the recipe to a Java Application. Since the introduction of the Java
platform, it has been by far the most widely used Software Development Kit on 17 November
2006, Sun announced that it would be released under the GNU General Public License (GPL), thus
making it free software. This happened in large part on 8 May 2007, when Sun contributed the
source code to the OpenJDK.

2.2.3 SERVER:
ANALYSIS

2.1 Detailed problem statement

Previous blood bank applications have many flaws that need to be addressed and should be
removed in order to make a better blood bank application.

Disadvantages of previous application:

1. Performance of the user is not analyzed.

2. No online search of blood donors available.

2.1.1 Requirement Analysis

Information useful for designing this system is gathered. They are listed as follows:

1. Research papers to understand the underlying concepts.

2. Need of the project in present scenario.
3. Environment in which the software would be useful.

Lastly, information is gathered related to the applications that are required by the users. There are
different categories of users like developers, normal users etc. A user belonging to a particular
category can easily find a particular application of that category.

2.1.2 Functional Requirements

Functional requirements of the system describe the core part of the system and describe the main
functionalities of the system. Functional requirements of the system proposed are as follows:

 The application will help the user to find blood donors online.
 Only authorized person can access related details.
 The users can’t register themselves for using the application.
 User can post and receive blood requirements.
 The users can login through USER-ID and PASSWORD and register to the application.
 Administrator will be responsible for updating the site.
2.1.3 Non Functional Requirement:

Non Functional requirements are those which specifies the criteria for judging the performance
of the system rather than testing the specific behaviors. It particularly deals with degree of
performance and not the way of performing the task. Non Functional Requirements shows how a
system is supposed to be and to what degree. Also the specific qualities of the system are depicted
by these requirements.

The Non Functional requirements of our system are as follows:

 Security: Security is the facility provided to protect the data and restrict the access from
unauthorized user. This is realized using level security measures, first level is by
authenticating user using the credentials previously chosen by user and second level is
encrypting the data according to the protocol chosen by the client from the list given by the
server.

 Recoverability: The system should be restored to the previous state in which it was, when
the user last used it. User’s data must not get lost when the user closes the system abruptly.

 Usability: The system should be easy to use. Any user not familiar with the system should
be able to interpret the vocabulary used in the system and easily access.

 Reliability: System should be reliable in the sense that it should work for an adequate
period between two failures. Users must be confident of the reliability and must not fear
for the failure at any time.

 Configuration Management: Configuration Management is used to maintain the

performance, operations and the consistency of the system. When the team consist of more
than 2-3 members then problem of inconsistent changes in the documents is observed, thus
for facilitating proper informed changes throughout the team configuration management is
required.

 Cost: Cost of the system should be affordable for the user.

 Compatibility: It should be compatible to android version (jelly bean) and after that.

 Response Time: Response time of the system should be under the specified limits.

 Scalability: System should be scalable after practical implementation of the project and
should work for a large network and able to handle large number of clients.
  Deployment: Deployment of the system must be very easy as the users using this system
will have very less knowledge about the internal working and the source code so that later
on if the user changes the network he should not suffer from any problem.

Feasibility Study
Feasibility is defined as the possibility and practicality of the proposed project. Feasibility study
is done to identify the strength and weaknesses of the project. This further specifies the
opportunities and the threats of the project. Other factors which are analyzed in feasibility study
are the resources available and the prospects of ultimate success of the project. It not only focuses
on the technical aspect of the project but on the economic aspect also.

It is a process of analyzing, focusing, clarifying and resolving the key issues that are subject to the
viability of the project. Feasibility study is provided to identify the primary issues related to the
project idea. A project is possible or not is identified by its feasibility study. The feasibility study
focuses on helping answer the essential question of “should we proceed with the proposed project
idea” All activities of the study are directed toward helping answer this question.

Feasibility study permits the team to describe the idea and its prospects on the paper before
implementing it directly as chances of failure increase if the planning is not done properly with
major issues like time, cost and technicality of the project.

Risks and returns associated with the project are identified during feasibility analysis. If the
project promises for an adequate output with the specified input and available technologies then
we should proceed with the proposed idea otherwise taking the considerations, once again do
feasibility analysis and even if then the promising output is not obtained then the project idea
must be dropped.

Feasibility study is done before the business plan proposition because if the project seems to be
viable then only the hard work should be done on the planning otherwise whole project is ruined
and nothing can be gained even after substantial amount of efforts and costs.

Decision making in the project is very important at the start of planning phase for the continuation
of the project because based on that decision the project coming into reality is finalized and tried
for execution with proper business plan and funding propositions.

All these decisions of working on the project are taken into account only if feasibility study is done
and that too with taking all the constraints into the considerations.The decisions like make or break
are taken only after the study. Removing of all the projected and analyzed roadblocks are done
after the feasibility study.

Mainly three factors that it analyzes are market, finance and organizational aspects:

1. Technical feasibility
2. Economical feasibility
3. Operational feasibility.

3.1 Technical Feasibility:

Technical Feasibility assesses the current resources and technology, which are required to
accomplish user requirements in the software within the allocated time and for this, the software
development team ascertains whether the current resources and technology can be upgraded or
added in the software to accomplish specified user requirements.

The technical requirement for the system is economic and it does not use any other additional
Hardware and software. Most of the LAN computers have these specifications, so they will not
pose any technical feasibility issue.

3.2 Economic Feasibility:

This is the most frequently used method for evaluating the effectiveness of a system. It is also
called as a cost analysis. The system being developed is economic with respect to user point of
view. It is cost effective in the sense that has eliminated the paper work completely.

The technologies used are readily available and will suffice for the development of our software.
Also for implementation of the software no special hardware resources are needed. The
application developed in android which is freely available for registered candidates. So the
budget would not become a constraint or a limiting factor for the application under development.
Hence, the software is economically feasible.

3.3 Operational Feasibility:

Operational feasibility study tests the operational scope of the project to be developed.
Operational scope normally means that the usability of the project must be very high. This means
that the product at the end must be of use and of usable quality and must provide the
specifications as per the objectives determined. Our project is for android platform so already
available users on the android are the main target for this project.
CONCLUSION & FUTURE WORK

8.1 Conclusion

Work carried out in Phase I

As our project work is divided into two phases, first phase is the requirement gathering, analysis
and design of the project and second phase is the implementation of the project.

In phase 1, we first gathered what are the requirements of our project. We searched about the
existing systems that are already present and the systems that are performing nearly equal tasks
that our intended system is supposed to perform. Then we discussed about the protocols available
to implement our proposed system. After that we listed the detailed Functional and Non-functional
requirements. Then we did the feasibility study of our system whether the technologies are
available or not that can be used to implement it. Is this project possible technically. After the
feasibility it was then confirmed that the project is achievable in the specified time restrictions.
Then we listed the hardware support required to run the system and software support to build this
system. Then we discussed about the software development life cycle models, which model should
be used, and decided to choose Iterative model. Then, we made the use case diagram to get the
basic functionalities of the system. After use case diagram, and use-case description we made
architecture diagram of the system and following it, the activity diagram, flowcharts, and ER-
diagram are made.

Work to be carried out in Phase II

First phase aims to cover the three most important stages in software development life cycle i.e.
Requirement gathering, Analysis and Design. But the design part remains incomplete thus it will
be the first priority of the project to complete the diagrams of the design part. Design part is very
important stage in the SDLC model as properly designing all the aspects of the projects will help
in further implementing code and testing them. Even after that, in assembling all the components
and deploying all of them at their proper place would only result in the correct output of the project.

As project is planned to follow object oriented approach and is performing the software
development in iterative as well as in modular manner, the project is in the design stage. The next
task to be performed would be the study of behavioral interaction between the identified classes
of the project. On the basis of that study, interaction diagram would be made and that would be
either sequence or collaboration diagram. Sequence diagram should be made as it represents the
interaction on the scale of timestamps and managing the order of object interaction would be very
crucial. The next thing to be done would to create a state chart diagram for every object in the
project and showing process flow on the occurrence of different events. Modules can be created
in respect of the similar functionalities provided by the different classes and they can be divided
among team members so that parallel implementation of code can be performed. Similarly designs
for test cases should also be c reacted in advance for performing testing in the future.
After that, implementation of design can be started in the already chosen programming language
JAVA and Android. After the successful completion of different modules, test cases should also
be implemented using JUnit in JAVA and should be applied on the classes. This would cover the
unit testing for the project. After that, integration testing should be applied after integrating
respective modules and finally the whole assembling of modules will be performed. After that
Component diagram should also be made in order to show all the executable components of the
project and Deployment diagram for showing the actual hardware implementation in the project.

This would complete the project in all respect as this project need to be deployed on the Google
Play Store. Testing the project properly and assuring that it works properly for all the clients would
finish the second phase of the project.

References: