PROJECT NAME

“BLOOD DONATION MANAGEMENT SYSTEM”

BLOOD DONATION MANAGEMENT SYSTEM

SUBMITTED BY

BILAL BUTT
(0053)

University of Central Punjab Faisalabad

AL-QURAN
Without His help and His will, nothing can be done so
we’re grateful to ALLAH who gave is the strength and
courage to complete the project

CERTIFICATE
It is hereby declared that BILAL BUTT student of BSCS has completed
her project BLOOD DONATION MANAGEMENT SYSTEM.

-------------------- --------------------

Supervisor External Examiner

Mrs. Tahira
Computer Department

DEDICATION
 I dedicate this project

To
My dearest and respected Parents, who supported me throughout
my academic career ton achieve the passion

To

My respected and honorable teacher (SIR K NAAM) who

taught me and guided me making this project

To

My friends who always guide and encourage me and make

me feel comfortable even at toughest times

PROJECT BRIEF
 Project Title: Blood Donation Management System

Undertaken By: Bilal Butt

Supervised By: *(Sir K Naam)*

Submission Date: February 2018.

 CHAPTER#1

Objective:
The main objective of the system was to create electronic blood
donation management system in order to assist in management
of blood donor records planning and share information in a more
confidential, convenient and secure way using modern
technology
 CHAPTER#2

Existing System:
Blood donation management system is currently working manually, so following
are the problems that the department is facing:

 A manual record keeping system generate data redudancy problem. Redundancy

means that same data is duplicated in many different files. Sometimes record is
stored on many registers and cards, which are very difficult to handle and whenever
it is required to enter or retrieve some information from these record keeping register
and cards. It is very lengthy procedure to work on.

 Problems of redundancy lead to problem of inconsistency. It means that data has to

update in each separate file when it changes. For example, the department file may
be change address of the staff but the staff file may be fail to update its files and so
producing reports will contain out of data figures.

 File processing system is not very flexible. It cannot easily generate the information
that is different from routine. It can take a lot of time to collect the data from
different files and write programs to produce the desired information.

 Extensive skilled workforce is required to maintain the records and keeps the system
working in proper fashion. It is impossible to handle such an organization record
manually with out this work.

 If one department had data that was required by another department it was awkward
to obtain accuracy of data.

 The store data must satisfy certain type of consistency constraints. For example, roll
no. and marks of students should be numeric value. It is very difficult to apply these
constraints on files in file processing system.

 The data is very insecure because all the data is on registers and cards in the form of written
entries. It is quite easy to alter the data stored at any given time. There is no such security provided
to different user at different times. Therefore, it is quite risky to keep important data in this
manner.
 CHAPTER#3

Proposed system:
Proposed system is used to maintain the accurate and complete records. This system
will be computerized system that facilitates the user of the system and overcome the
drawbacks of the existing system. For developing computerized database we are
using MS access as DBMS. A database management system is a collection of
programs that facilitates of defining construction and manipulating database for
various applications. The proposed system is mainly based on the purpose of giving
a more sophisticated convenience to the administration.
A database is a collection of logically related facts. By facts we mean the data that
can be recorded and that have implicit meanings.

Features of The Proposed System

The main features of the proposed system are:

 All relevant data will be accessible by all related applications. This will
reduce the data redundancy and in-consistency.

 Only the authorized person will be able to access these records. It means that
this system will provide data security.

 Our computerized database will provide the facility for backup and recovery
of data in case of data loss or damage.

 This system will generate report for a specific data, so we can say that this
system is flexible. This system will reduce integrity problems as there will be
more accuracy to manipulate the records.

 This system will allow the user to design complex data structures. It also
means that database can be extended in future.

 This system will be easy to operate for every user of the database.
 Gr
CHAPTER#4

ENTITY RELATIONSHIP DIAGRAM

Introduction
1. An ERD is a model that identifies the concepts or entities that exist
in a system and the relationships between those entities. An ERD is
often used as a way to visualize a relational database. Each entity
represents a database table, and the relationship lines represent the
keys in one table that point to specific records in related tables.
ERDs may also be more abstract, not necessarily capturing every
table needed within a database, but serving to diagram the major
concepts and relationships.
Understanding the Model
2. There are several different systems for entity relationship
diagramming namely:-

a. Entities
Each entity is represented by a box within the ERD. Entities are
abstract concepts, each representing one or more instances of the
concept in question. Entities are equivalent to database tables in a
relational database, with each row of the table representing an
instance of that entity.

The diagram below has an entity for “student” and another for
“school”. This indicates that the system being modeled may contain
one or more students and one or more schools

STUDENT SCHOOL
So far, no relationship between students and schools has been
indicated.
 b. Relationships

Relationships are represented by lines between entities. Relationship

lines indicate that each instance of an entity may have a relationship
with instances of the connected entity, and vice versa.

STUDENT SCHOOL

The diagram above now indicates that students may have some
relationship with schools. More specifically, there may be a
relationship between a particular student (an instance of the student
entity) and a particular school (an instance of the school entity).
 ERD FOR BLOOD DONATION MANAGEMENT
SYSTEM

BLOOD is donated by

ISSUE BLOOD will

DONORS

Is stored in

to

BLOOD BANK have EMPLOYEES

PATIENT ATTENDENT

for

Is admitted
PATIENT in HOSPITAL has WARDS

Staffed by
Is treated by
Is in

DOCTOR NURSES
 BLOOD

Blood
Group

ID Rh Factor

BLOOD
Blood Date/Time
Bank ID

Donor ID

DONOR

Fathe
Name
ID r
Age

Blood ID Contact
DONOR Number

City Address

Blood Group Gender

CNIC
 Issue Blood

Blood
ID

Quantity
Blood
ID
ISSUE BLOOD
Date

Patient
ID Amount

Blood Bank

Registratio Name Contact

n ID Number

BLOOD BANK Addres

s

Donor Blood ID
ID
 Patient Attendant

Name Father
Patient ID Name

Contact
Number

PATIENT ATTENDENT
Issue
Blood

CNIC Gende Addres

r s

Patient

Name Father
Age
ID

Blood Contact
Number
Patient
City
Addres

Doctor
Gender
ID
Diseas CNI
 Doctor

Father Name
Name
Age
ID CNIC

Contact
Hospital Reg.ID
DOCTOR
Specializatio Addres

Experienc Nationalit
e Qualificatio

Hospital

Name
Contact Number
Registration
ID

Address
Ward
Number
HOSPITAL
 Nurses

Father Name
Nam
e
Age
ID

CNI
C
Hospital
Reg.ID NURSE
Shift

Ward
Numbe Contac
Addres t
s

Employees

Name Father
Name
Age
ID

CNIC
EMPLOYEE

Blood
Bank ID Contact
Numbe
Addres
s
 Ward

Numbe Name
r

No. of Nurses WARD Patient ID

No. of Beds
 CHAPTER#4
DATA BASE OBJECTS
1. TABLES
 Blood info
Blood contains information about blood and Rh-factor involved in
blood. Design view of the Blood table is:

Description
This table includes fields like Blood Group, Rh-factor, Id, Date and
Day
 Donors Info
This table contains personal information of Donors.

Description
This table contains fields related to donors like Id, Name, F.Name,
Age, Contact, Adress, Gender, CNIC, Blood Group, City
 Blood bank Info
This table contains data about Blood Bank.

Description
This table contains fields that are: Name, Reg.Id, Contact, Adress
 Issue Blood
This table contains data related to the issuance of the blood.

Description
This table contains fields of Patient Id, Date, Quantity, Id, Blood
group, Amount
 Patient Attendant Info
This table contains information about Patient Attendant.

Description
This table contains fields of Patient Id, Name, F.Name, Contact,
Address, Gender, CNIC
 Patient Info
This table contains information about Patient.

Description
This table contains fields that are: Id, Name, F.Name, Age, Contact, Adress,
Gender, CNIC, Disease, Doctor’s Id, City, Blood Group, Bed No
 Doctor Info
This table contains personal information about Doctor.

Description
This table contains fields of Id, Name, F.Name, Age, CNIC, Contact, Adress,
Nationality, Qualification, Specialization, Hospital Id.
 Hospital Info
This table contains information about Hospital.

Description
This table contains fields that are: Reg. Id, Adress, Name, Contact.

 Nurses Info
 This table contains personal information about Doctor.

Description
This table contains fields of Id, Name, F.Name, Age, CNIC, Shift, Contact,
Adress, Ward No, Hospital, Reg. Id
 Ward info
Ward contains details about Ward present in the hospital. Design
view of the Ward table is:

Description
This table includes fields like Number, Name, Patient Id, no. Of
beds and No. Of nurses
 Employees info
Employees contain information about the Employees that works in
the Hospital.

Description
This table contains fields related to employees like Id,
Name, F.Name, Age, Contact, CNIC
2. RELATIONSHIPS

Relationships are formed so that the linkage of tables in a

particular group can be specified. This also establishes relationship
of data in one table with other. The main table with which the other
tables form relationship is Blood. This is because it contains the
main information regarding the project. The relationships are:-
3. FORMS

A graphical interference use to interact with the database is called Forms.

Forms are use to enter data in the database. A Form consists text boxes,
buttons, labels and other graphical objects. These objects enable the user to
interact with the database easily. The user can also retrieve, change, delete
and update by using forms. The application programmers create the user
interface by designing forms in different ways.

 Blood
  Donors

 Blood bank
 Issue Blood

 Patient Attendant Info

 Patient Info
 Doctor
 Hospital Info
 Nurses
 Wa





 Ward
 Employees
4. QUERIES

A query is statement that extracts specific information from database.

Queries are used to retrieve the required data from database. Data is
retrieved according to the criteria given by the user. It is more flexible way
of selecting, filtering and sorting records.
The query is written in database access language.
The most commonly used query language is SQL. Query retrieves data from
the database and displays it in the form of tables. The user can also change
data in the database by using queries. Queries can also be used to perform
calculations on different fields. The output of query can be used as a source
of records for forms & reports.
A query is used to view and analyze data in my
ways. It is actually a stored question or request. The queries are designed in
design view of MS Access.

 Blood / Blood Bank

 Donors
 Issue Blood
 Doctor / Hospital
 Disease
 Patient
  Issue blood / Patient Attendant

5. REPORTS
Reports are the outputs of database application. Reports are used to retrieve
and present data in a formatted way. The information on reports is arranged
in different ways. A report may also contain graphs, charts and tables etc.
The user can generate different types of reports by manipulating database.
Some reports are simple a list of the record in database.
Reports are very important in making key decision.
The user can print reports to send them to different people. The output of a
query can also be used as source for reports. Most of the DBMS provide
facility reports.

Advantages:
Some important advantages of reports are as follows:
 Reports provide quick result from databases.
 Reports help in making important decisions.
 Reports can display processed data using graphs and charts etc.
 Reports can easily be printed or emailed easily.

Disadvantages:
Some important disadvantages of reports are as follows:
 The data in the reports cannot be modified.
 The user cannot add new data using reports.
 The data in the reports cannot be deleted.

 Blood
 Donors
 Blood bank
 Issue Blood
 Patient Attendant Info
 Patient Info
 Doctor
 Hospital Info
 Nurses
 Ward
 Employees