This document outlines a database project for a blood bank management system. It includes sections on the project proposal, requirements, scope, architecture, data flow diagram, use case diagram, system sequence diagram, class diagram, entity relationship diagram, hardware and software specifications, tools and technologies used, screenshots of tables with sample data, and examples of select, update, delete and insert queries. The overall goal is to develop software to manage the daily operations of a blood bank such as registering donors, collecting and distributing blood, and generating various reports.

1. 1
Department of Computer Science &
Information Technology
University of Sargodha
DATABASE PROJECT : BLOOD BANK
GROUP MEM TEACHER
AMAR SAJID RABIA MURTAZAA
ABDUL BASIT BSIT-4TH
-C
ADIL ASHRAF
Faculty of Computing & Information Technology
University of Sargodha
Session 2017-21

2. 2
TABLE OF CONTENTS
NAME PAGE
Project Proposal.......................................................................................................2
1.1 Introduction........................................................................................................3
1.2. Project Overview statement:............................................................................3
Project Title: BLOOD BANK...............................................................................3
Project Goal:...........................................................................................................3
Objectives:..............................................................................................................3
1.3. Product Scope:...................................................................................................4
1.4. Requirement:.....................................................................................................4
1.5. Exclusion:...........................................................................................................5
1.6. Application Architecture: ................................................................................5
1.7. data flow diagram:............................................................................................5
1.8. use case diagram: ..............................................................................................6
1.9. SSD (system sequence diagram):.....................................................................7
1.10. class Diagram: .................................................................................................7
1.11. ERD:.................................................................................................................7
1.12.Hardware and software specification: ...........................................................8
1.13. Tools and technologies used with reasoning: ...............................................8
1.14. Screenshots of my project…………………………………………………………………..
1.15. Five quires………………………………………………………………………………….

3. 3
Project Proposal
1.1 Introduction
 The project blood bank management system is known to be a pilot project that is
designed for the blood bank to gather blood from various sources and distribute it to the
needy people who have high requirements for it.
 The software is designed to handle the daily transactions of the blood bank and search the
details when required.
 It also helps to register the details of donors, blood collection details as well as blood
issued reports.
 The software application is designed in such a manner that it can suit the needs of all the
blood bank requirements in the course of future
1.2. Project Overview statement:
Project Title: BLOOD BANK
Project Members:
Name Registration # Email Address Signature
Amar sajid BSIT-F17-58 Amarsajid999@gmail.com
Abdul basit BSIT-F17-47 Freeky66197ee@gmail.com
Adil Ashraf BSIT-F17- Adil18178@gmail.com
Project Goal:
 The main aim of this project is to develop a software which is used for maintain whole
information about campus.
 In this project mainly 3 modules are there.
 Admin ,Donors ,Acceptors
Objectives:
Sr.# Objectives
1 The specification builds on the experience of users of IT technology in blood
transfusion that is currently available and informs both Connecting for
Health (CFH) and commercial companies producing both hardware and
software.
2 Routine blood transfusion.
3 Emergency issue of blood
4 Management of returned and unused blood units
5 The main objective of this specification is to support the automated tracking of
blood
6 To help anyone, in case of any requirement for blood.
7 Blood safety

4. 4
1.3. Product Scope:
 The software is designed to handle the daily transactions of the blood bank and search the
details when required.
 It also helps to register the details of donors, blood collection details as well as blood
issued reports.
 The software application is designed in such a manner that it can suit the needs of all the
blood bank requirements in the course of future.
 Routine blood transfusion;
 Emergency issue of blood;
 Management of returned and unused blood units.
1.4. Requirements
Requirement
Name
Requirement Description
Registration of
Donor
Requires an interface for the registration the details of the donor
Donor Details Attributes - Donor ID, Name, Age, Address, Contact, Email, Blood
Group, Gender, Date
Health
Information
Attributes- Body Weight, Pulse Rate, Haemoglobin, Weight of Bag,
Blood Pressure, Temperature
Donation
Details
Attributes - Blood Group, Number of Bags, Donation Date
Blood Bank Requires an interface to display the details of the blood bank. Attributes
–Name, Address, Contacts, Hospitals Linked
MDI Form Requires an interface to build an MDI form. Requires the following
menus:Employee(Update-Details,Change-Password),
Transactions(Display various transactions), Reports(Display donor and
test related reports), Help(Contact and Information), Exit(Terminate the
project), Sign Out(User Log Out
Login Requires 2 Interfaces for login, Change of Password and Password
Recovery. Attributes –Email, Password, New Password, Recovery
Question, Recovery Answer
Report Requires interfaces for displaying various reports. Attroibutes- Date
Daily
Remittance
Requires an interface to update the various details of the transaction.
Attributes –Transaction No., Donor, Date, Stock, Amount, Hospital
Details(Name, Contact, Address)
Employee Requires an interface for updating or adding the details of the blood bank
employee. ID, Name, Address, Email, DOB, Blood Group, Qualification
Skills, Gender, Contact
Crystal Form Requires an interface that consists af a form displaying all the details
which are auto generated as per the requirement.
8 Reliable , secure

5. 5
1.5. Exclusion:
Due to lake of time, we do not complete the whole blood bank.
1.6. Application Architecture:
This application is a 3-tier application.
1.7. Data flow diagram:
A data-flow diagram is a way of representing a flow of a data of a process or a system. The DFD
also provides information about the outputs and inputs of each entity and the process itself. A
data-flow diagram has no control flow, there are no decision rules and no loops.

6. 6
1.8. use case diagram:
A use case diagram is a graphic depiction of the interactions among the elements of a
system. A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements.

7. 7
1.9. SSD (system sequence diagram):
1.10. Class Diagram:

8. 8
1.11.ER DIAGRAM OF BLOOD BANK
1.12.Hardware and software specification:
Software requirements:
Windows
SQL
HTML&CSS
Hardware requirement:
RAM 1GB or above MB
20GB or above Hard disk
1.13. Tools and technologies used with reasoning:
HTML & CSS

9. 9
The Screenshots of our Project
1. The SQL coding of our project.
2. Structure of our project.

10. 10
3. Data inserting in tables which is “Blood” .
Code
Structure

11. 11
4. Data insert in table which is”Blood Inventory”.
Code
Structure

12. 12
5. Data insert in table which is “Donors”.
Code
Structure

13. 13
6. Data insert in table which is”Hospital”.
Code
Structure

14. 14
7. Data insert in table that is “Inventory management”.
Code
Structure

15. 15
8. Data insert in table which is “receptionist”.
Code
Structure

16. 16
Five Queries
There are five queries that is most important for project.
 Select
 Select*
 Insert
 Update
 Delete
1. Select
Result

17. 17
2. Select*
Result

18. 18
3. Update
Result

19. 19
4. Delete
5. Insert
We already use in data inserting in tables.