UIU Blood Bank
DONATE BLOOD & SAVE ANOTHER LIVE.

Presenters’
Md. Shajahan 011 121 088
G.M. Muktadir 011 121 054
Manik Deb Nath 011 122 012
Shahriar Ibrahim 011 121 008
Tauhidul Khandaker 011 111 010
Ove Pramanik 011 121 055

Repertory
 Preface
 Labyrinth Statement
 Feature List
 Objective
 Diagrams (and Details in Need)
 SWOT Analysis
 Sequence diagram
 Class diagram
 State diagram
 Grantt Chart
 Proposed Budget
 Final View of Project

Preface
 UIU Blood Bank is specially meant for hospital who
need blood for their patient or for other blood bank who
collect blood to be given for different hospital. Here we
maintain the information about the donor. Our System
encourages the blood communication between the donor
to donate and doctor to find and provide as recipients
need.

Labyrinth Statement
 Scarcity of rare blood group.
 Unavailability of blood during emergency.
 Less awareness among people about blood donation and
blood transfusion.
 Deaths due to lack of blood during operations.
 Not enough supply of Bloods for Thalassemia patients.

Feature List (Intro)
 To made the feature list of our site we surveyed
the following renowned sites.
1. quantummethod.org.bd
2. blooddonorsbd.com
3. ifrc.org
4. sandhani.org
5. orcabloodforlife.org

Feature List
Frontend 1 2 3 4 5 Proposed System
Home      
Donor Reg./ Login      
Social Campaign      
Online Blood
Transfer Froom
Bank To Bank
     
Search Donor By
Blood Group
     
Blood Bank Reg.
And Request
     
Social Network      

Feature List
Frontend 1 2 3 4 5 Proposed System
SMS Gateway/
Email
     
FAQ, Downloads,
User Guide
     
Photo Gallery      
Event, Seminar
And Q & A      
Refer Your Friends      
Admin Area      
Donor Area      

Feature List
Frontend 1 2 3 4 5 Proposed System
Online Blood
Management
     
Module & Plug In
Customization
     
Donor/ User
Management
     
Email Notifier      
Latest News      
Database Results      
Detailed Blood
Banks Report
     

Objective of UIU Blood Bank
 Promote and support national activities to celebrate and promote voluntary
non-remunerated blood donation by:
 Encouraging existing low-risk voluntary donors to give
blood regularly
 Encouraging new people to donate their blood on a
voluntary unpaid basis
 Build wider public awareness of the need for regular blood donation
throughout the year in order to maintain an adequate supply of blood for all
patients requiring transfusion.

Context Diagram

Use Case Diagram

Description form of Use Case
(Scenario 1 of 4)
Use Case : Login
Primary Actor : User
Stakeholders and Interests
User: Want to enter the system.
Admin : Permit the request.
Preconditions : Must be registered and valid user.
Main Success Scenario: Extensions( or Alternative Flows)
1. Click the login page.
2. Enter the name and pin.
3. Click the login button.
4. Successfully enter.
*a. Site hacked
1. Close the site , try again.
2a. Not match
2. Go to the Reg. page and register.
4a. Invalid username and password
1. Forget password & Recover.
2. Report to admin.

Description form of Use Case
(Scenario 2 of 4)
Use Case : Registration
Primary Actor: User
Stakeholders and Interests
User: Want to register
Admin : Permit the request and feedback the user .
Preconditions : Must be registered and submit the real data.
Postconditions: Registration is saved and update the database.
Main Success Scenario Extensions( or Alternative Flows)
1. Click the Registration page.
2. Enter the name, address, contact
number .
3. Click the submit button.
4. Successfully registered.
*a. Site hacked
1. Close the site , try again.
2a. Empty any input field
1. Fill up the input box .
4a. Not registered
1. Try again.

Description form of Use Case
(Scenario 3 of 4)
Use Case: Search
Primary Actor : Seeker
Stakeholders and Interests
Seeker: Want to search the blood
Admin : Permit the action and feedback to the Seeker
Preconditions: Seeker is identified and authenticated.
Main Success Scenario Extensions( or Alternative Flows)
1. Valid Seeker browse the search
system.
2. Response to the Seeker.
*a. System hacked
1. Close the system and try later.
2a. No response
1. Search again.
2. Report.

Description form of Use Case
(Scenario 4 of 4)
Use Case: Collect Blood
Primary Actor : Seeker
Stakeholders and Interests
Seeker: Want blood and collect the blood
Admin: Permit the request and send a confirmation message
Preconditions: Seeker is identified and authenticated.
Post conditions: Transaction is saved and update the database.
Main Success Scenario: Extensions( or Alternative Flows)
1. Valid Seeker click the page .
2. Search blood .
3. Apply to collect the blood .
4. Get a confirmation message into the
Admin.
*a. System hacked or crashed
1. Try again.
2a. Not success
1. Search again .
2. Report the Admin.
4a. No confirmation
1. Report to admin about problem.

Data Flow Diagram

Activity Diagram

SWOT Analysis
Strengths Weakness
1. Five hundred members are
interested from social club.
2. User friendly.
3. Management.
4. Social service.
1. This system is built only for UIU
students.
2. This site builds base on English
tradition.
Opportunity Threats
1. Online service system.
2. Increasing demand for service.
3. Quick response.
4. No blood bank in UIU.
1. Request will through by email.
2. Many students are not interested
to give blood.
3. Not business purpose.

Sequence Diagram
 A Sequence diagram is an interaction diagram that shows how processes
operate with one another and what is their order. It is a construct of a
Message Sequence Chart.
 A sequence diagram shows object interactions arranged in time sequence.
It portrait 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.
 Sequence diagrams are typically associated with use case realizations in
the Logical View of the system under development.
 Sequence diagrams are sometimes called event diagrams or event
scenarios.

Symbol Table

Rules for Sequence Diagram
 A lifeline can represent an object or its class. Thus, you can use a lifeline to
model both class and object behaviour. Usually, however, a lifeline represents
all the objects of a certain class.
 An object's class can be unspecified. Normally you create a sequence
diagram with objects first, and specify their classes later.
 The objects can be unnamed, but you should name them if you want to
discriminate different objects of the same class.
 Several lifelines in the same diagram can represent different objects of the
same class; but, as stated previously, the objects should be named that so you
can discriminate between the two objects.
 A lifeline that represents a class can exist in parallel with lifelines that
represent objects of that class. The object name of the lifeline that represents
the class can be set to the name of the class.

Sequence Diagram
Diagram: Sequence diagram as our blood donation working module.

Class Diagram
This section describes style guidelines that are relevant to
various types of class diagrams.
 Show visibility only on design models
 Assess responsibilities on domain class diagrams
 Highlight language-dependent visibility with property strings
 Highlight types only on design models
 Highlight types on analysis models only when the type is an
actual requirement

Diagram: Class diagram as our blood donation working module.
Class Diagram

State Diagram
A state diagram is a type of diagram used in computer science and related fields to describe
the behaviour of systems. State diagrams require that the system described is composed of a finite
number of states; sometimes, this is indeed the case, while at other times this is a reasonable
abstraction. Many forms of state diagrams exist, which differ slightly and have different semantics.
 Initial State:
Definition: An initial state is used to identify the first transition to be taken within a model. The
destination of the first transition is thus the first state to be entered within the model (i.e. the default
state).
 Representation:
An initial state is represented by a solid circular shaped node that is (by default) black in color.
i.e.
 Creation:
The initial state is created automatically when the model is first created.

State Diagram
This section describes style guidelines that are relevant to
various types of class diagrams.
 Show visibility only on design models
 Assess responsibilities on domain class diagrams
 Highlight language-dependent visibility with property strings
 Highlight types only on design models
 Highlight types on analysis models only when the type is an
actual requirement

Symbol table

Diagram: State diagram as our blood donation working module.

Phase Diagram (Phase 1.1)
 For better understanding we divided These Diagrams into 4
(Four) phases.

Phase Diagram (Phase 1.2)

Phase Diagram (Phase 2.1)

Phase Diagram (Phase 2.2)

Phase Diagram (Phase 3)

Phase Diagram (Phase 4)

Deployment Diagram

Grantt Chart (Part 1)
Tasks Description Prerequisite Required Days
A Phase Study - 5
B Problem Analysis A 4
C Feature List A 2
D Design B, C 4
E Coding D 3
F Implementation D, E 3
G Documentation F 4
H Presentation G 1

Grantt Chart (Part 2)

Pert Chart

Proposed Budget
Sector Type Quantity Price/ Unit Total Cost
(Tk)
Hardware Laptop 2 40,000 80,000
Donor Collection Boot camp 1 100(10) 10,00(Apprx.)
Domain Reg. uiubloodbank.com 1 5000 5,000
Web Hosting Unlimited 1 24,999/year 24,999
Testing Server Server 1 20000 20,000
Software Tools Oracle, PHP,XAMP,
Netbeans IDE
- 50000 50,000
Total 1,89,999