Senior project

senior project as attached files

‫| كلية الحوسبة والمعلوماتية‬
College of Computing and Informatics
College of Computing & Informatics (CCI)
SENIOR PROJECT-I REPORT
Author(s):
Student Reg#
Student Name
Student Reg#
Student Name
Student Reg#
Student Name
Student Reg#
Student Name
Student Reg#
Student Name
Student Reg#
Student Name
Project Supervisor:
1
‫| كلية الحوسبة والمعلوماتية‬
College of Computing and Informatics
Topic of Project (28 Pts. Bold)
By: NAME OF PARTICIPTANT(s) (14 Pts. Normal)
Thesis/Project submitted to:
College of Computing & Informatics, Saudi Electronic University, Riyadh, Saudi Arabia.
In partial fulfillment of the requirements for the degree of:
BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY
Project Supervisor
2
Project Committee Chair
ABSTRACT
Include a 2-3 paragraph brief about the project, its utility and your contribution. Also highlight
how the project has helped in your professional growth. It should briefly explain the problem and
why you need to solve it, what method did you use and what is the advantages of your proposed
method with reflection on the findings or results.
DEDICATION
This work is dedicated to…
PREFACE
The preface content comes here. Make sure it is not more than one page. Preface should be used
to describe any special clarifications regarding project report. You may also include
acknowledgment paragraph in this section.
REVISION HISTORY
Name
Date
Reason For Changes
Version
5
TABLE OF CONTENTS
CHAPTER 1: INTRODUCTION ………………………………………………………………………………. 7
1.1
Project Background/Overview: ………………………………………………………………………………7
1.2
Problem Description: ……………………………………………………………………………………………7
1.3
Project Scope: ……………………………………………………………………………………………………..7
1.4
Project Objectives: ……………………………………………………………………………………………….7
1.5
Project Structure/Plan: …………………………………………………………………………………………7
CHAPTER 2: LITERATURE REVIEW …………………………………………………………………….. 8
CHAPTER 3: METHODOLOGY ……………………………………………………………………………… 9
CHAPTER 4: SYSTEM ANALYSIS ………………………………………………………………………… 10
4.1
Product Features: ……………………………………………………………………………………………… 10
4.2
Functional Requirements: …………………………………………………………………………………… 10
4.3
Nonfunctional Requirements……………………………………………………………………………….. 11
4.4
Analysis Models ………………………………………………………………………………………………… 11
CHAPTER 5: SYSTEM DESIGN ……………………………………………………………………………. 12
CHAPTER 6: DISCUSSION & CONCLUSION ………………………………………………………… 13
6.1
Discussion ………………………………………………………………………………………………………… 13
6.2
Conclusion ……………………………………………………………………………………………………….. 13
REFERENCES ……………………………………………………………………………………………………. 14
APPENDIX: Glossary …………………………………………………………………………………………… 15
6
CHAPTER 1: INTRODUCTION
The introduction should set the context for the project and should provide the reader with a summary of
the key things to look out for in the remainder of the report. When detailing the contributions it is helpful
to provide pointers to the section(s) of the report that provide the relevant technical details. The
introduction itself should be largely non-technical. It is useful to state the main objectives of the project as
part of the introduction. Should have the following headings:
1.1
Project Background/Overview:
1.2
Problem Description:
Briefly describe the problem and the need to solve it
1.3
Project Scope:
Describe the aims, benefits and the outcome of the solution developed
1.4
Project Objectives:
Describe the predetermined results or achievements
1.5
Project Structure/Plan:
Describe all the activities to be carried out from the start of the project till the end. Describe each
activity start, finish, duration, resource required and duration in tabular form and in textual form a
swell. Draw associated ADM/PDM Diagrams as well as GANTT charts for further elaboration.
You can also use mind maps show how your projects is structured or planned.
7
CHAPTER 2: LITERATURE REVIEW
Literature review is a systematic method of identifying, evaluating and interpreting the work (similar to
yours) produced by others. This chapter should set the project into context and give the proposed layout
for achieving the project goals. It is an important chapter especially if the project involves significant
amount of ground work. Review prior work critically, identify gaps in knowledge/areas of application and
build an argument for your own work. When referring to other pieces of work, cite the sources where they
are referred to or used, rather than just listing them at the end.
Note: Every model should be described under separate level 03 heading and with brief description.
12
CHAPTER 6: DISCUSSION & CONCLUSION
6.1
Discussion
6.2
Conclusion
13
REFERENCES
14
APPENDIX: Glossary
15
Course Expectations: Assignments Total 1000 points
Please note that each assignment builds on the previous
assignment(s) for this course. Each assignment will contribute to
your ability to complete the final deliverable for this course, the
Business and Technical Requirements document. Therefore, it is
important to complete each assignment on time and to read all
supporting learning materials.
Week
Assignment
2
2-1: Written Response (25 pts)
2-2: Discussion (5 pts)
2-3: Discussion (5 pts)
3
3-2: Select Senior Research Project (50 pts)
4
4-1: Literature Review (50 pts)
5
5-1: Value of the EHR Component (50 pts)
6
6-1: Organization Readiness (70 pts)
7
7-1: Systems Development Lifecycle (70 pts)
8
8-1: Data Requirements (50 pts)
9
9-1: Discussion (5 pts)
10
10-1: Conceptual Model (50 pts)
11
11-1: Logical System Design (60 pts)
12
12-1: Physical System Design (60 pts)
13
13-1: Business and Technical Requirements document: General Information
(70 pts)
14
14-1: Business and Technical Requirements document: Current System
Summary (70 pts)
15
15-1: Business and Technical Requirements document: Proposed System and
Design Considerations (140 pts)
16
16-1: Develop a Power Point Presentation of your Senior Research Project (70
pts)
16-2: Present your Senior Research Project (100 pts)
College of Computing & Informatics (CCIT)
SENIOR PROJECT REPORT
Web Solution of Blood Bank
Management
Project Team:
140110516
150028861
Atha Alghanmi
Jumana Almaghrabi
Project Supervisor
DR. Laxmi Upadhyay
SAUDI ELECTRONIC
UNIVERSITY
Web Solution of Blood Bank
Management
By
Atha Alghanmi
Jumana Almaghrabi
Thesis/Project submitted to
College of Computing & Informatics,
Saudi Electronic University,
Riyadh, Saudi Arabia.
in partial fulfillment of the requirements for the degree of
BACHELOR OF SCIENCE
IN
INFORMATION TECHNOLOGY
DR. Laxmi Upadhyay
Project Supervisor
Project Committee Chair
ABSTRACT
RedShare is an online platform that provides a service in the field of health in
the Kingdom of Saudi Arabia. It brings together three important parties: donors, blood
banks and donation campaigns.
This service allows the three users to easily communicate with each other by entering
their necessary data, update their data continuously, make requests for donations and
respond to donations campaigns. Donors can also find blood banks through the “Find
the Location” feature, by showing a map to the donor that showing blood banks in their
area.
RedShare provides a 24-hour service where blood banks can request blood
donations at any time, faster and more efficiently and to achieve the necessary comfort
for users. This also provides the donor with the possibility of updating his data, for
example changing the area or adding diseases, if any.
This service aims to urge people to donate, due to the increasing number of
messages on social media, which shows the lack of electronic platforms, whether
applications or sites that facilitate the process of requesting blood and the rapid response
of donors to the request.
Through our work on this project, we have acquired the necessary skills to start
and finish projects properly, and it added a lot on the personal and professional side.
He also helped to understand the development cycle of websites starting from the
planning stage to the end of the testing and deployment phase. it has also enhanced our
cooperation and teamwork for satisfactory and high-quality results.
Web Solution of Blood Bank Management
DEDICATION
First and foremost, we would like to thank the supervisor of our senior project,
Dr. Laxmi Upadhyay, for his support, to give us all the advice, guidance and to instill hope within
us to continue the completion of this project.
We would also like to express our gratitude and appreciation to our instructors for their
encouragement, patience, and assistance over the years. We are forever indebted to our university
which taught us that “self-reliance is the most important requirement for success”.
Page ii
Web Solution of Blood Bank Management
PREFACE
This report contains information related to the RedShare website, created to facilitate blood
donation between the donor and the blood bank. It will make it easier for users to meet requests
for donations, order blood type, know the locations of hospitals and the dates of volunteer
campaigns, etc.
Due to the increasing number of blood donation requests on social media sites and
randomly, it became necessary to include all these messages in the platform that facilitates the
requests process for hospitals and responses from donors. People ignore the ads of volunteer
campaigns launched by hospitals and blood centers in the country, which led to the lack of specific
blood groups from some centers, which exacerbated many cases of patients. Therefore, we have
also facilitated this process so that all ads reach all users by certain procedures. This site will help
save time and effort for all users.
The main purpose of this report is to clarify all the functional and non-functional
requirements, models of analysis and design that should be taken in the implementation phase.
This project will be presented as a final project for the Information Technology specialization in
the Bachelor’s degree at the College of Computing and Informatics at the Saudi Electronic
University.
Page iii
Web Solution of Blood Bank Management
Table of Contents
Table of Contents …………………………………………………………………………………………………………. iv
Revision History …………………………………………………………………………………………………………. viii
Chapter 01: Introduction ………………………………………………………………………………………………..1
1.1
1.2
1.3
1.4
1.5
1.6
Product………………………………………………………………………………………………………………………… 1
Scope ………………………………………………………………………………………………………………………….. 1
Business Goals …………………………………………………………………………………………………………….. 1
Document Conventions …………………………………………………………………………………………………. 1
Literature Review …………………………………………………………………………………………………………. 2
Project Plan ………………………………………………………………………………………………………………….. 5
Chapter 02: Overall Description ……………………………………………………………………………………..9
2.1
2.2
2.3
2.4
2.5
Product Features …………………………………………………………………………………………………………… 9
User Classes and Characteristics …………………………………………………………………………………… 10
Operating Environment ……………………………………………………………………………………………….. 10
Design and Implementation Constraints ………………………………………………………………………… 10
Assumptions and Dependencies ……………………………………………………………………………………. 11
Chapter 03: Software Analysis and Design …………………………………………………………………….12
3.1
Functional Requirements ……………………………………………………………………………………………… 12
3.1.1 Use-Case 1: Register ……………………………………………………………………………………………….. 12
3.1.2 Use-Case 2: Login …………………………………………………………………………………………………… 13
3.1.3 Use-Case 3: Create Account …………………………………………………………………………………….. 14
3.1.4 Use-Case 4: Update Information……………………………………………………………………………….. 15
3.1.5 Use-Case 5: Request Blood………………………………………………………………………………………. 16
3.1.6 Use-Case 6: Send Notification ………………………………………………………………………………….. 17
3.1.7 Use-Case 7: Create Ad …………………………………………………………………………………………….. 18
3.1.8 Use-Case 8: Publish Ad …………………………………………………………………………………………… 19
3.1.9 Use-Case 9: View location in map …………………………………………………………………………….. 20
3.1.10 Use-Case 10: Donation Statistics ………………………………………………………………………………. 21
3.1.11 Use-Case 11: Logout ……………………………………………………………………………………………….. 22
3.2
Nonfunctional Requirements ………………………………………………………………………………………… 23
3.2.1 Performance Requirements ………………………………………………………………………………………. 23
3.2.2 Safety Requirements ……………………………………………………………………………………………….. 23
3.2.3 Security Requirements …………………………………………………………………………………………….. 23
3.2.4 Software Quality Attributes ……………………………………………………………………………………… 24
3.3
Software Analysis Models ……………………………………………………………………………………………. 25
3.3.1 Use-Case Diagram ………………………………………………………………………………………………….. 25
3.3.2 Abstract Class Diagram …………………………………………………………………………………………… 26
3.3.3 Entity-Relationship Diagram ……………………………………………………………………………………. 27
3.3.4 Class Diagram ………………………………………………………………………………………………………… 28
3.3.5 Sequence Diagram ………………………………………………………………………………………………….. 29
3.3.6 Event Table ……………………………………………………………………………………………………………. 33
3.4
Software Design Models ……………………………………………………………………………………………… 34
3.4.1 Component Diagram ……………………………………………………………………………………………….. 34
3.4.2 Deployment Diagram ………………………………………………………………………………………………. 35
Chapter 04: System Implementation ……………………………………………………………………………..36
4.1
Software Algorithm …………………………………………………………………………………………………….. 36
4.2
Software Implementation Code …………………………………………………………………………………….. 37
4.3
Database Design and Implementation ……………………………………………………………………………. 41
4.3.1 Database Management System …………………………………………………………………………………. 41
4.3.2 Database Schema ……………………………………………………………………………………………………. 43
4.3.3 Database Physical Model …………………………………………………………………………………………. 45
4.3.4 Completed Database Screenshots ……………………………………………………………………………… 47
Page iv
Web Solution of Blood Bank Management
4.4
Software Interfaces ……………………………………………………………………………………………………… 50
4.4.1 Home Page …………………………………………………………………………………………………………….. 50
4.4.2 Login Page …………………………………………………………………………………………………………….. 51
4.4.3 Register Page………………………………………………………………………………………………………….. 51
4.4.4 Donor Profile page ………………………………………………………………………………………………….. 52
4.4.5 Hospital Profile Page ………………………………………………………………………………………………. 53
4.4.6 Volunteer Campaigns Profile Page ……………………………………………………………………………. 54
4.4.7 Emergency Form …………………………………………………………………………………………………….. 55
4.4.8 Admin Interface ……………………………………………………………………………………………………… 56
Chapter 05: Software Testing and Evaluation ………………………………………………………………..57
5.1
Software Testing …………………………………………………………………………………………………………. 57
5.1.1 User Register ………………………………………………………………………………………………………….. 57
5.1.2 Login …………………………………………………………………………………………………………………….. 57
5.1.3 Receive Notifications ………………………………………………………………………………………………. 58
5.1.4 Request Blood ………………………………………………………………………………………………………… 58
5.1.5 Create Ad ………………………………………………………………………………………………………………. 59
5.1.6 Publish Ad ……………………………………………………………………………………………………………… 59
5.1.7 Emergency Form …………………………………………………………………………………………………….. 60
5.1.8 Logout …………………………………………………………………………………………………………………… 60
5.2
Software Verification ………………………………………………………………………………………………….. 61
Chapter 06: Conclusion and Future Work……………………………………………………………………..62
References …………………………………………………………………………………………………………………….63
Appendix: Glossary ………………………………………………………………………………………………………66
Page v
Web Solution of Blood Bank Management
List Of Tables
1. Table 1: Project Plan
2. Table 2: UC-1
3. Table 3: UC-2
4. Table 4: UC-3
5. Table 5: UC-4
6. Table 6: UC-5
7. Table 7: UC-6
8. Table 8: UC-7
9. Table 9: UC-8
10. Table 10: UC-9
11. Table 11: UC-10
12. Table 12: UC-11
13. Table 13: Event Table
14. Table 14: Database Physical Model
15. Table 15: TC-1
16. Table 16: TC-2
17. Table 17: TC-3
18. Table 18: TC-4
19. Table 19: TC-5
20. Table 20: TC-6
21. Table 21: TC-7
22. Table 22: TC-8
23. Table 23: List of non-trivial defects
Page vi
Web Solution of Blood Bank Management
List Of Figures
1. Figure 1 : Arrow Diagramming Method
2. Figure 2 : Precedence Diagramming Method
3. Figure 3 : Gantt Chart
4. Figure 4 : Use-Case Diagram
5. Figure 5 Abstract Diagram
6. Figure 6 Entity Relationship Diagram
7. Figure 5 : ER Diagram
8. Figure 7 : Class Diagram
9. Figure 8 : Sequence Diagram For Admin
10. Figure 9 : Sequence Diagram For Donor
11. Figure 10 : Sequence Diagram For Hospital
12. Figure 11 : Sequence Diagram For Voluntary Campaigns
13. Figure 12 : Component Diagram
14. Figure 13 : Deployment Diagram
15. Figure 14: Control Flow Diagram
16. Figure 15: Database Schema
Page vii
Web Solution of Blood Bank Management
Revision History
Name
Date
Reason For Changes
Version
Page viii
Web Solution of Blood Bank Management
Chapter 01: Introduction
1.1 Product
The product we propose is a website that provides a solution for the blood bank sector in the
Middle east and Muslim refugees, and facilitates the process of bridging the need for blood banks. It is
an electronic means between blood banks and donors.
1.2 Scope
The site will include countries and Muslim refugee areas, that need the largest number of
donors.
1. Develop a website to solve the problem of blood banks
2. Register Blood Banks and Donors
3. Presenting the countries and refugee areas in need with priority
4. Host all contribute and blood campaigns.
1.3 Business Goals
We aim to provide a healthy and humane service through the use of technology which has
become a quick tool to reach several places and solve all problems. The site aims to meet the needs of
blood banks in our country and especially in the areas the presence of health centers Muslim refugees,
which will be a quick way to request blood from banks. For donors, it is a flexible and convenient way
to provide their information and contact with blood banks. We also aim to host campaigns and
volunteer contributions to inspire and educate people to volunteer.
1.4 Document Conventions
In this document, we use Times New Roman as font of all the paragraphs and Times font for
Headings and subheadings. Also, we use three size 18, 14, and 12. And italic font for the common terms.
The space between lines we use (1.5).
Page 1
Web Solution of Blood Bank Management
1.5 Literature Review
This document focuses on the blood donation management system, which is a web application
with a compatible mobile application that serves as a communication tool between patients (who need
blood) and the blood donor. To become members of the system, donors must create their profiles by
providing essential information such as name, blood group, email address, password and exact location
of “Google Map”. In order to find out the exact location of a donor, Google Map integrates with this
application. The mobile application always updates the location of a donor. As a result, the system can
automatically find a registered donor wherever he goes. Visitors can search for blood donors on the home
page by blood group and where blood is needed. The system will display the available donors along with
your phone number, email address and email address through your organization by nearest location and
the expiration date of the blood donation. Visitors can send messages to all donors via email, but a
member can send messages via email and mobile phone. An appointment will be created only when a
donor confirms that he / she will donate blood. Then the system will alert the donor before 12 hours of
donation. Blood donors can also be searched from the mobile application, but this is only accessible to
registered members. The purpose of this document is to reduce the complexity of the system to find
blood donors in an emergency situation. [13]
Most people want to know about online blood donation to patients at the same time. Patients
want to obtain Blood to live in time of emergency. Nowadays people are needed to know how to get in
touch with blood donors online. This system provides information on how to obtain blood at the most
serious time to prolong the life. Pairing system is implemented with Decision Tree and Table of decisions
by rules. This matcher applies the rules based on Blood donation in the blood bank in Myanmar.
Information has been reserved about donors and patients in the system so you are ready to donate blood
instantly. [14]
In the web-based blood donation system; it is mainly used to maintain the record of blood stocks.
In today’s system. First is the manual system and also when the person requires the particular type of
blood and if that type is not available in that blood bank, then it’s a long time to organize the blood of
Another blood bank can affect the patient’s health because the time is Very important in accidental cases.
So, in the blood based on the web the donation system is the best to verify if a particular type of Blood
is available in the stack or not and also gives the location climate that available. [15]
Page 2
Web Solution of Blood Bank Management
Other paper presents a high-end system to close the gap between blood donors and people who
need blood. The application for the blood bank management system is a way to synchronize blood banks
and hospitals with the help of Internet. It is a web application through which registered hospitals can
verify the availability of necessary blood and can send the Blood Request to the nearest blood bank or
donor that matches the blood requirement and you can apply online as and when necessary. The blood
bank may also send a request to another blood bank for unavailable blood. Person willing to donate.
Blood can find the nearest blood banks through the Android Blood Bank Management application. The
location of the blood bank. It can also be tracked using maps. Only donors can access the Android
application to search for blood donation. Centers and blood banks and hospitals that request to look for
nearest blood banks and donors. [16]
As we all know the operation of the blood bank management system. A blood bank is a cache or
Bank of blood or blood components, gathered as a result of the donation or collection of blood, stored
and preserved for later use in blood transfusions. But the real fact is that the blood transfusion service is
a trillion dollars. Profession / business around the world. So much Corruption involves in this System.
Still, we will not like to call It’s a business because of the fear in our minds that our general population
or blood donors will feel upset. With us and you cannot come to donate again. To solve this big problem,
they present the new concept of blood bank management system using a cloud computing concept. This
document is also an aid for provide a way to reduce the corruption involved in this Good job. With the
help of this new concept, also improve the facilities of the blood bank management system in the rural
area. In this document they using a The concept of cloud computing as we all know, what is the simple
definition of cloud computing in a very Simple word, they say that Cloud Computing is On Demand
Services. Many times, they do not clarify the donor in the moment of the donation there is a service
charge for the blood units. As a result, when the donor needs blood, it comes as a rude punch and he
makes accusations of the “sale” of blood. At that moment, the situation becomes. Embarrassing because
we hesitate to accept that we follow a cost recovery system that is part of the deal. In this research work,
they present a mobile blood bank management system based on SMS for rural areas. Area that connects
directly to the server in the cloud located in another location. Because in the rural area of the blood bank.
The management system does not have enough facilities to store blood in a long time. [17]
Page 3
Web Solution of Blood Bank Management
RedShare offers new horizons for health that offer health services using the Mobile devices and
communication technologies. In health services, blood donation is a complex process and it takes time
to find a donor that has blood group compatibility with the patient the proposed system is an Androidbased blood bank application to establish a Connection between the applicant and the donor at any time
and in any place. A blood bank as we know. Provides blood to people in need in times of emergency.
The blood bank system is designed in such a way that users can see the information about registered
blood donors that will help at the time of need. The proposed system has a login page where the user
must register, but the user does not You do not have to register if you do not find the desired result. The
user can also register to donate blood. In the system if they wish. In this way, this system helps to select
the right donor instantly using blood. Group. The main objective of the development of this system is to
reduce the time spent on Searching for the right donor and the availability of blood required. So, the
proposed system. It provides the required information quickly and also helps in making decisions faster.
[18]
There are other study uses data mining modeling techniques to examine the classification of
blood donors and their extension to facilitate the development of blood donor management in real time
using Boards with blood profile and geolocation data. Is allows decision makers the ability to manage
and plan the Blood donation activities based on key metrics. This ability it offers the possibility of
planning an effective and directed blood donation. Campaigns the scoring algorithm implemented for
the dashboard also helps in the optimized implementation of the budget Determination of resources and
budget allocation for blood. Donation campaigns. [19]
There is an expectation that blood will always be there when it is really necessary. Blood donor
volunteers are the main source of supply in an effective management of the blood supply chain. They
feed the blood reserves through your donation. In an emergency situation, if stocks are insufficient, the
only source of blood supply will be the people who go to the health center and donate blood voluntarily.
It is true that time is a very important component in such a situation. For this reason, the health care
center should call the nearest available donor to make sure they get the service as quickly as possible.
An application for smartphones was developed to facilitate the identification of the nearest available
blood donor volunteer and communication with him / her in emergency situations where blood cannot
be supplied through blood bank reserves. In this work this application will be presented. [20]
Page 4
Web Solution of Blood Bank Management
1.6 Project Plan
To develop any project, we need an approach that clarifies the course of work. In this case, we
chose the waterfall model as the stages of software development through specific steps: planning,
analysis, design, implementation, testing and delivery. The approach helps track operations on a regular
basis. In the sense that each step depends on the previous stage.
This approach provides an easy understanding and interpretation of its separate phases, which enables it
to correctly identify the requirements at each stage and to work the project appropriately.
Planning Process
In this process identifies and clarifies the project by establishing the project development
structure, identifying the basic functions of the application, clarifying the time period of the stages. Also,
organizing the resources such as Entity-Relationship diagram and Use-Case diagrams.
Executing Process
In this process, execute the tasks of the planning process, the distribution of tasks among the team
members, and the confirmation of the tasks by the supervisor to avoid risks occur.
Testing and delivery Process
Create the final report explaining the testing process performed by different users and sending it
to the supervisors of the project.
Page 5
Web Solution of Blood Bank Management
Task Name
Start Date
Introduction
28/01/2019
Product
28/01/2019
Scope
28/01/2019
Business Goals
28/01/2019
Document Conventions
03/02/2019
Literature Review
03/02/2019
Project Plan
05/02/2019
References
03/02/2019
Overall Description
10/02/2019
Product Features
10/02/2019
User Classes and Characteristics
11/02/2019
Operating Environment
12/02/2019
Design and Implementation Constraints 14/02/2019
Assumptions and Dependencies
15/02/2019
Use Case
16/02/2019
Register
16/02/2019
Login
17/02/2019
Create Account
17/02/2019
Update Information
18/02/2019
Request Blood
18/02/2019
Send Notification
18/02/2019
Create Ad
20/02/2019
Publish Ad
20/02/2019
View Location in Map
20/02/2019
Donation Statistics
20/02/2019
Logout
20/02/2019
Nonfunctional Requirements
01/03/2019
Performance Requirements
01/03/2019
Safety Requirements
02/03/2019
Security Requirements
03/03/2019
Software Quality Attributes
04/03/2019
Appendix Glossary
10/03/2019
Software Analysis Models
13/03/2019
Use-Case diagram
13/03/2019
Entity-Relationship diagram
16/03/2019
Class diagram
19/03/2019
Sequence diagram
22/03/2019
Software Design Models
25/03/2019
Component diagram
25/03/2019
Deployment diagram
25/03/2019
End Date Duration
9/2/2019
13 Days
28/01/2019 1 Days
28/01/2019 1 Days
28/01/2019 1 Days
03/02/2019 1 Days
09/02/2019 7 Days
05/02/2019
1 Day
09/02/2019 7 Days
15/02/2019 5 Days
10/02/2019 1 Days
11/02/2019 1 Days
12/02/2019 1 Days
14/02/2019 1 Days
15/02/2019 1 Days
20/02/2019 5 Days
16/02/2019 1 Days
17/02/2019 1 Days
17/02/2019 1 Days
18/02/2019 1 Days
18/02/2019 1 Days
18/02/2019 1 Days
20/02/2019 1 Days
20/02/2019 1 Days
20/02/2019 1 Days
20/02/2019 1 Days
20/02/2019 1 Days
04/03/2019 4 Days
01/03/2019 1 Days
02/03/2019 1 Days
03/03/2019 1 Days
04/03/2019 1 Days
12/03/2019 3 Days
24/03/2019 12 Days
15/03/2019 3 Days
18/03/2019 3 Days
21/03/2019 3 Days
24/03/2019 3 Days
25/03/2019 1 Days
25/03/2019 1 Days
25/03/2019 1 Days
Assigned To
ATHA
ATHA
ATHA
ATHA
JUMANA
ATHA
BOTH
ATHA
ATHA
ATHA
ATHA
ATHA
ATHA
JUMANA
JUMANA
JUMANA
JUMANA
JUMANA
ATHA
ATHA
ATHA
ATHA
ATHA
ATHA
ATHA
ATHA
ATHA
ATHA
ATHA
JUMANA
JUMANA
ATHA
JUMANA
ATHA
Table 1: Project Plan
Page 6
Web Solution of Blood Bank Management
Figure 1: Arrow Diagramming Method ( ADM )
Figure 2: Precedence Diagramming Method ( PDM )
Page 7
Web Solution of Blood Bank Management
Figure 3: Gantt Chart
Page 8
Web Solution of Blood Bank Management
Chapter 02: Overall Description
2.1 Product Features
The main features focus on making the site more user-friendly. It includes:
•
User Register: The interface includes three types of accounts: user, volunteer campaigns and
blood banks. Allows the user to choose the type of account he wants.
•
User Log in: An interface that allows the user to log on to the site by entering his username and
password. Require that the user have an account that has been created.
After successful login, the user will be able to:
•
User information: This step allows the user to complete his information and will be stored in a
database that enables the admin to deal with it according to the site’s requirements.
•
Update Information: The donor will be able to update his personal information that has already
been entered, such as social status, city, health condition, diseases, etc.
•
User Alert: The admin has been able to send the donate notices to the donor through the mobile
number or e-mail.
•
Find the nearest hospital: An advantage for the donor is to facilitate to find a hospital that offers
blood donation services. Through the GPS service.
•
Create Ads: This feature enable the Voluntary campaigns accounts to create and display ads on
the site’s homepage.
•
Site Statistics: The feature enables the admin to calculate the numbers of donors and voluntary
campaigns and show them to the interface of the site, through the accounts entered the database.
•
User Log Out: Enables the user to log out from his account properly and effectively.
Page 9
Web Solution of Blood Bank Management
2.2 User Classes and Characteristics
•
Administrator: The primary user of the site, which manages all accounts and do all the
activities of the site.
•
Donor: The donor who registered on the site and he can also find out about donation requests,
volunteer campaigns and blood banks that near him.
•
Volunteer campaigns: People who carry out voluntary blood donation campaigns.
•
Blood banks: that receive donors and meet the needs of blood donation.
•
Gust: Who can visit the Web-site.
2.3 Operating Environment
Website usually works in different operating systems such as Mac and Windows. In addition to various
facilities such as laptops, desktops, and mobile phones that Can access a web browser and Internet
connection such as Google Chrome, Internet Explorer, Firefox. [26]
The hardware we have used include the mouse, the keyboard, and monitor screen. The languages
in which the project is implemented are PHP, HTML and JavaScript language to create interactive pages
and easy interaction, HTML protocol is used to make sure that Information about events and event
owners must be saved and Stored in a database that we can access through websites. [26]
In addition, we will use Komodo Edit to write the code, and we will also use the MAMP server
and MySQL to handle the databases of the site.
2.4 Design and Implementation Constraints
The Blood Bank website facilitates the functioning of blood banks by dealing with donors. The
site will be available 24/7, so that users can access the site anytime, anywhere. The design will be
compatible with the concept of the project and will also use simple designs to enable users to interact
with the site without problems. It requires dealing with the site correctly by making sure to connect to
the Internet and make sure versions of modern operating systems devices of Mac and Windows.
Page 10
Web Solution of Blood Bank Management
2.5 Assumptions and Dependencies
Assumptions about Users:
•
The donor data is correctly registered in the database.
•
Ensure the validity of blood banks involved.
•
Ensure voluntary donation campaigns and under any health organization working.
•
Make sure the username and password of the user and their validity to access the site.
Assumptions based on site development:
•
Write the code correctly.
•
Create databases and link them together effectively.
•
The site’s ability to provide fast data access and processing must be ascertained.
The Dependences are:
•
Communicate with donors through information that is stored securely.
•
Periodic follow-up of databases and validation of information entered by the administrator.
•
Users can access their accounts on the site through any device through the user name and
password.
Page 11
Web Solution of Blood Bank Management
Chapter 03: Software Analysis and Design
3.1 Functional Requirements
Functional requirements specify all components required for the system. These components
may be the steps of user interaction with the system, data processing and other specifications that
support the system. The following use cases explain the main requirements of the Blood Bank website.
3.1.1 Use-Case 1: Register
Identifier
Purpose
Priority
Pre-conditions
Post-conditions
UC-1
The user Register by User name and Password.
High
The user must have email to register.
The Admin send e-mail to verified the user with user name and
password.
Typical Course of Action
S#
Actor Action
System Response
1
Select the account {Donor, Hospital,
Voluntary Campaigns}.
2
Fill in the registration form and press the
Submit button.
3
Log in into the website with username
and password that registered.
Open the account that user selected.
Add user information to the database.
Send message by phone number to the
user with username and password.
Display the website.
Alternate Course of Action
S#
Actor Action
System Response
1
Press the cancel button.
The system returned to the Select
Account page.
2
Invalid information entered.
Display error message and mark the
incorrect fields.
Table 2: UC-1
Page 12
Web Solution of Blood Bank Management
3.1.2 Use-Case 2: Login
Identifier
Purpose
Priority
Pre-conditions
UC-2
The user Login with user name and password.
High
The user has account in website.
Post-conditions
User are authenticated
Typical Course of Action
S#
1
Actor Action
Enter username and password
2
Press login
System Response
Authenticate user.
Alternate Course of Action
S#
Actor Action
System Response
1
Work As guest
Restriction
Table 3: UC-2
Page 13
Web Solution of Blood Bank Management
3.1.3 Use-Case 3: Create Account
Identifier
Purpose
Priority
Pre-conditions
UC-3
The user create account by add the details.
High
User are authenticated
Post-conditions
Donor or hospital details are entered and updated
Typical Course of Action
S#
Actor Action
1
The user enters details like age, blood Information are posted to database
group, city, and gender.
System Response
Alternate Course of Action
S#
Actor Action
System Response
1
User has not completed the data.
Alert the user to complete the data by
showing the alert message
Table 4: UC-3
Page 14
Web Solution of Blood Bank Management
3.1.4 Use-Case 4: Update Information
Identifier
Purpose
Priority
Pre-conditions
UC-4
The donor update his data.
Medium
The user has completed his data and has made a donation.
Post-conditions
The donor can donate again.
Typical Course of Action
S#
Actor Action
System Response
1
Clicking on the disease field and
updating it.
2
Clicking on the Social status field and
put the new data if he has.
3
Clicking on the city field and put the new
data if he has.
Update in the database.
Give permission to donate again
Alternate Course of Action
S#
1
Actor Action
System Response
The user has not added any new
information.
Give permission to donate again
Table 5: UC-4
Page 15
Web Solution of Blood Bank Management
3.1.5 Use-Case 5: Request Blood
Identifier
Purpose
Priority
Pre-conditions
UC-5
Request for donation by hospital.
High
The hospital or blood banks have account in website.
Post-conditions
Request are posted
Typical Course of Action
S#
Actor Action
1
Enter details of request like location, Give the blood group from database.
blood group, date and time
Posted the request.
System Response
Alternate Course of Action
S#
Actor Action
System Response
1
No blood group was entered
Show the message “Please enter the
blood group”.
Table 6: UC-5
Page 16
Web Solution of Blood Bank Management
3.1.6 Use-Case 6: Send Notification
Identifier
UC-6
Purpose
The admin sends a donation notification to the donors
Priority
High
Pre-conditions
Send to donors registered through database information.
Post-conditions
Donors receive the message.
Typical Course of Action
S#
Actor Action
1
The admin request Information of donors
The system searches the databases
2
The admin creates the notification
message.
Send to the donors.
System Response
Table 7: UC-6
Page 17
Web Solution of Blood Bank Management
3.1.7 Use-Case 7: Create Ad
Identifier
UC-7
Purpose
Create an advertisement for voluntary blood donation campaigns.
Priority
Medium
Pre-conditions
The voluntary campaigns have account.
Post-conditions
Publish ad through the website.
Typical Course of Action
S#
Actor Action
System Response
1
Tap the advertisement button.
Open the ad form.
2
Add the data in field like city, time, date
, name of blood banks and description.
Make the ad.
3
Review ad.
Publish ad.
Alternate Course of Action
S#
Actor Action
System Response
1
Clicking cancel button before reviewing.
Don’t Publish ad.
Table 8: UC-7
Page 18
Web Solution of Blood Bank Management
3.1.8 Use-Case 8: Publish Ad
Identifier
UC-8
Purpose
The admin publish ad through email and Ads box in website.
Priority
Medium
Pre-conditions
Create the ad.
Post-conditions
The donors receive the ad.
Typical Course of Action
S#
Actor Action
System Response
1
Clicking the publish button
Open the window have the request ads.
2
Select the ad by new dates that added.
Posting the ad.
Table 9: UC-8
Page 19
Web Solution of Blood Bank Management
3.1.9 Use-Case 9: View location in map
Identifier
UC-9
Purpose
View location in map by donors
Priority
Low
Pre-conditions
Receive the request of donation
Post-conditions
Donor goes to the hospital to donate blood.
Typical Course of Action
S#
Actor Action
1
Enter user name and password.
System Response
User Authentication
2
Click the map button
Display the map.
3
Click log out button.
Close the map and logout the user.
Alternate Course of Action
S#
1
Actor Action
System Response
Username and password are wrong.
Show the message “Error in username
or password.”.
Table 10: UC-9
Page 20
Web Solution of Blood Bank Management
3.1.10 Use-Case 10: Donation Statistics
Identifier
UC-10
Purpose
Donation statistics
Priority
Low
Pre-conditions
Admin are authenticated
Post-conditions
Display the statistics.
Typical Course of Action
S#
Actor Action
System Response
1
Click the Donation statistics button
Open the window
2
Request the statistics for blood group.
Select the blood group from database.
3
Order of blood groups descending.
Distribution the statistics for blood
group into 4 display interfaces.
Table 11: UC-10
Page 21
Web Solution of Blood Bank Management
3.1.11 Use-Case 11: Logout
Identifier
UC-11
Purpose
The user Logs out of the system.
Priority
Medium
Pre-conditions
The user must be logged in.
Post-conditions
The user is logged out.
Typical Course of Action
S#
1
Actor Action
System Response
Save any modification.
Display home page.
Tap Log out Button.
Alternate Course of Action
S#
Actor Action
System Response
1
10 minutes without interaction.
System Log out the user account.
2
User close the website.
End session and Log out the user.
Table 12: UC-11
Page 22
Web Solution of Blood Bank Management
3.2 Nonfunctional Requirements
3.2.1 Performance Requirements
Performance requirements are applied to the system through the speed of system interaction with
the user. The system must be enabled to achieve the desired results and to address many requests in less
than a second. The Blood Bank website acts as an interface between donor and blood banks, so the speed
of communication and system efficiency between blood banks and donors should be free from any
problems.
Therefore, the website must be able to bear the workload, it is obliged to update the databases in
a timely manner. As well as the speed of it response to the admin to send donation notices to registered
donors. The site must be accessible to all on a 24/7.
3.2.2 Safety Requirements
The Blood Bank website relies on databases that include data from donors, blood banks and
voluntaries campaign, which are necessary to protect them from any errors that cause damage or
tampering with them. Therefore, our development plan for the site is based on the creation of a repository
that stores backup copies of databases and maintains them in a security location. Care is also taken not
to access such data from non-admins on the site.
Data encryption increases the use of the site in a secure manner, so site development depends on
encrypting sensitive user data such as emails and phone numbers from unauthorized access.
3.2.3 Security Requirements
Security requirements are an important step in developing a system. For a security site, we have
identified the following security requirements:
•
Specify password policies and criteria, such as must contain a large letter, numbers and symbols
and not to exceed 8 digits to ensure a strong password.
•
Password encryption by the system before it is stored in the database.
•
Enable users to access only the data they are authorized to use.
•
Prevent malicious programs that are not authorized to infect the site and by providing the site
with protection tools.
Page 23
Web Solution of Blood Bank Management
•
Prevent SQL injections attacks.
3.2.4 Software Quality Attributes
System quality features provide user satisfaction with the system. So, we are keen to be provided
and developed correctly.
•
Adaptability: The site should be suitable for new changes and expansion by increasing the
number of users.
•
Availability: The site must be available 24/7. To meet the needs of hospitals and blood banks for
requests for blood donation.
•
Correctness: The site’s handling of donor data must be of the highest accuracy.
•
Flexibility: The ability of the site to deal with changes outside the usual, when an unintended
error by the user, the site can deal with it easily.
•
Reliability: The ability of the site to maintain its performance and to respond to requests and
dealing with error without failure, as it can be in the stage of recovery at the occurrence of any
failure.
•
Testability: Check that the system can create test criteria on its components and evaluate whether
they are met or not.
•
Usability: The system can navigate between its cases by developing the system interface in an
easy and understandable way.
•
Security: The quality of the system lies in the level of security and this level is provided by
guaranteeing user accounts and avoid hacking.
Page 24
Web Solution of Blood Bank Management
3.3 Software Analysis Models
3.3.1 Use-Case Diagram
Figure 4: Use-case Diagram
Page 25
Web Solution of Blood Bank Management
3.3.2 Abstract Class Diagram
Figure 5: Abstract Diagram
Page 26
Web Solution of Blood Bank Management
3.3.3 Entity-Relationship Diagram
Figure 6: ER Diagram
Page 27
Web Solution of Blood Bank Management
3.3.4 Class Diagram
Figure 7: Class Diagram
Page 28
Web Solution of Blood Bank Management
3.3.5 Sequence Diagram
Figure 8: Sequence Diagram for Admin
Page 29
Web Solution of Blood Bank Management
Figure 9: Sequence Diagram for Donor
Page 30
Web Solution of Blood Bank Management
Figure 10: Sequence Diagram for Hospital
Page 31
Web Solution of Blood Bank Management
Figure 11: Sequence Diagram for Voluntary Campaigns
Page 32
Web Solution of Blood Bank Management
3.3.6 Event Table
Event
Trigger
Source
User clicks on
register
Register in the User
system
Login
Login to the
system
Update profile
Use Case
Register
Response
Destination
Create user
account
Users database
Donor/Hospital/ Login
Volunteer
campaign
Validate login
inputs
User profile
In-need to
update
information
Donor/Hospital/ Update
Volunteer
information
campaign
Update user
information
Users database
Request blood
group
Hospital
requests blood
group
Hospital
Request blood
Send
notification to
donor
Donors
Receive notification
Donors
receive
notifications
View
donation
information
Hospital location
Donor
Send
notification
Create Ad
Volunteer
campaign
clicks the
create ad page
Volunteer
campaign
Create Ad
Fill the create
ad form
Donors
Publish Ad
Volunteer
campaign
clicks publish
Volunteer
campaign
Publish Ad
View ad in
home page
Donors
Emergency form
Hospital fills
Hospital
the emergency
form
–
Send
notification
about request
Donors
Logout
Logout of the
system
Logout
Stop making
changes
Home Page
User
Table 13: Event Table
Page 33
Web Solution of Blood Bank Management
3.4 Software Design Models
3.4.1 Component Diagram
Figure 12: Component Diagram
Page 34
Web Solution of Blood Bank Management
3.4.2 Deployment Diagram
Figure 13: Deployment Diagram
Page 35
Web Solution of Blood Bank Management
Chapter 04: System Implementation
4.1 Software Algorithm
Following diagram is showing the Control Flow Diagram:
Figure 14: Control Flow Diagram
Page 36
Web Solution of Blood Bank Management
4.2 Software Implementation Code
This snippet some from index.php file contains three functions the first one for count how many
donors, hospitals, and volunteer campaigns that registered and it is displayed on the home page. And the
second and third functions for getting hospitals and campaigns and with its markers that put on the map
and display it when selecting a city.
Page 37
Web Solution of Blood Bank Management
This snippet from the login.php file contains code for user login and check if the user entering
the correct username and password that have registered in the database or not.
Page 38
Web Solution of Blood Bank Management
This snippet from the register.php file contains code for registration new user. And check if the
information entering it’s new or already existing in the database.
Page 39
Web Solution of Blood Bank Management
This snippet from the profile.php file contains code that is general for the profile of each user
account. After the user login to the system, the code will check if the user is donor, hospital, volunteer
campaign or admin and then will profile page of user type will open.
This snippet from the logout.php file contains code logged out of users. And after the user logged
out the system will go to the homepage.
Page 40
Web Solution of Blood Bank Management
4.3 Database Design and Implementation
4.3.1 Database Management System
The tool that used with our website it is MySQL from Oracle Corporation with version 8.0.17
and phpMyAdmin
First we connected to the database by using MAMP server, after that we raised our website on
the host. We created the “inc.php” file to connected with all pages that needed the database.
MAMP server interface
Hosting Interface
Page 41
Web Solution of Blood Bank Management
This snippet show how the website connected to the hosting and it’s included to each file that has must
connect to the database.
Page 42
Web Solution of Blood Bank Management
4.3.2 Database Schema
In our database, we have created 10 tables with all the required information, created based on:
Users, Campaign, Requests, Cities, Countries, Suggestion, Request_particiption, Emergency_form,
Campaign_bloodbanks, and Campaign_participation
This table show the relationship between database tables:
FROM
TO
Relationship from
Relationship to
User (Hospital)
Request
One and only one
One or many
User (Volunteer Campaign)
Campaign
One and only one
One or many
User
Cities
One and only one
One and only one
User (Donor)
Campaign
Many
Many
User (Donor)
Request
Many
Many
Campaign
User (Hospital)
Many
Many
User table holds the user login details and profile information, as one and only one to the cities
and countries tables.
The relationship between user with hospital account and request is one and many that because
every hospital can request many blood group.
The relationship between user with donor account and request is many to many, because many
donors can receive many request of donation blood.
The relationship between user with volunteer campaign account and campaign table is one to
many, because every volunteer campaign account can create many campaigns.
So, many hospitals can exist in many campaigns and that relation show in Campaign_bloodbanks
table.
The relationship between user with donor account and campaign is many to many, because many
donors can receive many campaigns ad.
Page 43
Web Solution of Blood Bank Management
Figure 15: Database schema
Page 44
Web Solution of Blood Bank Management
4.3.3 Database Physical Model
Table
Users
Campaign
Requests
Cities
Countries
Entities
Primary key
user_id (int)
Username (var)
Password (var)
Email (var)
Uclass (var)
fullName (var)
Gender (var)
Age (int)
Address (var)
Nationality (var)
National_ID (var)
Phone (var)
BloodGroup (var)
Lat (var)
Lng (var)
Status (var)
ACode (var)
campaign_id (int)
User_id (int)
campaignName (var)
City_id (int)
Address (var)
Time (datatime)
Description (var)
FromDate (date)
ToDate (date)
Image (var)
Lat (var)
Lng (var)
Status (var)
Request_id (int)
User_id (int)
Bloodgroup (var)
Time (timestamp)
Status (var)
City_id (int)
City_name (var)
Lat (var)
Lng (var)
Country_code (var)
Country_enName (var)
Country_arName (var)
Country_enNationality (var)
Country_arNationality (var)
Secondary
Key
Constraints
Primary key, unique
and not null
user_id
City_id
Secondary key,
Not unique and not
null
Primary key, unique
and not null
User_id
First Secondary key is
not unique and not null
campaign_id
City_id
Request_id
User_id
Second Secondary key
is Not unique and not
null
Primary key, unique
and not null
Secondary key is Not
unique and not null
City_id
Primary key, unique
and not null
Country_code
Primary key, unique
and not null
Page 45
Web Solution of Blood Bank Management
Table
Entities
Primary key
Request_particiption
Participation_id (int)
Request_id (int)
User_id (int)
Time (datetime)
Status (var)
Campaign_particiption Participation_id (int)
campaign_id (int)
User_id (int)
Time (datetime)
Status (var)
Campaign_bloodbanks Cd_id (int)
campaign_id (int)
Hospital_id (int)
Status (int)
Emergency_form
Suggestion
Er_id (int)
Name (var)
Email (var)
Phone (var)
BloodGroup (var)
City_id (int)
Status (var)
Suggestion_id (int)
Name (var)
Email (var)
Phone (var)
Suggestion (var)
Secondary
Key
Request_id
Constraints
Primary key, unique
and not null
Participation_id
User_id
campaign_id
Secondary key is not
unique and not null
Primary key, unique
and not null
Participation_id
User_id
campaign_id
Secondary key is not
unique and not null
Primary key, unique
and not null
Cd_id
Hospital_id
Secondary key is not
unique and not null
Er_id
Primary key, unique
and not null
Suggestion_id
Primary key, unique
and not null
Table 14: Database Physical Model
Page 46
Web Solution of Blood Bank Management
4.3.4 Completed Database Screenshots
4.3.4.1 User Table
4.3.4.2 Requests Table
4.3.4.3 Request Participation Table
Page 47
Web Solution of Blood Bank Management
4.3.4.4 Campaign Table
4.3.4.5 Campaign Blood Banks Table
4.3.4.6 Cities Table
Page 48
Web Solution of Blood Bank Management
4.3.4.7 Countries Table
4.3.4.8 Suggestions Table
4.3.4.9 Emergency Form Table
4.3.4.10 Campaign Participation Table
Page 49
Web Solution of Blood Bank Management
4.4 Software Interfaces
4.4.1 Home Page
The homepage provides the navbar that
contains Login, Register, and About Us pages.
The icon on the top right side of the interface
provide the emergency form, that can hospital
make an emergency request of blood. And
statistic section that shows the numbers of a
donor, hospitals and, volunteer campaign that
have an account on the website. Also, on this
page, the donor can find any hospital’s location
by the map. The visitor can share his opinion or
suggestion with us by the form at the end of the
home page.
Page 50
Web Solution of Blood Bank Management
4.4.2 Login Page
Users can fill the form to login to a profile, by entering his user name and password.
4.4.3 Register Page
This page contains the registration form, this form contains three types of accounts: as donor,
hospital, or volunteer campaign. The user can select any type of that and complete the registration.
Page 51
Web Solution of Blood Bank Management
4.4.4 Donor Profile page
This page allows the donors to complete their information and receive all notifications about
request blood or volunteer campaign ads. Also, they can change their password by “Change password”
feature.
Page 52
Web Solution of Blood Bank Management
4.4.5 Hospital Profile Page
This page, showing on top a message that it states that the hospital must complete the required
information until the account is approved to be able to use all the features. After the account approved
the user can request blood type by the “Blood Request” feature on the left side of the page.
Page 53
Web Solution of Blood Bank Management
4.4.6 Volunteer Campaigns Profile Page
This page contains the form about user information and the main feature it’s a create Ad. The
user must complete all the required information about the ad to can publish to the donors. The
“Campaigns List ” contains all campaigns that the user created.
Page 54
Web Solution of Blood Bank Management
4.4.7 Emergency Form
This icon on the top right of the
homepage, when the visitor clicks on
it! will appear a form, this form can
allow visitors entering the required
information to request blood group
without must have an account.
Page 55
Web Solution of Blood Bank Management
4.4.8 Admin Interface
This interface is for administrators of the site, as the first picture shows the login interface of the
administrator by entering the user name and password. The other image shows the administrator control
panel as his familiarity with all the processes that occur from users as well as visitors. The interface
shows the statistics of each type of accounts registered and has two icons representing one of the
suggestions sent and the other for campaigns that require publication.
Page 56
Web Solution of Blood Bank Management
Chapter 05: Software Testing and Evaluation
5.1 Software Testing
5.1.1 User Register
This Test Case will test if the user able to register easily.
Identifier
Priority
Related requirements(s)
TC-1
High
UC-1
Short description
Ability to register new user
Pre-condition(s)
User enter to the website and have the email.
Input data
Filling the form {select account, username, password and email}
Detailed steps
Select an account type then enter the user name, enter password
and confirm password then add email address and press the
Register button.
Expected result(s)
user profile page appears.
Post-condition(s)
Fill the profile form.
Table 15: TC-1
5.1.2 Login
This Test Case will test if the user able to login into the website.
Identifier
Priority
Related requirements(s)
Short description
TC-2
High
UC-2
The user can access the account and ability to login into the
website after entering username and password.
Pre-condition(s)
User open the website and has not logged into the system.
Input data
Username and Password
Detailed steps
Expected result(s)
Post-condition(s)
•
•
•
Click the login page from the navbar
Enter user name and password
Press Login button
User profile page appears and access the system.
User can access to notifications page.
Table 16: TC-2
Page 57
Web Solution of Blood Bank Management
5.1.3 Receive Notifications
This Test Case will test if the user receives the notification from the hospital about donation.
Identifier
Priority
Related requirements(s)
Short description
TC-3
High
UC-6
The user receives notifications through the notifications field in
the profile page or through an e-mail message.
Pre-condition(s)
The user must have an account and complete his information.
Input data
Blood group, Hospital name and date & time.
Detailed steps
Expected result(s)
Post-condition(s)
• Login to the system
• Open profile page
• Click the notifications field
• Show notifications
• Click Accept button
Appearance of the hospital location.
Table 17: TC-3
5.1.4 Request Blood
This Test Case will test if the hospital able to request the blood group.
Identifier
Priority
Related requirements(s)
Short description
Pre-condition(s)
TC-4
High
UC-5
The hospital can request a specific blood type.
The hospital must have an account.
Input data
Select blood group
Detailed steps
Expected result(s)
Post-condition(s)
• Login to the system
• Open profile page
• Click Blood Request field
• Select blood group
• Press submit button
Donors receive the Request.
Table 18: TC-4
Page 58
Web Solution of Blood Bank Management
5.1.5 Create Ad
This Test Case will test if the volunteer campaign can create an ad.
Identifier
Priority
Related requirements(s)
TC-5
High
Short description
Create an advertisement for voluntary blood donation campaigns.
Pre-condition(s)
The voluntary campaigns have account.
Input data
Campaign name, City, Address, Data and Time
• Click Login button in navbar
• Enter Username and Password
• Enter Campaign name, city, the Address, Date and Time
• Press Create Campaign button
• Click Logout Button
The ad was created.
Publish ad through the website.
Detailed steps
Expected result(s)
Post-condition(s)
UC-7
Table 19: TC-5
5.1.6 Publish Ad
This Test Case will test if the volunteer campaign can publish an ad.
Identifier
Priority
Related requirements(s)
TC-6
High
Short description
When volunteer campaign creates ad, and click the button Create
Campaign then the ad will publish.
Pre-condition(s)
Create the ad.
Input data
Click Publish button.
UC-8
Expected result(s)
• Clicking the publish button
• Show ad in the Ads box on the homepage
• Click Logout Button
The Ad will be published.
Post-condition(s)
The donors receive the ad.
Detailed steps
Table 20: TC-6
Page 59
Web Solution of Blood Bank Management
5.1.7 Emergency Form
This Test Case will test if the visitor can request a blood group without register to the website.
Identifier
Priority
Related requirements(s)
TC-7
Medium
SRS Chapter 04 (Design and Implementation Constraints)
Short description
The visitor can Identification of Emergency Blood Donation
Request
Pre-condition(s)
The user most have an emergency blood request.
Input data
Name of hospital, email, phone number, and select blood group.
Detailed steps
Expected result(s)
Post-condition(s)
•
•
•
•
•
Enter the first Name
Enter phone Number
Enter Email
Select blood group
Press submit button
The request will be received by the administrator.
Table 21: TC-7
5.1.8 Logout
This Test Case will test if the user can log out from website.
Identifier
Priority
Related requirements(s)
Short description
Pre-condition(s)
TC-8
High
Input data
Logout button
Detailed steps
UC-11
The user Logs out of the system.
The user must Login.
•
Press the Logout button
Expected result(s)
User logged out from the system.
Post-condition(s)
Return to the Homepage.
Table 22: TC-8
Page 60
Web Solution of Blood Bank Management
5.2 Software Verification
S#
Defect Description
1
The user with volunteer campaigns
Fix Time
Hours Minutes
Origin Stage
Status
Testing
Fixed
1
0
Testing
Fixed
2
0
Testing
Fixed
0
30
account, when he/she clicks the logout
button then the create Ad button doesn’t
disappear from the navbar.
2
The user with a volunteer campaign
account, when he/she select the hospital
field on Create Ad, and clicks add button it
doesn’t work and go direct to the home
page.
3
When the user clicks the submit button on
the register page, then the profile page
doesn’t appear.
Table 23: List of non-trivial defects
Page 61
Web Solution of Blood Bank Management
Chapter 06: Conclusion and Future Work
Redshare has been developed to facilitate blood donation, through its simple and uncomplicated
design that enables tasks to be performed effectively for young and old people, while saving time,
communication speed and easy mobility of users.
Through the site, donors can complete and store their data form so that they can meet critical
blood donation requests faster than ever. As with hospitals can request donors to make an urgent donation
by identifying the desired blood type of the donation and sending the notification via their account on
the site or phone numbers or through their e-mail.
Redshare includes a feature that has never been provided by other sites, which is to enable
volunteer campaigns of blood donation to send their ads to everyone, through the development of an
easy user interface that helps them send ads to the largest number of donors.
Our future plan is to provide and implement new features that enable both donors and blood
banks and volunteer campaigns to quickly implement their requirements, such as the ability of volunteer
campaigns to create their own ads and save them in advance instead of being published immediately,
add an option to donor’s profile that can choose between blood donation or platelet donation, activate
“My Points” feature which promotes and motivates donors to donate blood regularly. Finally, an organ
transplantation center interface will be developed that enables hospitals to request organ donation as
well, not just blood.
Page 62
Web Solution of Blood Bank Management
References
[1] Raghuwanshi.B, Pehlajani.N, & Sinha.M. (2016, October 1). Voluntary Blood Donation among
Students. Retrieved from https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5121683/
[2] Sapkota.A, Poudel.S, Sedhain.A, & Khatiwada.N. (2018, February 12). Blood Transfusion Practice
among
Healthcare
Personnel
in
Nepal.
Retrieved
from
https://www.hindawi.com/journals/jbt/2018/6190859/
[3] Loua.A, Sonoo.J, Musango.L, Nikiema.J.B & Moustapha.T.L. (2017, October 17). Blood Safety
Status
in
WHO
African
Region
Countries.
Retrieved
from
4,
from
https://www.hindawi.com/journals/jbt/2017/1970479/
[4]
Safe
Blood
and
Blood
Products.
(n.d.).
Retrieved
March
2018,
https://www.who.int/bloodsafety/transfusion_services/Module1.pdf
[5] Blood Banking and Transfusion Medicine. (n.d.). Retrieved March 4, 2018, from
https://www.pdfdrive.com/blood-banking-and-transfusion-medicine-e53322780.html
[6]
Essentials
of
Blood
Banking.
(2013).
Retrieved
March
4,
2018,
from

[7] Blood Safety Information System (BSIS). (2019). Retrieved March 4, 2018, from
https://www.jembi.org/project/blood-safety-information-system/
[8] Blood Bank India. (2017). Retrieved March 4, 2018, from https://www.bloodbankindia.net/
[9] eBloodBank. (2019). Retrieved March 4, 2018, from http://ebloodbank.rexbd.net/
[10] NHS Blood Donation.(n.d). Retrieved March 4, 2018, from https://www.blood.co.uk/
[11] oneBlood. (2019). Retrieved March 4, 2018, from https://www.oneblood.org/
[12]
American
Red
Cross
Blood
Services.
(2019).
Retrieved
March
4,
2018,
from
https://www.redcrossblood.org/
[13] K M Akkas Ali, Israt Jahan, Md. Ariful Islam, Md. Shafa-at Parvez, Blood Donation Management
System, Volume-4, Issue-6, pp-123-136- 2015.
[14] San San Tint and Htoi Mai, BLOOD DONATION SYSTEM FOR ONLINE USERS, Computer
Applications: An International Journal (CAIJ), Vol.2, No.1, February 2015.
Page 63
Web Solution of Blood Bank Management
[15] Aware Sachin B, Arshad Rashid, Ansari aadil, Bombale R.R, Web Based Blood Donation System,
International Journal of Scientific and Research Publications, Volume 4, Issue 12, December 2014.
[16] PRATHAMESH RAUT, PRACHI PARAB, YOGESH SUTHAR, SUMEET NARWANI,
SANJAY PANDEY. BLOOD BANK MANAGEMENT SYSTEM. International Journal of Advanced
Computational Engineering and Networking, ISSN: 2320-2106,
[17] JavedAkhtar Khan and M.R. Alony, “A New Concept of Blood Bank Management System using
Cloud Computing for Rural Area (INDIA)”, TIT Group of Institute of Engineering, Bhagwant University
Ajmer, (RJ) INDIA, International Journal of Electrical, Electronics
[18] Aishwarya Shinde, Advait Gharat, Varad Sakhalkar, Rajendra Chapke. RedDonate A Blood Bank
Android Application. Computer Engineering,Universal College Of Engineering,Kaman, Vasai
[19] ShyamSundaram,Santhanam , “Real-Time Blood Donor Management Using Dashboards Based on
Data Mining Models”, Dept. of Computer Science, DG Vaishnav College Chennai 600106, Tamil
Nadu,India.
[20] Sultan Turhan , “An Android Application for Volunteer Blood Donors”, Department of Computer
Engineering, GalatasarayUniversity, Instanbul, TURKEY,url:sturhan@gsu.edu.tr
[21] A. ClemenTeena, K. Sankar and S. Kannan, “A Study on Blood Bank Management”, Department
of MCA, Bharath University, Selaiyur, Chennai-73, Tamil Nadu, India, Middle-East Journal of
Scientific
Research
19
(8):
1123-
1126,
2014
,ISSN
1990-9233,DOI:
10.5829/idosi.mejsr.2014.19.8.11202
[22] Sumazly Sulaiman, abdul aziz k abdul hamid, Nurul Ain Najihah Yusri. Development of a Blood
Bank Management System. Procedia – Social and Behavioral Sciences 195:2008-2013 · July 2015.
[23] Ravi kumar, Shubham Singh, V Anu Ragavi. Blood Bank Management System. IJARIIE-ISSN(O)2395-4396 Vol-3 Issue-5 2017
[24] Vikas Kulshreshtha, Dr. Sharad Maheshwari. Benefits of Management Information System in Blood
Bank. International Journal of Engineering And Science ISSN: 2278-4721, Vol. 1, Issue 12(December
2012), PP 05-07 Www.Researchinventy.Com
Page 64
Web Solution of Blood Bank Management
[25] ClemenTeena, K. Sankar and S. Kannan. A Study on Blood Bank Management System. Department
of MCA, Bharath University, Selaiyur, Chennai-73, Tamil Nadu, India
[26] Almutairi.M, Alrasheed.R, Aldayle.H. (2018). AlBurhan Academy.
Page 65
Web Solution of Blood Bank Management
Appendix: Glossary
•
Donor: The person who gives blood to the patient.
•
Patient: who need a blood.
•
Blood Bank: The place where the donors receive.
•
SMS: Short Messages Service
•
RedShare: A server that provides health services.
•
Android: Operating system for mobile devices.
•
Mac: Is an operating system for computers.
•
Windows: Is an operating system for computers.
•
ADM / PDM: Diagrams used to determine the path of activity in the project.
•
Gantt Chart: a chart that represents the project plan path.
•
GPS: Global Positioning System.
•
PHP: Hypertext Preprocessor – A server-side scripting language used to develop websites.
•
HTML: HyperText Markup Language – A markup language used to create and design websites.
•
SQL: Structured Query Language – A programming language that stores, manipulates and fetches
data from a database.
•
24/7: 24 hours a day, seven days a week.
•
ID: Identification.
•
Usability: The term refers to the ease of dealing and access to the site.
Page 66
Web Solution of Blood Bank Management
•
User: the person who use a computer or network service.
Page 67