Blood Donor Symbiosis (Mini)

BLOOD DONOR SYMBIOSIS
Abstract
Blood donation saves lives everyday at various situations. A blood transfusion may give them
the energy to spend time with family and friends. Blood cannot be manufactured it can only
comes as a gift from people. One person only allowed 6 pints of blood donation. One pint of
blood can save upto 33 lives The number of blood donor is very less when compared with other
countries. Here we propose a new and efficient way to overcome such outline. When we just
touch the button donor the App will be ask you to enter an individual's details like name, phone
number, age, weight, date of birth, blood group, address etc. At the emergency time of blood
needed we can check for blood donor nearby by using GPS. Once the app user enter the blood
group which he/she needed it will automatically show the donor nearby and send an alert
message to the donor. In case if the first donor is not available it will automatically search the
next donor which is present in queue. If the donor accept the request then an one time
password(OTP) will be send to the donor to verify. Blood donation app provider list of donor in
your city/area. Once the donor donate the blood it will automatically remove the donor detail for
next three months.
DEPARTMENT OF INFORMATION TECHNOLOGY 1

CONTENTS
List of tables
1. INTRODUCTION
1.1 ORGANIZATION PROFILE
1.2 LITERATURE SURVEY
1.3 PROBLEM DEFINITION
1.4 DATA COLLECTION
2. SYSTEM ANALYSIS
2.1 REQUIREMENT SPECIFICATION SOFTWARE
3. SYSTEM IMPLEMENTATION
3.1 USER REQUIREMENTS
3.2 FEASABILITY STUDY
4. SYSTEM ARCHITECTURE
4.1 DATA DICTIONARY
5. SYSTEM DESIGN
5.1 UML CONCEPTS
5.2 CLASS DIAGRAM
5.3 SEQUENCE DIAGRAM
6. SAMPLE CODE
7. SOFTWARE TESTING
8. SCREEN SHOTS
9. CONCLUSION

10. PROJECT REVIEW
10.1 BIBILIOGRAPHY

1.INTRODUCTION
1.1 ORGANIZATION PROFILE

Coalesce Technologies Private Limited is a global information technology (IT) services
company providing IT consulting, technology and outsourcing services. Using our enhanced
global delivery model, innovative plat forming approach and industry expertise, it provide cost-
effective services that enable our clients to use IT to enhance business performance, accelerate
time-to-market, increase productivity and improve services. Coalesce is the Services Provided by
the Organization.
Ever since its inception in 2001, Coalesce has been committed to providing Total Client
Satisfaction on higher-end platforms through Total Quality. In today's largely impersonal
business environment, Coalesce, with its firmly ingrained corporate philosophy of ‘Responsible
Relationships’ remains committed to its clients till they attain self sufficiency. With a rapidly
growing network of branches in India and overseas, Coalesce has built up an impressive client-
base of corporations within the country and abroad and has become one of the fastest growing IT
organizations, posting a phenomenal growth rate in the last financial year. Whether it is offering
Turnkey Solutions, providing right Manpower or creating extraordinary Software Careers,
Coalesce is sensitive to the needs of the industry .We partner with our clients to provide business
process improvement in key areas, cost reduction through process management, process re-
engineering and automation. Our customized solutions enable flexible business processes,
enhanced process clarity and cycle time. We also provide business strategy inputs to improve
competitiveness, ensure better market positioning and reduced time to market.
Innovation and customization is key to our delivery of value added services that best serve our
clientele. Our approach to address customer requirements involve people, processes, technology,
data and strategy to provide holistic solutions that can best address the customer needs and create
new business opportunities. Our consultants apply industry leading best practices to improve
business effectiveness, employee productivity and implement enterprise solutions that aim to
increase the efficiency of business operations. We consistently provide high standards of service
and bring the best teams of mind with cutting edge industry and functional experience so that our
clients can be derived from the maximum no of business value from our engagement.

1.2 LITERATURE SURVEY
Literature survey is the most important step in software development process. Before
developing the web Application tool it is necessary to determine the time factor, economy
and company strength. Once these things are satisfied, then next steps are to determine which
operating system and language can be used for developing the tool. Once the programmers
start building the tool the programmers need lot of external support. This support can be
obtained from senior programmers, from book or from websites. Before building the system
the above consideration are taken into account for developing the proposed system.
1.3 PROBLEM DEFINITION
A blood bank is doing collection of blood or donates blood. If you want to collect any blood
group from blood banks, we have to search for banks or we have to call to the bank. It is time
take taken process because if blood is not available in that bank means we have to search
another bank and we have call to that bank and search if blood group is matching or not, to
avoid these problems we providing blood bank system through online.
1.4 DATA COLLECTION
Data collection is any process of preparing and collecting data, for example, as part of a
process improvement or similar project. The purpose of data collection is to obtain
information to keep on record, to make decisions about important issues, or to pass
information on to others. Data are primarily collected to provide information regarding a
specific topic.
avoid these problems we providing blood bank system through online

2.SYSTEM ANALYSIS
Present Working System :
avoid these problems we providing blood bank system through online. in proposed system we
are showing how online blood bank is working.
To Be Proposed :
The development of this new system contains the following activities, which try to
automate the entire process keeping in the view of database integration approach.
In this project we are proposing online blood bank system, online blood bank means the
blood bank works through online. This is easy process to collect the blood or donate the
blood. Here we are providing all the blood bank details and hospital details and where blood
is available, Where camp is conducting, user have direct contact with the hospital person, and
the hospital person search for details by contacting with the admin. Admin will provide, in
which blood bank matching blood group is available or where the blood camp is conducting.
These details are provided to hospital person, hospital person will give the details to the user.
This is easy way to collect blood. Less time taken.
2.1 SOFTWARE REQUIREMENT SPECIFICATION
SOFTWARE REQUIREMENTS
Operating System : Windows XP/2003 or Linux

User Interface : HTML, CSS
Client-side Scripting : JavaScript
Programming Language : Java
Framework : struts 1.x, Hibernate 3.0
IDE/Workbench : My Eclipse 6.0
Database : Oracle 10g
Server Deployment : Tomcat 6.x
HARDWARE REQUIREMENTS
Processor : Core 2 Duo
Hard Disk : 160GB
RAM : 1GB or more

3.SYSTEM IMPLEMENTATION
3.1 USER REQUIREMENTS:

1. Home
2. Register
3. Login
4. Administrator
5. User
6. Hospital user
Home:
Use case ID OBBS
Use case Name Home button
Description Display home page of application
Primary actor User
Precondition User must open application
Post condition Display the Home Page of an application
Frequency of Use case Many times
Alternative use case N/A
Use case Diagrams
Attachments N/A
Registration Form:
Use case ID OBBS
Use case Name Registration
Description It display the credential form
Primary actor User
Precondition User Must have Email ID and Phone
Post condition User get the popup Message” U successfully Registered”
Frequency of Use case One time

Use case Diagrams

Attachments N/A
Login Form:
Use case ID OBBS
Use case Name Login Form
Description Display Login form to the user
Primary actor User
Precondition User must have username &password
Post condition Display the Home Page
Alternative use case Forgot password
Use case Diagrams
Attachments N/A
Administrator :
Use case ID OBBS

Use case Name administrator
Description View hospitals
Primary actor User
Precondition Must open the application home page
Post condition It displays hospital names
Use case Diagrams
Attachments N/A
System user
Use case ID OBBS

Use case Name System user

Description Add blood details and camp details

Primary actor User
Precondition Must open the application home page
Post condition It view blood details
Use case Diagrams
Attachments N/A
USER:
Use case ID OBBS

Use case Name User
Description Update details
Primary actor User
Precondition User must be login
Post condition It displays post events
Use case Diagrams
Attachments Photos (if any)
3.2 FEASABILTY STUDY

Preliminary investigation examines project feasibility; the likelihood the system will
be useful to the organization. The main objective of the feasibility study is to test the
Technical, Operational and Economical feasibility for adding new modules and debugging
old running system. All systems are feasible if they are given unlimited resources and infinite
time. There are aspects in the feasibility study portion of the preliminary investigation:
 Economical Feasibility
 Technical Feasibility
 Operation Feasibility
ECONOMIC FEASILITY
The computerized system takes care of the present existing system’s data flow and
procedures completely and should generate all the reports of the manual system besides a
host of other management reports. It should be built as a web based application with separate
web server and database server. This is required as the activities are spread throughout the
organization customer wants a centralized database. Further some of the linked transactions
take place in different locations. Open source software like TOMCAT, JAVA used to
minimize the cost for the Customer.
TECHNICAL FEASIBILITY
The technical issue usually raised during the feasibility stage of the investigation includes the
following: We can strongly say that it is technically feasible, since there will not be much
difficulty in getting required resources for the development and maintaining the system as
well. All the resources needed for the development of the software as well as the maintenance
of the same is available in the organization here we are utilizing the resources which are
available already.
i) The Java technology is sufficient to develop all the requirements of this project.
ii) Apache Tomcat server is sufficient for hosting this application.
OPERATIONAL FEASIBILITY

User-friendly
Customer will use the forms for their various transactions i.e. for adding new routes,
viewing the routes details. Also the Customer wants the reports to view the various
transactions based on the constraints. These forms and reports are generated as user-
friendly to the Client.
Reliability
The package wills pick-up current transactions on line. Regarding the old
transactions, User will enter them in to the system.
Security
The web server and database server should be protected from hacking, virus etc
Portability
The application will be developed using standard open source software (Except
Oracle) like Java, tomcat web server, Internet Explorer Browser etc these software will
work both on Windows and Linux o/s. Hence portability problems will not arise.
Availability
This software will be available always.
Maintainability
The system uses the 2-tier architecture. The 1st tier is the GUI, which is said to be
front-end and the 2nd tier is the database, which uses Oracle, which is the back-end.
The front-end can be run on different systems (clients). The database will be running at
the server. Users access these forms by using the user-ids and the passwords.

4.SYSTEM ARCHITECTURE
4.1 DATA DICTIONARY
NORMALIZATION:
Definition: Normalization is the process of efficiently organizing data in a database. There
are two goals of the normalization process: eliminating redundant data (for example, storing
the same data in more than one table) and ensuring data dependencies make sense (only
storing related data in a table). Both of these are worthy goals as they reduce the amount of
space a database consumes and ensure that data is logically stored. There are several benefits
for using Normalization in Database.
Benefits:
 Eliminate data redundancy

 Improve performance
 Query optimization
 Faster update due to less number of columns in one table
 Index improvement
There are different types of Normalizations form available in the Database. Let’s see one by
one.
1. First Normal Form (1NF):
First normal form (1NF) sets the very basic rules for an organized database:
 Eliminate duplicative columns from the same table.
 Create separate tables for each group of related data and identify each row with a
unique column or set of columns (the primary key).
 Create Primary Key
NOTE:
In Our Tables There is no First Normalization. Because we are not allowing the duplicate
columns.
2. Second Normal Form (2NF):
Second normal form (2NF) further addresses the concept of removing duplicative data:
 Meet all the requirements of the first normal form.
 Remove subsets of data that apply to multiple rows of a table and place them in
separate tables.
 Create relationships between these new tables and their predecessors through the
use of foreign keys.

 Remove columns which create duplicate data in a table and related a new table with
Primary Key – Foreign Key relationship
Column Name Data Type Null able Primary Key Constraint

USERNAME VARCHAR2(40) No 1 alphanumeric(0-9)
PID NUMBER(8,0) Yes -
FNAME VARCHAR2(20) Yes -
LNAME VARCHAR2(20) Yes -
- It Should Consists only
PASSWORD VARCHAR2(20) Yes
characters
GENDER VARCHAR2(10) Yes -
DOB VARCHAR2(20) Yes -
DOORNO VARCHAR2(20) Yes -
STREET VARCHAR2(20) Yes -
CITY VARCHAR2(20) Yes -
STATE VARCHAR2(20) Yes -
COUNTRY VARCHAR2(20) Yes -
PINCODE NUMBER(10,0) Yes -
EMAIL VARCHAR2(40) Yes -
MOBILE VARCHAR2(10) Yes -
TELNO VARCHAR2(15) Yes -
Note:
In the Above table we are not allowing duplication for columns, for that we are using
PRIMARY KEY for username [only once]
Column Null Primary Key

Name Data Type able Constraints
VARCHAR2(4 1 alphanumeric(0-
USERNAME No
0) 9)

PID NUMBER(8,0) Yes -

VARCHAR2(2
FNAME Yes -
0)
VARCHAR2(2
LNAME Yes -
0)
VARCHAR2(2 -It Should Consists only
PASSWORD Yes
0) characters
VARCHAR2(1
GENDER Yes -
0)
VARCHAR2(2
DOB Yes -
0)
VARCHAR2(2
DOORNO Yes -
0)
VARCHAR2(2
STREET Yes -
0)
VARCHAR2(2
CITY Yes -
0)
VARCHAR2(2
STATE Yes -
0)
VARCHAR2(2
COUNTRY Yes -
0)
NUMBER(10,0
PINCODE Yes -
)
VARCHAR2(4
EMAIL Yes -
0)
VARCHAR2(1
MOBILE Yes -
0)
VARCHAR2(1
TELNO Yes -
5)
Third Normalization:
In the above table we are using the REFERANCE for PID into Another table by using
FOREIGN KEY.

6.1.1. DATA DICTIONARY

Table Name: ADMIN
Field Name Data Type Size
USERNAME VARCHAR 100
PASSWORD VARCHAR 100
Table Name: USER

Table Name: Hospital user

Table Name: Hospital user register

(fname VARCHAR 100

lname VARCHAR 100
rollno VARCHAR 100

gender VARCHAR 100
mailid VARCHAR 100

address VARCHAR 100
phone VARCHAR 100
password VARCHAR 100
Table Name : USERregister

(fname VARCHAR 100

lname VARCHAR 100
rollno VARCHAR 100
gender VARCHAR 100
mailid VARCHAR 100

address VARCHAR 100
phone VARCHAR 100
password VARCHAR 100

5.SYSTEM DESIGN
The System Design includes the maintenance of the Patient information, their login details,
authorization services, details of the messages with respect to the user logged into and their
accessibility information in the database server.
The design also needs to provide the communication channel to the user to communicate
with the website to know better details about the healthcare system. Authorization and
authentication services are preferred most for this purpose.
The user is also expected to have the facility to store the information of the healthcare
system, to speed up the communication process between the server and the process of
maintaining the details, which include all the doctors and there suggested medicines, and
their detailed information required for the usage process. The user also should give all his
details as a registration to get registered.
WHY CHOOSE “JAVA":
In its brief existence, the WORLD WIDE WEB has evolved into a truly global Information
space. Not only does it offer information on any subject, it provides its citizens with the
power to globally publish information on any subject and at minimal cost. The massive
international participation in the web has resulted in the creation of many web pages that are
not only informative, but also entertaining. This entertainment value has further fuelled the
webs growth and has led to browsing becoming an international pastime. Browsing involves
scanning web pages for interesting information, following useful links to other pages, and
repeating the process until we come across something that makes us temporarily stop and
focus sometimes we mutter "HMM" or "That's interesting!" and create a bookmark. Then,
eventually, we move on. The tendency to move on and continue browsing is natural.
We usually don't read the same book over and over. If we have stock of magazines in front of
us, we are likely to flip through them all. Web pages are like magazine pages, except that
they are move available, usually free and have more "next" pages to which to turn computer

programs are different. They are active, while books, magazines, and web pages are static or
passive.
The Modern software developers faces enormous headaches and challenges when he tries to
develop software that is portable to Microsoft windows, x window systems, motif,
Macintosh, and OS/2 windowing and networking environments. The usual approach is to
pick a target operating system (o s), write software for that o s, and eventually migrate it to
the other o s platforms. This usually involves great expense in terms of labour and software
development resources. It also results in the sacrifice of features that are difficult to support
across multiple o s platforms.
Java fulfils the software developer's dream of being able to write software in a single
language that will support windowing and networking on all major o s platforms, without
specified tailoring or even compilation. But Java's attractiveness does not end here. Sun's
engineers were thoughtful enough to develop in java a language and runtime system that art
simple, compact, Object Oriented, extendible, and secure. And then they gave it away for
free.
ABOUT JAVA:
Java is a programming language, a runtime system, a set of development tools, an application

programming interface (API). The relationship between these elements is depicted in figure.
The Java API contains predefined software packages with numerous platform-independent
"hooks" into the native windowing and networking capabilities of the host operating system.
The Java API provides a single common API across all operating system to which Java is
ported.
The keys to Java's portability are its run time system, and it’s API. The run time system is
very compact, evolving from earlier Sun efforts to build a software platform for consumer
electronics. Because this platform was not designed around any existing microprocessor, it
was built from scratch to be simple and efficient. The fact that it was not tied to a given
hardware architecture enabled it to be architecture neutral.

JAVA AND MODULARITY
Application Java supports the partition of a large program into modules. Specifically, a Java
program consists of number of classes. If the program is properly designed, these classes will
reflect encapsulation and information hiding. In Java, grouping sets of related classes into
packages. Could enhance encapsulation and information hiding.
JAVA AND CONSTANTS

Java is pure object-oriented language. Thus, it does not support constants as such instead;
constants have to be defined as final variables within a class. It is somewhat confusing for a
constant to be defended as a "variable". Unlike C and C++, Java also do not support macros
such as # defines that can be used, in conjunction with a pre-processor, to declare the value of
a constant? There is a good reason for this. Java applets are design to be independent
programs loaded over the Internet. Java therefore does not support header files or other
components that need to be available in conjunction with otherwise stand-alone programs.
JAVA AND OBJECT ORIENTATION

Java supports the five basic elements of Object-Oriented language, namely, classes, objects,
inheritance, polymorphism, and dynamic binding. Java is a pure Object-Oriented language; it
does not support the classical paradigm. Thus there are no functions or procedures, only
methods or classes.
JAVA AND REUSABILITY

All Object-Oriented programming language supports reuse via inheritance of classes. In
addition, mechanisms such as templates (in C++) and generics (in Adam) provide reuse at a
higher level of abstraction. A template or generic is a module that is defined in terms of
parameters. The generic is then instantiated for a particular set of parameters. There is a good
reason for this. Java applets are design to be independent programs loaded over the Internet.
There is a good reason for this. Java applets are design to be independent programs loaded
over the Internet.

JAVA DATABASE CONNECTIVITY

The database is the most important component of a company's information services
infrastructure. It is heart of the applications on which a company depends for its survival.
Any programming language must be able to provide an application with access to these
databases if it is to be considered a serious programming language.
The issues surrounding database access are often very difficult; other languages use either
proprietary APIs specific to individual databases or complex universal APIs such as ODBC.
Before starting any program the must be a need to used through data modeling and database
design.
JSP:
Java Server Pages (JSP) is a technology for developing web pages that support dynamic
content which helps developers insert java code in HTML pages by making use of special
JSP tags, most of which start with <% and end with %>.
A Java Server Pages component is a type of Java served that is designed to fulfil the role of a
user interface for a Java web application. Web developers write JSPs as text files that
combine HTML or XHTML code, XML elements, and embedded JSP actions and
commands.
Using JSP, you can collect input from users through web page forms, present records from a
database or another source, and create web pages dynamically.
JSP tags can be used for a variety of purposes, such as retrieving information from a database
or registering user preferences, accessing JavaBeans components, passing control between
pages and sharing information between requests, pages etc.
Why Use JSP?
Java Server Pages often serve the same purpose as programs implemented using the Common
Gateway Interface (CGI). But JSP offer several advantages in comparison with the CGI.
Performance is significantly better because JSP allows embedding Dynamic Elements in
HTML Pages itself instead of having a separate CGI files.
JSP are always compiled before it's processed by the server unlike CGI/Perl which requires
the server to load an interpreter and the target script each time the page is requested.

5.1 UML CONCEPTS
What is UML?
The Unified Modelling Language (UML) is a standard language for specifying, visualizing,
constructing and documenting the artefacts of software systems, as well as for business
modelling and other non-software systems. The UML represents a collection of best
engineering practices that have proven successful in the modelling of large and complex
systems. The UML is a very important part of developing objects oriented software and the
software development process. The UML uses mostly graphical notations to express the
design of software projects. Using the UML helps project teams communicate, explore
potential designs, and validate the architectural design of the software.
USE CASE DIAGRAM:

login
register
update details
general user
post events
logout

login
register
add blood details
hospital user
add camp details
view blood details
logout
login
view hospitals
admin
view users
logout

5.2 CLASS DIAGRAM
The servlet API class diagram will be as follows.
general person hospital person

+user id +user id admin
+password +password
+user id
+registration() +registration() +password
+update details() +add blood details()
+post events() +add camp details() +view hospitals()
+logout() +view blood details() +view users()
+logout() +logout()
Fig: 8.1.1.1. Class Diagram describes the structure of the system in terms of classes and
objects
5.3 SEQUENCE DIAGRAM
This diagram views the static structures.

general person system hospital person admin
register register
login login login
update details
post events
add blood details
add camp details
view blood details
view hospitals
view users
logout logout
Sequence diagram describes data and functionality are arrived from inside the system.
ACTIVITY DIAGRAM
Activity diagram is basically a flow chart to represent the flow from one activity to
another activity.

home page
login
general person
hospital person admin
update details add blood details

view hospitals
post events add camp details
view users
view blood details
logout
Fig 8.1.3.1 Activity Diagram describes the flow from one activity to another activity
DEPLOYMENT DIAGRAM
The Deployment diagram shows the configuration of runtime processing notes and

the components that live on them
home
login
hospital person
admin
general person
add blood details

view hospitals
update details
add camp details
view users
post events
view blood details
logout
Fig 8.1.4.1 Deployment Diagram describes runtime processing notes and the components
8.2. LLD (Low Level Design)
1) LLD _id: LLD _001

Name : Login
Description : 1. Username: - Textbox
 Allows alphanumeric of minimum 5characters & maximum
25characters
 Blank spaces are not allowed
2. Password: Textbox
 Allows alphanumeric and special characters of maximum 15
characters.
 It allows only the registered candidates.
3. Submit: Button
 By hitting the submit button we will enter into the Home Page.
Sub-Operations:
I) Id : LLD-001.1
Name : Change Password
Description:
1. Current Password : Textbox
 It takes the current password.
characters. But it doesn’t allow the blank spaces.
2. New Password : Textbox
characters. But it doesn’t allow the blank spaces.
3. Confirm Password : Textbox
 It is same as new password.
4. Ok : Button
2) LLD_ id: LLD _002

Name : Registration
Description :
1. Name: - Text box
 Textbox allows alphanumeric maximum of 26 characters
2. Password: - Text box

 Allows at least 8 characters with special characters,

numbers, alphanumeric and Blank spaces are not allowed
3. Confirm Password: - Same as password

4. Address: - Textbox
 Allows maximum of 50 characters
5. Gender: - List box

 Select either female or male from the list box
6. Phone Number: - Textbox

 Allows only numeric values which is maximum of 10
characters
7. Date of Birth: - Textbox

 Allows the format of date
8. Location: - Textbox
 Allows alphanumeric of maximum 50 characters
6.SAMPLE CODE
<%@page contentType="text/html" pageEncoding="UTF-8"%>

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"

"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>login</title>
<link href="style.css" rel="stylesheet" type="text/css" />
<script language="javascript">
function loginvalidate()
{
if(document.f2.t1.value=="" || document.f2.t2.value==""){
alert("enter usrname and pwd");
exit(0);
}else{
document.f2.method="post";
document.f2.action="validation.jsp";
document.f2.submit();
}
}
</script>
</head>
<body>
<div id="container">
<div id="header">
<div id="logo_w1">Blood Donor</div>
<div id="logo_w2">Symbiosis</div>
<div id="header_text">
<p>Donate Blood, Save Life</p>
<a href="registration.jsp">Register As Donor!</a>
</div>
<ul >
<li><a href="homepage.jsp">Home</a></li>
<li><a href="aboutblood.jsp">About Blood</a></li>
<li><a href="searchreg.jsp">Search</a></li>
<li><a href="bbhome.jsp">BloodBank Details</a></li>
<li><a href="hospitalhome.jsp">Hospital Details</a></li>
<li><a href="todayspostreg1.jsp">Todays Posts</a></li>
<li><a href="docarticles.jsp">Doctor Articles</a></li>
</ul>
</div>
<div id="content">
<div id="center">
<form name="f2">
<br>
<br>
<br>
<%if(request.getAttribute("regsuccess")!=null){%>
<font color="green">you are successfully registered!please login</font>
<%}%>

<center> USERNAME: <input type="text" name="t1" /><br><br>

PASSWORD: <input type="password" name="t2" /><br><br><br>
<input type="button" onclick="javascript:loginvalidate()" value="LOGIN"
name="s1" />
<input type="reset" value="reset"></center>
</form>
<% if(request.getAttribute("wronguid")!=null){ %>
<center> <font color="red">Wrong Username,please check!</font></center>
<%}%>
<%if(request.getAttribute("wrongpwd")!=null){%>
<center> <font color="red">Wrong Password,please check!</font></center>
<%}%>
<%if(request.getAttribute("wrgpwd")!=null){%>
<center> <font color="red">Wrong Password,please check!</font></center>
<%}%>
</div>
<div id="footerline"></div>
</div>
<div id="footer">Copyright © 2011 Blood Donor Symbiosis. All rights
reserved.</div>
</div>
</body>
</html>
<?xml version="1.0" encoding="UTF-8"?>

<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5">
<display-name>BloodDonorWeb</display-name>
<welcome-file-list>
<welcome-file>login.jsp</welcome-file>
</welcome-file-list>
<servlet>
<description></description>
<display-name>AndroidUserReg</display-name>
<servlet-name>AndroidUserReg</servlet-name>
<servlet-class>AndroidUserReg</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>AndroidUserReg</servlet-name>
<url-pattern>/AndroidUserReg</url-pattern>
</servlet-mapping>
<servlet>
<display-name>AndroidUserLogin</display-name>
<servlet-name>AndroidUserLogin</servlet-name>

<servlet-class>AndroidUserLogin</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>AndroidUserLogin</servlet-name>
<url-pattern>/AndroidUserLogin</url-pattern>
</servlet-mapping>
<servlet>
<display-name>AndroidUpdateProfile</display-name>
<servlet-name>AndroidUpdateProfile</servlet-name>
<servlet-class>AndroidUpdateProfile</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>AndroidUpdateProfile</servlet-name>
<url-pattern>/AndroidUpdateProfile</url-pattern>
</servlet-mapping>
<servlet>
<display-name>AndroidDonorSearch</display-name>
<servlet-name>AndroidDonorSearch</servlet-name>
<servlet-class>AndroidDonorSearch</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>AndroidDonorSearch</servlet-name>
<url-pattern>/AndroidDonorSearch</url-pattern>
</servlet-mapping>
<servlet>
<display-name>AndroidCurrentLocation</display-name>
<servlet-name>AndroidCurrentLocation</servlet-name>
<servlet-class>AndroidCurrentLocation</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>AndroidCurrentLocation</servlet-name>
<url-pattern>/AndroidCurrentLocation</url-pattern>
</servlet-mapping>
<servlet>
<display-name>AndroidUpdateStatus</display-name>
<servlet-name>AndroidUpdateStatus</servlet-name>
<servlet-class>AndroidUpdateStatus</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>AndroidUpdateStatus</servlet-name>
<url-pattern>/AndroidUpdateStatus</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>homepage.jsp</welcome-file>

</welcome-file-list>
</web-app>
7.SOFTWARE TESTING
TESTING STRATEGIES :-

In order to make sure that the system does not have errors, the different levels of
testing strategies that are applied at differing phases of software development are:
UNIT TESTING:
Unit Testing is done on individual modules as they are completed and become
executable. It is confined only to the designer's requirements. Each module can be tested
using the following two Strategies:
BLACK BOX TESTING:
In this strategy some test cases are generated as input conditions that fully execute
all functional requirements for the program. This testing has been uses to find errors in
the following categories:
i. Incorrect or missing functions

ii. Interface errors
iii. Errors in data structure or external database access
iv. Performance errors
v. Initialization and termination errors.
In this testing only the output is checked for correctness.
The logical flow of the data is not checked.
WHITE BOX TESTING:
In this the test cases are generated on the logic of each module by drawing flow
graphs of that module and logical decisions are tested on all the cases. It has been uses to
generate the test cases in the following cases:

i. Guarantee that all independent paths have been executed.

ii. Execute all logical decisions on their true and false sides.
iii. Execute all loops at their boundaries and within their operational bounds
INTEGRATING TEST:
Integration testing ensures that software and subsystems work together a whole. It
tests the interface of all the modules to make sure that the modules behave properly
when integrated together.
SYSTEM TESTING:
Involves in-house testing of the entire system before delivery to the user. Its aim is to
satisfy the user the system meets all requirements of the client's specifications.
TEST APPROACH:
Testing can be done in two ways:
 Bottom up approach
 Top down approach
 Validation
BOTTOM UP APPROACH:
Testing can be performed starting from smallest and lowest level modules and
proceeding one at a time. For each module in bottom up testing a short program
executes the module and provides the needed data so that the module is asked to
perform the way it will when embedded within the larger system. When bottom level
modules are tested attention turns to those on the next level that use the lower level
ones they are tested individually and then linked with the previously examined lower
level modules.
TOP DOWN APPROACH:

This type of testing starts from upper level modules. Since the detailed activities
usually performed in the lower level routines are not provided stubs are written. A stub is
a module shell called by upper level module and that when reached properly will return a
message to the calling module indicating that proper interaction occurred. No attempt is
made to verify the correctness of the lower level module.
VALIDATION:
The system has been tested and implemented successfully and thus ensured that all the
requirements as listed in the software requirements specification are completely fulfilled.
In case of erroneous input corresponding error messages are displayed
TEST CASES
Use case Name: ADMIN Login

Test Case OBBS
Test case Operational Expected Observed Discrepancy Priority Severity

Number Description Output Output
Tc1 Enter the Error Error No - -
invalid admin Message Message
email id and in should be should be
valid password. displayed displayed.
invalid id
and
password.
Tc2 Enter the valid Message Message No - -

admin email id should be should be
and valid displayed displayed.
password. invalid id
and
password.

Tc3 Add hospital Message Yes No - -

details should be
displayed.
Use case Name: Hospital user Login

invalid Message Message
employee should be should be
email id and in displayed displayed.
valid password. invalid id
and
password.

employee email should be should be
id and valid displayed displayed.
and
password.
Tc3 Add blood Message Yes No - -

details should be
displayed.
Tc4 View Blood Message Yes No - -

details should be
displayed.
Use case Name: USER Login
Test Case ID: OBBS



invalid user Message Message
email id and in should be should be
valid password. displayed displayed.
invalid id
and
password.

user email id should be should be
and valid displayed displayed.
and
password.
Tc4 Update details Message Yes No - -

should be
displayed.
Tc5 Post event Displays the Yes No - -
magazine
lists.
8.SCREENSHOTS

This is the page that opens directly in this there I an option of register
as donor so by clicking this a user can register himself as a donor.
In the next step the donor can register himself by by entering his
details. And it shows as the donor registration.

After the donor registration it shows as successfully the donor has registered in the top URL
and it is represented in the below image with blue color.
If we want to search for a donor then by entering blood group and district name it display the
no of available donors in the particular area.
If we want to check the details of the bloodbank that are available then we can easily get the
details of no of units of blood available in the blood bank.

If a hospital want to register then by entering all the essential details the hospital can register
itself.

9.CONCLUSION
Blood donation is the one way to a person in healthy life. This is because during the blood
donation our body will be replaced new blood cell which have a better protein ,from this
program awareness of important of blood donation will increase.
Today the world is become a global village where everything is online. There are so many
web based solutions provided in the market for the comfort of people but without blood
human being is non living, just by providing the web solution of blood donors information is
just one more step in order to serve the man kind.

10. PROJECT REVIEW
10.1 BIBLIOGRAPHY
Book Resources:
[1] “Thinking in Java”, Bruce Eckel, Second Edition, Prentice Hall, mid-June 2000.
[2] “Oracle Database 10g Sets for TPC-H Three TB Benchmark". Retrieved 2008-01-31.
[3] “Java2 The Complete Reference”, Herbert Scheldt , McGraw Hill September 2001.
[4] “Java Server Pages”, Hans Bergsten, O’reilly, Third Edition December 2003.
[5]“Oracle Database" Reference 10g Release 1 (10.1). Oracle. Retrieved 2008-11-17.

[6]“IEEE, IEEE Software Standards”, IEEE Press, 2009
[7] “Software Engineering- A Practioners Approach”, Roger S.Pressman, McGraw-Hill
[8] “JDBC, Servlets, and JSP”, Santosh Kumar K and Cogent Solutions Inc. Edition 6.
Web Resources:
[1] www.java2share.com
[2] www.way2java.com
[3] www.java2s.com
[4] www.roseindia.net
[5] www.javatpoint.com
[6] www.ajava2all.com
[7] www.booksboon.com

Blood Donor Symbiosis (Mini)

Uploaded by

Document Information

Original Title

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

Blood Donor Symbiosis (Mini)

Uploaded by

Copyright:

Available Formats

BLOOD DONOR SYMBIOSIS

DEPARTMENT OF INFORMATION TECHNOLOGY 1

2.1 REQUIREMENT SPECIFICATION SOFTWARE

3.1 USER REQUIREMENTS

3.2 FEASABILITY STUDY

4.1 DATA DICTIONARY

5.1 UML CONCEPTS

5.2 CLASS DIAGRAM

5.3 SEQUENCE DIAGRAM

DEPARTMENT OF INFORMATION TECHNOLOGY 2

10. PROJECT REVIEW

DEPARTMENT OF INFORMATION TECHNOLOGY 3

1.1 ORGANIZATION PROFILE

DEPARTMENT OF INFORMATION TECHNOLOGY 4

1.2 LITERATURE SURVEY

1.3 PROBLEM DEFINITION

1.4 DATA COLLECTION

DEPARTMENT OF INFORMATION TECHNOLOGY 5

2.1 SOFTWARE REQUIREMENT SPECIFICATION

Operating System : Windows XP/2003 or Linux

DEPARTMENT OF INFORMATION TECHNOLOGY 6

3.1 USER REQUIREMENTS:

DEPARTMENT OF INFORMATION TECHNOLOGY 7

Use case Diagrams

Use case ID OBBS

Use case ID OBBS

DEPARTMENT OF INFORMATION TECHNOLOGY 8

Description Add blood details and camp details

Use case ID OBBS

3.2 FEASABILTY STUDY

DEPARTMENT OF INFORMATION TECHNOLOGY 9

DEPARTMENT OF INFORMATION TECHNOLOGY 10

This software will be available always.

DEPARTMENT OF INFORMATION TECHNOLOGY 11

4.1 DATA DICTIONARY

 Eliminate data redundancy

DEPARTMENT OF INFORMATION TECHNOLOGY 12

Column Name Data Type Null able Primary Key Constraint

Column Null Primary Key

DEPARTMENT OF INFORMATION TECHNOLOGY 13

PID NUMBER(8,0) Yes -

DEPARTMENT OF INFORMATION TECHNOLOGY 14

6.1.1. DATA DICTIONARY

Table Name: USER

Table Name: Hospital user

Table Name: Hospital user register

(fname VARCHAR 100

DEPARTMENT OF INFORMATION TECHNOLOGY 15

gender VARCHAR 100

mailid VARCHAR 100

Table Name : USERregister

(fname VARCHAR 100

mailid VARCHAR 100

DEPARTMENT OF INFORMATION TECHNOLOGY 16

WHY CHOOSE “JAVA":

DEPARTMENT OF INFORMATION TECHNOLOGY 17

Java is a programming language, a runtime system, a set of development tools, an application

DEPARTMENT OF INFORMATION TECHNOLOGY 18

JAVA AND MODULARITY

JAVA AND CONSTANTS

JAVA AND OBJECT ORIENTATION

JAVA AND REUSABILITY

DEPARTMENT OF INFORMATION TECHNOLOGY 19

<center> USERNAME: <input type="text" name="t1" /><br><br>