The project titled "Blood Donation Management System of Rangdhanu, JKKNIU" has been

submitted by Md. Abdul Kader, Roll No:19102020, session: 2018-19 and Sabrina Sultana, Roll
No: 19102026, session: 2018-19, has been accepted as satisfactory for the 3rd year 2nd semester
Software Development Project.

BOARD OF EXAMINERS

Signature Supervisor

1. Name of the Supervisor:

Dr. Md. Saiful Islam
Designation: Professor
Dept. of Computer Science & Engineering
Jatiya Kabi Kazi Nazrul Islam University

Signature Supervisor

2. Name of the Internal Member:

Designation:
Dept. of Computer Science & Engineering
Jatiya Kabi Kazi Nazrul Islam University

Signature Supervisor

3. Name of the Internal Member:

Designation:
Address:
 CANDIDATE 'S DECLARATION AND SUPERVISOR'S APPROVAL

As candidates, we declare that this project is our own work and has not been submitted by any
other form for another degree or diploma at any university of other institute of tertiary education.
Information derived from the published and unpublished work of others has been acknowledged
in the text and list of references is given.

Date: 20.02.2023 Signature

Md. Abdul Kader

Roll no: 19102020
Session: 2018-19

Date: 20.02.2023 Signature

Sabrina Sultana
Roll no:19102020
Session: 2018-19
As a supervisor, I authorize that the work is done under by close guidance. I have given
approval to submit that report to go for evaluation.

Date: 20.02.2023 Signature

Dr. Md. Saiful Islam

Professor
 DEDICATED TO

This project is dedicated to 'RANGDHANU', a voluntary organization of JKKNIU, who works

for managing blood in the crucial moments.
 TABLE OF CONTENTS:

List of figures

Acknowledgement

Abstract

Chapter 1: Introduction

1.1 Introduction

1.2 Problem statement

1.3 Motivation

1.4 Objective

1.5 Scope of the project

Chapter 2: Literature Review

2.1 Background

2.2 Analysis

2.3 Tools and method

Chapter 3: Requirements Specification

3.1 Functional Requirement

3.2 Non-functional Requirement

3.3 Domain Requirement

Chapter 4: Methodology

4.1 Software Model

4.2 Advantage of this Model in the System

4.3 Why not other Model?

Chapter 5: Design and Implementation

5.1 Design goals

5.2 Design Class Diagram

5.3 Database design

5.4 Algorithm

5.5 Architecture Design

Chapter 6: Software Testing

6.1 Unit testing

6.2 Integration testing

6.3 Acceptance testing

6.4 System testing

6.5 User Interface testing

Chapter 7: Conclusion

7.1 Result

7.2 Discussion
7.3 Limitations

7.4 Future Scope

7.5. References
 LIST OF FIGURES

Fig 2: Block diagram of literature review

Fig 2.3: Basic tools

Fig 4.1: Incremental Model

Fig 4.2: Member module design

Fig 4.3: Donor module design

Fig 5.2: Admin Module Design

Fig 5.5.1: Architectural Design for Admin

Fig 5.5.2 Architectural Design for User

Fig 7.1: Home page

Fig 7.2: About

Fig 7.3: Registration menu

Fig 7.4: Donor Registration Form

Fig 7.5: Member Registration Form

Fig 7.6: Log-in menu

Fig 7.7: Admin Log-in

Fig 7.8: Admin Page

Fig 7.9: Donor list to admin

Fig 7.10: Available donor for AB+ group

Fig 7.11: Member request list

Fig 7.13: Blood requests list

Fig 7.14: Form for new Campaign or post

Fig 7.15: Member log-in

Fig 7.16: Member page

Fig 7.17: Member Profile

Fig 7.18: Member Profile Edition

Fig 7.19: Donor Log-in

Fig 7.20: Donor profile

Fig 7.21: Edit Donor profile

Fig 7.22: Blood Request Form

 ACKNOWLEDGEMENT

All praise is to Almighty God for giving us such capabilities for the successful completion of this
project. A project is a golden opportunity for learning and self-development. We consider
ourselves very lucky and honored to have so many wonderful people lead us through in
completion of this project.

We would like to express our heartily gratitude to our project supervisor, Jatiya Kabi Kazi
Nazrul Islam University, Trishal, Mymensingh, for his guidance and supervision during the
entire project work who in spite of being extraordinary busy with her duties, took time out to
hear, guide and keep us on the correct path.

We also thank all of our friends, group members and lab assistant and our family for helping to
implement the project "Blood Donation Management System of Rangdhanu, JKKNIU". Finally,
we express our thanks to the Department of Computer Science and Engineering for supporting us
greatly through our graduate study.
 ABSTRACT

The gift of blood helps save lives, and the demand for blood and blood products is great. Blood
donation is a vital part of worldwide healthcare. It relates to blood transfusion as a life-sustaining
and life-saving procedure as well as a form of therapeutic phlebotomy as a primary medical
intervention. Over one hundred million units of blood are donated each year throughout the
world. Donors are screened for health risks that could make the donation unsafe for the recipient.
The donor is also examined and asked specific questions about their medical history to make
sure that donating blood is not hazardous to their health. Rangdhanu, a Voluntary Organization
works for the management of the donor at a large range. The process of donating and requesting
for blood needs a proper and systematic management. The development of “Blood Donation
Management System of Rangdhanu, JKKNIU” is proposed to provide a website capable of
storing information of donors and the people who request for blood and create a path for them to
communicate with each other by the voluntary organization.
 CHAPTER-1

INTRODUCTION
1.1 Introduction:

The gift of blood helps save lives, and the demand for blood and blood products is great.
Donation be of whole blood, or of specific components directly. Today in the developed world,
most blood donors are unpaid volunteers who donate blood for a community supply. In some
countries, established supplies are limited and donors usually give blood when family or friends
need a transfusion. Many donors donate for several reasons, such as a form of charity, general
awareness regarding the demand for blood, increased confidence in oneself, helping a personal
friend or relative, and social pressure. Despite the many reasons that people donate, not enough
potential donors actively donate.

“Blood Donation Management System of Rangdhanu, JKKNIU” project is aimed to developing

an online Blood Donation management system. The entire “Blood Donation Management
System of Rangdhanu, JKKNIU” project has been developed keeping in view of the distributed
client server computing technology, in mind. The system is to create an e-Information about the
donor and organization that are related to donating the blood. Through this System 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
patient 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 both the members of
Rangdhanu as well as donor and the member actually control the donor system.

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 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 visual
studio code.
 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 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.

The database connectivity was planned using the latest “SQL Connection” technology provided
by Microsoft Corporation. The authentication and authorization were crosschecked at all the
relevant stages. The user level accessibility has been restricted into two zones namely.

1.2 Problem Statement:

Rangdhanu, a voluntary organization, started its journey to meet the urgent blood needs of
patients. At first the journey started with very few members who started blood supply to their
relatives, friends, neighbors in need. But gradually the organization gained recognition through
their work and the demand for blood started increasing along with the members of the
organization. They receive about 20/30 requests for blood every day.
The percentage of people donating blood is increasing day by day due to awareness to
donate blood for those needed as well as the number of people that needs blood are also
increasing day by day. But the existing system is

To fixed these problems this project is conducted.

1.3 Motivations:

Safe blood saves lives. Blood is needed by women with complications during pregnancy and
childbirth, children with severe anemia, often resulting from malaria or malnutrition, accident
victims and surgical and cancer patients.

Rangdhanu manages blood donors who are unpaid volunteers who donate blood for a community
supply. Established supplies are limited and donors usually give blood when family or friends
need a transfusion. Many donors donate for several reasons, such as a form of charity, general
awareness regarding the demand for blood, increased confidence in oneself, helping a personal
friend or relative, and social pressure. Despite the many reasons that people donate, not enough
potential donors actively donate.

There is a constant need for a regular supply of blood because it can be stored only for a limited
period of time before use. Regular blood donation by a sufficient number of healthy people is
needed to ensure that blood will always be available whenever and wherever it is needed.

Blood is the most precious gift that anyone can give to another person - the gift of life. A
decision to donate your blood can save a life, or even several if your blood is separated into its
components red cells, platelets and plasma which can be used individually for patients with
specific conditions.

1.4 Objectives:

Donating blood is a great virtue. Our main objectives for this “Blood Donation Management
System of Rangdhanu, JKKNIU” are:

 A complete manual file system.

 No use of Web Services and Remoting.

 Risk of mismanagement of data.

 Less Security.

 Fewer Users – Friendly

 Store information about the donor.

 Store the information about the person who needs blood.

 Make them able to communicate with each other.

1.5. Scope of the Project:

Blood bank management system has much functionality. However, this project only focuses on
the information handling activities related to blood donors and blood distribution, managing the
collected blood information.

The scope of proposed system will focus on the following main tasks:

 The system used to register, update and view information of donor, members, .
 Creating account for user.
 Shows accessibility and availability of blood inside the stock by their blood group.
 Handling information with related to blood donors, seekers.
 Securing the information.
 An administration system which makes sure the total system for management.


 Chapter-2
Literature Review

This section provides the comprehensive background of the research conducted and discussions
are made on all the techniques used in this project. The chapter will be divided into sections that
provides with the brief introduction of the organization of prototype

Project
Design
Concept

Feasibility
Implementation
Study

Requirements
Testing
Analysis

Fig 2: Block diagram of literature review

2.1 Background

Blood Donation Management System is a Web Application based system that is designed to
store, process, retrieve and analyze information concerned with the administrative and inventory
management related activities. This management system is widely adopted to manage the data,
make the process clean and clear and introduce the transparency in process of work. Rangdhanu,
started the journey with a short scale blood donation system within the college. Gradually its
scope of action increased along with the demand for members and blood. But currently the
system is being physically maintained. Which is becoming difficult day by day. To solve the
problem, automatic system is required where the blood donor will enter the data with his
information, admin or member will check the donor's information and keep him in the list so that
everything can be easily maintained.

2.2 Analysis

Preliminary analyst analyses project feasibility, the likelihood the system will be useful to the
organization. The main objective of the analysis 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 analysis portion
of the preliminary investigation:
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 equipment 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?
Earlier no system existed to cater to the needs of ‘Secure Infrastructure Implementation System.
The current system developed is technically feasible. It is a web-based user interface. Thus, it
provides an easy access to the users. The database’s 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.
Operational Feasibility: Proposed projects are beneficial only if they can be turned out into
information system. That will meet the organization’s 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.

Economic Feasibility: A system can be developed technically and that will be used if installed
must still be a good investment for the organization. In the economic 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.

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 and technologies available
at NIC, there is nominal expenditure and economic feasibility for certain.
2.3 Tools and Methods

Proposed System is planned to developed under client server Architecture using the Web
Application System. To store the data backend MySQL Database is used. This system is
Developed using Microsoft Visual Studio\Notepad++. Following diagram illustrate the
implementation model that has been followed during the Development of Blood Donation
System.

Visual
Studio
Code/
Notepad
++

Front-end Back-end Database

HyperText Cascading
Hypertext
Markup Style JavaScript
Sheets Bootstrap Preprocessor MySQL
Language
(CSS) (PHP)
(HTML)

Fig 2.3: Basic tools

 Chapter-3

Requirements Specification
A software requirements specification is a document that describes what the software will do and
how it will be expected to perform.[2]

For a system the functional and nonfunctional requirements should be described so that they are
understandable by system users who don't have detailed technical knowledge. Ideally, they
should specify only the external behavior of the system. The requirements document should not
include details of the system architecture or design. System requirements are the user
requirements expanded versions of the user requirements that are used by software engineers as
the starting point for the system design.

3.1 Functional Requirements

The functional requirements for a system describe what the system should do. These
requirements depend on the type of software being developed, the expected users of the software,
and the general approach taken by the organization when writing requirements.

The functional requirements of our project are:

1. Registration and Log-in: the users (admin, members and donor) have to log in the
system for the total maintenance. For new members and donor they have to register a new
account for sign up. The admin give approve of the new member and donor for sign-up.
Member can also approve the donor.
2. Data entry, update and delete: when a new member or donor registration is approved
the data of info of him automatically store in the database. They can update their own
status. As the admin has the all access of the system, he can update the total status of all
the members and donor where as members have the access to update the donor info. The
admin can remove members and donors. The donor info is also stored for future analysis.
3. Donor status: A donor status can be on or off based on his ability to donate blood in case
of sickness or death.
 4. Request Blood: Any patient should be able to request for blood at emergency situations.
Admin and members need to define blood group, location, contact.

3.2 Non-Functional Requirements

Non-functional requirements, as the name suggests, are requirements that are not directly
concerned with the specific services delivered by the system to its users. They may relate to
emergent system properties such as reliability, response time, and store occupancy.
Alternatively, they may define constraints on the system implementation such as the capabilities
of I/O devices or the data representations used in interfaces with other systems. Non-functional
requirements are often more critical than individual functional requirements.

The non-functional requirements of our project are:

a. Maintainability & Serviceability:

 The Blood Donation Management System have must have high level of Maintainability.
If issue arises in the system, then the project will be programmed in such a way that we
can service it again.

b. Environmental & Usability:

 The blood donation system will work in latest operating system environments like
windows 7, windows 8, windows 10.
 The blood donation system will have a good looking and user-friendly interface.

c. Security:

 The blood donation system will be secured with proper user name and passwords.
 Chapter-4

Methodology
4.1 Software Model

A system model is the conceptual model as a result of system modeling that describes and
represents a system. A system comprises multiple views such as planning, requirement
(analysis), design, implementation, deployment, structure, behavior, input data and output data
views. A system model is required to describe and represent all these multiple views. There are
various software development models or methodologies. They are as follows:

 Waterfall model
 Incremental model
 Agile model
 Prototype model
 Spiral model
 RAD model

There is no standard model for every project. For our project “Blood Donation Management
System of Rangdhanu, JKKNIU” the process model suitable is Incremental Model.[3]

An incremental model is a type of software development model where the system is developed in
small increments or iterations. In this approach, the software is built in multiple stages, with each
stage delivering a working product that can be tested and evaluated.

Incremental Model is a process of software development where requirements divided into

multiple standalone modules of the software development cycle. In this model, each module goes
through the requirements, design, implementation and testing phases. Every subsequent release
of the module adds function to the previous release. The process continues until the complete
system achieved.

The incremental model is often used in agile software development methodologies, where
development is done in sprints or iterations, with each iteration building upon the previous one.
At the end of each iteration, the software is delivered and tested, and feedback is incorporated
into the next iteration.

The incremental model is useful when the requirements of the software are not well understood
or are likely to change during the development process. It allows for flexibility in the
development process, with changes being incorporated into later iterations.

This system is divided into different modules like admin, members, donor, request for blood,
updated campaign etc. and also it is a long-term process. So, we choose this incremental model
for the project.

Requirements

Admin Member Donor

Design & Design & Design &

Development Development Development

Testing Testing Testing

Implementation Implementation Implementation

Fig 4.1: Incremental Model

4.2 Advantage of this model in the System

 Early and frequent delivery of working software

 Improved collaboration and communication between developers and stakeholders
 Flexibility to incorporate changes in requirements
 Reduced risk of project failure due to early identification and resolution of issues
However, the incremental model can also be more complex to manage than other development
models, as it requires careful planning and coordination to ensure that each increment is
delivered on time and within budget.

4.3 Why not other model???

Incremental models are used when data arrives sequentially over time and the model needs to
adapt to changes in the data distribution. Here are some specific reasons why one might choose
an incremental model over other types of models:

 Real-time processing: Incremental models can update their parameters as new data
arrives, making them suitable for real-time processing where decisions need to be made
quickly. For example, in online advertising, the model needs to make ad placement
decisions in real-time based on the user's current behavior.

 Resource efficiency: Incremental models can be more resource-efficient than other

models because they update their parameters incrementally as new data arrives, rather
than retraining the model on the entire dataset every time new data arrives. This can save
time and computational resources, especially for large datasets.

 Non-stationary data: Incremental models can handle non-stationary data, where the data
distribution changes over time. For example, in anomaly detection, the model needs to
adapt to new types of anomalies that were not present in the training data.

 Scalability: Incremental models can scale well to large datasets because they can process
data in small batches rather than requiring all of the data to be loaded into memory at
once.
  Data privacy: Incremental models can be more privacy-preserving than other models
because they only need to store a small amount of data at any given time. This can be
important in situations where data privacy is a concern.

4.4 Modules and their functionalities used in the model:

4.4.1 Admin: Admin is the upper module which can access the total system. It’s
functionalities are

 Login & logout: To access the admin panel there is a session system where admin
has to log in via email and admin password.

 Donner management: It can access the blood request list and donor list. By which
it can ensure donor to the patients.

 Member request: It can approve or decline member request who are interested to
work for the organization.

 Donor request: Admin can also approve new donor

 Edition:

 Campaign: Admin can upload upcoming campaign of the team.

4.4.1 Member: Member module's functionalities are

 Registration: one has to register in the registration form for membership in the
organization. When admin approve the form he will get the membership.

 Login & logout: To access the module there is a session system where a member
has to log in via email and admin password.

 Donner management: Member can access the blood request list and donor list. By
which it can ensure donor to the patients.

 Donor request: Member can also approve new donor request.

 Edition: Member can edit his profile info.

4.4.1 Donor: Donor module's functionalities are

 Registration: One has to register in the registration form for entry as a donor in the
organization. When admin or any member approve the form, he will get the
membership.

 Login & logout: To access the module there is a session system where a donor has
to log in via email and admin password.

 Edition: Donor can edit his profile info after log in.

4.4.1 Patient: patient’s functionalities are

 Request for blood: A patient can only request for blood by filling up a form of the
blood info.
 Chapter-5

Design and Implementation

5.1 Design goals:

The design of the system is highlighted as follows, in terms of performance, maintenance, end
user criteria and security

Performance: The system will complete the task quickly to allow easy input of data and
to retrieve data from the server. The system will be accessible from any computer with
internet and will be accessible anytime a user would want to use the program. In terms of
performance, the system will help the user quickly accomplish their task.

Maintenance: It does not need expertise person but just it needs any professional person
in IT who can use database and internet. The system will require minimal upkeep and
maintenance to stay working at optimal levels.

End user: This project is very simple to use. Anyone who can read English language can
use the system, because, to use the system only clicking a button, it does not need to write
commands and to think how to use it. This program will have a well-defined and easily
understood interface. The processes will be easy to understand and use by a user of any
level.

Security requirement: Since the system will require strong security features to protect that
valuable information. To use it, it needs user name and password when they try to login
to the system. Therefore, it is very secured system. The end user of the system most of
the time will be asked for authorization login.
5.2 Design Class Diagram:

The class diagram represents the static view of an application. Class diagram is not only used for
visualizing, describing and documenting different aspects of a system but also for constructing
executable code of the software application. The class diagram describes the attributes and
operations of a class and the constraints imposed on the system. The classes diagrams are widely
used in the modeling of object-oriented systems because they are the only UML diagrams, which
can be mapped directly with object-oriented languages. The class diagram shows a collection of
classes, interfaces, associations, collaborations and constraints. It is also known as structural
diagram for this the team developed the following class diagram.
 New donor &
member

Ap Regi
stra
pr tion
ov
e

Admin Patients

login Request
Admin Panel

Donor

Logout

Donor
info

Donor list

Fig 4.1: Admin module design

 New donor

Ap Regi
stra
pr tion
ov
e

Member Patients
Login & Edit

profile Request
Member module

Donor
Logout

Donor
info

Fig 4.2: Member module

Donor list design
Donor

Login & Edit

profile
Member module

Logout

Donor
info

Donor list

Fig 4.3: Donor module design

5.3 Database Design

Physical database design translates the logical data model into a set of SQL statements that
define the database. The physical design of the database optimizes performance while ensuring
data integrity by avoiding unnecessary data redundancies. During physical design, the entities are
transformed into tables, the instances are transformed into rows, and the attributes are
transformed into columns.

The design of our project database is simple yet efficient. There are seven tables included and
each of them have different types of information and data. Let's discuss about the tables and the
data or information contained in these tables.

 Database:

 admin: Contain admin information

 bloodrequest: The blood requests details are saved here.

 district: A table that contain the district of Bangladesh

 donor: Contain donor information via donor registration form..

 member: Contain member’s information via member registration form.

 post: Contain the campaign info.

 upojila: Contain all the union under all district

5.4 Algorithm:
5.5 Architectural Design:

The term system architecture is used to describe the overall design and structure of a computer network or
system. A method is required to organize and connect these items together in a cohesive manner. The
term is also used to describe complex computer software tools. Systems Architecture is a generic
discipline to handle objects called "systems", in a way that supports reasoning about the structural
properties of the objects or it is the conceptual model that defines the structure, behavior, and more views
of a system.

Client Server Internet Web Server

Database

5.5.1 Architectural Design for Admin:

Admin

Request List
Donor List

Database

Update Update

Delete Delete

Fig 5.5.1: Architectural Design for Admin

5.5.2 Architectural Design for User:

Start

Admin
Login
Register

Request
dashboard

Donate
Request List
See My
Record
Donor List

Database

Update Delete

Fig 5.5.2: Architectural design for User

 Chapter-6

Software Testing

Testing is intended to show that a program does what it is intended to do and to discover à
defects before it is put into use. When you test software, you execute a program using artificial
data. You check the results of the test run for errors, anomalies, or information about program
the program's non-functional attributes.

Here are some testings that were used in our project:

6.1 Unit testing:

Unit test has been performed during the development of the code to test the code after every
block of code that is performed.

Unit tests that are done in our system are as follow:

 Test for login

 Test for user registration
 Test for user update user account
 Test for feedback

6.2 Integration Testing:

Integration testing is the activity of software testing in which individual software modules are
combined and tested as a group. It occurs after unit testing and before acceptance testing. Thus,
Integration testing is a logical extension of unit testing.
6.2 Acceptance Testing:

Acceptance testing is the process of testing system prior to its delivery. A system is mainly
developed for an end user normally a customer of the organization. A system is said to be
accepted if and only if the user of the system is satisfied. In this perspective acceptance, testing is
widely used to prove that system performs as per the requirements. In acceptance, testing the
customers provides the input data to validate the system operation. It is also known as functional
testing, black box testing, release acceptance, application testing, confidence testing, final testing
and validation testing.

6.4 System Testing:

It is the final step of testing. In this the team members tests the entire system as a whole with all
forms, code, modules. This form of testing is popularly known as Black Box testing or System
tests. In this the team members tests all the functionalities in the System. All errors in the forms,
functions, modules are tested.

6.5 User Interface Testing:

User interface testing, a testing technique used to identify the presence of defects is a
product/software under test by using Graphical user interface [GUI].

 GUI is a hierarchical, graphical front end to the application, contains graphical objects
with a set of properties.
 GUI is a hierarchical, graphical front end to the application, contains graphical objects
with a set of properties.
 It strongly depends on the used technology.
 Chapter-7

Conclusion
7.1 Results:

Fig 7.1: Home page

 Fig 7.2: About

Fig 7.3: Registration menu

Fig 7.4: Donor Registration Form
Fig 7.5: Member Registration Form

Fig 7.6: Log-in menu

Fig 7.7: Admin Log-in

 Fig 7.8: Admin Page

Fig 7.9: Donor list to admin.

Fig 7.10: Available donor for AB+ group

Fig 7.11: Member request list

 Fig 7.12: Member list

Fig 7.13: Blood requests list

Fig 7.14: Form for new Campaign or post

Fig 7.15: Member log-in

Fig 7.16: Member page

Fig 7.17: Member Profile

Fig 7.18: Member Profile Edition

Fig 7.19: Donor Log-in

Fig 7.20: Donor profile

 Fig 7.21: Edit Donor profile

Fig 7.22: Blood Request Form

7.2 Discussion:

Blood Donation is an important part of the world as many people are donating blood.
Governments and other organizations are making people aware of the fact that blood is needed
and why we should donate blood. Blood is needed by women with complications during
pregnancy and childbirth, children with severe anemia, often resulting from malaria or
malnutrition, accident victims and surgical and cancer patients. There is a constant need for a
regular supply of blood because it can be stored only for a limited period of time before use.
Regular blood donation by a sufficient number of healthy people is needed to ensure that blood
will always be available whenever and wherever it is needed. So, "Blood Donation
Management System of Rangdhanu, JKKNIU" can be helpful in this regard providing
information about the donor and the people of the team, we hope that this website will at-least be
little helpful in this regard.

7.3 Limitations:

 There is no mail system.

 There is no system for campaign launching.
 No messaging system.
 No automated system for communication user to user.


7.4 Future Scope:

 Creating a notification system using the user email to notify them about information
needed.
 Creating automated communication system.

7.5 References:

 https://www.w3schools.com/html/default.asp
 https://www.facebook.com/rangdhanu.jkkniu