ABV Indian Institute of Information Technology and

Management, Gwalior

DBMS
PROJECT REPORT
(BLOOD BANK MANAGEMENT SYSTEM)

Submitted to: Submitted by:

Dr. Vinay Singh Pooja Karmakar

(2016MBA-20)

Shrahi Singh Karanwal

(2016MBA-28)
 Acknowledgement

We are thankful to the prestigious campus of ABV IIITM Gwalior for providing us the
esteemed platform for enhancing our knowledge and skills of management discipline.

We are also thankful to our mentor Dr. Vinay Singh for his time to time guidance for the
improvement of project work. This unique way of making the DBMS concepts seems
really interesting and without his guidance project would have been gone off the track.
We hope the project work is up to the expectations.

Last but not the least, we are thankful to our parents and friends for their cooperation and
also to our group members for working as a very cooperative team and putting in the best
efforts to make the project successful.
 INTRODUCTION
Project Overview

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.

Project Description

This project is aimed to developing an online Blood Donation Information. The entire
project has been developed keeping in view of the distributed client server computing
technology, in mind.
The Blood Donation Agent is to create an e-Information about the donor and organization
that are related to donating the blood. Through this application any person who is interested in
donating the blood can

register himself in the same way if any organization wants to register itself with this site that can
also register. Moreover if any general consumer wants to make request blood online he can also
take the help of this site.
Admin is the main authority who can do addition, deletion, and modification if
required.
The project has been planned to be having the view of distributed architecture, with
centralized storage of the database. The application for the storage of the data has been planned.
Using the constructs of MS-SQL Server and all the user interfaces have been designed using the
ASP.Net technologies.
The database connectivity is planned using the SQL Connection methodology. The
standards of security and data protective mechanism have been given a big choice for proper
usage.

The application takes care of different modules and their associated reports, which are
produced as per the applicable strategies and standards that are put forwarded by the
administrative staff.
The 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.
 PROBLEM DEFINITION
Existing System
Cannot Upload and Download the latest updates.
No use of Web Services and Remoting.
Risk of mismanagement and of data when the project is under development.
Less Security.
No proper coordination between different Applications and Users.
Fewer Users Friendly
Proposed System
To debug the existing system, remove procedures those cause data redundancy, make
navigational sequence proper. To provide information about audits on different level and also to
reflect the current work status depending on organization/auditor or date. To build strong
password mechanism.

Advantages:
User friendliness I provided in the application with various controls.
The system makes the overall project management much easier and flexible.
Readily upload the latest updates ,allows user to download the alerts by clicking
the url.
It provides high level of security with different level of authentication.
 MODULES
1. Administration:
In this module the Administrator has the privileges to add all the Blood Groups,
Blood Type, Organization, Type, Country, State, City, and Location. He can search
all the info about the Organization, Donor.
User Account:
AccountID
Username
Password
UserDesc
HintQuestion
Answer
RoleID
Active

UserRole:
RoleID
RoleName
RoleDesc
Active
BDA State:

StateID
StateName
StateCode
StateDesc
CountryID
Active
Country:
CountryID
CountryName
CountryDesc
CountryCode
Active

BDA City:
CityID
CityName
CityDesc
CityCode
StateID
Active
BDALocation:
LocationID
LocationName
LocationDesc
LocationCode
CityID
Pin code
Active

BloodGroup:
BloodGroupID
BloodGroup
Description
Active
 Blood Type:
BloodTypeID
TypeName
TypeDesc
Active
Personal Details:

UserAccountID
FirstName
MiddleName
LastName
Email
DOB
Weight
Gender
ImageURL
BloodGroupID
BloodType
BloodType
AddressID
ContactNo_Office
ContactNo_Residence
MobileNo
Active

Call Center:
In this module all the employee who has been appointed by Admin will come. Admin will add
all the information of employee and assign user name and password to them. By using that user
name and password they will enter to their login and can search for all the donor, and about all
the blood request which have been made by either consumer, donor or any organization. Call
center people will assign donor to related request.

Employee Detail:
EmpId
Name
Address
Phone
Email
Active
Donor:
Donor is that person who is interested in donating their blood so they can register themselves
through this website. If any requirement comes then they will be contacted and they can donate
their blood. Along with it they can search for the various organization locations wise and can
also make request for blood if needed
Donation Frequencies:
Frequency ID
Frequency
Description

Donor Preferred Organization:

User Account D
Organization ID
Active
Organization:
In this module if any organization wants to register itself then it can do it. It can also search for
donor location wise and if needed then it can also make request for blood
Organization:
OrgID
OrgName
OrgType
Email
OrgAddrID
OrgImageURL
OrgDescription
ContactNo
MobileNo
Active
Comment
Organization Type:
TypeID
TypeName
Type Description
HARDWARE REQUIREMENTS:

PIV 2.8 GHz Processor and Above

RAM 512MB and Above
HDD 20 GB Hard Disk Space and Above

SOFTWARE REQUIREMENTS:

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

Visual Studio .Net 2005 Enterprise Edition
Internet Information Server 5.0 (IIS)
Visual Studio .Net Framework (Minimal for Deployment)
SQL Server 2000 Enterprise Edition
 SYSTEM DESIGN

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 atleast 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.

Context Diagram

Admin

DataBase
Call Center

Blood Donation
Donor
Agent

Organization

Future Use
1st Level DFDs

Level 1 DFD: For Admin Module

Admin

Login
data
login

Value View of value

Abilities Abilities
Table details

Level 1 DFD: For Users Module

Call Center

Login

Value Abilities updating and

Table editing
 DFD For Donor Creation

Donor Donor Id
Details

Insert New
Donor
Insert Donor
Verify Id Verify
Data Data

1.1
1.2

Insert

Donor Details
 DFD For Operator Creation

Operator Id
Operator
Details

Verify
Insert New Data
Operator

Verify 2.2
Data

2.1

Insert
Operator Id

Insert

Operator
Details
 DFD For Call Center Creation

Call Center
Call Center Id
Details

Verify
Insert New Data
Call Center Verify
Data 3.2
3.1

Insert Call
Center Id

Call Center
Insert
Details

Donor
Details
DFD for Donor Creation

Donor Donor Id
Organizati
Details on Details

Insert New
Donor
Verify Data Verify Data
Verify Data
4.1 4.2
4.3

Insert
Donor
Details
Insert Donor Id
Check in
Organization

Check for
Check for Dates
Check for
Verify Blood Type
Verify Appointm Verify
Data ent Data
Data
Details
4.4

4.6 4.5

Appointment Dates
Blood Details Details Details

Insert

Donor Details
 3rd Level DFDS
DFD For Donor Creation

Donor Details Organization Details Dates Details

Request for new

Donor
Generate Validate
Validate
Donor-Id Org-Id ()
() Dates-Id ()

Validate Validate App-

Blood-Id () Id ()
Commit ()

Database
Updated

Blood Details Appointment Details

Donar Details
 Work Flow of All Modules

Administrator

Login data

Logs In

Donar

Call Organiza
Center tion
Appointment
Details

Various Reports Blood Details View Random

Generated the Information for
Donar the App Donar
Donor Report

Operator Report

Call Center Report

 DATABASE DESIGN
Entities with Attributes:
1.Administration:
Use rAccount:
AccountID
Username
Password
UserDesc
HintQuestion
Answer
RoleID
Active

UserRole:
RoleID
RoleName
RoleDesc
Active

BDAState:
StateID
StateName
StateCode
StateDesc
CountryID
Active
Country:
CountryID
 CountryName
CountryDesc
CountryCode

BDACity
CityID
CityName
CityDesc
CityCode
StateID
Active
:
BDALocation:

LocationID
LocationName
LocationDesc
LocationCode
CityID
Pin code
Active
BloodGroup:
BloodGroupID
BloodGroup
Description
Active

BloodType:
BloodTypeID
TypeName
 TypeDesc
Active
PersonalDetails:
UserAccountID
FirstName
MiddleName
LastName
Email
DOB
Weight
Gender
ImageURL
BloodGroupID
BloodType
BloodType
AddressID
ContactNo_Office
ContactNo_Residence
MobileNo
Active

EmployeeDetail:
EmpId
Name
Address
Phone
Email
Active
DonationFrequencies:
FrequencyID
 Frequency
Description
Active

Donor Preferred Organization:

UserAcountID
OrganisationID
Active
Organisation:
OrgID
OrgName
OrgType
Email
OrgAddrID
OrgImageURL
OrgDescription
ContactNo
MobileNo
Active
Comment
OrganisationType:
TypeID
TypeName
TypeDescription
OrgImage
Active

ER Diagrams
 ER diagram for User Account and Users

Has/b
User Account: elongs UserRole:

UserAccount: UserRole:

AccountID RoleID

Username RoleName

Password RoleDesc

UserDesc Active

HintQuestion

Answer

RoleID
 ER diagram for User Account and Organisation

User Account Has/b Organisation:

elongs

Organisation:
UserAccount:
OrgID
AccountID OrgName
OrgType
Username
Email
OrgAddrID
Password
OrgImageURL
UserDesc OrgDescription
ContactNo
Hint Question MobileNo
Active
Answer
Comment

RoleID
 ER diagram for Users Account and Personal Details

Has/b
elongs Personal details
User Account:

UserAccount: Personal Details:

AccountID
First Name

Username
Email

Password
DOB

UserDesc
Weight

HintQuestion
Gender

Answer
ImageURL

RoleID
BloodGroupID

BloodType

BloodType

AddressID

ContactNo_Office

ContactNo_Residence

MobileNo

Active

MiddleName
 ER diagram for User Account and Employee Details

Employee Details
User Account Has/b
elongs

User Account: Employee Details:

Emp Id
AccountID
Name
Username Address
Phone
Password
Email
User Desc Active

Hint Question

Answer

Role ID
 ER diagram for User Role and Blood User account

Has/b User Account

elongs
UserRole

User Account:
UserRole:
AccountID
RoleID
Username
RoleName
Password
RoleDesc
User Desc
Active
Hint Question

Answer

Role ID
 ER Diagram for State and BDA City

Has/b
State BDAcity
elongs

BDACity:

BDAState: CityID

StateID CityName

StateName CityDesc

StateCode CityCode

StateDesc StateID

CountryID Active

Active
 ER diagram for State and Address

Has/b
State elong Address:
s

BDAState: dBDA_Address

StateID AddressID

StateName AddressLine1

StateCode LocationID

StateDesc CityID

CountryID StateID

Active CountryID

CountryID

Zipcode

Active
 ER diagram for State and Country:

State Has/b Country

elong
s

BDAState:

StateID Country:

StateName CountryID

StateCode CountryName

StateDesc CountryDesc

CountryID CountryCode

Active Active
 ER diagram for Location and City

Has/b
Location: elong State
s

BDALocation:
BDAState:
LocationID
StateID
LocationName
StateName
LocationDesc
StateCode
LocationCode
StateDesc
CityID

CountryID
Pin code

Active
Active
 ER diagram for Location and City

Has/b City:
DBDAddress: elong
s

BDACity:

dBDA_Address
CityID

AddressID
CityName

AddressLine1
CityDesc

LocationID
CityCode

CityID
StateID

StateID
Active

CountryID
 CountryID

Zipcode

Active

ER diagram for Location and Address

BDALocation: DBDAddress:
Has/b
elong
s

BDALocation: DBDAAddress

LocationID AddressID

LocationName AddressLine1

LocationDesc LocationID

LocationCode CityID

CityID StateID

Pin code CountryID

Active CountryID

Zipcode

Active
 ER diagram for Blood group Personal details

Has/b
Blood group: elong Personal details
s

Personal details:
BloodGroup:
UserAccountID
BloodGroupID

FirstName
BloodGroup

MiddleName
Description

Active
LastName

Email

DOB

Weight

Gender

ImageURL

BloodGroupID

BloodType

AddressID

ContactNo_Office

ContactNo_Residence

MobileNo

Active
 ER diagram for Personal details and Blood Donation preferences

Personal details Has/b Preferd location Day Time Details.

elong
s
Personal details:
PreferredDonationDayTime
UserAccountID
DonorPreferenceID
FirstName
WeekDay
MiddleName
TimeFrom

LastName
TimeFrom
Email
TimeUpto
DOB
UserAccountID
Weight
Comment
Gender
Active
ImageURL

BloodGroupID

BloodType

AddressID

ContactNo_Office

ContactNo_Residence

MobileNo

Active
 ER diagram for Donor Frequencies and Blood Donation Preferences

Has/b
DonationFrequencies: elong BloodDonationPrefere
s nce

BloodDonationPreference:
DonationFrequencies:
PreferenceID
FrequencyID
UserAccountID
Frequency
DonationFrequencyID
Description
WantToDonateWhitecells
Active
Active
 ER diagram for Donor preferred organization and personal details

Has/b
Donar preferred organization elong Persanal Details
s

DonorPreferredOrganisation: Personal details:

UserAcountID UserAccountID

OrganisationID FirstName

Active
MiddleName

LastName

Email

DOB

Weight

Gender

ImageURL

BloodGroupID

BloodType

AddressID

ContactNo_Office

ContactNo_Residence

MobileNo
 Active

ER diagram for Organization type and Organization .

Has/b
Organization type Organization
elong
s

Organisation:
OrganisationType: OrgID

TypeID OrgName
OrgType
TypeName Email
OrgAddrID
TypeDescription
OrgImageURL

OrgImage OrgDescription
ContactNo
Active MobileNo
Active
Comment
 DATABASE TABLES
BDA_ Address

Sno Column name Data type Constraint Reference

1 AddressID Bigint Primary Key
2 AddressLine1 varchar(512) Not null
3 LocationID Bigint Foreign key BDA_Location
4 CityID Bigint Foreign key BDA_City
5 StateID Bigint Foreign key BDA_state
6 CountryID Bigint Allow Null BDA_Country
7 Zipcode varchar(10) Allow Null
8 Active Bit Not Null

BDA_BloodDonationDetails

Sno Column name Datatype Constraint Reference

1 ID Bigint Primary Key
2 DonorID Bigint Foreign key BDA_BloodRequest
3 DonationDate Datetime Notnull
4 TakerID Bigint Foreign key BDA_UserAccount
5 OrgID Bigint Foreign key Bda_Organisation
6 Quantity varchar(10) Allow Null
7 Comment varchar(1024) Allow Null
8 Active Bit Notnull
BDA_BloodDonationPreference

Sno Columnname Datatype Constraint Reference

1 PreferenceID bigint Primary key

2 UserAccountID bigint Foreign key BDA_UserAccount

3 DonationFrequencyID tinyint Foreign key BDA_Donation Frequencies

4 WantToDonateWhitecells bit AllowNull

5 Active bit AllowNull

BDA_BloodGroup

Sno Columnname Datatype Constraint Reference

1 BloodGroupID Tinyint Primary Key
2 BloodGroup varchar(10) Not Null
3 Description varchar(1024) Allow Null
4 Active Bit Not Null

BDA_BloodRequest

Sno Columnname Datatype Constraint Reference

1 RequestID int Primary Key
2 DonorId bigint Foreign key BDA_UserAccount
3 OrgId bigint Foreign key BDA_Organisation
4 Name varchar(50) Allow Null
5 Email varchar(50) Allow Null
6 Phone varchar(20) Allow Null
7 Country varchar(50) Allow Null
8 State varchar(50) Allow Null
9 City varchar(50) Allow Null
10 Location varchar(50) Allow Null
11 BloodRequireAddress varchar(100) Allow Null
12 BloodType varchar(50) Allow Null
13 BloodGroup varchar(50) Allow Null
14 AppDate datetime Allow Null
15 ReqDate datetime Allow Null
16 Status varchar(10) Allow Null
17 RequestType varchar(50) Allow Null

BDA_City

Sno Columnname Datatype Constraint Reference

1 CityID Bigint Primary key
2 CityName varchar(100) Not null
3 CityDesc varchar(1024) allownull
4 CityCode varchar(5) Allownull
5 StateID Bigint Foreign key BDA_State
6 Active Bit notnull

BDA_BloodType

Sno Columnnames Datatypes Constraint reference

1 BloodTypeID Tinyint Primary Key
2 TypeName varchar(50) Not null
3 TypeDesc varchar(1024) AllowNull
4 Active Bit Notnull
BDA_Country

Sno Columnname Datatype Constraint Reference

1 CountryID Bigint Primary key
2 CountryName varchar(100) Not null
3 CountryDesc varchar(1024) Allow Null
4 CountryCode varchar(5) Allow Null
5 Active Bit Not null

BDA_DonationFrequencies

Sno Columnname Datatype Constraint Reference

1 FrequencyID Tinyint Primary key
2 Frequency varchar(50) Not null
3 Description varchar(255) Allow null
4 Active Bit Allow null

BDA_DonorPreferredOrganisation

Sno Columnname Datatype Constraint Reference

1 UserAcountID Bigint Primary key
2 OrganisationID Bigint Not null
3 Active Bit Allow null
BDA_EmployeeDetail

Sno Columnname Datatype Constraint Reference

1 EmpId Bigint Primary Key
2 Name varchar(60) Allow Null
3 Address varchar(150) Allow Null
4 Phone varchar(20) Allow Null
5 Email varchar(25) Allow Null
6 Active Tinyint Allow Null

BDA_FAQ

Sno Columnname Datatype Constraint Reference

1 FaqID Bigint Primary key
2 Question varchar(300) Allow null
3 Answer varchar(1000) Allow null
4 Active Bit Allow null

BDA_Location

Sno Columnname Datatype Constraints Reference

1 LocationID Bigint Primary Key
2 LocationName varchar(100) Not Null
3 LocationDesc varchar(1024) Allow null
4 LocationCode varchar(5) Allow null
5 CityID bigint Allow null
6 Pincode varchar(10) Allow null
7 Active bit Allow null
BDA_Organisation
Sno Columnname Datatype Constraint Reference
1 OrgID bigint Primary key
2 OrgName varchar(100) Not null
3 OrgType tinyint Foreign key BDA_Organisation Type
4 Email varchar(50) Allownull
5 OrgAddrID bigint Foreign key BDA_Address
6 OrgImageURL varchar(155) Allownull
7 OrgDescription varchar(1024) Allownull
8 ContactNo varchar(20) Allownull
9 MobileNo varchar(20) Allownull
10 Active bit Allownull
11 Comment varchar(512) Allownull

BDA_OrganisationType

Sno Columnname Datatype Constraint Reference

1 TypeID tinyint Primary key
2 TypeName varchar(50) Not null
3 TypeDescription varchar(50) Allow null
4 OrgImage varchar(300) Allow null
5 Active bit Allow null
BDA_PreferredDonationDayTime

Sno Columnnames Datattype Constarint Reference

1 DonorPreferenceID Bigint Primary Key
2 WeekDay varchar(10) Not null
3 TimeFrom varchar(10) Allow null
4 TimeUpto varchar(10) Allow null
5 UserAccountID Bigint Allow null
6 Comment varchar(1024) Allow null
7 Active Bit Not null
8
BDA_PersonalDetails

Sno Columnname Datatype Constraint Reference

1 UserAccountID Bigint Primary Key
2 FirstName varchar(50) Not Null
3 MiddleName varchar(50) Allow Null
4 LastName varchar(50) Allow Null
5 Email varchar(100) Allow Null
6 DOB datetime Notnull
7 Weight float Allow Null
8 Gender varchar(6) Not Null
9 ImageURL varchar(155) Allow Null
10 BloodGroupID tinyint Foreign key BDA_Bloodgroup
11 BloodType tinyint Foreign key BDA_BloodType
12 AddressID bigint Foreign key BDA_Address
13 ContactNo_Office varchar(20) Allow Null
14 ContactNo_Residence varchar(20) Allow Null
15 MobileNo varchar(20) Not Null
16 Active bit Allow Null
BDA_UserRole

Sno Columnname DAtatype Constraint Reference

1 RoleID tinyint Primary key
2 RoleName varchar(50) Not null
3 RoleDesc varchar(1024) Allow null
4 Active bit Not null

BDA_State

Sno Columnname Datatype Constraint Reference

1 StateID bigint Primary key

2 StateName varchar(100) Not null

3 StateCode varchar(5) Allow null

4 StateDesc varchar(1024 Allow null

)
5 CountryID bigint Foreign Key BDA_Country
6 Active bit Not null
BDA_UserAccount

Sno Columnname Datatype Constraint Reference

1 AccountID bigint Primary key
2 Username varchar(100) Not null
3 Password varchar(100) Not null
4 UserDesc varchar(1024) Allow null
5 HintQuestion varchar(155) Allow null
6 Answer varchar(155) Allow null
7 RoleID tinyint Foreign key BDA_UserRole
8 Active bit Not null
 ASP.NET
Server Application Development
Server-side applications in the managed world are implemented through runtime hosts.
Unmanaged applications host the common language runtime, which allows your custom
managed code to control the behavior of the server. This model provides you with all the features
of the common language runtime and class library while gaining the performance and scalability
of the host server.
The following illustration shows a basic network schema with managed code running in
different server environments. Servers such as IIS and SQL Server can perform standard
operations while your application logic executes through the managed code.

Server-Side Managed Code:

ASP.NET is the hosting environment that enables developers to use the .NET Framework
to target Web-based applications. However, ASP.NET is more than just a runtime host; it is a
complete architecture for developing Web sites and Internet-distributed objects using managed
code. Both Web Forms and XML Web services use IIS and ASP.NET as the publishing
mechanism for applications, and both have a collection of supporting classes in the .NET
Framework.
If you develop and publish your own XML Web service, the .NET Framework provides a
set of classes that conform to all the underlying communication standards, such as SOAP,
WSDL, and XML. Using those classes enables you to focus on the logic of your service, without
concerning yourself with the communications infrastructure required by distributed software
development.
Finally, like Web Forms pages in the managed environment, your XML Web service will run
with the speed of native machine language using the scalable communication of IIS.
Active Server Pages.NET
ASP.NET is a programming framework built on the common language runtime that can
be used on a server to build powerful Web applications. ASP.NET offers several important
advantages over previous Web development models:
Enhanced Performance. ASP.NET is compiled common language runtime code running on
the server. Unlike its interpreted predecessors, ASP.NET can take advantage of early
binding, just-in-time compilation, native optimization, and caching services right out of the
box. This amounts to dramatically better performance before you ever write a line of code.
World-Class Tool Support. The ASP.NET framework is complemented by a rich toolbox
and designer in the Visual Studio integrated development environment. WYSIWYG editing,
drag-and-drop server controls, and automatic deployment are just a few of the features this
powerful tool provides.
Power and Flexibility. Because ASP.NET is based on the common language runtime, the
power and flexibility of that entire platform is available to Web application developers. The
.NET Framework class library, Messaging, and Data Access solutions are all seamlessly
accessible from the Web. ASP.NET is also language-independent, so you can choose the
language that best applies to your application or partition your application across many
languages. Further, common language runtime interoperability guarantees that your existing
investment in COM-based development is preserved when migrating to ASP.NET.
Simplicity. ASP.NET makes it easy to perform common tasks, from simple form submission
and client authentication to deployment and site configuration. For example, the ASP.NET
page framework allows you to build user interfaces that cleanly separate application logic
from presentation code and to handle events in a simple, Visual Basic - like forms processing
model. Additionally, the common language runtime simplifies development, with managed
code services such as automatic reference counting and garbage collection.
Manageability. ASP.NET employs a text-based, hierarchical configuration system, which
simplifies applying settings to your server environment and Web applications. Because
configuration information is stored as plain text, new settings may be applied without the aid
of local administration tools. This "zero local administration" philosophy extends to
deploying ASP.NET
 Scalability and Availability. ASP.NET has been designed with scalability in mind, with
features specifically tailored to improve performance in clustered and multiprocessor
environments. Further, processes are closely monitored and managed by the ASP.NET
runtime, so that if one misbehaves (leaks, deadlocks), a new process can be created in its
place, which helps keep your application constantly available to handle requests.
Customizability and Extensibility. ASP.NET delivers a well-factored architecture that
allows developers to "plug-in" their code at the appropriate level. In fact, it is possible to
extend or replace any subcomponent of the ASP.NET runtime with your own custom-written
component. Implementing custom authentication or state services has never been easier.
Security. With built in Windows authentication and per-application configuration, you can
be assured that your applications are secure.

LANGUAGE SUPPORT
The Microsoft .NET Platform currently offers built-in support for three languages: C#, Visual
Basic, and JScript.

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 stores data in two or more tables and
enables you to define relationships between the table 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.
 CODING
WEBCONFIG FILE:(Design Code)
Used to set the connections of each page.
<?xml version="1.0"?>
<!--
Note: As an alternative to hand editing this file you can
use the
web admin tool to configure settings for your application.
Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
\Windows\Microsoft.Net\Framework\v2.x\Config
-->
<configuration>
<appSettings>
<add key="ConnStr" value="data source=RAMYA-
2DCA5B123;database=BloodBequeathFederalAgent;integrated
security=sspi"/>
</appSettings>
<connectionStrings>
<add name="BloodDonationAgentConnectionString"
connectionString="Data Source=RAMYA-2DCA5B123;Initial
Catalog=BloodDonationAgent;integrated security=sspi"
providerName="System.Data.SqlClient" />
</connectionStrings>
<system.web>
<!--
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.
-->
<compilation debug="true">
<assemblies>
<add assembly="System.Design,
Version=2.0.0.0, Culture=neutral,
PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Web.Extensions,
Version=1.0.61025.0, Culture=neutral,
PublicKeyToken=31BF3856AD364E35"/>
 <add assembly="System.Web.Extensions.Design,
Version=1.0.61025.0, Culture=neutral,
PublicKeyToken=31BF3856AD364E35"/>
<add assembly="System.Windows.Forms,
Version=2.0.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089"/></assemblies></compilation>
<!--
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<authentication mode="Windows"/>
<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.

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

User Login Form

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

protected void btnLogin_Click(object sender, EventArgs e)

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

if (user.GetUser() == true)
{
account.Username = txtUsername.Text;
DataSet ds = new DataSet();
ds = account.GetAccountId();
string AcId = ds.Tables[0].Rows[0][0].ToString();
Session["username"] = txtUsername.Text;
Session["Acid"] = AcId;
DataSet ds1 = new DataSet();
account.Accountid =int.Parse(AcId);
ds1 = account.GetAddressId();
Session["addid"] = ds1.Tables[0].Rows[0][0].ToString();
Response.Redirect("~/Donor/DonorHome.aspx");
}
else
Image2.Visible = true;
lblMsg.Text = "Your Login Attempt Is Failed Plz try Again....!";
txtPassword.Text = "";
txtUsername.Focus();
//Checking Organization
if (user.GetOrganization() == true)
{
account.Username = txtUsername.Text;
DataSet ds = new DataSet();
ds = account.GetAccountId();
string AcId = ds.Tables[0].Rows[0][0].ToString();
Session["username"] = txtUsername.Text;
Session["Acid"] = AcId;
DataSet ds1 = new DataSet();
org.Orgid =int.Parse(AcId);
ds1 = org.GetOrgAddressId();
Session["addid"]=ds1.Tables[0].Rows[0][0].ToString();
Response.Redirect("~/Organization/OrganizationHome.aspx");
}
else
Image2.Visible = true;
lblMsg.Text = "Your Login Atempt Is Failed Plz try Again....!";
txtPassword.Text = "";
txtUsername.Focus();
//Employee Checking
if (user.CheckEmployee() == true)
 {
account.Username = txtUsername.Text;
DataSet ds = new DataSet();
ds = account.GetAccountId();
string AcId = ds.Tables[0].Rows[0][0].ToString();
Session["username"] = txtUsername.Text;
Session["Acid"] = AcId;
Response.Redirect("~/CallCenter/CallCenterHome.aspx");
}

}
}

TESTING

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

A strategy for software testing integrates software test case design methods into a well-
planned series of steps that result in the successful construction of software. Testing is the set of
activities that can be planned in advance and conducted systematically. The underlying
motivation of program testing is to affirm software quality with methods that can economically
and effectively apply to both strategic to both large and small-scale systems.

STRATEGIC APPROACH TO SOFTWARE TESTING

The software engineering process can be viewed as a spiral. Initially system engineering
defines the role of software and leads to software requirement analysis where the information
domain, functions, behavior, performance, constraints and validation criteria for software are
established. Moving inward along the spiral, we come to design and finally to coding. To
develop computer software we spiral in along streamlines that decrease the level of abstraction
on each turn.
 UNIT TESTING

MODULE TESTING

Component Testing
SUB-SYSTEM TESING

SYSTEM TESTING
Integration Testing

ACCEPTANCE TESTING
User Testing
 OUTPUT SCREENS

Home Page
Admin Login

Admin Home
Add new Organization
Retrieving Organization information

ADD NEW COUNTRY

Country Information

ADD NEW STATE

State Information
ADD NEW CITY

City Information
ADD NEW LOCATION

Location Information
Registration Form For All Users

Login form
User Home

SearchForDonor
Update Account Details

Request for blood

 CONCLUSION

It has been a great pleasure for us to work on this exciting and challenging project. It also
provides knowledge about the latest technology used in developing web enabled application and
client server technology that will be great demand in future. This will provide better
opportunities and guidance in future in developing projects independently.

BENEFITS:

The project is identified by the merits of the system offered to the user. The merits of this project
are as follows: -

Its a web-enabled project.

This project offers user to enter the data through simple and interactive forms. This is very
helpful for the client to enter the desired information through so much simplicity.
The user is mainly more concerned about the validity of the data, whatever he is entering.
There are checks on every stages of any new creation, data entry or updation so that the user
cannot enter the invalid data, which can create problems at later date.
Sometimes the user finds in the later stages of using project that he needs to update some of
the information that he entered earlier. There are options for him by which he can update the
records. Moreover there is restriction for his that he cannot change the primary data field.
This keeps the validity of the data to longer extent.
User is provided the option of monitoring the records he entered earlier. He can see the
desired records with the variety of options provided by him.
From every part of the project the user is provided with the links through framing so that he
can go from one option of the project to other as per the requirement. This is bound to be
simple and very friendly as per the user is concerned. That is, we can sat that the project is
user friendly which is one of the primary concerns of any good project.
Data storage and retrieval will become faster and easier to maintain because data is stored in
a systematic manner and in a single database.
 Decision making process would be greatly enhanced because of faster processing of
information since data collection from information available on computer takes much less
time then manual system.
Allocating of sample results becomes much faster because at a time the user can see the
records of last years.
Easier and faster data transfer through latest technology associated with the computer and
communication.
Through these features it will increase the efficiency, accuracy and transparency,

LIMITATIONS:

The size of the database increases day-by-day, increasing the load on the database back up
and data maintenance activity.
Training for simple computer operations is necessary for the users working on the system.
BIBLIOGRAPHY

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