Final Project Documentation
Final Project Documentation
Centre code:
Index number:
2018
Declaration
I Glenn Mbugua Kinyanjui declare that this is my original work and has
not been presented in any other collage or any other institution of higher
learning for examination purposes.
Signature……………………………………..
Date……………………………………..
SUPERVISOR NAME
Madam C Rose
Signature……………………………………..Date………………………
……………..
Acknowledgement
I acknowledge the almighty God for seeing me through the entire
research. I thank my supervisor, Madam Loraine, for the guidance she gave me
during study time and the project development period. Her valuable
recommendations have guide me to produce a management system that I am
proud to be part of. I also appreciate the support from my family, friends, my
lecturers and classmates for all the support that made it possible for me to
complete this project and the interior diploma course. I would also like to
appreciate those who took part in this project process for their time patience
and support, without their support this work wouldn’t have been a success
Lastly I thank Thika Technical Training Institute administration, lecturers, staff,
and the students for their support.
Abstract
Central blood bank management system is a web application that allows
one to access information about blood donations and request, readily scalable
and adaptable to meet the complex need of blood bank who is the key
facilitator for the health care sector. The system also records information of the
donor and the recipient. The project includes three main forms; admin, donor,
and recipient. The admin forms focuses on both the admin and recipient. Each
member, a donor and acceptor is given a user id and password, which identifies
them uniquely. The member is given a login form to enter the login details.
Each member in the can change the password; inquire on a particular blood
group and information on ‘Why to donate blood’. In this you can store the
information about recipient. The whole project makes work easier for every
person using the software in their required category
Table of Contents
Declaration.................................................................................................................................................2
Acknowledgement.......................................................................................................................................3
Abstract.......................................................................................................................................................4
CHAPTER ONE..............................................................................................................................................8
1.0 Introduction.......................................................................................................................................8
1.1 Background........................................................................................................................................8
1.2 problem statement............................................................................................................................9
1.3 proposed system..............................................................................................................................10
1.4 justification......................................................................................................................................10
1.5 objectives.........................................................................................................................................11
1.6 scope...............................................................................................................................................11
CHAPTER TWO...........................................................................................................................................12
2.0 SYSTEM ANALYSIS AND FEASIBILITY STUDY..........................................................................................12
2.1 introduction.....................................................................................................................................12
2.2 feasibility study................................................................................................................................12
2.2.1 Operation feasibility study........................................................................................................12
2.2.2 Economic feasibility..................................................................................................................13
2.2.3 Technical feasibility...................................................................................................................14
2.3 design methodology........................................................................................................................15
2.3.1 Information gathering (Inception..............................................................................................15
2.3.2 Analysis phase...........................................................................................................................15
2.3.3 Design phase-...........................................................................................................................15
2.3.4 Construction phase-..................................................................................................................15
2.4 Data collection.................................................................................................................................15
2.4.1 Questionnaires..........................................................................................................................16
2.4.2 Observation..............................................................................................................................16
2.5 Data analysis procedure...................................................................................................................17
2.5.1 Questionnaires..........................................................................................................................17
2.5.1.1 Donor Questionnaire sample.................................................................................................17
CHAPTER THREE:.......................................................................................................................................24
SYSTEM DESIGN.........................................................................................................................................24
3.0 Introduction.....................................................................................................................................24
3.1 System design..................................................................................................................................24
3.1.1 Physical design..........................................................................................................................24
3.1.2 Logical design............................................................................................................................28
3.1.3 Process design..........................................................................................................................30
3.1.5 Sequence diagram....................................................................................................................33
3.1.4 OUTPUT DESIGN...........................................................................................................................35
3.6. STORAGE DESIGN............................................................................................................................42
3.6.1Blood donor...............................................................................................................................42
3.6.2 Blood group..............................................................................................................................42
3.6.3 Query........................................................................................................................................43
3.6.4 Donate blood............................................................................................................................43
3.6.5 Request blood...........................................................................................................................43
3.6.6 Recipient...................................................................................................................................43
3.7 INTERFACE DESIGN..........................................................................................................................44
3.7.1 Admin interface........................................................................................................................44
3.7.2 Donor interface.........................................................................................................................44
3.7.3.Recipient interface....................................................................................................................45
CHAPTER FOUR..........................................................................................................................................46
4.0 INTRODUCTION...............................................................................................................................46
4.1 user documentation........................................................................................................................46
4.1.1 Administrator............................................................................................................................46
4.1.2 Donor........................................................................................................................................46
4.1.3 Recipient...................................................................................................................................47
CHAPTER FIVE............................................................................................................................................48
5.0 INTRODUCTION...............................................................................................................................48
5.1 type of test.......................................................................................................................................48
5.1.1 Unit testing...............................................................................................................................48
5.1.2 Integration testing.....................................................................................................................49
5.1.3 Install/ uninstall testing.............................................................................................................49
5.1.4 System testing...........................................................................................................................50
5.1.5 Interface testing........................................................................................................................50
5.1.6 Acceptance testing....................................................................................................................51
6.0 Appendices..........................................................................................................................................52
Appendix I Questionnaire......................................................................................................................52
Appendix II TIME SCHEDULE..................................................................................................................55
Gantt chart Appendix III.........................................................................................................................56
Budget Appendix IV...............................................................................................................................58
Sample code Appendix VI......................................................................................................................59
Manage-blood group sample code........................................................................................................67
CHAPTER ONE
1.0 Introduction
1.1 Background
“……and in other news, the deputy surgical director of Kenyatta National Hospital
, Dr. John Ong’ech, has urged Kenya to come forth and donate blood since the
hospital blood bank is running dry of a specific blood Group and its urgently need
by a patient….”. This are the headline that are in the news in most cases when
disaster has struck the country. This happen because most hospital have manual
database of donors with that specific blood group type but to retrieve such data
would take longer plus to contact the donor to donate blood might be too late for
the patient to survive.
Blood is a body fluid in humans and other animals that delivers necessary
substances such as nutrients and oxygen to the cells and transports metabolic waste
products away from those same cells. A blood bank is a center where blood
gathered as a result of blood donation is stored and preserved for later use in blood
transfusion. Blood transfusion is the process of receiving blood into a person’s
body and it is a practice which for many years has been used to save people’s lives.
The term "blood bank" typically refers to a division of a hospital where the
storage of blood product occurs and where proper testing is performed (to reduce
the risk of transfusion related adverse events). It can also refer to a collection
center, and indeed some hospitals also perform collection. Blood donation
necessitates the availability of blood in the blood banks.
1.4 justification
This project is a web-based database application system that is to be used by
the blood banks or blood centers as a means to advertise the nationwide blood
donation events to the public and at the same time allow the public to make online
request for blood.
The system keeps the record of all the donors, recipients, blood donation programs,
rejected blood. This system also has the ability to keep track of the donor's
donation records and the blood stock in the blood bank. This project intends to
computerize the blood and donor management system in a blood bank in order to
improve the record management efficiency due to the grown size of records of
data.
10
1.5 objectives
I. To allow the probable recipients to make search and match the volunteer
donors, and make request for the blood.
II. To provide an efficient donor and recipient management functions to the
blood bank by recording the donor and blood details.
III. To provide a synchronized and centralized donor and recipient database.
1.6 scope
The system will be a web based application. The system is used for
maintaining all the process and activities of blood bank management system and it
also takes care of the details of the blood donors and recipients. There are several
users with different privileges. Administrator: has full privilege on the system's
functions, Public: can view the blood donation events and donate or can make
requests for donation (Donor and Recipients fall under this category). It has also
the capability to show the history of a donor or recipient.
11
CHAPTER TWO
2.1 introduction
System analysis is the process of gathering and interpreting facts, diagnosing
problem and the information to recommend improvement on the system. The
system analyst play the role of the interrogator and the dwells deep into working of
the present system identified. The output form the system are traced to the various
process
2.2 feasibility study
The analyst carried out study to determine whether the proposed system is
viable or not. The study showed that the proposed system is viable because the
system is able to solve frequent problems encountered. Some of the areas which
were covered during the study are outlined below:-
2.2.1 Operation feasibility study
Operational feasibility deals with issues such as whether the system will be
used if it is developed and implemented. Whether there will be resistance from
users that will affect the possible application benefits. Some of the essential
questions that help in testing the operational feasibility of a system are:
If yes, then they will welcome the change and the new system.
This will be achieved by having the users involved in the planning and
development of the system. This will be done by asking the various users of the
12
system on their views concerning the various functionalities the system is to have.
Early involvement reduces the probability of resistance towards the new system.
The estimated cost for developing the system is 97,000 including the
hardware devices needed for testing also. The benefits that the system will give to
the community is more and it will reduce the high cost of money used to purchase
document files that cost 100,000 for one year, carbon papers that cost 20,000 for
one year, pens A4 size papers for writing that both cost 60,000 again for one year.
Therefore, by using return on investment (ROI) we can have the following
Capital gains (capital used on the current system to carry out operations) =
50,000+25,000+60,000 = 135,000
38,000/97,000
13
= 0.391752577
From the above feasibility, the development of the proposed system will be of
great profit as it will save 39.18% of the yearly costs incurred with the manual
process.
2.2.3 Technical feasibility
Technical Feasibility Study assesses the details of how a product will be
delivered that is the materials needed, labor, the technology needed among other
things. The technology needed for this particular system is a well-equipped
computer with an operating system, web browsers, XAMPP, storage, any antivirus.
This software’s are readily available and only need be installed to allow the
running of the system.
14
2.3.2 Analysis phase- In this phase the research findings will be used to
model at a conceptual level. The results obtained will help in coming up with
an appropriate design that suits the problem.
2.3.3 Design phase- conceptual level will be used to come up with DFDs
diagrams that represent the system and its functionality. The DFDs design
models are a more detailed version of the design identified in the analysis
phase.
2.3.4 Construction phase- The design model will be translated into an actual
system. It is also at this stage where the database will be constructed based on
the Entity Relational Diagram or class diagram depending on whether it is a
relational database or object oriented database.
2.4.1 Questionnaires
This is also referred to as survey, it is an instrument used for collecting data
in survey research. They usually include a set of standardized questions that
explore a specific topic and collect information about demographics, opinions and
behavior. For the project, the questionnaires is used to target. The reason for
conducting this questionnaire is to know some the problems they really go through.
15
2.4.2 Observation
Using observation, it was also a best way of collecting data. This was done
directly with the subject knowing or unaware that they were being observed. While
still observing the data was collected through continuous observation and the data
gathered was interpreted using the following mechanisms.
information given will be taken with outmost security and confidentiality. Thank
you.
I. Please put a tick tick in the box next to the answer of your choice or
write in the space provided as the case may be.
II. Only tick in one box.
III. No answer is wrong.
1. Indicate your gender.
Male Female
2. Indicate your age
18.30 31-40 41-50 51 and above
3. Have you ever donated blood before?
Yes No
Others
3b) How long does it take to find your previous donation records history?
5. How long does it take for you to complete the donation process?
10 minutes 20 minutes 30 minutes more than 30
minutes
more than 1 hour
6. Is providing a platform where a patient or recipient who requires blood to
contact you as a donor a good approach?
Yes No
6a) If yes in (6) above please give reasons.
18
5 minutes 12 7
7 minutes 17 7
More than 10 minutes 29 7
Using the above questionnaire the critical issue was automation and response time
taken when making a query. Thus the development of the proposed system would
be of benefit and useful to a donor.
19
Manual Automated
11a) Give reasons for your answer above
12.How difficult is it to find a blood match donor when the hospital has no
blood available?
2.5.1.4Questionnaire analysis
7 minutes 10
More than 10 minutes 35
PIE CHART
Male automation Manual Undecided
10.00%
20.00%
70.00%
21
PIE CHART
Automated Manual Undecided
15.00%
20.00%
65.00%
60.00%
50.00%
40.00%
Series 3
30.00%
20.00%
10.00%
0.00%
Automation Manual Undecided
22
CHAPTER THREE:
SYSTEM DESIGN
3.0 Introduction
3.1 System design
Logical design-in logical design, it shows the blueprint of the proposed system as
how it will appear after the system has been developed.
Physical design-in physical design, it shows the blueprint of the proposed system
as how it appears in the programmers mind.
PASSWORD
LOGIN
Back home
23
For a new user (donor or a recipient)to access the system, one must, register into
the system and an account is allocated. Few details are require to register.
FULL NAME
USERNAME
PASSWORD
CONFIRM PASSOWRD
MOBILE NUMBER
AGE
ADDRESS
SUBMIT
GENDER CANCEL
EMAIL
BLOOD GROUP
24
3.1.1.3 Admin
The admin has access to the system and the management power as compared to the
other users. One can access and add another donor to the donor list. He can also
view and manage.
MANAGE PATIENT/RECIPIENT
VIEW REQUESTS
MANAGE INQUIRY
GOBACK
CANCEL
SAVE
25
After the donor has register the can also view his/her profile, make a new donation
HOME
zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
PROFILE
MAKE DONATION
3.1.1.5 Recipient
HOME
PROFILE
3.1
REQUEST BLOOD
26
27
3.1.2.2 Donor
28
3.1.2.3 Patient/recipient
29
30
31
32
33
34
This is used to show the system output as per how the user used the
system. The system process to data entered by the user to give full information to
the recipient.
Admin log in
In the above screenshot the admin opens the admin log in page and enters the
username and password so that they can gain access into the account
35
View donations
Below is a screen shot of the donors list in the administrator account
36
37
Recipient list
Once an account has been created one can log in into their account using credentials
(email account and password) used during creation of the account. When one logs in they can be
able to do various things with their accounts. The screenshot below shows the recipient log in
page
Become a donor
38
The above screenshot shows the page with details required when signing up or
creating a donor account. Once all information is filled one clicks the register
button and their details are saved into the database and they can log in into their
account that they have created.
Donor’s log in
Donor log in page
39
The administrator can be able to view the list of donations requested and can either
approve or cancel the request
Request blood
40
Become a recipient
41
42
3.6.3 Query
3.6.6 Recipient
43
44
3.7.3.Recipient interface
45
CHAPTER FOUR
4.0 INTRODUCTION
This chapter involves or explain on how the system works to the
users. It should explain what takes places in the system.
4.1.2 Donor
The accounts has the following features;
Sign up: One can sign up to be a donor to the system using their
details such name, username, phone number, email etc.
Log in: The donor can now login using the password created during
sign up to access the account dashboard.
46
Edit profile: The donor can also change the details in his or her
account using the feature called Edit profile.
View request: Each donor can view the list if the recipient asking for
them to donate blood and the blood type of the recipient.
4.1.3 Recipient
Sign up: one can sign up to be a donor to the system using their
details such name, username, phone number, email etc.
Log in: The recipient can now login using the password created
during sign up to access the accounts Dashboard.
Make a request: The recipient can also make a request for blood
donations with another compatible donor
Complain: all users can complain to the admin if theirs is any
complain, challenge with the system
47
CHAPTER FIVE
5.0 INTRODUCTION
In this process of testing the whole system and integrated software. The
purpose is to evaluate the system compliance with the specified requirement. These
are several type of testing
5.1 type of test
This is the process of testing complete and integrated software. The purpose
is to evaluate the systems compliance with the specified requirements. There are
several types of testing that can be done. The following tests were done:
48
Objective Achievement
To test if the system can be installed The system was installed on various
and run on different computers machines and performed as
expected
49
The system will allow fast data search All registered users and their records can be
for donors and recipients easily found.
Formal testing conducted to determine whether or not a system satisfies its
acceptance criteria and to enable the customer the system.
50
6.0 Appendices
Appendix I Questionnaire
Please put a tick tick in the box next to the answer of your choice or write in
the space provided as the case may be. Only tick in one box. No answer is wrong.
Others
3b) How long does it take to find your previous donation records history?
51
5. How long does it take for you to complete the donation process?
10 minutes 20 minutes 30 minutes more than 30
minutes
more than 1 hour
6. Is providing a platform where a patient or recipient who requires blood to
contact you as a donor a good approach?
Yes No
6a) If yes in (6) above please give reasons.
52
12.How difficult is it to find a blood match donor when the hospital has no
blood available?
53
54
of the project
stages
55
Budget Appendix IV
Serial Item Quantity Price Justification
no per
Item
1 Transport 3,500 For system
requirements
collection
2 Software Kaspersky 1,000 For developing the
resources Operating 1,500 system
System
3 Hardware Hard disk- 5,000 For running and
resources 500GB 37,000 developing the
Laptop 3,500 system
Modem
4 Internet 2,000 Research
5 Miscellaneous 6,500 For unaccounted
expenses extra costs inquired
TOTAL 60,000
56
<?php
error_reporting(0);
include('includes/config.php');
?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1,
shrink-to-fit=no">
<meta name="description" content="">
<meta name="author" content="">
</head>
<body>
58
59
<div class="row">
<?php
60
$status=1;
$sql = "SELECT * from tblblooddonars where status=:status order by rand()
limit 3";
$query = $dbh -> prepare($sql);
$query->bindParam(':status',$status,PDO::PARAM_STR);
$query->execute();
$results=$query->fetchAll(PDO::FETCH_OBJ);
$cnt=1;
if($query->rowCount() > 0)
{
foreach($results as $result)
{ ?>
</div>
</div>
61
</div>
<?php }} ?>
</div>
<!-- /.row -->
62
<hr>
Type O individuals are often called "universal donors" since their blood can
be transfused into persons with any blood type. Those with type AB blood are
called "universal recipients" because they can receive blood of any type.</p>
<img class="img-fluid rounded" src="images/rbc_table.png" alt="">
</div>
<div class="col-md-4">
<a class="btn btn-lg btn-danger btn-block" href="become-
donar.php">Become a Donor </a>
63
</div>
<!-- /.container -->
</body>
</html>
64
65