HAWASSA UNIVERSITY 2ND YEAR COMPUTER SCIENCE

DEPARTMENT EVENING PROGRAM DATABASE GROUP

ASSIGNMENT

TITLE:

BLOOD DONATION MANAGEMENT

DATABASE SYSTEM PROJECT

GROUP NAME ID NUMBER

1. YIDIDIYA KASSA----------------------------------------------0090/14E.C
2. WUBSHET NIGUSE------------------------------------------00
3. ANDUALEM GESESE---------------------------------------
4.
5.
  INTRODUCTION
The blood donation management system is a software application designed to help blood
donation centers manage their operations efficiently and effectively. The system includes
several key features, including donor management, blood type management, donation
management, administrative management, and communication management. The system is
designed to be user-friendly and easy to use, with a graphical user interface that allows users to
enter and retrieve information quickly and easily.

The blood donation management system is an essential tool for blood donation centers of all
sizes. The system helps to ensure that blood donation operations are managed efficiently and
that blood products are easily accessible to patients in need. The system also helps to
streamline administrative processes and improve communication between different
departments, leading to a more efficient and effective blood donation center experience for
everyone involved.

The database design for the blood donation management system is a critical component of the
project. The database is designed to store and manage all of the necessary information in an
efficient and effective manner. The database design includes an entity-relationship diagram,
tables, relationships, data types, and indexes. The design must be carefully planned and
executed to ensure that the database is efficient, effective, and easy to use.

Overall, the blood donation management system is a critical software application that helps
blood donation centers manages their operations effectively and efficiently. The system is
designed to be user-friendly and easy to use, with a focus on donor management, blood type
management, donation management, administrative management, and communication
management. The system is an essential tool for blood donation centers of all sizes, helping to
ensure that blood products are easily accessible to patients in need.

Blood Donation database system have user friendly interface. This system also has the
queries option.

 Problem: storage time accuracy efficiency

1. This system is manual.
2. Manually data entry has a chance of inaccuracy.
3. Manual data entry in inefficient.
4. Wastage of time
 Solution
1. It will be the computer base system
2. Data entry become more efficient

HAWASSA UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE 2ND YEAR EVENING PROGRAM

DATABASE ASSIGNMENT 2015E.C
Page 2
 3. Reduction of errors
4. No wastage of time

DATA REQUIREMENT
 Entity

In total we have eight entities and information of each entity is mentioned below:-

1. Blood Donor:
Blood donor is the person who donates blood, on donation.
2. Blood type: This table stores information about the different blood types that are
available for donation.
3. Donation: This table stores information about the blood donations that have been
made by donors.
4. Administrative: This table stores information about the administrative staff who work
at the blood donation center.
5. Communication: This table stores information about the communication that takes
place between the blood donation center and donors or other stakeholders.
 Attributes
1. Blood Donor: donors class have 6 attributes
i. BD_ID
ii. BD_name
iii. bd_sex
iv. BD_age
v. BD_Bgroup
vi. BD_reg_date
2. Blood type: blood type class have 3 attributes
i. BT_ID
ii. BT_name
iii. BT_status
3. Donation: Donation class have 3 attributes
i. Donation_ID
ii. Donation_date
iii. Quantity of blood donated
4. Administrative: Administrative class have 3 attributes
i. Staff ID
ii. Staff _Name
iii. Staff_phNo

HAWASSA UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE 2ND YEAR EVENING PROGRAM

DATABASE ASSIGNMENT 2015E.C
Page 3
 5. Communication: Communication class have 3 attributes
i. Communication_Id
ii. Sender_Id
iii. Date/time

 ER DIAGRAM

BD_ID BD_NAME

BLOODDONOR
BD_AGE

BD_SEX
BD_REG_DATE

BT_ID
BD_Bgroup

Blood type

BT_NAME

BT_STATUS

HAWASSA UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE 2ND YEAR EVENING PROGRAM

DATABASE ASSIGNMENT 2015E.C
Page 4
 DONATION_ID

DONATION

DONATION DATE

QUANTITY OF BLOOD
DONATED

STAFF_ID

ADMNISTRATIVE

STAFF_Ph_NO
STAFF_NAME

HAWASSA UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE 2ND YEAR EVENING PROGRAM

DATABASE ASSIGNMENT 2015E.C
Page 5
 COMMUNICATION_ID

SENDER_ID

COMMUNICATION

DATE/TIME

 FUNCTIONAL DEPENDENCY AND NORMALIZATION

There are following tables for normalization

1. BLOOD DONOR

HAWASSA UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE 2ND YEAR EVENING PROGRAM

DATABASE ASSIGNMENT 2015E.C
Page 6
 {BD_ID} = > {BD_NAME} (functional dependency exists, because two different
BD_NAME do not correspond to the same BD_ID).

{BD_ID} = > {BD_SEX} (functional dependency exists).

{BD_ID} = > {BD_AGE} (functional dependency exists).

{BD_ID} = > {BD_REG_DATE} date (functional dependency exists).

{BD_ID} = > {BD_BGROUP} (functional dependency exists).

i. First Normal Form (1NF): DONOR table has no repeating group so this table
is in 1NF.
ii. Second Normal Form (2NF): there is no partial dependency because
DONOR table has no composite primary key. So this table is already in 2NF.
iii. Third Normal Form (3NF): there is no transitive dependency so this table is
in 3NF.
2. BLOOD TYPE

{BT_ID} = > {BT_NAME} (functional dependency exists).

{BT_ID} = > {BT_STATUS} (functional dependency exists).

i. First Normal Form (1NF): BLOOD TYPE table has no repeating group so this
table is in 1NF.
ii. Second Normal Form (2NF): there is no partial dependency because BLOOD
TYPE table has no composite primary key. So this table is already in 2NF.
iii. Third Normal Form (3NF): there is no transitive dependency so this table is
in 3NF.

HAWASSA UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE 2ND YEAR EVENING PROGRAM

DATABASE ASSIGNMENT 2015E.C
Page 7
 3. DONATION

{DONATION_ID} = > {DONATION DATE} (functional dependency exists)

{DONATION_ID} = > {QUANTITY OF BLOOD DONATED} (functional dependency
exists)

i. First Normal Form (1NF): DONATION table has no repeating group so this
table is in 1NF.
ii. Second Normal Form (2NF): there is no partial dependency because
DONATION table has no composite primary key. So this table is already in
2NF.
iii. Third Normal Form (3NF): there is no transitive dependency so this table is
in 3NF.
4. ADMNISTRATIVE

{STAFF_ID} = > {STAFF_NAME} (functional dependency exists).

{STAFF_ID} = > {STAFF_PH_NO} (functional dependency exists).

i. First Normal Form (1NF): ADMNISTRATIVE table has no repeating group so

this table is in 1NF.
ii. Second Normal Form (2NF): there is no partial dependency because
ADMNISTRATIVE table has no composite primary key. So this table is already
in 2NF.
iii. Third Normal Form (3NF): there is no transitive dependency so this table is
in 3NF.

HAWASSA UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE 2ND YEAR EVENING PROGRAM

DATABASE ASSIGNMENT 2015E.C
Page 8
 5. COMMUNICATION

{COMMUNICATION_ID} = > {DATE/TIME} (functional dependency exists).

i. First Normal Form (1NF): COMMUNICATION table has no repeating group

so this table is in 1NF.
ii. Second Normal Form (2NF): there is no partial dependency because BLOOD
COMMUNICATION table has no composite primary key. So this table is
already in 2NF.
iii. Third Normal Form (3NF): there is no transitive dependency so this table is
in 3NF.

 SAMPLE SQL QUERIES

 BLOOD DONATION

HAWASSA UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE 2ND YEAR EVENING PROGRAM

DATABASE ASSIGNMENT 2015E.C
Page 9
  BLOOD TYPE

 DONATION

 ADMNISTRATIVE

 COMMUNICATION

HAWASSA UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE 2ND YEAR EVENING PROGRAM

DATABASE ASSIGNMENT 2015E.C
Page 10
  IMPLEMENTED BY STRUCTURED QUERY LANGUAGE (SQL)

HAWASSA UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE 2ND YEAR EVENING PROGRAM

DATABASE ASSIGNMENT 2015E.C
Page 11
CREATE TABLE BLOOD_DONOR (BD_ID VARCHAR (15), BD_NAME VARCHAR (15),
BD_SEX CHAR (7), BD_AGE VARCHAR (4), BD_BGROUP VARCHAR (3),
BD_REG_DATE DATE);

insert into blood_donor values('111','hayilet','male',

'25','o','5/22/2023')
insert into blood_donor values('222','babi','male',
'19','o-','5/1/2023')
insert into blood_donor values('333','tsion','female',
'25','b+','5/2/2023')
insert into blood_donor values('111','dawit','male',
'20','o','5/3/2023')

select * from blood_donor

CREATE TABLE BLOOD_TYPE (BT_ID VARCHAR (10), BT_NAME VARCHAR (15),

BT_STATUS VARCHAR (8));

insert into blood_type values('111','biniyam','normal')

insert into blood_type values('222','behayilu','normal')
insert into blood_type values('333','misgana','normal')

select * from blood_type

CREATE TABLE DONATION (DONATION_ID VARCHAR (8), DONATION_DATE DATE,

QUANTITY_BLOOD_DONATED VARCHAR (5));

insert into donation values('111','1/4/2023','7')

insert into donation values('222','1/29/2023','11')
insert into donation values('333','1/20/2023','3')

select * from donation

CREATE TABLE ADMNISTRATIVE (STAFF_ID VARCHAR (8), STAFF_NAME VARCHAR

(10), STAFF_PH_NO VARCHAR (15));

insert into admnistrative values('111','lemlem','333')

insert into admnistrative values('222','helen','222')
insert into admnistrative values('333','yaikob','111')

select * from admnistrative

CREATE TABLE COMMUNICATION (COMMUNICATION_ID VARCHAR (8), SENDE_ID

VARCHAR (8), DATE_TIME DATE);

insert into communication values('111','101','5/1/2023')

insert into communication values('222','102','5/2/2023')
insert into communication values('333','103','5/3/2023')

HAWASSA UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE 2ND YEAR EVENING PROGRAM

DATABASE ASSIGNMENT 2015E.C
Page 12
select * from communication

 CONCLUSION
In conclusion, the blood donation management system is a critical software application that
helps blood donation centers manages their operations efficiently and effectively. The system
includes several key features, including donor management, blood type management, donation
management, administrative management, and communication management. The system is
designed to be user-friendly and easy to use, with a graphical user interface that allows users to
enter and retrieve information quickly and easily.

The database design for the blood donation management system is a critical component of the
project. The database is designed to store and manage all of the necessary information in an
efficient and effective manner. The database design includes an entity-relationship diagram,
tables, relationships, data types, and indexes. The design must be carefully planned and
executed to ensure that the database is efficient, effective, and easy to use.

Overall, the blood donation management system is an essential tool for blood donation centers
of all sizes. The system helps to ensure that blood donation operations are managed efficiently
and that blood products are easily accessible to patients in need. The system also helps to
streamline administrative processes and improve communication between different
departments, leading to a more efficient and effective blood donation center experience for
everyone involved.

HAWASSA UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE 2ND YEAR EVENING PROGRAM

DATABASE ASSIGNMENT 2015E.C
Page 13
HAWASSA UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE 2ND YEAR EVENING PROGRAM
DATABASE ASSIGNMENT 2015E.C
Page 14