BLOOD BANK MANAGEMENT APPLICATION USING RULE-

BASED METHOD

AHMAD FADHLAN BIN MAT JOHA

BACHELOR OF COMPUTER SCIENCE

(SOFTWARE DEVELOPMENT)

UNIVERSITI SULTAN ZAINAL ABIDIN

2018

BLOOD BANK MANAGEMENT APPLICATION USING RULE-BASED

METHOD

AHMAD FADHLAN BIN MAT JOHA

Bachelor of Computer Science (Software Development)

Faculty of Informatics and Computing

Universiti Sultan Zainal Abidin, Terengganu, Malaysia

MAY 2018

i

DECLARATION

I hereby declare that this report is based on my original work except for quotations and

citations, which have been duly acknowledged. I also declare that it has not been previously

or concurrently submitted for any other degree at Universiti Sultan Zainal Abidin or other

institutions.

______________________________

Name : Ahmad Fadhlan Bin Mat Joha

Date : .…………………………...…..

ii

CONFIRMATION

This is to confirm that:

The research conducted and the writing of this report was under my supervision.

________________________________

Name : Dr Syarilla Iryani Binti Ahmad Saany

Date : ..................................................

iii

DEDICATION

In the name of Allah, Most Gracious, Most Merciful.

Alhamdulillah with blessed from Allah to ease this project, Blood Bank Management

Application to be completed. I would like to express my gratitude to my beloved supervisor

of this Final Year Project, Dr Syarilla Iryani Binti Ahmad Saany for this suggestion or ideas

and also the valuable guidance and advice that encourage me to complete the system

successfully.

I would like to thank also to all lecturers and ISMSK (PP) group members who helped me

directly and indirectly in many ways. I would like to express my gratitude to my mother,

Wan Maharam Binti Wan Daud, my father, Mat Joha Bin Husin, siblings and friends for

giving me support and encouragement to complete this project and to propose this project

as Final Year Project.

iv

ABSTRACT

In this technological and modern era, people like to interact with their gadget like smart

phone. This proposed system of the Blood Bank Management Application is an application

that mobilize both the manual Blood Bank Management System and ready have web base

Blood Bank Management System. This application intends to manage the donation record

to replace the blood donor red card called Certificate. There are many flaws when keeping

the blood donation record manually. Through manual system, Blood Bank Center always

have a difficult time when their quantity of the blood bank is almost running out. They are

also facing a problem to inform donors about this situation. Besides, the donor might not

have the same blood type as required by Blood Bank Center. This proposed application can

notify the specific donor if the quantity of blood in the blood bank reaches its critical level.

It will notify the donor to come to that particular Donation Center. The rule-based method

has been chosen in this application to solve the problem above. It will filter certain donor

based on their blood group, and last date of donation. Then, the application will notify them

for the next blood donation whenever their blood group is needed at the Blood Bank Center.

v

ABSTRAK

Dalam era moden dan berteknologi ini, manusia suka untuk berinteraksi dengan gajet

seperti telefon pintar. Sistem cadangan Aplikasi Pengurusan Tabung Darah ini merupakan

satu aplikasi yang menaik taraf kedua-dua Sistem Tabung Darah manual dan Sistem

Tabung Darah berasaskan web. Aplikasi ini bercadang untuk menguruskan rekod derma

darah untuk menggantikan kad merah penderma darah yang dipanggil sebagai

“Certificate”. Terdapat banyak kekurangan semasa menyimpan rekod derma darah secara

manual. Melalui sistem manual, Pusat Tabung Darah selalu menghadapi waktu kesukaran

apabila kuantiti tabung darah hampir kehabisan. Mereka juga menghadapi masalah untuk

memaklumkan kepada penderma berkenaan situasi ini. Selain itu, penderma mungkin tidak

mempunyai jenis darah seperti yang diperlukan oleh Pusat Tabung Darah. Aplikasi

cadangan ini boleh memberitahu penderma tertentu jika jumlah darah dalam Pusat Tabung

Darah mencecah tahap kritikal. Ia akan maklumkan penderma untuk datang ke Pusat Derma

Darah tersebut. Kaedah “Rule-Based” telah digunakan dalam aplikasi ini bagi

menyelesaikan masalah diatas. Ia akan menapis penderma tertentu berdasarkan jenis darah

mereka, dan tarikh terakhir menderma. Seterusnya, aplikasi ini akan memaklumkan mereka

untuk menderma darah di Pusat Tabung Darah sekiranya jenis darah tersebut diperlukan.

vi

TABLE OF CONTENT

DECLARATION i

CONFIRMATION ii

DEDICATION iii

ABSTRACT iv

ABSTRAK v

LIST OF TABLES viii

LIST OF FIGURES ix

LIST OF ABBREVIATION/TERM/SYMBOLS xi

LIST OF APPENDICES xii

CHAPTER 1 INTRODUCTION 1

1.1 Project Background 1

1.2 Problem Statement 2

1.3 Objective 2

1.4 Scope 3

1.5 Limitation Of Work 4

CHAPTER 2 LITERATURE RIVIEW 5

2.1 Introduction 5

2.2 Blood Bank Management System Using Rule-Based Method 6

vii

2.3 A Rule-Based Decision Support System for Evaluating and Selecting IS

Projects. 7

2.4 Friends2Support.org Mobile Application 8

CHAPTER 3 METHODOLOGY 10

3.1 Introduction 10

3.1.1 Verification Phases 11

3.1.2 Coding Phase 12

3.1.3 Validation Phases 12

3.2 Requirement 13

3.2.1 Software Requirement 13

3.2.2 Hardware Requirement 14

3.3 System Design 15

3.3.1 Framework Design 15

3.3.2 Architecture Design 16

3.3.2.1 Data Dictionary 16

3.3.3 Interface Design 21

3.3.3 Process Model 25

3.3.3.1 Contact Diagram 25

3.3.4 Data Model 26

3.3.4.1 Data Flow Diagram (DFD) level 0 26

3.3.4.2 Data Flow Diagram (DFD) level 1 27

3.3.4.3 Entity Relationship Diagram (ERD) 30

REFERENCES 31

APPENDIX A (GANTT CHART) 33

viii

LIST OF TABLES

TABLE TITLE PAGE

3.1 Software Requirement 13

3.2 Hardware Requirement 14

ix

LIST OF FIGURES

FIGURE TITLE PAGE

2.1 Admin Main Page 6

2.2 The application shown at Play Store 8

3.1 V-Shape Model System Development Life Cycled 10

3.2 System Framework for Blood Bank Management Application 15

3.3 user Table 16

3.4 donor Table 17

3.5 staff Table 18

3.6 donation Table 19

3.7 bloodbank Table 20

3.8 Login Interface 21

3.9 (a) Admin main page

(b) Register new staff page

22

3.10 (a) Main page for staff

(b) Add Donation page

23

3.11 (a) Page for donor to register to the apps 24

x

(b) Donor’s Red Card

3.12 Contact Diagram (CD) 25

3.13 Data Flow Diagram (DFD) level 0 26

3.14 DFD Level 1 (Process 1.0) 27

3.15 DFD Level 1 (Process 2.0) 28

3.16 DFD Level 1 (Process 3.0) 29

3.17 ERD for Blood Bank Management Application 30

xi

LIST OF ABBREVIATION/TERM/SYMBOLS

CD Context Diagram

DFD Data Flow Diagram

FYP Final Year Project

xii

LIST OF APPENDICES

APPENDIX TITLE PAGE

A Gantt Chart 33

1

CHAPTER 1

INTRODUCTION

1.1 Project Background

This project Blood bank Management Application is developed for the mobile

operating system (or mobile OS), such as Android OS. A mobile OS is compatible

support various features like Web Browser, Email, Bluetooth and etc. It is also a

platform so developers can create applications or 'apps' (software programs developed

for smartphones that can carry out specific functions).

Blood Bank Management Application is a mobile application used by the

hospital or a blood center. The system developed to promote the important of blood

donation and also serve as a medium for public to increase their awareness on blood

donation that can save many lives. This system have function use in notification to

alert the donors about the critical blood needed by the hospital by sending notification

to them. Besides, this application also can keep the donation record of the donor.

2

This application goal is to save time and ease the blood bank management in

hospital. Moreover, donors no need to open the laptop or computer to check about the

blood donation information. Thus, all of the problem above is consuming a lot of time.

1.2 Problem Statement

Currently, the availability of mobile application for Blood Bank Management

is not wide, thus, it is done manually using traditional method. This will lead to the

problems where the staff hard to search for the blood donation record. The record can

be stored inside the application. Besides, donor did not know if the blood bank center

need the blood of their type. With this Blood Bank Management Application, blood

bank staff can manage the donor information in their phone and this will save a lot of

times. Moreover, the application will notify the donor if the blood quantity at the

hospital are critical. This can encourage donor to come to the hospital and donate their

blood.

1.3 Objective

There are the objectives in this project to be achieve to make this project

successfully complete:

To design an application that records blood donation as the alternative to replace

the traditional way of recording Red Book Certificate.

To provide a platform for publicize and advertise the advantage of blood donation

to encourage people to donate blood.

3

To develop an application than can be used to notify the donor that has the same

type of blood that hospitals need.

1.4 Scope

The scope for this system is divided into four which are administrator, blood bank

staff, and donor.

1. Admin

Manage Blood Bank Staff.

2. Blood Bank Staff

Manage Profile.

Manage Donation

Manage Blood Bank

Manage Donor

3. Blood Donor.

Manage registration and profile.

View blood donation record

Receive notification of blood critical demand

4

1.5 Limitation Of Work

There are some limitation of work since the proposed system is only cover certain

aspects.

1. The system only cover English language. It did not support other languages.

2. There is no real time interaction between donor and blood bank staff in the system.

3. This application need human intervention to update the quantity of blood in the

hospital.

5

CHAPTER 2

LITERATURE REVIEW

2.1 Introduction

In the literature review, it discusses about the previous journal and research paper.

The purpose of writing literature review is to provide background for the topic choose

using previous research that has been done.

6

2.2 Blood Bank Management System Using Rule-Based Method

Figure 2.1 Admin Main Page

This web-based system is developed to computerize the blood bank management

system in a hospital blood bank in order to manage the records of blood donors, blood

donation campaign announcement and broadcast message about critical blood demand to

donors. This Blood Bank Management System Using Rule Based method to store database

on blood donation and making notification on campaign and critical blood demand.

The advantages of the system would be as follows:

1. Access to the system secured by login.

2. This system filter the people that want to donate blood. So that the right people only

can login as a donor.

3. Donor will be noticed if the blood quantity reach critical.

4. Donor also will be informed if there are blood donation campaign around

Terengganu.

7

2.3 A Rule-Based Decision Support System for Evaluating and Selecting IS

Projects.

This paper presents a rule-based decision support system (DSS) for facilitating the

adoption of the most appropriate multi-criteria analysis (MA) method in solving

information systems (IS) project evaluation and selection problems. A knowledge base

consisting of IF-THEN production rules is developed for assisting with a systematic

adoption of the most appropriate MA method through considering the decision maker’s

requirements in project selection with the efficient use of the powerful reasoning and

explanation capabilities of DSS. The idea of letting the problem to be solved determines

the method to be used is incorporated into the DSS development. As a result, effective

decisions can be made for solving the IS project evaluation and selection problem. An

example is presented to demonstrate the applicability of the proposed DSS for solving the

problem of evaluating and selecting IS projects in real world situations.

The advantages of the rule-based decision support system (DSS) would be as follows:

1. Flexibility to respond quickly to the decision maker’s questions.

2. The ability to help the decision maker better understand the decision problem

and the implications of their decision behaviors.

3. The capability to accommodate various requirements of the decision problem

and the decision maker.

8

2.4 Friends2Support.org Mobile Application

Figure 2.2 The application shown at Play Store

This application are developed to become a platform for recipient to find available

donor easily arround them until around the world. Person who become the donor are listed

in the system. Recepient can search any blood type and the choose the location of the donor.

The system will filter it and display the donor that has the same blood type.

The advantages of the system would be as follows:

1. This application have strong privacy control.

2. It contain a lot of facts about blood donation.

9

3. People can do report if the donor phone number are not available anymore.

The disadvantage of the application is:

1. This application only available for 6 countries only in the world.

2. Not many donor registered in this application except people in India.

3. The interface is less attractive and not really friendly.

10

CHAPTER 3

METHODOLOGY

3.1 Introduction

Figure 3.1 below show the V-process Model that are chosen in developing this final

year project. It is known as Verification and Validation model. This model are selected

because of every single phase in the development cycle, there is a directly associated testing

phase.

Figure 3.1 V-Shape Model System Development Life Cycled

11

3.1.1 Verification Phases

Verification focuses on development. There are several verification phase in this V-

process Model such as:

1) Requirement Analysis

Requirement Analysis is the first phase on the cycle. At this phase, requirement are

collected by analyzing the needs of the users.

2) Functional Specification

Developing the plan for the system design or blueprint, including requirements for

hardware, software and network for the system under development.

3) Architectural Design

This is also referred to as High Level Design (HLD). HLD phase focuses on system

architecture and design. It provide overview of solution, platform, system, product

and service/process.

4) Detail Design

Detail Design phase can also be referred to as low-level design. The designed

system is broken up into smaller units or modules and each of them is explained so

that the programmer can start coding directly. The low level design document or

program specifications will contain a detailed functional logic of the module.

12

3.1.2 Coding Phase

At this point, halfway through the stages along the process, the actual coding and

implementation occur. This period should allot for as much time as is necessary to convert

all previously generated design and specification docs into a coded, functional system. This

stage should be fully complete once the testing phases begin.

3.1.3 Validation Phases

Validation Phases ensures that all that development was carried out correctly. This

process is very dynamic and a great deal of testing takes place. These steps are also referred

to as the 'tester's life cycle.'

1) Unit Testing

In the V-Model, Unit Test Plans (UTPs) are developed during module design phase.

These UTPs are executed to eliminate bugs at code level or unit level. A unit is the

smallest entity which can independently exist, e.g. a program module. Unit testing

verifies that the smallest entity can function correctly when isolated from the rest

of the codes/units.

2) Integration Testing

Integration testing is associated with the architectural design phase. Integration tests

are performed to test the coexistence and communication of the internal modules

within the system.

13

3) System Testing

System testing is directly associated with the system design phase. System tests

check the entire system functionality and the communication of the system under

development.

4) Acceptance Testing

Lastly, acceptance testing is the process of implementing all tests created during the

initial requirements phase and should ensure that the system is functional in a live

environment with actual data, ready for deployment.

3.2 Requirement

3.2.1 Software Requirement

SOFTWARE DESCRIPTION

MySQL (phpMyAdmin ) A software to run database of the system.

XAMPP Server A localhost to run phpMyAdmin

MySQL ( Workbench ) A software to create databases and tables

Microsoft Word 2013 A software to write the report.

UC Browser A browser to open the application.

Notepad++ Use to create PHP code program.

Visual Studio Code A software to create Ionic code (HTML, JS, and

SCSS)

Command Prompt Use to run the Ionic code and to deploy the

application into smart phone.

Table 3.1 Software Requirement

14

3.2.2 Hardware Requirement

Table 3.2 Hardware Requirement

HARDWARE DESCRIPTION

Laptop Laptop that used to build the system

Memory :4GB RAM RAM of the laptop.

USB cable Used to connect between the Smart phone and

laptop.

Smart Phone Smart phone will kept the application and test

the application.

15

3.3 System Design

3.3.1 Framework Design

Figure 3.2 System Framework for Blood Bank Management Application

Figure 3.2 shows about the framework of the system which consists of entities involves and

the flow of the system generally.

16

3.3.2 Architecture Design

3.3.2.1 Data Dictionary

a) User Table

Data Dictionary for Blood Bank Management Application consists of five entities such as

user, staff, donor, donation and bloodbank. Figure 3.3 shows the data dictionary for user.

Tthere are two attributes consists in the table which are userID, userPassword. userID is

the primary key for this table.

Figure 3.3 user Table

17

b) Donor Table

In Figure 3.4 below, there are fourteen attributes consists in the table which are donorID,

donorName, address, address2, postcode, city, state, bloodType, rhesus, phoneNo,

donorIC, gender, weight, donorQualification. donorID is the primary key for this table.

Figure 3.4 donor Table

18

c) Staff Table

In Figure 3.5, there are ten attributes consists in the table which are staffID, staffName,

position, address, address2, postcode, city, state, phoneNo, gender. staffID is the primary

key for this table

Figure 3.5 staff Table

19

d) Donation Table

In Figure 3.6, there are nine attributes consists in the table which are donorID, dateDonate,

bloodSeriesNo, bloodType, rhesus, donationType, amount, place. donorID, dateDonate

and bloodSeriesNo is the composite primary key for this table.

Figure 3.6 donation Table

20

e) Blood Bank Table

In Figure 3.7, there are six attributes consists in the table which are bloodSeriesNo, amount,

bloodType, rhesus, dateUpdate and dateExpire. bloodSeriesNo is the primary key for this

table.

Figure 3.7 bloodbank Table

21

3.3.3 Interface Design

Interface design is a communication display between system and user. In this project,

the interface design is sketched using mockup design. The real design of the system should

look almost the same with this design. The interface design should lead user to navigate the

system easily. It will make the user understand the flow of the system. One of the important

aspect of interface design is user friendliness, user can understand what need to do on every

pages. Besides, the interface also must be consistent in design such as color, button, and

many more.

a) Interface for all user

Figure 3.8 Login Interface

Figure 3.8 above show the login interface of the blood Bank Management Application that

every actor see before go through the application.

22

b) Admin interface

Figure 3.9 (a) Admin main page Figure 3.9 (b) Register new staff page

Figure 3.9 (a) above show the interface that will be show to admin. Admin can tap at profile

to view profile. Admin also can manage the blood bank staff and view staff report. Figure

3.9 (b) show that the form that admin need to fill to register new blood bank staff.

23

c) Blood Bank Staff Interface

Figure 3.10 (a) Main page for staff Figure 3.10 (b) Add Donation page

Figure 3.10 show the example of Blood Bank Staff interface. Staff interface also provide

staff profile page, Manage page and view report page. Figure 3.10 (a) is the interface for

blood bank staff to select Manage Donor, Manage Donation, and Manage Blood Bank.

Figure 3.10 (b) is the interface for adding donation in Manage Donation.

24

d) Donor Interface

Figure 3.11 (a) show the Donor interface when the donor want to register into the Blood

Bank Management Application. Figure 3.11 (b) show the donation record of the donor.

Donor also can manage their profile and read the information about blood bank.

Figure 3.11 (a) Page for

donor to register to the apps

Figure 3.11 (b) Donor’s Red

Card

25

3.3.3 Process Model

3.3.3.1 Contact Diagram

Figure 3.12 Contact Diagram (CD)

The Blood Bank Management Application consists of 3 actors as shown in Figure 3.12

which are Administrator, Staff, and Donor. All of these actors need to login into the

application before able to access their interface. Admin make registration of the staff into

the system. The Staff is able to manage profile, manage staff details, manage blood

donation, manage donor, manage blood bank and view report. As for Donor need to register

before use this application. Donor also can manage profile, view the blood donation record,

receive the notification of critical blood demand and view report.

26

3.3.4 Data Model

3.3.4.1 Data Flow Diagram (DFD) level 0

Figure 3.13 Data Flow Diagram (DFD) level 0

A Data Flow Diagram (DFD) level 0 is a diagram of a flow of data through an application.

In Figure 3.13, there are four processes involved. Processes in this system consist of

manage staff, manage donor, manage blood bank, and manage blood donation. There are

four data store involved in this application which are staff, donor, bloodbank and donation

data store.

27

3.3.4.2 Data Flow Diagram (DFD) level 1

Figure 3.14 DFD Level 1 (Process 1.0)

Figure 3.14 shows the detail process for admin to manage staff. In managing the staff,

administrator is able to Register Staff, Update Staff Record, Delete Staff, and View Staff.

The detail of blood bank staff is stored in STAFF data store.

28

Figure 3.15 DFD Level 1 (Process 2.0)

Figure 3.15 shows the detail process manage donor. In managing donor, the donor is able

to view profile, register and update donor. The staff is able to vie donor, delete donor, and

update donor. The detail of the donor is then stored in DONOR data store.

29

Figure 3.16 DFD Level 1 (Process 3.0)

Figure 3.16 shows the detail process for staff to manage blood donation. In managing the

blood donation staff is able to add blood donation and search for blood donation record.

The detail of the blood donation is stored in DONATION data store.

30

3.3.4.3 Entity Relationship Diagram (ERD)

Figure 3.17 below show the ERD of the system. It shows all the entities involve in

the database of the Blood Management Application. All the updated data in the data store

is self-updated by user.

Figure 3.17 ERD for Blood Bank Management Application

31

REFERENCES

Journal

[1] Sara A. Hashim, Afnan M. Al-Madani, Shatha M. Al-Amri, Abeer M. Al-Ghamdi,

Bayan S. Bashamakh. Nahla Aljojo, PhD (2014). Online Blood Donation

Reservation And Managementsystem In Jeddah. Life Science Journal.

[2] K M Akkas Ali, Israt Jahan, Md. Ariful Islam, Md. Shafa-at Parvez (2015). Blood

Donation Management System. American Journal of Engineering Research

(AJER).

[3] Prathamesh Raut, Prachi Parab, Yogesh Suthar, Sumeet Narwani, Sanjay Pandey

(2016). Blood Bank Management System. International Journal of Advanced

Computational Engineering and Networking.

[4] Ashita Jain, Amit Nirmal, Nitish Sapre, Prof Shubhada Mone (2016). Online Blood

Bank Management System using Android. International Journal of Innovative

Studies in Sciences and Engineering Technology (IJISSET).

[5] Prof. Snigdha, Varsha Anabhavane, Pratiksha lokhande, Siddhi Kasar, Pranita More

(2015). Android Blood Bank. International Journal of Advanced Research in

Computer and Communication Engineering (IJAECCE).

32

Webpages

[6] Rule Based System, 2008. Suresh Sambandam, Founder of OrangeScape & CEO at

KiSSFLOW. https://www.slideshare.net/sureshsambandam/rule-based-system-

presentation. Access on 20 May 2018.

Thesis

[7] Fazlin Liyana Binti Mohammed Wadzir, 2017. Title of Degree, Universiti Sultan

Zainal Abidin. Blood Bank Management System Using Rule-Based Method.

33

APPENDIX A (GANTT CHART)

FYP 1 Schedule

Duration

Task

February March April May

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Topic Discussion and

Determination

Project Title Proposal

Proposal Writing – Introduction

Proposal Writing - Literature

Review

Proposal Progress Presentation

& Evaluation

Discussion & Correction Proposal

Proposed Solution Methodology

Proof of Concept

Drafting Report of the Proposal

Submit draft of report to

supervisor

Seminar Presentation

Report Correction

Final Report Submission