JIMMA UNIVERSITY

INSTITUTE OF TECHNOLOGY
DEPARTMENT OF COMPUTER SCIENCE

REQUIRMEN SPECIFICATION, ANALYSIS AND SYSTEM DESIGN OF

ONLINE BLOOD DONATION RESERVATION AND MANAGEMENT
SYSTEM FOR JIMMA UNIVERSITY HOSPITAL

BY
Ibrahim Alesso AND Jafer Abdella
Advisors:
1. Mr. Murali Krishna (Msc)
2. Mr. Tsigab Gebre(Bsc)

A Document is submitted to JU School of graduate for BA in Computer Science

January 16-2013

Jimma University Department of Computer Science Page i

 Acknowledgment

First and foremost 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 Murali and co advisor tsigab for guiding and
correcting various documents of ours with attention and care. They both have give time and go
through the project and made necessary correction as and when needed.
In addition, we would like to forward our gratitude to Jimma University Blood Bank Worker who
helped us by providing information and by giving useful documents and materials that are useful
for our project.
We would also thank our Department and our faculty members without whom this project would
have been a distant reality.

Abstract
Online Blood Donation Reservation and Management System (OBDRMS) is
a web database application that enables the public to make online session reservation,
to view blood donation events online and at the same time provides
centralized donor and blood stock database. This application is developed by using
JSPIServlet technology from J2EE with the MySQL 5.0 as the database management
system. The methodology used to develop this system as a whole is Object Oriented
Analysis and Design; whilst, the database for OBDRMS is developed by following
the steps in Database Life Cycle. The targeted users for this application are the
public (donor) who is eligible to donate blood, Blood Seeker, administrator from
Blood Bank Center and the staffs who are working in the blood banks of the
participating hospitals. The main objective of the development of this application is
to overcome the problems that exist in the current system, which is the lack of

Jimma University Department of Computer Science Page ii

facilities for online session reservation and online advertising on the blood donation events, and
also decentralized donor and blood stock database.

Besides, extra features in the system such as security protection by using password,
generating reports, reminders of blood stock shortage and workflow tracking can
even enhance the efficiency of the management in the blood banks. The final result
of this project is the development of web database application, which is the OBDRMS.
Figure Figure content
Figure 1.1 time scheduling
Figure 2.1 use case diagram
Figure 2.2 Sequence diagram for Create Account
Figure 2.3 Sequence diagram for Registration
Figure 2.4 Sequence diagram for for Blood Bank Information Details
Figure 2.5 Sequence diagram for Stock Management Details
Figure 2.6 Sequence diagram for Blood Collection
Figure 2.7 Sequence diagram for Blood Donation
Figure 2.8 Sequence diagram for Screening
Figure 2.9 Sequence diagram for Refer Friend
Figure 2.10 Sequence diagram for Approve
Figure 2.11 Sequence diagram for Distribution
Figure 2.12 State chart diagram for Login
Figure 2.13 State chart diagram for Registration
Figure 2.14 State chart diagram for Blood Bank Information Details
Figure 2.15 State Chart diagram for Stock Management store
Figure 2.16 State Chart diagram for Screening
Figure 2.17 State chart Diagram for Blood Collection
Figure 2.18 State chart diagram for Blood Donation
Figure 2.19 State chart Diagram for Refer Friend
Figure 2.20 State Chart Diagram for Approvance
Figure 2.21 Activity Diagram for Login
Figure 2.22 Activity Diagram for Registration
Figure 2.23 Activity Diagram for Blood Bank Information Details
Figure 2.24 Activity Diagram for Stock management
Figure 2.25 Activity Diagram for Blood Collection
Figure 2.26 Activity Diagram for Blood Donation
Figure 2.27 Activity Diagram for Refer Friend
Figure 2.28 State Chart diagram for Distribution

Jimma University Department of Computer Science Page iii

 Figure 2.29 Class diagram
Figure 2.30 Home page User interface
Figure 3.1 software architecture
Figure 3.2 F Subsystem decomposition
Figure 3.3 Component diagram
Figure 3.4 Deployment diagram
Figure 3.5 persistence modeling

Jimma University Department of Computer Science Page iv

 Contents
CHAPTER ONE...........................................................................................................................................1

1........................................................................................................................................INTRODUCTION
.................................................................................................................................................................... 1

1.1 Project Background.............................................................................................................................1

1.2 Problem statement.............................................................................................................................2

1.3 Objective of the project......................................................................................................................2

1.3.1 General objectives........................................................................................................................2

1.3.2 Specific objectives........................................................................................................................3

1.4 Methodologies....................................................................................................................................3

1.4.1 Data Collection methodology.......................................................................................................3

1.4.2 System development methodologies and tools.............................................................................4

1.5.1. Economic Feasibility:...................................................................................................................4

1.5.2. Technical Feasibility:...................................................................................................................5

1.7 Significance of the project...............................................................................................................6

1.8 Time scheduling..............................................................................................................................7

CHAPTER TWO..........................................................................................................................................8

ANALYSIS...................................................................................................................................................8

2.1 Existing System....................................................................................................................................8

2.2 New System.....................................................................................................................................9

2.2.1 Non-functional Requirements and Constraints........................................................................9

2.2.2 Functional Requirements.........................................................................................................9

2.2.3 Use case diagram...................................................................................................................11

2.2.5 Sequence diagram..................................................................................................................21

Jimma University Department of Computer Science Page v

 2.2.6 State chart diagram.....................................................................................................................32

2.2.7 Activity diagram.........................................................................................................................41

2.2.8 Class Responsibility and Collaboration for New System...........................................................49

2.2.9 Class diagram.............................................................................................................................51

2.2.10 Identifying change cases...........................................................................................................53

2.2.11 User interface prototyping........................................................................................................53

CHAPTER 3...............................................................................................................................................56

SYSTEM DESIGN.....................................................................................................................................56

3.1 Introduction......................................................................................................................................56

3.2 Design Goals......................................................................................................................................56

3.3 Proposed software architecture......................................................................................................57

Software architecture is structured into three layers by dotted lines. Each layer is an abstraction of
functionality. The layer on the bottom offers data management functionality to the services layer. And
the services layer offers functionality to several clients on the Internet. Each layer is build onto the
functionality of the next layer down the stack.......................................................................................57

Figure 3.1 software architecture..............................................................................................................58

3.3.1 Subsystem decomposition......................................................................................................58

3.3 Component diagram.......................................................................................................................61

3.4 Deployment diagram.....................................................................................................................62

3.5 Persistence Modeling for object oriented database........................................................................62

3.7 Access Control and Security.............................................................................................................65

Reference................................................................................................................................................65

Jimma University Department of Computer Science Page vi

Jimma University Department of Computer Science Page 7
CHAPTER ONE
1. INTRODUCTION

1.1 Project Background

The system that is going to be developed is Online Blood Donation Reservation and Management
System (OBDRMS).Blood cannot be created by any means; it can only be collected from people.
Online blood donation reservation and management system is a part of Red Cross whose mission
is to mobilize the power of humanity for improving the lives of the vulnerable. It is a web-based
database application system that is to be used by the hospital blood bank or blood center as a
means to advertise the nationwide blood donation events to the public in order to raise up the
public awareness on the events and at the same time allows the public to make online reservation
on their desired session. In addition, the system also provides functions for the hospital
administrators to manage the appointments made by the donors, the blood stock and donor. This
system also has the ability to keep track of the donor's donation records and the blood stock in
the blood bank. This project intends to computerize the blood and donor management system in a
hospital blood bank in order to improve the record management efficiency due to the grown size
of records of data.

Jimma University Department of Computer Science Page 1

1.2 Problem statement
 Every year our nation requires about more units of blood, out of which only a less units of
blood are available. This implies, people do not want to donate blood. Often they are
unaware of the need and also they do not have a proper facility to enquire about it.
 Currently, the public can only know about the blood donation events through
Conventional media means such as radio, news paper or television advertisements.
Since these ask more budget the company does not using any advertisements.
 Besides, for those who want to make blood donation, they cannot make early
reservation or booking on the session and day that they are free. It is a very important facility
for those who are very busy and yet enthusiastic people to know and be sure when they can
make blood.
 The current system that is using by the blood bank of most of the government
hospital is manual system. With the manual system, there are problems in managing
the donors' records. Without an automated management system, there are also problems in
keeping track of the actual amount of each and every blood type in the blood bank.

1.3 Objective of the project

1.3.1 General objectives

 To develop a web-based portal to facilitate the co-ordination between supply and demand of
blood. 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.
 To automate the 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.

Jimma University Department of Computer Science Page 2

1.3.2 Specific objectives
After defining the problems exist in the current system, the objectives of the OBDRMS are
as follows:-
 To provide a means for the hospital's blood bank to publicize information about the
blood donation events to the public.
 To allow the public and organization to make online reservation on the day and session
that they want or free to make blood donation.
 To provide an efficient donor and blood stock management functions to the blood
bank by providing the logging functions in order to control and trace the workflow
 To provide authentic and authorized features to the current system where private and
confidential data can only be viewed by authorized user.
 To provide the recording functions for every process of the blood in order to keep track
of the blood stock accurately.
 To improve the efficiency of blood stock management by alerting the blood bank
administrator when the blood quantity is below its par level.
 To provide synchronized and centralized donor and blood stock database to the blood
bank

1.4 Methodologies
1.4.1 Data Collection methodology
Data source for this project is the office JU hospital blood bank and representatives of the office.
We got information by interviewing and observation. We have used different methods to collect
data. Data collection is the most important part of our project to find the main requirement of the
system and to understand how the system does.
A. Interviews
This is one of the methods used for the collection of data in which the project designers have the
chance of asking different questions to the organization employee for obtaining the required
information and data. The project designers used this kind of collecting data most of the time.
We have collected enough information and we could make another appointment if we want
additional information concerning the existing system.

Jimma University Department of Computer Science Page 3

B. Observation
This is another type of method for collecting data and information in which we could witness the
actual events which will happen in the organization. In this method all we have to do is
observation and note down the events what we observed.

1.4.2 System development methodologies and tools

The technologies used to develop OBDRMS are listed as below: -
Operating System: Windows 7, window xp.
Database Management System (DBMS): MySQL
Technology: JSPIServlet from Java 2 Platform, Enterprise Edition (J2EE)
Browser: Google chrome, Internet explorer, Firefox
Documentation:
I. Report: Microsoft Word
II. Unified Modeling Language (UML) Diagrams: Rational Rose 2000
III. Gantt Chart: Microsoft Project 2003
A feasibility is conducted to identify the best system that meets the all the requirements. This
includes an identification description, and evaluation of the proposed systems and selection of
the best system for the job.
1.5.1. Economic Feasibility:
Economic feasibility is the most important and frequently used method for evaluating the
effectiveness of the proposed system. Cost benefit analysis is usually performed for this purpose.
The organization does not using any media advertization 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. Everyone can advertize to his/her friend in simple way.

Jimma University Department of Computer Science Page 4

 1.5.2. Technical Feasibility:

The organization was using manually and in some part automation. For example they use
automation for only storing the information and data. Therefore our system simplifies their work
effectively.
1.5.3 Time feasibility.
This feasibility is most important because time has more effect on project success/failure. The
organization was decide when reservation was made for the voluntary donars.But this project is
very important to make reservation on the session and day that they are free.
1.6 Scopes and significance
 The deliverable of this project is the OBDRMS, which is a web-based database application
system
 This project allows the blood bank administrator to publicize blood donation events online. The
public can view the venue and time of the blood donation drives to be held.
 The public can make online reservation on their desired session and date. The blood centers'
administrators can then manage their appointments by either to approve or reject the
appointments.
 The blood bank administrators can manage the blood stock starting from the blood collection, to
blood screening, processing, storage, transference and lastly transfusion through this system e.i
responsible for storing blood donor records organizing, analyzing, and preparing reports.
 The system will also give an alert to the administrator whenever the blood quantity is below its
par level.
 The records of all donors and their history are kept in one centralized database and thus reducing
duplicate data in the database. Donors can make blood donation in any blood center and their
records are maintained by the OBDRMS.
 The system is able to generate pre-defined reports such as the list donors, Staffs, and hospitals,
the blood quantity in a blood bank, and the workflow for each blood donation process.

Jimma University Department of Computer Science Page 5

 1.7 Significance of the project
 The system provides security features through password security where only authorized user can
access to the system with different authorization level.
 Inadequate blood supplies at the hospitals and medical sectors have always been a problem. To
create awareness among public of importance of donating blood, and means that available at all
the time plays a crucial role in providing information.
 With the implementation of this project, the blood bank is the organization that will gain the
most benefits from. This is because of the risen of the public awareness on the blood donation
events by advertising the blood donation events at 24 hours a day and 7 days a week basis.
Moreover, the system also provides convenient way for the public to make online reservation on
their desired session.
 The Blood Center administrator will be able to manage and coordinate the blood supply among
the blood banks of the hospitals and medical center more efficiently as they can view the records
of blood stocks in all participating hospitals.
 Besides, the blood bank the staff can manage the blood and donor records more efficiently with
better security and added automation function in alerting the administrator when the blood
quantity is below par level. In addition, the administrator can also trace the person responsible in
case of human error such as fault blood transfusion and blood screening result. The staff can also
manage the system user more efficiently.
 The blood bank medical lab technicians also gain the advantage of having an automation system
in assisting his/her works. This is because works can be done in more systematic and organized
way when managing the blood stock in blood banks.
 This system also creates a convenient and paperless environment for the doctors and nurses in
managing and processing the incoming donors and the blood stocks as the donors' records have
been centralized. The registration time for old donor is shorten as the records are retrievable from
the system.

Jimma University Department of Computer Science Page 6

 1.8 Time scheduling
In order to accomplish time effective and efficiently, we used the Gant charts to schedule times
in all phases of project we do. Its major phases are listed below.
Nov 25, '12 Dec 2, '12 Dec 9, '12 Dec 16, '12 Dec 23, '12 Dec 3
ID Task Name F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M
1 1. Introduction
2 1.1 Background
3 1.2 Statement of problem
4 1.3 Objective
5 1.4 Methodology
6 1.5 Scope and limitation
7
8 2. Analysis
9 2.1 Existing System
10 2.2 New system
11 2.2.1 Non functional requirements
12 2.2.2 Functional requirements
13 2.2.3 Use case diagram
14 2.2.4 Use case documentation
15 2.2.5 Activity diagram
16 2.2.6 Class diagram
17 2.2.7 user interface prototyping
18
19 3 Design
20 3.1 Purpose and goal
21 3.2 Proposed software architecture
22 3.2.1 Subsystems decomposition
23 3.2.2 Component diagram
24 3.2.3 Deployment diagram
25 3.2.4 ER Diagram
26 3.2.5 Persistence modeling for OODB
27 3.2.6 Access control and security

Figure 1.1 time scheduling

Jimma University Department of Computer Science Page 7

CHAPTER TWO

ANALYSIS

2.1 Existing System

Existing System Description

 The company use human power for awareness creation by organizing clubs.
 Because of the lack of budget company does not using any advertisements.
 They decide when and where the reservation for blood donation can be hold.
 They are using manual system.

Business Rules
1. Age of the Donor must between 18 to 60 to donate the blood.
2. Weight of the Donor must greater than 45 kg.
3. For weight 45kg to 50kg, 350ml amount of blood is received
4. For weight greater than 50 kg, 450ml amount of blood is received.
5. If Weight is greater than 50kg, but length is not appropriate 350ml amount of blood is
received.
6. If you have desire to "give back" to the community in every 3 Months.
7. No donation if the Donor have any disease and not in proper health condition.
8. First In First Out(FIFO) rule
9. If the donor who donates the blood wants the blood before 3 months, he can get the blood
free from the blood bank.
10. The blood in the blood stock is expired after 35 days.

2.2 New System

2.2.1 Non-functional Requirements and Constraints

Jimma University Department of Computer Science Page 8

The system must be developed to suit the particular needs of a user-friendly environment.
This means that the system must accommodate a clearly understandable user interface as
well as clear online help documentation at any stage of the user interaction with the system.
A fast response time in obtaining and providing information to the system may also prove to be a
significant advantage. In addition to these requirements, the system should also embrace the
following requirements:-
Security: Each user is required to log in. The system should log staff that has been assigned user
names and passwords. The system should be designed to make it impossible for anybody to
logon without a valid username and password. Data encryption should be employed to keep the
user login name and password secret.
Reliability: The system would be used by about 4 staff worker at the JU hospital blood bank.
The System should have little or no downtime and be able to handle multiple concurrent users.
Ease of Use: The general and administrative views should be easy to use and intuitive.
Online help and documentation should be provided.

2.2.2 Functional Requirements

In our project we aim at developing a system which should improve on the current
one with a lot of functionalities and therefore the Major target or goal here is to:
 To develop a blood donor database that can support -; Donor DB, Donation DB, Transfusion
DB and etc.
 To develop a client interface that allows privileged users to carry out tasks such as registering
or modifying their data in the database;
 To develop a searching functionality in order to allow normal and privileged users to search
the details of a given donor, blood group, and if necessary a type of disease common which
causes one to need the donated blood.
 To fully integrate the Web-based management information system to the Web and hence
allow access from any Internet networked terminal and Web browser.
 To develop a facility that can export details entered via the web front end to endnote as well
as import and confidential detail from the Endnote Database.

Jimma University Department of Computer Science Page 9

 To develop functionality that produces summary information of required data to enhance
decision making.
 To embed high security features in the Web DBMS to provide privacy, integrity;
 And finally the system should be flexible enough to store data for several years and also be
able provide sufficient User and Administration Guides.

2.2.3 Use case diagram

Jimma University Department of Computer Science Page 10

 Figure 2.1 use case diagram

Jimma University Department of Computer Science Page 11

 2.2.4 Use case Description
Use case documentation for create user account

Use case name Account Management

Actor Admin
Description This activity is performed when the administrator want to create a new user.
Basic course of action Actor action System response

1: System administrator initiate to login 2: System displays login page.

3:System administrator enter username 4: System checks the validity and then
and password authentication and authorization of
6: System administrator select create user username and password.
account page. Or delete account 5: System displays admin page
If create account 7: System display create account page.
8:System administrator enter user 9:System creates user account
information

Alternative course of Step 4: If the username and password is not validated and verified, system displays
action error message and go to step2
Step8: if the user information is not validated and verified ,system display error
message and go to step8

Jimma University Department of Computer Science Page 12

 Use case description for Registration

Use case name: Registration

Participatory actor: Donar,Admin ,Blood Seeker
Entry condition: for registration to get access from the blood bank
Event flow:: 1. Click on the Registration
2. Select from Donor Registration and Recipient Registration
3. the system display “registration form”
4. Enter Donor information or recipient information
5. Select submit, the system check if the value you enter is correct
or not from the database if correct the system display
“Successfully registered” if not the system display “re enter
blank space”.
6. System generates UserID.
7. You have to Print UserID.
Exit condition: Logout.

Use case description for Blood Bank Information Details

Use case name: Blood Bank Details

Jimma University Department of Computer Science Page 13

 Participatory actor: Admin
Entry condition: To Edit Blood Bank Details information
Event flow:: 1. Enter username and password
2. Click login,
3. the system check if the value is valid or not from the database
4. If valid the system display “Blood Bank Details menu” if not
the system display “re enter user name or password”.
5. Add new Information for Awareness
6. Upload
7. Advertize
8. Publicize blood donation event
Exit condition: Logout:

Use case name: Blood Bank Details

Participatory actor: Donor
Entry condition: To View Blood Bank Details information
Event flow:: 1. Enter username and password
2. Click login,
3. the system check if the value is valid or not from the database
4. If valid the system display “Blood Bank Details menu” if not
the system display “re enter user name or password”.
5. View any information

Use case description for Stock Management Details

Jimma University Department of Computer Science Page 14

 Use case name: Stock Management Details
Participatory actor: Admin
Entry condition: Initiate the Details of the Blood Stock
Event flow:: 1. Initiate Stock Management Details
2. Enter username and password
3. Click on Login()
4. If “not valid”
5. Display “Re enter again”
6. If “Valid”
7. Display Details of the Blood Stock
8. Check Expired Blood and Amount of Blood
9. If There if there is Expired Blood and
Less Amount of Blood per level
10. Generate Alert Signal
11. Remove Expired Blood
Exit condition: Logout.

Use case description for Blood Collection

Use case name: Blood Collection

Jimma University Department of Computer Science Page 15

 Participatory actor: Worker
Entry condition: To Collect The Blood
Event flow:: 1. Click on Blood Collection
2. Login
3. Check The Authentication
4. If Valid
5. The system Display “Blood Collection Menu”
6. Select and Fill The Differed Category forms
7. If Rejected “Donation is Failed”
8. If accepted
9. Donate the Blood
10. Send the Result to the Stock management
11. Save

Exit condition: Logout.

Use case description for Screening

Use case name: Screening

Participatory actor: Worker

Jimma University Department of Computer Science Page 16

 Precondition Take sample test
Entry condition: For Testing person’s blood in order to identify those with particular
characteristics
Event flow:: 1. Enter user name and password
2. Check authentication
3. If “not valid”
4. Display “Re enter again”
5. If “Valid”
6. Search()
7. If Result is Donor
1 Display “Blood Donor Enrollment Form”
2 Fill the form
3 Blood Collection Form
8 If Result is Blood Seeker
1 Display “Blood Seeker Form”
2 Fill the form
3 Distribution Room

Use case description for Blood Donation

Use case name: Blood Donation

Participatory actor: Donor

Jimma University Department of Computer Science Page 17

 Entry condition: Reservation of registered Donor to donate blood voluntarily
Event flow:: 1. Click on Blood Donation
2. Enter Full name and UserID
3. If not Valid “Re enter again your UserID or Name”
4. If “Valid”
5. Display Appointment Form
6. Fill appointment Form
7. Submit
8. If you haven’t User ID
9. Click On Registration
10. Fill Registration Form
11. Get UserID
12. Go to Blood Donation
Exit condition: Back

Use case description for Refer Friend

Use case name: Refer Friend

Jimma University Department of Computer Science Page 18

 Participatory actor: Donor
Entry condition: Advertizing your Friends for Donation
Event flow:: 1. Click on Refer Friend
2. System Displays Refer Friend Form
3. Fill The Refer Friend Form
4. If “Valid”
5. Display the Acknowledgement
6. If not Valid
7. Re Enter Again
8. Submit

Exit condition: Back

Use case description for Approve

Use case name: Approve

Participatory actor: Admin

Jimma University Department of Computer Science Page 19

 Entry condition: For Approving those who donate the blood and Disapprove those who
fail their appointment by their session date.
Event flow:: 1. Initiate the Approve
2. Enter Username and password
3. Login()
4. Check validity
5. If Not valid “Re Enter Again”
6. If Valid
7. Check message from workers ”Donate /Fail to Donate”
8. If Valid message “Approve”
9. If Not Valid message” Disapprove”

Exit condition: Back

Use case description for Distribution

Use case name: Distribution

Participatory actor: Admin
Precondition Blood Seeker must exist
Entry condition: For Blood distribution

Jimma University Department of Computer Science Page 20

 Event flow:: 1. Enter user name and password
2. Check authentication
3. If “not valid”
4. Display “Re enter again”
5. If “Valid”
6. Search() from Stock that fit with the blood Seeker
7. If exist
8. Distribute

2.2.5 Sequence diagram

A sequence diagram is a kind of interaction diagram that shows how processes operate with one another
and in what order. It depicts the objects and classes involved in the scenario and the sequence of
messages exchanged between the objects needed to carry out the functionality of the scenario.

Jimma University Department of Computer Science Page 21

 Figure 2.2 Sequence diagram for Create Account

Jimma University Department of Computer Science Page 22

 Figure 2.3 Sequence diagram for Registration

Jimma University Department of Computer Science Page 23

Figure 2.4 Sequence diagram for for Blood Bank Information Details

Jimma University Department of Computer Science Page 24

Figure 2.5 Sequence diagram for Stock Management Details

Jimma University Department of Computer Science Page 25

Figure 2.6 Sequence diagram for Blood Collection

Jimma University Department of Computer Science Page 26

Figure 2.7 Sequence diagram for Blood Donation

Jimma University Department of Computer Science Page 27

Figure 2.8 Sequence diagram for Screening

Jimma University Department of Computer Science Page 28

 Figure 2.9 Sequence diagram for Refer Friend

Jimma University Department of Computer Science Page 29

Figure 2.10 Sequence diagram for Approve

Jimma University Department of Computer Science Page 30

Figure 2.11 Sequence diagram for Distribution

Jimma University Department of Computer Science Page 31

2.2.6 State chart diagram
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 2.12 State chart diagram for Login

Jimma University Department of Computer Science Page 32

Figure 2.13 State chart diagram for Registration

Jimma University Department of Computer Science Page 33

Figure 2.14 State chart diagrams for Blood Bank Information Details

Jimma University Department of Computer Science Page 34

Figure 2.15 State Chart diagram for Stock Management store

Jimma University Department of Computer Science Page 35

Figure 2.16 State Chart diagram for Screening

Jimma University Department of Computer Science Page 36

Figure 2.17 State chart Diagram for Blood Collection

Jimma University Department of Computer Science Page 37

Figure 2.18 State chart diagram for Blood Donation

Jimma University Department of Computer Science Page 38

Figure 2.19 State chart Diagram for Refer Friend

Jimma University Department of Computer Science Page 39

Figure 2.20 State Chart Diagram for Approvance

Jimma University Department of Computer Science Page 40

2.2.7 Activity diagram
The following figure depicts the high level activity diagram of the system. The figure depicts the
high level interaction of the actors with the system that specifies the work flow the system.

Figure 2.21 Activity Diagram for Login

Jimma University Department of Computer Science Page 41

Figure 2.22 Activity Diagram for Registration

Jimma University Department of Computer Science Page 42

Figure 2.23 Activity Diagram for Blood Bank Information Details

Jimma University Department of Computer Science Page 43

Figure 2.24 Activity Diagram for Stock management

Jimma University Department of Computer Science Page 44

Figure 2.25 Activity Diagram for Blood Collection

Jimma University Department of Computer Science Page 45

Figure 2.26 Activity Diagram for Blood Donation

Jimma University Department of Computer Science Page 46

Figure 2.27 Activity Diagram for Refer Friend

Jimma University Department of Computer Science Page 47

Figure 2.28 State Chart diagram for Distribution

Jimma University Department of Computer Science Page 48

2.2.8 Class Responsibility and Collaboration for New System
Class responsibility and collaboration is a model that helps to show the collaboration or
interaction between classes and responsibility of each class in the system.

Jimma University Department of Computer Science Page 49

Jimma University Department of Computer Science Page 50
2.2.9 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. The class diagram with its corresponding objects will be present
in the following section.

Jimma University Department of Computer Science Page 51

Figure 2.29 Class diagram

Jimma University Department of Computer Science Page 52

 2.2.10 Identifying change cases
The change happens in any systems. Any successful software needs to change and allows over its
life cycle. That is changes are motivated by new and/or modified requirements. The change case
as follows: User interface work on browser that support html codes and jsp code; The systems will
work sun Solaris server; The system will be written by .jsp and java language. The systems will
use data contained existing oracle data base.

2.2.11 User interface prototyping

Is an iterative analysis technique in which users are actively involved in the mocking-up of the UI
for a system. UI prototypes used as an analysis artifact that enables you to explore the problem
space with your stakeholders.

Jimma University Department of Computer Science Page 53

Figure 2.30 Home page User interface

Jimma University Department of Computer Science Page 54

Figure 2.31 Donor Registration Form User interface

Jimma University Department of Computer Science Page 55

 CHAPTER 3

SYSTEM DESIGN

3.1 Introduction

Design is process of describing, organizing, and structuring system components at architectural

design level and detailed design level. Design converts functional models from analysis into
models that represent the solution. This project is designed in a manner that solves the problems
of the organization by minimizing the work load of the existing system and employee. It
provides more efficient, reliable and time saving system.

3.2 Design Goals

The design part is very important so as to make the implementation very easy. The different
types of the system modeling techniques that are used for the implementation of the system such
as deployment and component modeling are show in detail. Not only the system modeling
techniques but also some system design techniques such as system decomposition design are
cover in detail in this phase. The non-functional requirement is the description of the feature
characters and attributes of the system. Some of the design goals are:-
 Performance (Response time)
In terms of performance, the existing/manual system is not as satisfactory because it is slow/time
consuming, energy consuming and does not support online information system about the
awareness of blood donation, when to donate and how to donate. For this they use human power
and some group, this take more time.
 Security- The system should be secured that unauthorized user can not access the data that does
not concern with them.
 Reliability- The reliability of the proposed system will be better due to proper storage of
information when users access the application.
 Fault Tolerance-The system should be able to give response (error message) when the user enter
incorrect input. This recommends the user to enter correct input.

Jimma University Department of Computer Science Page 56

 Throughput:-Since OBDRMS has both desktop application and web application it is able to
perform many tasks in fixed period of time. Different service center do different tasks in their
working time without worrying the other service center are using the same system.
 User friendly Interface: Users can easily input and retrieve their profile and history.
This means that the system must accommodate a clearly understandable user interface.
 Backup and Recovery We have used backup mechanisms such as removable flash disks, CDs
and hard disks. Because the data might lose due to computer viruses or power fluctuation
 Availability: shared resources that cooperate to guarantee essential services. The system must
high availability.
 No Redundancy: In the proposed system can be avoided reputation of data anywhere in the
database.
 Dependability: The Company needs the system to be highly dependable as it is expected to be
used by non-IT professions. The system should be robust and fault tolerant. Furthermore as the
system is handling sensitive data of the blood bank, high emphasis should be given with regards
to security, as there are subsystems to be accessed through web.
3.3 Proposed software architecture
Software architecture is structured into three layers by dotted lines. Each layer is an abstraction
of functionality. The layer on the bottom offers data management functionality to the services
layer. And the services layer offers functionality to several clients on the Internet. Each layer is
build onto the functionality of the next layer down the stack.

Jimma University Department of Computer Science Page 57

 Figure 3.1 software architecture
3.3.1 Subsystem decomposition

Subsystem decompositions will help reduce the complexity of the system. The subsystems can be
considered as packages holding related classes/objects. These subsystems are further
decomposed into other subsystems. The major subsystems identified are “Registration”, “Login”,
“Screening”, “Donate Blood”, “Blood Distribution”, “Blood Collection” “Refer Friend” and
“Report” subsystems. Users are classified in to roles. The “Login” subsystem authenticates a
user to grant access based on the role of the user.

Jimma University Department of Computer Science Page 58

Jimma University Department of Computer Science Page 59
Figure 3.2 Subsystem decomposition

Jimma University Department of Computer Science Page 60

 3.3 Component diagram

A component diagram depicts how components are wired together to form larger components and o

They are used to illustrate the structure of arbitrarily complex systems.

Figure 3.3 Component diagram

Jimma University Department of Computer Science Page 61

 3.4 Deployment diagram
Deployment diagram depicts a static view of the run-time configuration of processing
nodes and the components that run on those nodes. In other words, deployment diagrams
show the hardware for your system, the software that is installed on that hardware, and
the middleware used to connect the disparate machines to one another. You want to
create a deployment diagram for applications that are deployed to several machines.

Figure 3.4 Deployment diagram

3.5 Persistence Modeling for object oriented database

Persistence modeling is used to communicate the design of the database, usually the data base to
both the users and the developers. It is also used to describe the persistence data aspect of the
system. The following diagram indicates the persistence diagram of the system.

Jimma University Department of Computer Science Page 62

Jimma University Department of Computer Science Page 63
 Figure 3.5 persistence modeling

Jimma University Department of Computer Science Page 64

3.7 Access Control and Security
Access control and security describes the user model of the system in terms of access
matrix. The system is provided for free access for any interested Donor. Accordingly to the
following access control list is given for the system

Registration Refer Friend Screening, Distribution Sock management

Collection
Actor
Donor Register Online Advertize by sending
for giving blood Message to friends

Admin Memorize by sending Control Distribution Manage the Stock

Message to registered of Blood
Donor for appointment

Worker Screen the blood Distribute blood as

register values and ordered by Admin
if valid value
collect the blood

Blood Register online Advertize by sending

Seeker for receive blood Message to friends

Reference
1. Frederick P. Brooks, Jr. - The Mythical Man-Month Essays on Software Engineering,
Anniversary Edition
2. James Rumbaugh, Ivar Jacobson, Grady Booch – The Unified Modeling Language
Reference Manual Second Edition.
3. http://www.bharatbloodbank.com/

Jimma University Department of Computer Science Page 65

Jimma University Department of Computer Science Page 66