PROJECT REPORT

ON

Blood Bank Management App

at
Chandigarh University
BACHELOR OF TECHNOLOGY
IN
(COMPUTER SCIENCE & ENGINEERING)

SUBMITTED BY:

Mehul Puri (17BCS3190)

Deepanshu Raghuwanshi(17BCS3168)
Ajay Lubana(17BCS3135)
Sehtajpreet Singh Thind(17BCS3166)

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

Chandigarh University
 CONTENTS

● Candidate’s Declaration
● Acknowledgement
● Abstract
● Technology
● Project Profile
● Introduction
● Screenshots
● References
● Conclusion
 CANDIDATE'S DECLARATION

We hereby declare that the project work entitled “Blood Bank Management App”

submitted to the Chandigarh University, is a record of anoriginal work done by us under

the guidance of  Miss SAAKSHI ,

PGDept Of Computer Science & Engineering, Shadan College of Engineering &Technology, 

and this project work is submitted in the partial fulfillment of therequirements for the award

of the degree of Master of Technology in Computer Science & Engineering. The results

embodied in this thesis have not been submitted to any other University or Institute for the

award of any degree or diploma

Signature of the Student

The Summer training Viva–Voce Examination of __________________ has been held on

____________ and accepted.

Signature of Internal Examiner Signature of External

Examiner
 ACKNOWLEDGEMENT

We are highly grateful to the Miss Dipti and Saakshi of Chandigarh University
for providing this opportunity.

We would like to expresses my gratitude to other faculty members of Computer

Science Department for providing academic inputs, guidance and
encouragement throughout the training period.

Finally, we express my indebtedness to all who have directly or indirectly

contributed to the successful completion of the project.

Mehul Puri
Deepanshu Raghuwanshi
Ajay LubanaSehtajpreet
Singh Thind
 ABSTRACT

The project named Blood Bank Management System isdeveloped using

Android Studio. This project has been developed in partial fulfilment of
Requirements for the degree of B.Tech. (CSE), from Chandigarh University.

The Blood Bank Management System is developed for people for their daily
use. This application is helpful to individuals for daily donor records. This
application is very helpful for modern usage of technology.

The application is responsible to get the inputs from the users about their details
and keep the records. The application also allows the user to check the number
of available donors and their respective blood group with their contact details.

This project constitutes of following activities:

● Donor registration and collection of blood.

● Blood requisition/issue
● User access
● Detailed database for donors
● Maintain and update unique donor identification
● Correlation and cross referencing between files
● Powerful search for donors by blood group.
●
 Chapter-2

Software Training Work Undertaken

2.1 Java:

2.1.1 Introduction:

Java is a programming language created by James Gosling from Sun

Microsystems (Sun) in 1991. The target of Java is to write a program once and
then run this program on multiple operating systems. The first publicly
available version of Java (Java 1.0) was released in 1995. Sun Microsystems
was acquired by the Oracle Corporation in 2010. Oracle has now the
steermanship for Java. In 2006 Sun started to make Java available under the
GNU General Public License (GPL). Oracle continues this project called
OpenJDK.

Java is defined by a specification and consists of a programming language, a

compiler, core libraries and a runtime (Java virtual machine) The Java runtime
allows software developers to write program code in other languages than the
Java programming language which still runs on the Java virtual machine. The
Java platform is usually associated with the Java virtual machine and the Java
core libraries.

2.1.2 Java virtual machine (JVM):

The Java virtual machine (JVM) is a software implementation of a computer

that executes programs like a real machine. The Java virtual machine is written
specifically for a specific operating system, e.g., for Linux a special
implementation is required as well as for Windows. Java programs are
compiled by the Java compiler into bytecode. The Java virtual machine
interprets this bytecode and executes the Java program.

2.1.3 Java Runtime Environment vs. Java Development Kit:

A Java distribution typically comes in two flavors, the Java Runtime

Environment (JRE) and the Java Development Kit (JDK). The JRE consists of the
JVM and the Java class libraries. Those contain the necessary functionality to
start Java programs. The JDK additionally contains the development tools
necessary to create Java programs. The JDK therefore consists of a Java
compiler, the Java virtual machine and the Java class libraries.

2.1.4 Development Process with Java:

Java source files are written as plain text documents. The programmer typically
writes Java source code in an Integrated Development Environment (IDE) for
programming. An IDE supports the programmer in the task of writing code,
e.g., it provides auto-formating of the source code, highlighting of the
important keywords, etc.

At some point the programmer (or the IDE) calls the Java compiler ( javac ). The
Java compiler creates the bytecode instructions. These instructions are stored
in .class files and can be executed by the Java Virtual Machine.
2.1.5 Garbage collector:

The JVM automatically re-collects the memory which is not referred to by

other objects. The Java garbage collector checks all object references and finds
the objects which can be automatically released.

While the garbage collector relieves the programmer from the need to
explicitly manage memory, the programmer still need to ensure that he does
not keep unneeded object references, otherwise the garbage collector cannot
release the associated memory. Keeping unneeded object references are
typically called memory leaks.

2.1.6 Classpath:

The classpath defines where the Java compiler and Java runtime look for .class
files to load. These instructions can be used in the Java program.

For example, if you want to use an external Java library you have to add this
library to your classpath to use it in your program.

2.1.7 Types of Java Applications:

2.1.7.1Web Application – Java is used to create server-side web applications.

Currently, servlet, jsp, struts, jsf etc. technologies are used.

2.1.7.2 Standalone Application – It is also known as desktop application or

window-based application. An application that we need to install on every
machine or server such as media player, antivirus etc. AWT and Swing are used
in java for creating standalone applications.

2.1.7.3Enterprise Application – An application that is distributed in nature,

such as banking applications etc. It has the advantage of high level security,
load balancing and clustering. In java, EJB is used for creating enterprise
applications.

2.1.7.4Mobile Application – Java is used to create application softwares for

mobile devices. Currently Java ME is used for creating applications for small
devices, and also Java is programming language for Google Android application
development.

2.1.8 Features of Java:

2.1.8.1 Object Oriented – In java everything is an Object. Java can be easily

expanded since it is based on the Object model.

2.1.8.2 Platform independent – C and C++ are platform dependency languages

hence the application programs written in one Operating system cannot run in
any other Operating system, but in platform independence language like Java
application programs written in one Operating system can able to run on any
Operating system.

2.1.8.3 Simple – Java is designed to be easy to learn. If you understand the

basic concept of OOP java would be easy to master.

2.1.8.4 Secure –With Java’s secure feature it enables to develop virus-free,

tamper-free systems. Authentication techniques are based on public-key
encryption.

2.1.8.5 Architectural-neutral – Java compiler generates an architecture-neutral

object file format which makes the compiled code to be executable on many
processors, with the presence Java runtime system.

2.1.8.6 Portable – being architectural neutral and having no implementation

dependent aspects of the specification makes Java portable. Compiler and Java
is written in ANSI C with a clean portability boundary which is a POSIX subset.
2.1.8.7 Robust – Java makes an effort to eliminate error prone situations by
emphasizing mainly on compile time error checking and runtime checking.

2.1.8.8 Multi-threaded – With Java’s multi-threaded feature it is possible to

write programs that can do many tasks simultaneously. This design feature
allows developers to construct smoothly running interactive applications.

2.1.8.9 Interpreted – Java byte code is translated on the fly to native machine
instructions and is not stored anywhere. The development process is more
rapid and analytical since the linking is an incremental and light weight
process.

2.1.8.10 High Performance – With the use of Just-In-Time compilers Java

enables high performance.

2.1.8.11 Distributed – Java is designed for the distributed environment of the

internet.

2.1.8.12 Dynamic – Java is considered to be more dynamic than C or C++ since

it is designed to adapt to an evolving environment. Java programs can carry an
extensive amount of run-time information that can be used to verify and
resolve accesses to objects on run-time.
2.2 Android

2.2.1 Introduction:

Android is a mobile operating system developed by Google, based on the Linux

kernel and designed primarily for touchscreen mobile devices such as
smartphones and tablets. Android's user interface is mainly based on direct
manipulation, using touch gestures that loosely correspond to real-world
actions, such as swiping, tapping and pinching, to manipulate on-screen
objects, along with a virtual keyboard for text input. In addition to touchscreen
devices, Google has further developed Android TV for televisions, Android
Auto for cars, and Android Wear for wrist watches, each with a specialized user
interface. Variants of Android are also used on game consoles, digital cameras,
PCs and other electronics.

Initially developed by Android Inc., which Google bought in 2005, Android was
unveiled in 2007, along with the founding of the Open Handset Alliance – a
consortium of hardware, software, and telecommunication companies devoted
to advancing open standards for mobile devices. Beginning with the first
commercial Android device in September 2008, the operating system has gone
through multiple major releases, with the current version being 8.0 "Oreo",
released in August 2017. Android applications ("apps") can be downloaded
from the Google Play store, which features over 2.7 million apps as of February
2017. Android has been the best-selling OS on tablets since 2013, and runs on
the vast majority of smartphones. As of May 2017, Android has two billion
monthly active users, and it has the largest installed base of any operating
system.

Android's source code is released by Google under an open source license,

although most Android devices ultimately ship with a combination of free and
open source and proprietary software, including proprietary software required
for accessing Google services. Android is popular with technology companies
that require a ready-made, low-cost and customizable operating system for
high-tech devices. Its open nature has encouraged a large community of
developers and enthusiasts to use the open-source code as a foundation for
community-driven projects, which deliver updates to older devices, add new
features for advanced users or bring Android to devices originally shipped with
other operating systems. The extensive variation of hardware in Android
devices causes significant delays for software upgrades, with new versions of
the operating system and security patches typically taking months before
reaching consumers, or sometimes not at all. The success of Android has made
it a target for patent and copyright litigation between technology companies.

2.2.2 Features of Android:

2.2.2.1 Messaging:

SMS and MMS are available forms of messaging, including threaded text
messaging and Android Cloud To Device Messaging (C2DM) and now enhanced
version of C2DM, Android Google Cloud Messaging (GCM) is also a part of
Android Push Messaging services.

2.2.2.2 Web browser:

The web browser available in Android is based on the open-source Blink

(previously WebKit) layout engine, coupled with Chrome's V8 JavaScript
engine. Then the WebKit-using Android Browser scored 100/100 on the Acid3
test on Android 4.0 ICS; the Blink-based browser currently has better standards
support. The browser is variably known as 'Android Browser', 'AOSP browser',
'stock browser', 'native browser', and 'default browser'. Starting with Android
4.4 KitKat, Google has mandated that the default browser for Android proper
be Google Chrome.[citation needed] Since Android 5.0 Lollipop, the WebView
browser that apps can use to display web content without leaving the app has
been separated from the rest of the Android firmware in order to facilitate
separate security updates by Google.

2.2.2.3 Voice-based features:

Google search through voice has been available since initial release. Voice
actions for calling, texting, navigation, etc. are supported on Android 2.2
onwards. As of Android 4.1, Google has expanded Voice Actions with ability to
talk back and read answers from Google's Knowledge Graph when queried
with specific commands. The ability to control hardware has not yet been
implemented.

2.2.2.4Multi-touch:

Android has native support for multi-touch which was initially made available
in handsets such as the HTC Hero. The feature was originally disabled at the
kernel level (possibly to avoid infringing Apple's patents on touch-screen
technology at the time). Google has since released an update for the Nexus
One and the Motorola Droid which enables multi-touch natively.

2.2.2.5 Multitasking:

Multitasking of applications, with unique handling of memory allocation,

is available.

2.2.2.6 Screen capture:

Android supports capturing a screenshot by pressing the power and

home-screen buttons at the same time. Prior to Android 4.0, the only methods
of capturing a screenshot were through manufacturer and third-party
customizations (apps), or otherwise by using a PC connection (DDMS
developer's tool). These alternative methods are still available with the latest
Android.

2.2.2.7 TV recording:

Android TV supports capturing video and replaying it.

2.2.2.8 Video calling:

Android does not support native video calling, but some handsets have a
customized version of the operating system that supports it, either via the
UMTS network (like the Samsung Galaxy S) or over IP. Video calling through
Google Talk is available in Android 2.3.4 (Gingerbread) and later. Gingerbread
allows Nexus S to place Internet calls with a SIP account. This allows for
enhanced VoIP dialing to other SIP accounts and even phone numbers. Skype
2.1 offers video calling in Android 2.3, including front camera support. Users
with the Google+ Android app can video chat with other Google+ users
through Hangouts.
 2.2.2.9 Multiple language support:

Android supports multiple languages.

2.2.2.10 Accessibility:

Built-in text-to-speech is provided by TalkBack for people with low or no vision.

Enhancements for people with hearing difficulties are available, as are other
aids.

2.2.2.11 Connectivity:

Android supports connectivity technologies including GSM/EDGE, Bluetooth,

LTE, CDMA, EV-DO, UMTS, NFC, IDEN and WiMAX.

2.2.2.12 Bluetooth:

Supports voice dialing and sending contacts between phones, playing music,
sending files (OPP), accessing the phone book (PBAP), A2DP and AVRCP.
Keyboard, mouse and joystick (HID) support is available in Android 3.1+, and in
earlier versions through manufacturer customizations and third-party
applications.

2.2.2.13 Tethering:

Android supports tethering, which allows a phone to be used as a

wireless/wired Wi-Fi hotspot. Before Android 2.2 this was supported by third-
party applications or manufacturer customizations.

2.2.2.14 Streaming media support:

RTP/RTSP streaming (3GPP PSS, ISMA), HTML progressive download (HTML5

<video> tag). Adobe Flash Streaming (RTMP) and HTTP Dynamic Streaming are
supported by the Flash plugin. Apple HTTP Live Streaming is supported by
RealPlayer for Android, and by the operating system since Android 3.0
(Honeycomb).

2.2.2.15 Media support:

Android supports the following audio/video/still media formats: WebM, H.263,

H.264, AAC, HE-AAC (in 3GP or MP4 container), MPEG-4 SP, AMR, AMR-WB (in
3GP container), MP3, MIDI, OggVorbis, FLAC, WAV, JPEG, PNG, GIF, BMP, and
WebP.

2.2.2.16 External storage:

Most Android devices include microSD card slots and can read microSD cards
formatted with the FAT32, Ext3 or Ext4 file systems. To allow use of external
storage media such as USB flash drives and USB HDDs, some Android devices
are packaged with USB-OTG cables. Storage formatted with FAT32 is handled
by the Linux Kernel vFAT driver, while 3rd party solutions are required to
handle some other file systems such as NTFS, HFS Plus and exFAT.

2.2.2.17 Java support:

While most Android applications are written in Java, there is no Java Virtual
Machine in the platform and Java byte code is not executed. Java classes are
compiled into Dalvik executables and run on using Android Runtime or in
Dalvik in older versions, a specialized virtual machine designed specifically for
Android and optimized for battery-powered mobile devices with limited
memory and CPU. J2ME support can be provided via third-party applications.

2.2.2.18 Handset layouts:

The platform works for various screen sizes from smartphone sizes and to
tablet size, and can potentially connect to an external screen, e.g. through
HDMI, or wirelessly with Miracast. Portrait and landscape orientations are
supported and usually switching between by turning. A 2D graphics library, 3D
graphics library based on OpenGL ES 2.0 specifications is used.

2.2.2.19 Storage:

SQLite, a lightweight relational database, is used for data storage

purposes.

2.2.2.20 Native Apps:

Android apps are also written in HTML.

2.2.2.21 Instant Apps:

Android apps are hosted on a specific website path and load instead of the
website itself. They are part-apps and load almost instantly without the need
for an installation. One of the first apps being developed with such
functionality is the B&H app.

2.2.3 Official development tools:

2.2.3.1 Android SDK:

The Android software development kit (SDK) includes a comprehensive set of

development tools. These include a debugger, libraries, a handset emulator
based on QEMU, documentation, sample code, and tutorials. Currently
supported development platforms include computers running Linux (any
modern desktop Linux distribution), Mac OS X 10.5.8 or later, and Windows 7
or later. As of March 2015, the SDK is not available on Android itself, but
software development is possible by using specialized Android applications.
2.2.3.2 Android Debug Bridge:

The Android Debug Bridge (ADB) is a toolkit included in the Android SDK
package. It consists of both client and server-side programs that communicate
with one another. The ADB is typically accessed through the command-line
interface, although numerous graphical user interfaces exist to control ADB.

The format for issuing commands through the ADB is typically:

adb [-d|-e|-s <serialNumber>] <command>

where -d is the option for specifying the USB-attached device,

-e for indicating a running Android emulator on the computer,

-s for specifying either one by its adb-assigned serial number.

If there is only one attached device or running emulator, these options are not
necessary.

For example, Android applications can be saved by the command backup to a

file, whose name is backup.ab by default.

2.2.3.3 Fastboot:

Fastboot is a diagnostic protocol included with the SDK package used

primarily to modify the flash file system via a USB connection from host
computer. It requires that the device be started in a boot loader or Secondary
Program Loader mode, in which only the most basic hardware initialization is
performed. After enabling the protocol on the device itself, it will accept a
specific set of commands sent to it via USB using a command line. Some of the
most commonly used fastboot commands include:
 ● flash – rewrites a partition with a binary image stored on the host
computer

● erase – erases a specific partition

● reboot – reboots the device into either the main operating

system, the system recovery partition or back into its boot loader

● devices – displays a list of all devices (with the serial number)

connected to the host computer

● format – formats a specific partition; the file system of the

partition must be recognized by the device.

2.2.3.4 Android NDK:

Libraries written in C/C++ can be compiled to ARM, MIPS or x86 native code (or
their 64-bit variants) and installed using the Android Native Development Kit
(NDK). These native libraries can be called from Java code running under the
Dalvik VM using the System.loadLibrary call, which is part of the standard
Android Java classes.

2.2.3.5 Android Open Accessory Development Kit:

The Android 3.1 platform (also backported to Android 2.3.4) introduces

Android Open Accessory support, which allows external USB hardware (an
Android USB accessory) to interact with an Android-powered device in a
special "accessory" mode. When an Android-powered device is in accessory
mode, the connected accessory acts as the USB host (powers the bus and
enumerates devices) and the Android-powered device acts as the USB device.

2.2.4 Versions of Android:

Code Name Version Number Initial Release API level

Date
September 23,
(No Codename) 1.0 1
2008
(Internally known
1.1 February 9, 2009 2
as "Petit Four")
Cupcake 1.5 April 27, 2009 3
September 15,
Donut 1.6 4
2009
Éclair 2.0 – 2.1 October 26, 2009 5-7
Froyo 2.2 – 2.2.3 May 20, 2010 8
Gingerbread 2.3 – 2.3.7 December 6, 2010 9-10
Honeycomb 3.0 – 3.2.6 February 22, 2011 11-13
Ice Cream
4.0 – 4.0.4 October 18, 2011 14-15
Sandwich
Jelly Bean 4.1 – 4.3.1 July 9, 2012 16-18
KitKat 4.4 – 4.4.4 October 31, 2013 19-20
November 12,
Lollipop 5.0 – 5.1.1 21-22
2014
 Marshmallow 6.0 – 6.0.1 October 5, 2015 23
Nougat 7.0 – 7.1.2 August 22, 2016 24-25
Oreo 8.0 August 21, 2017 26

Table: 2.1

2.2.5 Why Android Development:

There are multiple operating systems powering our mobile devices today. For
both indie developers and large companies, there is a critical question that
needs to be answered before development begins: what platform should be
targeted first?

Reasons I choose Android Development are:-

2.2.5.1 Portability:

Native Android apps are developed using the Java programming language, and
can easily be ported to other mobile operating systems like Blackberry,
Symbian and Ubuntu. In addition, Android apps can also be ported easily to
Chrome OS. Not surprisingly, Microsoft has also announced that it will provide
an easy method to port Android apps to Windows 10 devices.

2.2.5.2 Android Studio:

Android Studio is an excellent IDE, based on the equally excellent IntelliJ IDE.
As the name suggests, Android Studio is an IDE designed and developed
specifically for Android app development. It is blazingly fast and efficient, and
you can setup a new Android project for different types of Android apps within
seconds. When Android was launched, Android app development was done
with Eclipse and the Android Developer Tools plugin. However, that changed
with the release of Android Studio.

2.2.5.3 Java:

Java is a proven and powerful programming language, used on a wide range of

devices and operating systems. Learning Java can open doors for other
opportunities, including the ability to develop applications for other operating
systems (Windows, Linux) and devices. Developing for iOS, on the other hand,
requires that you learn one of Apple’s development languages (Objective C or
Swift). Both of these languages are really only used for Apple-centric
development (iOS and OS X), and the skills needed to develop in these
languages cannot be carried over to other operating systems. But to be fair,
Apple has announced Swift will be open sourced, with Linux tools available
before the end of the year.

2.2.5.4 Google Play Store:

Apps deployed to the Google Play store are available for download by users
within a few hours, compared to a few weeks for Apple’s App Store. An app
can literally be updated multiple times a day on the Google play store, in
response to user complaints and/or issues, while on the App store, your app
would have to pass through the same lengthy process whenever you submit an
update and/or bug fix. For a new app or game that might need to be constantly
and speedily refined and updated in response to user feedback, the Play Store
is the perfect platform.
2.2.5.5 Low barrier of entry:

To develop for iOS devices, a developer must use a Mac. However, Android
app development can be done on Windows, Mac and Linux. Also, to register as
a developer on the Apple App Store requires a yearly fee of $99, whereas to
register as a developer on the Google Play Store requires a one time payment
of $25. In plain terms, all a developer needs to begin developing and releasing
Android apps is a $25 payment, and a computer, while for iOS, you will require
a Mac and a $99 yearly subscription.

2.2.5.6 Profitability:

The general consensus has always been that the iPhone is used by richer and
more affluent users, and so, iPhone users are more likely to spend money on
apps than Android users. This might have been true in the past, but not any
more. In most app categories, Android apps have been found to be as
profitable (even more profitable in some instances) as iPhone apps, both for
initial app purchases and for in-app purchases. Also, with many apps using a
free with ads model, as long as the ads are being shown to app users, the app
generates income. According to DAU-UP, the average revenue per user for
Android games was a measly 20% of that from iOS games in January 2014. By
December 2014, the figure had spiked to 65%. In addition, advertising costs are
generally lower on Android devices, which means that apps can advertise to
more users on Android devices than users on iOS devices for the same amount.

2.2.5.7 Market share:

This has to be the number one reason why indie developers should develop for
Android first. According to IDC, Android absolutely dominated the number of
smartphones shipped worldwide in the first three months of 2015, with 78%
market share. The estimated total number of Android devices in the hands of
consumers, as at December 2014, according to statista.com, lies north of 1.6
billion. This is a staggering amount, and a very large potential market of users.
Compare this with an estimated 395 million iOS devices, and 46 million and 45
million Windows and Blackberry devices respectively. If you are designing an
app (or game) for the general public, it makes economic sense to target the
platform that would give you the greatest access to potential users.

Chapter-3

Technical Work Undertaken

3.1 Android Studio:

3.1.1 Introduction:

Previously, the Android development was spread using the Eclipse platform
with the Android Development Kit (ADK), provided by Google, which launched
the Android Studio platform. This is based on IntelliJ IDEA, which is an IDE that
also supports Android, but it has a high cost.The Android Studio IDE has some
advantages like, for example, the Gradle dependency manager (see Links
section), also based on IntelliJ, widely used all over the world. This is one of the
great strengths of the platform editor as it offers more options to the
developer at build time, once Eclipse used the classic compilation way.

Android Studio can be installed on Windows operating systems, OSX and Linux
and is recommended by Google itself that the hardware must have at least 4
GB of memory and 1GB of free hard disk space, but we recommend that you
have more memory because it was noted that Android Studio is still a little
slow. You must have Java installed on the machine via the JDK (Java
Development Kit), not the JRE, as it is usually installed, once to develop on
Android is necessary for all Java development classes to be present on the
machine.

3.1.2 Features of Android Studio:

New features are expected to be rolled out with each release of Android
Studio. The following features are provided in the current stable version:

● Gradle-based build support

● Android-specific refactoring and quick fixes

● Lint tools to catch performance, usability, version compatibility

and other problems

● ProGuard integration and app-signing capabilities

● Template-based wizards to create common Android designs and

components

● A rich layout editor that allows users to drag-and-drop UI

components, option to preview layouts on multiple screen
configurations.

● Support for building Android Wear apps

● Built-in support for Google Cloud Platform, enabling integration

with Firebase Cloud Messaging (Earlier 'Google Cloud Messaging')
and Google App Engine.

● Android Virtual Device (Emulator) to run and debug apps in the

Android studio.

Android Studio supports a number of programming languages, e.g. Kotlin; and

Android Studio 3.0 supports "Java 7 language features and a subset of Java 8
language features that vary by platform version." External projects backport
some Java 9 features.

3.1.3 System Requirements:

3.1.3.1 Version 3.x:

Criterion Description
OS version Microsoft® Windows® 7/8/10 (32-bit or 64-bit)

Mac® OS X® 10.10 (Yosemite) or higher, up to 10.13 (macOS

High Sierra)

GNOME or KDE desktop

RAM 3 GB RAM minimum, 8 GB RAM recommended; plus 1 GB for
the Android Emulator
Disk space 2 GB of available disk space minimum,

4 GB recommended (500 MB for IDE + 1.5 GB for Android SDK

and emulator system image)
Java version Java Development Kit (JDK) 8
Screen 1280×800 minimum screen resolution
resolution
Table: 3.1

3.1.3.2 Version 2.x:

Criterion Description
OS version Windows 7 or later

Mac OS X 10.9.5 or later

GNOME or KDE desktop

RAM 8 GB RAM recommended; plus 1 GB for the Android Emulator[
Disk space 500 MB disk space for Android Studio, at least 1.5 GB for
Android SDK, emulator system images, and caches
Java version Java Development Kit (JDK) 8
Screen 1280×800 minimum screen resolution
resolution
Table: 3.2

3.1.3.3 Version 1.x:

Criterion Description
OS version Windows XP or later

Mac OS X 10.8.5 or later

GNOME, KDE or Unity desktop on Ubuntu or Fedora or

GNU/Linux Debian
RAM 3 GB RAM minimum, 4 GB RAM recommended
Disk space 500 MB disk space for Android Studio, at least 1 GB for Android
SDK, emulator system images, and caches
Java version Java Development Kit (JDK) 7 or higher
Screen 1280×800 minimum screen resolution
resolution
Table: 3.3

3.1.4 Version History:

Version Release Date Version Release Date Version Release Date

0.1.x May 2013 1.1.0 February 2015 2.0.0 April 2016
0.2.x July 2013 1.2.0 April 2015 2.1.0 April 2016
0.3.2 Oct 2013 1.2.1 May 2015 2.1.1 May 2016
0.4.2 Jan 2014 1.2.1 June 2015 2.1.2 June 2016
0.4.6 March 2014 1.3.0 July 2015 2.1.3 August 2016
0.5.2 May 2014 1.3.1 August 2015 2.2.0 September
2016
0.8.0 June 2014 1.3.2 August 2015 2.2.1 October 2016
0.8.6 August 2014 1.4.0 September 2.2.2 October 2016
2015
0.8.14 October 2014 1.4.1 October 2015 2.2.3 December
2016
1.0 December 1.5.0 November 2.3.0 March 2017
2014 2015
1.0.1 December 1.5.1 December 2015 2.3.1 April 2017
2014
2.3.2 April 2017 2.3.3 June 2017 3.0 October 2017
Table: 3.4
3.2 Postman:

3.2.1 Introduction:

A powerful GUI platform to make your API development faster & easier, from
building API requests through testing, documentation and sharing. Postman is
a type of software testing that involves testing application programming
interfaces (APIs) directly and as part of integration testing to determine if they
meet expectations for functionality, reliability, performance, and security.
Since APIs lack a GUI, API testing is performed at the message layer. API testing
is now considered critical for automating testing because APIs now serve as the
 primary interface to application logic. Postman is used to determine whether
APIs return the correct response (in the expected format) for a broad range of
feasible requests, react properly to edge cases such as failures and
unexpected/extreme inputs, deliver responses in an acceptable amount of
time, and respond securely to potential security attacks.

Some features of Postman:

● Collaboration

● API documentation

● API monitoring

Project Profile
PROJECT TITLE:
Blood Bank Management System

PROJECT TEAM SIZE:

⮚ Four Student

SEC- SEM:

⮚ IS13 SEM 6

Functional Requirements:

1. Admin Page who have contacts with blood banks,

2. Donors will download the application and REGISTER with ID, DOB, phone no., blood group

etc.

3. Admin will send notification to the application users.

4. Admin can sort-out people who can come in emergency and send a notification to everyone if

he gets a donor.

5. Record of donor’s information along with their details

HARDWARE AND SOFTWARE REQUIREMENTS:

Hardware Requirements: 

⮚ Android mobile with a minimum version 2.2.

⮚ The processor is not less than 500MHZ.

⮚ RAM is not less than 2048MB.

⮚ SD card with a minimum of 512MB.

⮚ Resolution is not less than 480*800pixs.

Software Requirements: 

⮚ Mobile Operating System: Android 2.2 or Later

⮚ Server Operating System: Windows XP or Later

⮚ Tools (IDE): Eclipse or Android Studio

⮚ User Interface: XML

⮚ Code Behind: JAVA and XML

⮚ Telephony Service: Yes

 ⮚ Internet: Yes

Project Introduction

Project Title :Blood Bank Management System

Project category : Android Application

The project named Blood Bank Management System is developed using

Android Studio. This project has been developed in partial fulfilment of
Requirements for the degree of B.Tech. (CSE), from CHANDIGARH
UNIVERSITY.

The Blood Bank Management System is developed for people for their daily
use. This application is helpful to individuals for daily donor records. This
application is very helpful for modern usage of technology.

The application is responsible to get the inputs from the users about their details
and keep the records. The application also allows the user to check the number
of available donors and their respective blood group with their contact details.

This project constitutes of following activities:

● Donor registration and collection of blood.

● Blood requisition/issue
● User access
● Detailed database for donors
● Maintain and update unique donor identification
● Correlation and cross referencing between files
● Powerful search for donors by blood group, gender, contact number

● Android Studio

● Android Studio is the official  integrated development environment (IDE)

for Google's Android operating system, built on JetBrains' IntelliJ IDEA software and
designed specifically for Android development. It is available for download
on Windows, macOS and Linux based operating systems. It is a replacement for
the Eclipse Android Development Tools (ADT) as the primary IDE for native
Android application development.ASP.NET is a managed framework that facilitates
building server-side applications based on HTTP, HTML, XML and SOAP. To .NET
developers, ASP.NET is a platform that provides one-stop shopping for all application
development that requires the processing of HTTP requests.
● Android Studio was announced on May 16, 2013 at the Google I/O conference. It was
in early access preview stage starting from version 0.1 in May 2013, then entered beta
stage starting from version 0.8 which was released in June 2014.The first stable build
was released in December 2014, starting from version 1.0.The current stable version
is 3.2.1, which was released in October 2018.
● The following features are provided in the current stable version

⮚ Gradle-based build support

⮚ Android-specific refactoring and quick fixes
⮚ Lint tools to catch performance, usability, version compatibility and other
problems
⮚ ProGuard integration and app-signing capabilities
⮚ Template-based wizards to create common Android designs and components

Login Screen: Registration:

HOME SCREEN :
Profile Screen :
Create Request :
About Us:
References
 ⮚ https://en.wikipedia.org/wiki/Android_Studio

⮚ https://developer.android.com/studio/intro/

⮚ https://www.tutorialspoint.com/android/android_studio.htm

⮚ https://www.tutorialspoint.com/android/android_sqlite_database.htm

⮚ https://developer.android.com/reference/android/database/sqlite/package-

⮚ https://www.google.com/search?q=android+studio+javatpoint&rlz=

Conclusion
The android application for blood donation can be used by a lot of people and
will help a lot of different communities like the doctors, donors, receivers and
other general public. The user can be a blood donor as well as a recipient, this
user can use the features of the application. The goal of the application is to
provide solution to the existing deficit
of blood and will connect the donors and the receivers who need blood. The
application will get continuous updates from the hospital regarding the quantity
of blood available. This application will solve the current problem that the
world is facing, and hence save a lot of lives. This is the solution that we have
for the existing problem