Blood Management System

SYNOPSIS
Synopsis is a general documentation tool. By means of a modular structure, it

adapts to different styles of embedded documentation, different programming
language and various output formats. It scales well with the size of the project by
allowing processing to be controlled by making files.
The website is designed to provide information about “BLOOD DONATION

SYSTEM”.
The website contains both static and dynamic pages. Dynamic pages in the website
cover all the information required by needy person about Blood or Blood Bank.
It also provides brief details of the blood donor or blood group available.
Manually creating a report takes hours but this website is built-in to allow creating
different report in a few clicks and of course its required data entry operators.
Yet this data if structured properly can be used for many different reports.
Project is developed under the windows 7 (ultimate) operating system with visual
studio and Microsoft SQL server as backend.
Modules of the project
Administration:
In this module the Administrator has the privileges to add all the Blood Groups,
Blood Type, and Organization. He can search all the info about the Organization,
Donor.
 HOME PAGE
 DONOR REGISTRATION
 LOGIN
 ORGANIZATION DETAILS
 SEARCH
 CONTACT US
 ABOUT
1
HOME:
This page introduces you to the webpage and about blood donation
DONOR REGISTRATION
This is the registration of the donors.
ORGANISATION DETAILS
This page is registration of the organization details.
LOGIN
This page is regarding donor registration.
SERACH
To search the required blood group.
CONTACT US:
This page takes the input of the customer with the name, contact number.
ABOUT US
This about the Blood Donation System.
2
INTRODUCTION
1.1. About the organization
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.
1.2. Objectives of the proposed
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 been planned. Using the constructs of MS-SQL Server and all the user
interfaces have been designed using the ASP.Net technologies.
3
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 was crosschecked at all the relevant stages. The user level accessibility
has been restricted into two zones namely.
4
SYSTEM STDUY
System study is an initial step for developing any new application software. A
report will be prepared on the basis of a study conducted on the current
process. Additional requirement and modifications are recommended for the
proposed system. This phase software development lays foundation for a
detailed system analysis and design phase of proposed system. In practice,
the system study is done in one levels of user. In this Administration level the
system done which help in user Administration can search a patient‟s record
by his/her name or their registration date or identifying the scope of the
system.
2.1 Existing System
 Cannot Upload and Download the latest updates.

 No use of Web Services and .
 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
2.2. 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.
2.3 TOOLS & TECHNIQUES USED TO COMPLETE THE STUDY
 Firstly we the associates of this project had an interaction with the

general public and donors.
5
 Walk through into existing system for more details.
 Collecting the old details for the new proposed system
 Discussed with my Project Guide for further clarification to continue
the project work.
6
SYSTEM ANALYSIS
3.1 Problem Analysis
 Problem analysis is the process of understanding real - world problems

and user‟s needs and proposing solution to meet those needs.
 The goal of problem analysis is to gain a better understanding, before

development Begins, of the problem being solved
 To identify the root cause, or the problem behind the problem, as the people
directly involved
 Identifying the actors on the system is a key step in problem analysis
3.2 Feasibility Study
A project feasibility study is a comprehensive report that examines in detail

the five Frames of analyses of a project. A feasibility study aims to objectively
and rationally Uncover the strengths and weakness of an existing business
or proposed venture, Opportunities and threats present in the natural environment ,
the resources required To carry through, and ultimately the prospects for success.
The following are the areas for Feasibility
 Technical
 Resource
 Legal
 Financial
Technical Feasibility
This assessment is based on an outline design of system requirements, to

determine Whether the company has the technical expertise to handle
completion of the project. The technical fesibility assessment is focused on gaining
an understanding of the present technical resources of the organization and
7
their applicability to the expected needs of The proposed system. It is an evaluation
of the hardware and software.
Resource Feasibility
Describe how much time is available to build the new system, when it can be built,
whether it interferes with normal business operations, type and amount of resources
required, dependencies, and development procedures with company revenue
prospectus.
Legal Feasibility
Determines whether the proposed system conflicts with legal requirements, e.g.,
data Processing system must comply with the local data protection regulations and if
the proposed System is acceptable in accord -acne to the laws of the land
Financial Feasibility
 Time Based
Contrast to the manual system management can generate any report just by single
click. In Manual system it is too difficult to maintain historical data which become
easier in this system. Time consumed to add new records or to view the reports is
very less compared to manual ystem.so this project is feasible in this point of view.
 Cost Based
No special investment need to manage the tool. No specific training is required for
employees to use the tool. Investment requires only once at the time of installation.
The software used in this project is freeware so the cost of developing the tool is
minimal and hence the overall cost.
3.3 Tools and Environment Used
Front End
8
 Visual studio 2010
Back End
 My SQL 2008
 INTRODUTION ON ASP.NET
ASP.NET is a web application framework developed and marketed by Microsoft

to allow programmer to build dynamic web site, web application and web
services .it was first released in January 2002 with version 1.0 of the .NET
framework, and is the successor to Microsoft‟s active server page (ASP)
technology. ASP.NET is built the common language runtime (CLR),
Allowing programmer to write ASP.NET code using any supported .NET language.
In ASP.NET support with the following list:-
 Better language support

 Programmable controls
 Events –drive programming
 XML-based components
 User authentications ,with accounts and roles
 Higher scalability
 Increased performance-compiled code
 Easier configuration and deployment
 Not fully asp compatible
Language support
 ASP.NET uses ADO.NET

 ASP.NET support full visual basics, not VB script.
 ASP.NET support C#(C sharp)and C++
 ASP.NET support JavaScript.
9
ASP.NET controls
ASP.NET controls a large set of HTML, controls, almost all the HTML elements on a
page can be defined as ASP.NET control object that can be controlled by
scripts.ASP.NET also contain a new set of object-oriented input controls, like
programmable list –boxes and validation controls.
ASP.NET components
ASP.NET components are heavily based on XML. Like the new AD rotator, that uses
XML to store advertisement and configuration.
User Authentication
ASP.NET support form-based user authentication, cookie management, and

automatic redirecting of unauthorized login.
High scalability
Much has been done with the ASP.NET to provide greater scalability.
Server-to-server communication has been greatly enhanced, making it possible to

scale a communication over several servers.
Compiled code
Much has been done with ASP.NET page on the server will compile the ASP.NET
code and keep a cached copy in memory .The result of this is greatly increased
performance.
Easy configuration
Configuration of ASP.NET is done with plain text files. Configuration files can be
uploaded or changed while the application is running. No need to restart the server.
No more Meta base or registry puzzle.
Easy deployment
10
No more server restart to display or replace compiled code. ASP.NET simply
redirects all new requests to the new code.
Compatibility
ASP.NET is not fully with easier version of ASP, so most of the old ASP code will
need to change some ASP.NET. Overcome this problem, ASP.NET uses a new file
extension “apsx”. This will make ASP.NET application able to run side by side with
standard ASP application on the same server.
 C#.NET
ADO.NET OVERVIEW
ADO.NET is an evolution of the ADO data access model that directly addresses
user requirements for developing scalable applications. It was designed specifically
for the web with scalability, statelessness, and XML in mind.
ADO.NET uses some ADO objects, such as the Connection and Command objects,
and also introduces new objects. Key new ADO.NET objects include the Datasets,
Data Reader, and Data Adapter.
The important distinction between this evolved stage of ADO.NET and

previous data architectures is that there exists an object -- the Datasets -- that is
separate and distinct from any data stores. Because of that, the Datasets functions as
a standalone entity. You can think of the Datasets as an always disconnected record
set that knows nothing about the source or destination of the data it contains. Inside
a Datasets, much like in a database, there are tables, columns, relationships,
constraints, views, and so forth. A Data Adapter is the object that connects to the
database to fill the Datasets. Then, it connects back to the database to update the
data there, based on operations performed while the Datasets held the data. In the
past, data processing has been primarily connection-based. Now, in an effort to
make multi-tiered apps more efficient, data processing is turning to a message-based
approach that revolves around chunks of information. At the center of this approach
is the data Adapter, which provides a bridge to retrieve and save data between a
11
Datasets and its source data store. It accomplishes this by means of requests to the
appropriate SQL commands made against the data store.
 Connections. For connection to and managing transactions against a

database.
 Commands. For issuing SQL commands against a database.
 Data Readers. For reading a forward-only stream of data records from a SQL
Server data source.
 Datasets. For storing, remoting and programming against flat data, XML data
and relational data.
 Data Adapters. For pushing data into a Datasets, and reconciling data against
a database.
Connections:
Connections are used to 'talk to' databases, and are represented by provider-
specific classes such as SqlConnection. Commands travel over connections and
result sets are returned in the form of streams which can be read by a Data Reader
object, or pushed into a Dataset object.
Commands:
Commands contain the information that is submitted to a database, and are
represented by provider-specific classes such as SqlCommand. A command can be a
stored procedure call, an UPDATE statement, or a statement that returns results.
You can also use input and output parameters, and return values as part of your
command syntax. The example below shows how to issue an INSERT statement
against the North wind database.
Data Readers:
The Data Reader object is somewhat synonymous with a read-only/forward-only
cursor over data. The Data Reader API supports flat as well as hierarchical data. A
Data Reader object is returned after executing a command against a database. The
format of the returned Data Reader object is different from a record set. For
example, you might use the Data Reader to show the results of a search list in a web
page.
12
 SQL SERVER
A database management, or DBMS, gives the user access to their data and
helps them transform the data into information. Such database management systems
include dBase, paradox, IMS, SQL Server and SQL Server. These systems allow
users to create, update and extract information from their database.
A database is a structured collection of data. Data refers to the characteristics
of people, things and events. SQL Server stores each data item in its own fields. In
SQL Server, the fields relating to a particular person, thing or event are bundled
together to form a single complete unit of data, called a record (it can also be referred
to as raw or an occurrence). Each record is made up of a number of fields. No two
fields in a record can have the same field name.
During an SQL Server Database design project, the analysis of your business
needs identifies all the fields or attributes of interest. If your business needs change
over time, you define any additional fields or change the definition of existing fields.
SQL Server Tables

SQL Server stores records relating to each other in a table. Different tables are
created for the various groups of information. Related tables are grouped together to form a
database.
Primary Key
Every table in SQL Server has a field or a combination of fields that uniquely
identifies each record in the table. The Unique identifier is called the Primary Key,
Or simply the key. The primary key provides the means to distinguish one record
from all other in a table. It allows the user and the database system to identify,
locate and refer to one particular record in the database.
Relational Database
Sometimes all the information of interest to a business operation can be stored
in one table. SQL Server makes it very easy to link the data in multiple tables.
Matching an employee to the department in which they work is one example. This
is what makes SQL Server a relational database management system, or RDBMS. It
13
stores data in two or more tables and enables you to define relationships between
the tables and enables you to define relationships between the tables.
Foreign Key
When a field is one table matches the primary key of another field is referred
to as a foreign key. A foreign key is a field or a group of fields in one table whose
values match those of the primary key of another table.
Referential Integrity
Not only does SQL Server allow you to link multiple tables, it also maintains
consistency between them. Ensuring that the data among related tables is correctly
matched is referred to as maintaining referential integrity.
3.4 HARDWARE CONFIGURATION
 Processor : INTEL i5 CORE

 CPU speed : 2.50 GHZ
 RAM : 2GB
 Hard Disk : 500GB
 Monitor : Laptop
 Keys : 109 keys
 Operating system : Windows 7
SOFTWARE REQUIREMENTS
 Front end : .net with c#

 Back end : MS MY SQL SERVER 2008
14
SYSTEM DESIGN
System design is included in order to cover the user‟s necessity and the detailed
analysis of the system .It is the most crucial phase in the development of a system
.Usually, the design proceeds in two stages:
 Preliminary or general design

 Structured or detailed design
Preliminary or general design:-
At this stage, new features of the system are specified. Estimation of costs for
implementing these features & the benefits to be accessed are carried out. If the
project considered to be feasible, then the next stage of detailed design is processed.
Structured or detailed design:-
In it, computer oriented work begins in earnest .At this level, the design of the
system becomes more structured. Structured design is a blue print of a computer
system solution to a given problem having the same components & inter-
relationship among the same components as the original problem.
SYSTEM DIAGRAM
REPORT
INPUT
PROCESSING
DISPALY
DATABASE
15
4.1 Data Flow Diagrams (DFD)
Data flow diagram are directed graphs in which the nodes specify processing
activities and the arcs specify data items transmitted between processing nodes.
The data flow diagrams that are used for the design of proposed system are
given below:
Data flow diagram symbols:
- Source or Destination of data
- Data flow
- process
- Data storage
Constructing A DFD:
Several rules of thumb are used in drawing DFD‟S:
1. Process should be named and numbered for an easy reference. Each name
should be representative of the process.
2. The direction of flow is from top to bottom and from left to right. Data
traditionally flow from source to the destination although they may flow back to
16
the source. One way to indicate this is to draw long flow line back to a source.
An alternative way is to repeat the source symbol as a destination. Since it is used
more than once in the DFD it is marked with a short diagonal.
3. When a process is exploded into lower level details, they are numbered.
4. The names of data stores and destinations are written in capital letters. Process
and dataflow names have the first letter of each work capitalized.
A DFD typically shows the minimum contents of data store. Each data store should
contain all the data elements that flow in and out. Questionnaires should contain all
the data elements that flow in and out. Missing interfaces redundancies and like is
then accounted for often through interviews.
SAILENT FEATURES OF DFD’S
1. The DFD shows flow of data, not of control loops and decision are controlled
considerations do not appear on a DFD.
2. The DFD does not indicate the time factor involved in any process whether the
dataflow take place daily, weekly, monthly or yearly.
3. The sequence of events is not brought out on the DFD.
TYPES OF DATA FLOW DIAGRAMS
1. Current Physical
2. Current Logical
3. New Logical
4. New Physical
CURRENT PHYSICAL:
In Current Physical DFD process label include the name of people or their positions
or the names of computer systems that might provide some of the overall system-
processing label includes an identification of the technology used to process the data.
17
Similarly data flows and data stores are often labels with the names of the actual
physical media on which data are stored such as file folders, computer files, business
forms or computer tapes.
CURRENT LOGICAL:
The physical aspects at the system are removed as much as possible so that the
current system is reduced to its essence to the data and the processors that transform
them regardless of actual physical form.
NEW LOGICAL:
This is exactly like a current logical model if the user were completely happy with
the user were completely happy with the functionality of the current system but had
problems with how it was implemented typically through the new logical model will
differ from current logical model while having additional functions, absolute
function removal and inefficient flows recognized.
NEW PHYSICAL:
The new physical represents only the physical implementation of the new
system.
RULES GOVERNING THE DFD’S
PROCESS
1) No process can have only outputs.

2) No process can have only inputs. If an object has only inputs than it must be a
sink.
3) A process has a verb phrase label.
18
DATA STORE
1) Data cannot move directly from one data store to another data store, a process
must move data.
2) Data cannot move directly from an outside source to a data store, a process,
which receives, must move data from the source and place the data into data
store
3) A data store has a noun phrase label.
SOURCE OR SINK
The origin and / or destination of data.
1) Data cannot move direly from a source to sink it must be moved by a process.
2) A source and /or sink has a noun phrase land
DATA FLOW
1) A Data Flow has only one direction of flow between symbols. It may flow in
both directions between a process and a data store to show a read before an
update. The later is usually indicated however by two separate arrows since
these happen at different type
.
2) A join in DFD means that exactly the same data comes from any of two or more
different processes data store or sink to a common location.
3) A data flow cannot go directly back to the same process it leads. There must be
at least one other process that handles the data flow produce some other data
flow returns the original data into the beginning process.
4) A Data flow to a data store means update (delete or change).
5) A data Flow from a data store means retrieve or use.
19
DATA FLOW DIAGRAM
ADMIN
DONORS/USERS DATABASE
DONORS
ORGANISATIONS
Blood Donation
Agent
FUTURE USE
EDIT/UPDTAE
NEED BLOOD
20
4.2 E-R Diagram
This document is an entity Relation - ship (ER) diagram or „‟ERD‟‟ for a system to
manage Electronic resources. An ERD is a model that identifies the concepts or
entities that exit. In a system and the relationship between those entities. An ERD is
often used as a way to visualize a relationship database. Each entity represents a
database table and the keys in one table that point to specific records in related
tables. ERD may also be more abstract not necessarily capturing every table needed
within database, but serving to diagram the major concepts and relationship.
The ERD is the later type, intended to present an abstract, theoretical view of major
Entities and relationships needed for management of electronic device.
It may assist the Database design process for an eco-trip management system but
does not identify ever Table would be necessary for a trip management system.
Entity
Attribute
Relationship
21
WORK FLOW OF ALL MODULES
Administrator
Login data
Logs In
Donor
Organization
Appointment
Details
Various Reports Blood Details View Random

Generated the Information for
Donor Donor Report the App Donor
Operator Report
22
4.3 Input Design
Input design is the process of converting user oriented input to a computer based
format. The Input data were collected and once they were identified, appropriate
input media were selected for processing. The goal of designing input data was to
make data entry as easy and free from errors as possible. An input format should be
logical and easy to understand. Each area in the form was clearly identified and
specified to the user what to write and where to write it.
While entering the data, the operators need to know the allocated space from each
field, The format in which data fields are entered and the name of the data for the
specified in addition to this the input design phase made sure that data values and
transaction have validations to detect errors and comments to warn the user a
wrong input. Control was ensuring for entering input data. Input controls provided
ways to ensure that:
 Only authorized user can access the system

 Validate the data for accuracy
 Determine whether any necessary data have been omitted
4.4 Output Design
Computer output is the most important and direct source of information to the user
efficient and intelligent output design improves the system relationship with the
user and help in decision making. The output also provides a means of storing a
copy of results for later reference and consultation. Output also provides a means of
storing a copy of results for later reference and consultation. Output generally refers
to the results and in the form of operational documents or reports. The report section
in the proposed system consists of the following:
 Report of the general public

 Report of the blood donor
23
ER-DIAGRAMS
USER ID
USER ID
REGISTER HOME SIGN IN
USER
PASSSWORD
NAME
PASSSWORD
ADD ADMIN1 VIEW
CONTACT NO.
ADDRESS
ORGANISATION
NAME
ADMIN DONOR DETAILS

ORGANISATION 2
DETAILS
NAME BLOOD
GRUOP
DOB AGE
ORGANISATION
DETAILS GENDER
REPORT OF DONOR REPORT ORGANISATIONS PAGE

DETAILS
24
4.5 Database Design
Designing a database is carried out with proper planning which require team effort
and corporation. Improper database design, if implemented .May result is too few or
too many fields. Data base design runs in parallel with the application design. As we
collect information about what is to be done, we will obviously collect information
about what data needs to be enter, stored, messaged and printed on the reports.
Various steps involved in the database design are listed below:
 Data definition
In the first phases of design, we must make lists of all attributes involved in my
applications. It should be noted that, all the fields of our database might be
required, should be included
 Data Refinement
The second step in the database design is to refine our initial list of fields so that
the fields from the accurate description of the types of data will be needed in the
database.
 Identifying the keys
The next step in the database design is to identify the key that is used as a
primary key is a key which uniquely identifies a row in a table.
The foreign key is identified. A foreign key which acts as a primary key for
another table
 Normalization
Normalization is the process of decomposing the attributes in an application, which

results in a set of tables with very simple structures or in simple word; it is a
process of simplifying the relationship between data elements in file.
The purpose of normalization is to make tables as simple as possible.
25
Normalization is carried for the following reason. There exit five normalization tests,
of which the first three are of most important. When the database structure has
passed the first test it is said to be first normal form (INF). When it has passed the
first and the second test than it is said to be second normal Form (2NF) and so on.
TABLE STRUCTURE
TABLE NAME: DEPT.
TABLE NAME: REGISTER
26
TABLE NAME: DONOR
27
SAMPLE CODING
Home
<%@ Page Language="C#" AutoEventWireup="true" Code File="HOME (1).aspx.cs"

Inherits="JNRM_PROJECT_HOME_1_" %>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title>HOME PAGE</title>
<style>
</style>
</head>
<body background="images.jpg" style="background-size:cover;">
<form id="form1" runat="server"
style="font-family: 'Comic Sans MS'; font-size: larger; font-weight: bold; color:
#FF0000; font-style: italic">
<div>
<h1 style="text-align:center; color:cornflowerblue; font-family: Cambria; font-size:
xx-large; font-weight: bold; font-style: normal;">JAWAHARLAL NEHRU
RAJKEEYE MAHAVIDYALAYA</h1>
</div>
<h2 style="text-align:center; color:cornflowerblue; text-decoration:underline;
cursor:pointer; font-family: 'Bookman Old Style'; font-size: x-large; font-weight: bold;
font-style: normal;">
BLOOD DONATION SYSTEM</h2>
           &nbs
p;           &n
bsp;
28
           &nbs
p;
"Donate Blood Save a Life"
           &nbs
p;           &n
bsp;
           &nbs
p;    <br />
           &nbs
p;           &n
bsp;
           &nbs
p;
<br />
           &nbs
p;           &n
bsp;

<asp:Button ID="Button1" runat="server" BackColor="#99CCFF"
Font-Size="Large" ForeColor="#990033" Height="39px" Text="REGISTER"
Width="147px" onclick="Button1_Click1"/>
           &nbs
p;           &n
bsp;
<asp:Button ID="Button2" runat="server" BackColor="#99CCFF"
Font-Size="Large" ForeColor="#990033" Height="39px" Text="SIGN IN"
Width="147px" onclick="Button2_Click1"/>
<br />
<br />
<br />
29
<br />
<br />
<br />
           &nbs
p;           &n
bsp;
           &nbs
p;           &n
bsp;
           &nbs
p;           &n
bsp;
           &nbs
p;           &n
bsp;
       <br />
           &nbs
p;           &n
bsp;
           &nbs
p;           &n
bsp;
           &nbs
p;           &n
bsp;
           &nbs
p;
           &nbs
p;
<br />
<br />
30
<br />
<br />
<br />
<br />
<br />
</form>
</body>
</html>
Login
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="LOGIN.aspx.cs"

Inherits="LOGIN" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<title></title>
<style type="text/css">
.style1
{
width: 83%;
margin-left: 47px;
}
.style4
{
height: 23px;
}
.style8
31
{
width: 283px;
}
.style9
{
text-decoration: underline;
}
</style>
</head>
<form id="form1" runat="server">
<div>
<asp:HyperLink ID="HyperLink1" runat="server"
NavigateUrl="~/HOME(1).aspx">BACK</asp:HyperLink>
<h1 style="text-align:center; color:cornflowerblue;" class="style9">BLOOD
DONATION
SYSTEM</h1>
</div>
<asp:Panel runat=server BackColor=Transparent BorderStyle=Groove
BorderColor=ActiveBorder Height="130px" style="margin-left: 329px"
Width="686px">
<table class="style1">
<tr>
<td colspan="2" class="style4">
           &nbs
p;           &n
bsp;
           &nbs
p;           &n
bsp;     LOGIN HERE!!!</td>
32
</tr>
<tr>
<td class="style8">
           &nbs
p;           &n
bsp;
         USER
ID         :</td>
<td>
<asp:DropDownList ID="DropDownList1" runat="server" AutoPostBack="True">
<asp:ListItem>-----SELECT------</asp:ListItem>
<asp:ListItem>Admin</asp:ListItem>
<asp:ListItem>User</asp:ListItem>
</asp:DropDownList>
</td>
</tr>
<tr>
<td class="style8">
           &nbs
p;
           &nbs
p;        PASSWORD :</td>
<td>
<asp:TextBox ID="TextBox2" runat="server" TextMode="Password"
Width="170px"></asp:TextBox>
</td>
</tr>
<tr>
<td class="style4" colspan="2">
           &nbs
p;           &n
33
bsp;
           &nbs
p;
         <asp:Button
ID="Button1" runat="server" Font-Bold="True" onclick="Button1_Click"
Text="LOGIN" Width="147px" />
           &nbs
p;           &n
bsp;
           &nbs
p;           &n
bsp;          <asp:Literal
ID="Literal1" runat="server"></asp:Literal>

<br />
           &nbs
p;           &n
bsp;
           &nbs
p;           &n
bsp;
           &nbs
p;           &n
bsp;
           &nbs
p;           &n
bsp;

           &nbs
p;           &n
34
bsp;

</td>
</tr>
</table>
</asp:Panel>
</form>
</body>
</html>
Register
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="REGISTER.aspx.cs"

Inherits="REGISTER" %>
<!DOCTYPE html>
<title></title>
<style type="text/css">
.auto-style1 {
position: absolute;
width: 513px;
height: 366px;
top: 85px;
left: 278px;
z-index: 1;
margin-left: 135px;
margin-top: 23px;
}
35
.auto-style2 {
width: 100%;
height: 272px;
}
.auto-style3 {
}
.style4
{
height: 14px;
}
.style5
{
height: 26px;
}
.style6
{
height: 29px;
}
.style7
{
text-decoration: underline;
}
</style>
</head>
<form id="form1" runat="server">
<div>
<asp:HyperLink ID="HyperLink1" runat="server"
NavigateUrl="~/HOME(1).aspx">BACK</asp:HyperLink>
36
<h1 style="text-align:center; color:cornflowerblue;" class="style7">BLOOD
DONATION
SYSTEM</h1>
</div>
<asp:Panel ID="Panel1" runat="server" BackColor="Transparent"
CssClass="auto-style1">
           &nbs
p;           &n
bsp;
           &nbs
p;           &n
bsp;

<br />
           &nbs
p;           &n
bsp;
           &nbs
p;
<asp:Label ID="Label1" runat="server" Text="REGISTER HERE" Font-Size="Large"
ForeColor="red"></asp:Label>
   <br />

<br />
<table class="auto-style2">
<tr>
<td class="style4">

           &nbs
p;
<asp:Label ID="Label2" runat="server" Text="USERID"></asp:Label>
37
</td>
<td class="style4">
<asp:DropDownList ID="DropDownList1" runat="server" AutoPostBack="True"
>
<asp:ListItem>-----SELECT-----</asp:ListItem>
<asp:ListItem>Admin</asp:ListItem>
<asp:ListItem>User</asp:ListItem>
</asp:DropDownList>
</td>
</tr>
<tr>
<td class="style5">

           &nbs
p;
<asp:Label ID="Label4" runat="server" Text="USERNAME"></asp:Label>
</td>
<td class="style5">
<asp:TextBox ID="TextBox2" runat="server" Width="207px"></asp:TextBox>
</td>
</tr>
<tr>
<td class="style6">
           &nbs
p;           &n
bsp;
<asp:Label ID="Label5" runat="server" Text="PASSWORD"></asp:Label>
</td>
<td class="style6">
<asp:TextBox ID="TextBox3" runat="server" Width="207px"
TextMode="Password"></asp:TextBox>
38
</td>
</tr>
</table>
           &nbs
p;
<asp:Button ID="Button1" runat="server" Font-Bold="True" Height="34px"
Text="REGISTER" Width="161px" onclick="Button1_Click1" />
     <asp:Button ID="Button2" runat="server"
Font-Bold="True" Height="34px"
Text="DELETE" Width="161px" onclick="Button2_Click" />
<br />
<br />
           &nbs
p;           &n
bsp;

<asp:Literal ID="Literal1" runat="server"></asp:Literal>
</asp:Panel>
</form>
<p>

</p>
</body>
</html>
Home page
using System;
using System.Collections.Generic;
using System.Linq;
39
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
public partial class JNRM_PROJECT_HOME_1_ : System.Web.UI.Page

{
protected void Page_Load(object sender, EventArgs e)
{
protected void Button1_Click1(object sender, EventArgs e)

{
Response.Redirect("REGISTER.aspx");
}
{
Response.Redirect("LOGIN.aspx");
}
}
Register
using System;
using System.Linq;
using System.Web;
using System.Data;
40
using System.Data.SqlClient;
public partial class REGISTER : System.Web.UI.Page
{
SqlConnection con = new SqlConnection("Data Source=DELL-PC;Initial
Catalog=pavithra;Integrated Security=True");
SqlCommand cmd;
{
Literal1.Visible = false;
}
public void clear()
{
DropDownList1.SelectedValue = "";
TextBox2.Text = "";
TextBox3.Text = "";
}

{
//register coding
if (TextBox2.Text == "" || TextBox3.Text == "")
{
Literal1.Text = "Enter all the fields";
}
String con = "Data Source=DELL-PC;Initial Catalog=pavithra;Integrated
Security=True";
SqlConnection conn = new SqlConnection(con);
cmd = new SqlCommand("insert into reg (userid,username,pwd)values('" +
DropDownList1.SelectedItem.Text + "','" + TextBox2.Text + "','" + TextBox3.Text +
"')", conn);
41
cmd.CommandType = CommandType.Text;
try
{
conn.Open();
cmd.ExecuteNonQuery();
Literal1.Visible = true;
Literal1.Text = "Saved";
clear();
conn.Close();
}
catch (Exception)
{
Literal1.Text = "Already someone has this password!!!";
TextBox3.Focus();
}
}
protected void Button2_Click(object sender, EventArgs e)
{
//delete coding
Security=True";
cmd = new SqlCommand("delete from reg where username='" + TextBox2.Text + "'",

conn);
42
try
{
conn.Open();
Literal1.Text = "Deleted";
clear();
conn.Close();
}
catch (Exception ex)

{
Literal1.Text = ex.Message;
}
}
}
Login page
using System;
using System.Linq;
using System.Xml.Linq;
using System.Web;
using System.Data;
43
public partial class LOGIN : System.Web.UI.Page
{
{
TextBox2.Focus();
}
{
//register coding
Security=True";
SqlCommand cmd = new SqlCommand("CUser5", conn);
cmd.CommandType = System.Data.CommandType.StoredProcedure;
SqlParameter p1 = new SqlParameter("userid", DropDownList1.SelectedItem.Text);
SqlParameter p2 = new SqlParameter("pwd", TextBox2.Text);
cmd.Parameters.Add(p1);
cmd.Parameters.Add(p2);
conn.Open();
SqlDataReader rd = cmd.ExecuteReader();
if (rd.HasRows)
{
if (DropDownList1.SelectedIndex == 1)
{
rd.Read();
Response.Redirect("ADMIN VIEW.aspx");
}
44
{
rd.Read();
Response.Redirect("STUDENT WELCOME.aspx");
}
else
{
Literal1.Text = "Not Found";
}
}
Admin report
Using System;
Using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Data;
45
public partial class admin_report_view : System.Web.UI.Page
{
SqlDataSource ds;
SqlCommand cmd;

{
}
{
Button5.Visible = true;
}
{
DropDownList1.Visible = true;
Label1.Visible = true;
}
protected void DropDownList1_SelectedIndexChanged(object sender, EventArgs e)
{
string str = "Data Source=DELL-PC;Initial Catalog=pavithra;Integrated
Security=True";
con = new SqlConnection(str);
con.Open();
SqlCommand cmd = new SqlCommand("select * from donor where
BLOODGROUP='" + DropDownList1.SelectedItem.Text + "'", con);
SqlDataAdapter da = new SqlDataAdapter(cmd);
DataSet ds = new DataSet();
da.Fill(ds, "donor");
46
GridView1.DataMember = "donor";
GridView1.DataSource = ds;
GridView1.DataBind()
con.Close();
}
}
Admin view
using System;
using System.Linq;
using System.Web;
public partial class ADMIN_VIEW : System.Web.UI.Page

{
{

{
Response.Redirect("Copy of ADMIN VIEW.aspx");
}
{
Response.Redirect("admin report view.aspx");
47
}
}
Class entry
using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class CLASS_ENTRY : System.Web.UI.Page

{
SqlCommand cmd;

{
TextBox7.Focus();
GridView1.Visible = false;
try
{
if (!Page.IsPostBack)
{
BindGrid();
48
}
}
{
}
}
private void BindGrid()
{
SqlCommand cmd = new SqlCommand("select * from donor", con);
DataSet ds = new DataSet();
da.Fill(ds);
GridView1.DataSource = ds;
GridView1.DataBind();
public void clear()

{
TextBox7.Text = "";
TextBox8.Text = "";
TextBox10.Text = "";
TextBox11.Text = "";
TextBox6.Text = "";
RadioButton1.Checked = false;
RadioButton2.Checked = false;
DropDownList1.SelectedIndex = 0;
49
}

{
string gen="",bg="";
if (RadioButton1.Checked == true)
{
gen = "MALE";
}
else
{
gen = "FEMALE";
}
{
bg = "A+";
}
{
bg = "A-";
}
{
bg = "B+";
}
{
bg = "B-";
}
50
{
bg = "O+";
}
{
bg = "O-";
}
{
bg = "AB+";
}
{
bg = "AB-";
}
try
{
cmd = new SqlCommand("insert into

donor(NAME,AGE,GENDER,BLOODGROUP,DOB,ADDRESS,PHONENO)values('"
+ TextBox7.Text + "','" + TextBox8.Text +
"','"+gen+"','"+bg+"','"+TextBox10.Text+"','"+TextBox11.Text+"','"+TextBox6.Text+"')",
con);
con.Open();
Literal1.Text = "Saved";
clear();
cmd.Dispose();
BindGrid();
51
con.Close();
}
{
}
}
{
string gen="",bg="";
if (RadioButton1.Checked == true)
{
gen = "MALE";
}
else
{
gen = "FEMALE";
}
{
bg = "A+";
}
{
bg = "A-";
}
{
bg = "B+";
}
52
{
bg = "B-";
}
{
bg = "O+";
}
{
bg = "O-";
}
{
bg = "AB+";
}
{
bg = "AB-";
}
try
{
cmd = new SqlCommand("update donor set NAME='"+TextBox7.Text +"',AGE='" +

TextBox8.Text +
"',GENDER='"+gen+"',BLOODGROUP='"+bg+"',DOB='"+TextBox10.Text+"',ADDRE
SS='"+TextBox11.Text+"',PHONENO='"+TextBox6.Text+"' WHERE
NAME='"+TextBox7.Text+"'",con);
con.Open();
53
Literal1.Text = "Updated";
GridView1.EditIndex = -1;
BindGrid();
con.Close();
clear();
}
{
}
}
{
try
{
cmd = new SqlCommand("delete from donor where NAME='" + TextBox7.Text + "'",
con);
con.Open();
Literal1.Text = "deleted";
clear();
con.Close();
54
{
}
}
{
/*GridView1.Visible = true;
con.Open();
SqlCommand cmd = new SqlCommand("select * from donor", con);
DataTable dt = new DataTable();
da.Fill(dt);
GridView1.DataSource = dt;
con.Close();
*/
GridView1.Visible = true;
BindGrid();
}
protected void GridView1_SelectedIndexChanged(object sender, EventArgs e)
{
GridViewRow row = GridView1.SelectedRow;
TextBox7.Text = row.Cells[2].Text;
55
}
protected void GridView1_RowDeleting(object sender, EventArgs e)
{
try
{
cmd = new SqlCommand("delete from donor where NAME='" + TextBox7.Text + "'",

con);
con.Open();
Literal1.Text = "Deleted";
GridView1.EditIndex = -1;
con.Close();
}
{
}
}
protected void DropDownList1_SelectedIndexChanged(object sender, EventArgs e)

{
}
}
56
SYSTEM TESTING & IMPLEMENTIONS
INTRODUCTION:
System implementation is the important stage of the project when the Theoretical
designing is turn into practical system. The main stage in the
Implementations are as follow:
1. PLANNING:
When implementation is concerned planning plays an important role. The

implementation of system will have to face any practical problems of controlling
various activities of people outside their own data processing department. The active
co-operation of different staff member will be essential for successful
implementation.
2. TRAINING:
For successful implementation trained computer staffs are essential.so we have to

select some staff and teach them about the computer implementation phase, and
then only the designed system can be successfully implementation.
3. TESTING :
Before implementation, the designed system should be tested with raw data to
ensure that all module of the system work correctly and satisfactorily. Software
testing is a crucial element of software quality assurance and represents the ultimate
review of specification, design and coding. Testing represents an interesting
anomaly for the software. During earlier definition and development phases, it was
attempted to build software from an abstract concept to a tangible implementation
specifies .The Blood Donation System was successfully tested with unit testing and
system testing.
57
A. UNIT TESTING
At the very lowest level is unit testing where the programmer that writes the codes
as per the detailed specification. Unit testing comprises the set of tests perform by
individual performed by individual programmers prior to integrations of the unit
into a larger system .This situation is illustrated as follows:
Coding & Debugging Unit testing Integration Testing
B. SYSYTEM TESTING
The next level of testing is the system testing where the project leader or system
analyst test all of the components to see that that they correctly when combined as
system. A series of testing are performed for the newly developed system before
the system is ready for user acceptance testing.
C. VALIDATION TESTING
Validation succeeds when the software function in a manner that can be

reasonably expected by the customer. Software validation is achieved through a
series of black box test that demonstrate confirm with the requirements. Deviation
or errors discovered at this step are corrected .prior to the completion with the help
of the user by negotiating to establish evolving deficiencies.
D. OUTPUT TESTING:
The output generated by the system under consideration is in the format required
by the user. And the information in the report id accurate .It is possible to
generated timely report without any errors.
E. USER ACCEPTANCE TESTING:
The system developed is tested for acceptance by constantly keeping in touch with
prospective system user at the time of development and changes were made
whenever required. This is done with respect to the following input and output
screen design online help message to guide the user.
58
INPUT/OUTPUT SCREEN
HOME PAGE
REGISTER PAGE
59
SIGN-IN PAGE
ADMIN PAGE 1
60
ADMIN PAGE 2
ORGANISATION DETAILS PAGE
61
REPORT OF ORGANISATION DETALIS
DONOR DETAILS PAGE
62
REPORT OF DONOR DETAILS PAGE
USER PAGE
63
LIMITATIONS OF THE PROJECT
 Blood can be donated 6 times a year per person.
 The size of the database increases day-by-day, increasing the load on the
database backup and data maintenance activity.
 Training for simple computer operations is necessary for the users working
on the system.
64
FUTURE APPLICATION OF THE PROJECT
BLOOD DONATION SYSTEM is a software application to build such a way that it

should suits for all type of blood banks in future.
One important future scope is availability of location based blood bank details and
extraction of location based donor‟s details, which is very helpful to the acceptant
people. All the time the network facilities cannot be used. This time donor request
does not reach in proper time, this can be avoid through adding some message
sending procedure this will help to find proper blood donor in time . This will
provide availability of blood in time.
65
CONCLUSION
With the theoretical inclination of our syllabus it becomes very essential to take the
almost advantage of any opportunity of gaining practical experience that comes
along. The building blocks of this major project “BLOOD DONATION SYSTEM”
was one of these opportunities. It gave us the requisite practical knowledge to
supplement the already taught theoretical concepts thus making us more competent
as a computer engineer. The project from a personal view also helped us in
understanding the following aspects of project development:
 The planning that goes into implementing a project.

 The importance of proper planning and an organized methodology.
 The key element of team spirit and co-ordination in a successful project.
66
BIBLOGRAPHY
 FOR .NET INSTALLATION

www.support.mircosoft.com
 FOR DEPLOYMENT AND PACKING ON SERVER

www.developer.com
www.15seconds.com
 FOR SQL
www.msdn.microsoft.com
 FOR ASP.NET
www.msdn.microsoft.com/net/quickstart/aspplus/default.com
www.asp.net
www.fmexpense.com/quickstart/aspplus/default.com
www.asptoday.com
www.aspfree.com
www.4guysfromrolla.com/index.aspx
67

Blood Management System

Uploaded by

Copyright:

Available Formats

You might also like

Blood Management System

Uploaded by

Document Information

Original Description:

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

Blood Management System

Uploaded by

Copyright:

Available Formats

SYNOPSIS

Synopsis is a general documentation tool. By means of a modular structure, it

The website is designed to provide information about “BLOOD DONATION

Modules of the project

This is the registration of the donors.

This page is registration of the organization details.

This page is regarding donor registration.

To search the required blood group.

This about the Blood Donation System.

1.1. About the organization

1.2. Objectives of the proposed

This project is aimed to developing an online Blood Donation Information.

Admin is the main authority who can do addition, deletion, and

The project has been planned to be having the view of distributed

2.1 Existing System

 Cannot Upload and Download the latest updates.

2.2. Proposed System

2.3 TOOLS & TECHNIQUES USED TO COMPLETE THE STUDY

 Firstly we the associates of this project had an interaction with the

3.1 Problem Analysis

 Problem analysis is the process of understanding real - world problems

 The goal of problem analysis is to gain a better understanding, before

 Identifying the actors on the system is a key step in problem analysis

3.2 Feasibility Study

A project feasibility study is a comprehensive report that examines in detail

The following are the areas for Feasibility

This assessment is based on an outline design of system requirements, to

3.3 Tools and Environment Used

ASP.NET is a web application framework developed and marketed by Microsoft

In ASP.NET support with the following list:-

 Better language support

 ASP.NET uses ADO.NET

ASP.NET support form-based user authentication, cookie management, and

Server-to-server communication has been greatly enhanced, making it possible to

The important distinction between this evolved stage of ADO.NET and

 Connections. For connection to and managing transactions against a

SQL Server Tables

3.4 HARDWARE CONFIGURATION

 Processor : INTEL i5 CORE

 Front end : .net with c#

 Preliminary or general design

Preliminary or general design:-

Structured or detailed design:-

Data flow diagram symbols:

- Source or Destination of data

Several rules of thumb are used in drawing DFD‟S:

SAILENT FEATURES OF DFD’S

TYPES OF DATA FLOW DIAGRAMS

RULES GOVERNING THE DFD’S

1) No process can have only outputs.

The origin and / or destination of data.

4) A Data flow to a data store means update (delete or change).

5) A data Flow from a data store means retrieve or use.

Various Reports Blood Details View Random

 Only authorized user can access the system

4.4 Output Design

 Report of the general public

ADD ADMIN1 VIEW