BLOOD DONATION SYSTEM by

Using PHP
By

Haider Ali 2017-GCUF-058167

Talha Bin Saleem 2017-GCUF-058188
Humza Hussain 2017-GCUF-058170

BACHELOR OF SCIENCE IN
COMPUTER SCIENCE

DEPARTMENT OF COMPUTER
SCIENCE
Government College University Faisalabad
(2017-2021)
Revision History

Name Date Reason for changes Version

Coordinator 08-03-2021 Grammar, Sentences and I

font style mistakes were
corrected by the sir. Also,
help us in developing
WBS.

HOD 12-03-2021 Documentation styles and II

some major model
changings were
suggested by the sir.

Final Submission for 14-03-2021 III

Defense
Contents
1. Introduction....................................................................................................................4
1.1. General Information............................................................................................................4
Name to the project as well as pertinent information about the personal involved.....................4
1.2. Purpose...............................................................................................................................4
1.3. Document Conventions.......................................................................................................5
1.4. Project Objective.................................................................................................................6
1.5. Intended Audience and Reading Suggestions......................................................................6
1.6. Project Scope......................................................................................................................7
2. Overall Description........................................................................................................7
2.1. Product Perspective.............................................................................................................7
2.2. Product Features:.................................................................................................................7
2.3. User Classes and Characteristics:........................................................................................8
2.4. Operating Environment:......................................................................................................9
2.5. Design and Implementation Constraints:.............................................................................9
2.6. User Documentation:..........................................................................................................9
2.7. Assumptions and Dependencies:.........................................................................................9
3. System Features...........................................................................................................10
3.1 System Feature 1:...............................................................................................................10
3.2 Description and Priority:....................................................................................................10
3.3. Stimulus/Response Sequences:.........................................................................................10
3.4 Functional Requirements....................................................................................................10
3.5. System Feature 2 (and so on)............................................................................................10
4. External Interface Requirements...............................................................................10
4.1. User Interfaces:.................................................................................................................10
4.2. Hardware Interfaces:.........................................................................................................10
4.3. Software Interfaces:..........................................................................................................11
4.4. Communications Interfaces...............................................................................................11
5. Other Nonfunctional Requirements...........................................................................11
5.1. Performance Requirements:..............................................................................................11
5.2. Security Requirements:...................................................................................................11
5.3. Software Quality Attributes.............................................................................................11
6. WBS Project Management.........................................................................................12
7. Tools & Technologies...................................................................................................12
7.1. Programming Languages...................................................................................................12
7.2. Databases/Data storages....................................................................................................12
7.3. Operating System..............................................................................................................12
Appendix A: Glossary......................................................................................................13
Appendix B: Analysis Models.........................................................................................14
Appendix C: Check List..................................................................................................18
(For office use only).......................................................................................................19
Government College University Faisalabad

1. Introduction
Blood is a first and foremost component among the most critical necessities.
Healthy range of blood in human body plays an essential role in saving countless life
in both regular and emergency conditions. Every second there is a requirement for
blood. Patients’ life is saved by the voluntary act of blood donors. Our main focus will
be on designing an efficient and reliable which controls the information of blood
donors.

1.1. General Information

Name to the project as well as pertinent information about the personal involved.

Project Name: Starting Date:

BLOOD DONATION 14/03/2021
SYSTEM by Using PHP
Controlling Agency: Final Date:
Times Institute Multan 12/07/2021
Prepared By: Authorized By:
Haider Ali Dr. Farkhand Shakeel Mehmood
Talha Bin Saleem
Humza Hussain

1.2. Purpose
The purpose is to meet the challenging requirement of modern-day blood to
efficiently collect blood during emergency.

1.3. Document Conventions

This document is formed using IEEE template for System Requirement
Specification (SRS) documents.

Bold/Spacing Font Font Size

Page 4
Government College University Faisalabad

Items

Paper size Portrait Times New Roman A4

Title Bold Times New Roman 22
Main Heading Bold Times New Roman 18
Heading Bold Times New Roman 16
Sub Heading Bold Times New Roman 14
Sub Heading Bold Times New Roman 12
Paragraph line spacing 1.5 line Spacing and
Times New Roman 12
Paragraph writing one Tab
The rest of the document is
Justify Times New Roman 12
written.
Right bottom of the
Paging Times New Roman 12
page
Fig caption Under the fig Times New Roman 12
Table caption Over the table Times New Roman 12
APA (American
Reference style psychologist Times New Roman 12
Association)

Page 5
 Government College University Faisalabad

1.4. Project Objective

Blood donation is required during an organ transplant, accidents, cancer
treatment and surgeries. The manual blood donation system has many demerits which
includes time consuming, lot of manpower, lack of donor information and less
accuracy in terms of results and percentage. In the time of emergency, it becomes
difficult to approach the right donor. There are many blood donation management
systems, but these systems only maintain the information of blood banks and donors.
This project aims to maintain all information regarding blood donors, different blood
groups available in blood banks and help them to manage in a better way. This project
will facilitate the list of blood donors and also help the recipients to track and search
the right donor easily. The external oversight committee must approve the project
performance measurement plan.

Agency Goals Project Objectives

The main objective of developing the current project
The vital goal is minimized the
entitled Blood Donation system which is fast, accurate,
complexities during the blood
consistency, reliable and flexible enough so that It can
donation.
incorporate any future enhancements
By automating the system using the computers with
Improve the quality of Blood
sophisticated technology which can be used for making
donner Record in real time.
the information accurate , secure and user friendly.
Time and man power can be more effectively utilize
Provide the facility to the users
and online information which can be easily available to
to view their record in a efficient
the user and at the same time we can maintain higher
manner with good quality GUI.
level of security.
1.5. Intended Audience and Reading Suggestions
There are different types of indented audience for this document, such as
developers, testers, document writers and most important the users. We have divided
the rest of the document into different categories It is suggested to begin with
understanding the introduction, general information and, then sequentially go through
content, overview section and proceeding through the detailed description that is most
pertinent. At the end acronyms, abbreviation and analysis models.

Page 6
Government College University Faisalabad

1.6. Project Scope

The purpose of the online blood donation system is to create convenient and
easy-to-use online system for users to get or donate blood. The system is based on a
relational database with. We will have a database supporting dozens of major cities of
Pakistan.
 Human Welfare
 Quick Search
 Better Communication
 Cost Optimizing
 Time Optimizing
 Access Any Time
 Management of returned and unused blood units

2. Overall Description
2.1. Product Perspective
Online Blood donation system will be easier to find a donor for exact blood
type and easy to build the connection between donor and the blood bank authorities.
The main intention of building this software is too formal for procedure of blood
donation to motivate donors in order to donate blood. This system also consists of
some local hardware devices as well. Printer and SMS indicator are the main sources
among the other devices. The entire software products include all-relevant features to
create a better connection between the blood donor & blood bank authorities.
2.2. Product Features:
Admin:
In this module the Administrator has the privileges to add all the Blood Groups
and Blood Types. It can search all the piece of information about the donor. This
module focuses on the both donors & acceptors. Each member in a donor given a user
name and password, which identifies him uniquely. The options given to administrator
in the interface will be Change Password, Maintain donor details, Update donor details.
Admin can maintain donor details
The options given to:
 Maintain donor details
 Maintain referral once
 Update donor details
 View Experiences
 Logout
 Change Password
Whenever a user wants to change his / her password, he can select the change
password option. This system displays the form, which asks him for his old password
and new password. It compares the old password with the existing password in the
database.

Page 7
Government College University Faisalabad

Donor:
Donor is that person who is interested in donating his blood so that he can
register himself through this website. If any demand arises then system will be
contacted and they can donate their blood. This system helps in searching for a
particular blood group if needed. Each member in a Donor module is given a user id
and password, which identifies him uniquely. Member is given a login form. Where he
enters the login details user id and password.
The option given to donor are:
 Change password
 Find a Blood donor of a specific blood group.
 Edit Profile
 Frequently Asked Questions about Blood donation.
 Logout

Acceptor:
In this module any general user who is not registered as a Donor can also
make request for blood if needed. Donor can also make a request for blood
if needed. In this you can search for donors. The options given to
Acceptors are: 
 Register as a blood Donor. (If not yet registered)
 Find a Blood donor for a specific blood group.
2.3. User Classes and Characteristics:
Users of this application are those who use the Blood Donation Web
application in their institutions, it can be used by customers, users, developers and
designers etc. But they have some special characteristics related to web app. The
system provides different types of services based on the type of users.
 Customers: Those who only use the web application.
 Developers: Those who both use the web application as well as edit the web
application.
 Designers: Those who edit, use and change the design of web application.
 Administration: Those who only use the web app and edit the web application.

Page 8
Government College University Faisalabad

2.4. Operating Environment:

The blood donation system is expected to be deployed in a real environment.
The centralized database is to store the information the application is developed as a
web application that can run on windows operating system with internet connectivity
and with wall known browser e.g., Chrome.

Particulars Clint system Server System

Operating system Windows XAMPP

Processor Pentium Pentium4,2GHz
4.1.2GHz
Hard Disk 50GB 100GB
RAM 256MB 512MB

2.5. Design and Implementation Constraints:

During the implementation of the product different challenges are faced.
Choosing the interface for the management system was a paramount issue. Connecting
the database with the application was a major problem. For connecting database, we
had to install XAMPP Server. The connection of database that is created in MySQL
with Laravel.is not very simple. So, for the connection of database with Laravel we
have to create environmental file and provide our database credentials. The college
management system is designed in such a way that the user can easily interact with the
screen because of GUI.
2.6. User Documentation:
In our user manual, we shell keep the information regarding our product which
can be understandable by a new person who is going to use it. If a new person will use
it this system will be helpful to handle and operate.
2.7. Assumptions and Dependencies:
Every donor carries a mobile phone. This system doesn’t keep the details of
the gathering stock of blood. This system database will be accessible in real time.
Donors who want to contribute in a donation will definitely reply to the request of
system. The installation of the system to the website server haven’t considered as a
process inside the system. That process will do by the authorities who are controlling
the website. Therefore, in here the installation process is considered as a process which
is in outside of the scope. A doctor or a patient can request for an exact blood group.

Page 9
Government College University Faisalabad

3. System Features
3.1 System Feature 1:
BDS will help the patients who need blood.
3.2 Description and Priority:
This is also a high priority feature as nothing can be done without input of
required data authentication is most important without this it is useless so it has high
priority level.
3.3. Stimulus/Response Sequences:
Once data is entered into form/table and it is of appropriate format, it is
accepted and saved. If format or data type of data is wrong then system prompts user of
the error in data type and invalidates data, asking the user to input correct data type.
3.4 Functional Requirements
 Login of admin. 
 Blood Donor.
 Change the login password of admin.
 Register the donor by himself.
 Register the donor by system admin.
 Login of the donor.
 Change the login password of donor.
 Change personal, contact details by the donors himself.
 Withdraw reg. details by the admin. 
 Send blood donation details to the relevant donors. 
 Send blood testing details.
3.5. System Feature 2 (and so on)
There are some features of Online blood donation web application.
 Maintain Donor information.
 Donor database Blood group wise and area wise.
 Maintain Donor identification.
 Accurate Database.
 Reduce man power
 Save the time and cost.

4. External Interface Requirements

4.1. User Interfaces:
GUI is one of most important for any kind of computer based or software-
based application, because it helps to manage or control the system easily by using
some icons and some other buttons. A first-time user of the web portal should see the
log-in page when he/she opens the portal. If the user has not registered, he/she should
be able to do that on the log-in page. If the user is not a first-time user, he/she should
be able to see the dashboard which contains different domains like academics and
Profile. Every user should have a profile page where they can edit their e-mail address,
phone number and password and other personal details.

4.2. Hardware Interfaces:

We require LAN connection for interacting with the database and local
computers for any help or any other requirement. We use TCP/IP protocol for

Page 10
Government College University Faisalabad

communicating with local hosts. We also need a system with P4 processor; 2GB RAM
and database memory.
4.3. Software Interfaces:
We use Laravel Framework for writing the code for the project.HTML, CSS,
BOOSTRAP for creating the web pages using GUI for login screens and
interacting with the database. MySQL is used to creating the database. Visual Studio
Code IDE for writings the programs.
4.4. Communications Interfaces
The communication functions required by this product are LAN connection
within the whole college so that the admin, employee and customer can interact with
each other. We use TCP/IP protocol.

5. Other Nonfunctional Requirements

5.1. Performance Requirements:
 This project will meet the user’s requirement.
 Response Time: The response of all the operations included in this project take
minimum time delay according to the speed of operating machine. This can be
made possible by careful programming
 Performance should not be an issue because all of our server queries involve
small pieces of data. Server updates should only take a few seconds as long as
the phone can maintain a steady signal.
Safety Requirements:
The database may get crashed at any certain time due to virus or operating
system failure therefore, it is required take the database backup.
5.2. Security Requirements:
Administrator and Users with valid credentials will be able to log in to Portal.
Administrator will have access to the database structures at back-end. Administrator
will have the rights for modifications as well as any Updating work for the datasets and
website. Access to the various subsystems will be protected by a user log in screen that
requires a user name and password. To be updated in future.
5.3. Software Quality Attributes
Availability: The BDS Portal shall be available, up and running for 24*7 throughout
the year except due to the routine maintenance activities.
Security: The system should encrypt user’s password by using hash encryption
system.
Maintainability: The system should be closed 24 hours per week for maintenance and
elaboration.
Reliability: The system should never crash more than 10 minutes per month.
Usability: The users should learn how to use the system at most in 2 hours.

Page 11
6. WBS Project Management

WBS Online Blood Donation System

7. Tools & Technologies

7.1. Programming Languages
HTML, CSS, Bootstrap, PHP
7.2. Databases/Data storages
MySQL.
7.3. Operating System
Windows 10.

Page 12
Appendix A: Glossary
BDS Blood Donation System
GUI Graphical User Interface
IDE Integrated Development Environment
LAN Local Area Network
TCP/IP Transmission Control Protocol /Internet Protocol
RAM Random Access Memory
GB Giga Byte
XAMPP Apache MySQL PHP Perl

PHP Hyper Text Preprocessor

HTML Hyper Text Markup Language

CSS Cascading Style Sheet

SRS Software Requirement Specification

DFD Data Flow Diagram

Page 13
Appendix B: Analysis Models
Level 0:

User Admin

Search for Organization

Blood Donation
Blood
System

Request for
Blood Login

Upgrade Blood
Information

Page 14
Level 1:

Generate User
Report

Search for Blood

Admin

Request for Blood

Blood
User Donation
System (BDS) Update Blood
Information

Organization
Login

Profile view and

Manage

Page 15
Level 2:

Admin:

Manage user
Login to Check Details
Admin
System Roles of
Access

Manage
Organization
Details

Check
Credentials Manage
Module
Manage Blood
update
information

Manage Role
Of user
Manage Blood
Request Detail
Manage User
Permission

Page 16
 User:

Login to Check Create Account

User System Role of
Access

Search for
Blood

Manage
Check Search for
Module
Credentials Organization

Manage
donation
Information

Organization:

Login to Check Create Account

Organization
System Role of
Access

Manage Donner
Information

Manage
Check Module Manage
Credentials Organization
Information

Manage Blood
Information

Page 17
Appendix C: Check List
Check List Yes No

Project Scope
Product modules (covering all
aspects of scope)
System Features (covering scope)
Interface Requirements
Non-Functional Requirements
WBS
Tools and Technologies Detail
(for implementation)
Plagiarism Report
Starting/Ending Dates
Project Scope

Page 18
 Appendix D: Supervisory Committee

For approval of any two consultant Teacher

Teacher Consulted Teacher Consulted
Name: Name:
Designation: Designation:

Comments: Comments:

Signature: Signature:

---------------------------------------------------------------------
(For office use only)
Date: _______
Approved Group ID

Meeting Required: Date

Time: Place:

Rejected:
Remarks:

Project Title (if Revised):

Project Coordinator

Page 19