Documentation For All Projects 2020

Blood Bank Management System Page |1
CHAPTER-1
INTRODUCTION
Acharya Institutes of Graduate Studies Department of Computer Application

INTRODUCTION
Blood is the part of life that is given to those who need it by those who have the resource to
satisfy the need. The love of fellow human and desire to share something of one self is what
signal out of blood donor from the others. Emergency and the patients could have set back if
blood is not available.
A single donation from you can help one or more patients. This is possible because whole
blood is made up of several useful components. These components perform special function
in your body and the of patients who receives your blood. The various blood components are
Red Blood Cells, Platelets, plasma and plasma proteins. Each of these components can be
separated from your donation volume of blood and transfused into a specific patient requiring
the particular component. Thus, it can benefit one unit of blood.
Blood is needed every minute:
a) To replace blood lost because of accidents or diseases.

b) To treat shocks due to injury.
c) For major and minor surgeries including open heat surgeries, transplants etc.
d) For burn victims.
e) For patients suffering from Anemia.
f) During child birth for mother.
g) For exchange transfusion for new born infants.
h) To make blood derivatives which are used to treat medical problem.
An early leading to the establishment of blood bank occurred in 1915. In 1937, the first
hospital blood bank in the United States was established. In creating a hospital laboratory that
preserved
and store donor blood, Fantasy originated the team “Blood bank”. With a few year Hospital
and community blood bank were established across the United States of America. Now blood
banks are widely spread across the globe.
In the developed world, most blood are unpaid volunteers who give blood for a community
supply. In poorer countries, established supplies are limited and donor usually give blood
when family or friend need a transfusion. Many donors donate as an act of charity, but some

are paid and in some cases there are incentive other than money such as paid time off from
work. A donor is evaluated for anything that might make their blood unsafe to use. The
screening include testing for disease that can be transmitted by a blood transfusion, including
HIV and viral hepatitis. The donor is also asked about medical history and given a short
physical examination to make sure that the donation is not hazardous to his or her health.
How often a donor can give varies from days to month based on what he or she donates the
law of the country where the donation takes place.
Introduction to module:
a) Admin login
b) Add Blood donor
c) Add Blood
d) Add Blood Stock
e) Donors Report
f) Blood report
g) Stock Report

CHAPTER – 2
LITERATURE SURVEY

Literature survey
Everything on the earth living or non-living ha an evolution cycle. Like scientist has prove
implemented an evolution cycle from ape of man. In same manner the computer has an
evolution cycle, as technology is improving the computer are becoming more and more
efficient. Similarly, as the computer architecture is improving day by day, it is require
upgrading the previous system according.
As our company is launching this software for the first time. Similarly, software's of different
companies are present in the market and we tried to study those, a brief discussion was
carried out with the project guide to know more details about existing system. After
discussion the various deficiencies in the system was identified these points are noted down
and discussed with project guide again and decide where to make modification over existing
system.
Since we are implementing our software in the new environment and using the present
technology so make more efficient, there was a need to understanding the software's
environment and also about the new technologies. and while implementing the software
various thing has been taken into consideration like software will also be usable for those end
users who don't understand English.
Existing system
An existing system refers to the system that is being followed till now. Presently in almost all
the hospital und blood banks they store all the details in a huge ledger. Whenever an
emergency arises the employees of the blood bank has to go through the huge ledger or a
matching one. In such emergency situation, it’s not advisable to continue with the present
system. Even if the donor details are found are found, the people number or the other contact
details may not be valid or update one.
Drawback of Existing System

a. Time consuming.
b. Updating and Retrieval task are very tedious.
c. More manual work.
d. Easy Customer service is difficult.
e. Lot of paper work result in lot of confusion.
f. Data is not readily available in an emergency situation.

To avoid all these limitations and make the system working more accurately it needs to be
computerized.
Proposed system
The Online blood bank management system is user-friendly software. The main objective of
the system is which shows and help you to collect Information about the donor such as the
contact details. It helps in finding out the blood bank details such as donor details, employee
details, etc.
The main objective the proposed system can be enumerated as follows:

a. Patients are easily getting the matching blood.
b. Donor search is possible
c. Matching blood group can be found easily form the table.
d. Employee details and salary generation become easy.
e. Stock details are easily available.
Merits of proposed system

The system is very simple in design and to implement. The system requires very low system
resource and the system will work in almost all Configurations.
A. Security of data
B. Ensure data accuracies.
C. Administrator control the entire system
D. Data storage becomes more effort less.
E. Minimize manual data entry
F. great efficiency
G. User friendly and interactive.
H. Saves lot of time.
I. Retrieve and updating tasks can be performed much faster and easier.
Overview of languages used

The proposed system is developed using visual basic as the front end and MySQL as the back
end
PHP
PHP was originally an acronym for Personal Home Pages, but is now a recursive acronym for
PHP: Hypertext Preprocessor
PHP was originally developed by the Danish Greenlander Rasmus Lerdorf, and was
subsequently developed as open source. PHP is not a proper web standard but an open-source

technology. PHP is neither real programming language - but PHP lets you so-called scripting
in your documents.
To describe what a PHP page is, you could say that it is a file with the extension PHP that
contains a combination of HTML tags and scripts that run on a web server.
OPERATORS
Programming language have a set of operators that perform arithmetical operations, and other
such as Boolean operators on truth values, and string operators manipulating strings of text.
Computers are mathematical devices, but compilers and interpreters require a full syntactic
theory of all operations in order to parse formula involving any combinations correctly. In
particular they depend on operator precedence rules, on order of operations, that are tacitly
assumed in mathematical writing.
So, operators are special symbols that are used to represent for example simple computations
like addition and multiplication. Most of the operators in VB do exactly what you would
expect them to do, because they are common mathematical symbols. For example, the
operators for adding two integers is +.
PHP CONTROLS
Like its procedure, PHP in creating graphical user interfaces. Although the programmer still
has the option of creating controls and setting their properties programmatically (i.e. by hand
writing the code), he usually will create many, if not all of the controls in the interfaces by
selecting items from the toolbox and adding to a particular form. While working with forms,
you can use the toolbox to drag different controls to the form you are designing, resize them
and relocate them using the mouse, and set the controls properties in a corresponding
properties window to quickly develop the user interface. Event handler for each controls most
common event can be quickly created by double-clicking to create a new event handler and
be send to that event handler in the code window.
How MYSQL works

MySQL is a fast, easy-to-use RDBMS being used for many small and big businesses.
MySQL is developed, marketed, and supported by MySQL. AB, which is a Swedish
company. MySQL is becoming so popular because of many good reasons:
 The MySQL software consists of the MySQL server, several utility programs
 that assist in the administration of MySQL databases, and some MySQL
 MySQL is released under an open-source license. So you have nothing to pay to use
it.
 MySQL is a very powerful program in its own right. It handles a large subset of the
functionality of the most expensive and powerful database packages.
 MySQL uses a standard form of the well-known SQL data language.

 MySQL works on many operating systems and with many languages including PHP.
PERL C, C AVA, etc.
 MySQL works very quickly and works well even with large data sets.
 MySQL is very friendly to PHP, the most appreciated language for web development.
 MySQL supports large databases, up to 50 million rows or more in a table. The
default file size limit for table is 4GB, but you can increase this (if your operating system can
handle it) to a theoretical limit of 8 million terabytes (TB).
 MySQL is customizable. The open-source GPL license allows programmers to
modify the MySQL software to fit their own specific environments. Supporting software that
the MySQL server needs (but you don't need to know about).
The heart of the system is the MySQL server. The MySQL server is the manager of the
database system. Handles all your database instructions. For instance, if you want to create a
new database, you send message to the MySQL server that says "create a new database and
call it new data." The MySQL server then creates a subdirectory in its data directory, names
the new subdirectory new data, and puts necessary files with the required format into the new
data subdirectory. In the same manner, to add data to that database, you send a message to the
MySQL server, giving it the data and telling it where you want the data to be added. You find
out how to write and send messages to MySQL in Part II. Before you can pass instructions to
the MySQL server, it must be running and waiting for requests. The MySQL server is usually
set up so that it starts when the computer starts and continues running all the time. This is the
usual setup for a Web site. However, it's not necessary to set it up to start when the computer
starts. If you need to, you can start it manually whenever you want to access a database.
When it's running, the MySQL server listens continuously for messages that are directed to it.
CONCLUSION
MySQL triggers allow you to execute stored program code whenever a DML statement is
issued against database table. In MySQL 5.0. triggers can be used to automate
denormalization or logging implementation of data validation in MySQL triggers is more of a
challenge, as in MySQL there Is no easy or straightforward way to raise an error condition or
abort the transaction when validation fails. be remedied when the SIGNAL statement is
implemented in MySQL 5.2. In this chapter we presented a workaround that does allow data
validation triggers to be created in the interim. Although the error text generated far from
ideal.

CHAPTER – 3
REQUIREMENT ANALYSIS

Blood Bank Management System P a g e | 10
Requirement Analysis
Role of 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 inputs) into a formal document. Software Requirement
Specification is the medium though which the client and user needs are accurately specified.
It forms the basis of software development.
The SRS document itself states in precise and explicit language those function and
capabilities a software system must provide as well as states any required constraints by
which the system must abide. The SRS also function as a blueprint for completing a project
with as little cost growth as possible. The SRS is often referred to as the "parent" document
because all subsequent project management documents, such as design specifications,
statements of work, software architecture specifications, testing and validation plans, and
documentation plans, as related to it.
It's important to note that an SRS contains functional and non-functional requirement only:
it’s doesn't offer design suggestions, possible solutions to technology or business issues, or
any other information other than what the development team understands the customers
system requirements to be.
A well-designed, well-written SRS accomplishes four major goals:
a. It provides feedback to the customer. An SRS is the customer's assurance that the
development organization understands the issues or problems to be solved and the software
behaviour necessary to address those problems. Therefore, the SRS should be written in
natural language, in an unambiguous manner that may also include charts, tables, data flow
diagrams, decision tables, and so on.
b. It decomposes the problem into component parts. The simple act of writing down
software requirements in a well-designed format organize information, places borders around
the problem, solidifies ideas, and helps break down the problem into its component parts in
an orderly fashion.
SRS are typically developed during the first stages of "Requirement Development" which is
the initial product development phase in which information is gathered about what
requirements are needed and not. This information gathering stage on-investment (ROI)
analysis or needs analysis of the customer or client current business environment. The actual
specification, then, is written after the requirement have been gathered and analysed.
AIM
a. This application is designed to maintain the details of Blood Bank

b. This software helps in correct maintenances of the details of the blond bank such as
Donor receipt details, equipment details, blood issue details etc.
c. The application allows administrator to access the data and to update the data of the
system
d. The application is user friendly and provides all the information required.
e. The application must work properly without problems on all targeted devices and
network support.
PURPOSE
The purpose of the documents is to describe all external requirements of Online Blood Bank.
It also describes the interfaces for the system. The basic idea the project is to provide the
details available in the blood bank. The main objective of this application is to automate the
complete operations of the blood bank. They need maintain hundreds of thousands of records.
Also searching should be very faster so they can find required details instantly.
SCOPE
This application is built such a way that it should suits for all type of blood banks in future.
So every effort is taken to implements this projects in this blood bank, on successful
implementation in this blood bank, we can target other blood bank in the city.
SOFTWARE REQUIREMENTS:
Front End : HTML, CSS, JavaScript, PHP
Back End : MY SQL
Operating System : All Windows Operating System, Linux & Mac Operating
System
HARDWARE REQUIREMENTS:

PROCESSOR : Intel core
RAM : 512 MB
HARD DISK : 20GB or more
MONITOR : CRT &LED
KEYWORD : Normal or Multimedia
MOUSE : Compatible mouse
MODEM : ADLS, DLS
FUNCTIONAL REQUIEMENTS:
The main purpose of functional requirements is to define all activities or operations that take
place in the system. These are derived through interactions with the users of the system.
Since requirements specification is a comprehensive document and contains a lot of data, it
has been broken down into different stages in this report.
ADMINISTRATOR MODULE FUNCTIONAL REQUIRMENTS:
Administrator has all the rights of maintaining all the records of the blood bank and also can
maintain the stock and employee details. Administrator will be responsible for editing and
updating the information of the application. Administrator will only have the access to the
application.
NON-FUNCTIONAL REQUIREMENTS:
1. RELIABILITY
Reliability is the correlation of an item with a hypothetical one, which truly measures what it
is supposed to. Since the true instrument is not available. The program according to the
requirement can perform the intended function

a. Back-up option for backing up the database etc.

b. Error-handling-exception occurring while accessing database need to be addressed.
2. USABILITY
Usability refers to the capability of the product to be understood, learned and used and user
friendly to users, when used specified conditions. This section should include all of those
requirements that affect usability.
3. MAINTAINABILITY
Maintainability is the ease with which a program/specification can be corrected if an error

occurs desires a change in requirements. Specify attributes of software that relate to the ease
of maintenance of the affect usability.
4. PERFORMANCE
Performance is measured in terms of the output provided by the application. Requirements

specification plays an important part in the analysis of a system. Only when the requirements
specifications are properly given, it is possible to design a system, which will fit into required
environment.

CHAPTER – 4
DESIGN

Data flow diagram notation

The data flow diagram (DFD) is the one of the most important modeling tools. It shows the
use of the pictorially. DFD represent the flow of data between different transformations and
process in the system. The data flow shows logical flow of data, Different notation used in
DFD are:
Function processing
It is represented by Oval. This notation specifies the processing or main transactions.
Data Flow
An arrow line represents it and name of the data is specified by the side of the line as label.
This arrow line is used to indicate data movement.
Data Store
It is represented by one end open rectangle. The databases used in the system are specified by
this notation.
Source or sink
It is represented by a rectangle. It is used for specifying from where data is coming and where
it will reach.

SYSTEM DESIGN
A computer procedure is a series of operation design to manipulate data to produce a output a
computer System. The procedure may be a single program or a series of programs. The
detailed design of the computer procedure follows acceptance by management of an outline
design proposal. The aim is to design procedure at lower level of detail, which will define the
detailed steps to be taken to produce the specified computer output. When complete, this
procedure definition together with data specification reorganizes for programmer from which
the required programs can be written.
Design
Various tools are being used by system analysis to specify computer procedure. Not all of
them are used here to design this project. Some of the most important tools that have been
used are
a. Entity relationship diagram.
b. Input design.
c. Output design
d. Database design.
Input design
Input design is a part of the overall system design, which requires very careful attention.
Often the collection input data is the most expensive process of the system, in term of both
the equipment used and the number of people involved, it is point of most contact for the user
with the computer system; and it is prone to error. If data going into the system is incorrect,
then the processing and output will magnify their errors.
One of the earlier activities of input design is to determine the nature of the input data. this is
done partially in logical system design but it needs to be made more explicit.
Error avoidance and detection

Every effort must be made to ensure that input data remains accurate from the stage at which
it is recorded and documentation to the stage at which the customer accept it. While every
effort is made to avoid errors during the preparation of errors are likely to be present.

The user is free from the anxiety of keeping the uniqueness of the primary key since the
system itself generates the primary key for the users.
As soon as the user keys erroneous data it, the system will not accept the data and provide the
appropriate messages.
Data validation
Computer input procedure is also designed to detect errors in the data at a lower level of
details which is beyond the capability of the control procedures. These are combined with
the input process itself.
The validation procedure must be designed to check each record, data item, and certain
criteria against the field by a system analyst or programmer.
Outside design
The specification of the user requirement is the starting for the appraisal of the detailed
physical design must be done with the light of the continuous user involvement. The normal
procedure is to design the output in detail first and then return to work. The output can be in
the form of operational documents, lengthy reports, and replies to queries or summarizing
graphs.
Output from computer systems are required to provide a permanent copy of the result for
later consultation. Output design can proceed before any data item is yet to be identified and
recorded. There is often a need to provide output at various levels. It is not always desirable
to print or display data as it is held on a computer. The system analyst must make sure that
the system is stored in the output.
In proposed system the user has been provided with many outputs in the form of messages
and alerts so as to help the user enter the correct data.
Report
Reports enhance the application programmer's effort to output the formatted data in a manner
that is practical for the user, 'This also helps create hard copy of valid information.
Architectural design
Architectural design represents the structure of data and program components that are
required to build computer based system. It considers the architectural style that a system
will take, the structure and properties of the component that constitute the system, and the
inter relationship that occurs among all the architectural component of a system.
Although a software engineer can design both and architecture, the job is often allocated to
specialists when large, Complex system are to be built. A database or a data warehouse
designer creates the data architecture of a system. The system architect selects an appropriate

architectural style for the requirements derived during system engineering and software
requirement analysis.
Architectural design begins with data design and the proceeds to the derivation of one or
more Representations of the architectural structural of the system alternative architectural
style or patterns are analyzed to derive the structure that is best suited to customer
requirements and quality attributes. Once an alternative has been selected, the architectural is
elaborated using an architectural design method. An architectural model encompassing data
architectural and program structure is create during architectural design. In addition,
component properties and relationship are described.
Context Diagram
Blood Bank
Administrator Management Database
Low Level DFD
1 level DFD Administrator
Blood Bank Relational

Administrator
Management Database
Login details
Login

High Level DFD
Profile
DBMS Donor Details
Admin Login
Contact Us
Admin Details View Donor
View Blood
Add Donor
Add Blood
Blood Details
Add Stock
View Stock

Database Design
Introduction to database design
Donor Registration
Entry Work
Login Information User name

Basic Information
Name
Confirm Password
Age Blood Group
Gender Date of Birth
Contact Information
State
City
Message
Pin Code
E-mail id
Date of Birth
Mobile no

Database design
Introduction to database
Data base design is concern with the data focus from the perspective of the system designer.
The end product is called a database, a technical blueprint of database.
Database design translates the data model that were developed for the system users during the
definition phase in to data structure supported by the chosen database technology. The goals
of database design are as follows:
a) Database should provide for the efficient storage, update and retrieval of data.
b) A database should be reliable – the storage data should have high integrity to promote
user in that data.
c) A database should be adaptable and scalable to new and unforeseen requirements and
applications.
Database design
Table created
Donor Registration Table
Field Type Null Key Default Extra

Username varchar(10) YES NULL
Password varchar(10) YES NULL
Name varchar(10) YES NULL
Age varchar(10) YES NULL
Gender varchar(10) YES NULL
DOB date YES NULL
Blood Group varchar(20) YES NULL
State varchar(10) YES NULL
City varchar(10) YES NULL
Pin Code int(10) YES NULL
Mobile no int(10) YES NULL
Email ID varchar(20) YES NULL

CHAPTER-5
CODING

Coding
Login Page
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Blood Bank Management System</title>

<link rel="stylesheet" type="text/css" href="./css/style.css" />
<link rel="stylesheet" type="text/css" href="./css/ddsmoothmenu.css" />
<link rel="stylesheet" type="text/css" href="./css/contentslider.css" />
<link rel="stylesheet" type="text/css" href="./css/jquery.fancybox-1.3.1.css" />
<link rel="stylesheet" type="text/css" href="./css/slider.css" />
<link rel="stylesheet" type="text/css" href="./css/jquery-ui.css">

<script type="text/javascript" src="js/jquery-1.10.2.js"></script>
<script type="text/javascript" src="./js/validation.js"></script>
<script type="text/javascript" src="./js/jquery.easing.1.2.js"></script>
<script type="text/javascript" src="./js/jquery.anythingslider.js"></script>
<script type="text/javascript" src="./js/anythingslider.js"></script>
<script type="text/javascript" src="./js/animatedcollapse.js"></script>
<script type="text/javascript" src="./js/ddsmoothmenu.js"></script>
<script type="text/javascript" src="./js/menu.js"></script>
<script type="text/javascript" src="./js/contentslider.js"></script>
<script type="text/javascript" src="./js/ddaccordion.js"></script>
<script type="text/javascript" src="./js/acrodin.js"></script>
<script type="text/javascript" src="./js/jquery.fancybox-1.3.1.js"></script>
<script type="text/javascript" src="./js/lightbox.js"></script>
<script type="text/javascript" src="./js/menu-collapsed.js"></script>
<script type="text/javascript" src="./js/cufon-yui.js"></script>
<script type="text/javascript" src="./js/trebuchet_ms_400-trebuchet_ms_700-
trebuchet_ms_italic_700-trebuchet_ms_italic_400.font.js"></script>
<script type="text/javascript" src="./js/cufon.js"></script>
<script type="text/javascript" src="./js/jquery.validate.js"></script>
<script type="text/javascript" src="js/jquery-ui.js"></script>
</head>
<body>
<div id="wrapper_sec">
<div id="masthead">
<div class="logo">

<a href="./index.php" class="logo-custom">Blood Bank Management System</a>

</div>
<div class="slogan"></div>
<div class="clear"></div>
<div class="navigation">
<div id="smoothmenu1" class="ddsmoothmenu">
<ul>
<li><a href="./index.php">Home</a>
</li>
<li><a href="./about.php">About Us</a></li>
<li><a href="./login.php">Login</a></li>
<li><a href="./contact.php">Contact Us</a></li>
</ul>
<br style="clear: left" />
</div>
</div>
</div>
<div class="crumb">
</div>
<div id="content_sec">
<div class="col1">
<div class="contact">
<h4 class="heading colr">Login To Your Account</h4>
<div class='msg'></div>
<form action="lib/login.php" method="post" name="frm_car">
<ul class="forms">
<li class="txt">Username</li>
<li class="inputfield"><input name="user_user" type="text" class="bar" required /></li>
</ul>
<ul class="forms">
<li class="txt">Password</li>
<li class="inputfield"><input name="user_password" type="password" class="bar"
required /></li>
</ul>
<ul class="forms">
<li class="txt"> </li>
<li class="textfield"><input type="submit" value="Submit" class="simplebtn"></li>
<li class="textfield"><input type="reset" value="Reset" class="resetbtn"></li>
</ul>
<input type="hidden" name="act" value="check_login">
</form>
</div>
</div>

<div class="col2">
<div class="contactfinder">
<h4 class="heading colr">Advertisemet</h4>
<div><img src="images/save_1.jpg" style="width: 250px"></div><br>
</div>
</div>
</div>
<div id="footer">
<ul class="right">
<li>© Blood Bank Management System</li>
</ul>
</div>
</body>
</html>
Dashboard
<head>


</head>
<body>
<div id="masthead">
<div class="logo">
</div>
<ul>
</li>
<li><a href="./login-home.php">Dashboard</a></li>
<li><a href="#">Administration</a>
<ul>
<li><a href="doner.php">Add Blood Doner</a></li>
<li><a href="blood.php">Add Blood</a></li>
<li><a href="stock.php">Add Blood Stock</a></li>
</ul>
</li>
<li><a href="#">Reports</a>
<ul>
<li><a href="doner-report.php">Doners Report</a></li>
<li><a href="blood-report.php">Blood Report</a></li>
<li><a href="stock-report.php">Stock Report</a></li>
</ul>
</li>
<li><a href="change-password.php">Change Password</a></li>
<li><a href="./lib/login.php?act=logout">Logout</a></li>
</ul>
</div>
</div>
</div>

<div class="crumb">
</div>
<div class="col1">
<h4 class="heading colr">Welcome to Blood Bank Management System</h4>
<div class='msg'></div>
<ul class='login-home-listing'>
</ul>
</div>
</div>
<div class="col2">
</div>
</div>
</div>
<div id="footer">
<ul class="right">
</ul>
</div>
</body>
</html>
Donor Registration
<head>


</head>
<body>
<div id="masthead">
<div class="logo">
</div>
<ul>
</li>

<ul>
</ul>
</li>
<ul>
</ul>
</li>
</ul>
</div>
</div>
</div>
<script>
jQuery(function() {
jQuery( "#doner_dob" ).datepicker({
changeMonth: true,
changeYear: true,
yearRange: "-65:-10",
dateFormat: 'd MM,yy'
});
jQuery('#frm_doner').validate({
rules: {
doner_confirm_password: {
equalTo: '#doner_password'
}
}
});
});
function validateForm(obj) {
if(validateEmail(obj.doner_email.value))
return true;
jQuery('#error-msg').show();
return false;
}
</script>
<div class="crumb">

</div>
<div class="col1">
<h4 class="heading colr">Doner Registration</h4>
<div class="msg" style="display:none" id="error-msg">Enter valid EmailID !!!</div>
<form action="lib/doner.php" enctype="multipart/form-data" method="post"
name="frm_doner" onsubmit="return validateForm(this)">
<ul class="forms">
<li class="txt">Name</li>
<li class="inputfield"><input name="doner_name" type="text" class="bar" required
value=""/></li>
</ul>
<ul class="forms">
<li class="txt">Blood Group</li>
<li class="inputfield"><input name="doner_blood_group" type="text" class="bar" required
value=""/></li>
</ul>
<ul class="forms">
<li class="txt">Mobile</li>
<li class="inputfield"><input name="doner_mobile" type="number" size="10"
maxlength="10" class="bar" required value=""/></li>
</ul>
<ul class="forms">
<li class="txt">Email</li>
<li class="inputfield"><input name="doner_email" id="doner_email" type="text"
class="bar" required value="" onchange="validateEmail(this)" /></li>
</ul>
<ul class="forms">
<li class="txt">Date of Birth</li>
<li class="inputfield"><input name="doner_dob" id="doner_dob" type="text" class="bar"
required value=""/></li>
</ul>
<ul class="forms">
<li class="txt">Address Line 1</li>
<li class="inputfield"><input name="doner_add1" type="text" class="bar" required
value=""/></li>
</ul>
<ul class="forms">
<li class="txt">Address Line 2</li>
<li class="inputfield"><input name="doner_add2" type="text" class="bar" required
value=""/></li>
</ul>
<ul class="forms">

<li class="txt">City</li>
<li class="inputfield">
<select name="doner_city" class="bar" required/>
<option value=''>Please Select</option><option value='1'>Bangalore</option><option
value='2'>Varanasi</option> </select>
</li>
</ul>
<ul class="forms">
<li class="txt">State</li>
<select name="doner_state" class="bar" required/>
<option value=''>Please Select</option><option value='1'>Karnataka</option><option
value='2'>MP</option> </select>
</li>
</ul>
<ul class="forms">
<li class="txt">Country</li>
<select name="doner_country" class="bar" required/>
<option value=''>Please Select</option><option value='1'>India</option><option
value='2'>USA</option> </select>
</li>
</ul>
<ul class="forms">
<li class="txt">Photo</li>
<li class="inputfield"><input name="doner_image" type="file" class="bar"/></li>
</ul>
<ul class="forms">
</ul>
<input type="hidden" name="act" value="save_doner">
<input type="hidden" name="avail_image" value="">
<input type="hidden" name="doner_id" value="">
</form>
</div>
</div>
<div class="col2">
</div>
<div class="col2">

</div>
</div>
</div>
<script>
jQuery( "#doner_level_id" ).val(3);
jQuery( "#doner_level" ).hide();
</script>
<div id="footer">
<ul class="right">
</ul>
</div>
</body>
</html>
Add Blood
<head>


</head>
<body>
<div id="masthead">
<div class="logo">
</div>
<ul>
</li>
<ul>
</ul>
</li>
<ul>
</ul>
</li>
</ul>
</div>
</div>
</div>

<div class="crumb">
</div>
<div class="col1">
<h4 class="heading colr">Blood Entry Form</h4>
<form action="lib/blood.php" enctype="multipart/form-data" method="post"
name="frm_blood">
<ul class="forms">
<li class="txt">Blood Type</li>
<select name="blood_type_id" class="bar" required/>
<option value=''>Please Select</option><option value='1'>A +ve</option><option
value='4'>A -ve</option><option value='3'>AB +ve</option><option value='2'>B
+ve</option><option value='5'>B -ve</option><option value='6'>O +ve</option><option
value='7'>O -ve</option> </select>
</li>
</ul>
<ul class="forms">
<li class="txt">Cost</li>
<li class="inputfield"><input name="blood_price_per_unit" id="blood_price_per_unit"
type="text" class="bar" required value=""/></li>
</ul>
<ul class="forms">
<li class="txt">Description</li>
<li class="textfield"><textarea name="blood_description" cols="" rows="6"
required></textarea></li>
</ul>
<ul class="forms">
</ul>
<input type="hidden" name="act" value="save_blood">
<input type="hidden" name="blood_id" value="">
</form>
</div>
</div>
<div class="col2">
</div>

</div>
</div>
<div id="footer">
<ul class="right">
</ul>
</div>
</body>
</html>
Add Blood Stock

<head>

</head>
<body>
<div id="masthead">
<div class="logo">
</div>
<ul>
</li>
<ul>
</ul>
</li>
<ul>
</ul>
</li>
</ul>
</div>
</div>
</div>
<div class="crumb">
</div>

<div class="col1">
<h4 class="heading colr">Stock Entry Form</h4>
<form action="lib/stock.php" enctype="multipart/form-data" method="post"
name="frm_stock">
<ul class="forms">
<li class="txt">Stock Type</li>
<select name="stock_blood_id" class="bar" required/>
<option value=''>Please Select</option><option value='1'>A +ve</option><option
value='4'>A -ve</option><option value='3'>AB +ve</option><option value='2'>B
+ve</option><option value='5'>B -ve</option><option value='6'>O +ve</option><option
value='7'>O -ve</option> </select>
</li>
</ul>
<ul class="forms">
<li class="txt">Units</li>
<li class="inputfield"><input name="stock_number" id="stock_number" type="text"
class="bar" required value=""/></li>
</ul>
<ul class="forms">
<li class="txt">Date</li>
<li class="inputfield"><input name="stock_date" id="stock_date" type="text" class="bar"
required value=""/></li>
</ul>
<ul class="forms">
<li class="txt">Description</li>
<li class="textfield"><textarea name="stock_description" cols="" rows="6"
required></textarea></li>
</ul>
<ul class="forms">
</ul>
<input type="hidden" name="act" value="save_stock">
<input type="hidden" name="stock_id" value="">
</form>
</div>
</div>
<div class="col2">

</div>
</div>
</div>
<div id="footer">
<ul class="right">
</ul>
</div>
</body>
</html>
Donor Report
<head>


</head>
<body>
<div id="masthead">
<div class="logo">
</div>
<ul>
</li>
<ul>
</ul>
</li>
<ul>
</ul>
</li>
</ul>
</div>
</div>
</div>
<script>
function delete_doner(doner_id)
{

if(confirm("Do you want to delete the doner?"))

{
this.document.frm_doner.doner_id.value=doner_id;
this.document.frm_doner.act.value="delete_doner";
this.document.frm_doner.submit();
}
}
</script>
<div class="crumb">
</div>
<div class="col1" style="width:100%">
<h4 class="heading colr">Doner Reports</h4>
<form name="frm_doner" action="lib/doner.php" method="post">
<div class="static">
<table style="width:100%">
<tbody>
<tr class="tablehead bold">
<td scope="col">Sr. No.</td>
<td scope="col">Image</td>
<td scope="col">Name</td>
<td scope="col">Mobile</td>
<td scope="col">Email</td>
<td scope="col">Group</td>
<td scope="col">Date Of Birth</td>
<td scope="col">Action</td>
</tr>
<tr>
<td style="text-align:center; font-weight:bold;">1</td>
<td><img src="http://127.0.0.1/blood_bank_system/uploads/jobin.jpg" style="heigh:50px;
width:50px"></td>
<td>Jobin Reji</td>
<td>7868062222</td>
<td>biuafhuod@jgwhs.srgsr</td>
<td>O+</td>
<td>14 August,1999</td>
<td style="text-align:center"><a href="doner.php?doner_id=3">Edit</a> | <a
href="Javascript:delete_doner(3)">Delete</a> </td>
</tr>
<tr>
<td style="text-align:center; font-weight:bold;">2</td>
<td><img src="http://127.0.0.1/blood_bank_system/uploads/avatar.gif" style="heigh:50px;
width:50px"></td>

<td>MAYISHA NAZAR</td>
<td>7889671593</td>
<td>MAHI@GMAIL.COM</td>
<td>O+</td>
<td>13 November,1999</td>
<td style="text-align:center"><a href="doner.php?doner_id=5">Edit</a> | <a
href="Javascript:delete_doner(5)">Delete</a> </td>
</tr>
</tbody>
</table>
</div>
<input type="hidden" name="act" />
<input type="hidden" name="doner_id" />
</form>
</div>
</div>
</div>
<div id="footer">
<ul class="right">
</ul>
</div>
</body>
</html>

CHAPTER – 6
TESTING

TESTING
Testing is the process of evaluating a system or its component(s) with the intent to find that
whether it satisfies the specified requirements or not. This activity results in the actual,
expected and difference between their results. In simple words testing is executing a system
in order to identity any gaps, errors or missing requirements in contrary to the actual desire or
requirements.
It depends on the process and the associated stakeholders of the project(s). In the IT industry,
large companies have a team with responsibilities to evaluate the developed software in the
context of the given requirements. Moreover, developers also conduct testing which is called
Unit Testing. In most cases, following professionals are involved in testing of a system within
their respective capacities.
 Software Tester.
 Software Developer.
 Project Lead/Manager.
 End User
Different companies have difference designations for people who test the software on the
basis of their experience and knowledge such as Software Tester, Software Quality
Assurance Engineer, and QA Analyst etc.
it is not possible to test the software at any time during its cycle. The next two sections state
when testing should be started and when to end it during the SDLC
WHITE BOX TESTING

White box testing is when the tester has access to the internal data structures and algorithms
including the code that implement these.
Types of white box testing

The following types of white box testing exist:
 API testing (application programming interface) testing of the application using

public and private APls.
 Code coverage creating tests to satisfy some criteria of code coverage (eg. the test
designer can create tests to cause all statements in the program to be executed at least
once)
 Fault injection methods improving the coverage of a test by introducing faults to test
code paths
 Mutation testing methods
 Static testing White box testing includes all static testing.
BLACK BOX TESTING

Black box testing treats the software as a "black box"-without any knowledge of internal
implementation. Black box testing methods include: equivalence partitioning, boundary value
analysis, all-pairs testing, fuzz testing, model-based testing. exploratory testing and
specification- based testing Specification-based testing:
Specification-based testing aims to test the functionality of software according to the

applicable requirements.1221 Thus, the tester inputs data into, and only sees the output from,
the test object. This level of testing usually requires thorough test cases to be provided to the
tester, who then can simply verify that for a given input, the output value (or behavior), either
"is" or "is not" the same as the expected value specified in the test case Specification-based
testing is necessary, but it is insufficient to guard against certain risks.
GREY BOX TESTING

Grey box testing (American spelling: gray box testing) involves having knowledge of internal
data structures and algorithms for purposes of designing the test cases, but testing at the user,
or black-box level. Manipulating input data and formatting output do not qualify as grey box,
because the input and output are clearly outside of the "black-box" that we are calling the
system under test. This distinction is particularly important when conducting integration
testing between two modules of code written by two different developers, where only the
interfaces are exposed for test. However, modifying a data repository does qualify as grey
box, as the user would not normally be able to change the data outside of the system under
test. Grey box testing may also Include reverse engineering to determine, for instance,
boundary values or error messages.
UNIT TESTING
Unit testing refers to tests that verify the functionality of a specific section of code, usually at
the function level. In an object-oriented environment, this is usually at the class level, and the
minimal unit tests include the constructors and destructors.
These types of tests are usually written by developers as they work on code (white-
box style), to ensure that the specific function is working as expected. One function might
have multiple tests, to catch corner cases or other branches in the code. Unit testing alone
cannot verify the functionality of piece of software, but rather is used to assure that the
building blocks the software uses work independently of each other.
unit testing is also called component testing.
INTEGRATION TESTING
Integration testing is any type of software testing that seeks to verify the interfaces between
components against a software design. Software components may be integrated in an iterative
way or all together ("big hang"). Normally the former is considered a better practice since it
allows interface issues to be localized more quickly and fixed.

Integration testing works to expose defects in the interfaces and interaction between
integrated components (modules). Progressively larger groups of tested software components
corresponding to elements of the architectural design are integrated and tested until the
software works as a system.
VALIDATION TESTING
The main aim of this testing is to verify that the software system does what it was designed
for. The system was tested to ensure that the purpose of automating the Blood bank was
fulfilled. Blood bank management system testing was carried out to ensure the validity of the
system.
SYSTEM TESTING
The idea of applying this testing strategy was to put the system to a series of tests to ensure
that it performed well and exactly same under all condition.
The test that the system was put were
Recovery Testing
Performance testing
The tests were made on each form for its correctness of accepting the data and storing the
data into the respective tables in the desired form of data type. The algorithm was tested with
the test data t and then with the real data. The tests were made for all types of constraints. The
tests were done in presence of the user so that he/she is familiar with the system that is going
to be introduced, During the testing each objective of the system of the system was tested and
found to be working correctly.

CHAPTER-7
CONCLUTION

Conclusion
In the area of communication and revolution, information has been an inevitable component.
Effecting Computing capabilities are therefore utilized. The availability of required
information at the press of a button is something favourable and therefore computers are used
for purpose. Thus, way of potential taping is achieved.
The project “BLOOD BANK MANAGEMENT SYSTEM” after being tested was
found to be achieved what is meant for. The system is found to be 100% error free and ready
for implementation. Any work may not be always perfect. There may be any errors or
shortcomings in this work. We have taken at most care to ensure that the project works
perfectly.
The system has been designed in such a way that it can be modified with very little
effort which such a need arises in the future, as it follows the struts framework. The system
has been found to work efficiently and effectively. Due to its higher user friendliness, others
may use these documents as a prototype for developing similar application.
The developed software is tested with sample data and outputs obtained in according
to the requirement. Though it could not be claimed that ours is an ideal project, it will meet
the primary requirements of the concern. Even though I have tried my level best to make it a
dream project, due to time constrains I could not add more facilities to it. So, the projects
have to be improved by having modifications as and when the necessity arises in due course.
The project BLOOD BANK MANAGEMENT SYSTEM is for computerizing the working
in a local blood bank in the town. The software care of all requirements of a blood bank and
is capable to provide easy and effective storage of information related to the blood bank
functioning and its employee’s details.

CHAPTER-8
FUTURE ENHANCEMENT

Future Enhancement
This project has been developed in very short period of time and have been taken so that this
project is very efficient in its execution there still exists some scope of improvement in our
project. The following are the some of the enhancement that can be added incorporate into
the project.
Help file for work direction can be included. The system as of now does not support any help
facility for the user of the system. A help menu can be provided with a special function key
and help command in main page itself. Help can be either introduced in a separate window, a
reference to a printed manual or one or two line suggestion produced in a fixed screen
location.
Application of the project can be done more attractively. Database management and stock
maintenance module can be added which helps the administrator. This project can also be
modified into a client server application. More security measures can be taken.
Another additive to this project would be regarding the means and channels of
communication through which a donor receives relevant information. The first idea would be
to send an e-mail to the donor on the same e-mail id which was used by him/her to register on
the portal. But then a situation could arrive that the donor is not near to the computer or if
he/she uses a smart phone to access internet the accessibility may get affected as per the
geographic location of the donor and hence the e-mail would not be accessed in desirable
time. So, to conquer the situation we would us the simple and verified method of texting the
door which wouldn’t require much of the resources besides a very basic cell phone that can
connect to cellular network and the relevant information would get passed to the donor in the
stipulated amount of time.

CHAPTER-9
BIBLIOGRAPHY
Bibliography

Books
1. PHP Reference book
2. MySQL Complete reference
Websites
1. www.Google.com
2. www.Wikipedia.com
3. www.slideshare.com
4. www.GoogleImage.com
5. www.Youtube.com

CHAPTER-10
USER MANUAL
User Manual

Front page
Login Page
Dashboard

Add Donor
Add Blood

Blood Stock
Donor Report

Blood Report
Stock Report

Change Password
Contact Us

Documentation For All Projects 2020

Uploaded by

Copyright:

Available Formats

You might also like

Documentation For All Projects 2020

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Documentation For All Projects 2020

Uploaded by

Copyright:

Available Formats

Blood Bank Management System Page |1

Acharya Institutes of Graduate Studies Department of Computer Application

Blood is needed every minute:

a) To replace blood lost because of accidents or diseases.

Acharya Institutes of Graduate Studies Department of Computer Application

Acharya Institutes of Graduate Studies Department of Computer Application

Acharya Institutes of Graduate Studies Department of Computer Application

Drawback of Existing System

b. Updating and Retrieval task are very tedious.

c. More manual work.

d. Easy Customer service is difficult.

e. Lot of paper work result in lot of confusion.

f. Data is not readily available in an emergency situation.

Acharya Institutes of Graduate Studies Department of Computer Application

The main objective the proposed system can be enumerated as follows:

b. Donor search is possible

c. Matching blood group can be found easily form the table.

d. Employee details and salary generation become easy.

e. Stock details are easily available.

Merits of proposed system

Overview of languages used

Acharya Institutes of Graduate Studies Department of Computer Application

How MYSQL works

Acharya Institutes of Graduate Studies Department of Computer Application

Acharya Institutes of Graduate Studies Department of Computer Application

Acharya Institutes of Graduate Studies Department of Computer Application

A well-designed, well-written SRS accomplishes four major goals:

Acharya Institutes of Graduate Studies Department of Computer Application

Front End : HTML, CSS, JavaScript, PHP

Back End : MY SQL

Acharya Institutes of Graduate Studies Department of Computer Application

PROCESSOR : Intel core

HARD DISK : 20GB or more

MONITOR : CRT &LED

KEYWORD : Normal or Multimedia

MOUSE : Compatible mouse

MODEM : ADLS, DLS

ADMINISTRATOR MODULE FUNCTIONAL REQUIRMENTS:

Acharya Institutes of Graduate Studies Department of Computer Application

a. Back-up option for backing up the database etc.

Maintainability is the ease with which a program/specification can be corrected if an error

Performance is measured in terms of the output provided by the application. Requirements

Acharya Institutes of Graduate Studies Department of Computer Application

Acharya Institutes of Graduate Studies Department of Computer Application

Data flow diagram notation

Acharya Institutes of Graduate Studies Department of Computer Application

a. Entity relationship diagram.

Error avoidance and detection

Acharya Institutes of Graduate Studies Department of Computer Application

Acharya Institutes of Graduate Studies Department of Computer Application

Low Level DFD

1 level DFD Administrator

Blood Bank Relational

Acharya Institutes of Graduate Studies Department of Computer Application

High Level DFD

Admin Details View Donor

Acharya Institutes of Graduate Studies Department of Computer Application

Introduction to database design