,,

A PROJECT REPORT ON

A SMART SYSTEM FOR DONATION HANDLING

OF CHARITABLE TRUSTs AND NGOs

SUBMITTED TO THE SAVITRIBAI PHULE PUNE UNIVERSITY ,

PUNE IN THE PARTIAL FULFILLMENT OF THE REQUIREMENTS
FOR THE AWARD OF THE DEGREE

BACHELOR OF ENGINEERING
(Computer Engineering)

BY

Salve Stella Raju PRN No: 71629043L

Kedari Aishwarya Santosh PRN NO: 71849049F

Under The Guidance of

Prof. Shelar S.R.

DEPARTMENT OF COMPUTER ENGINEERING

ADSUL TECHNICAL CAMPUS FACULTY OF
ENGINEERING CHAS, AHMEDNAGAR 414005
SAVITRIBAI PHULE PUNE UNIVERSITY, PUNE
2019 - 2020
 CERTIFICATE
This is to certify that the Project Entitled
A SMART SYSTEM FOR DONATION HANDLING
OF CHARITABLE TRUSTs AND NGOs

Submitted by

Salve Stella Raju PRN No: 71629043L

Kedari Aishwarya Santosh PRN NO: 71849049F

is a bonafide work carried out by them under the supervision of Prof.Shelar

S.R. and it is approved for the partial fulfillment of the requirement of
Savtribai Phule Pune university, Pune for the award of the degree of Bachelor
of Engineering (Computer Engineering).

Prof.Shelar S.R. Prof.Shelar S.R.

Guide H.O.D
Dept. of Computer Engg. Dept. of Computer Engg.

Principal
Adsul Technical Campus Faculty Of Engineering

Signature of Internal Examiner Signature of External Examiner

 PROJECT APPROVAL SHEET

A Project Report Titled as

A SMART SYSTEM FOR DONATION HANDLING

OF CHARITABLE TRUSTs AND NGOs

Is verified for its originality in documentation, problem statement, proposed

work and implementation successfully completed by

Salve Stella Raju PRN No: 71629043L

Kedari Aishwarya Santosh PRN NO: 71849049F

at

DEPARTMENT OF COMPUTER ENGINEERING

Adsul Technical Campus Faculty Of Engineering

SAVITRIBAI PHULE PUNE UNIVERSITY,PUNE

ACADEMIC YEAR 2019-2020

Prof.Shelar S.R. Prof.Shelar S.R.

Dept. of Computer Engg. Dept. of Computer Engg.
 Abstract

This Project is aimed to developing an online blood, clothes, food and money
donation . The entire project has been developed keeping in view of dis-
tributed client server computing technology in mind. Through this appli-
cation any person who is interested in donating the blood, money, clothes
and money can register himself. Admin is the main authority who can do
addition, deletion, and modification if required. The process of managing
the blood bag that is received from the blood donation events needs a proper
and systematic management. The process of managing the blood bag that
is received from the blood donation events needs a proper and systematic
management The process of managing the blood bag that is received from
the blood donation events needs a proper and systematic management. The
process of managing the blood bag that is received from the blood donation
events needs a proper and systematic management. The process of manag-
ing the blood, food, clothes and money bag that is received from the blood
donation events.

Dept of Computer Engineering, ATCFOE, Pune 2019-20 I

 Acknowledgments

It gives us great pleasure in presenting the preliminary project report on ‘A

SMART SYSTEM FOR DONATION HANDLING OF CHARI-
TABLE TRUSTs AND NGOs’.

I would like to take this opportunity to thank my internal guide Prof.Shelar

S.R for giving me all the help and guidance I needed. I am really grateful
to them for their kind support. Their valuable suggestions were very helpful.

I am also grateful to Prof. Chaudary M., Head of Computer Engineering

Department, Sinhgad College of Engineering for his indispensable support,
suggestions.

In the end our special thanks to Family for providing various resources such
as laboratory with all needed software platforms, continuous Internet con-
nection, for our Project.

Miss. Salve Stella Raju

Miss. Kedari Aishwarya Santosh

(B.E. Computer Engg.)

Dept of Computer Engineering, ATCFOE, Pune 2019-20 II

Contents

1 Introduction 1
1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Motivation of the Project . . . . . . . . . . . . . . . . . . . . 2
1.3 Problem Definition . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4 Project Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.5 Methodology of Problem Solving . . . . . . . . . . . . . . . . 3

2 Literature Survey 5
2.1 Literature Survey . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 Software requirement specification 13

3.1 Assumptions and Dependencies . . . . . . . . . . . . . . . . . 14
3.2 Functional Requirements . . . . . . . . . . . . . . . . . . . . . 14
3.2.1 System feature . . . . . . . . . . . . . . . . . . . . . . 14
3.3 External interface requirements . . . . . . . . . . . . . . . . . 14
3.3.1 User interfaces . . . . . . . . . . . . . . . . . . . . . . 14
3.4 Hardware interfaces . . . . . . . . . . . . . . . . . . . . . . . . 14
3.5 Software interfaces . . . . . . . . . . . . . . . . . . . . . . . . 14
3.6 Communication interfaces . . . . . . . . . . . . . . . . . . . . 16
3.7 Non Functional Requirements . . . . . . . . . . . . . . . . . . 16
3.7.1 Performance Requirement . . . . . . . . . . . . . . . . 16
3.7.2 Safety Requirement . . . . . . . . . . . . . . . . . . . . 16
3.7.3 Security Requirement . . . . . . . . . . . . . . . . . . . 16
3.7.4 Software Quality Attributes . . . . . . . . . . . . . . . 16
3.8 System Requirements . . . . . . . . . . . . . . . . . . . . . . . 17
3.8.1 Database Requirements . . . . . . . . . . . . . . . . . 17
3.9 Software Requirements(Platform Choice) . . . . . . . . . . . . 17
3.10 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . 17

4 System Design 18
4.1 Architectural Design . . . . . . . . . . . . . . . . . . . . . . . 19
4.2 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . 21
 4.2.1 Level 0 Data Flow Diagram . . . . . . . . . . . . . . . 21
4.2.2 Level 1 Data Flow Diagram . . . . . . . . . . . . . . . 21
4.3 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . 21
4.4 Activity Diagram: . . . . . . . . . . . . . . . . . . . . . . . . . 23

5 Project Plan 27
5.1 Project Estimates . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.1.1 Reconciled Estimates . . . . . . . . . . . . . . . . . . . 28
5.1.2 Project Resources . . . . . . . . . . . . . . . . . . . . . 30
5.2 Risk Management w.r.t. NP Hard analysis . . . . . . . . . . . 30
5.2.1 Risk Identification . . . . . . . . . . . . . . . . . . . . 30
5.2.2 Risk Analysis . . . . . . . . . . . . . . . . . . . . . . . 31
5.2.3 Overview of Risk Mitigation, Monitoring, Management 32
5.3 Project Schedule . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.3.1 Project task set . . . . . . . . . . . . . . . . . . . . . . 32
5.3.2 Task network . . . . . . . . . . . . . . . . . . . . . . . 34
5.3.3 Timeline Chart . . . . . . . . . . . . . . . . . . . . . . 34
5.4 Team Organization . . . . . . . . . . . . . . . . . . . . . . . . 35
5.4.1 Team structure . . . . . . . . . . . . . . . . . . . . . . 36
5.4.2 Management reporting and communication . . . . . . . 37

6 Project Implementation 38
6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.2 Tools and Technologies Used . . . . . . . . . . . . . . . . . . . 39
6.3 Methodologies/Algorithm Details . . . . . . . . . . . . . . . . 41
6.4 Verification and Validation for Acceptance . . . . . . . . . . . 41

7 Software Testing 43
7.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
7.2 Scope of Testing . . . . . . . . . . . . . . . . . . . . . . . . . . 44
7.3 Software to be tested . . . . . . . . . . . . . . . . . . . . . . . 44
7.4 Test Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
7.5 Type of Testing . . . . . . . . . . . . . . . . . . . . . . . . . . 45
7.6 Test Cases and Test Results . . . . . . . . . . . . . . . . . . . 46

8 Result 49
8.1 SCREENSHOT . . . . . . . . . . . . . . . . . . . . . . . . . . 50

9 Conclusion and Future Scope 58

References 59

Dept of Computer Engineering, ATCFOE, Pune 2019-20 IV

Annexure A 62
List of Figures

4.1 Architecture diagram . . . . . . . . . . . . . . . . . . . . . . . 20

4.2 Level 0 Data flow diagram . . . . . . . . . . . . . . . . . . . . 21
4.3 Level 1 Data flow diagram . . . . . . . . . . . . . . . . . . . . 21
4.4 Use case diagram . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.5 Activity diagram . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.6 class diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.7 sequence diagram . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.8 State diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

8.1 SCREENSHOT 1 . . . . . . . . . . . . . . . . . . . . . . . . . 50
8.2 SCREENSHOT 2 . . . . . . . . . . . . . . . . . . . . . . . . . 51
8.3 SCREENSHOT 3 . . . . . . . . . . . . . . . . . . . . . . . . . 52
8.4 SCREENSHOT 4 . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.5 SCREENSHOT 6 . . . . . . . . . . . . . . . . . . . . . . . . . 54
8.6 SCREENSHOT 7 . . . . . . . . . . . . . . . . . . . . . . . . . 55
8.7 SCREENSHOT 8 . . . . . . . . . . . . . . . . . . . . . . . . . 56
8.8 SCREENSHOT 9 . . . . . . . . . . . . . . . . . . . . . . . . . 57

A.1 P Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
A.2 NP Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
A.3 NP Complete Problem . . . . . . . . . . . . . . . . . . . . . . 65

Dept of Computer Engineering, ATCFOE, Pune 2019-20 VI

List of Tables

3.1 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . 17

5.1 Risk Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

5.2 Risk Probability definitions [?] . . . . . . . . . . . . . . . . . . 31
5.3 Risk Impact definitions [?] . . . . . . . . . . . . . . . . . . . . 32
 CHAPTER 1
INTRODUCTION
1.1 Overview
The entire project has developed keeping in view of distributed client
server . In this project who is intrested in donating (clothe,blood,food,money)
rst we login to our system. Then u will donate like clothe food and money
to NGO. User will donate blood to blood bank. the project is to build an
application program to reduce manual work of managing and also an ease
for the donors to donate. Bangladesh is an emerging country. Every year
many natural disasters like Sidr, Ayla, Tsunami, Cyclone, Tornedo, Flood
etc. took place in this coun-try. At that time innumerable people require
help to overcome from those disasters. There are also so many people who
are su ering from immeasur-able nancial problems. Besides, there are many
unwanted incidents took place in Bangladesh, like garments burning, build-
ing collapse, road accident etc. There are many kind people, who wants to
help those people through donation. Donation System” is such an applica-
tion which will help them to accomplish their donation. Every single time
you help somebody stand up, you are helping humanity rise - Dr. Steve
Maraboli”. Here, helping a single person means helping his family, society
and ultimately the nation.

1.2 Motivation of the Project

To reduce a scam. To see the history of donating Track your donation. To
take anawareness of donation. Our motivation lies within the rich detail that
the results are able to give us, and in the variation and inequalities that our
data continue to reveal. When we look behind the averages we are confronted
with stark realities.

1.3 Problem Definition

The proposed system provides a comprehensive overview of the privacy preser-
vation mechanisms in big data and presents the challenges for existing mech-
anisms. In particular, in this paper, we illustrate the infrastructure of big
data and the state-of-the-art privacy-preserving mechanisms in each stage of
the big data life cycle.

Dept of Computer Engineering, ATCFOE, Pune 2019-20 2

1.4 Project Scope
We will give a comprehensive overview of the state-of-the-art technologies to
preserve privacy of big data at each stage of big data life cycle. Moreover,
we will discuss and manage the details of the donors and the things they
are donating. It will also display the related things available for the needy if
admin and user system. The purpose of the project is to build an application
program to reduce manual work of managing and also an ease for the donors
to donate.

1.5 Methodology of Problem Solving

We are using waterfall model for our project.

1. Requirement Gathering and Analysis: In this step of waterfall we iden-

tify what are various requirements are need for our project such are
software and hardware required, database, and interfaces.
2. System Design: In this system design phase we design the system which
is easily understood for end user i.e. user friendly. We design some

Dept of Computer Engineering, ATCFOE, Pune 2019-20 3

 UML diagrams and data flow diagram to understand the system flow
and system module and sequence of execution.

3. Implementation: In implementation phase of our project we have im-

plemented various module required of successfully getting expected out-
come at the different module levels. With inputs from system design,
the system is first developed in small programs called units, which are
integrated in the next phase. Each unit is developed and tested for its
functionality which is referred to as Unit Testing.

4. Testing: The different test cases are performed to test whether the
project module are giving expected outcome in assumed time. All
the units developed in the implementation phase are integrated into a
system after testing of each unit. Post integration the entire system is
tested for any faults and failures.

5. Deployment of System: Once the functional and non-functional testing

is done, the product is deployed in the customer environment or released
into the market.

6. Maintenance: There are some issues which come up in the client en-
vironment. To fix those issues patches are released. Also to enhance
the product some better versions are released. Maintenance is done to
deliver these changes in the customer environment. All these phases
are cascaded to each other in which progress is seen as flowing steadily
downwards like a waterfall through the phases. The next phase is
started only after the defined set of goals are achieved for previous
phase and it is signed off, so the name Waterfall Model. In this model
phases do not overlap.
 CHAPTER 2
LITERATURE SURVEY
2.1 Literature Survey
Dr. A. Meiappane , K.Logavignesh , R. Prasanna ,T. Sakthivel,IEEE AC-
CESS,DWORLD: Blood Donation App Using Android in this paper ad-
vantages are access information such as the nearby hospitals and the blood
banks and the availability of blood banks. And disadvantages are technolo-
gies, there is not many options and advancement in the end of blood donation.
Zahid Ahmed, Sabina Yasmin,University of Science Bejing,Helping Hand An
efficient Donation Procedure based on Mobile Banking the advantages are
donation procedure can be completed within a short time by using mobile
banking and the disadvantages are Spyware Flexi spy: In an SMS based pay-
ment system such malware could seriously impact the privacy of the user

Paper Name: Helping Hand an efficient Donation Procedure based on

Mobile Banking.

Authors: Zahid Ahmed Department of IT UITS Dhaka, Bangladesh ahmed.,

Sabina Yasmin Department of IT UITS Dhaka, Bangladesh ,Al Imtiaz De-
partment of CSE UITS Dhaka, Bangladesh

Description: In this society there are too many people who are so suf-
fering from numerous problems. Only a few of them are getting help from
others. Some people may present their problems through electronic and press
media, but most of the distressed people cannot express their problems to
others. Even some people are not getting sufficient help as they need. The
drawbacks of present system are: 1. Bureaucratic complexity of Donation
Process 2. Present manual procedures are time consuming 3. Formal Bank-
ing procedure is not user friendly. 4. Unavailability of Common platform
for donation 5. Lack of Communication between Donor and Needy people.
6.Unavailability of the list of needy people 7. Fraud Detection prevention
procedure is very poor. 8. A large number of needy people could not express
their appeal to others 9. There is no common platform for micro donation
(E.g. Students). 10. Donors have to depend on the third parties, who de-
cide how and for whom the donation will be utilized. There are many more
draw-backs of present procedure. At present the donor have to face much
hassle to donate others.

Conclusion: The impact of donation on socioeconomic is enormous. With

the help of ”Helping Hand” the donation procedure will be more popular,
easier, faster and effective than ever. In most of the case the security of this

Dept of Computer Engineering, ATCFOE, Pune 2019-20 6

application depends on internet and mobile banking. A Strong network of
Host is required to ensure the efficiency of fraud detection and prevention.
This mobile application with the help of mobile banking will change the con-
cept of formal donation procedure.

Paper Name: Transforming In-kind Giving in Disaster Response: A Case

for Online Donation Registry with Retailers.

Author:Md. Moinul Islam, John Vande Vate School of Industrial and Sys-
tems Engineering Georgia Institute of Technology Atlanta, USA

Description: Whats known as the second disaster, a result of unsolicited

inkind donations, has been a long-standing problem in disaster relief. Over
the years, NGOs have tried to convince donors to contribute only cash in an
effort to reduce the impact of this issue. The cash only” approach, however,
has not been fully successful and the burden of unsolicited donations con-
tinues to cripple NGO relief operations in all major disasters although cash
giving is most convenient for NGOs, it does not have the same emotional
appeal for donors. In-kind donations are more tangible, specific, and often
the most economical way to give. Yet because there is no formal mechanism
to ensure they are appropriate and productive, unsolicited in-kind donations
pose a challenge in disaster response. By establishing an on - line donation
registry with national retailers, NGOs can solicit targeted in-kind donations
for disaster relief in a timely fashion.. During the Superstorm Sandy response
in 2012, a group in New York proved this concept can work by repurposing
Amazons wedding registry to solicit relief supplies. They were able to collect
over 35,000 needed items through the registry in the rest few weeks after
the storm. This paper reviews the forces that lead to the second disaster,
describes a successful implementation of the on-line registry as part of the
Superstorm Sandy response, compares the registry with a donation portal
such as the Aid matrix national donation portal and discusses the challenges
and opportunities for implementing a registry on a national scale.

Conclusion: Despite the efforts to stop it, in-kind donations to disaster

response will continue unabated. A national on-line donation registry to-
getherwith an enhanced donation portal can transform some of the energies
and resources that are today wasted in creating the second disaster into a
value-able new source of timely and targeted relief supplies. What are we
waiting for? The next disaster?

Paper Name: Smart Donation Machine - Automation of donation process

Dept of Computer Engineering, ATCFOE, Pune 2019-20 7

using Arduino Authors: K V Sai Krishna1, P V Indu Bhanu2, B.Valarmathi3
Descriptions The main purpose of this project is to automate the donation
process. Our intention is to support all the programs conducted by the char-
ity organizations, so this project welcomes all those who helps and supports
the citizens in the charities by providing donations in the donation machine
where the machine is designed in such a way that it can sense, send a mes-
sage, captures picture and posts a message in social networking sites. This
project works in the real-time environment to automate the process.

Conclusion: Smart Donation machine will take the process of donating to

the next level. With the increase of popularity of social networks as people
now-a-days are addicted to these networking sites, we integrated the process
of tweeting a message in our project. The process of emptying the bin is made
easy by just sending messages/calls to the respective organization when the
billings. It encourages the individuals and many groups by the automation
of social networking sites. The future work is described as we discussed ear-
lier in the constraints and trade s topic, it cannot recognize the objects but
can just sense the donations that has been donated.By implementing Digital
Image Processing, we can recognize the things that have been donated and
also the security to the system will be improved. Finally, this project future
work extends by tweeting the picture taken by the Android mobile camera
application in the social networking site.

Paper Name: Donate.lk: A smart donation handling system Authors:

Pasan Lanerolle Department of Information Technology Sri LankaInstitute of
Information Technology Malabe, Sri Lanka pasan.sampath Description: Sri
Lanka is a small island in the Indian Ocean which is in thepath of two mon-
soons. Therefore, the country is mostly affected by weather related hazards.
Floods are one of the most common hazards that the country faces due to
monsoonal rain or effects of low pressure systems. Droughts due to failure of
monsoonal rain are another common hazard experienced in Sri Lanka. More-
over, Sri Lanka is also prone to hazards such as land-slides, lightning strikes
and coastal erosion. In 2004, almost two-thirds of the Sri Lankan coast was
affected by the Indian Ocean tsunami.State, Non-governmental and Media
organizations in Sri Lanka initiate much needed relief to people affected by
floods and landslides across the country by organizing donation campaigns.
People from all around the country help victims through those campaigns.
While delivering those rations, there have been many conflicts related to
identifying most needed people and what kind of rations they needed. Dur-
ing such disasters, manual labour is hard to end. At present there is no
proper system to manage those donation campaigns to verify equal distribu-

Dept of Computer Engineering, ATCFOE, Pune 2019-20 8

tion of donations to victims. People handle those with difficulty by making
groups through social media which is a temporary solution. All of the above
matters indicate that, a country like ours must have an automated system to
manage donations/rations. Also, by using global servers, an optimum route
will be created to make sure that the rations are delivered and provided to
the people in need. Therefore, as a solution, this paper proposes a system
that manages donations and delivers them to the people in need with fewer
burdens.

Conclusion: Donate.lk is a mobile application developed to enhance the-

donation handling process in Sri Lanka at a time of a disaster using latest
technologies. The main objective of this research is to provide a better solu-
tion for donation handling.The system consists of a web application and the
donation handling process mainly functions through a mobile application.
Therefore, those allocations will be made by analysing the desired donations
and available donation teams. Stocks of donations and Pro ling of those
stocks are mandatory even before setting out to reach the people in need this
sys-tem will expand using mobile ad-hoc network technology. It may be help-
ful when mobile communications are down during disasters. The proposed
solution can be enhanced by several methods. One futuristic idea would be
to expand the proposed application as an island wide system and to improve
the system to handle multiple requests without any delays in analysing and
allocating resources. For further clarifications, the proposed system can be
improved to identify identical twins of a family in crisis.

Paper Name: Data Warehouse Based Analysis with Integrated Blood Do-
nation Management System.

Authors: Giridhar Maji Dept. of Electrical Engineering Asansol Polytech-

nic Asansol, India

Description: Blood donation is an important issue framework with all re-

lated but isolated web based sub systems of a blood management system.
We propose a data warehouse (DW) as an integral part of the integrated
framework to store historical blood donation data in a centralized database
for analytical processing. Proposed system would enable the authorities to
take informed throughout the world to save and manage lives. In order to
make this process more effective an auto-mated system could be built to
monitor and organize blood donation camps. In this paper we developed an
integrated blood donation camping decision based on the analytical reports
from the DW for some area for a particular time and citizen demography.

Dept of Computer Engineering, ATCFOE, Pune 2019-20 9

Finally, we introduce a new measure of humanity (scoring system for good
deeds) of citizens called Philanthropy Score (PS) and Philanthropy League
(PL) derived from PS.In our proposed system after blood collection at do-
nation camps, little health related details would be updated in the blood
management system database and most importantly PS of the donor would
be updated into the national citizens database. A well-advertised communi-
cation would allow the citizens to know about the PS points they can accrue
for every possible good deed. Blood donation is merely a prototype use of
the proposed PS. Keywords-Blood donation campaign management system;
philanthropy score; philanthropy league; OLAP; DW schema.

Conclusion: An integrated framework to manage end to end blood man-

agement process has been devised with front end web modules and back
end databases. Special focus has been given to localized blood donation
campaignmanagement. A data warehouse has been proposed to store his-
torical blood donation camping data so as to take future camp location
and timing decisions based on concrete analytical results instead of political
whim. Donor intimation, registration and scheduling time becomes much
user friendly and convenient. Also nodal user can utilize the analytical re-
ports to estimate the requirement, expected volume and other infrastructure
requirements in advance. A new measure of humanity called philanthropy
score (PS) and based on the PS value a corresponding philanthropy league
(PL) has been proposed. On every humanitarian deed, citizens will earn
PS and accordingly they will be placed in different PL. People with higher
PL will get priority and extra benefits while availing different government
services and benefits. This will encourage citizens to get involved in more
and more humanitarian acts. Blood donation is merely one of many possible
good deeds. In our future work we plan to explore the generic mathematical
model for the above scores along with different donor grouping using data
mining tools.

Paper Name: DWORLD: Blood Donation App Using Android

Authors: 1 Associate Professor, 2, 3, 4Student, Department of Informa-

tionTechnology, Manakula Vinayagar Institute of Technology, Puducherry,
India

Description: The Main aim of this project DWORLD is to spare existence-

sof individuals by giving blood. A Blood donation seek App utilizing Android
is grown with the goal that clients can see the data of close-by Donors. Our
task is created on two points of view for example patient and benefactor. We

Dept of Computer Engineering, ATCFOE, Pune 2019-20 10

will give validation to the client, for example, enrolment and login for new
client and existing client. An individual is permitted to give just 6 pints of
blood. One 16 ounces of blood can set aside to 33 lives. . The quantity of
blood giver is less when contrasted and differentiations. There are number
of e-blood donation places for compelling correspondence among themselves
and medical offices. None of the eblood donation systemfocuseson ers the
quick contact among recipient and them. This is the genuine drawback of
the present application. Here we propose another and productive approach
to defeat such existing system. Blood donation application supplier records
the giver in the city/territory. When the giver gives the blood it will natu-
rally evacuate the contributor detail for next three months. Our application
searches for the nearest donor accessible, in an ash by following their present
area using GPS by utilizing Haversine Mathematical Algorithm. It addition-
ally confirms with the Department of Health and Welfare to guarantee the
benefactor medical case history. Our application decreases the opportunity
to a more noteworthy degree that is searching for the blood benefactor of
the required blood gather through the specific area. In this way our appli-
cation gives the required data (results) in less time and furthermore helps in
faster basic leadership. The primary reason for our task is to interconnect
all the blood giving benefactors into a solitary system, approving, putting
awaytheir information and data of blood and strength of every person. Con-
clusion: The main purpose of our project to provide the security on data
sets and provide fastest searching process. Defining the user’s personality
can be used to improve numerous products and services. Digital services
could be designed in accordance’s with reviewed personality Hospitals, gov-
ernmental departments on blood donating could use the personality data for
conducting easy surveys, research about the donor detail for their need. Our
application decreases time to a more prominent degree that is looking for the
blood benefactor of the required blood aggregate through the specific area.
The fundamental reason for our undertaking is to interconnect all the blood
giving givers into a solitary In this manner our application gives the required
data (results) in less time and furthermore helps in quick decision making.
The Donor is sorted out with following constrains such as Blood Group, Rh
factor, Last date of Donation and at last based on the Location. System,
approving, putting away their in-formation and data of blood and soundness
of every person.

Paper Name: Forecast and Analysis of Food Donations Using Support

Vector Regression.

Authors: Nigel Pugh Department of Computational Science and Engineer-

Dept of Computer Engineering, ATCFOE, Pune 2019-20 11

ing North Carolina Agricultural Technical State University Greensboro, NC
USA.

Description: Food banks collect and distribute food donations to partner-

ing agencies to help get food insecurity. Donations come from several retail,
manufacturing, and community donors and can vary significantly over time
with respect to frequency, amount, and quality. Support Vector Regression
has shown to have tremendous advantages over other forecasting methods
but has not been previously applied to the food donation supply problem.
Using data obtained from alocalfood bank, this study describes the follow-
ing: (I) the prediction accuracy for food donations when using support vector
regression; and (ii) the relationship between prediction accuracy, historical
data length, and food donation data variability. Results from our study show
that support vector regression has comparable results to other food donation
forecasting techniques previously explored in the literature.

Conclusion: Support Vector Regression has shown to be a powerful super-

vised machine learning technique. SVR has been used previously to predict
future events like customer demand and blood donations and has also pro-
duced respectful results for these problems. Our research applies support
vector regression to the food donation supply uncertainty problem an dour
results illustrate the potential of this technique at producing good estimates
of monthly food donation quantities. Our best model produced a MAPE
of 7.9 for the training set and 11.2 for the validation set. Previous studies
predicting in kind food donations have used machine learning techniques and
statistical fore-casting techniques. Due to the simplicity and traditional high
prediction accuracy of SVM, our study opened the discussion of utilizing
SVR to assist food banks.
 CHAPTER 3
SOFTWARE REQUIREMENT
SPECIFICATION
3.1 Assumptions and Dependencies
• User must require the android .

• User has to install the android studio on his pc.

• User has to login to the system.

3.2 Functional Requirements

3.2.1 System feature
• To have understanding of the problem statement.

• To know what are the hardware and software requirements of proposed

system.

• To have understanding of proposed system.

• To do planning various activates with the help of planner.

• Designing, programming, testing etc.

3.3 External interface requirements

3.3.1 User interfaces
User of the system will be provided with Graphical User Interface, there is
no command line interface for the functions of the product.

3.4 Hardware interfaces

Since the application must run over the Internet, all the hardware shall re-
quire to connect Internet will be hardware interface for the system. As for
e.g. WAN LAN, Ethernet Cross-Cable.

3.5 Software interfaces

Eclipse:

Dept of Computer Engineering, ATCFOE, Pune 2019-20 14

 • Eclipse is an open source community whose projects building tools and
frameworks are used for creating general purpose application. The most
popular usage of Eclipse is as a Java development environment .

• Eclipse is an open source community, whose projects are focused on

building an open development platform comprised of extensible frame-
works, tools and runtimes for building, deploying and managing soft-
ware across the lifecycle. The Eclipse Foundation is a not-for-profit,
member supported corporation that hosts the Eclipse projects and
helps cultivate both an open source community and an ecosystem of
complementary products and services.

• The Eclipse Project was originally created by IBM in November 2001

and supported by a consortium of software vendors. The Eclipse Foun-
dation was created in January 2004 as an independent not-for-profit
corporation to act as the steward of the Eclipse community. The inde-
pendent not-for-profit corporation was created to allow a vendor neu-
tral and open, transparent community to be established around Eclipse.
Today, the Eclipse community consists of individuals and organizations
from a cross section of the software industry.

JDK 7

• Project Coin support

• Editor enhancements: Code completion, hints

Database description

MySQL: MySQL, the most popular Open Source SQL database man-
agement system, is developed, distributed, and supported by Oracle Corpo-
ration. The MySQL Web site
(http://www.mysql.com/) provides the latest information about MySQL soft-
ware.
MySQL is a database management system.
A database is a structured collection of data. It may be anything from a sim-
ple shopping list to a picture gallery or the vast amounts of information in
a corporate network. To add, access, and process data stored in a computer
database, you need a database management system such as MySQL Server.
Since computers are very good at handling large amounts of data, database
management systems play a central role in computing, as standalone utilities,
or as parts of other applications.

Dept of Computer Engineering, ATCFOE, Pune 2019-20 15

3.6 Communication interfaces
The system can use the HTTP protocol for communication over the Internet
and for the intranet communication will be through TCP/IP protocol suite.

3.7 Non Functional Requirements

3.7.1 Performance Requirement
The performance of the functions and every module must be well. The
overall performance of the software will enable the users to work efficiently.
Performance of detect face should be fast. Performance of the providing
virtual environment should be fast.

3.7.2 Safety Requirement

The application is designed in modules where errors can be detected. This
makes it easier to install and update new functionality if required.

3.7.3 Security Requirement

Detect object using camera and perform Algorithms.

3.7.4 Software Quality Attributes

Our software has many quality attribute that are given below:-

Adaptability: This software is adaptable by all users.

Availability: This software is freely available to all users. The availabil-

ity of the software is easy for everyone.

Maintainability: After the deployment of the project if any error occurs

then it can beeasily maintained by the software developer.

Reliability: The performance of the software is better which will increase

the reliability of the Software.

Dept of Computer Engineering, ATCFOE, Pune 2019-20 16

3.8 System Requirements
3.8.1 Database Requirements
• MYSQL

3.9 Software Requirements(Platform Choice)

Platform :

1. Operating System: 32-bit Windows 7 and onword

2. IDE: Eclipse Keplere

3. Programming Language: Android Java J2EE

4. Database : MySQL

3.10 Hardware Requirements

Sr. No. Parameter Minimum Requirement Justification

1 CPU Speed 2 GHz Remark Required
2 RAM 3 GB Remark Required

Table 3.1: Hardware Requirements

 CHAPTER 4
SYSTEM DESIGN
4.1 Architectural Design
We will give a comprehensive overview of the state-of-the-art technologies to
preserve privacy of big data at each stage of big data life cycle. Moreover,
we will discuss privacy issues related to big data when they are stored and
processed on cloud, as cloud computing plays very important role in the ap-
plication of big data. Furthermore, we will discuss about potential research
directions. In this system we are providing attribute Based encryption as
well as third party auditing in which we figure out the collusion attack in
the exiting scheme and provide an efficient public integrity auditing scheme
with secure group user revocation based on vector commitment and verifier-
local revocation group signature. We design a concrete scheme based on the
scheme definition. We are providing concept of deduplication, in simplified
terms, data deduplication compares objects (usually files or blocks) and re-
moves objects (copies) that already exist in the data set. The deduplication
process removes blocks that are not unique.

Dept of Computer Engineering, ATCFOE, Pune 2019-20 19

 Figure 4.1: Architecture diagram

Dept of Computer Engineering, ATCFOE, Pune 2019-20 20

4.2 Data Flow Diagram
4.2.1 Level 0 Data Flow Diagram

Figure 4.2: Level 0 Data flow diagram

4.2.2 Level 1 Data Flow Diagram

Figure 4.3: Level 1 Data flow diagram

4.3 Use Case Diagram

A use case diagram in the Unified Modeling Language (UML) is a type of
behavioral diagram defined by and created from a Use-case analysis. Its
purpose is to present a graphical overview of the functionality provided by
a system in terms of actors, their goals (represented as use cases), and any

Dept of Computer Engineering, ATCFOE, Pune 2019-20 21

dependencies between those use cases. The main purpose of a use case dia-
gram is to show what system functions are performed for which actor. Roles
of the actors in the system can be depicted.

Figure 4.4: Use case diagram

Dept of Computer Engineering, ATCFOE, Pune 2019-20 22

4.4 Activity Diagram:

Figure 4.5: Activity diagram

Dept of Computer Engineering, ATCFOE, Pune 2019-20 23

 Figure 4.6: class diagram

Dept of Computer Engineering, ATCFOE, Pune 2019-20 24

 Figure 4.7: sequence diagram

Dept of Computer Engineering, ATCFOE, Pune 2019-20 25

Figure 4.8: State diagram
 CHAPTER 5
PROJECT PLAN
5.1 Project Estimates
We are using waterfall model for our project estimation.

5.1.1 Reconciled Estimates

5.1.1.1 Cost Estimate
The project cost can be found using any one of the model.
COCOMO-1 Model
COCOMO-2 Model
Model -1: The basic COCOMO model computes software development ef-
forts as a function of program size expressed in estimated lines of code.
Model-2: The intermediate COCOMO model computes software develop-
ment efforts as a function of program size and a set of cost drivers that
include subjective assessment of the product, hardware, personnel, project
attributes
Model-3: The advanced COCOMO model incorporates all characteristics of
the intermediate version with a assessment of the cost drivers impact on each
step of the software engineering process. Following is the basic COCOMO
-2 model.
The basic COCOMO -2 model equations take form:
E=A(b)KLOCB(b)
D=C(b)ED(b)
Where E is the effort applied in person months. D is development time in
chronological month. KLOC is estimated number of delivered lines of code for
the project. This project can be classified as Semidetached software project.
The rough estimate of number of lines of this project is 9.072k.Applying the
above formula
E=3.0*(9.072)1.22
= 44.20 person- months
D=2.5* 44.35
= 9.40 months
Hence according COCOMO -2 model the time required for completion of the
project is 9 ( 9.40) months.

Cost of Project:
Equation for calculation of cost of project using COCOMO - 2 model is:
C = D * Cp
Where,
C = Cost of project

Dept of Computer Engineering, ATCFOE, Pune 2019-20 28

D = Duration in month
Cp= Cost incurred per person-month,
Cp=Rs.1500/- (per person-month) (approx.)
C = 9 * 5000
= 20000/-
Hence according COCOMO - 2 model the cost of project is 20000/-(approx.)

5.1.1.2 Time Estimates

1. Requirement gathering and analysis:
In this step of waterfall we identify what are various requirements are need
for our project such are software and hardware required, database, and in-
terfaces.
2. System Design:
In this system design phase we design the system which is easily understood
for end user i.e. user friendly.
We design some UML diagrams and data flow diagram to understand the
system flow and system module and sequence of execution.
3. Implementation:
In implementation phase of our project we have implemented various mod-
ule required of successfully getting expected outcome at the different module
levels.
With inputs from system design, the system is first developed in small pro-
grams called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality which is referred to as Unit Test-
ing.
4. Testing:
The different test cases are performed to test whether the project module
are giving expected outcome in assumed time. All the units developed in the
implementation phase are integrated into a system after testing of each unit.
Post integration the entire system is tested for any faults and failures.
5. Deployment of System:
Once the functional and non-functional testing is done, the product is de-
ployed in the customer environment or released into the market.
6. Maintenance:
There are some issues which come up in the client environment. To fix those
issues patches are released. Also to enhance the product some better versions
are released. Maintenance is done to deliver these changes in the customer
environment. All these phases are cascaded to each other in which progress
is seen as flowing steadily downwards like a waterfall through the phases.

Dept of Computer Engineering, ATCFOE, Pune 2019-20 29

The next phase is started only after the defined set of goals are achieved for
previous phase and it is signed off, so the name ”Waterfall Model”. In this
model phases do not overlap.

5.1.2 Project Resources

Well configured Laptop, eclipse IDE, 2 GHZ CPU speed, 2 GB RAM, Internet
connection

5.2 Risk Management w.r.t. NP Hard anal-

ysis
1. In appropriate dataset -To overcome this risk we are trying to use well
organized and complete dataset. 2. Security- To overcome and improving
security we use multilevel security like access permissions of user.

5.2.1 Risk Identification

For risks identification, review of scope document, requirements specifications
and schedule is done. Answers to questionnaire revealed some risks. Each
risk is categorized as per the categories mentioned in [?]. Please refer table 5.1
for all the risks. You can refereed following risk identification questionnaire.

1. Have top software and customer managers formally committed to sup-

port the project?
Ans- Not Applicable

2. Are end-users enthusiastically committed to the project and the sys-

tem/product to be built?
Ans- Not known at this time.

3. Are requirements fully understood by the software engineering team

and its customers?
Ans-yes

4. Have customers been involved fully in the definition of requirements?

Ans-Not applicable

Dept of Computer Engineering, ATCFOE, Pune 2019-20 30

 5. Do end-users have realistic expectations?
Ans-Not applicable

6. Does the software engineering team have the right mix of skills? Ans-
yes

7. Are project requirements stable? Ans-Not applicable

8. Is the number of people on the project team adequate to do the job?

Ans-Not applicable

9. Do all customer/user constituencies agree on the importance of the

project and on the requirements for the system/product to be built?
Ans-Not applicable

5.2.2 Risk Analysis

The risks for the Project can be analyzed within the constraints of time and
quality

Impact
ID Risk Description Probability
Schedule Quality Overall
1 Description 1 Low Low High High
2 Description 2 Low Low High High

Table 5.1: Risk Table

Probability Value Description

High Probability of occurrence is > 75%
Medium Probability of occurrence is 26 − 75%
Low Probability of occurrence is < 25%

Table 5.2: Risk Probability definitions [?]

Dept of Computer Engineering, ATCFOE, Pune 2019-20 31

 Impact Value Description
Very high > 10% Schedule impact or Unacceptable quality
High 5 − 10% Schedule impact or Some parts of the project have
low quality
Medium < 5% Schedule impact or Barely noticeable degradation
in quality Low Impact on schedule or Quality can
be incorporated

Table 5.3: Risk Impact definitions [?]

5.2.3 Overview of Risk Mitigation, Monitoring, Man-

agement
Following are the details for each risk.

Risk ID 1
Risk Description Description 1
Category Development Environment.
Source Software requirement Specification document.
Probability Low
Impact High
Response Mitigate
Strategy Strategy
Risk Status Occurred

5.3 Project Schedule

5.3.1 Project task set
Major Tasks in the Project stages are:
• Task 1:Correctness

Dept of Computer Engineering, ATCFOE, Pune 2019-20 32

Risk ID 2
Risk Description Description 2
Category Requirements
Source Software Design Specification documentation review.
Probability Low
Impact High
Response Mitigate
Strategy Better testing will resolve this issue.
Risk Status Identified

Risk ID 3
Risk Description Description 3
Category Technology
Source This was identified during early development and
testing.
Probability Low
Impact Very High
Response Accept
Strategy Example Running Service Registry behind proxy
balancer
Risk Status Identified

Dept of Computer Engineering, ATCFOE, Pune 2019-20 33

 • Task 2: Availability

• Task 3: Integrity

5.3.2 Task network

Project tasks and their dependencies are noted in this diagrammatic form.

5.3.3 Timeline Chart

A project timeline chart is presented. This may include a time line for the
entire project. Above points should be covered in Project Planner as Annex
C and you can mention here Please refer Annex C for the planner

Dept of Computer Engineering, ATCFOE, Pune 2019-20 34

5.4 Team Organization
The manner in which staff is organized and the mechanisms for reporting are
noted.

Dept of Computer Engineering, ATCFOE, Pune 2019-20 35

5.4.1 Team structure
The team structure for the project is identified. Roles are defined. Our team
have three members. We select this topic after discussing with each other.
All the members performing all the task whatever tasks are assign to the
members.

Dept of Computer Engineering, ATCFOE, Pune 2019-20 36

5.4.2 Management reporting and communication
For developing this project, first finalise the project topic after reviewing the
multiple project topics. After that we gather the requirements about this
project. Then we make the synopsis, SRS, PPT and report for sem1. For
all above requirements, our team member and our guide discuss with each
other. Every time we maintain all the details about whatever activities are
performed by us.
 CHAPTER 6
PROJECT IMPLEMENTATION
6.1 Overview
Step 1: Launch the Sun Java wireless toolkit 2.5.2

Step 2: Select the new project option and enter the project name and the
MIDlet name as public class name and select the create project option

Step 3: Write the program in notepad++

Step 4: Save the program in j2mewtk. application src folder with file ex-
tension of .java Step

Step 5:Open the Sun Java Wireless toolkit window Step

Step 6:Select the open project option and choose the project Step

Step 7: Build the project and run the project Step 8: The output is dis-
played.

6.2 Tools and Technologies Used

HARDWARE REQUIREMENTS:

• System Processors : Core2Duo

• Speed : 2.4 GHz

• Hard Disk : 150 GB

SOFTWARE REQUIREMENTS:

• Operating system : 32bit Windows 7 and onword

• Coding Language : Android Java J2EE

• IDE : Eclipse keplere

• Database : MYSQL

JAVA
Java programming language was originally developed by Sun Microsystems
which was initiated by James Gosling and released in 1995 as core component
of Sun Microsystems’ Java platform (Java 1.0 [J2SE]).

Dept of Computer Engineering, ATCFOE, Pune 2019-20 39

The latest release of the Java Standard Edition is Java SE 8. With the
advancement of Java and its widespread popularity, multiple configurations
were built to suit various types of platforms. For example: J2EE for Enter-
prise Applications, J2ME for Mobile Applications.
The new J2 versions were renamed as Java SE, Java EE, and Java ME re-
spectively. Java is guaranteed to be Write Once, Run Anywhere.
Java is
Object Oriented In Java, everything is an Object. Java can be easily ex-
tended since it is based on the Object model.
Platform Independent Unlike many other programming languages including
C and C++, when Java is compiled, it is not compiled into platform spe-
cific machine, rather into platform independent byte code. This byte code is
distributed over the web and interpreted by the Virtual Machine (JVM) on
whichever platform it is being run on.
Simple Java is designed to be easy to learn. If you understand the basic
concept of OOP Java, it would be easy to master.
Secure With Java’s secure feature it enables to develop virus-free, tamper-
free systems. Authentication techniques are based on public-key encryption.
Architecture-neutral Java compiler generates an architecture-neutral object
file format, which makes the compiled code executable on many processors,
with the presence of Java runtime system.
Portable Being architecture-neutral and having no implementation depen-
dent aspects of the specification makes Java portable. Compiler in Java is
written in ANSI C with a clean portability boundary, which is a POSIX sub-
set.
Robust Java makes an effort to eliminate error prone situations by empha-
sizing mainly on compile time error checking and runtime checking.
Multithreaded With Java’s multithreaded feature it is possible to write
programs that can perform many tasks simultaneously. This design fea-
ture allows the developers to construct interactive applications that can run
smoothly.
Interpreted Java byte code is translated on the fly to native machine instruc-
tions and is not stored anywhere. The development process is more rapid
and analytical since the linking is an incremental and light-weight process.
High Performance With the use of Just-In-Time compilers, Java enables
high performance.
Distributed Java is designed for the distributed environment of the internet.
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
extensive amount of run-time information that can be used to verify and
resolve accesses to objects on run-time.

Dept of Computer Engineering, ATCFOE, Pune 2019-20 40

ANDROID
Android is an open source and Linux-based Operating System for mobile
devices such as smartphones and tablet computers. Android was developed
by the Open Handset Alliance, led by Google, and other companies.
Android offers a unified approach to application development for mobile de-
vices which means developers need only develop for Android, and their ap-
plications should be able to run on different devices powered by Android.
The first beta version of the Android Software Development Kit (SDK) was
released by Google in 2007 where as the first commercial version, Android
1.0, was released in September 2008.
On June 27, 2012, at the Google I/O conference, Google announced the next
Android version, 4.1 Jelly Bean. Jelly Bean is an incremental update, with
the primary aim of improving the user interface, both in terms of function-
ality and performance.
The source code for Android is available under free and open source software
licenses. Google publishes most of the code under the Apache License ver-
sion 2.0 and the rest, Linux kernel changes, under the GNU General Public
License version 2.

6.3 Methodologies/Algorithm Details

• The training examples are vectors in a multidimensional feature space,
each with a class label.

• The training phase of the algorithm consists only of storing the feature
vectors and class labels of the training samples.

• In the classification phase, k is a user-defined constant,

• It is an unlabeled vector (a query or test point) is classified by assigning

the label which is most frequent among the k training samples nearest
to that query point.

6.4 Verification and Validation for Acceptance

Verification is done at the starting of the development process. It includes
reviews and meetings, walk-throughs, inspection, etc. to evaluate documents,
plans, code, requirements and specifications. Suppose you are building a
table. Here the verification is about checking all the parts of the table,

Dept of Computer Engineering, ATCFOE, Pune 2019-20 41

whether all the four legs are of correct size or not. If one leg of table is
not of the right size it will imbalance the end product. Similar behavior is
also noticed in case of the software product or application. If any feature of
software product or application is not up to the mark or if any defect is found
then it will result into the failure of the end product. Hence, verification is
very important. It takes place at the starting of the development process.
 CHAPTER 7
SOFTWARE TESTING
7.1 Purpose
Testing is an investigation conducted to provide stakeholders with informa-
tion about the quality of the product or service under test. Software testing
also provides an objective, independent view of the software to allow the
business to appreciate and understand the risks of software implementation.
Test techniques include, but are not limited to, the process of executing a
program or application with the intent of nding software bugs. Software
testing can also be stated as the process of validat- ing and verifying that a
software program or application or product:
1. Meets the business and technical requirements that guided
2. Works as expected;
3. Can be implemented with the same characteristics.

7.2 Scope of Testing

Software testing, depending on the testing method employed, can be imple-
mented at any time in the development process. However, most of the test
eort occurs after the requirements have been defined and the coding process
has been completed. As such, the methodology of the test is governed by
the software development methodology adopted. Dierent software develop-
ment models will focus the test effort at different points in the development
process. Newer development models, such as Agile, often employ test driven
development and place an increased portion of the testing in the hands of the
developer, before it reaches a formal team of testers. In a more traditional
model, most of the test execution occurs after the requirements have been
defined and the coding process has been completed.

7.3 Software to be tested

1. Edraw Max: It enables students, teachers and business professional
store liable create and pub- lish various kinds of diagram store present any
ideas. With this application users can easily create professional- looking
ow charts, organizational charts, network diagrams, business presentations,
building plans, mind maps, science illustration, fashion designs, UML dia-
grams and much more.

2. Star UML: Star UML is a fully edged, open source, UML modeling tool
thats supports the ability to create software designs, from basic concepts,

Dept of Computer Engineering, ATCFOE, Pune 2019-20 44

through to the coded so- lution. The user should be aware that this tool is
more complex than a simple UML diagram editing tool, in that, through the
use of the model Drive Architec- ture (MDA) standard, the tool supports
complex modeling which is realizable in code.

7.4 Test Plan

To test this application we are going with proper sequencing of testing like
unit, integration, validation, GUI, Low level and High level test cases, major
scenarios likewise. We will go with the GUI testing first and then integration
testing. After integration testing performs the high level test cases and major
scenarios which can aect the working on the application. We will perform
the testing on the data transmitted using the various inputs and outputs and
validate the results.

7.5 Type of Testing

Testing is an investigation conducted to provide stakeholders with informa-
tion about the quality of the product or service under test. Software testing
also provides an objective, independent view of the software to allow the
business to appreciate and understand the risks of software implementation.
Test techniques include, but are not limited to, the process of executing a
program or application with the intent of ending software bugs. Software
testing can also be stated as the process of validating and verifying that a
software program or application or product.
Software testing, depending on the testing method employed, can be imple-
mented at any time in the development process. However, most of the test
extort occurs after the requirements have been deaned and the coding pro-
cess has been completed. As such, the methodology of the test is governed by
the software development methodology adopted.In a more traditional model,
most of the test execution occurs after the requirements have been deaned
and the coding process has been completed.

• Unit Testing:
It focuses on smallest unit of software design. In this we test an indi-
vidual unit or group of inter related units.

• Regression Testing:
The objective is to take unit tested components and build a program

Dept of Computer Engineering, ATCFOE, Pune 2019-20 45

 structure that has been dictated by design.Integration testing is testing
in which a group of components are combined to produce output.

• Smoke Testing:
very time new module is added leads to changes in program. This type
of testing make sure that whole component works properly even after
adding components to the complete program.

• System Testing:
In this software is tested such that it works
ne for dierent operating system.It is covered under the black box testing
technique. In this we just focus on required input and output without
focusing on internal working.

7.6 Test Cases and Test Results

Black Box
Testing Black box testing methods focus on the functional requirements in
the software. That is, black box testing enables us to derive sets of input
conditions that will fully exercise. All functional requirements of the program
Black box testing attempts to end errors in the following categories:

• Incorrect or missing function

• Interface errors

• Errors in data structure or

external job access

• Performance errors

• Initialization and termination errors.

In the proposed application with the help of this technique, we do not use
the code to determine a test suite; rather, knowing the problem that we are
trying to solve, we come up with four types of test data:

Dept of Computer Engineering, ATCFOE, Pune 2019-20 46

 • Easy-to-compute data,

• Typical data,

• Boundary
extreme data,

• Bogus data.

But in our application we does not provide any external data, the role of
user is only to give number of nodes for formation of clusters and for the
formation of sink node.
White Box
Testing White box testing is a set case design method that uses the control
structure of the procedural design to derive test cases. Using white box test-
ing methods, we can derive test cases that: Guarantee that all independent
paths within a module have been exercised at least once.
Exercise all logical decisions on their true and false sides.
Execute all loops at their boundaries and within their operational bounds.
Exercise internal data structures to ensure their validity. In the proposed
application the white box testing is done by the us on the implemented code,
we study the code and then determines all legal (valid and invalid) and illegal
inputs and verifies the outputs against the expected outcomes, which is also
determined by studying the implementation code.
Unit Testing
Unit testing enables a programmer to detect error in coding. A unit test
focuses versification of the smallest unit of software design. This testing was
carried out during the coding itself. In this testing step, each module going
to be work satisfactorily as the expected output from the module. The front
end design consists of various forms. They were tested for data acceptance.
Similarly, the back-end also tested for successful acceptance and retrieval of
data. The unit testing is done on the developed code. Mainly the unit testing
is done on modules.
System Testing
After performing the integration testing, the next step is output testing of
the proposed system. No system could be useful if it doest produce the re-
quired output in a specified format. The outputs generated are displayed by
the user. Here the output format is considered in to two ways. One in on
screen and other in printed format.

Dept of Computer Engineering, ATCFOE, Pune 2019-20 47

Integration Testing
Through each program work individually, they should work after linking
together. This is referred to as interfacing. Data may be lost across the
interface; one module can have adverse erect on the other subroutines af-
ter linking may not do the desired function expected by the main routine.
Integration testing is the systematic technique for constructing the program
structure while at the same time conducting test to uncover errors associated
with the interface. Using integrated test plan prepared in the design phase
of the system development as a guide, the integration test was carried out.
All the errors found in the system were corrected for the next testing step.
CHAPTER 8
RESULT
8.1 SCREENSHOT

Figure 8.1: SCREENSHOT 1

Dept of Computer Engineering, ATCFOE, Pune 2019-20 50

 Figure 8.2: SCREENSHOT 2

Dept of Computer Engineering, ATCFOE, Pune 2019-20 51

 Figure 8.3: SCREENSHOT 3

Dept of Computer Engineering, ATCFOE, Pune 2019-20 52

 Figure 8.4: SCREENSHOT 4

Dept of Computer Engineering, ATCFOE, Pune 2019-20 53

 Figure 8.5: SCREENSHOT 6

Dept of Computer Engineering, ATCFOE, Pune 2019-20 54

 Figure 8.6: SCREENSHOT 7

Dept of Computer Engineering, ATCFOE, Pune 2019-20 55

 Figure 8.7: SCREENSHOT 8

Dept of Computer Engineering, ATCFOE, Pune 2019-20 56

Figure 8.8: SCREENSHOT 9
 CHAPTER 9
CONCLUSION AND FUTURE
SCOPE
We conclude that in our system we propose The Donor registers with a
system. When Donor login with the system they donate Blood then system
show blood bank downer want to donate (money,food,clothes)then he show
NGO. Donor track his donation system also detect scrm.
REFERENCES
 1 J. Manyika et al., Big data: The Next Frontier for Innovation, Compe-
tition, and Productivity. Zrich, Switzerland: McKinsey Global Inst.,
Jun. 2011, pp. 1137.

2 J. Gantz and D. Reinsel, “Extracting value from chaos,” in Proc. IDC

IView, Jun. 2011, pp. 112.

3 Z. Xiao and Y. Xiao, “Security and privacy in cloud computing,” IEEE

Commune. Surveys Tuts., vol. 15, no. 2, pp. 843859, May 2013.

4 A. Katal, M. Wazid, and R. H. Goudar, “Big data: Issues, challenges,

tools and good practices,” in Proc. IEEE Int. Conf. Contemp. Com-
pute., Aug. 2013, pp. 404409

5 N. Cao, C. Wang, M. Li, K. Ren, and W. Lou, “Privacy-preserving

multi keyword ranked search over encrypted cloud data,” IEEE Trans.
Parallel Distribute. System.,vol. 25, no. 1, pp. 222233, Jan. 2014.

6 B. Matturdi, X. Zhou, S. Li, and F. Lin, “Big data security and privacy:
A review,” China Commune., vol. 11, no. 14, pp. 135145, Apr. 2014.

7 O. M. Soundararajan, Y. Jenifer, S. Dhivya, and T. K. P. Rajagopal,

“Data security and privacy in cloud using RC6 and SHA algorithms,”.
Commune. Eng., vol. 6, no. 5, pp. 202205, Jun. 2014.

8 H. Hu, Y. Wen, T.-S. Chua, and X. Li, “toward scalable systems for
big data analytics: A technology tutorial,” IEEE Access, vol. 2, pp.
652687, Jul. 2014

9 L. Xu, C. Jiang, J.Wang, J. Yuan, and Y. Ren, “Information security

in big data: Privacy and data mining,” in IEEE Access, vol. 2, pp.
11491176, Oct. 2014. 31

10 C. Hongbing, R. Chunming, H. Kai,W.Weihong, and L. Yanyan, “Se-

cure big data storage and sharing scheme for cloud tenants,” China
Commune., vol. 12, no. 6, pp. 106115, Jun. 2015.
ANNEXURE A
NP-Hard NP-Complete:

What is P?

• P is set of all decision problems which can be solved in polynomial time

by a deterministic.

• Since it can be solved in polynomial time, it can be verified in polyno-

mial time.

• Therefore P is a subset of NP.

P : This results in the development of various prediction algorithms

under the domain of machine learning, data mining, and forecasting. This
project focuses on analysis of theweather data pattern and its behavior us-
ing univariate forecasting model. Temperature is taken as the univariate
observation from weather dataset, and the forecast value is predicted us-
ing forecasting algorithms. The predicted forecast value is compared with
real-time data from which it is observed that level component plays a major
role than trend and seasonal component in real-time data, and the predicted
forecast value does not depend on size of the dataset.

Figure A.1: P Problem

Dept of Computer Engineering, ATCFOE, Pune 2019-20 63

 What is NP?

NP means we can solve it in polynomial time if we can break the normal

rules of step-by-step computing.

What is NP Hard?
A problem is NP-hard if an algorithm for solving it can be translated into
one for solving any NP-problem (nondeterministic polynomial time) problem.
NP-hard therefore means ”at least as hard as any NP-problem,” although it
might, in fact, be harder.

NP-Hard:
In server less it is mostly the function that gets triggered whenever the event
occurs. A function usually executes in a dedicated function instance (a con-
tainer or other kindof sandbox) with restricted resources such as CPU time
and memory i.e. P=NP-Hard

Figure A.2: NP Problem

What is NP-Complete?

• Since this amazing ”N” computer can also do anything a normal com-
puter can, we know that ”P” problems are also in ”NP”.
• So, the easy problems are in ”P” (and ”NP”), but the really hard ones
are *only* in ”NP”, and they are called ”NP-complete”.

Dept of Computer Engineering, ATCFOE, Pune 2019-20 64

• It is like saying there are things that People can do (”P”), there are
things that Super People can do (”SP”), and there are things *only*
Super People can do (”SP-complete”).

Figure A.3: NP Complete Problem

NP-Complete:

We have used inbuilt mobile sensor to identify road conditions.

Hence the P is NP-Complete in this case.

Dept of Computer Engineering, ATCFOE, Pune 2019-20 65