Final BDS

Blood Donation System
ONLINE BLOOD DONATION SYSTEM
Project Advisor: Muhammad Asif
Submitted By
Bilawal Naseeb (152151011)

Bilal Ahmed (152151012)
Muhammad Shahid (152151013)
Falik Sher (152151014)
Muhammad Islahuddin (152151015)
Department of Computer Science,

National College of Business Administration & Economics
(ECC) Lahore.
BS Computer Science (2012-2016)
National College of Business Administration & Economics (ECC)

STATEMENT OF SUBMISSION
This is to certify that Bilawal Naseeb Roll No. 152151011, Bilal Ahmed Roll No.
152151012, Muhammad Shahid Roll No. 152151013, Falik Sher Roll No. 152151014
and Muhammad Islahuddin Roll No. 15215015 have successfully completed the final
project named as: Blood Donation System, at the National College Of Business
Administration & Economics ECC Lahore to fulfill the partial requirement of the degree
of BS Computer Science (Hons.).
__________________ ___________________
Project Advisor Project Examiner
Name: Muhammad Asif Name:
Designation: Lecturer Designating:
National College of Business

Administration Economics ECC
Lahore.

PROOFREADING CERTIFICATE
It is to certify that I have read the document meticulously and circumspectly. I am
convinced that the resultant project does not contain any spelling, punctuation or
grammatical mistakes as such. All in all I find this document well organized and I am in
no doubt that its objectives have been successfully met.
_____________________
Mr.
Business Communication and Technical Writing,
Lecturer, NCBA& ECC.

ACKNOWLEDGEMENT
We truly acknowledge the cooperation and help make by Mr. Shahbaz Younus, Head
of Computer-Science Department at National College of Business Administration &
Economics ECC Lahore. He has been a constant source of guidance throughout the
course of this project. We would also like to thank Mr. Muhammad Asif, Lecturer
Computer Science at National College of Business Administration & Economics
ECC Lahore. For his help and guidance throughout this project. He has been a source of
motivation for me throughout in compilation of this project. We are also thankful to all
our teachers for building our concepts comprehensible and clear. I pay special thanks to
other officials of the university for their great support during my final year project. At the
end we would like to thank all those who have helped us during this research work.
1. Bilawal Naseeb
2. Muhammad Shahid
3. Bilal Ahmed
4. Muhammad Islahuddin
5. Falik Sher
Date:

ABSTRACT
Now days, it is often seemed difficult for people to find a blood donor as most of the
people doesn’t know from where to get while others have not enough time to approach
any hospital or blood banks. So we have come up with a solution for such problems in a
form of a web based application. By using this application, any person can find donor
without stepping out of home. This is the modern, advanced and trusted solution to find
the needed blood easily.

Table of Contents
STATEMENT OF SUBMISSION…………………...……………………………….I
ACKNOWLEDGEMENT………………………….…………………………………III
ABSTRACT……………………………………………………………………………IV
Chapter No.1
PROJECT OVERVIEW…………………………………………………………………. .... 1
1.1 Projectoverview……………………………………………………....………...2
1.2 Problem Definition…………………………………………………….……….2

1.3 Advantages………………….…………….........................................................3
1.4 Disadvantages…………………………………………………………….……3
Chapter No.2
PROJECT DESCRIPTION……………………………………………………………..4
2.1 Project Title…………………………..…………………………………...…..5
2.2 Project Area......................................................................................................5
2.3 Project Correlation with industry………………..…..…………………….....5
2.4 Industrial Influence.…………..………………..…………………………….5
2.5 Processes with Phases………………………..……………………………....6
2.6 System Basis…………………………..……..………………………………7
Chapter No.3
SYSTEM ANALYSIS……………………………………………………………………8
3.1 Purpose Of SRS……………………………………………………………….9
3.2 Scope……………………………………………………………….………....9
3.3 Definition ,Acronyms & Abbreviations………………………………………9
3.4 Overview of remaining SRS...……………………….……………………….9

Chapter No.4
OVERALL DESCRIPTION ................................................................................................. 10
4.1 Overall Description……………………………………………..……………11
4.1 Product Perspective………………………………….…………..…………...11

4.2 Memory………………………………………………..………….……….....11
4.3 Site Adaption Requirement…………………………….…………….……....11
4.4 Product Functions……………………………………………………………12
4.5 User Characteristics…………………………………………………....…….12
4.6 Constraints……………………………………………….…………………..12
4.7 Assumptions and Dependencies………………………….………………….13
Chapter No.5
DEVELOPMENT OF PROJECT………………….…………………..…...…..………….14
5.1 Testing Methodology…………………………………….………………….15

5.1.1 Testing Objectives……………..……………………….………………….15
5.1.2 Strategic Approach To Software Testing.……………………….………...16
5.1.3. Unit Testing:………………………………………………..…….……….17

5.1.4 Integration Testing………………………..………….…………………….18
5.1.5 Validation Testing………………………………………………………….18

5.1.5.1 Merits…..…………………………………………………………………19
5.1.6 Objective……………………………………………………………………19

Chapter No.6
SPECIFIC REQUIREMENT……………………………………………………….20
6.1 Security and Protocol Architecture…………………………………….….21
6.2 External Interphases…………….……….………………………………...21
6.3 Performance Requirement…….……….……………………………….....21
6.4 Hardware Requirements……………..……………………………………21
6.5 Software Requirements…………….…..………………………………….22
Chapter No.7
TECHNICAL SPECIFICATIONS…………………………………………..……….23
7.1 Java Language………………………………………………………… ... 24
7.2 MySQL..............................................................................................… …. 29
7.3 JQuery………………………………………………………………… ..... 31
7.4 JQuery UI ………………………………………………………… ….….. 32
7.5 JQXWidgets ……………………………………………………...… …… 32
7.5 JSP…………………………………………………………………… ……32
Chapter No.8
SOFTWARE DEVELOPMENT TOOLS……………….……………………..……..37
Chapter No.9
USE CASE DIAGRAM...……..…………………………………………………….….42
Chapter No.10
SEQUENCE DIAGRAMS …..………………………………………………..……….44

Chapter No.11
USE-CASE DESCRIPTION…………………………………………………..……….50
Chapter No.12
ERD DIAGRAM……………………………………………………………….……….56
Chapter No.13
SCREENSHOTS……………...……………………………….……………….……….58
Chapter No.14
TEAM MEMBER………………..…………………………………………….……….64
Chapter No.15
REFERENCES…………….……….…………………………………………..……….68

Chapter No.1
PROJECT OVERVIEW
1|Page
1 Project Overview:
1.1 Overview:
Donate Today, You Never Know When you need it!
Basically our mission is to improve the lives of Pakistani through the power of humanity,
Every Pakistani Must Know His/her Free Blood Group. We introduce the new vision of
Blood Donors. Back with a desire of no one going through the pain of watching
helplessly when their loved ones are suffering and do not get aid in time. Thus Blood
Donors was born with a Mission to help those who would be in dire need of blood, since
our inception thousands of people have come forward as potential donors and enrolled in
our database from all Over Pakistan, some of them even from the Middle East. Through
this application any person who is interested in donating the blood can register Himself in
the same way if any organization wants to register itself with this site that can also
register. Moreover if any general consumer wants to make request blood online He can
also take the help of this site. Admin is the main authority who can do addition, Deletion,
and modification if required. We are now focusing on our campaign to eradicate
Thalassemia from Pakistan by the Year 2017. Insha’Allah (Allah Willing).
1.2 Problem Definition:

Existing System:
 Cannot Upload and Download the latest updates.
 No use of Web Services and Remoting.
 Risk of mismanagement and of data when the project is under development.
 Less Security.
 No proper coordination between different Applications and Users.
 Fewer Users – Friendly
2|Page
1.3 Advantages:
These are some following advantages:
 Less time consumption.
 The main objective of the project is to design and develop a user friendly system
which is easy to use, efficient system and reliable for mobile user.
 To allow the recipients to make search and match the volunteer donors, and make
request for the blood.
 For children suffering from ailments like Thalassemia, Hemophilia. For major &
minor surgeries including open heart surgeries, transplants etc.
For the cure of patients suffering from Anemia.
1.4 Disadvantages:
 User friendliness is provided in the application with various controls.
 The system makes the overall project management much easier and flexible.
 Readily upload the latest updates, allows user to download the alerts by clicking
the URL.
 There is no risk of data mismanagement at any level while the project
development is under process.
 It provides high level of security with different level of authentication.
3|Page
Chapter No.2
PROJECT DESCRIPTION
4|Page
2. PROJECT DESCRIPTION:
2.1. Project Title:
“BLOOD DONATION SYSTEM”
2.2. Project Area:

This web based application will be developed using the most powerful framework that is,
Spring MVC 4.1.6 and MYSQL Server for the database. This application to be handled
smoothly. Also it is compatible with all web browsers. Another top of the top
functionality is that our web based application can also be accessed by smart phones and
tabs. This is the height of comfort and accessibility.
2.3. Project Correlation with industry:

The Scope of IT is popular and vast today and is being implemented in almost all aspects
and fields of life. The IT industry has introduced many solutions regarding all areas of
concern and made all the time consuming tasks performed in seconds, just a few clicks
away. So, the main achievement is the saving of time and modernization of the blood
banks problem solving trends. This project is one of such innovations. It will help the
industry to facilitate people in real life blood needier at their homes.
2.4. Industrial Influence:

The quality and popularity of software reaches extent when it becomes more versatile.
The ideal application is that which can be accessed on multiple platforms and can be used
in various blood fields. The industries can manage the blood banks, their availability ratio
and the user’s reviews about them. So these are the factors for the industrial progression.
5|Page
2.5. Processes with phases:

This Blood Donor is based on physical activity of the people.
2.5.1. Phases:
st
 1 phase:
In the first phase find a blood donor.
1-Select City
2-Blood Group
nd
 2 phase:
In the Second phase if donor wants to donate a blood then click on.
 Donor Register.
 Donate Blood.
 Donor Login.
 3rd phase:
In this phase donor can also change profile and password check
Requests.
6|Page
th
 4 phase:
In this phase the Donor gets a blood request notification on
mobile too.
th
 5 Phase:
In this phase donor check his Request alerts on his emails
like yahoo, Gmail etc.
2.6. System Basis:

 Hp Laptops
 Apple Laptops
 Dell Laptops
 Also Tabs and Cell phones
7|Page
Chapter No.3
System Analysis
8|Page
3. System Analysis
3.1. Purpose of SRS:
The purpose of this document is to provide a consistent and complete description of
the requirement of the project that is
“BLOOD DONATION SYSTEM”
The purpose of SRS (Software Requirements Specification) to Help people find blood
donors with the matching blood group in the nearest area as the donors do not know
where the blood is required urgently.
3.2. Scope:
The specification builds on the experience of users of IT technology in blood donation
that is currently available and informs both Connecting for Health (CFH) and commercial
companies producing software. Moreover this application is efficient for any laptops, cell
phones or tabs either which is of low price.
3.3. Definitions, Acronyms & Abbreviations:
FAQ: Frequently Asked Questions
3.4. Overview of Remaining SRS:

The rest of SRS document contains all the requirements for the game named
“BLOOD DONATION SYSTEM“ The next section consists of the overall
Description of the project and things associate with it and all the operation that are going
to perform in the Blood Bank. This part will consist of textual and diagrams to get this
application more clear. The last section will represent the specific requirement of our
system. This is the most important section of SRS document, as it will hold the
functioning requirement of Online Blood Bank, data model and external interface.
9|Page
Chapter No.4
OVERALL DESCRIPTION
10 | P a g e
4. Overall Description:
Today we have many blood management systems in market than we had in past which
serve the main purpose of having an automated system. Though many of them have been
automated and functionality but they are hardly updated to modern needs.
4.1 Product Perspective:

Online blood gift framework is chiefly towards persons who are willing to give blood to the patients.
Through this framework it will be less demanding to discover a benefactor for careful blood classification
and simple to construct the association between contributor and the patients. The principle expect of
building this product is to formal the strategy of blood gift and rouse benefactors so as to gift blood.
4.2. Memory:
Hardware and software requirements for system.
Processor 2.5 GHz, Ram 512MB and hard disc for storage 40GB.
4.3. Site Adaptation Requirement:

A system based on voluntary unpaid blood donation, particularly regular. Learn about the
eligibility requirements for blood donor including age restrictions, medication restrictions
health requirements and more. Simply as ideas for consideration and adaptation to the
requirements. Internet access is required.
11 | P a g e
4.4. Product Functions:
Following are the functions of this game:
1. Donor Registration
2. Donor Login
3. Blood Request
4. Search Blood
5. Blood Request Alerts
4.5. User Characteristics:
 Admin can access to login form, Send Alerts, Add City, Add Blood Group.
 Acceptor or Blood needed can access to Search Blood and Send Request for
blood Donor.
 Donor can access to Login and Registration form, Search Blood,
 Edit account and Logout.
4.6. Constraints:
The donor who uses internet connection will be guided through small & clear descriptions. Every donor
may get a user name /Contact Number & a password in order to log into the system. After the registration
of a donor the program will authenticate the accuracy of the donor’s mobile number through counting
the number of characters in the entered mobile number System.
12 | P a g e
4.7. Assumptions and Dependencies:
Users are assuming that the Application is run on the small phones. But this application is
run on smart phones, Tabs, Laptops etc either than small Phones.
13 | P a g e
Chapter No.5
DEVELOPMENT OF PROJECT
14 | P a g e
5. Testing Methodologies
5.1. Testing Introduction:

Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and coding. In fact, testing is the one step in the
software engineering process that could be viewed as destructive rather than constructive.
A strategy for software testing integrates software test case design methods into a well-
planned series of steps that result in the successful construction of software. Testing is the
set of activities that can be planned in advance and conducted systematically. The
underlying motivation of program testing is to affirm software quality with methods that
can economically and effectively apply to both strategic to both large and small-scale
systems.
5.1.1. Testing Objective:

The Key to determining the objectives of a performance-testing effort is to identify
change, potential risks and opportunities for improvement. One way to determine and
record performance-testing objectives is simply to ask each member of the project team
what value you can add or risk you can mitigate for him or her while you are conducting
performance testing at a particular point in the project or immediately following the
accomplishment of a particular milestone.
The primary purpose of the Test Phase is to determine whether the automated system/
application software or other IT solution developed or acquired and preliminarily tested
during the Development Phase is ready for implementation. During the Test Phase,
formally controlled and focused testing is performed to uncover errors and bugs in the IT
solution that need to be resolved. There are a number of specific, validation tests that are
performed during the Test Phase (e.g. requirements validation, system and user
acceptance). Additional tests may be conducted to validate documentation, training,
15 | P a g e
contingency plans, disaster recovery, and installation depending upon the specific
circumstances of the project. The Test Phase ends with a review to determine readiness to
proceed to the implementation phase.
5.1.2. STRATEGIC APPROACH TO SOFTWARE TESTING:

The software engineering process can be viewed as a spiral. Initially system engineering
defines the role of software and leads to software requirement analysis where the
information domain, functions, behavior, performance, constraints and validation criteria
for software are established. Moving inward along the spiral, we come to design and
finally to coding. To develop computer software we spiral in along streamlines that
decrease the level of abstraction on each turn.
UNIT TESTING
MODULE TESTING
Component Testing
SUB-SYSTEM TESING
SYSTEM TESTING
Integration Testing
ACCEPTANCE TESTING
User Testing
16 | P a g e
5.1.3. Unit Testing:
Module Testing or unit testing is a process of testing the individual subprograms,

subroutines, or procedures in a program. That is rather than initially testing the program
as a whole, testing is first focused on the smaller building blocks of the program.
First, module testing is a way of managing the combinatory of testing, since attention is
focused initially on smaller units of the program. Second, module testing eases the task of
debugging (the process of pinpointing and correcting a discovered error), since, when an
error is found, it is known to exist in a particular module. Finally, module testing
introduces parallelism into the testing process by presenting us with the opportunity to
test multiple modules simultaneously.
1. WHITE BOX TESTING

This type of testing ensures that
 All independent paths have been exercised at least once
 All logical decisions have been exercised on their true and false sides
 All loops are executed at their boundaries and within their operational bounds
 All internal data structures have been exercised to assure their validity.
To follow the concept of white box testing we have tested each form .we have created
independently to verify that Data flow is correct, All conditions are exercised to check
their validity, All loops are executed on their boundaries.
2. CONDITIONAL TESTING
In this part of the testing each of the conditions were tested to both true and false aspects.
And all the resulting paths were tested. So that each path that may be generate on
particular condition is traced to uncover any possible errors.
17 | P a g e
3. DATA FLOW TESTING

This type of testing selects the path of the program according to the location of
definition and use of variables. This kind of testing was used only when some local
variable were declared. The definition-use chain method was used in this type of testing.
These were particularly useful in nested statements.
4. LOOP TESTING
In this type of testing all the loops are tested to all the limits possible. The following
exercise was adopted for all loops:
 All the loops were tested at their limits, just above them and just below them.
 All the loops were skipped at least once.
 For nested loops test the inner most loop first and then work outwards.
 For concatenated loops the values of dependent loops were set with the help of
connected loop.
 Unstructured loops were resolved into nested loops or concatenated loops and tested
as above.
Each unit has been separately tested by the development team itself and all the input
have been validated.
5.1.4. Integration Testing:

Testing combinations of pieces of the product is called integration testing. The primary
objective of integration testing is to discover errors in the interfaces between the
components.
5.1.5. Validation Testing:

The aim of software testing is to measure the quality of software in terms of number of
defects found in it, the number of tests run, and the system covered by the tests. When
bugs or defects are found with the help of testing, the bugs are logged and the
18 | P a g e
development team fixes them. Once the bugs are fixed, testing is carried out again to
ensure that they are indeed fixed and no new defects have been introduced in the
software. With the entire cycle, the quality of the software increases.
The process of evaluating software during or at the end of the development process to
determine whether it satisfies specified business requirements.
5.1.5.1. Merits:
 By unit testing we are checking initial stability and functionality for the provided
module.
 Before integrating particular module to the daily build, Testers understand its
function and its importance as a part of visual plant.
 It’s useful to cover more test cases by knowing its effect on other module as well
as overall system.
5.1.6. Objective:
The objective of validation testing is to ensure that the product actually meets the user’s
needs and that the specifications were correct in the first place. In other words, to
demonstrate that the product will fulfills its intended use when placed in its intended
environment.
19 | P a g e
Chapter No.6
SPECIFICATIONS AND REQUIREMENT
20 | P a g e
6. Specification and Requirement:
6.1.1. Security and Protocol Architecture:
This application is more secure for users. The use of Java makes our product meet the
highly security measures. The product is developed considering all the vulnerability aspects
of web applications such as cross site scripting, SQL injection, denial of service, remote file
inclusion and buffer overflow etc. This makes our product highly secured.
6.2. External Interfaces:
In this application the Eclipse Neon tool is used. MVC framework is used for the
notifications.
6.3. Performance Requirement:
Our major purpose is to provide facilities to peoples who find the better way of blood
donors. At a time multiple users access it.
6.4 HARDWARE REQUIREMENTS:
 CPU P IV 2.8 GHz Processor and Above

 Memory RAM 512MB and Above
 Storage HDD 20 GB Hard Disk Space and Above
21 | P a g e
6.5 SOFTWARE REQUIREMENTS:
Operating System Windows, Linux, MacOS, UNIX

Technologies JAVA
Web Technologies HTML, CSS, JavaScript, JQX Widget
Web Framework JQuery, JQuery UI, Spring MVC 4.1.6
IDE Eclipse Neon
Web Server Xammp/JBoss Wildfly
Database MySQL
Web Browser Internet Explorer, Chrome, Mozilla Firefox
22 | P a g e
Chapter 7
TECHNICAL SPECIFICATIONS
23 | P a g e
7. JAVA LANGUAGE:
What Is Java?
Java is an object-oriented programming language developed by Sun Microsystems, a
company best known for its high-end UNIX workstations. Modeled after C++, the Java
language was designed to be small, simple, and portable across platforms and operating
systems, both at the source and at the binary level (more about this later).
Java is often mentioned in the same breath as HotJava. What makes HotJava different
from most other browsers is that, in addition to all its basic Web features, it can also
download and play applets on the reader’s system. Applets appear in a Web page much in
the same way as images do, but unlike images, applets are dynamic and interactive.
Applets can be used to create animations, figures, or areas that can respond to input from
the reader, games, or other interactive effects on the same Web pages among the text and
graphics.
Java Applets:
Although HotJava was the first World Wide Web browser to be able to play Java applets,
Java support is rapidly becoming available in other browsers. Netscape 2.0 provides
support for Java applets, and other browser developers have also announced support for
Java in forthcoming products.
Create an applet, you write it in the Java language, compile it using a Java compiler, and
refer to that applet in your HTML Web pages. You put the resulting HTML and Java files
on a Web site much in the same way that you make ordinary HTML and image files
available. Then, when someone using the HotJava browser (or other Java-aware browser)
views your page with the embedded applet, that browser downloads the applet to the
local system and executes it, and then the reader can view and interact with your applet in
all its glory (readers using other browsers won’t see anything).The important thing to
understand about Java is that you can do so much more with it besides create applets.
Java was written as a full-fledged programming language in which you can accomplish
the same sorts of tasks and solve the same sorts of problems that you can in other
24 | P a g e
programming languages, such as C or C++. HotJava itself, including all the networking,
display, and user interface elements, is written in Java.
Java’s Past, Present, and Future:

The Java language was developed at Sun Microsystems in 1991 as part of a research
project to develop software for consumer electronics devices—television sets, VCRs,
toasters, and the other sorts of machines you can buy at any department store. Java’s
goals at that time were to be small, fast, efficient, and easily portable to a wide range of
hardware devices. It is those same goals that made Java an ideal language for distributing
executable programs via the World Wide Web (WWW), and also a general-purpose
programming language for developing programs that are easily usable and portable
across different platforms.
The Java language was used in several projects within Sun, but did not get very much
commercial attention until it was paired with HotJava. HotJava was written in 1994 in a
matter of months, both as a vehicle for downloading and running applets and also as an
example of the sort of complex application that can be written in Java.
At the time Sun has released the beta version of the Java Developer’s Kit (JDK), which
includes tools for developing Java applets and applications on Sun systems running
Solaris 2.3 or higher for Windows NT and for Windows 95. By the time you read this,
support for Java development may have appeared on other platforms, either from Sun or
from third-party companies.
Note that because the JDK is currently in beta, it is still subject to change between now
and when it is officially released. Applets and applications you write using the JDK and
using the examples in this book may require some changes to work with future versions
of the JDK. However, because the Java language has been around for several years and
has been used for several projects, the language itself is quite stable and robust and most
likely will not change excessively. Keep this beta status in mind as you read through this
book and as you develop your own Java programs.
25 | P a g e
Support for playing Java programs is a little more confusing at the moment. Sun’s
HotJava is not currently included with the Beta JDK; the only available version of
HotJava is an older alpha version, and, tragically, applets written for the alpha version of
Java do not work with the beta JDK, and vice versa. By the time you read this, Sun may
have released a newer version of HotJava which will enable you to view applets.
The JDK does include an application called applet viewer that allows you to test your
Java applets as you write them. If an applet works in the applet viewer, it should work
with any Java-capable browser. You’ll learn more about applet viewer later today.
What’s in store for the future?

In addition to the final Java release from Sun, other companies have announced support
for Java in their own World Wide Web browsers. Netscape Communications Corporation
has already incorporated Java capabilities into the 2.0 version of their very popular
Netscape Navigator Web browser—pages with embedded Java applets can be viewed and
played with Netscape. With support for Java available in as popular a browser as
Netscape,
Tools to help develop Java applications (debuggers, development environments, and so
on) most likely will be rapidly available as well.
Why Learn Java? At the moment, probably the most compelling reason to learn Java—
and probably the reason you bought this book—is that HotJava applets are written in
Java. Even if that were not the case, Java as a language has significant advantages over
other languages and other programming environments that make it suitable for just about
any programming task. This section describes some of those advantages.
Platform-Independent:
Java Is Platform-Independent Platform independence is one of the most significant
advantages that Java has over other programming languages, particularly for systems that
need to work on many different platforms. Java is platform-independent at both the
source and the binary level.
26 | P a g e
Platform-independence is a program’s capability of moving easily from one computer

system to another.
At the source level, Java’s primitive data types have consistent sizes across all
development platforms. Java’s foundation class libraries make it easy to write code that
can be moved from platform to platform without the need to rewrite it to work with that
platform. Platform-independence doesn’t stop at the source level, however. Java binary
files are also platform-independent and can run on multiple problems without the need to
recompile the source. How does this work? Java binary files are actually in a form called
byte codes. Byte codes are a set of instructions that looks a lot like some machine codes,
but that is not specific to any one processor.
Normally, when you compile a program written in C or in most other languages, the
compiler translates your program into machine codes or processor instructions. Those
instructions are specific to the processor your computer is running—so, for example, if
you compile your code on a Pentium system, the resulting program will run only on other
Pentium systems. If you want to use the same program on another system, you have to go
back to your original source, get a compiler for that system, and recompile your code.
Things are different when you write code in Java. The Java development environment has
two parts: a Java compiler and a Java interpreter. The Java compiler takes your Java
program and instead of generating machine codes from your source files, it generates
byte codes.
Java byte code:

To run a Java program, you run a program called a byte code interpreter, which in turn
executes your Java program. You can either run the interpreter by itself, or—for
applets— there is a byte code interpreter built into HotJava and other Java-capable
browsers that runs the applet for you.
Why go through all the trouble of adding this extra layer of the byte code interpreter?
Having your Java programs in byte code form means that instead of being specific to any
27 | P a g e
one system, your programs can be run on any platform and any operating or window
system as long as the Java interpreter is available.
This capability of a single binary file to be executable across platforms is crucial to what
enables applets to work, because the World Wide Web itself is also platform
independent. Just as HTML files can be read on any platform, so applets can be executed
on any platform that is a Java-capable browser.
The disadvantage of using byte codes is in execution speed. Because system-specific
programs run directly on the hardware for which they are compiled, they run significantly
faster than Java byte codes, which must be processed by the interpreter. For many Java
programs, the speed may not be an issue. If you write programs that require more
execution speed than the Java interpreter can provide, you have several solutions
available to you, including being able to link native code into your Java program or using
tools to convert your Java byte codes into native code. Note that by using any of these
solutions, you lose the portability that Java byte codes provide. You’ll learn about each of
these mechanisms on Day 20.
Object-Oriented:
Java Is Object-Oriented To some, object-oriented programming (OOP) technique is
merely a way of organizing programs, and it can be accomplished using any language.
Working with a real object-oriented language and programming environment, however,
enables you to take full advantage of object-oriented methodology and its capabilities of
creating flexible, modular programs and reusing code.
Many of Java’s object-oriented concepts are inherited from C++, the language on which
it is based, but it borrows many concepts from other object-oriented languages as well.
Like most object-oriented programming languages, Java includes a set of class libraries
that provide basic data types, system input and output capabilities, and other utility
functions.
28 | P a g e
7.2 MySQL
What is MySQL?
MySQL, the most popular Open Source SQL database management system, is developed,
distributed, and supported by Oracle Corporation. MySQL offers great reliability and ease
of use. It is free, and comes with free documentation as well as thousands of programmers
that share their code that relates to communicating with a MySQL database.
MySQL software is Open Source:

Open Source means that it is possible for anyone to use and modify the software.
Anybody can download the MySQL software from the Internet and use it without paying
anything. If you wish, you may study the source code and change it to suit your needs.
The MySQL Database Server is very fast, reliable, scalable, and easy to use.
MySQL Server can run comfortably on a desktop or laptop, alongside your other
applications, web servers, and so on, requiring little or no attention. If you dedicate an
entire machine to MySQL, you can adjust the settings to take advantage of all the
memory, CPU power, and I/O capacity available. MySQL can also scale up to clusters of
machines, networked together.
MySQL Server was originally developed to handle large databases much faster than
existing solutions and has been successfully used in highly demanding production
environments for several years. Although under constant development, MySQL Server
today offers a rich and useful set of functions. Its connectivity, speed, and security make
MySQL Server highly suited for accessing databases on the Internet.
MySQL Server works in client/server or embedded systems.

The MySQL Database Software is a client/server system that consists of a multi-threaded
SQL server that supports different backbend’s, several different client programs and
libraries, administrative tools, and a wide range of application programming interfaces
(APIs).
29 | P a g e
We also provide MySQL Server as an embedded multi-threaded library that you can link
into your application to get a smaller, faster, easier-to-manage standalone product.
MySQL Server has a practical set of features developed in close cooperation with our
users. It is very likely that your favorite application or language supports the MySQL
Database Server.
The official way to pronounce “MySQL” is “My Ess Que Ell” (not “my sequel”), but we
do not mind if you pronounce it as “my sequel” or in some other localized way.
MySQL databases as a relational:

A relational database stores data in separate tables rather than putting all the data in one
big storeroom. The database structures are organized into physical files optimized for
speed. The logical model, with objects such as databases, tables, views, rows, and
columns, offers a flexible programming environment.
You set up rules governing the relationships between different data fields, such as one-to-
one, one-to-many, unique, required or optional, and “pointers” between different tables.
The database enforces these rules, so that with a well-designed database, your application
never sees inconsistent, duplicate, orphan, out-of-date, or missing data.
The SQL part of “MySQL” stands for “Structured Query Language”. SQL is the most
common standardized language used to access databases. Depending on your
programming environment, you might enter SQL directly (for example, to generate
reports), embed SQL statements into code written in another language, or use a language-
specific API that hides the SQL syntax.
SQL is defined by the ANSI/ISO SQL Standard. The SQL standard has been evolving
since 1986 and several versions exist. In this manual, “SQL-92” refers to the standard
released in 1992, “SQL: 1999” refers to the standard released in 1999, and “SQL: 2003”
refers to the current version of the standard. We use the phrase “the SQL standard” to
mean the current version of the SQL Standard at any time.
30 | P a g e
7.3 jQuery
JQuery is a cross-platform JavaScript library designed to simplify the client-side
scripting of HTML... Used by over 60% of the 10,000 most visited websites, jQuery is
the most popular JavaScript library in use today. JQuery is free, open source software,
licensed under the MIT License.
JQuery’s syntax is designed to make it easier to navigate a document, select DOM
elements, create animations, handle events, and develop Ajax applications. JQuery also
provides capabilities for developers to create plug-ins on top of the JavaScript library.
This enables developers to create abstractions for low-level interaction and animation,
advanced effects and high-level, theme-able widgets. The modular approach to the
jQuery library allows the creation of powerful dynamic web pages and web applications.
The advantages of using jQuery are:

Separates JavaScript and HTML:
Instead of using HTML attributes to call JavaScript functions for event handling, jQuery
allows all event-handling functions to be done purely in JavaScript. Thus, the HTML tags
And JavaScript can be completely separated.
Brevity and Clarity:
JQuery provides various syntaxes that promotes brevity and clarity, e.g. chaining effects
and actions, shorthand methods.
Eliminates cross-browser incompatibilities:
The JavaScript engines of different browsers differ slightly, so JavaScript code that
works for one browser may not work on the other. JQuery handles all these cross-browser
inconsistencies and provides a consistent interface that works across different browsers.
31 | P a g e
7.4 JQuery UI
JQuery UI is a curated set of user interface interactions, effects, widgets, and themes
built on top of the jQuery JavaScript Library. Whether you're building highly interactive
web applications or you just need to add a date picker to a form control, jQuery UI is the
perfect choice. JQuery UI provides abstractions for low-level interaction and animation,
advanced effects and high-level, theme able widgets,
7.5 jQxWidgets
JQXWidgets provides a comprehensive solution for building professional web sites and
mobile apps. It is built entirely on open standards and technologies like HTML5, CSS,
JavaScript and jQuery. JQXWidgets enables responsive web development and helps you
create apps and websites that look beautiful on desktops, tablets and smart phones.
Use JQXWidgets with popular frameworks like AngularJS, KnockoutJS and server-side
technologies like ASP.NET, MVC, PHP, JSP and Node.js
JQXWidgets is a feature complete framework with professional touch-enabled jQuery
widgets, themes, input validation, drag & drop plug-ins, data adapters, built-in WAI-
ARIA accessibility, internationalization and MVVM support.
7.6. JSP
Server Application Development:
Server-side applications in the managed world are implemented through runtime hosts.
Unmanaged applications host the common language runtime, which allows your custom
managed code to control the behavior of the server. This model provides you with all the
features of the common language runtime and class library while gaining the performance
and scalability of the host server.
The following illustration shows a basic network schema with managed code running in
different server environments. Servers such as IIS and SQL Server can perform standard
operations while your application logic executes through the managed code.
32 | P a g e
Server-Side Managed Code:

JSP is the hosting environment that enables developers to use the Spring Framework to
target Web-based applications. However, JSP is more than just a runtime host; it is a
complete architecture for developing Web sites and Internet-distributed objects using
managed code. Both Web Forms and XML Web services use IIS and JSP as the
publishing mechanism for applications, and both have a collection of supporting classes
in the Spring MVC Framework.
If you develop and publish your own XML Web service, the Spring MVC Framework
provides a set of classes that conform to all the underlying communication standards,
such as SOAP, WSDL, and XML. Using those classes enables you to focus on the logic
of your service, without concerning yourself with the communications infrastructure
required by distributed software development.
Finally, like Web Forms pages in the managed environment, your XML Web service will
run with the speed of native machine language using the scalable communication of IIS.
Active Server Pages Spring MVC:

JSP is a programming framework built on the common language runtime that can be used
on a server to build powerful Web applications. JSP offers several important advantages
over previous Web development models:
Enhanced Performance.
JSP is compiled common language runtime code running on the server. Unlike its
interpreted predecessors, JSP can take advantage of early binding, just-in-time
compilation, native optimization, and caching services right out of the box. This amounts
to dramatically better performance before you ever write a line of code.
33 | P a g e
World-Class Tool Support.

The JSP framework is complemented by a rich toolbox and designer in the Visual Studio
integrated development environment. WYSIWYG editing, drag-and-drop server controls,
and automatic deployment are just a few of the features this powerful tool provides.
Power and Flexibility.

Because JSP is based on the common language runtime, the power and flexibility of that
entire platform is available to Web application developers. The Spring MVC Framework
class library, Messaging, and Data Access solutions are all seamlessly accessible from the
Web. JSP is also language-independent, so you can choose the language that best applies
to your application or partition your application across many languages. Further, common
language runtime interoperability guarantees that your existing investment in COM-based
development is preserved when migrating to JSP.
Simplicity.
JSP makes it easy to perform common tasks, from simple form submission and client
authentication to deployment and site configuration. For example, the JSP page
framework allows you to build user interfaces that cleanly separate application logic from
presentation code and to handle events in a simple, Visual Basic - like forms processing
model. Additionally, the common language runtime simplifies development, with
managed code services such as automatic reference counting and garbage collection.
Manageability.
JSP employs a text-based, hierarchical configuration system, which simplifies applying
settings to your server environment and Web applications. Because configuration
information is stored as plain text, new settings may be applied without the aid of local
administration tools. This "zero local administration" philosophy extends to deploying
JSP
34 | P a g e
Scalability and Availability.

JSP has been designed with scalability in mind, with features specifically tailored to
improve performance in clustered and multiprocessor environments. Further, processes
are closely monitored and managed by the JSP runtime, so that if one misbehaves (leaks,
deadlocks), a new process can be created in its place, which helps keep your application
constantly available to handle requests.
Customizability and Extensibility.

JSP delivers a well-factored architecture that allows developers to "plug-in" their code at
the appropriate level. In fact, it is possible to extend or replace any subcomponent of the
JSP runtime with your own custom-written component. Implementing custom
authentication or state services has never been easier.
Security.
With built in Windows authentication and per-application configuration, you can be
assured that your applications are secure.
LANGUAGE SUPPORT:
The Microsoft Spring MVC Platform currently offers built-in support for three languages: C#,
Visual Basic, and JScript.
WHAT IS JSP WEB FORMS?

The JSP Web Forms page framework is a scalable common language runtime
programming model that can be used on the server to dynamically generate Web pages.
Intended as a logical evolution of ASP (JSP provides syntax compatibility with existing
pages),
The JSP Web Forms framework has been specifically designed to address a number of
key deficiencies in the previous model. In particular, it provides:
35 | P a g e
 The ability to create and use reusable UI controls that can encapsulate common
functionality and thus reduce the amount of code that a page developer has to write.
 The ability for developers to cleanly structure their page logic in an orderly fashion
(not "spaghetti code").
CODE-BEHIND WEB FORMS

JSP supports two methods of authoring dynamic pages. The first is the method shown in
the preceding samples, where the page code is physically declared within the originating.
File.
An alternative approach--known as the code-behind method--enables the page code to be
more cleanly separated from the HTML content into an entirely separate file.
36 | P a g e
Chapter 8
Software Development Tools
37 | P a g e
8. Software Development Tools

8.1. Tools:
8.1.1. Eclipse Neon 2016:
Eclipse is a Java-based open source platform that allows a software developer to create a
customized development environment (IDE) from plug-in components built by Eclipse
members. Eclipse is managed and directed by the Eclipse.org Consortium.
Eclipse got its start in 2001 when IBM donated three million lines of code from its Java
tools. The original goal of Eclipse was to create and foster an open source IDE
community that would complement the community that surrounds Apache.
In the enterprise, a major advantage to an open source development platform is that it
allows an IT department to mix and match development tools rather than being
committed to a single vendor's suite of development products. Although the Eclipse
Platform is written in Java, it supports plug-ins that allow developers to develop and test
code written in other languages.
Eclipse is released under the terms of the Eclipse Public License.
8.2. Spring MVC Framework:

Introduction to Spring MVC Framework:
The Spring MVC Framework is a new computing platform that simplifies application
development in the highly distributed environment of the Internet. The Spring MVC
Framework is designed to fulfill the following objectives:
 To provide a consistent object-oriented programming environment whether object

code is stored and executed locally, executed locally but Internet-distributed, or
executed remotely.
 To provide a code-execution environment that minimizes software deployment and
versioning conflicts.
38 | P a g e
 To provide a code-execution environment that guarantees safe execution of code,

including code created by an unknown or semi-trusted third party.
 To provide a code-execution environment that eliminates the performance problems
of scripted or interpreted environments.
 To make the developer experience consistent across widely varying types of
applications, such as Windows-based applications and Web-based applications.
 To build all communication on industry standards to ensure that code based on the
Spring MVC Framework can integrate with any other code.
The Spring MVC Framework has two main components: the common
language runtime and the Spring MVC Framework class library. The common language
runtime is the foundation of the Spring MVC Framework. You can think of the runtime
as an agent that manages code at execution time, providing core services such as memory
management, thread management, and Remoting, while also enforcing strict type safety
and other forms of code accuracy that ensure security and robustness. In fact, the concept
of code management is a fundamental principle of the runtime. Code that targets the
runtime is known as managed code, while code that does not target the runtime is known
as unmanaged code.
FEATURES OF THE COMMON LANGUAGE RUNTIME:

The common language runtime manages memory, thread execution, code execution, code
safety verification, compilation, and other system services. These features are intrinsic to
the managed code that runs on the common language runtime. With regards to security,
managed components are awarded varying degrees of trust, depending on a number of
factors that include their origin (such as the Internet, enterprise network, or local
computer).
This means that a managed component might or might not be able to perform file-access
operations, registry-access operations, or other sensitive functions, even if it is being used
in the same active application. The runtime enforces code access security.
39 | P a g e
For example, users can trust that an executable embedded in a Web page can play an
animation on screen or sing a song, but cannot access their personal data, file system, or
network. The security features of the runtime thus enable legitimate Internet-deployed
software to be exceptionally featuring rich. The runtime also enforces code robustness by
implementing a strict type- and code-verification infrastructure called the common type
system (CTS). The CTS ensures that all managed code is self-describing.
The various Microsoft and third-party language compilers Generate managed code that
conforms to the CTS. This means that managed code can consume other managed types
and instances, while strictly enforcing type fidelity and type safety. IN addition, the
managed environment of the runtime eliminates many common software issues.
For example, the runtime automatically handles object layout and manages references to
objects, releasing them when they are no longer being used. This automatic memory
management resolves the two most common application errors, memory leaks and invalid
memory references.
The runtime also accelerates developer productivity. For example, programmers can
write applications in their development language of choice, yet take full advantage of the
runtime, the class library, and components written in other languages by other
developers. Any compiler vendor who chooses to target the runtime can do so. Language
compilers that target the Spring MVC Framework make the features of the Spring MVC
Framework available to existing code written in that language, greatly easing the
migration process for existing applications.
SPRING MVC FRAMEWORK CLASS LIBRARY:

The Spring MVC Framework class library is a collection of reusable types that tightly
integrate with the common language runtime. The class library is object oriented,
providing types from which your own managed code can derive functionality.
This not only makes the Spring MVC Framework types easy to use, but also reduces the
time associated with learning new features of the Spring MVC Framework. In addition,
40 | P a g e
third-party components can integrate seamlessly with classes in the Spring MVC
Framework.
For example, the Spring MVC Framework collection classes implement a set of
interfaces that you can use to develop your own collection classes. Your collection
classes will blend seamlessly with the classes in the Spring MVC Framework.
As you would expect from an object-oriented class library,
The Spring MVC Framework types enable you to accomplish a range of common
programming tasks, including tasks such as string management, data collection, database
connectivity, and file access. In addition to these common tasks, the class library includes
types that support a variety of specialized development scenarios. For example, you can
use the Spring MVC Framework to develop the following types of applications and
services:
 Console applications.
 Scripted or hosted applications.
 Windows GUI applications (Windows Forms).
 JSP applications.
 XML Web services.
 Windows services.
For example, the Windows Forms classes are a comprehensive set of reusable types that
vastly simplify Windows GUI development. If you write a JSP Web Form application,
you can use the Web Forms classes.
41 | P a g e
Chapter 9
USE-CASE DIAGRAM
42 | P a g e
USE CASE DIAGRAM
Fig.1 Use Case Diagram
43 | P a g e
Chapter No.10
SEQUENCE DIAGRAMS
44 | P a g e
SEQUENCE DIAGRAMS
General MVC Diagram:
Fig.2 General MVC Diagram
45 | P a g e
Registration Diagram:
Fig.3 Registration Diagram
46 | P a g e
Login Diagram:
Fig.4 Login Diagram
47 | P a g e
Search Blood Request Diagram:
Fig.5 Search Blood Request Diagram
48 | P a g e
Update User Profile Page Diagram:
Fig.6 Update User Profile Diagram
49 | P a g e
Chapter No.11
USE-CASE DESCRIPTION
50 | P a g e
USE-CASE DESCRIPTION
User:
Use case 1 :- User

Sign up
Actors: user
Feature: Web Form
Use case Id: Usecase1
Over View:
If donor wants to create an account. Initially he/she open web site and then go on
Sign Up Page Then he/she must provide username, Cell no and password. Then proceed
further.
Pre-condition: 1. Connection on Internet is established.
Scenarios
Step# Action Software Reaction
1. Click on Signup Link Selected Signup Link from GUI.
2. Enter Username Entered Username by user and then show

Username in text field.
3. Enter Cell Number Entered Cell Number by user and then show
in text field.
4. Enter Password Shown password in password field in

Password form/notation.
6. Select City City selected from dropdown menu
7. Enter Cell Number Contact Number entered
8. Signup Button Pressed
51 | P a g e
Alternate Scenarios:
Action Application Response

Username AND/OR 1- Show Error Message on same page
Cell Number AND/OR 2- Again try to Signup
Post Conditions
Step# Description
1 User Signup successfully .
2 User is Signed Up.
3 Data is saved in database.
4 Maintain log in state and starts a Session.
5 Redirect to the Home Page.
User Interface reference 1- H o m e page, from which user transfer to Signup

Page by select and click the link of Signup.
2- S i g n u p Page on which user enter their specific
required data for Signup for creating their account.
52 | P a g e
Login:
Usecase2:-login
Actors: user
Feature: Web Form
Use case Id: usecase2
Over View:
If user (Donor) wants sign in then he/she must be registered. He/she provide Cell Number
and password and further proceed.

2. User is Registered.
3. User remembers his/her Cell Number and password.
4. Current user is not logged in already.
Scenarios
1. Click on sign in link Select sign in link from GUI.
2. Cell Number Enter Cell Number by user and shown in text

field.
3. Enter Password Show Password in password field
4. Click sign in Button Pressed

Cell Number 1. Show Error Message on same page
AND is/are invalid 2.Erase data from text fields
Password 3. Again try to sign in.
53 | P a g e
Use case For Viewer:
Usecase3 : View
FAQs
Actors: user
Feature: Web Form
Use case Id: Usecase3
Over View:
If the user (Donor) wants to view help about FAQs then he/she just click the FAQs
Link.
Scenarios
1. Click FAQs button Button is pressed
Business logic:
1 FAQs link button is clicked.
2 And then redirected to FAQs page, which is static page.
Post Conditions
54 | P a g e
Step# Description
1 Page is redirected to FAQs page successfully.
Use Case Cross referenced Search
User Interface reference 3- U s e r is at Home Page.

4- P a g e redirected to FAQs page.
55 | P a g e
Chapter No.12
ERD DIAGRAM
56 | P a g e
ERD DIAGRAM
Fig.7 ERD Diagram
57 | P a g e
Chapter No.13
SCREENSHOTS
58 | P a g e
Screenshots
Home Page:
Fig.8 Home Page
59 | P a g e
Donor Registeration Form
SignUp Form:
Fig 9 SignUp Page
60 | P a g e
Donor Login Page

Login Form:
Fig 10. Donor Login Page
61 | P a g e
Searching form To Find the nearest donor:
Fig 11. Donor Search
62 | P a g e
User Update/Edit Profile Page
Fig 12. Donor Update Profile
63 | P a g e
Chapter No.14
TEAM MEMBER
64 | P a g e
BLOOD DONATION SYSTEM IS developed as a BS Computer Science final year project.

Details about team members and their Skills are as follows.
Bilawal Naseeb (Team Leader)

He is group leader for the project. He has qualities of management, leadership and
technical skills. He is very good in System analysis and design.
He has following skills.
• Programming skills in Java, C/C++, JQuery, JQxWidget, HTML, CSS
• Experience for different DBMSs MySQL, PL/SQL Server
• Experience for different Technologies like Angular JS, Hibernate and Spring MVC
• UML Modeling
• Project Management expertise
Bilal Ahmed
He has expertise in web design and development. He has rich designing abilities.
• Understand the Language and Have Programming skills in PHP, C++, and JavaScript
• Understand the Great deal of knowledge in HTML, JQuery, CSS, and JavaScript
• Graphics Designing ability With AI
• UML Modeling
• Experience for different DBMSs MySQL, Oracle 11g,
• Expert in CMS
65 | P a g e
Muhammad Shahid
• Graphics designing and Web Designing ability With Adobe Photoshop
• UML Modeling
• Experience for different DBMSs MySQL,
Falik Sher
• Understand the Great deal of knowledge in HTML, CSS
• Graphics Designing ability With Adobe Photoshop
• UML Modeling
66 | P a g e
Muhammad Islahuddin
• Graphics designing and Web Designing ability With Adobe Photoshop
• UML Modeling
• Experience for Handling Different Network System
67 | P a g e
Chapter No.15
REFERENCES
68 | P a g e
https://www.w3schools.com/
http://stackoverflow.com/
https://docs.oracle.com/en/java
https://spring.io/docs
https://www.jqwidgets.com/tag/jqxwidgets/
https://en.wikipedia.org/wiki/Eclipse_(software)
http://www.mallstuffs.com/Blogs/BlogDetails.aspx?BlogId=14&BlogType=
Technical&
69 | P a g e
THE END
70 | P a g e

Final BDS

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Final BDS

Uploaded by

Copyright:

Available Formats

Blood Donation System

ONLINE BLOOD DONATION SYSTEM

Project Advisor: Muhammad Asif

Bilawal Naseeb (152151011)

Department of Computer Science,

National College of Business Administration & Economics (ECC)

Project Advisor Project Examiner

Name: Muhammad Asif Name:

Designation: Lecturer Designating:

National College of Business

National College of Business Administration & Economics (ECC)

National College of Business Administration & Economics (ECC)

National College of Business Administration & Economics (ECC)

National College of Business Administration & Economics (ECC)

1.2 Problem Definition…………………………………………………….……….2

2.1 Project Title…………………………..…………………………………...…..5

2.2 Project Area......................................................................................................5

2.3 Project Correlation with industry………………..…..…………………….....5

2.4 Industrial Influence.…………..………………..…………………………….5

2.5 Processes with Phases………………………..……………………………....6

2.6 System Basis…………………………..……..………………………………7

3.3 Definition ,Acronyms & Abbreviations………………………………………9

3.4 Overview of remaining SRS...……………………….……………………….9

National College of Business Administration & Economics (ECC)

4.1 Overall Description……………………………………………..……………11

4.1 Product Perspective………………………………….…………..…………...11

5.1 Testing Methodology…………………………………….………………….15

5.1.3. Unit Testing:………………………………………………..…….……….17

5.1.5 Validation Testing………………………………………………………….18

National College of Business Administration & Economics (ECC)

National College of Business Administration & Economics (ECC)

National College of Business Administration & Economics (ECC)

1.2 Problem Definition:

2.1. Project Title:

“BLOOD DONATION SYSTEM”

2.2. Project Area:

2.3. Project Correlation with industry:

2.4. Industrial Influence:

2.5. Processes with phases:

In the first phase find a blood donor.

2.6. System Basis:

3.3. Definitions, Acronyms & Abbreviations:

FAQ: Frequently Asked Questions

3.4. Overview of Remaining SRS:

4.1 Product Perspective:

4.3. Site Adaptation Requirement:

4.4. Product Functions:

Following are the functions of this game:

5. Blood Request Alerts

4.5. User Characteristics:

4.7. Assumptions and Dependencies:

5.1. Testing Introduction:

5.1.1. Testing Objective:

5.1.2. STRATEGIC APPROACH TO SOFTWARE TESTING:

5.1.3. Unit Testing:

Module Testing or unit testing is a process of testing the individual subprograms,

1. WHITE BOX TESTING

3. DATA FLOW TESTING

5.1.4. Integration Testing:

5.1.5. Validation Testing:

SPECIFICATIONS AND REQUIREMENT

6. Specification and Requirement:

6.1.1. Security and Protocol Architecture:

6.2. External Interfaces: