BLOOD BANK AND DONOR MANAGEMENT

SYSTEM
A dissertation submitted in partial fulfillment for the award of the degree of
BACHELOR OF ENGINEERING
in
KONGUNADU COLLEGE OF ENGINEERING AND
TECHNOLOGY
(AUTONOMOUS)
Submitted by
R.Abinaya (621318104002)
M.Prithika (621318104039)
M.Priyanka (621318104040)
Under the Guidance of
Mr. K.BASKAR, M.E.,(Ph.D),
Assistant Professor
Department of Computer Science and Engineering
KONGUNADU COLLEGE OF ENGINEERING AND
TECHNOLOGY
(AUTONOMOUS)
TRICHY-621215
DEC-MAY
2019-2020
KONGUNADU COLLEGE OF ENGINEERING AND TECHNOLOGY
(AUTONOMOUS)
Tholurpatti (Po), Thottiam (Tk), Trichy (Dt) - 621 215
COLLEGE VISION & MISSION STATEMENT

VISION

"To become an Internationally renowned Institution in technical education,

research and development, by transforming the students into competent
professionals with leadership skills and ethical values."

MISSION

 Providing the Best Resources and Infrastructure.

 Creating Learner centric Environment and continuous -Learning.

 Promoting Effective Links with Intellectuals and Industries.

 Enriching Employability and Entrepreneurial Skills.

 Adapting to Changes for Sustainable Development.

 COMPUTER SCIENCE AND ENGINEERING
VISION
To produce competent software professionals, academicians, researchers and
entrepreneurs with moral values through quality education in the field of Computer
Science and Engineering.
MISSION
 Enrich the students' knowledge and computing skills through innovative
teaching-learning process with state- of- art- infrastructure facilities.
 Endeavour the students to become an entrepreneur and employable through
adequate industry institute interaction.
 Inculcating leadership skills, professional communication skills with moral
and ethical values to serve the society and focus on students' overall
development.

PROGRAM EDUCATIONAL OBJECTIVES

 PEO I: Graduates shall be professionals with expertise in the fields of
Software Engineering, Networking, Data Mining and Cloud computing
and shall undertake Software Development, Teaching and Research.
 PEO II: Graduates will analyze problems, design solutions and develop
programs with sound Domain Knowledge.
 PEO III: Graduates shall have professional ethics, team spirit, life-long
learning, good oral and written communication skills and adopt
corporate culture, core values and leadership skills.
PROGRAM OUTCOMES:

1. Engineering knowledge: Apply the knowledge of mathematics, science,

engineering fundamentals, and an engineering specialization to the solution of
 complex engineering problems.

2. Problem analysis: Identify, formulate, review research literature, and analyze

complex engineering problems reaching substantiated conclusions using first
principles of mathematics, natural sciences, and engineering sciences.

3. Design/development of solutions: Design solutions for complex engineering

problems and design system components or processes that meet the specified
needs with appropriate consideration for the public health and safety, and the
cultural, societal, and environmental considerations.

4. Conduct investigations of complex problems: Use research-based

knowledge and research methods including design of experiments, analysis
and interpretation of data, and synthesis of the information to provide valid
conclusions.

5. Modern tool usage: Create, select, and apply appropriate techniques,

resources, and modern engineering and IT tools including prediction and
modeling to complex engineering activities with an understanding of the
limitations.

6. The engineer and society: Apply reasoning informed by the contextual

knowledge to assess societal, health, safety, legal and cultural issues and the
consequent responsibilities relevant to the professional engineering practice.

7. Environment and sustainability: Understand the impact of the professional

engineering solutions in societal and environmental contexts, and demonstrate
the knowledge of, and need for sustainable development.

8. Ethics: Apply ethical principles and commit to professional ethics and

responsibilities and norms ofthe engineering practice.
9. Individual and team work: Function effectively as an individual, and as a
member or leader in diverse teams, and in multidisciplinary settings.

10.Communication: Communicate effectively on complex engineering activities

with the engineering community and with society at large, such as, being able
to comprehend and write effective reports and design documentation, make
effective presentations, and give and receive clear instructions.

11.Project management and finance: Demonstrate knowledge and

understanding of the engineering and management principles and apply these
to one’s own work, as a member and leader in a team, to manage projects and
in multidisciplinary environments.

12.Life Long Learning: Recognize the need for, and have the preparation and
ability to engage in independent and life-long learning in the broadest
context of technological change.

B. E (CSE) - PROGRAM SPECIFIC OUTCOMES (PSO's)

 PSO1: Professional skills: Students shall understand, analyze and develop

computer applications in the field of Data Mining/Analytics, Cloud

Computing, Networking etc., to meet the requirements of industry and
society.

 PSO2: Competency: Students shall qualify at the State, National and

International level competitive examination for employment, higher studies

and research.
 BONAFIDE CERTIFICATE

This is to certify that the dissertation entitled “BLOOD BANK AND

DONOR MANAGEMENT SYSTEM” is a bonafide work carried out by
R.Abinaya (621318104002), M.Prithika (621318104039), M.Priyanka
(621318104040) my direct supervision is submitted in partial fulfillment of the
requirements for the award of degree of Bachelor of Engineering in COMPUTER
SCIENCE AND ENGINEERING to Kongunadu College of Engineering and
Technology, Trichy – 621 215. No part of the dissertation has been submitted for
any degree/diploma or any other academic award anywhere before.

SIGNATURE SIGNATURE
Dr .C. SARAVANABHAVAN, M.Tech Ph.D., Mr. K.BASKAR,M.E.,(Ph.D),
HEAD OF THE DEPARTMENT SUPERVISOR
Assistant Professor
Department of Computer Science and Department of Computer Science and
Engineering Engineering
Kongunadu College of Engineering and Kongunadu College of Engineering and
Technology, Thottiam,Trichy-621 215 Technology, Thottiam,Trichy-621 215
 ACKNOWLEDGEMENT

We wish to express our sincere thanks to our beloved respectful and

honorable chairman Dr. PSK.R.PERIASWAMY for providing immense facilities
in our institution.
We proudly render our thanks to our Principal Dr. R. ASOKAN, M.S.,
M.Tech., Ph.D., for the facilities and the encouragement given by him to the
progress and completion of my mini project.
We proudly render our immense gratitude to our Head of the Department of
Computer Science and Engineering Dr. C. SARAVANABHAVAN, M.Tech.,
Ph.D., for his effective leadership, encouragement and guidance in the mini
project.
We highly indebted to provide our heartfelt thanks to my respectful
supervisor Mr. K.BASKAR, M.E.,(Ph.D), for his valuable ideas, constant
encouragement and supportive guidance throughout the project.

We highly indebted to provide our heartfelt thanks to our respectful mini

project coordinator Mr. K.KARTHICK, M.E., (Ph.D)., for his supportive
guidance throughout the mini project.

We wish to extend our sincere thanks to all teaching and nonteaching staff of
information technology department for their valuable suggestions, cooperation and
encouragement on successful completion of this project.

We wish to acknowledge the help received from various department and

various individuals during the preparation and editing stages of the manuscript.
 TABLE OF CONTENTS
CHAPTER NO TITLE PAGE NO
ABSTRACT 1
1 INTRODUCTION
1.1 Objective 2
1.2 Problem Description 2
2 REQUIREMENT SPECIFICATION
2.1 Hardware specification 4
2.2 Software specification 4
3 ANALYSIS
3.1 Existing system 5
3.2 Feasibility study 6
4 DESIGN
4.1 System Design 7
5 IMPLEMENTATION
5.1 Source Code 8
6 TESTING
6.1 Introduction 12
7 SCREEN SHOTS 13

8 CONCLUSION

8.1 Conclusion 14

8.2 Benefits 14

9 REFERENCE

9.1 References for blood donation 15

 ABSTRACT

The purpose of the study is to develop blood management information

system to assist in the management of blood donor records and case to control the

distribution of blood in various part of the country based on the hospital demands

without quick and timely access to donor records, creating market strategies for

blood donation, lobbying and sensitization of blood donors become very difficult.

The blood management information system offers functionalities to quick access

donor records. The language behind the project in the part of front end is HTML

and the back end is MySQL. It enables monitoring of results and performance of

blood donation activities such that relevant and measurable object of organization

can be checked. All the updating information can be viewed by the users. It gives

answers to various managements.

1
 CHAPTER-I
1.INTRODUCTION

1.1 Objective:

The Blood Donation Agent is to create an e-Information about the donor and
organization that are related to donating the blood. Through this application any person
who is interested in donating the blood can register himself in the same way if any
organization wants to register itself with this site that can also register. Moreover if any
general consumer wants to make request blood online he can also take the help of this
site. Admin is the main authority who can do addition, deletion, an d
modification if required.

1.2 Problem Description:

This project is aimed to developing 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 and
organization that are related to donating the blood. Through this application any person
who is interested in donating the blood can register himself in the same way if any
organization wants to register itself with this site that can also register. Moreover if any
general consumer wants to make request blood online he can also take the help of this
site.
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

2
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 data protective 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.
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.
The entire project has been developed keeping in view of the distributed
client server computing technology, in mind. The specification has been normalized up to
3NF to eliminate all the anomalies that may arise due to the database transaction that are
executed by the general users and the organizational administration. The user interfaces
are browser specific to give distributed accessibility for the overall system. The internal
database has been selected as MS-SQL server 2000.

The basic constructs of table spaces, clusters and indexes have been exploited
to provide higher consistency and reliability for the data storage. The MS-SQL server
2000 was a choice as it provides the constructs of high-level reliability and security. The
total front end was dominated using the ASP.Net technologies. At all proper levels high
care was taken to check that the system manages the data consistency with proper
business rules or validations.

3
 CHAPTER- II
2.REQUIREMENT SPECIFICATION

2.1. HARDWARE SPECIFICATION:

1.PIV 2.8 GHz Processor

2.RAM 512MB and Above

3.HDD 20 GB Hard Disk Space and Above

2.2 SOFTWARE SPECIFICATION:

1.WINDOWS OS (XP / 2000 / 200 Server / 2003 Server)

2.Visual Studio .Net 2005 Enterprise Edition

3.Internet Information Server 5.0 (IIS)

4.Visual Studio .Net Framework (Minimal for Deployment)

5.SQL Server 2000 Enterprise Edition

4
 CHAPTER-III
3. SYSTEM ANALYSIS
Software Requirement Specification (SRS)
The software, Site Explorer is designed for management of web sites from a
remote location.
INTRODUCTION
Purpose: The main purpose for preparing this document is to give a general
insight into the analysis and requirements of the existing system or situation and
for determining the operating characteristics of the system.
Scope: This Document plays a vital role in the development life cycle (SDLC) and
it describes the complete requirement of the system. It is meant for use by the
developers and will be the basic during testing phase. Any changes made to the
requirements in the future will have to go through formal change approval process.

3.1.Existing System:
 Cannot Upload and Download the latest updates.
 No use of Web Services and Remoting.
 Risk of mismanagement and of data when the project is under
development.
 Less Security.
 No proper coordination between different Applications and Users.
 Fewer Users – Friendly
Disadvantages
1. User friendliness is provided in the application with various controls.

5
 2. The system makes the overall project management much easier and
flexible.
3. Readily upload the latest updates, allows user to download the alerts by
clicking the URL.
4. There is no risk of data mismanagement at any level while the project
development is under process.
5. It provides high level of security with different level of authentication.

Proposed System:
To debug the existing system, remove procedures those cause data redundancy,
make navigational sequence proper. To provide information about audits on
different level and also to reflect the current work status depending on
organization/auditor or date. To build strong password mechanism.

Advantages:
 User friendliness I provided in the application with various controls.
 The 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 high level of security with different level of
authentication.

6
 CHAPTER-IV
4. SYSTEM DESIGN

4.1. Data Flow Diagrams (DFD)

A data flow diagram is graphical tool used to describe and analyze
movement of data through a system. These are the central tool and the basis from
which the other components are developed. The transformation of data from input
to output, through processed, may be described logically and independently of
physical components associated with the system. These are known as the logical
data flow diagrams.
The physical data flow diagrams show the actual implements and movement
of data between people, departments and workstations. A full description of a
system actually consists of a set of data flow diagrams. Using two familiar
notations Yourdon, Gane and Sarson notation develops the data flow diagrams.
Each component in a DFD is labeled with a descriptive name. Process is further
identified with a number that will be used for identification purpose.
The development of DFD’S is done in several levels. Each process in lower
level diagrams can be broken down into a more detailed DFD in the next level.
The lop-level diagram is often called context diagram. It consists a single process
bit, which plays vital role in studying the current system. The process in the
context level diagram is exploded into other process at the first level DFD.
The idea behind the explosion of a process into more process is that understanding
at one level of detail is exploded into greater detail at the next level.

7
 CHAPTER-V
5. IMPLEMENTATION
5.1. CODING:
WEBCONFIG FILE:(Design Code)
Used to set the connections of each page.
<?xml version="1.0"?>
<!--
Note: As an alternative to hand editing this file you can
use the
web admin tool to configure settings for your application.
Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
\Windows\Microsoft.Net\Framework\v2.x\Config
-->
<configuration>
<appSettings>
<add key="ConnStr" value="data source=RAMYA-
2DCA5B123;database=BloodBequeathFederalAgent;integrated
security=sspi"/>
</appSettings>
<connectionStrings>
<add name="BloodDonationAgentConnectionString"
connectionString="Data Source=RAMYA-2DCA5B123;Initial
Catalog=BloodDonationAgent;integrated security=sspi"
providerName="System.Data.SqlClient" />
</connectionStrings>
<system.web>
<!--
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.
-->
<compilation debug="true">
<assemblies>

8
 <add assembly="System.Design,
Version=2.0.0.0, Culture=neutral,
PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Web.Extensions,
Version=1.0.61025.0, Culture=neutral,
PublicKeyToken=31BF3856AD364E35"/>
<add assembly="System.Web.Extensions.Design,
Version=1.0.61025.0, Culture=neutral,
PublicKeyToken=31BF3856AD364E35"/>
<add assembly="System.Windows.Forms,
Version=2.0.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089"/></assemblies></compilation>
<!--
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<authentication mode="Windows"/>
<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.

<customErrors mode="RemoteOnly"
defaultRedirect="GenericErrorPage.htm">
<error statusCode="403" redirect="NoAccess.htm" />
<error statusCode="404" redirect="FileNotFound.htm"
/>
</customErrors>
-->
</system.web>
</configuration>

9
 User Login Form
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
public partial class Login : System.Web.UI.Page
{
CheckUser user = new CheckUser();
UserAccountBusinessLayer account = new
UserAccountBusinessLayer();
OrganizationAccountBusinessLayer org = new
OrganizationAccountBusinessLayer();
protected void Page_Load(object sender, EventArgs e)
{
txtUsername.Focus();
}

protected void btnLogin_Click(object sender, EventArgs e)

{
try
{
user.Username = txtUsername.Text;
user.Password = txtPassword.Text;
//Check User

if (user.GetUser() == true)
{
account.Username = txtUsername.Text;
DataSet ds = new DataSet();
ds = account.GetAccountId();
string AcId =
ds.Tables[0].Rows[0][0].ToString();
Session["username"] = txtUsername.Text;
Session["Acid"] = AcId;
DataSet ds1 = new DataSet();
account.Accountid =int.Parse(AcId);
ds1 = account.GetAddressId();

10
 Session["addid"] =
ds1.Tables[0].Rows[0][0].ToString();
Response.Redirect("~/Donor/DonorHome.aspx");
}
else
Image2.Visible = true;
lblMsg.Text = "Your Login Attempt Is Failed Plz try
Again....!";
txtPassword.Text = "";
txtUsername.Focus();
//Checking Organization
if (user.GetOrganization() == true)
{
account.Username = txtUsername.Text;org.Orgid
=int.Parse(AcId);
ds1 = org.GetOrgAddressId();

Session["addid"]=ds1.Tables[0].Rows[0][0].ToString();

Response.Redirect("~/Organization/OrganizationHome.aspx");
}
else
Image2.Visible = true;
lblMsg.Text = "Your Login Atempt Is Failed Plz try
Again....!";
txtPassword.Text = "";
txtUsername.Focus();
//Employee Checking
if (user.CheckEmployee() == true)
{
account.Username = txtUsername.Text;
DataSet ds = new DataSet();
ds = account.GetAccountId();
string AcId =
ds.Tables[0].Rows[0][0].ToString();
Session["username"] = txtUsername.Text;
Session["Acid"] = AcId;

Response.Redirect("~/CallCenter/CallCenterHome.aspx");
}

}
}

11
 CHAPTER-VI
6. TESTING
6.1. INTRODUCTION

Software testing is a critical element of software quality assurance and

represents the ultimate review of specification, design and coding. In fact, testing is
the one step in the software engineering process that could be viewed as
destructive rather than constructive.

A strategy for software testing integrates software test case design methods
into a well-planned series of steps that result in the successful construction of
software. Testing is the set of activities that can be planned in advance and
conducted systematically.
The software engineering process can be viewed as a spiral. Initially system
engineering defines the role of software and leads to software requirement analysis
where the information domain, functions, behavior, performance, constraints and
validation criteria for software are established.
TYPES OF TESTING:
1.Unit testing
2.Module testing
3.Sub system testing
4.System testing
5.Acceptance testing

12
CHAPTER-VII
7.SCREENSHOT

13
 CHAPTER-VIII
8.CONCLUSION

8.1. CONCLUSION:

It has been a great pleasure for me to work on this exciting and challenging Project
.This project proved good for me as it provided practical knowledge of not only
programming in ASP.NET and VB.NET web based application and no some extent
Windows Application and SQL server , but also about all handling procedure
related with “Blood Bequeth Federal” .It also provides knowledge about the latest
technology used in developing web enable Application and client server
technology that will be great demand in future .This will provide Better
oppurtunities and guidance in future in developing projects independently.

8.2. BENEFITS:
 This project offers user to enter the data through simple and interactive forms.
This is very helpful for the client to enter the desired information through so
much simplicity.
 The user is mainly more concerned about the validity of the data, whatever he is
entering. There are checks on every stages of any new creation, data entry or
updation so that the user cannot enter the invalid data, which can create
problems at later date.

14
 CHAPTER-IX
9. REFERENCE

9.1. REFERENCES:

1).Safe blood and blood products . Module 1: Safe blood donation. Geneva:
World Health Organization; 2002. [17 August 2012]. http://www
.who.int/bloodsafety/transfusion_services/bts_learningmaterials
/en/index.html
2).Blood donor selection Guidelines on assessing donor suitability for blood
donation Annex 3. Geneva: World Health Organization; 2012. [17 August
2012]. http://www.who.int/bloodsafety/voluntary_donation/blood_donor
_selection_counselling/en/ [PubMed]

3).Aide-mémoire Blood safety. Geneva: World Health Organization; 2002.

[17 August 2012]. http://www.who.int/bloodsafety/publications
/who_bct_02_03/en/index.html.

4).WHO/IFRC. Towards 100% voluntary blood donation: A global

framework for action. Geneva: World Health Organization; 2010. [17 August
2012]. http://www.who.int/bloodsafety/publications/9789241599696/en/

5).The Melbourne Declaration on 100% voluntary non-remunerated donation

of blood and blood components. Geneva: World Health Organization; 2009.
[17 August 2012]. http://www.who.int/worldblooddonorday/Melbourne
_Declaration_VNRBD_2009.pdf.

15