A MINI PROJECT REPORT

ON

ONLINE BLOOD DONATION MANAGEMENT SYSTEM

Submitted in partial fulfilment of the requirement for the award of the

degree

Of

BACHELOR OF TECHNOLOGY

In

COMPUTER SCIENCE AND ENGINEERING

By

K.RAMAKRISHNA (13K91A0597)

Under the Guidance

Of
Mr. T.MADHU Sir
Assistant Professor

Department of Computer Science and Engineering

TKR COLLEGE OF ENGINEERING &TECHNOLOGY
(Affiliated to JNTUH, Hyderabad, Approved by AICTE, Accredited by NBA)
Medbowli, Meerpet, Saroornagar, Hyderabad-500097.
August, 2016
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

CERTIFICATE

This is to certify that the project work entitled ONLINE BLOOD

DONATION MANAGEMENT SYSTEM carried out by

K.RAMAKRISHNA bearing Roll No.13K91A0597 partial fulfilment of

the requirements for the award of the degree of Bachelor of Technology

in Computer Science and Engineering is a record of bonafide work

carried out by them under my guidance.

The results of investigations enclosed in this report have been

verified and found satisfactory. The results embodied in this thesis have

not been submitted to any other University or Institution for the award of

any Degree or Diploma

INTERNAL GUIDE HOD

Mr. T.MADHU Dr. A. SURESH RAO
Asst.Professor
 EXTERNAL EXAMINER

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

DECLARATION BY THE CANDIDATE

I K.RAMAKRISHNA bearing Roll No.13K91A0597. I hereby declare that

the project report entitled ONLINE BLOOD DONATION MANAGEMENT

SYSTEM is done under the guidance of MR. T MADHU, Dept. of CSE, TKR

College of Engineering and Technology, is submitted in partial fulfilment of the

requirements for the award of the Degree of Bachelor of Technology in Computer

Science and Engineering.

This is a record of Bonafide work carried out by me in TKR College of Engineering

and Technology.

K.RAMAKRISHNA (13K91A0597)
Department of CSE,
TKR College of Engineering and Technology,
 Hyderabad.

ACKNOWLEDGEMENT

The satisfaction and euphoria that accompanies the successful

completion of any task would be incomplete without the
mention of the people who made it possible and whose
encouragement and guidance have crowned our efforts with
success.
I extend my deep sense of gratitude to
Principal, Dr. D.V. RAVISHANKAR, TKR College of
Engineering & Technology, for consistent motivation and
without whom this could not have been possible.
I am also indebted to the Head of the Department of CSE, Dr.
A. SURESH RAO, for his constant encourage and support.
I am indebted to the Internal Guide, MR. T.MADHU,
Asst..Professor, Computer Science Engineering, TKR College of
Engineering & Technology, Meerpet, for his guidance and
support.
Finally, I express thanks to one and all that have helped me in
successfully completing this project. Furthermore I would like
to thank my family and friends for their moral support and
encouragement.
 K.RAMAKRISHNA (13K91A0597)

CONTENTS
S.NO Page.No

1. INTRODUCTION 1
1.1 INTRODUCTION TO PROJECT
1.2 PURPOSE OF THE PROJECT 2
1.3 EXISTING SYSTEM & ITS DISADVANTAGES
1.4 PROPOSED SYSTEM & ITS ADVANTAGES

2. SYSTEM ANALYSIS 3
2.1 PROCESS MODELS USED WITH JUSTIFICATION 4
2.2 SYSTEM ARCHITECTURE 8

3. FEASIBILITY STUDY 10
3.1 OPERATIONAL FEASIBILITY
3.2 TECHNICAL FEASIBILITY
3.3 ECONOMIC FEASIBILITY

4. REQUIREMENT SPECIFICATIONS 11
4.1 FUNCIONAL REQUIREMENTS 12
4.2 PERFORMANCE REQUIREMENTS
4.3 SOFTWARE &HARDWARE REQUIREMENTS
4.3.1 html
 4.3.2 php
4.3.3 ionic frameworks
4.3.4 android sdk 13

.
28

5. SYSTEM DESIGN 29
5.1 INTRODUCTION
5.2 UML DIAGRAMS

6. IMPLEMENTATION 39
6.1 SAMPLE CODE
6.2 SCREEN SHOTS 52

7. SYSTEM TESTING 55
7.1 INTRODUCTION TO TESTING
7.2 TESTING STRATEGIES

8. SYSTEM SECURITY 58
8.1 INTRODUCTION
8.2 SECURITY IN SOFTWARE

9. BIBLIOGRAPHY 60
 1. INTRODUCTION

1.1 ABSTRACT
This project is aimed to develop an online Blood Donation
Information. The entire project has been developed keeping in
view of the distributed client server computing technology, in
mind. The Blood Donation Agent is to create an e-Information
about the donor that are related to donate the blood. Through
this application any person who is interested in donating the
blood can register himself by entering required details.
Moreover if any general consumer wants to make request blood
online , he can also take the help of this application. Admin is
the main authority who can do addition, deletion, and
modification if required.
The project has been planned to be having
the view of distributed architecture, with centralized storage of
the database. The application for the storage of the data has been
planned. Using the constructs of MS-SQL Server and all the
user interfaces have been designed using the ASP.Net
technologies. The database connectivity is planned using the
SQL Connection methodology. The standards of security and
mechanism have been given a big choice for proper usage. The
application takes care of different modules and their associated
reports, which are produced as per the applicable strategies and
standards that are put forwarded by the administrative staff.
1.2 PURPOSE
The purpose of this project to eradicate the unavailability of
blood during emergency situations with the provision of e-blood
application. Minimization of deaths due to lack of blood during
operations and also to provide awareness among people about
blood donation. This application also creates an online platform
for blood exchange among donors and acceptors.

1.3 Existing system:

Consumes lot of manpower
Lack of donor information
Uncertainty of Donor availability
Retrieval of data takes lot of time
Percentage of accuracy is less
Some data may be lost due to mismanagement.
Time consuming

1.4 Proposed system:

To overcome the above problems we came up with an idea to implement
a system called Suburb Possessor ship.
Ease of communication between Donor and Acceptor.
Access from any where of world
Access at any time
Quick Search
Time Optimize
Cost Optimize

Advantages:
User friendly atmosphere is provided in the application with
various controls.
This system makes the overall project management much
easier and flexible.
 Readily upload the latest updates ,allows user to download
the alerts by clicking the url.
It provides a decent level of security with different level of
authentication

2. SYSTEM ANALYSIS
Software Requirement Specification (SRS)
SOFTWARE REQUIREMENT SPECIFICATION

What is SRS?

Software Requirement Specification (SRS) is the starting point

of the software developing activity. As system grew more complex it
became evident that the goal of the entire system cannot be easily
comprehended. Hence the need for the requirement phase arose.
The software project is initiated by the client needs. The SRS is the
means of translating the ideas of the minds of clients (the input) into
a formal document (the output of the requirement phase.)

The SRS phase consists of two basic activities:

1) Problem/Requirement Analysis:

The process is order and more nebulous of the two, deals with
understand the problem, the goal and constraints.

2) Requirement Specification:

Here, the focus is on specifying what has been found giving

analysis such as representation, specification languages and tools,
and checking the specifications are addressed during this activity.

The Requirement phase terminates with the production of the

validate SRS document.
Producing the SRS document is the basic goal of this phase.
 2.1 PROCESS MODEL USED WITH JUSTIFICATION
There are various software development approaches defined and
designed which are used/employed during development process of
software, these approaches are also referred as "Software Development
Process Models". Each process model follows a particular life cycle in
order to ensure success in process of software development.

Waterfall Model:

Waterfall approach was first Process Model to be introduced

and followed widely in Software Engineering to ensure success of the
project. In "The Waterfall" approach, the whole process of software
development is divided into separate process phases.

The phases in Waterfall model are: Requirement

Specifications phase, Software Design, Implementation, Testing,
Deployment phase and Maintenance. All these phases are cascaded
to each other so that second phase is started as and when defined
set of goals are achieved for first phase and it is signed off, so the
name "Waterfall Model". All the methods and processes undertaken
in Waterfall Model are more visible.
The stages of "The Waterfall Model" are:

Requirement Analysis & Definition:

All possible requirements of the system to be developed are

captured in this phase. Requirements are set of functionalities and
constraints that the end-user (who will be using the system) expects
from the system. The requirements are gathered from the end-user
by consultation, these requirements are analyzed for their validity
and the possibility of incorporating the requirements in the system
to be development is also studied. Finally, a Requirement
Specification document is created which serves the purpose of
guideline for the next phase of the model.

System & Software Design:

Before a starting for actual coding, it is highly important to

understand what we are going to create and what it should look like?
The requirement specifications from first phase are studied in this
phase and system design is prepared. System Design helps in
specifying hardware and system requirements and also helps in
defining overall system architecture. The system design
specifications serve as input for the next phase of the model.

Implementation & Unit Testing:

On receiving system design documents, the works divided in

modules/units and actual coding is started. 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; this is referred to as Unit Testing. Unit testing mainly
verifies if the modules/units meet their specifications.
Integration & System Testing:

As specified above, the system is first divided in units which

are developed and tested for their functionalities. These units are
integrated into a complete system during Integration phase and
tested to check if all modules/units coordinate between each other
and the system as a whole behaves as per the specifications. After
successfully testing the software, it is delivered to the customer.

Operations & Maintenance:

This phase of "The Waterfall Model" is virtually never ending

phase (Very long). Generally, problems with the system developed
(which are not found during the development life cycle) come up
after its practical use starts, so the issues related to the system are
solved after deployment of the system. Not all the problems come in
picture directly but they arise time to time and needs to be solved;
hence this process is referred as Maintenance.

Advantages of Waterfall Model:

Advantages:

The advantage of waterfall development is that it allows for

departmentalization and managerial control. A schedule can be set
with deadlines for each stage of development and a product can
proceed through the development process like a car in a carwash,
and theoretically, be delivered on time. Development moves from
concept, through design, implementation, testing, installation,
troubleshooting, and ends up at operation and maintenance. Each
phase of development proceeds in strict order, without any
overlapping or iterative steps.
2.2 SYSTEM ARCHITECTURE

Architecture Flow:

Below architecture diagram represents mainly the flow of requests

from users to database through server. In this scenario overall system is
designed in three tires separately using three layers called presentation
layer, business logic layer and data link layer. This project was developed
using 3-tire architecture.

URL Pattern:

User

SERVER

Data
Base

Request Response
URL pattern represents how the requests are flowing through one layer
to another layer and how the responses are getting by other layers to
presentation layer through server in architecture diagram.

3. Feasibility Study
The main objective of the feasibility study is to test the Technical,
Operational and Economical feasibility for adding new modules and
debugging old running system. All system is feasible if they are unlimited
resources and infinite time. There are aspects in the feasibility study
portion of the preliminary investigation:
 Technical Feasibility
Operation Feasibility
Economical Feasibility

3.1 Technical Feasibility

The technical issue usually raised during the feasibility stage of the
investigation includes the following:

Does the necessary technology exist to do what is suggested?

Do the proposed equipments have the technical capacity to hold the
data required to use the new system?
Will the proposed system provide adequate response to inquiries,
regardless of the number or location of users?
Can the system be upgraded if developed?
Are there technical guarantees of accuracy, reliability, ease of access
and data security?

The databases purpose is to create, establish and maintain a

workflow among various entities in order to facilitate all concerned users
in their various capacities or roles. Permission to the users would be
granted based on the roles specified. Therefore, it provides the technical
guarantee of accuracy, reliability and security.

The software and hard requirements for the development of this

project are not many are available as free as open source. The work for
the project is done with the current equipment and existing software
technology. Necessary bandwidth exists for providing a fast feedback to
the users irrespective of the number of users using the system.
3.2. Operational Feasibility
Proposed projects are beneficial only if they can be turned out into
information system. That will meet the organizations operating
requirements. Operational feasibility aspects of the project are to be taken
as an important part of the project implementation. Some of the important
issues raised are to test the operational feasibility of a project includes the
following: -

Is there sufficient support for the management from the users?

Will the system be used and work properly if it is being developed and
implemented?
Will there be any resistance from the user that will undermine the
possible application benefits?

This system is targeted to be in accordance with the above-

mentioned issues. Beforehand, the management issues and user
requirements have been taken into consideration. So there is no question
of resistance from the users that can undermine the possible application
benefits.

The well-planned design would ensure the optimal utilization of the

computer resources and would help in the improvement of performance
status.

3.3. Economic Feasibility

The system is economically feasible. It does not require any
addition hardware or software. Since the interface for this system is
developed using the existing resources. There is nominal expenditure and
economical feasibility for certain.
A system can be developed technically and that will be used if installed
must still be a good investment for the organization. In the economical
feasibility, the development cost in creating the system is evaluated
against the ultimate benefit derived from the new systems. Financial
benefits must equal or exceed the costs.

4. REQUIREMENTS SPECIFICATION
4.1 functional requirements
The system is proposed to have the following modules:

1. Administration

2. Donor

3.acceptor
Administrator:-
In this module the Administrator has the privileges to add all the Blood
Groups, Blood Type, City, and Location. He can search all the info about the
Donor.

Donor:-
Donor is that person who is interested in donating his blood, so they can
register themselves through this application. If any requirement comes then
they will be contacted and they can donate their blood. Along with it they can
also make request for blood if needed.

ACCEPTOR:-
acceptor is that person who is in need of a particular blood.In this module any
general user who is not registered can also make request for blood if needed.
He can visit all the static pages and can get information about the various
issues related with blood donation.
 4.2 PERFORMANCE REQUIREMENTS

Performance is measured in terms of the output provided by

the application. Requirement specification plays an important part in
the analysis of a system. Only when the requirement specifications
are properly given, it is possible to design a system, which will fit
into required environment. It rests largely with the users of the
existing system to give the requirement specifications because they
are the people who finally use the system. This is because the
requirements have to be known during the initial stages so that the
system can be designed according to those requirements. It is very
difficult to change the system once it has been designed and on the
other hand designing a system, which does not cater to the
requirements of the user, is of no use.

The requirement specification for any system can be broadly stated as

given below:

The system should be able to interface with the existing

system

The system should be accurate

The system should be better than the existing system

The existing system is completely dependent on the user to perform all

the duties.

4.3 HARDWARE REQUIREMENTS:

Intel Virtualization Enabled Processor

 RAM 2GB
HDD 20 GB Hard Disk Space and Above

SOFTWARE REQUIREMENTS:

Windows OS

Ionic framework

Cordova Platform

Jdk

Android SDK

Node.js

Apache ANT

SQL server

4.3.5 HTML
Webpages are written in HTML - a simple scripting language.

HTML is short for HyperText Markup Language.

Hypertext is simply a piece of text that works as a link.

Markup Language is a way of writing layout information within documents.

Basically an HTML document is a plain text file that contains text

and nothing else. When a browser opens an HTML file, the browser will
look for HTML codes in the text and use them to change the layout,
insert images, or create links to other pages.

Since HTML documents are just text files they can be written in
even the simplest text editorA more popular choice is to use a
special HTML editor - maybe even one that puts focus on the visual
result rather than the codes - a so-called WYSIWYG editor ("What
You See Is What You Get").
 Some of the most popular HTML editors, such as FrontPage or
Dreamweaver will let you create pages more or less as you write
documents in Word or whatever text editor you're using.

However, there are some very good reasons to create your own pages - or
parts of them - by hand...

It is possible to create webpages without knowing anything about

the HTML source behind the page.

There are excellent editors on the market that will take care of the HTML
parts. All you need to do is layout the page.

HTML Tags

What are HTML tags?

HTML tags are used to mark-up HTML elements

HTML tags are surrounded by the two characters < and >

The surrounding characters are called angle brackets

HTML tags normally come in pairs like <b> and </b>

The first tag in a pair is the start tag, the second tag is the end tag

The text between the start and end tags is the element content

HTML tags are not case sensitive, <b> means the same as <B>

4.3.3 ionic framworks

The Ionic Platform offers a range of powerful, hybrid-focused mobile backend

services and tools to make it easy to scale beautiful, performant hybrid apps, at a
rapid pace.

Ionic is a bunch of UI elements made in HTML5 & CSS3 that covers a

lot of the mobile interactions The big advantage of Ionic is all the UI
components are AngularJS Directives

Ionic is a complete open-source SDK for hybrid mobile app development.[4] Built
on top of AngularJS and Apache Cordova, Ionic provides tools and services for
developing hybrid mobile apps using Web technologies like CSS, HTML5,
and Sass. Apps can be built with these Web technologies and then distributed
 through native app stores to be installed on devices by leveraging Cordova. Ionic
was created by Max Lynch, Ben Sperry, and Adam Bradley of Drifty Co. in 2013.

Services & features[edit]

Ionic provides all the functionality that can be found in native mobile development SDKs.
Users can build their apps, customize them for Android or iOS, and deploy
through Cordova. Ionic includes mobile components, typography, interactive paradigms,
and an extensible base theme.

Using Angular, Ionic provides custom components and methods for interacting with them.
One such component, collection repeat, allows users to scroll through a list of thousands
of items without any performance hits. Another component, scroll-view, creates a
scrollable container with which users can interact using a native-influenced delegate
system.

<ion-content>
</ion-content>

Developers can programmatically control the scroll-view to get the scroll position, scroll to
bottom/top, zoom, or get information about the current scroll-view instances.

$ionicScrollDelegate.scrollTop();
$ionicScrollDelegate.scrollBottom();
$ionicScrollDelegate.zoomTo(1.5);
$ionicScrollDelegate.getScrollView();

Besides the SDK, Ionic also provides services that developers can use to enable
features, such as push notifications, A/B testing, analytics, code deploys, and automated
builds.

Ionic also provides a powerful command-line interface (CLI), so developers can get
started and create a project with a simple command. The CLI also allows developers to
add Cordova plugins and additional front-end packages, enable push notifications,
generate app Icons and Splash screens, and build native binaries.

Supported platforms[edit]
Ionic is focused on building for modern Web standards and for modern mobile devices.
For Android, Ionic supports Android 4.1 and up. For iOS, Ionic supports iOS 7 and up.
[6]
Ionic 2 supports the Universal Windows Platform for building Windows 10 apps.[7] Ionic
Framework, powered by Angular.js, supports BlackBerry 10 apps.[8]

Performance[edit]
Compared to hybrid apps, mixing Ionic code with native mobile app code
in PhoneGap allows for higher performance of the resulting product:
utilizing AngularJS (rather than jQuery) allows Ionic to rely on native hardware
acceleration (rather than extensive DOM manipulation). Ionic leverages CSS transitions
and transforms for animation as a way to leverage the GPU and maximize available
processor time.

Installation[edit]
Ionic is an npm module and requires Node.js.

4.3.4 android sdk

Android software development is the process by which new applications are created
for the Android operating system. Applications are usually developed
inJava programming language using the Android software development kit (SDK), but
other development environments are also available.

Android SDK[edit]
Android SDK

Developer(s) Google

Initial release October 2009; 6 years ago

Stable release 24.4.1 / October 2015; 9 months ago[2]

Written in Java

Operating Cross-platform

system

Available in English

Type IDE, SDK

Website developer.android.com/tools/sdk/eclipse-

adt.html, developer.android.com/sdk/index.ht

ml

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

development tools.[3] These include a debugger, libraries, a handset emulatorbased
on QEMU, documentation, sample code, and tutorials. Currently supported development
platforms include computers running Linux (any modern desktop Linux distribution), Mac
OS X 10.5.8 or later, and Windows XP or later. As of March 2015, the SDK is not
available on Android itself, but the software development is possible by using specialized
Android applications.[4][5][6]

Until around the end of 2014, the officially supported integrated development
environment (IDE) was Eclipse using the Android Development Tools (ADT) Plugin,
though IntelliJ IDEA IDE (all editions) fully supports Android development out of the box,
[7]
and NetBeans IDE also supports Android development via a plugin. [8] As of
2015, Android Studio,[9] made by Google and powered by IntelliJ, is the official IDE;
however, developers are free to use others. Additionally, developers may use any text
editor to edit Java and XML files, then use command line tools (Java Development
Kit and Apache Ant are required) to create, build and debug Android applications as well
as control attached Android devices (e.g., triggering a reboot, installing software
package(s) remotely).[10]

Enhancements to Android's SDK go hand in hand with the overall Android platform
development. The SDK also supports older versions of the Android platform in case
developers wish to target their applications at older devices. Development tools are
downloadable components, so after one has downloaded the latest version and platform,
older platforms and tools can also be downloaded for compatibility testing. [11]

Android applications are packaged in .apk format and stored under /data/app folder on
the Android OS (the folder is accessible only to the root user for security reasons). APK
package contains .dex files[12] (compiled byte code files called Dalvik executables),
resource files, etc.

4.3.4 php
PHP is a server-side scripting language designed for web development but also used as
a general-purpose programming language. Originally created byRasmus Lerdorf in 1994,
[4]
the PHP reference implementation is now produced by The PHP Group.[5] PHP
originally stood for Personal Home Page,[4] but it now stands for
the recursive backronym PHP: Hypertext Preprocessor.[6]

PHP code may be embedded into HTML code, or it can be used in combination with
various web template systems, web content management systems andweb frameworks.
PHP code is usually processed by a PHP interpreter implemented as a module in the
web server or as a Common Gateway Interface (CGI) executable. The web server
combines the results of the interpreted and executed PHP code, which may be any type
of data, including images, with the generated web page. PHP code may also be executed
with a command-line interface (CLI) and can be used to implement standalone graphical
applications.[7]

The standard PHP interpreter, powered by the Zend Engine, is free software released
under the PHP License. PHP has been widely ported and can be deployed on most web
servers on almost every operating system and platform, free of charge.[8]

The PHP language evolved without a written formal specification or standard until 2014,
leaving the canonical PHP interpreter as a de facto standard. Since 2014 work has gone
on to create a formal PHP specification.[9]

During the 2010s there have been increased efforts towards standardisation and code
sharing in PHP applications by projects such as PHP-FIG in the form of PSR-
initiatives as well as Composer dependency manager and the Packagist repository.

5. SYSTEM DESIGN

Introduction: Systems Design is the process or art of defining the architecture, components, modules,
interfaces, and data for a system to satisfy specified requirements. One could see it as the application of
systems theory to product development. There is some overlap and synergy with the disciplines of
systems analysis, systems architecture and systems engineering.

5.2 UML DIAGRAMS

Unified Modeling Language: The Unified Modeling Language allows the software engineer to express
an analysis model using the modeling notation that is governed by a set of syntactic semantic and
pragmatic rules.

A UML system is represented using five different views that describe the system from distinctly different
perspective. Each view is defined by a set of diagram, which is as follows.

User Model View i. This view represents the system from the users perspective. ii. The analysis
representation describes a usage scenario from the end-users perspective.

Structural model view i. In this model the data and functionality are arrived from inside the system. ii.
This model view models the static structures.
 Behavioral Model View It represents the dynamic of behavioral as parts of the system, depicting the
interactions of collection between various structural elements described in the user model and structural
model view.

Implementation Model View In this the structural and behavioral as parts of the
system are represented as they are to be built.
Environmental Model View In this the structural and behavioral aspects
of the environment in which the system is to be implemented are represented.
UML is specifically constructed through two different domains they are:
UML Analysis modeling, this focuses on the user model and structural model
views of the system. UML design modeling, which focuses on the behavioral
modeling, implementation modeling and environmental model views.
Use case Diagrams represent the functionality of the system from a users point
of view. Use cases are used during requirements elicitation and analysis to
represent the functionality of the system. Use cases focus on the behavior of the
system from external point of view.
Actors are external entities that interact with the system. Examples of actors
include users like administrator, bank customer etc., or another system like
6. IMPLEMENTATION

6.1 SAMPLE CODE:

Home page
<ion-view class=" " style="background-color: rgb(96, 125, 139);" id="page1"
title="e-Blood" hide-back-button="true">
<ion-content class="has-header" padding="true">
<div style="" class="">
<img style="display: block; margin-left: auto; margin-right: auto;"
src="img/firstimage.png" height="auto" width="100%">
</div>
<div style="width: 278.75px; height: 6px;" class="spacer"></div>
<ion-list style="" class=" " id="eBlood-list2"></ion-list>
<a style="" class=" button button-balanced button-block icon-left ion-ios-
search" href="#"
onclick="window.open('http://www.atozdownload.in/eblood/search.php',
'_blank', 'location=no' )">Search Donors</a>
 <a style="" class=" button button-royal button-block icon-left ion-android-
create " href="#"
onclick="window.open('http://www.atozdownload.in/eblood/index.php',
'_blank', 'location=no' )">Donor Registration</a>
<a style="" class=" button button-calm button-block icon-left ion-
information-circled " id="eBlood-button3" ui-sref="tipsfordonors">Tips For
Donors</a>
<a style="" class=" button button-dark button-block icon-left ion-android-
people " id="eBlood-button12" ui-sref="aboutus">About Us</a>
</ion-view>
Donor registration
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<title>Donor Registration</title>
<meta name="viewport" content="width=device-width; height=device-
height; user-scalable=yes; initial-scale=1.0" >
</head>
<body style="background-color:#192122">
<link rel="stylesheet" href="formoid_files/formoid1/formoid-biz-green.css"
type="text/css" />
<form class="formoid-biz-green" style="background-color:#1A2223;font-
size:15px;font-family:'Open Sans','Helvetica Neue', 'Helvetica', Arial, Verdana,
sans-serif;color:#ECECEC;max-device-width;min-device-width"
method="post" action="submit.php"><div class="title"><h2>Donor
Registration</h2></div>
<div class="element-input" title="Type Your Username"><label
class="title"></label><input class="large" type="text" name="name"
placeholder="Username" required/></div>
<div class="element-input"><label class="title"></label><input
class="large" type="email" name="email" placeholder="Email"
required/></div>
<div class="element-select" title="Choose Your Gender"><label
class="title"></label><div class="large"><span><select name="gender"
required>
<option value="">Gender</option>
 <option value="Male">Male</option>
<option
value="Female">Female</option></select><i></i></span></div></div>
<div class="element-select" title="Blood Group"><label
class="title"></label><div class="large"><span><select name="bloodgroup"
required>
<option value="">Blood Group</option>
<option value="A+">A+</option>
<option value="A-">A-</option>
<option value="B+">B+</option>
<option value="B-">B-</option>
<option value="AB+">AB+</option>
<option value="AB-">AB-</option>
<option value="O+">O+</option>
<option value="O-">O-</option>
</select><i></i></span></div></div>
<div class="element-input"><label class="title"></label><input
class="large" type="text" name="phoneno" placeholder="Phone Number"
required/></div>
<div class="element-select" title="Choose Your City"><label
class="title"></label><div class="large"><span><select name="city" required>
<option value="">City</option>
<option value="Adilabad">Adilabad</option>
<option value="Hyderabad">Hyderabad</option>
<option value="Karimnagar">Karimnagar</option>
<option value="Khammam">Khammam</option>
<option value="Mahbubnagar">Mahbubnagar</option>
<option value="Medak">Medak</option>
<option value="Nalgonda">Nalgonda</option>
<option value="Nizamabad">Nizamabad</option>
<option value="RangaReddy">RangaReddy</option>
<option value="Warangal">Warangal</option>
</select><i></i></span></div></div>
<div class="submit"><center><input type="submit"
value="Submit"/></center></div></form>
</body>
</html>
database storage
<?php
// Only process the form if $_POST isn't empty
if ( ! empty( $_POST ) ) {

// Connect to MySQL
$mysqli = new mysqli( 'localhost', 'eblood', '8099322060', 'eblood' );

// Checking connection
if ( $mysqli->connect_error ) {
die( 'Connect Error: ' . $mysqli->connect_errno . ': ' . $mysqli-
>connect_error );
}

$sql = "INSERT INTO user ( name, email, gender, bloodgroup, phoneno, city)
VALUES ( '{$mysqli->real_escape_string($_POST['name'])}', '{$mysqli-
>real_escape_string($_POST['email'])}', '{$mysqli-
>real_escape_string($_POST['gender'])}','{$mysqli-
>real_escape_string($_POST['bloodgroup'])}','{$mysqli-
>real_escape_string($_POST['phoneno'])}', '{$mysqli-
>real_escape_string($_POST['city'])}')";
$insert = $mysqli->query($sql);

if ( $insert ) {
echo "Registration Successful";
header("Location:http://www.atozdownload.in/eblood/search/");

} else {
die("Error: {$mysqli->errno} : {$mysqli->error}");
}
 // Close our connection
$mysqli->close();
}
?>
<html>
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width; height=device-
height; user-scalable=yes; initial-scale=1.0" >
</head>
</html>

search
<html>
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width; user-scalable=yes;
initial-scale=1.0">
</head>
<link rel = "stylesheet" type = "text/css" href = "style.css">
<link rel = "stylesheet" type = "text/css" href = "bootstrap.css">
<body>
<center><form id="search" action="searchfunction.php" method="post" >
<label>Blood Group</label>
<div class="element-select" title="Blood Group"><label
class="title"></label><div class="large"><span><select name="bloodgroup"
required>
<option value="select">select</option>
<option value="A+">A+</option>
<option value="A-">A-</option>
<option value="B+">B+</option>
<option value="B-">B-</option>
 <option value="AB+">AB+</option>
<option value="AB-">AB-</option>
<option value="O+">O+</option>
<option value="O-">O-</option>
</select><i></i></span></div></div>
<label>City</label>
<div class="element-select" title="Choose Your City"><label
class="title"></label><div class="large"><span><select name="city" required>
<option value="select">select</option>
<option value="Adilabad">Adilabad</option>
<option value="Hyderabad">Hyderabad</option>
<option value="Karimnagar">Karimnagar</option>
<option value="Khammam">Khammam</option>
<option value="Mahbubnagar">Mahbubnagar</option>
<option value="Medak">Medak</option>
<option value="Nalgonda">Nalgonda</option>
<option value="Nizamabad">Nizamabad</option>
<option value="RangaReddy">RangaReddy</option>
<option value="Warangal">Warangal</option>
</select><i></i></span></div></div>
<button type="submit" class="btn">Search</button>
</form></center>
</body>
</html>
Search function
<html>
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width; user-scalable=yes;
initial-scale=1.0">
</head>
<body>
<?php
$bloodgroup = $_POST['bloodgroup'];
$city = $_POST['city'];
$mysql_host='localhost';
$mysql_user='eblood';
$mysql_pass='8099322060';
$mysql_database='eblood';
$connect=mysql_connect($mysql_host,$mysql_user, $mysql_pass);
mysql_select_db("eblood") or die("no db :'(");
$query="SELECT name,email,gender,bloodgroup,phoneno,city FROM user
WHERE bloodgroup='$bloodgroup' AND city='$city' ";
$result=mysql_query($query);
$numrows=mysql_num_rows($result);
?>
<table class="table table-hover table-striped">
<thead>
<tr>
<th><font face="Arial, Helvetica, sans-serif">Name</font></th>

<th><font face="Arial, Helvetica, sans-serif">Phoneno.</font></th>

<th><font face="Arial, Helvetica, sans-serif">Email</font></th>

</tr>
</thead>
<tbody>
<?php
$i=0;
while ($i < $numrows) {
$r2=mysql_fetch_array($result);
 $f1=$r2['name'];
$f3=$r2['gender'];
$f4=$r2['bloodgroup'];
$f5=$r2['phoneno'];
$f6=$r2['email'];
$f7=$r2['city'];
$i++;
?>

<tr>
<td><font face="Arial, Helvetica, sans-serif"><?php echo $f1; ?></font></td>

<td><font face="Arial, Helvetica, sans-serif"><?php echo $f5; ?></font></td>

<td><font face="Arial, Helvetica, sans-serif"><?php echo $f6; ?></font></td>

</tr>

<?php
}
mysql_close();
?>
</tbody>
</table>
</div>

</body>
</html>
About us

<ion-view style="" class=" " id="page5" title="About Us">

 <ion-content class="has-header" padding="true">
<h3 class=" " style="color: rgb(0, 0, 0); text-align: center;"
id="aboutTheApp-heading18">Application is developed and documented
by</h3>
<h4 class=" " style="color: rgb(0, 0, 0); text-align: center;"
id="aboutTheApp-heading20">K.Ramakrishna</h4>
<h4 class=" " style="color: rgb(0, 0, 0); text-align: center;"
id="aboutTheApp-heading20">G.Sai Priya</h4>
<h4 class=" " style="color: rgb(0, 0, 0); text-align: center;"
id="aboutTheApp-heading20">T.Sai Tarun</h4>
<h3 class=" " style="color: rgb(0, 0, 0); text-align: center;"
id="aboutTheApp-heading21">Under the Guidance of</h3>
<h4 class=" " style="color: rgb(0, 0, 0); text-align: center;"
id="aboutTheApp-heading20">T.Madhu(Asst.Prof.)</h4>
<div style="width: 285px; height: 21px;" class="spacer"></div>
</ion-content>
</ion-view>

6.2 SCREEN SHOTS:

7. testing

7.1Introduction to Testing:
Testing is a process, which reveals errors in the program. It is the
major quality measure employed during software development. During
testing, the program is executed with a set of test cases and the output
of the program for the test cases is evaluated to determine if the
program is performing as it is expected to perform.

7.2 TESTING STRATEGIES

In order to make sure that the system does not have errors, the
different levels of testing strategies that are applied at differing phases
of software development are:
 Unit Testing:

Unit Testing is done on individual modules as they are completed

and become executable. It is confined only to the designer's
requirements.

Each module can be tested using the following two Strategies:

Black Box Testing:

In this strategy some test cases are generated as input

conditions that fully execute all functional requirements for the
program. This testing has been uses to find errors in the
following categories:

Incorrect or missing functions

Interface errors
Errors in data structure or external database
access
Performance errors
Initialization and termination errors.
In this testing only the output is checked for correctness.
The logical flow of the data is not checked.

White Box testing :

In this the test cases are generated on the logic of each

module by drawing flow graphs of that module and logical
decisions are tested on all the cases. It has been uses to
generate the test cases in the following cases:

Guarantee that all independent paths have been

Executed.
Execute all logical decisions on their true and false Sides.
 Execute all loops at their boundaries and within their
operational bounds Execute internal data structures to
ensure their validity.

Integrating Testing :

Integration testing ensures that software and subsystems

work together a whole. It tests the interface of all the modules
to make sure that the modules behave properly when
integrated together.

System Testing:

Involves in-house testing of the entire system before delivery to the

user. It's aim is to satisfy the user the system meets all
requirements of the client's specifications.

Acceptance Testing :

It is a pre-delivery testing in which entire system is tested

at client's site on real world data to find errors.
Test Approach :
Testing can be done in two ways:

Bottom up approach
Top down approach

Bottom Up Approach:

Testing can be performed starting from smallest and

lowest level modules and proceeding one at a time. For each
module in bottom up testing a short program executes the
module and provides the needed data so that the module is
asked to perform the way it will when embedded with in the
larger system. When bottom level modules are tested attention
turns to those on the next level that use the lower level ones
they are tested individually and then linked with the previously
examined lower level modules.

Top Down Approach:

This type of testing starts from upper level modules. Since

the detailed activities usually performed in the lower level
routines are not provided stubs are written. A stub is a module
shell called by upper level module and that when reached
properly will return a message to the calling module indicating
that proper interaction occurred. No attempt is made to verify the
correctness of the lower level module.

Validation:

The system has been tested and implemented successfully and

thus ensured that all the requirements as listed in the software
requirements specification are completely fulfilled. In case of
erroneous input corresponding error messages are displayed.

System security

The data base information we

9. BIBLIOGRAPHY
References for the project development were taken from the following books and
web Sites.