METTU 

UNIVERSTIY
COLLEGE OF EDUCATION AND BEHAVIORAL SCIENCE
DEPARTMENTOFEDUCATIONALTECHNOLOGYANDINFORMATIONMANAGEMENT
PROJECT TITLE: ONLINE BLOOD BANK INFORMATION MANAGEMENT SYSTEM

PROJECT PROPOSAL SUBMITTED TO: DEPARTMENT

OFEDUCATIONALTECHNOLOGY  AND  INFORMATION  MANAGEMENT  IN  PARTIAL
FULFILLMENT  OF
THE REQUIREMENT FOR BACHELOR OF SCIENCE DEGREE IN EDUCATIONAL
TECHNOLOGY AND INFORMATION MANAGEMENT

ADVISOR: Mr. FATA TEFERI (Msc)

August,10, 2021
Mettu University,Oromia, Ethiopia
 Declaration

We hereby declare that the project allowed Online Blood Bank Information Management
system submitted in partial fulfillment of the requirement for the award of the degree in BA
Degree in Collage of Education and Behavioral Science Department of Educational
Technology and Information Management), Mettu University, is a record of the own work
carried out by us during the academic year 2013. The extent and source of information are
derived from the existing literature and have been indicated through the project at the
appropriate places.

S/No. Student Name ID Signature

1. Kebeda Ejeta RU/1454/10 ________

2. Dawit Tasfaye RU/1160/10 ________

3. Dechasa Merera RU/1163/10 ________

4. Yohannis Dereje RU/1156/10 ________

5. Burtukan Melese RU/1154/10 ________

6. Geda Abera RU/1156/10 ________

7. Elias Samuel RU/1154/10 ________

i
Approval Sheet

Approval Sheet This proposal has been submitted for Department of Educational
Technology and Information Management with our approval as the project advisor.

Head of Department:
Mr. Fanta Teferi (Msc) Signature: ____________
Project Advisor:
Mr. Fanta Teferi (Msc): Signature:__________

Examiners Name Signature

1. ___________________ _________________

2. ___________________ _________________

3. ___________________ _________________
 Acknowledgments
First and for most and above all our biggest thanks would be to Almighty “GOD” because
nothing could be possible without his free will and the completion of this project is supported by
him. Secondly, our deepest thanks go to our Advisor Mr. Fanta Teferi (MSC) for guidingand
correcting our document with attention and care. He has given time and goes through the project
and made the necessary correction as and when needed.
We would like to forward our special thanks to Mettu blood bank staff employee.
At the last but not the least, even if it is unusual, the group members would like to thank each
other. The main contributors to the success of this project are teamwork, friendship and the belief
that we may achieve something we set out to do. We also hope that this project and the
documentation may be testaments to our continued friendship and better work. And it may also
be the essence of success and symbolic witness of what we have worked for during our stay at
the Mettu University.
Abstract
The  intension of this project is developing a supplemental web based blood bank system for
Mettu  town.  A  blood  bank  information  management system holds information about blood
groups, blood donors and  keeps samples of blood gathered as a result of blood donation and 
the
expired  blood  types. However, the current system is  limited  on manual work. This has limitati
on
on  controlling  the work securely, for declaring the result on  time, and has a high consumptio
n  on
resources. The project follows a design science methodology and an  object orientedsystem
analysis and  design  approach to analyze and design the system. Indepth interview, document
review  and inventory  were done to analyze the existing situation. To model the analysisand
design of the proposed system  Unified Modeling Language (UML) modeling techniques  is use
d
and  both  Hyper-Text Transfer Protocol (HTML) and Hypertext Preprocessor (PHP) is used  t
o
develop the  system prototype. And My Structured Query Language (MySQL)database
management system is  used to design the prototype database. Web based BloodBank
management System is an online portal to facilitate the  coordination between supply and
demand  of  blood.  The whole purpose of the project is bringing an online edge for blood dono
rs
and  patients (blood seekers)  and to create an interactive way of bringing the  Blood donors a
nd
Blood requester.  The system gives a lot of information about Blood groups, donation methods
,
frequency of blood donation  and the details of the coming blood donation  camps. Besides,  ext
ra
features in the system  such as security protection by using  a password, Generating reports,
reminders of blood stock shortage  and workflow tracking can even enhance the  efficiency  of  t
he
management in the  blood  banks. The project includes main modules admin, donor,blood
request/hospital, inventory manager, nurse and labtechnician. It maintains all the information
of donor and all  the record of blood requests and the available blood. The Blood Bank syste
m
helps the people who are  in  need of a blood by giving them all details of blood group availa
bility
or regarding the  donors.

Table of Contents
CHAPTER 1...................................................................................................................................9
Introduction..................................................................................................................................................9
1.1 organizational background.................................................................................................................10
1.2 Background of the system.................................................................................................................11
1.3 Statement of the problem...............................................................................................................11
1.4 objectives..........................................................................................................................................12
1.4.1 General Objective of the project..................................................................................................12
1.4.2 Specific Objective of the project.................................................................................................12
1.5 Significance of the project.................................................................................................................12
1.6 Scope and Limitation of Project.........................................................................................................13
1.6.1 Scope of the project....................................................................................................................13
1.6.2 Limitation of the project.............................................................................................................15
1.7 Feasibility study................................................................................................................................15
1.7.1 Technical feasibility....................................................................................................................15
1.7.2 Operational feasibility.................................................................................................................15
1.7.3 Political feasibility......................................................................................................................15
1.7.4 Economical feasibility.................................................................................................................16
1.8 Methodology.....................................................................................................................................16
1.8.1Data collection Methodology........................................................................................................16
 1.8.2Software Process Model.............................................................................................................17
1.8.3 Tools and Techniques..............................................................................................................17
1.8.4 Techniques................................................................................................................................18
1.9 Cost budgeting.................................................................................................................................19
1.10 Roles and Responsibilities...........................................................................................................20
1.11 Dependencies and Constraints....................................................................................................22
1.12 Risks and Contingencies..............................................................................................................22
1.13 Time Table....................................................................................................................................23
Chapter 2......................................................................................................................................25
Study of Existing System.............................................................................................................25
2.1 Introduction.....................................................................................................................................25
2.2 Existing System...............................................................................................................................25
2.2.1 Existing System Description.....................................................................................................25
2.3 Organization Structure.................................................................................................................26
2.4 Services provided...........................................................................................................................27
2.5 Users................................................................................................................................................27
2.6 Existing infrastructure..................................................................................................................28
Chapter 3..................................................................................................................................................28
Analysis Deliverable of New System......................................................................................................28
Introduction.........................................................................................................................................28
3.1 Specific Requirements...................................................................................................................29
3.1.1 External Interface Requirements...............................................................................................29
3.1.1.1User Interfaces......................................................................................................................29
3.1.1.2 Hardware Interfaces............................................................................................................30
3.1.1.3Software Interfaces...............................................................................................................31
3.1.1.4 Communications Interfaces................................................................................................32
3.2 Functional Requirements..............................................................................................................32
3.2.1 <Functional Requirement or Feature #1>.............................................................................32
3.2.2 <Functional Requirement or Feature #2>.............................................................................33
3.3 Use Cases........................................................................................................................................33
3.3.1 Actors.......................................................................................................................................33
3.3.2 Use Case Diagram...................................................................................................................34
3.3.3 Use Case #1..............................................................................................................................34
 3.3.4 Use Case #2..............................................................................................................................35
3.4 Classes / Objects.............................................................................................................................59
3.4.1 Class Diagram.........................................................................................................................59
3.4.2 <Class / Object #1>.................................................................................................................59
3.4.3 <Class / Object #2>.................................................................................................................60
3.5 Non-Functional Requirements......................................................................................................66
3.5.1 Performance............................................................................................................................66
3.5.2 Reliability................................................................................................................................66
3.5.3 Availability..............................................................................................................................66
3.5.4 Security....................................................................................................................................67
3.5.5 Maintainability........................................................................................................................67
3.5.6 Portability................................................................................................................................67
3.6 Design Constraint..........................................................................................................................67
3.7 Logical Database Requirements...................................................................................................67
3.8 Other Requirements......................................................................................................................68
3.9 Analysis Models.............................................................................................................................68
3.9.1 Sequence Diagrams.................................................................................................................68
3.9.2 State-Transition Diagrams (STD)..........................................................................................84
Chapter 4: System Design...........................................................................................................92
4.1 Design Overview............................................................................................................................92
4.2 System Architectural Design(include Component and Deployment Diagram).........................93
4.2.1 Chosen System Architecture..................................................................................................93
4.2.2 Deployment Diagram................................................................................................................94
4.2.3 System Interface Description.................................................................................................95
4.3 Component Diagram.....................................................................................................................96
4.3.1 Detailed Description Of Components....................................................................................97
4.4 User Interface Design....................................................................................................................99
4.4.1 Description of the User Interface...........................................................................................99
4.4.2 Screen Images.......................................................................................................................100
4.4.3 Objects and Actions..............................................................................................................107
Chapter 5: Testing.....................................................................................................................108
5.1 System Overview..........................................................................................................................108
5.2 Test Approach..............................................................................................................................108
 5.3 Test Plan.......................................................................................................................................108
5.3.1 Testing:...................................................................................................................................108
5.3.1 White Box Testing..................................................................................................................109
5.3.2 Black Box Testing..................................................................................................................109
5.3.3 Functional Tests......................................................................................................................109
5.3.1 Features to be Tested............................................................................................................110
5.3.2 Features not to be Tested.....................................................................................................110
5.3.3 Testing Tools and Environment...........................................................................................110
Chapter 6................................................................................................................................................112
Conclusion..........................................................................................................................................112
6.1 Summary of Final product.........................................................................................................112
6.2 Recommendation.........................................................................................................................113
6.3 Future Work................................................................................................................................113
References...........................................................................................................................................114
Appendix.............................................................................................................................................114

List of Tables

Table 1. 1 Cost of the project.....................................................................................................................22

Table 1. 2 Team composition.....................................................................................................................24
Table 1. 3 Risk and action..........................................................................................................................25
Table 1. 4Time Schedule.............................................................................................................................26
Y

Table 3. 1 user interface............................................................................................................................33

Table 3. 2 Hardware interface...................................................................................................................34
Table 3. 3Software interface......................................................................................................................35
Table 3. 4 Use case documentation for Login description..........................................................................38
Table 3. 5 Use case documentation for manage account............................................................................39
Table 3. 6 Use case documentation for add new information.....................................................................40
Table 3. 7 Use case documentation for view report...................................................................................42
Table 3. 8 Use case documentation for Approve........................................................................................43
Table 3. 9 Use case documentation for view comment..............................................................................44
Table 3. 10 Use case documentation for registration..................................................................................45
Table 3. 11 Use case description for donation request...............................................................................47
Table 3. 12 Use case description for Searching process.............................................................................49
Table 3. 13 Use case documentation for Comment the system................................................................50
Table 3. 14 Use case documentation for blood request..............................................................................51
Table 3. 15 Use case documentation for collect blood...............................................................................53
Table 3. 16 Use case documentation for view donor registration...............................................................55
Table 3. 17 Use case documentation for Blood Screen..............................................................................56
Table 3. 18 Use case documentation Distributed.......................................................................................57
Table 3. 19 Use case documentation for Manage stock.............................................................................59
Table 3.1. 1 class diagram description of attribute Administrator..............................................................63
Table 3.1. 2 Class diagram description of blood collect.............................................................................65
Table 3.1. 3 Class diagram description of add blood.................................................................................65
Table 3.1. 4 Class Diagram Description of total blood In stock.................................................................66
Table 3.1. 5 Class diagram description of approve....................................................................................67

Table 4. 1 Table that shows detailed description of component...............................................................101

Table 4. 2 Test case to register................................................................................................................112
Table 4. 3 Login......................................................................................................................................113

List of Figures

YFigure 1. 1Water fall model.........................................................................................................................

Y
Figure 2. 1Organization Structure..............................................................................................................29

YFigure 4. 1Home Page................................................................................................................................1

Figure 4. 2Home Page..............................................................................................................................101
Figure 4. 3Log In form.............................................................................................................................102
Figure 4. 4Log In form.............................................................................................................................103
Figure 4. 5Donor Registration form.........................................................................................................104
Figure 4. 6Collect Blood form.................................................................................................................106
Figure 4. 7Hospital Registration form......................................................................................................107

Figure 3. 1 Sequence Diagram for login....................................................................................................73

Figure 3. 2Sequence Diagram for Manage account....................................................................................74
Figure 3. 3 Sequence Diagram for Add new information...........................................................................75
Figure 3. 4 Sequence Diagram for View report..........................................................................................76
Figure 3. 5 Sequence Diagram for Approve...............................................................................................77
Figure 3. 6 Sequence Diagram for View comment....................................................................................78
Figure 3. 7 Sequence Diagram for Donation request..................................................................................79
Figure 3. 8 Sequence Diagram for Searching process................................................................................80
Figure 3. 9 Sequence Diagram for Comment the system...........................................................................81
Figure 3. 10 Sequence Diagram for Send request......................................................................................82
Figure 3. 11 Sequence Diagram for Collect blood.....................................................................................83
Figure 3. 12 Sequence Diagram for View donor registration.....................................................................84
Figure 3. 13 Sequence Diagram for Testing...............................................................................................85
Figure 3. 14 Sequence Diagram for Testing...............................................................................................86
Figure 3. 15 Sequence Diagram for Manage stock.....................................................................................87
Figure 3. 16 state chart diagram for login..................................................................................................88
Figure 3. 17 Add information.....................................................................................................................89
Figure 3. 18 Nurse collect blood................................................................................................................89
Figure 3. 19 registration form....................................................................................................................90
Figure 3. 20 Create account.......................................................................................................................91
Figure 3. 21 state diagram for registration.................................................................................................91
Figure 3. 22 Admin....................................................................................................................................92
Figure 3. 23 Nurse......................................................................................................................................93
Figure 3. 24 Manager.................................................................................................................................93
Figure 3. 25 Lab.........................................................................................................................................94
Figure 3. 26 donor......................................................................................................................................95
Figure 3. 27 Tier architecture in deployment.............................................................................................97
Figure 3. 28 Deployment diagram..............................................................................................................98
Figure 3. 29 Component diagram.............................................................................................................100
Abbreviations Description Abbreviations Description
DB Database HTML Hypertext            markup
Language
PHP Hyper                        Text GUI Graphical        User
Preprocessor
Interface
Exp.date Expired date Fig Figure

Reg.no Registration number ABO blood group

Hep b hepatitis b Hep c hepatitis c

OOD Object Oriented Design OOA Object Oriented

Analysis

CDCP Ethiopia     Red     Cross ERCS Ethiopia     Red     Cross

Society Society
FMOH Federal     ministry     of OOSD Object oriented system
health development
methodology
MS Microsoft PHP Structured             Query
Language
MYSQL Structured             Query INFO Information
Language
Pack_No Pack number CSS Cascading          Style
Sheets

1. Table of abbreviation
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
 12. Chapter One

Introduction

The Blood Bank Information Management system is great project. This project is designed for

Successful completion of project on blood bank management system. The basic building aim isto
provide blood donation service to the Mettu city. Blood Bank Information ManagementSystem

(BBIMS) is a browserbased system that is designed to store, process, retrieve and analyze

information concerned with the administrative, donor, blood request/hospital, inventory

manager, nurse and lab-technician within a blood bank (Bell, 2005).

Bank blood donation system is planned to collect blood from any donors in short from various

sources and distribute that blood to needy people who require blood. On the basis of humanity,

everyone is welcome to register as a blood donor. This project is give efficient serviceandaccurat
e in comparison to the existing system.

The main objectives of this project are to automate the complete operations of the blood bank.

They need maintain hundreds of thousands of records. Also searching should be very faster so

they can find required details instantly. To develop a web-based portal to facilitate the co-
ordination between supply and demand of blood.

This system makes conveniently available good quality, safe blood and other blood components,
which can be provided in a sound, ethical and acceptable manner, consistent with the long-term
well-being of the community. It actively encourage voluntary blood donation, motivate and
maintain a well indexed record of blood donors and educate the community on the benefits of
blood donation.
This will also serve as the site for interaction of best practices in reducing unnecessary utilization
of blood and help the state work more efficiently towards self sufficiency in blood. The system
will provide the user the option to look at the details of the existing Donor List, Blood Group an
add a new Donor.It also allows the user to modify the record. The administrator can alter all the
system data. Lotof paper work, slow data processing, not userfriendly environment, difficult to 
keep old recordsand can’t update daily, due to these problems it is necessary to develop a syste
m that address allthese issues.

1.1 organizational background
In Ethiopia blood bank service introduced in 1969 on yikatet12 hospitals. Ethiopia blood bank

supported by FMOH and CDC Separated from ERCS since 2004. Blood bank system in Ethiopia

has one main bank in Addis Ababa and 26 sub branch around all Ethiopia (Gundu, 2006). Mettu

blood bank is one of 26 blood bank branches. Mettu blood bank was established by federal

government and Oromia regional state since in 2006 E.C. this organization was begin giving

small capacity of blood service. The aim of the organization is to provide efficient service to

user, to increase the capacity to provide blood for the recipient, to increases the number blood

donors by teaching the society and facilitating blood donating service for the blood donors.

From time to time the capacity of it is increasing but the organization was working with manual

system. Since the organization is using manual system this makes the employee to fail with data

redundancy and erroneous data storing. Generally this organization was established to save the

life of people who are affected by these problem like accidents, cancer, sickle cell, premature and

surgery (Rudmann, 2005).

Ethiopian people’s are donating and accepting blood time to time, there has been a good rise in

the number of people who donate blood but the system is very old and paper based, therefore we

are very interested to make computerized the system “Mettu blood bankinformation

management system”.
1.2 Background of the system
The project that we are going to be developed is about online blood bankInformation

Management System for Mettu blood bank.The main purpose of our project is to handle and mai
ntain Mettu blood bankinformation

management system and also provide efficient transfusion services. The primary target is only a

blood transfusion unit.Our system manage blood transfusion process starting from donor registra
tion, blood collection,blood testing, storing blood in blood stock and distribution of blood for the 

hospitals through patient name.

This project is intended to provide information about the availability of blood in emergency

conditions their respective locations. Reservation date of Blood donation though online and

maintaining the status of donors for Gathering Volunteers for blood bank and hospitals send

request through patient name to get blood from blood bank.

Our project can manage blood types, quantity and expiry dates for each category of blood that

stored in blood transfusion unit. System show total amount of blood inside the stockfor

efficiently management of blood bank in addition to that, this system show to the inventory

manager which blood types are expired.

1.3 Statement of the problem
The existing system has many problems, such as Document Mismanagement is Chances for

losing the vital information related to hospital, blood and blood donors. A manual systemfor

record keeping so sometime the information is incorrect, difficult to calculate amount of blood in

stock, Error handling is not efficient requires more resources means consumes more resources

and costs such as paper, pen. There is Information gap between workers. The percentage of

security is less. Difficult for the administrator to now the total amount of blood exist in the blood

stock. The system not efficient, reliable, available and difficult to get data fast from the paper.
The existing system does not show the inventory manager when the blood expired but the system

going to developed show it. Difficult for prepared organized report, difficult for give pack

number to collected blood, difficult for to know fit blood during blood transfusion service,

difficult to for making comment the system user to blood bank services, less awareness among

people about blood donation and blood transfusion services and difficult to know how match

time donor donate blood.

1.4 objectives
1.4.1 General Objective of the project
 Thegeneral objective of this project is to develop and to design Online BloodBank

Information management system.

1.4.2 Specific Objective of the project
 Analyzing the existing system
 Identifying functional and non-functional requirements
 Create a database to register blood donor, hospital and to store personal informati
on for individual donor and hospital of the blood bank.
 To develop a secured database that will store the information of registered donors 
and organization.
 Coding and testing
 To  implement  and  design  webbased  blood  bank  information  management  system that
will give proper service for a users.

1.5 Significance of the project
The existing system is not using computerized data processing system. So making the system

web based will give benefits from the following four aspects. For Administrator: Administrators

easier to manage the information. For Inventory manager: It makes Alert home(expired, amount

of blood), blood(view, add, delete, update the blood). Lab-technician: It makes search screen

blood, update, delete blood, views the message and send message. For Blood donors: It provides
the unique identification number easily at the time of blood donation camp which helps the user

for the future correspondence.  Donors can view the blood donation camp organizing at different

places.  Donors can make reservation Online.

For blood seekers: Seeker can get the information of the desired blood group from the central

inventory. Seeker can see available Blood on the database. Seeker can get the information of the

blood groups which is or not fit for blood transfusion inquests. Seekers can save time, effort and

money. For Blood bank center: The camp is getting rid from manual procedure. Now they to do

the entries in the information system. The probability of error should be minimal. Information

retrieval should be precise and effective. Report about donors, seekers, total consumption of the

blood units and overall report can be generated. Can get the information which ismaximum

cause for which the blood units are required such as accidental cases, heart surgery,delivery

cases etc. Can view the list of discarded blood units, they can also view the reason for which the

blood units are discarded. For The Developers: While developing the system Developer’steam

and skills will be improved knowledge how to conduct and prepare a web based system.

Developer’s team problem solving skill will be increase.

1.6 Scope and Limitation of Project
1.6.1 Scope of the project
 The system will Covers the following information:

 The system can manage the blood stock starting from the donor registration, blood
 collection, blood testing, and add new blood, hospital request and blood distribution to
the hospitals.
 Donors receive message from blood bank and donors send the feedback to blood bank.
 The system count how many donors donate the blood frequently.
 Blood Donors and Hospital registration in the system to access the system,
 The system show to the inventory manager when the blood is expired.
 The system is able to view pre-defined reports the workflow for each blood donation and
transfusion process.
 The system provides security features through password security where only authorized
user can access to the system with different authorization level.
 The probability of error should be minimal.
 Information retrieval should be precise and effective.
 Easily searching the related blood type.
 The systems show how much blood inside the stock.
 The system easily give pack number to the collected blood,
 The expired blood is automatically disqualified by the inventory manager from the blood
bank and record is deleted from the data base.
 Inventory manager can be properly controlled and managed as using the FIFO (First in
First Out) concept.
 The system allows the donor to make online reservation on the day and session that they
want or free to make blood donation for the purpose of saving life.
 The system enables administrator to manage account, add news, update, delete news,
view blood, send message, view message, view report, view appointment, delete
appointment, approve, view comment, delete comment, search and delete hospital, andlogou
t the system.
 The system enables administrator to manage real donor account, collect blood, message.
 The system enables inventory manger to manage alert home(expired, amount of blood),
blood(view, add, delete, update the blood), message and logout.
 The system enables lab technician search screen blood, update, delete blood, shows the
message and send message and logout.
 The system enables donor to register, register for appointment and logout.
 The system enables hospital register the patients.

1.6.2 Limitation of the project
 Our system can have the out scope in the case of the following:
 Lack of experience
 Shortage of time: the duration given of time may not be sufficient to be accomplishing
 successfully the project. This enforces to minimize the scope.
 The system does not support languages other than English and Afaan Oromoo language.
 The system cannot help people with visual impairment.
 The system is accessible when the internet is available.

1.7 Feasibility study
The important among the preliminary investigation is the determination  of  whether the
system
is feasible or not. There are four aspects of feasibility study which should be checked
in preliminary investigation.

1.7.1 Technical feasibility
The system is self-explanatory and does not need any extra sophisticated training. As the 
system
has been built by concentrating on the graphical user interface concepts, the application canalso
be handled very easily with a novice user.

1.7.2 Operational feasibility
Our input screens are designed as per requirements. One or two hour training is sufficient touse
rof the system. The system operation easy for the users.

1.7.3 Political feasibility
Political feasibility determines whether the proposed system conflicts with the legalrequirement
or not.
 A project may face legal issues after completion if this factor is not considered at the first
stage. As a result, the system is political and doesn’t conflict with the law of thecountry;it
works based on the rule and regulation of the Ethiopian constitution. Concernsifthe
develop  project would have  any  legal implications for the organization due to government
regulation or software license agreements.

1.7.4 Economical feasibility
Economic feasibility is the most important and frequently used method for evaluating
effectiveness of the proposed system. Cost benefit analysis is usually performed for this purpos
e.
The organization does not using any media advertisement because it asks more budget.This
project is economically feasible because it makes all information online and every one can get

the information from the site.

1.8 Methodology
1.8.1Data collection Methodology
To gather data from the different users and worker of the existing system the team will be used
the following four techniques.
Interview
We orally discussed and interviewed some staff members and manager of the Mettu blood bank
for necessary information. This information helps us to identify the blood bank problems and
also to understand the current system. So, we analyzed the information of the blood bank and
obtained some basic concepts on how the blood bank is managed in the current system.
Questionnaire
We used this technique in the initial and final phases of our project. In the initial phase we
prepared some questionnaire to get some basic information about the current system. Thenwe
used the questionnaire to get some numerical data.
Record review
This was the most beneficial technique for us while making our database. We studiedtheexisting 
file structure, documents used and generated in the organization. For everyfiles
registered we tried to identify its significance need and relation with other data item.
Observation
While finding the facts we intensely observed all the activities and transaction usage of files and
document. Observation helped us in finding out the actual way functioning apart from the ideal
or desired.

1.8.2Software Process Model

We use waterfall Model for our project. This model is simple and easy to understand and use. It
is easy to manage due to the inflexibility of the model. Each phase has specific deliverables and a
review process. The phases are processed and completed one at a time and do not overlap. The
reason to choose this model is that our project requirements are very well known, clear, fixed and
no ambiguous requirements.

Waterfall [linear] -Phases are organized in a linear order. Every next phase starts upon
completion of previous phase.

Diagram of waterfall model is shown below:

Figure 1. Water fall model

1.8.3 Tools and Techniques

Hardware and software tools required for successful completion of the projects are listed below
with their respective significance.
Hardware tools required are:-
Personal computer (PC): almost all tasks of the project are performed on computer
Flash: required for data movement
Disks (CD, DVD): necessary for the movement of relevant data and for backup and recovery
mechanism.
Printer: to print documentations
Stationeries (pen, paper): for writing all necessary documentations associated with the project
Note book: to take notes during data collection and for other documentations
Software tools required are:-
XAMPP server: to provide MySQL for creating and manipulating databases and PHP (Hypertext
Preprocessor) to design user interface from the front end of software.
It also provides the latest releases of phpMyAdmin, HTML, CSS and JAVA SCRIPT embedded
inside it.
Microsoft office 2007 and Notepad++: to write on any necessary documents about the project
Microsoft Visio 2010: used to draw diagrams and Gantt chart.
EdraUML: to draw diagrams such as use cases diagrams, class diagrams, sequence diagrams,
collaboration diagrams, activity diagrams and state charts
Adobe Photoshop and Picasso: to edit images and texts.
Windows 8 Operating system.

1.8.4 Techniques
Modeling
For designing the different models such as use case, sequence diagram and other models
we have been used enterprise architecture.
Interface design
For designing an interface we have been use frontend for html and java script. Backend for PHP.
Database design
For the designing and creating of database we use My SQL.
Server
The use XAMPP server for storing and communicating between the database and applications.

1.9 Cost budgeting

The following table lists budget required for the successful development of the
proposed system

Types of costs Tool name Quantity Unit price (in Total price (in
Birr) Birr)
Desktop 5 2000 10000
Flash(8 GB) 2 250 500
 CD ROM 2 7 14
Hard ware DVD 2 20 40
Printer 1 3500 3500
costs Pen 6 3 18
Paper 1 packet 80 80
Note book 2 25 50

XAMPP server 1 Free Free

Microsoft office 2007 1 40 40
Notepad++ 1 Free Free
Software costs Microsoft Visio 2010 1 40 40
EDROUML 2 Free Free
Adobe Photoshop 1 50 50
Picasso 1 Free Free
Windows 7 OS 1 40 40
Other costs Transportation cost - - 200
and labor
Meal cost - - 500
Miscellaneous cost - - 150
Total cost - - - 150000
Table 1. Cost of the project

1.10 Roles and Responsibilities

Involves organization of the team and communication among each member of the team. There
are three (3) types of team organization:-

Centralized– control team organization: standard management technique in well understood

discipline worker report to supervisor who directly controls and is responsible for their
performance

De-centralized– control team organization:- is ring-like management because of lack of

hierarchy . The team member are at the same level , and then can review each other’s work and
responsible as a group

Mixed – control team organization: combines the benefits of centralized and de-
centralized organization by minimizing or avoiding disadvantages
Among these three control team organization our project team chooses decentralized – control
team organization.

Reason of choice:

 our team members are on the same level and we can review each other’s work
 Higher moral among team member
 Job satisfaction
 Feel more ownership and responsible
 Encourage to share and review other’s

 Our team composition can be summarized as :-

Table 1. Team composition
Id_no Name responsibility

RU/1454/10 Kebede ejeta Planning, designing, modeling, analysis and

implementing

RU/1772/10 Dawit tesfaye Planning, designing, modeling, analysis and

implementing

RU/1532/10 Geda abera Planning, designing, modeling, analysis and

implementing

RU/1493/10 Dachesa meraera Planning, designing, modeling, analysis and

implementing
RU/1832/10 Burtukan melesa Planning, designing, modeling, analysis and
implementing

RU/1848/10 Elias Samuel Planning, designing, modeling, analysis and

implementing
RU/1825/10 Yohanis Dereje Planning, designing, modeling, analysis and
implementing

 Our team composition is taking the gender issues into consideration by having 6 male
students and 1 female students without any discrimination.

1.11 Dependencies and Constraints

Constraints
 Project schedule/time limit
 There is a few month to work and to implement a production system of web-based
information system from project commencement in time for graduation of truly and the
time is very consistent to use wisely because there is a class schedule all day and
preparing and reading for the class as the same time working other assignments and project
works.
 So that time limit may affect the work of this project.
Dependencies
 User must have the basic knowledge of English.
 The user must have the ability to use the internet.
 The user must have connected to the intranet or internet to use the system.
 The accuracy of the information of user is the responsibility of all users.
1.12 Risks and Contingencies
Every programmer may face many problems when he/she want to develop any project. While we are
doing this project we encounter or come across different problems.
 Loss of data by different problem.
 Shortage of time while doing the project.
 The problem of contacting the office manager at the time we needed.
 Lack of enough reference.
This constraint may be hindrance to come up with the software we need to develop. To overcome these
we try to schedule our time and budget and scanning with anti-viruses and recovering the system.
No. Risk Actions/solution
1 Computer viruses, computer Backup the file, scanning with anti-
failures viruses and recovering the system.

Lack of as much as necessary To read information from different

2 references sites, using internet when there is
access.
3 Lack of financial support from the Use own money appropriately and
Organization. effectively.
Table 1. Risk and action
1.13 Time Table
The proposed system OBBIMS will be developed totally and begin to give services according
to the time given. Therefore, it is feasible in schedule.
Table 1. Time Schedule
 13. Chapter 2
14. Study of Existing System

2.1 Introduction
As mentioned in the first chapter, in this project, the team used an object oriented system
development methodology. In this chapter the major activities performed or identified are:
modeling the function of the use case, identifying actors, identifying use case, constructing use
case model and use case scenarios and final designing of user interface.

2.2 Existing System

2.2.1 Existing System Description
The existing system does everything manually. Documenting, writing, finding and searching of
the specific information of the blood is done manual. In the current system the administrators
cannot manage the blood stock starting from the blood collection, to blood screening, processing,
storage, distribution and lastly transfusion through this system. Moreover, there is no logging
function available So that each process or workflow cannot be traced from the database. The
system will not show the expired blood. These types of system make the worker to document
erroneous and redundancy information and it also consume the time of worker for completing
specific task.
The Existing system performance is weak in case of following reasons:
Efficiency: due to the manual operation most of activities are likely to wastage of resources
like papers, man power, time etc. to produce the corresponding outputs. This makes the current
system ineffective while utilizing resources.
Services: the main users of the current system are hospitals and donor. The services given to
the user are not flexible, reliable and expandable i.e. the users must there in the blood bank to get
the services given by the system. Those services given by the system are limited to a particular
area.
Economical: Mettu blood bank performs all of its tasks manually which requires lot of
man power to do that tasks, and needs huge amount of papers to store data manually.
 Consume money for advertization. This manual system spends more money for human
resource, purchasing papers and other materials.
Controlling: All the records associated with the manual system are recorded and
stored manually. The security that the system provides for the privacy of those records is
not in good manner. The system shouldn’t provide sufficient protection for access and
manipulation of the records associated with the system.

2.3 Organization Structure

Figure 2. Organization Structure

2.4 Services provided
During donation of the blood the service provided are the place where the donor sit called donor
classroom.
Also the material on which the the blood is collected on and that used as the container is cold
chain.
The material on which the donor sit on and lay down on is chair and table is provided for the
donor during donate blood.
The machine produce the pack number during real donor donate blood for each of donor.
2.5 Users
Users are entities that interact with the system. It concerns only in Blood Bank
management system in Mettu town. 
There are many  basic beneficiaries which can get benefitsfromthe DM blood bank Service
s. Which are:-
Blood Donors: person who wants to donate the blood voluntarily at the blood donation
camp.

Blood Seekers: An Organization who wants the blood from the blood bank due to various
reasons like accidents, surgeries, delivery and many more.

Blood bank: staff people are working in the blood bank whichincludes staffmember, 
operator, blood bank in charge, head of pathological department.

Nurses: check donor healthiness and received blood.

Manager:managing, supervising, budget all of action for the overall activity of thesyste
m.

Lab Technician:-test blood, give blood for client hospitals and manage the sock.

Data Encoder: - Register all the donor profile and send report for manager.
The Receptionist: Nurse Register blood donors give pre donation information and  motivate

donors to full fill questionnaires.

2.6 Existing infrastructure

 Paper
 Class room table/chair
 copy machine
 stapler
 Electric light.

15. Chapter 3
16. Analysis Deliverable of New System
Introduction
The proposed system has server, database and client. The server used to fetch data from the
database and store data in to the database according to the instruction of the user. Database used
to store the information of donor and patient. The client is display the pages to the user and after
the user insert input, the client send the request to the server and also display the response of a
server to the user. Every data regarding patient and patient information is stored at a central
database in high capacity server. The software performs every mathematical computation like
calculate number of patient and real donor in each year, how many patients are given
appointment.
The new system is designed to solve problems affecting the manual system in use. It is design to
be used online thereby relieving both the patients, donors and the hospital staff from much stress
as experienced in the manual system.

This system will do the analyzing and storing of information either automatically or
interactively. It will make use of online access to Internet. The proposed system will also have
some other features like:-

 Login system must be present and secured by password and logout after cover.
  Accuracy in the handling of data.
 Fast rate of operation and excellent response time.
 The system is flexible i.e. it can be accessed at any time.
 Better storage and faster retrieval system.
 Accessibility from anywhere.
3.1 Specific Requirements
This section provides software requirements to level of detail sufficient to enable designers to de
sign the system andtesters to test the system.

3.1.1 External Interface Requirements

 "External interface requirements specify hardware, software, or database elements with which
a system or component must interface." This section provides information to ensure that the
system will communicate properly with external components.
3.1.1.1User Interfaces

User Interfaces Role
organization Registration  Various fields available on this screen will be:
Screen F Login Name
F About
F Help
F Language
F organization Name
F Registration Form
F Feedback

Admin Login Screen Fields available on this screen are:

F Login Name
F Password
Nurse login screen  Various Fields are:
F Login Name
F Password

Inventory  Manager  Various Fields are:

Screen F Login Name
F Password
Donor Login Screen  Various Fields are:
F Login Name
F Password
Lab Technician Screen  Various Fields are:

F Password
F Login Name

Table 3. user interface

3.1.1.2 Hardware Interfaces

Different hardware’s used to develop this project are listed below:
Image of hardware

used for the movement of data from one machine to another.

to print documentations

for writing all necessary documentations associated with the

project
Note book: to take notes during data collection and for other
documentations
 necessary for the movement of relevant data and for backup and
recovery mechanism.

almost all tasks of the project are performed on computer

Table 3. Hardware interface

3.1.1.3Software Interfaces
Software Tools used are:
Image of software

 used to design unified modeling diagram.

used to draw diagrams and Gantt chart.

 It offers great scope for endless revision of a

document; this includes words, word order, style
and layout. It is what we use to type our project
work.
 Power point: Used to present our project in short
and brief way.

to write on any necessary documents about the project

 to provide MySQL for creating and manipulating
databases and PHP (Hypertext Preprocessor) to design
user interface from the front end of software.
Table 3. Software interface

3.1.1.4 Communications Interfaces

The system should be accessed over LAN or WAN. For Clients to access application server the
network should be running TCP/IP protocol.

3.2 Functional Requirements

The functional and nonfunctional requirement of the proposed system is identify from
requirement use cases associated with each actor and use case interaction.

3.2.1 <Functional Requirement or Feature #1>

Functional requirements explain what has to be done by identifying the necessary task, action or
activity that must be accomplished. A function is described as a set of inputs, processing, and
outputs. Functional requirements may be technical details, data manipulation and processing and
other specific functionality that define what a system is supposed to accomplish. The system
provides the following basic functionality:-
1. Advertisement and announcement: The system to promoting about the organization
what is there services, how they treat customers and others. Like other advertising media, it
frequently involves a publisher, who integrates advertisements into its online content and users
of the system who has an account can be visited published information through internet access.
2. Member signup and staff member registration: This BBMS allows the users to
store his/her details in to the system to gain the system services.
3. Online reservation and appointment : The system allows to public can make online
reservation on their desired session and date. The blood centers' administrators can then manage
their appointments.
4. Blood request and Cross matching: BBMS allows the user to request for blood and
blood transfusion for which the cross matching using the appropriate technique can be carried
out and the results can further be processed and analyzed by the experts to issue the blood. Also
various reports for blood requisition and the cross matching can be generated at run time.
5. Searching functionality: functionality in order to allow normal and privileged users to
search the details of a given donor, Develop a searching blood group, and if necessary a type of
disease common which causes one to need the donated blood.
6. No installation: As it is a web application, it prevents users from any kind of hindrances
faced during installation or up-gradation of application. User simply needs a browser to access
the application.
7. Report generation: Various comprehensive reports can be generated any time by the end
user to measure the performance parameters in the blood bank and also to analyses the inventory
and other aspects in blood bank.
3.2.2 <Functional Requirement or Feature #2>
3.3 Use Cases
Use Case Diagram represents user requirements gathered during requirement elicitation, contains
use case, actors, system boundary and their relationships. Use Case diagram of the system is
shown as follows with respective description [4].

3.3.1 Actors
A new system contains different players to carry out its job. Among that different player, the
most common are administrator.

The major actors in the new system are:

Admin: create the staff and manage the system

Donor: a person, who is voluntarily to donate blood,
Hospital: send blood request through patient name
Nurse: collected blood from donor and give pack number for the blood component.
Lab technician: tests the incoming blood packet, grade the blood packet usable or not
usable.
Inventory manager: accept safe blood from lab technician. Mange stock and he also
processes the request from the person through hospitals
 3.3.2 Use Case Diagram
The second step is to construct the use case model which graphically represents the interaction of
the system with the external environment. The major actors that plays major role out of the
system are: - administrator, nurse, lab technician, inventory manager, hospital and donor the use
cases incorporated in the system are:-Login, manage account, add new information, approve,
view report, Register donor, register hospital, donation request, add new blood, collect blood,
blood request, blood distribution and searching process. The following figure specifies the use
case model of the system.

3.3.3 Use Case #1

Usecase 3. usecase

3.3.4 Use Case #2

The third step is to document each of the above use case events to determine the requirement use
Cases as described in the following section.
Table 3. Use case documentation for Login description
Use case id Use case No1

Use case name Login

Actors Admin, Donor, Hospital, nurse, lab

technician. Inventory manager.

Description The authentication for authorized users in

the system to interact with the system Mettu
online blood bank.

Goal To be acceded by an authorized and trust

system user

Precondition Any user must have user name and

password.

Basic flow of action Actor action System response

Step1:system show screen

Step2:user
enter user
name and pass
word

Step3: the
system check the
authentication of
user name and
password

Step4:system
display user
page

Post condition System transfer control to user main screen

to precede actions.

Alternative action A. The username and password is invalid.

1. The system displays error message.
2. The system continues at step 2 to fill user name
and password again.
Table 3. Use case documentation for manage account

Use case id Use case No2

Use case name manage account

Actor Admin
Precondition The System administrator must login to control the account

Description This activity is performed when the admin want to manage the account
Goal To control the system worker.
Basic course of action Actor action System response

Step1: admin enter user name and

password
Step2: the system check the
authentication of user name
and password

Step3:the system display

Step4: admin select mange ac
admin page
count page :-
1.create account
2.update account
3.delete account

If create account
Step6 admin enter user account Step5: System display create account
information page.
Step7:system check create user
account information
Step8:System creates user account

Post condition The system admin successfully create, update and delete the account!

Alternative course of A. Invalid information entry.

action 1. The system displays error message.
 2. Go to step 6 to fill again.

Table 3. Use case documentation for add new information

Use case id Use case No3

Use case name Add new information

Actor Admin
Description Add new information to create awareness and use full information

Goal To add new information to the blood bank users

Precondition The System admin must login to add new information

Basic course of action Actor action System response

Step1: admin enter user name and

password
Step2: the system check the
authentication of user name
and password

Step3:the system display

Step4: admin select add new
main admin page
information link

Step6:System admin enter

add new available information Step5: System display add new
information page.
Step7:system check add new
information
Step8:System post new information

Post condition The system posted information will be viewed by an authorized users

Alternative course of A. If the submitted new information is not valid.

action 1. The system displays error message.
2. Go toStep5 to submit the add again.
Table 3. Use case documentation for view report

Use case id Use case N04

Use case name View report

Primary actors Admin

Description Want to view report information by searching date

Goal To view about blood distribution

Precondition The admin must be log in the system

Actor action System response

Basic flow of action

Step1:main admin enter
user name and password Step2: the system check
the authentication of user
name and password

Step3:system display
admin page
Step4:admin select view
report link
Step5:the system display
view report page
Step6: admin insert
report date

Step7: system display

report

Post condition The admin view report

Alternative action A. The system If no information found to see generated

report
 1. The system displays error message.
2. Go to step4 to view report again.

Table 3. Use case documentation for Approve

Use case id Use case N05

Use case name Approve

Primary actors Admin

Description For Approving those who send donation request to donate blood.

Goal Give decision for the donor appointment

Precondition Admin to approve must be view the donor donation request

Actor action System response

Basic flow of action

Step1:admin enter user
name and password Step2: the system check
the authentication of user
name and password

Step3:system display
admin page
Step4:admin select
approve form
Step5:the system display
approve
Step6: admin search
request and
if the request is valid
approve
Step7:system check
information
 Step8:system display the
request is approved

Post condition Send for donor session date to donate the blood

Alternative action The request is not disapprove

Table 3. Use case documentation for view comment

Use case id Use case N06

Use case name View comment

Primary actors Admin

Description Admin can see the comments that are submitted from the user (Donor,
Hospitals).

Goal To view system user feedback about the system .

Precondition Go to the site and register

Basic flow of Actor action System response
action
Step1: admin enter user
name and password

Step2: the system check the

authentication of user name and
password

Step3:system display admin

page

Step4:admin select view

comment link
 Step6:admin view Step45:system display
comment comment records

Post condition Admin views the submitted comments.

Alternative action A.If fill to view comment

1. The system displays error message.

2. Go to step4 to view comment again.

Table 3. Use case documentation for registration

Use case id Use case N07

Use case name Registration

Primary actors Donor, Hospital

Description for registration to get access from the blood bank

Goal To access the system and to be the system user member.

Precondition Go to the site and register

Basic flow of Actor action System response
action
Step1:user click on the
registration link

Step2: the system display

registration form
Step3:user select from
registration
1.donor registration
2.hospital registration
If select donor registration
 Step4 :system display donor
registration form

Step5:donor fill registration Step6:system check donor

form registration information

Step7:system Display
successfully register

Post condition If valid successfully register if not valid Alternate action

Alternative action A. If fill to registered

1. The system displays error message.
2. Go to step5 to fill again registration information

Table 3. Use case description for donation request

Use case id Use case N08

Use case name Use Donation request

case id

Primary actors Donor

Description The donor should be visit the blood bank makes

appointment date for the blood donation purpose.

Goal To specify the donation date.

Precondition Want to make appointment date for the donation

Actor action System response

 Basic flow of action Step1:Donor enter user
name and password

Step2: the system

check the
authentication of user
name and password

Step3:system display
Step4:donor select donor page
donation request link
Step5:system display
donation request
Step6:fill the donation menu
request form and send

Step7:system save the

request in DB

Step8:system display
Inserted record

Post condition If Get appointment date to donate blood

Alternative action A. The donor fill to donation request send

1. The system displays error message.
2. Go to step5 to fill again donation request.

Table 3. Use case description for Searching process

Use case id Use case N09

Use case name Use Searching process

case id

Primary actors Donor and Donne

Description Searching the blood bank of the location within blood

result, blood group.
 Goal To view or search the required information

Precondition searching to click search button

Actor action System response

Basic flow of action Step1:user enter user

name and password

Step2: the system

check the
authentication of user
name and password
Step4:user select
searching link Step3:system display
user page

Step6:user enter to Step5:system display

search search menu
1.related blood
group

Step7:system check
searching information

Step8:system display
searching result

Post condition Display the searching information

Alternative action A.faill to search

1.the system display error message
2. Go to step6 to enter again to search.

Table 3. Use case documentation for Comment the system

Use case id Use case No10

Use case name Comment the system

Primary actors System user

 Description Comment the blood bank system about any thing

Goal To give the weakness and strength of the system

Precondition User must have valid email address comment the system

Actor action System response

Basic flow of action

Step1:system display user page

Step2:user select
comment the system
link Step3:system display comment
form

Step4user write
comment about the Step5:system check comment
system information

Step6:system display comment

submitted

User send comment to the system

Post condition
A. fill to send the comment if valid
Alternative action
1. The system displays error message.

2. Go to step4 to fill again comment validly.

Table 3. Use case documentation for blood request

Use case id Use case No11

Use case name blood request

Primary actors Hospital

Description Sending request for required blood unit, blood group. with the patient name
just for the identification of blood accepter
Goal Asking blood from the blood bank for the patient.

Precondition Hospital send request to blood bank.

Actor System response

Step1:hospital admin
Basic flow of action enter user name and
password

Step2: the system check the

authentication of user name and
password

Step3:system display hospital

Step4:hospital select page
send blood request link

Step5:system display blood

Step6:user fill the request form
blood request in the
name of patient

Step7:system check blood

request information

Step8:system display inserted

Step9:user print out request record
record then give patient
family or friend

Indirectly accept the required blood thorough patient name

Post condition
A. The hospital fails for to send
Alternative action
1. The system displays error message.

2. Go to step6 to fill again the request.

Table 3. Use case documentation for collect blood

Use case id Use case N012

Use case name collect blood

Primary actors Nurse

Description To Collect The Blood from voluntary donors by filling

full information,
 Goal To Collect The Blood from voluntary donors

Precondition Fill collected blood information

Actor System response

Basic flow of action
Step1:nurse enter
user name and
password
Step2: the system check
the authentication of user
name and password

Step3:system display
nurse page
Step4:nurse select
collect blood link
Step5:system display
collect blood menu
Step6: fill collect
blood information

Step7:system check
collect blood information

Step8:system display
collected blood record
Step8:nurse print
out record then give
for donor

Post condition Submit collected blood information

Alternative action A. if not valid enter nurse fill to blood collection

1. The system displays error message.
2. Go to step6 to fill again the collected blood.

Table 3. Use case documentation for view donor registration

Use case id Use case N013

Use case name View donor registration

Primary actors Nurse

Description To register new donor and search the old donor for the
blood collection mechanism

Goal To search the old blood donor.

Precondition Register new donor

Actor System response

Basic flow of action
Step1:nurse enter
user name and Step2: the system check
password the authentication of
user name and password

Step3:system display
nurse page

Step4:nurse select Step5:system display

view donor donor registration form
registration link

Step6:the volunteer
old donor search()
from donor
registration and
If the new donor Step7:the system check
come fill the donor donor registration
registration form information

Step8:system display
new donor
Information

Step8:nurse view
donor record
information

Post condition Register detail donor information

Alternative action A. Nurse new donor registration us filled

1. The system displays error message.
2. Go to step6 to register new donor or search old donor
Table 3. Use case documentation for Blood Screen

Use case id Use case N014

Use case name Blood screen

Primary actors Lab technician

Description For Testing donated blood in order to identify those with

particular blood group characteristics

Goal To identify each blood group and blood is safe or infected.

Precondition Fill testing blood information

Actor System response

Basic flow of action

Step1:enter user name

and password Step2: the system check the
authentication of user name
and password

Step3:system display lab

technician page
Step4:lab technician
select testing link
Step5:system display blood
Step6: lab technician testing form
fill the form test result

Step7:the system check

information

Step8:system display screen

blood information

Post condition submitted lab testing result

Alternative action A. if invalid enter tested result fill to submit

1. The system displays error message.
2. Go to step6 to submit the tested result.
Table 3. Use case documentation Distributed

Use case id Use case N015

Use case name Distributed

Primary actors Inventory manager

Description For Blood distribution. blood accepter must be

come using hospital blood donation request

Goal To distribute the safe blood to the hospitals.

Precondition Searching the blood fit from the stock

Actor action System responses

Basic flow of
action Step1:User name
&Enter password
Step2: the system
check the
authentication of user
name and password

Step3:the system
Step4:inventory display inventory
manger select manager page
blood distribution
link
Step5:the system
display distribution
Step6:search() form
from blood stock
that fit with the
blood accepter Step7:system check
blood stock
information

Step8:system display
fit blood

Post condition Distribute blood for the accepter

Alternative action A. Fill to the distribution blood

 1. The system displays error message.
2. Go to step6 to search fit blood from the stock for
the distribution.

Table 3. Use case documentation for Manage stock

Use case id Use case N016

Use case name Manage stock

Primary actors Inventory manager

Description Manage the amount of blood in stock too knows the amount Less amount of
Blood per level and the expired blood. and also to insert new blood

Goal To manage the blood in the blood stock.

Precondition view the Details of the Blood Stock

Actor System response

Basic flow of
action
Step1:enter user name and
Pass word
Step2: the system check the
authentication of user name and
password

Step3:the system display

inventory manger page
Step4:inventory manger
select blood stock link
Steps5:the system display mange
stock form

Step6:inventory manger
select
1.register blood
2.update blood
3.delete blood
If select register blood
Step7:system display blood
registration form
Step7:inventory manager
fill blood registration form
Step7:system check register
blood information

Step8:system display blood

successfully registered

Post condition Add new blood to stock, view the Less amount of Blood per level and
expired blood
 Alternative action A. Fill to the inventory manger to add new blood or discard blood
1. The system displays error message.
2. Go to step6 to fill again the add new blood or discard.

3.4 Classes / Objects

3.4.1 Class Diagram
Class diagrams are used to describe the structure of this system. Classes are abstractions that
specify the common structure and behavior of a set of objects in the new system. Class diagrams
which going to be designed is describing the system in terms of objects, classes, attributes,
operations and their association.

Once the team has identified the association and the corresponding multiplicity of association of
the objects of the proposed new system, the next step will be to draw the class diagram. The next
sub topic shows the class diagram of the new system.
3.4.2 <Class / Object #1>
 CLASS DIAGERAM FOR ONLINE BLOOD BANK INFORMATION MANAGEMENT SYSTEM
1
Blood bank
Manage -name
Register -creation date
1
1 1..* -email
Nurse -phone no
-Name -location
Donor
-Phone no +accept()
Admin Create -Address -Name +store blood()
-Name 1..* -Age 1..*
+Register doner() 1
-Phone _no -Date of brith
-Email
1 +Pack no() Register -Occupation 1
1 1..*
-Address -Donor type
+Approve() 1 -Reg.no
+Manag acount() -Zone
0..* -Woreda
+Add info()
-Kebela Register
-Phone no
1 Collect -City : string
1
-Email
+Register()
+Donation request()

Create 1..* 1..* Has

Donat
1 1..*
Blood
Create -Blood type
1..*
Lab technician -Pack no Hospital
-Name -Info -H Name
-Phone no Test 1..* +Add() Request -donee name
1
-Email +Subtract() -phone no
-Address 1..* 1..* -fax
+Test blood() 1..* -Reason
+Acept blood()
Manage 1..*
-Requerement date
+Reject test() +Request blood()

Has

1
1..*
Inventory manager Blood stock
-Name
1 -Stock_id : string
1 -Phone no
-Date : Date
-Email
-Aposative : string
-Address
+Stock info()
+Manage stock()
+Acept blood()
Manage 1..* +Updat stock()
+Reject blood()
1
+Distribute()

object 3. Logical database

3.4.3 <Class / Object #2>

Class Diagram Description

Class Administrator
diagram
name
No Field name Data type Description
1 Name Varchar(30)not null Full Name of Administrator
2 ID Varchar(20)not null Identification of Admin
3 Username Varchar(20)not null Username of Admin
4 Password Varchar(20)not null Password of Admin
Method: UpdateAdminAcc(),DeleteAdminAcc()
UpdateAdminAcc(): to change the account of admin
DeleteAdminAcc(): to delete the account of the admin
Table 3.1. class diagram description of attribute Administrator
Class diagram User
name

No Fieldname Data Type Description

1 Name Varchar(30) not null Full name of the user (donor,
nurse, lab technician,
inventory manager, )
2 IDNo Varchar(20) PRIMARY Identification number of user
KEY, not null

3 Username Varchar(20) not null Username of User

4 Password Varchar(20) not null Password of the user

5 Account type Varchar(50) not null Account type of the user

Method:CreateAccount(), Delete Account(), change Account()
Create Account():enables admin to create user account for users
Edit Account():enables admin to edit user account for users

class diagram description of User

Blood collect
Class
diagram
name
 No Field Name Data Type Description
1 Donor No int(20) PRIMARY KEY, Identification number of donor
NOT NULL

2 Fullname Varchar(50) NOT NULL Name of the donor

3 Sex Varchar(50) NOT NULL Sex donor

4 Age int(50) NOT NULL Age of donor

Wt Varchar(50) NOT NULL Weight of donor

5

Bp Varchar(50) NOT NULL Body mass index of donor

6

Small units int(50) NOT NULL Amount of blood

7
8 Type of int(50) NOT NULL Type of donation either substitution
donation or transfusion
9 Remark int(50) NOT NULL Remark /idea
Method: Add blood(), update blood(), Delete blood(), search blood()

Add_ blood (): enables Nurse to add the course

update_ blood (): enables Nurse to edit course
Delete_ blood (): enables Nurse to delete the course

 
Table 3.1. Class diagram description of blood collect

Class diagram Add blood

name
No Field Name Data Type Description
1 Pack No int(20) PRIMARY KEY, Identification number of blood
NOT NULL
2 ABO Type Varchar(50) NOT NULL Type of the blood
3 Rh Varchar(1000) NOT NULL Rh- or Rh+
4 Small unit int(1000)NOT NULL Amount of blood
5 Date of Date The date of blood collected
collection
6 Expire date Datetime( Date of blood expired
7 Remark Varchar(50) NOTT NULL remark

Method: Add blood (), Edit blood (), Delete blood (),search blood ()

Add_ blood (): enables inventory manager to add the blood

Edit_ blood (): enables inventory manager to edit blood
Delete_ blood (): enables inventory manager to delete the blood
Search_ blood (): enables inventory manager to search blood
Table 3.1. Class diagram description of add blood

Class Total blood in stock

diagra
m name
No Field Name Data Type Description
1 Blood type Varchar(20) NOT NULL Blood type
2 No.blood type Varchar(50) NOT NULL Total Result of blood
Method: See total blood()
See Result(): enables admin
Calculate Result(): enables the system to calculate the number of blood in each type of blood
Table 3.1. Class Diagram Description of total blood In stock
Class diagram Approve request donor
name
No Field Name Data Type Description
1 No int(20) PRIMARY KEY, Identification number of blood donor
NOT NULL
2 Fullname Varchar(50) NOT NULL Name blood donor
3 Address Varchar(1000) NOT NULL Address of blood donor
4 Sex Varchar (1000)NOT NULL Sex of blood donor
5 ABO Varchar(1000) NOT NULL Type blood of blood donor
6 Type of Varchar(1000) NOT NULL Substitution/transfusion
donation
7 Session date Varchar(50) NOTT NULL Date of request asked

8 Status Varchar(50) NOTT NULL It is seen or not seen

Method: view appointment (),Delete blood (),approve ()

view appointment (): enables admin to view appointment

Delete_ blood (): enables admin to delete donor request
approve (): enables view appointment to approve request blood donation
Table 3.1. Class diagram description of approve

Class Blood collect

diagram
name

No Field Name Data Type Description

1 No int(20) PRIMARY KEY, Identification number of donor
NOT NULL

2 Fname Varchar(50) NOT NULL First Name of the donor

3 Sname Varchar(50) NOT NULL Second name of donor

4 Lname Varchar (50) NOT NULL Last name of donor

Age Varchar(50) NOT NULL Age of donor

5
 Gender
Varchar(50) NOT NULL Sex of donor
6
Address
varchar(50) NOT NULL Address blood
7
8 Username varchhar(50) NOT NULL Username of donor
9 Password varchar(50) NOT NULL Password of donor
10 Confirm varchar(50) NOT NULL Confirm password
password
11 Phone no int(50) NOT NULL Phone number of donor

12 Email Varchar (50) NOT NULL Email of donor

Method: registration of donor()

Register donor (): enables donor to register themselves

3.5 Non-Functional Requirements

The non-functional requirement of the system deals with how well the system provides service to
the user.
3.5.1 Performance
Easy to use: unlike manual the web based is easy to use because it is just
pressing a simple and single keys or symbols of.
Fast and reliable: - since the data is stored and accessed electronically, like that
of manual it cannot be failed always and Serve users efficiently.

3.5.2 Reliability
The system consistently performs its intended function e.g. the important functions are validated.
So the system is reliable.
The system is operational and consistent in that integrity of information is maintained and
supplied to the system.  
3.5.3 Availability
The system is available 24 hours /7 days to everyone. There is no delay in the availability of any
information, whatever needed, can be captured very quickly and easily. The server should be
always on to be available.
3.5.4 Security
Provide authentic and authorized features to the proposed system where private and confidential
data can only be viewed by authorized user.
3.5.5 Maintainability
To ensure that the system continues to work properly by checking it regularly and making repairs
and adjustments if required.
3.5.6 Portability
The system is machine independent and software system independent so it can be moved to
different target platforms.

3.6 Design Constraint

Project limitations typically fall into several categories. By recognizing these categories, you can
focus the investigations and thereby increase the chances that you’ll discover all limitations
affecting the project.
The project drivers and supporters may have preset expectations or requirements in one or more
of the following categories:
 Time frames: When you must produce certain results. For example, the project must
be done by September 8. We don’t know whether it’s possible to finish by September 8.
 Resources: The type, amount, and availability of resources to perform our project
work. Resources can include people, funds, equipment, materials, facilities, information,
and so on.
Activity performance: The strategies for performing different tasks.
3.7 Logical Database Requirements
 3.9 Analysis Models
3.9.1 Sequence Diagrams
The following figure represents the high-level sequence diagram of the Mettu Online Blood
Bank Information Management system. The figure describes the high level interaction of the
actors with the system that specifies the work flow of the system

Sequence Diagram for login

Figure 3. Sequence Diagram for login
Sequence Diagram for Manage account

Figure 3. Sequence Diagram for Manage account

Sequence Diagram for Add new information

Sequence Diagram For add news

add new info add new in fo Databas e

Basic
Basiccourse
courseofof <<U I>> <<Con trol>> <<DB>>
action
action a d m in

S t e p1 : adm in select add new

link

select add news

S t e p 2 :t he syst em display a dd request
news form
display

S t e p 3 : a dm in add new
avalia ble inform a tion fill new
information
submit if not valid entery
S t ep 4 :syst em check a dded
new informa tion
if valid entery
error message
S t ep 5 :syst em display news
successfully posted!! news
successfully
posted!!

Figure 3. Sequence Diagram for Add new information

Sequence Diagram for View report

Sequence Diagram For View Report

view report view report Databas e

Basic
Basiccourse
courseofof <<U I>> <<Con t rol>> <<DB>>
action
action adm in

S t e p1 : a dm in select view report

link

select the view

report
S t e p 2 :the syst em displa y request
view report page
display

insert report date

S t e p 3 : a dm in insert search
da y form at

if not valid entery

S t e p 4 : system check view

report info press serach
if valid entery
error message
S t e p 5 : system displa y
report

display report

Figure 3. Sequence Diagram for View report

Sequence Diagram for Approve

Sequence Diagram For create approve

approve Database
Basiccourse
Basic courseofof approve
<<UI>>
<<DB>>
<<UI>>
action
action admin
<<Control>>

S t e p 1 :a dm i n s el ect
a pprove l i nk
select approve
link
request
S t e p 2 :s ys t em di s pl a y
a pprove form

display form

S t e p 3 :a dm i n s era ch search approve

a pprove reques t
click search if not valid entery
S t e p 4 :t he s ys t e m di s pla y
re que s t
error message if valid entery

display donation
S t e p 5 :a dm i n cl i ck
request
a pprove but t on
view donation
if not valid entery
request click approve
S t e p 6 :s ys t em di s pl a y
reques t a pprove d if valid entery
You Have
aproved
Successfully

Figure 3. Sequence Diagram for Approve

Sequence Diagram for View comment

Sequence Diagram For view comment

view view com m en t Databas e

Basic
Basiccourse
courseofof com m en t <<Cont rol>> <<DB>>
action
action system
user
<<U I>>

S t ep 1 : select view com m ent

click view
S t ep 2 :syst em dispsly comment link
request
com m ent

S t ep 3 : a dm in view com m ent

if not valid

error message

if valid

display comment

Figure 3. Sequence Diagram for View comment

Sequence Diagram for Donation request

Sequence Diagram For Donation Request

don ation don ation

Databas e
Basic
Basiccourse
courseofof requ es t requ es t
<<D B>>
B ra nch << Con trol>>
action
action a d m in
<<U I>>

Step 1: select donation request link

click the
donation request
S t ep 2 : t he syst em display link
dona t ion request form

Step 3: fill the donation request fill the donation

form and send request form

if not valid
S t ep 4 :system sa ve t he request
in t he DB error message

if valid
S t ep 5 The syst em displa ys
acknowledgem ent
you
successffully
send your
donation request

Figure 3. Sequence Diagram for Donation request

Sequence Diagram for Searching process

Sequence Diagram For Searching Process

s ea rch i n g s ear ch i n g
D a t a bas e
Basic
B a s iccourse
cou rs eofof proc es s proce s s
< < D B> >
s yst em < < Con t rol > >
action
a ction us e r
< < U I> >

S t e p 1 :us er s elect s ea rching

link
click t h e
sear ch ing
S t e p 2 :syst em dis pla y s ea rch pr ocess lin k open
m enu

display
S t e p 3 :us er s elect wha t he fill th e
wa nt know sear ch ing for m
1.s ea rch a ppont m ent sear ch
a pprove
if n ot valid
S t e p 4 :s ys t em check s ea rching
inform a t ion er r or m essage

if valid
S t e p 5 :s ys t em displa y
s ea rching res ult
display
sear ch ing r esu lt

Figure 3. Sequence Diagram for Searching process

Sequence Diagram for Comment the system

Sequence Diagram For Comment The System

com m ent com m ent Databas e

Basic
Basiccourse
courseofof <<U I>> <<Control>> <<DB>>
system
action
action user

S t ep 1 : select comment the

system link

click comment
S t ep 2 :system dispsly the system link
comment form

S t ep 3 : write comment about write comment

the system

if not valid
S t ep 4 :system check comm ent
information
error message

if valid
S t e p 5 :syst em display sented
comment
Your comment
has been Sent
successfully!

Figure 3. Sequence Diagram for Comment the system

Sequence Diagram for Send request

Sequence Diagram For Send Request

Send Sen d Requ es t Databas e

Basic
Basiccourse
courseofof Reques t <<Control>> <<DB>>
action
action h o s pit al <<U I>>

S t ep 1 :hospit a l worker select

send request link

select send
request link
S t e p 2 :syst em display send
request form

S t ep 3 :fill request form in t he

name of pat ient fill request form
in t he nam e of
pa t ient s
S t ep 4 :t he syst em check request send
informa t ion if not valid

S t e p 5 :syst em displa y request

error message
is sends
if valid

successfully
send request

Figure 3. Sequence Diagram for Send request

Sequence Diagram for Collect blood

Sequence Diagram For Cillect Blood

collect blood collect blood Databas e

Basic
Basiccourse
courseofof <<U I>> <<Cont rol>> <<DB>>
action
action nurse

S t ep 1 : select collect blood link

click collect
S t ep 2 :syst em displa y send blood link
request form

fill collect blood

S t ep 3 : fill collect blood
info
inform ation

if not valid
S t ep 4 :syst em check collect ed
blood informa t ion
error message

if valid
S t ep 5 :syst em display a dd
collected blood
successfully add
collected blood

Figure 3. Sequence Diagram for Collect blood

Sequence Diagram for View donor registration

Sequence Diagram For Real Donor registration

real don or real donor

Databas e
Basic
Basiccourse
courseofof regis tration regs itration
<<DB>>
<<Control>>
action
action n u r se
<<U I>>

S t ep 1 : select collect blood link

click collect
S t ep 2 :system displa y register blood link
real donor form

fill collect blood

S t ep 3 : fill real
info
donorinforma tion

if not valid
S t ep 4 :system check real donor
information
error message

if valid
S t e p 5 :system display register
real donor unfo successfully
register real
donor her is
donor information

Figure 3. Sequence Diagram for View donor registration

Sequence Diagram for Testing

Sequence Diagram For Testing

Tes tin g Tes ting Databas e

Basic
Basiccourse
courseofof <<U I>> <<Control>> <<DB>>
lab
action
action technician

S t ep 1 : lab technician select

collect blood link

click testing
S t ep 2 :system display blood link
testing form

S t ep 3 : lab technician fill

blood testing information fill tesing result

if not valid
S t ep 4 :system check testing
information
error message

if valid
S t ep 5 :system display
successfully submit blood successfully
testing result subm it blood
testing result

Figure 3. Sequence Diagram for Testing

Sequence Diagram for Blood Distribution
Figure 3. Sequence Diagram for Testing
Sequence Diagram for Manage stock

Sequence Diagram For Manage Stock

m anage D a t a ba s e
m a n a g e s t oc k
Basic
B a s i c course of
cou r s e of s t ock
< < Con t rol > > <<DB>>
aaction
ct i on i n v e n t or y < < U I> >
m a n g er
S t e p 1 : invent ory m a nger s elect
m a nge s t ock link

s elect m a na ge
a ccount link
S t e p 2 : S ys t em dis p la y m a n ge
open
s t ock pa ge.

display for m

view a ler t if
s t e p 3 :in ve n tor y m a n ge r vie w expir ed blood
stock if ale r t e xpir e d blood
r em ove expir ed()
S t e p 4 :invent ory m a nger if n ot va lid
rem ove expired() from blood
s t ock error m es s a ge
if valid

S t e p 5 :S ys t em dis pla y blood

blood s ucces s fully
dis ca rd from s t ock
dis ca rd from
s t ock
if wa n t t oo a dd
ret urn s t ep 3: new blood t o
s t e p 4 :if invent ory m a nger blood s t ock
a ccept ed s a fe blood fill form open

display
S t e p 5 :invent ory m a nger s a ve
new blood t os s t ock fill a ccept ed sa fe
blood for m
save if n ot va lid
S t e p 6 :S ys t em dis pla y blood
s a ve t o blood s t ock er r or m essage

if valid

new blood
s ucces s fully a dd
blood s t ock

Figure 3. Sequence Diagram for Manage stock

 3.9.2 State-Transition Diagrams (STD)
In this part the team used to model the behaviors of the objects by drawing the state diagram.
The state diagram depicts the state of objects as their attributes change from one state to the other
state. State chart modeling is used to show the sequence of states that an object goes through, the
events that cause the transition from one state to the other and the actions that result from a state
change. The following figure shows the state of the objects of the corresponding use cases.

Figure 3. state chart diagram for login

Figure 3. Add information

Figure 3. Nurse collect blood

Figure 3. state diagram Donor registration form
Figure 3. state diagram Admin Create account
Figure 3. state diagram of Admin role
Figure 3. state diagram of Nurse role

Figure 3. state diagram of Inventory Manager

Figure 3. state diagram of lab technician role
Figure 3. state diagram donor role

17.Chapter 4: System Design

Design is view patterns seen in the analysis phase to be a pattern in a design phase. System
design is the process of defining the elements of a system such as the architecture, modules and
components, the different interfaces of those components and the data that goes through that
system. It is meant to satisfy specific needs and requirements of a business or organization
through the engineering of a coherent and well-running system.

4.1 Design Overview

The system design of Online Blood Bank Information Management System with intelligent
feedback contains different type of architecture, hardware and soft ware mapping and data of the
system that are exist. The purpose of system design is to create a technical solution that satisfies
the functional requirements for the system. At this point in the project lifecycle there should be a
Functional Specification, written primarily in business terminology, containing a complete
description of the operation.
4.2 System Architectural Design (include Component and Deployment
Diagram)
4.2.1 Chosen System Architecture
Architecture is the fundamental organization of a system, embodied in its components, their
relationship to each other and the environment, and the principles governing its design and
evolution.
Three-tier architecture is a client-server architecture in which the functional process logic,
data access computer data storage and user interface are developed and maintained as
independent modules on separate platforms. Three-tier architecture is a software design pattern
and well-established software architecture. Its three tiers are the presentation tier, application tier
and data tier.
Three tier architectures consist of three components distributed in three layers:
1. Client (requester of services),
2. Server (provider of services) and
3. Database.
The three components made the three-tier architecture.
1. User System Interface (such as session, text input, dialog, and display output services).
2. Application server
3. Database Management server (such as data and file services).
Why we choose three-tier architecture?
Because of the system is distributed application with client which are distributed around
different area hence each need to contact the central server to get some service which in turn
contacts the Database server for persistent data storage and retrievable. Based on this scenario it
is straight forward to select 3-tier architecture.
Figure 3. Tier architecture in deployment

4.2.2 Deployment Diagram

The name Deployment itself describes the purpose of the diagram. Deployment diagrams are
used for describing the hardware components where software components are deployed.
Component diagrams and deployment diagrams are closely related. Component diagrams are
used to describe the components and deployment diagrams shows how they are deployed in
hardware. UML is mainly designed to focus on software artifacts of a system. But these two
diagrams are special diagrams used to focus on software components and hardware components.
So most of the UML diagrams are used to handle logical components but deployment diagrams
are made to focus on hardware topology of a system. Deployment diagrams are used by the
system engineers.
The purpose of deployment diagrams can be described as:
 Visualize hardware topology of a system.
 Describe the hardware components used to deploy software components.
 Describe runtime processing nodes.
 Application
Manage account

Web server Database server

Customer computer Add new info

View report

Web browser PHP

Approve
MYSQL

View comment

Wamp Register
Database

Donation request

Search

Give comment

Manage stock

Mozila firefox DIstribute

Generate report

Collect blood

View d.reg

Send request

Test blood

Fig
ure 3. Deployment diagram

4.2.3 System Interface Description

The system will remain operational and its functionality will be complementary but
independent from the online blood bank information management system of the donor and
patient. At any time, user may use either the user service system or the online registration.
The online user creation will be operational even if the user service system is offline also
the system interfaces are not needed during the development of this project that the system
is connected with organization data base.

4.3 Component Diagram

Component diagram is a special kind of diagram in UML. The purpose is also different from all
other diagrams discussed so far. It does not describe the functionality of the system but it
describes the components used to make those functionalities. So from that point component
diagrams are used to visualize the physical components in a system. Component diagrams can
also be described as a static implementation view of a system. Static implementation represents
the organization of the components at a particular moment. A single component diagram cannot
represent the entire system but a collection of diagrams are used to represent the whole.
So the purpose of the component diagram can be summarized as:
 Visualize the components of a system.
 Construct executables by using forward and reverse engineering.
 Describe the organization and relationships of the components.
 Application server
Client Database server

Manage account

Add new info

View report
Admin

Approve

Security
View comment

Donor
Register

Donation request

Inventory manager Search

Give comment

Manage stock Persistence

Hospital

Distribute

collect blood

Nurse
View d.reg
Da t a b a s e

Send request

Lab technician Testing blood

Figure 3. Component diagram

4.3.1 Detailed Description Of Components

Component name Component number Description Of Components

#1 Login page which enables

Login page user of system log into system
by entering their user name
and password.
#2 User interface part where main
page of the OBBIMS would
Home page be viewed and link for related
interface.
#3 The system Admin Page is the
page that enables the system
Administrator page Administrator to manage user
account (add, update and
modify the user account for
users of the system.
Inventory Manager page #4 It is the page contains all
activities of the Inventory
manager Enables to manage
blood in stock.
Donor page #5 Donor can login into the
system and make appointment
and view appointment from
the system

Lab Technician #6 It is the page contains all

activities that would be done
by Lab Technician. Enables to
test blood and collect the
blood that obtained from
donor.
Hospital page It is the page contains all
#7 activities that would be done
by hospital. Request blood
through patient name and
register patient.
Table 4. Table that shows detailed description of component
4.4 User Interface Design
Application will be accessed through a Browser Interface. The software would be fully
compatible with Microsoft Internet Explorer, Mozilla Firefox and Google Chrome. No user
would be able to access secured part of the application (such as appointment, request page,
account settings etc.) without logging on to the system. The system should be accessed over
WAN.
The OBBIMS is also user friendly that it is simple to be used by any users. The user interface of
this application is shown bellow.
4.4.1 Description of the User Interface
Admin: create the staff and manage the system.
Donor: a person, who is voluntarily to donate blood, register, make appointment.
Hospital: send blood request through patient name.
Nurse: collected blood from donor and give pack number for the blood component.
Lab technician: tests the incoming blood packet, grade the blood packet usable or not
usable.
Inventory manger: accept safe blood from lab technician. Manage stock and he also
processes the request from the person through hospitals.

4.4.2 Screen Images

I. Home Page: This form contains some links which lead it to the concerned page,
and if the user has an account he/she will directly go to concerned page by entering
their username and password
Figure 4. Home Page
Figure 4. Home Page
 II. Log In form:-this form found immediately following the home page. Home page appears
as the site on which the system is deployed is opened. System user will have their own
password. Those forms appeared using password and user name will not accessible by other
persons except for those who have privilege.

Figure 4. Log In form

Figure 4. Log In form
 III. Donor Registration form

Figure 4. Donor Registration form

IV. Collect Blood form
Figure 4. Collect Blood form
 V. Hospital Registration form

Figure 4. Hospital Registration form

4.4.3 Objects and Actions

The Administrator Login page consists of:
Id text box – the administrator writes his/her id (string, max_length 40 characters)
Password text box – the administrator writes his/her password (string, max_length 40 characters)
 Log in button – after being pressed the system performs user authentication. If the
administrator inputs correct data, he/she gets the access to the system. Otherwise, the
system displays please inter valid username/password massage in error page.
The Main Page is the user page that provides him/her with the access to other pages he/she
intends to visit. It contains of:
 Logo of the company
The User Login Page is contain select account type. It consists of the:
 text boxes for users username and password,
 18.Chapter 5: Testing
5.1 System Overview
This test document defines all the procedures and activities required to prepare for testing
of the functionalities of the system . Functional testing consists of a series of functional tests
of workflows and transactions created and executed to identify and measure the quality of
software. The testing will simulate user interaction with the system so that functionality of the
system can be evaluated with different User Roles. The objectives of the test plan are to
define the activities to perform testing, define the test deliverable documents and to identify
the various risks and contingencies involved in testing.

5.2 Test Approach

Testing is an empirical investigation conducted to provide stake holders with information about
the quality of the product or service under test, with respect to the context in which it is intended
to operate. Some new projects are testing also provides an objectives, independent view of the
new system to allow the user to appreciate and understand the testing including.
Allow the user to appreciate.
Understand the risks at implementation of the new system
Defects and failures
5.3 Test Plan
In case of Online Blood Bank Information Management system the following testing
mechanisms are used:

5.3.1 Testing
It is typically done by system developer during system development and the team tested different
service of the system and checked the effectiveness of the system and weather they are
computable to Online Blood Bank Information Management system. These testing include:
Web based Online Blood Bank Management system
Web based view appointment.
Web based request blood donation.
Web based submit request blood.

5.3.1 White Box Testing

In this type of testing, skilled man in different programming languages tries to test the logic of
our system. If the person who tests the system is not skilled, it is difficult to understand our
systems functionality. If any failures occur while testing the system in all of the above testing
methods, the team will take immediate correction where this fault occurred before jumping to
next work. So, that it will meet the goal.

5.3.2 Black Box Testing

To test our system, the tester may use black box testing, if he/she has not enough time to check
internal modules or codes. By looking only input /output or user interface, the tester can test our
systems functionalities without looking the internal code. We used this testing technique for the
following reasons:-

 This testing type is more effective on larger units of code

 Tester needs no knowledge of implementation, including specific programming
languages
 Tester and programmer are independent of each other
 Testers are done from a user's point of view

5.3.3 Functional Tests

Functional tests provide a systematic demonstration that functions tested are available as
specified by the business and technical requirements, system documentation, and user manuals.
Functional testing is centered on the following items:
F Valid Input: identified classes of valid input must be accepted.
F Invalid Input: identified classes of invalid input must be rejected.
F Functions: identified functions must be exercised.
Test objectives:
F All field entries must work properly.
F Pages must be activated from the identified link.
F The entry screen, messages and responses must not be delayed.
 5.3.1 Features to be Tested
The following list describes the features to be tested:
USER
F Registration
F Login
ADMIN:
 Delete user
 login
 Manage user
5.3.2 Features not to be Tested
 Data base server recovery and maintenance will not be tested. Internal errors i.e.
communication and other outside system components related to the system
5.3.3 Testing Tools and Environment
The following resources requirements are needed for testing the hardware and software
components of the system.
Hardware Requirement and Software Requirement (recommended)
F Processor speed: 2.0GHz
F RAM size: 1gb
F Hard disk size: 80GB
F Network card and fast Ethernet port for networking and connectivity.
F 4.0 GB RAM for server side
F 3.6 GHz processor for server side
F Windows Os (XP and above)
F Windows Server 2003/2008
Table 4. Test case to register

Test Case 1: Register donor

Test case objective : To register donor
 Test case description: the donor hem self enters basic info of the donors, and then presses
create button. Client program contacts with server, server contacts with the database, and
database checks for registration and sends message to the donor himself.
Requirements Verified: Yes
Test Environment: Apache Mysql server must be in running state, Database Should contain
appropriate table and link must be established between server and client program.
Test Setup/Pre-Conditions: Apache server should be in running state and all fields should be
filled.
Actions Expected Results

The donor presses the register menu. Displays registration page.

Donor should enter donors information Displays success message
If some fields are not filled the system display to fill the fields again.

Table 4. Login

Test Case 2: Login

Test case objective : To access the system
Test case description: System user enters Username and Password, then presses login button.
Client program contacts with server, server contacts with the database, and database checks for
authentication and displays System user page.
Requirements Verified: Yes
Test Environment: Apache Mysql server must be in running state, Database Should contain
appropriate table and link must be established between server and client program.
Test Setup/Pre-Conditions: Apache server should be in running state and User name and
Password fields should be filled correctly.
Actions Expected Results
The System user should enter the correct user name and Displays System user page.
password to login.
If user name and password are not filled correctly the system display to fill the user name and
 password again.

19.Chapter 6
Conclusion

It is known that developing online system for Mettu blood bank information management system
is not easy. It is also very difficult for the project members to gather the documented data
because the project area does not have documented materials. But the team has developed
interesting online information management system for Mettu blood bank.
It is flexible, accurate and attractive with easy GUI approach. Generally, the team confidently
can ensure that the software is completed successfully with negligible errors. Finally the team
expects that the developed system will change the general information management atmosphere
of the Mettu blood bank information management system, and makes it more reliable and
efficient than the previous manual system.

6.1 Summary of Final product

In general, the project (system) that the team developed will benefit the organization by changing
its business range from manual to computerize by developing web based application.

The overall benefits of the system are:

F Provide sufficient services.

F Minimize the time required to perform task.
F Facilitates the services given by the organization.
F Attract more users get reliable and sufficient service.
F Reducing human power and cost that are spent on the manual system.

While developing a system in Team the group member have acquired more knowledge and
experience about the different phases of the software development life-cycle, design and other
programming language as software developers, the team has worked together and assessed risks.

6.2 Recommendation
While doing this system the team members has faced different challenges. But by the
cooperation of all the group members and the advisor the team is now able to reach to the final
result. I.e. all the group members strongly fight these challenge and take the turn to the front.

So now all the group members strongly recommend the department that for the coming students,
it has to provide them with better service than the present in better hard ware, guaranteed
software’s, giving orientations how to proceed, offering guest to provide them with more
experienced work, support morally, manually, forming good relation with students, giving
students description of each phases and so on. So that it will get what it expects from its students
and satisfy with them. Neatly, the team would recommend that further work should be done on the
system in order to make the system perform better like official website of others. For example currently,
for Mettu blood bank information system.
In this paper we have done a lot for the proposed system as much as possible. But it does not
cover the whole applications for wide use. For that matter we wish to add some features of the
system to be included in the future. Some of the features are the following:-
 Profile of the users e.g photo of the user .

6.3 Future Work

F Make the system friendly in such a way that anyone can use the system using Small
devices which have narrow screen resolution such as smart phones.
F Make the system help blind people by making sound sensor machine.
F Capable of sending text messages to mobiles after donor donate blood.

References
Gundu, Handbook of Blood Banking and Transfusion Medicine, 2006

Textbook of Blood Banking and Transfusion Medicine, February 2005

(Sally V. Rudmann, Textbook of Blood Banking and Transfusion Medicine - Pageburst E-Book
on VitalSource (Retail Access Card), 2nd Edition, 2005)
http://nevonprojects.com/online-blood bank-project /the software system is an online blood
bank management

Video is a screen shot of a real time project called blood bank management system created by
praghalya

Appendix
 Source Code(important sections )
Index source code
<?php
require_once('function.php');
session_start();
?>
<!doctype html>
<html><br>
<head>
<link rel="stylesheet" type=" text/css" href="css/nav.css">
<!--<link href="../FrontEnd/css/admin_panel_home.css" rel="stylesheet"
type="text/css" /-->
<link href="css/admin_panel.css" rel="stylesheet" type="text/css" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>INDEX</title>

<link rel="stylesheet" href="css/layout.css" type="text/css" media="screen" />

<!--[if lt IE 9]>
<link rel="stylesheet" href="css/ie.css" type="text/css" media="screen" />
<script
src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
 <script src="js/jquery-1.5.2.min.js" type="text/javascript"></script>
<script src="js/hideshow.js" type="text/javascript"></script>
<!--<script src="js/jquery.tablesorter.min.js"
type="text/javascript"></script>-->
<!--<script type="text/javascript"
src="js/jquery.equalHeight.js"></script>-->
<script type="text/javascript">
$(document).ready(function()
{
$(".tablesorter").tablesorter();
}
);
$(document).ready(function() {

//When page loads...

$(".tab_content").hide(); //Hide all content
$("ul.tabs li:first").addClass("active").show(); //Activate first tab
$(".tab_content:first").show(); //Show first tab content

//On Click Event

$("ul.tabs li").click(function() {

$("ul.tabs li").removeClass("active"); //Remove any "active" class

$(this).addClass("active"); //Add "active" class to selected tab
$(".tab_content").hide(); //Hide all tab content

var activeTab = $(this).find("a").attr("href"); //Find the href attribute

value to identify the active tab + content
$(activeTab).fadeIn(); //Fade in the active ID content
 return false;
});

});
</script>
<script type="text/javascript">
$(function(){
$('.column').equalHeight();
});
</script>

<style type="text/css">
table.test {
width : 20000px;
/*border-collapse : collapse;*/
table-layout : fixed;
background:#FFF;

th.author {
width : 120px;
border : 1px solid red;
}

th.di {
width : 150px;
border : 1px solid red;
}

td.long {
overflow : hidden;
white-space : nowrap;
width : 50px;
border : 1px solid black;
}

th.id {
overflow : hidden;
white-space : nowrap;
width : 30px;
border : 1px solid black;
}

th.title {
overflow : hidden;
white-space : nowrap;
width : 100px;
border : 1px solid red;
}

th.heading {
overflow : hidden;
white-space : nowrap;
width : 2400px;
border : 1px solid red;
}

th.body {
overflow : hidden;
white-space : nowrap;
width : 25000px;
border : 1px solid red;
}

th.ed {
overflow : hidden;
white-space : nowrap;
width : 50px;
border : 1px solid red;
}

td.id {
overflow : hidden;
white-space : nowrap;
width : 30px;
border : 1px solid red;
background:#C63;
}

td.title {
overflow : HIDDEN;
white-space : nowrap;
width : 100px;
border : 1px solid red;
 text-align:center;
}

td.heading {
overflow : HIDDEN;
white-space : nowrap;
width : 200px;
border : 1px solid red;
word-wrap: break-word;
text-align:center;
}

td.body {
overflow-y:scroll;
overflow-x: scroll;
overflow : scroll;

/*height:80px;*/ /*word-wrap: break-word;*/

/*word-wrap: break-word;*/
white-space : nowrap;
width : 800px;
border : 1px solid red;
text-align:center;
text-overflow: ellipsis;
overflow: auto;
position:relative;
}

td.author {
overflow : scroll;
white-space : nowrap;
width : 100px;
border : 1px solid red;
text-align:center;
}

td.di {
overflow : hidden;
white-space : nowrap;
width : 50px;
border : 1px solid red;
text-align:center;
}

td.ed {
overflow : hidden;
white-space : nowrap;
width : 50px;
border : 1px solid red;
text-align:center;
background:#3CF;
}

td.blank {
width : auto;
 border : 1px solid red;
height: auto;
border-bottom-style: groove;
padding: 10px;
}

/*p.test
{
word-wrap:break-word;
}*/

.style1 {
font-size: 12px;
font-weight: bold;
}
</style>

<center>
<?php include("adlogo.php"); ?>

<?php include("indexverticalbar.php"); ?>

</head>

<body link="#0066FF" vlink="#6633CC" bgcolor="#FFFFCC"

background="images/image001.jpg" style='margin:0'>

<!--div class="container">
<div class="header">
 <p>-->

<script src="js/validateaccount.js" language="javascript"

type="text/javascript"></script>
<style type="text/css">
body{

font-family:"Times New Roman", Times, serif;

color:#000000;
}
h2{
text-align:center;
font-size:36px;
margin:0px;
}
</style>
<table ><td>
<html lang="en">
<head>
<style>
body {font-family:Arial, Helvetica, sans-serif; font-size:12px;}

.fadein {
position:relative; height:332px; width:600px; margin:0 auto;
background: url("slideshow-bg.png") repeat-x scroll left top transparent;
padding: 10px;
}
.fadein img { position:absolute; left:10px; top:10px; }
</style>
 <script
src="http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js"></script>
<script>
$(function(){
$('.fadein img:gt(0)').hide();
setInterval(function(){$('.fadein :first-
child').fadeOut().next('img').fadeIn().end().appendTo('.fadein');}, 3000);
});
</script>

</td><td>

</img></div>

<div class="fadein" align="center">

<img src="images/5.JPG" width="600" height="400">
<img src="images/22.jpg" width="600" height="400">
<img src="images/10.jpg" width="600" height="400">
<img src="images/1t.jpg" width="600" height="400">
<img src="images/2t.jpg" width="600" height="400">
<img src="images/55.jpg" width="600" height="400">
<img src="images/14.jpg" width="600" height="400">
<img src="images/7.jpg" width="600" height="400">
<img src="images/20.jpg" width="600" height="400">
<img src="images/15.jpg" width="600" height="400">

<br><br>
</div>
</body>
</html>
<html>
<body>
<script src="js/validateaccount.js" language="javascript"
type="text/javascript"></script>
<style type="text/css">
body{

font-family:"Times New Roman", Times, serif;

color:#000000;
}
h2{
text-align:center;
font-size:36px;
margin:0px;
}
</style>
<p><br><br><br> <font size="3"
color="blue"><h2><Blink><Blink/></h2>
"Give blood for those who give life. Safe blood for saving mothers"<br>
Money people die because of lack of blood be hero by donating your blood
to save life.
</font></p>
<br>
</div>
</table>
 <?php include("footer.php"); ?>
</div>

</div>
<!---------------------------------- end container -------------------------------->
</td>
</table>
</body>

</table>
<br/>
</body>
</html>

 Test Logs
<?php
require_once('function.php');
session_start();
?>
<!doctype html>
<html><br>
<head>
<html>
<link rel="stylesheet" type=" text/css" href="css/nav.css">

<link href="css/admin_panel.css" rel="stylesheet" type="text/css" />

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<head><title>LOGIN PAGE</title></head>
<link rel="stylesheet" href="css/layout.css" type="text/css" media="screen" />

<script type="text/javascript">
function validateForm()
{

var y=document.forms["login1"]["username"].value;
var a=document.forms["login1"]["password"].value;
if( document.loginp1.position.value == "-1" )
{
alert( "Please select your account type!" );
document.login1.position.focus() ;
return false;
}
if ((y==null || y==""))
{
alert("you must enter your username");
return false;
}
if ((a==null || a==""))
{
alert("you must enter your password");
return false;
}
return true
}
</script>

<script>
 function ValidateAlpha(evt)
{
var keyCode = (evt.which) ? evt.which : evt.keyCode
if ((keyCode < 65 || keyCode > 90) && (keyCode < 97 || keyCode >
123) && keyCode != 32 && keyCode != 8 && keyCode != 9)
{
alert(" Only letters are allowed! ")
return false;
}}

function isNumberKey(evt)
{
var charCode = (evt.which) ? evt.which : event.keyCode
if (charCode > 31 && (charCode < 48 || charCode > 57)){
alert("Only number is allwed!")
return false;

</script>
<style type="text/css">
table.test {
width : 1000px;
/*border-collapse : collapse;*/
 table-layout : fixed;
background:#FFF;

th.author {
width : 120px;
border : 1px solid red;
}

th.di {
width : 150px;
border : 1px solid red;

td.long {
overflow : hidden;
white-space : nowrap;
width : 50px;
border : 1px solid black;
}

th.id {
overflow : hidden;
white-space : nowrap;
width : 30px;
border : 1px solid black;
}
th.title {
overflow : hidden;
white-space : nowrap;
width : 100px;
border : 1px solid red;
}

th.heading {
overflow : hidden;
white-space : nowrap;
width : 100px;
border : 1px solid red;
}

th.body {
overflow : hidden;
white-space : nowrap;
width : 150px;
border : 1px solid red;
}

th.ed {
overflow : hidden;
white-space : nowrap;
width : 50px;
border : 1px solid red;
}
td.id {
overflow : hidden;
white-space : nowrap;
width : 30px;
border : 1px solid red;
background:#C63;
}

td.title {
overflow : HIDDEN;
white-space : nowrap;
width : 100px;
border : 1px solid red;
text-align:center;
}

td.heading {
overflow : HIDDEN;
white-space : nowrap;
width : 200px;
border : 1px solid red;
word-wrap: break-word;
text-align:center;
}

td.body {
overflow-y:scroll;
overflow-x: scroll;
 overflow : scroll;

/*height:80px;*/ /*word-wrap: break-word;*/

/*word-wrap: break-word;*/
white-space : nowrap;
width : 800px;
border : 1px solid red;
text-align:center;
text-overflow: ellipsis;
overflow: auto;
position:relative;

td.author {
overflow : scroll;
white-space : nowrap;
width : 100px;
border : 1px solid red;
text-align:center;
}

td.di {
overflow : hidden;
white-space : nowrap;
width : 50px;
border : 1px solid red;
text-align:center;
}

td.ed {
overflow : hidden;
white-space : nowrap;
width : 50px;
border : 1px solid red;
text-align:center;
background:#3CF;
}

td.blank {
width : auto;
border : 1px solid red;
height: auto;
border-bottom-style: groove;
padding: 10px;
}

/*p.test
{
word-wrap:break-word;
}*/

.style1 {
font-size: 12px;
font-weight: bold;
}
</style>
</head>

<body link="#0066FF" vlink="#6633CC" bgcolor="#FFFFCC"

background="images/image001.jpg" style='margin:0'>
<!--div class="container">
<div class="header">
<p>-->
<center>
<form>
<?php include("adlogo.php"); ?>
</form>
<form>
<form>
<?php include("indexverticalbar.php"); ?>
</form>
<script src="js/validateaccount.js" language="javascript"
type="text/javascript"></script>
<style type="text/css">
body{

font-family:"Times New Roman", Times, serif;

color:#000000;
}
h2{
text-align:center;
font-size:36px;
margin:0px;
}
</style>
<br><br><br><br>
<form id="form1" name="login1" method="post" action="login1.php"
onSubmit="return validateForm()" >

<img src="images/login.jpg" align="left" width="200" height="200">

<div style="background-color:#MELKAMU; font-family:Arial, Helvetica,
sans-serif; color:#000000; padding:5px; height:10px;">

<h1 ALIGN=left><font>Login Here</font></h1><br><br>

</div>

</div>
<table width="300" align="left" >
<tr>
<td colspan="2">
</td>
</tr><tr rowspan="7">
<td colspan="4"></td>
<TR VALIGN="top">
<TD>
<DIV ALIGN=left>
<DIV ALIGN=down>
<B><font color="#993366"> Login as
:&nbsp;&nbsp;&nbsp;<B>
<select size="1" name="account_type" placeholder =
"account_type"required >
<option value="" >--Select--</option>
<OPTION>Administrator</option>
 <OPTION>Nurse</option>
<OPTION>Inventory Manger</option>
<OPTION>Lab technician</option>
<OPTION>Donor</option>
<OPTION>Hospital</option>
</SELECT></font>
</DIV><br/>
<TR>
<TD><font color="#993366"><B>User Name:</B></font>
<INPUT NAME="username" TYPE=TEXT onKeyPress="return
ValidateAlpha(event)"required /></TD><BR><BR>
</TR> <TR>
<TD><font
color="#993366"><B>Password:&nbsp;&nbsp;&nbsp;</B></font>
<INPUT NAME="password" TYPE=PASSWORD required></TD>
</TR>
<TR>
<TR>
<TD> <pre> <INPUT NAME="Submit" TYPE=SUBMIT
VALUE=Login> <INPUT NAME="Reset" TYPE=RESET VALUE=Clear>
</pre></TD>
</TR>
</TR>
<TR>
<center> <tr><td colspan="2"><a href="password.html"><i>
Forgot Password?</i></a></td></tr></center>
</TR>
</TR>
</DIV>
 </TD>
</TR>
</form>
</div>

</tr>
</table><br><br><br><br><br><br><br><br><br><br><br><br><br><br><
br><br>

<?php include("footer.php"); ?>

</body>
</html>