Chapter-1: 1.1 General Introduction

Sant Baba Bhag Singh Institute of Engineering and Technology
CHAPTER-1
INTRODUCTION
1.1 GENERAL INTRODUCTION
In the era of technology, internet is playing a major role in everyone’s life. People are
connecting to far-away places in a single tap on their mobile screen. The whole knowledge
available in the world can be accessed from a single hand-held device. People can do shopping,
watch TV shows, games, etc., make transactions from bank account and entertain themselves
with music, movies, games, etc. by sitting in any corner of the world, all they need is a device
with internet.
Android Devices play a very important role in making our life easier. There are lot of android
apps available today that helps an individual to achieve this ease of life. Similarly, our team at
Pisoft Informatics Pvt. Ltd. is going to develop a social android app for a well-known
organisation REHRAS SEWA SOCIETY(REGD) (www.rehrassewa.org).
This is an online blood donor finder system that helps in finding the blood to nearby places.
The project consists of a central depository containing various blood deposits available along
with associated details. These details include blood type, storage area and date of storage.
Maintenance and the monitoring of blood deposits become easy with the help of this system.
The project is an online system that provides an option to check the availability of the required
blood group within the blood bank. Moreover, the system also has added features such as
patient name and contacts, blood booking and requirement of blood group is posted on the App
to find available donors for a blood emergency.
This application is reduced as much as possible to avoid errors while entering the data. It also
provides error message while entering invalid data. No formal language is needed for the user
to use this system. Thus, by this all it proves it is user-friendly.
Every organization has challenges to overcome and managing the information of Donor,
Receiver, Blood group, Record. Therefore, we design exclusive employee management system
that are adapted to your managerial requirements. Thus, it will help organization in better
utilization of resources.
The inspiration of this project is to improve blood banks in India and to develop a blood bank
information system which focuses on making an online system that is accessible for both
donors and receivers. Donors can directly receive information regarding their previous blood
donations, including their blood results and donation history, to easily schedule their next
donations. They can also update the personal information through the system, without having
to contact the blood bank registry. More over the security and authentication both concepts are
kept in mind while making this App.
1
REHRAS SEWA (BLOOD DONOR FINDER APP)
1.1.1 Importance
Our main objective of developing this project are as follows:
I) Basic aim of this project is to bring all type blood donor in contact to the needy people
in such a way that no one to suffer from insufficiency of blood on demand.
II) The objectives of the Projects are to manage the details of Blood Group, Donor, Record,
Receiver.
III) The aim is to automate the existing manual system by the help of computerized
equipment and full-fledged computer software, fulfilling their requirements, so that
their valuable data/information of the same.
IV) Basically, the project describes how to manage for good performance and better
services for the receivers.
V) It tracks all the details about the Donor, Receiver, Blood Group.
VI) Centralize administration and storage of data from a server to reduce the redundancy of
data, resulting in lower work load.
VII) Providing access of the data from any kind of device having an active internet
connection, so that in case of failure, staff can use their own device to access the
required data.
VIII) Reduce the paperwork, so that the data can be managed easily, resulting in
saving of time and paper.
1.1.2 Existing System
If the current managing system is observed, there are many drawbacks like:
I) The Current System that is using by the organization is Manual system. With the
manual System, there are problems in managing donor’s detail,
II) and blood request details.
III) No immediate service, manually managing blood, Waiting queue of patients and not
secure record.
IV) Hospital, patients, organizational staff and doctors are affected by the Manual Blood
Bank Management System.
V) The data of system is not centrally managed.
VI) The redundancy of data results in data anomalies, which also results in increased work
load.
VII) The donor’s information can only be updated by the administrators of the blood
bank. A donor can update their information by calling, faxing, e-mailing, but not by
themselves. This is a waste of time just for updating a piece of information and it may
be troublesome for some donors.
VIII) The donor ID card is the only tangible evidence that contains the donor’s recent
donation records, if the card gets lost, donors may find it difficult to schedule their next
appointment since they are not able to see the last time they had donated blood.
2
1.1.3 Proposed System
Possible outcomes of our project will be as follows:
I) Provides the searching facilities based on various factors. Such as Donor, Blood Group
according to state and city.
II) Blood Donor Finder System also manage the Record details online for Blood Group.
III) It tracks all the details about the Donor, Receiver, Blood Group.
IV) Data is secured under password protection.
V) Proper authorization will increase the security of data stored in the database.
VI) Facility to easily add, finds, edit and delete any information by ADMIN.
VII) No formal language is needed for the user to use this system. Have a good User
interface. Thus, it is user-friendly.
VIII) Efficient performance.
IX) To inform donors of their blood result after their donation.
X) Show the information and description of the Blood Bank and Donor.
XI) To develop a system that provides functions to support donors to view and manage their
information conveniently.
XII) To support searching, matching and requesting for blood convenient for
administrators.
1.2 HARDWARE AND SOFTWARE REQUIREMENTS
BDF App is already hosted on the server. Server used is IBM server with 4GB RAM and
500GB storage space. Static IP enables the server to be accessed from any device connected to
the internet. The server stays on for 24x7 hours, this provides non-stop availability of BDF
App round the clock.
On the server, Microsoft Windows Server 2012 is installed, for data storage Oracle 10g XE
Database is installed, and BDF App is hosted on the server.
Following facilities are required for developing the App:

1.2.1 Software Requirements:
I) Android Studio 3.0.1
II) Android SDK (API Level 27 and API Level 26)
III) Mozilla Firefox Developer Edition (Latest available)
IV) Internet Access
V) OS: Ubuntu / Mac OSX / Windows 10
VI) MySQL Database
3
1.2.2 Minimum Hardware Requirements:
I) Computer System
II) RAM – 8GB
III) Hard disk Space – 20GB
IV) Processor Intel i5 6th Gen
V) Android Device with Marshmallow (Android version 6)
Following facilities are required to run the App:

1.2.3 Software Requirements:
I) Nginx Web Server
III) OS: Microsoft Windows Server 2012 / Ubuntu
III) MySQL Database
1.2.4 Minimum Hardware Requirements:
I) Computer System Server (dedicated/virtual)
II) Static IP Connection
III) RAM – 2GB
IV) Hard disk Space – 20GB
V) Processor- i3 5th Gen
4
1.3 Technology Used: -

The User Interface of this project is developed in Android, HTML5, JAVASCRIPT,
BOOTSTARP, JQUERY and the backend of this project is developed in JAVA EE and
database is designed in MYSQL 3.6. Server where project is deployed is GLASS FISH.
ANDROID: - Android is an operating system based on Linux with a Java programming

interface. Android is a mobile operating system (OS) developed by Google. Android is the first
completely open source mobile OS. Building on the contributions of the open-source Linux
community and more than 300 hardware, software, and carrier partners, Android has rapidly
become the fastest-growing mobile OS. A mobile application (or mobile app) is a software
application designed to run on smart phones, tablet computers and other mobile devices.
Mobile apps were originally offered for general productivity and information retrieval,
including email, calendar, contacts, and stock market and weather information. Android
operating system is a stack of software components which is roughly divided into five sections
and four main layers. The Application Framework layer provides many higher-level services
to applications in the form of Java classes. Application developers can make use of these
services in their applications.
HTML5: - HTML5 is the latest evolution of the standard that defines HTML. The term
represents two different concepts. It is a new version of the language HTML, with new
elements, attributes, and behaviors, and a larger set of technologies that allows the building of
more diverse and powerful Web sites and applications. This set is sometimes called HTML5
& friends and often shortened to just HTML5.
JAVASCRIPT:- JavaScript ("JS" for short) is a full-fledged dynamic programming language

that, when applied to an HTML document, can provide dynamic interactivity on websites. It
was invented by Brendan Eich, co-founder of the Mozilla project, the Mozilla Foundation, and
the Mozilla Corporation. JavaScript is incredibly versatile. You can start small, with carousels,
image galleries, fluctuating layouts, and responses to button clicks. With more experience,
you'll be able to create games, animated 2D and 3D graphics, comprehensive database-driven
apps, and much more. JavaScript itself is compact yet very flexible.
JQUERY: - jQuery is a fast, small, and feature-rich JavaScript library. It makes things like
HTML document traversal and manipulation, event handling, animation, and Ajax much
simpler with an easy-to-use API that works across a multitude of browsers. With a combination
of versatility and extensibility, jQuery has changed the way that millions of people write
JavaScript. Query also provides a paradigm for event handling that goes beyond basic DOM
element selection and manipulation. The event assignment and the event callback function
definition are done in a single step in a single location in the code. jQuery also aims to
incorporate other highly used JavaScript functionality.
5
JAVA EE: - Java Platform, Enterprise Edition (Java EE) is the standard in community-driven
enterprise software. Java EE is developed using the Java Community Process, with
contributions from industry experts, commercial and open source organizations, Java User
Groups, and countless individuals. Each release integrates new features that align with industry
needs, improves application portability, and increases developer productivity. Java EE 8
continues to improve API and programming models needed for today's applications and adds features
requested by our world-wide community. This release modernizes support for many industry standards
and continues simplification of enterprise ready APIs.
MySQL: - MySQL Enterprise Edition includes the most comprehensive set of advanced
features, management tools and technical support to achieve the highest levels of MySQL
scalability, security, reliability, and uptime. It reduces the risk, cost, and complexity in
developing, deploying, and managing business-critical MySQL applications. Oracle MySQL
Cloud Service is built on MySQL Enterprise Edition and powered by Oracle Cloud, providing
an enterprise-grade MySQL database service
GLASS FISH:- Glassfish is an open-source application server project started by Sun

Microsystems for the Java EE platform and now sponsored by Oracle Corporation. The
supported version is called Oracle Glassfish Server. Glassfish is free software, dual-licensed
under two free software licenses: the Common Development and Distribution License (CDDL)
and the GNU General Public License (GPL) with the class path exception. Glassfish is the
reference implementation of Java EE and as such supports Enterprise JavaBeans, JPA, Java
Server Faces, JMS, RMI, Java Server Pages, servlets, etc. This allows developers to create
enterprise applications that are portable and scalable, and that integrate with legacy
technologies. Optional components can also be installed for additional services.
6
CHAPTER-2
SOFTWARE DESIGN
2.1 DATA FLOW DIAGRAMS
These are commonly used during problem analysis. They are quite general and are useful in
understanding the systems. DFDs show the flow of data through the systems, it uses a system
as a function that transforms the inputs to desired outputs.
DFD NOTATIONS:
✓ DATA FLOW
(Arrows)
✓ TRANSFORMATION OF DATA
(Bubble)
✓ Data Store
7
2.1.1 Level 0 DFD: -
Rehras
User Sewa Database
Fig.2.1.1 Level 0 DFD
2.1.2 Level 1 DFD: -
User Registration Database
Login Check User

Not Verified
Forget
Verified
Password
Home Page
8
2.1.3 Level 2 DFD:-
9
2.1.4 Level 3 DFD:-
10
2.2 Data Base Design
2.2.1 ER Diagram:-
Fig.2.2.1 ER Diagram
11
2.2.2 Block Diagram
MODEM
WWW
SERVER
MOBILE CLIENT
MOBILE CLIENT
Fig.2.2.2 Block Diagram
2.2.3 Data Tables
2.2.3.1 Admin Login

2.2.3.2 Users
2.2.3.3 Donors Detail
2.2.3.4 Receivers Detail
2.2.3.5 Requested Donors Detail
2.2.3.6 Blood Donation Detail
2.2.3.7 Donors History Detail
2.2.3.8 Receivers History Detail
2.2.3.9 Feedback Detail
2.2.3.10 Contact Us Detail
2.2.3.11 Sliders
12
2.2.3.1 Admin Login
Table 2.2.3.1 Admin Login
2.2.3.2 Users
Table 2.2.3.2 Users
13
2.2.3.3 Donors Detail
Table 2.2.3.3 Donors Detail
2.2.3.4 Receivers Detail
Table 2.2.3.4 Receivers Detail
2.2.3.5 Requested Receivers Detail
Table 2.2.3.5 Requested Receivers Detail
14
2.2.3.6 Blood Donation Detail
Table 2.2.3.6 Blood Donation Detail
2.2.3.7 Donors History Detail
Table 2.2.3.7 Donors History Detail
15
2.2.3.8 Receivers History Detail
Table 2.2.3.8 Receivers History Detail
2.2.3.9 Feedback
Table 2.2.3.9 Feedback
16
2.2.3.10 Contact Us Detail
Table 2.2.3.10 Contact Us Detail
2.2.3.11 Sliders
Table 2.2.3.11 Sliders
17
CHAPTER-3
MODULES
This is an online blood donor finder system that helps in finding the blood to nearby places.
The project consists of a central depository containing various blood deposits available along
with associated details. These details include blood type, storage area and date of storage.
Maintenance and the monitoring of blood deposits become easy with the help of this system.
The project is an online system that provides an option to check the availability of the required
blood group within the blood bank. Moreover, the system also has added features such as
patient name and contacts, blood booking and requirement of blood group is posted on the App
to find available donors for a blood emergency.
3.1 Main Modules
3.1.1 Splash Screen
Fig.3.1 Splash Screen
18
3.1.2 Home
Fig. 3.2 Home Screen Fig. 3.3 Detailed Home Screen
Fig. 3.4 Modules of Home Screen
19
3.1.3 Main Login
Fig. 3.5 Main Login
3.1.4 Gallery: Every user can see the images through this activity.
Fig. 3.6 Gallery Fig. 3.7 Gallery Image
20
3.1.5 About Us: This activity will provide information about our team of project.
Fig. 3.8 About Us
3.1.6 Contact Us: This page will provide contact support for user with team of project.
Here a user can contact team member if some problem occurs. A user also can appraise the
work of team member.
Fig. 3.9 Contact Us
21
3.1.7 Feedback: Every user can ask any type of query from this module and send
feedback through this module
Fig. 3.10 Feedback
3.1 ADMIN Module
3.2.1 Login: Admin can be able to manage the Donor, Receiver and Emergency
User only by Login into this App.
Fig. 3.11 Admin Login
22
3.2.2 Forgot Password: Admin can submit email to check the password if he
forgot.
Fig. 3.12 Admin Forgot Password
3.2.3 Gallery: Admin can insert the images in this module.
Fig. 3.13 Admin Gallery Fig. 3.14 Admin Gallery Image
23
3.2.4 Donor Detail: In this activity admin can see all the details of the Donor.
Fig. 3.15 Donors Detail Fig. 3.16 Full Donor Detail
3.2.5 Receiver Detail: In this activity admin can see all the details of Receiver.
Fig. 3.17 Receivers Detail
3.2.6 Donation Detail: In this admin can check the donation details.
Fig. 3.18 Donations Detail
24
3.2.7 Show Feedback: In this activity admin can see all the feedbacks given by
users.
Fig. 3.19 Check Feedback
3.3 USER Module.
3.3.1 Receiver Module: Receiver can be able to find the nearby Donor only by
registering into this App.
a. Sign-Up: In this activity Receiver can register himself by provide some

basic information about himself which save in backend.
Fig. 3.20 Receiver Sign Up Fig. 3.21 Receiver Register
25
b. Login: User login module is for registered user who has successfully
completed sign up process. When the main page runs there is link for user
login in home activity. A user can login through link. When user inputs
data in this page, the given data will compare to the data in user sign up
table from database. Receiver can sign in with valid username and
password. He can also Sign-In with Facebook and Google.
Fig. 3.22 Receiver Login
c. Forgot Password: Admin can submit email to check the password if he

forgot.
Fig. 3.23 Receiver Forgot Password
26
d. Home: This is the main activity which is shown after Login. User also
can send feedback to the team member.
Fig. 3.24 Receiver Home Page
e. Find Donor: This is very important activity for our project. This provides
filter features where we can filter from the list of users based on their
blood group and name or by locality. The aim of making this page so
relevant is to make user too easier to search the user who is in need or the
person from we can contact urgently. If a user, simply types the single
letter of name the this will search the related name whose name is starting
with. The list of all donors is shown in this activity. The receiver can find
the donor according to the state and city. The receiver can send request
to donor.
Fig. 3.25 Find Donor
27
Fig. 3.26 Full Donor Detail
Fig. 3.27 Send Request to Donor
28
f. Accepted Requests: Here receiver can see those donors who accepted
their requests. Receivers can confirm the donation after receives the
blood.
Fig. 3.28 Accepted Requests
g. Gallery: All the images are seen in this activity which is inserted by the
Admin.
Fig. 3.29 Receiver Gallery Fig. 3.30 Receiver Gallery Image
29
h. Profile: When a user successfully login into the system then their profile
page opens. Profile activity is the graphical portal for a user. Here a user
can upload their profile picture and they can delete their account too. A
user can see their data that he has provided at the time of sign up. User
can search data on clicking search donor link. This page will profile
picture of then this page will open. In this page user simply can change
their profile picture. A user will have to select image and click on upload
file.
Fig. 3.31 Receiver Profile
i. History: Receiver can check their history. It shows that when, where and
by whom receiver can take the blood.
Fig. 3.32 Receiving History
30
j. About Us: This activity will provide information about our team of
project.
Fig. 3.33 Receiver About Us
k. Contact Us: This page will provide contact support for user with team of
project. Here a user can contact team member if some problem occurs. A
user also can appraise the work of team member.
Fig. 3.34 Receiver Contact Us
31
l. Feedback: Receivers can ask any type of query from this module and
send feedback through this module
Fig. 3.35 Receiver Feedback
32
3.3.2 Donor register: Donor can be able to donate the Blood only by registering into this App.
a. Sign Up: In this activity Receiver can register himself by provide

some basic information about himself which save in backend.
Fig. 3.36 Donor Sign Up Fig. 3.37 Donor Register
33
b. Login: User login module is for registered user who has

successfully completed sign up process. When the main page runs
there is link for user login in home activity. A user can login
through link. When user inputs data in this page, the given data
will compare to the data in user sign up table from database.
Receiver can sign in with valid username and password. He can
also Sign-In with Facebook and Google.
Fig. 3.38 Check Feedback
c. Forgot Password: Admin can submit email to check the

password if he forgot.
Fig. 3.39 Donor Forgot Password
34
d. Home: This is the main activity which is shown after Login. User
also can send feedback to the team member.
Fig. 3.40 Donor Home Page
e. Receiver Requests: This is very important activity for our

project. This show the list of requested receivers to the donor. The
donor can allow or may deny the receiver request.
Fig. 3.41 Receiver Requests
35
f. Confirm Receiver: Here donors can confirm the donation after

donating the blood to receiver.
Fig. 3.42 Confirm Donation
g. Gallery: All the images are seen in this activity which is inserted
by the Admin.
Fig. 3.43 Donor Gallery Fig. 3.44 Donor Gallery Image
36
h. Profile: When a user successfully login into the system then their
profile page opens. Profile activity is the graphical portal for a
user. Here a user can upload their profile picture and they can
delete their account too. A user can see their data that he has
provided at the time of sign up. User can search data on clicking
search donor link. This page will profile picture of then this page
will open. In this page user simply can change their profile
picture. A user will have to select image and click on upload file.
Fig. 3.45 Donor Profile
i. History: Receiver can check their history. It shows that when,

where and by whom receiver can take the blood.
Fig. 3.46 Donation History
37
j. About Us: This activity will provide information about our team
of project.
Fig. 3.47 Donor About Us
k. Contact Us: This page will provide contact support for user with
team of project. Here a user can contact team member if some
problem occurs. A user also can appraise the work of team
member.
Fig. 3.48 Donor Contact Us
38
l. Feedback: Donors can ask any type of query from this

module and also send feedback through this module
Fig. 3.49 Donor Feedback
39
CHAPTER-4
TESTING
Software testing is an activity to check whether the actual results match the expected results
and to ensure that the software system is Defect free. It involves execution of a software
component or system component to evaluate one or more properties of interest.
Software testing also helps to identify errors, gaps or missing requirements in contrary to the
actual requirements. It can be either done manually or using automated tools. Some prefer
saying Software testing as a white box and Black Box Testing.
4.1 Need of Testing: -

Testing is important because software bugs could be expensive or even dangerous. Software
bugs can potentially cause monetary and human loss. Software Testing is necessary because
we all make mistakes. Some of those mistakes are unimportant, but some of them are expensive
or dangerous. We need to check everything and anything we produce because things can
always go wrong – humans make mistakes all the time. nice we assume that our work may
have mistaken, hence we all need to check our own work. However, some mistakes come from
bad assumptions and blind spots, so we might make the same mistakes when we check our own
work as we made when we did it. So, we may not notice the flaws in what we have done.
Ideally, we should get someone else to check our work because another person is more likely
to spot the flaws.
There are several reasons which clearly tells us as why Software Testing is important and what
are the major things that we should consider while testing of any product or application.
Software testing is very important because of the following reasons:
1. Software testing is really required to point out the defects and errors that were made
during the development phases.
2. It’s essential since it makes sure of the Customer’s reliability and their satisfaction in the
application.
3. It is very important to ensure the Quality of the product. Quality product delivered to
the customers helps in gaining their confidence. (Know more about Software Quality)
4. Testing is necessary in order to provide the facilities to the customers like the delivery
of high quality product or software application which requires lower maintenance cost
and hence results into more accurate, consistent and reliable results.
5. Testing is required for an effective performance of software application or product.
6. It’s important to ensure that the application should not result into any failures because it
can be very expensive in the future or in the later stages of the development.
7. It’s required to stay in the business
40
Types of testing
• Unit testing
• Integration testing
• System testing
• Acceptance testing
4.1.1 Unit testing: -
A unit is the smallest testable part of software. It usually has one or a few inputs and usually
a single output. In procedural programming a unit may be an individual program, function,
procedure, etc. In object-oriented programming, the smallest unit is a method, which may
belong to a base/ super class, abstract class or derived/ child class. (Some treat a module of
an application as a unit. This is to be discouraged as there will probably be many individual
units within that module. Unit testing increases confidence in changing/ maintaining code.
If good unit tests are written and if they are run every time any code is changed, we will be
able to promptly catch any defects introduced due to the change. Also, if codes are already
made less interdependent to make unit testing possible, the unintended impact of changes
to any code is less.
Codes are more reusable. To make unit testing possible, codes need to be modular. This
means that codes are easier to reuse.
4.1.2 Integration testing: -
The purpose of this level of testing is to expose faults in the interaction between integrated
units. Test drivers and test stubs are used to assist in Integration Testing. During the process
of manufacturing a ballpoint pen, the cap, the body, the tail and clip, the ink cartridge and
the ballpoint are produced separately, and unit tested separately. When two or more units
are ready, they are assembled, and Integration Testing is performed. For example, whether
the cap fits into the body or not. Any of Black Box Testing, White Box Testing, and Gray
Box Testing methods can be used. Normally
4.1.3 System testing: -
It is a level of the software testing where a complete and integrated software is tested.
During the process of manufacturing a ballpoint pen, the cap, the body, the tail, the ink
cartridge and the ballpoint are produced separately, and unit tested separately. When two
or more units are ready, they are assembled, and Integration Testing is performed. When
the complete pen is integrated, System Testing is performed. System Testing is performed
after Integration Testing and before Acceptance Testing.
41
4.1.4 Acceptance testing: -
Acceptance Testing is a level of the software testing where a system is tested for
acceptability. Formal testing with respect to user needs, requirements, and
business processes conducted to determine whether a system satisfies the acceptance
criteria and to enable the user, customers or other authorized entity to determine whether
or not to accept the system Usually, Black Box Testing method is used in Acceptance
Testing. Testing does not normally follow a strict procedure and is not scripted but is rather
ad-hoc. Acceptance Testing is performed after System Testing and before making the
system available for actual use.
1.2 Test Plan: -

Testing is an extremely critical and time-consuming activity. It requires proper planning of
overall testing process. Testing process starts with a test plan. This test plan identifies all
the testing related activities that must be performed and specifies the schedule, allocates
the resources, and specified guidelines for testing. The test plan specifies conditions that
should be tested, different units to be tested, and way the module will be integrated
together.
Steps followed in testing overall UMS: -
• First, unit testing is performed. Each module of the system was tested separately so
that there are no syntax and logical errors.
• Integration testing was performed next by combining tested modules into
subsystems. Here we tested module interaction
• When the development of whole system was completed, we performed overall
system testing to discover any remaining errors.
• Next, we perform testing by installing the server and upload web portal on server.
• At the end acceptance testing was performed
42
CHAPTER-5
SCOPE OF THE PROJECT
It may help collecting perfect management in detail. In a very short time, the collection will be
obvious simple and sensible. It will help a person to know the management of passed year
perfectly. It also helps in current all works relative to Organization. This App bring all type
Blood donors in contact to the needy people in such a way that no one to suffer from
insufficiency of blood on demand It will be also reduced the cost of collecting the management
and collection procedure will go on smoothly.
43
CHAPTER-6
CONCLUSION
Provides the searching facilities based on various factors. Such as Donor, Blood Group
according to state and city. Blood Donor Finder System also manage the Record details online
for Blood Group. It tracks all the details about the Donor, Receiver, Blood Group. Data is
secured under password protection. By using this application, we can overcome the problem
which we are facing in current scenario and we can introduce a new way to find blood donors.
Aim to quickly make connection between user and donor. Most efficient in Emergency
Situation. Know the current donor details and Blood Group. If shortage, we can maintain Blood
stock in advance. Can be used by both donor and non-donor. Proper authorization will increase
the security of data stored in the database. Facility to easily add, finds, edit and delete any
information by ADMIN. No formal language is needed for the user to use this system. Have a
good User interface. Thus, it is user-friendly. Efficient performance. Show the information and
description of the Blood Bank and Donor. The BDF App had been developed in accordance to
user requirement. This is to make sure that the management of the blood group became
effective, systematic and meeting user requirements. The functional services provided in the
current version are profile management.
44
CHAPTER-7
FUTURE WORK
• The Rehras Sewa (Blood Donor Finder App) can be enhanced to include some other
functionality like location tracking.
• Location Listener based on the donors and receiver’s locations can be added.
• There is Different Module will be added for admin to delete the donor’s or receiver’s
detail.
• Notification functionality can be added to this App.
• The functionality that edit the individuals detail will be added.
• Social networking can also be added wherein donors and receivers can interact with
each other.
• Functionality of that and messages can be added.
• There is Different Module will be added for admin to maintain the donor’s and
receiver’s entries.
• New servers can be installed if data increased in future.
• Installing different mails servers to attach emails of donors and receivers.
• Android app and iOS apps will be developed in future for doing routine works from
induvial mobile only like Blood Bank System.
45
CHAPTER-8
REFERENCES
BOOKS
• O’Reilly – JAVA EE
• O’Reilly – MYSQL
• O’Reilly – JavaScript
• The Complete Reference Java 2
• Bootstrap Help book code ninja
• RDBMS
WEBSITES
• http://www.oracle.com/technetwork/java/javaee/overview/compatibility-jsp-
136984.html
• https://adtmag.com/articles/2017/09/12/java-ee-moving-to-eclipse.aspx
• https://javaee.github.io/tutorial/
• https://www.mysql.com/
• https://www.w3schools.com/php/php_mysql_update.asp
• YouTube channel Java Brains
• stackoverflow.com website
• javatpoint.com
46

Chapter-1: 1.1 General Introduction

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter-1: 1.1 General Introduction

Uploaded by

Copyright:

Available Formats

Sant Baba Bhag Singh Institute of Engineering and Technology

Our main objective of developing this project are as follows:

1.1.3 Proposed System

Possible outcomes of our project will be as follows:

1.2 HARDWARE AND SOFTWARE REQUIREMENTS

Following facilities are required for developing the App:

I) Android Studio 3.0.1

II) Android SDK (API Level 27 and API Level 26)

III) Mozilla Firefox Developer Edition (Latest available)

IV) Internet Access

V) OS: Ubuntu / Mac OSX / Windows 10

VI) MySQL Database

1.2.2 Minimum Hardware Requirements:

II) RAM – 8GB

III) Hard disk Space – 20GB

IV) Processor Intel i5 6th Gen

V) Android Device with Marshmallow (Android version 6)

Following facilities are required to run the App:

I) Nginx Web Server

III) OS: Microsoft Windows Server 2012 / Ubuntu

III) MySQL Database

1.2.4 Minimum Hardware Requirements:

I) Computer System Server (dedicated/virtual)

II) Static IP Connection

III) RAM – 2GB

IV) Hard disk Space – 20GB

V) Processor- i3 5th Gen

1.3 Technology Used: -

ANDROID: - Android is an operating system based on Linux with a Java programming

JAVASCRIPT:- JavaScript ("JS" for short) is a full-fledged dynamic programming language

GLASS FISH:- Glassfish is an open-source application server project started by Sun

2.1 DATA FLOW DIAGRAMS

2.1.1 Level 0 DFD: -

Fig.2.1.1 Level 0 DFD

2.1.2 Level 1 DFD: -

User Registration Database

Login Check User

Fig.2.1.2 Level 1 DFD

2.1.3 Level 2 DFD:-

Fig.2.1.3 Level 2 DFD

2.1.4 Level 3 DFD:-

Fig.2.1.4 Level 3 DFD

2.2 Data Base Design

2.2.2 Block Diagram

Fig.2.2.2 Block Diagram

2.2.3 Data Tables

2.2.3.1 Admin Login

2.2.3.1 Admin Login

Table 2.2.3.1 Admin Login

Table 2.2.3.2 Users

2.2.3.3 Donors Detail

Table 2.2.3.3 Donors Detail

2.2.3.4 Receivers Detail

Table 2.2.3.4 Receivers Detail

2.2.3.5 Requested Receivers Detail

Table 2.2.3.5 Requested Receivers Detail

2.2.3.6 Blood Donation Detail

Table 2.2.3.6 Blood Donation Detail

2.2.3.7 Donors History Detail

Table 2.2.3.7 Donors History Detail

2.2.3.8 Receivers History Detail

Table 2.2.3.8 Receivers History Detail

Table 2.2.3.9 Feedback