Professional Documents
Culture Documents
The “online blood bank for sacred heart college” is an online application. The objective of
this web application is to reduce the manual work of human beings. In reducing the manual
work, it brings out the importance of time saving and time consummation. Since the present
world is techno-free world, it enables the people make sure the availability of every opportunity
especially the internet access. Here the benevolent persons those who are willing to donate
blood can use this web application. Thus, it is very essential that makes impact on the daily
living.
The aim of the “Online Blood Bank for the Sacred Heart College” is to provide the
opportunity to the donors to make use of the available technologies. It is a great help to
humanity.
1
II. REQUIREMENT ANALYSIS
2.1 INTRODUCTION
Requirement analysis brings the system requirements of the project. This chapter gives the
analysis of the application, E-R diagram, DFD diagram, Product vision, Use case specification
of the application. This brings to get an idea about the scope of the project.
2.2.1 INTRODUCTION
System study provides brief information of each module and its activities of the project. This
WEB PORTAL for online blood bank is a website page which is used to show the direct
register for blood donation in this website. The purpose of this vision document is to collect,
analyze and define the basic requirements and functional units of WEB PORTAL. The vision
statement of this project is to support the functionalities of the book website through the web
portal. It focuses on the capabilities needed by the stakeholders and the target users, and why
these needs exist. The details of how WEB PORTAL fulfills the needs are in the use case
specification.
2
2.2.2 LIST OF MODULES:
AN ONLINE BLOOD BANK web application system consists of the following list of
modules:
Home
About Us
Admin Login
User Login
Registration
Module no : 1
Activity no :1
Purpose :The purpose of this activity is to know about the blood value and need it.
Entry Criteria :The Admin should have the proper authenticated/valid username and the
Exit Criteria :The uploaded Blood donation champ details are stored in the database.
Module no :2
Activity no :1
3
Purpose :The purpose of this activity is to know about us.
Entry Criteria :The User can know our details using about us.
Input :About us
Module no :3
Activity no :1
Sub-module no :1
Activity no :1
Purpose :This is used to add new user details into the application.
4
Sub-module no :2
Activity no :1
Purpose : This is used to View new Hospital detail into the application.
Sub-module no :3
Activity no :1
Purpose : This is used to View new Blood Group detail into the application.
Sub-module no :4
Overview : To View the Registration, edit, Update, Delete, Print and pdf.
Activity no :1
5
Activity name : Registration Details.
Purpose : This is used to View new Registration details into the application.
Input : Registration.
Module no :4
Activity no :1
Sub-module1 : Registration
Sub-module no :1
Overview : To View the Registration, edit, Update, Delete, Print and pdf.
Activity no :1
Purpose : This is used to View new Registration details into the application.
Input : Registration.
Module no : 5
6
Overview : To provide the details about the Registration.
Activity no :1
Entry Criteria :The Donators should have the Register their details.
Input :Name, DOB, Hospital, Gender, Blood Group, Last Date Of Blood Donation.
7
2.2.4.CLASS DIAGRAM
8
2.2.5 DATA FLOW DIAGRAM
Level 0:
Level 1:
9
Level 2:
Level 3:
10
2.3 VISION DOCUMENT
2.3.1 INTRODUCTION
ONLINE BLOOD BANK WEB PORTAL is a web application system which is used to
maintain the Blood Donors List through the online. The purpose of this vision document is to
collect, analyze and define the basic requirements and functional units of ONLINE BLOOD
BANK WEB PORTAL. The vision statement of this project is to work on the Blood Donors
and online Registration through the web application system. It focuses on the capabilities
needed by the stakeholders and the target users, and why these needs exist. The details of how
2.3.2 POSITIONING
2.3.2.1 SCOPE
The vision document applies to the BLOOD BANK ONLINE WEB PORTAL is used by the
blood donors and organizer. However, the blood donor’s registers on this website. Each
registration form will have unique registration. The system makes record keeping more
efficient and secure from an unauthorized people. Only authorized organizer has the right to
retrieve data. This will secure the blood donor’s information. The organizer will view the
The ONLINE BLOOD BANK WEB PORTAL is very useful the system is developing due
to the problems that exist when using the manual system. There is some problem arise
especially for the maintaining database, and giving unique codes and inserting new blood
donors. And also, time consuming is main weakness in existing system. Existing system is very
expensive method as lot of paper work has to be done and lot of wastage of manpower.
11
The problem of Maintaining all the blood donor’s
details in manually
details
organizer
12
2.3.2.3 PRODUCT POSITION STATEMENT
Who Maintain the data and enables the organizer to view the required Blood
That Using this system, that will ease the Organizer and blood donor’s
13
2.3.2.4 STAKEHOLDER AND USER DESCRIPTIONS
This stakeholder and user description solution describes the members of online blood band. All
details
User Environment:
The users are well known to the computer. This system application is for the all the staff and
14
2.3.2.5 SUMMARY OF KEY STAKEHOLDER OR USER NEEDS
solution solution
properly system
through SMS.
15
2.3.2.6 PRODUCT OVERVIEW
This section provides a high level view of the Blood Donor’s web portal i.e ,by Register my
website blood donors through My Registration.
Product perspective
The ONLINE BLOOD BANK WEB PORTAL website will consist of two way
communications such as client side and server side .
Hardware environment
Processor : intel i3
RAM : 4GB
Hard disk : 1 TB
Software environment
Browser : Chrome
PRODUCT FEATURES
16
Functionalities
Quality Ranges:
Quality ranges section defines the quality range for performance robustness, fault
tolerance and similar characteristics for ONLINE BLOOD BANK.
Availability
The system shall be available for 24 hours a day 7 days in a week. The user can use the
application at his/her working time. There is no specified time.
Usability
Web based interface shall enable the user to interact with system more quickly.
This system interface shall be designed for ease of use.
Since it is web-based application it can be used by anyone on online.
The works will be faster.
Reliability
Maintainability
17
2.4 USE CASE SPECIFICATION
The following use case specification describes the activities carried out in this project. It
describes each and every action carried out by the actors in few modules. The diagram which
is above describes the activities carried out by the primary actors and secondary actors.
Use-case names:
Organizer Details
Registration Details
Register Details
18
Use case no : 01
Actor : Admin
Basic flow :
Use case no : 02
19
Brief Description : To maintain the Blood Donor’s details.
Post Condition : The admin and organizer details are saved/ edited/deleted.
Basic flow :
Alternative flow : Admin and organizer password is wrong shows error message.
Use case no : 03
20
Brief Description : To maintain the Registration details.
Post Condition : The admin and organizer details are saved/ edited/deleted.
Basic flow :
Alternative flow : Admin and organizer password is wrong shows error message.
Use case no : 04
21
Brief Description : To maintain the Register details.
Post Condition : The admin and blood donor details are saved, admin also edit/delete.
Basic flow :
Alternative flow : Admin and organizer password is wrong shows error message.
2.5 CONCLUSION
This chapter described the requirements of this web application such as system study, use case
specification and vision of the application. The next chapter describes about the design of the
web application.
22
III. DESIGN DOCUMENT
3.1 INTRODUCTION
This “WEB PORTAL FOR Online Blood Bank” web application is used to store and retrieve
the details of Blood Donors. This system design clearly describes the main functionalities of
the system, behavior of the system and the actual design of the system. This consists of database
design, architecture design, user design, procedural design and so on. They are described as
follows.
23
3.2 ARCHITECTURAL DESIGN
(Client)
Web Browser
Application Layer
Registration Details
Organizer details
Camp Details
Login
Server
24
3.3 DATABASE DESIGN:
Id Integer 11 PK Id
Id Integer 11 PK Id
Table3.3.2 Hospitals
25
Table Name: Organizer
Id Integer 10 PK Id
Table3.3.3 Organizer
26
Table Name: Registration
Id Integer 11 PK Id
Donate Donate
Table3.3.4 Registration
27
Table Name: admin login
Id Integer 11 PK Id
Table3.3.5 Admin
28
3.4 INTERFACE DESIGN:
1.HOME PAGE:
29
2.LOGIN PAGE:
Login
Login
User Id ST001
Password *******
Login in
3.HOSPITAL PAGE:
Hospitals
Name
In charge
save Cancel
30
4.USERS PAGE:
Admin-user
Name Email
Usertype
save Cancel
31
5.REGISTER PAGE:
Registration
Name Dob
hospital gender
Name
Batch Dob
Blood Group
Conducted
HospitalBy Gender
MobileNo
Email
batch Last date of donation
save Cancel
32
3.6 TEST CASE DESIGN:
1 Ts01 Login Logi To make This No other TC01: User should have
n module is user should logged in with proper
Organizer Click
to help login in the user name and
to log into login
user to same user password
button
System login id.
without
enterin
g data
EX01:
User
should
not
have
logged
in and
proper
messag
e
should
be
shown
TC:02
Type
number
33
or
special
symbol
in the
user
name
for
more
than 10
charact
er.
EX:02
System
should
not
allow
the user
to type
more
than 10.
TC:03
Enter
proper
userna
me and
passwo
rd
34
EX:03
If the
user is
admin
system
should
redirect
to
admin
home.
EX01:
Admin
details
should
have
been
35
stored
in the
databas
e.
TC02
Click
save
button
with
filling
require
data
field
Ex02
Proper
error
messag
e
should
be
shown.
36
3 TS0 Registe Regi This page This page If register TC01: Registration details
3 r details ster gives the fetches the presses the displayed
By
and detai register data from register page
filling
donors ls details and register it goes to
name
and donors and registration
and
dono displays
email
rs
there
will be
a
persona
l details
fill then
press
submit
button
EX01
If the
Registr
ation is
pressed
the
register
form
button
is
display
ed then
enterin
37
g there
will an
Require
s fields
there
fill it.
after
that at
bottom
submit
button
will be
display
ed by
clickin
g the
Registr
ation is
stored
and
display
ed.
3.7 CONCLUSION
This chapter clearly demonstrates the design of the system, the Architectural diagram gives the
overall architecture of the system. The database design defines the fields of the table, the
interface design shows the output of the application and the test case gives the users action.
The following chapter provides the information about the overview of the project, pseudo code
38
IV. IMPLEMENTATION
4.1 INTRODUCTION
Implementation of the project describes the overview of the project and pseudocode of the
program code.
WEB PORTAL FOR ONLINE BLOOD BANK is a web application that keeps the details
of the Blood Donors. All the information of this website which can be stored and retrieved.
This application helps the admin to maintain database and Organizer can view the website and
Home
About Us
Admin Login
User Login
Registration
39
Website for Online blood bank
Sub modules
Sub modules
Donors List
Organizer also Maintain And View
Donors List Can Manipulate the
register Donors Details
take print Users Details
40
4.3 PSEUDO CODE
Login page:
login.php
Step 1: The username and the password of the user is stored in the Database.
Step 2: It checks whether the username and password are correct.
Step 3: If ((username) && (password))
Login correct (it redirects to a page called home_admin.php)
Else
Login Failed unable to redirect the page.
home_admin.php
Registration.php
Registration.php
Step 1: The first step is to assign the inputted text in the text box to a variable.
var a=document.forms["addproduct"]["pname"].value;
if (a==null || a=="")
return false;
41
var b=document.forms["addproduct"]["desc"].value;
if (b==null || b=="")
return false;
var f=document.forms["addproduct"]["version"].value;
if (f==null || f=="")
return false;
var c=document.forms["addproduct"]["price"].value;
if (c==null || c=="")
return false;
var d=document.forms["addproduct"]["cat"].value;
if (d==null || d=="")
return false;
42
}
var e=document.forms["addproduct"]["image"].value;
if (e==null || e=="")
return false;
}Step 2: Insert the inputted text in the text box into database
VALUES('$product')”);
4.4 CONCLUSION
Implementation of the project included all those activities such as explaining the overview
of the project and pseudo code. The next chapter describes the testing for various types of
43
V. TESTING
5.1 INTRODUCTION
Testing phase forms an important part of software development. It’s the process of finding the
errors and missing operations and also a complete verification to determine whether the
Unit testing focuses verification efforts on the smallest unit of software design of the modules.
result
Description
password successfully
and redirected
to the
specified page
44
Unit name: User Login
result
Description
password successfully
and redirected
to the
specified page
Description
45
Unit name: Registration
Description
register.
blood
46
Unit name: About Us
Description
1 Used to Know User can know User can view User and
know website.
47
5.3 INTEGRATION TESTING
In this integration testing there are two types of testing exists that is top-down integration and
bottom-up integration.
The top-down integration is an incremental approach to construct a program structure. Modules
are integrated by moving downward through the control hierarchy beginning with the main
control module.
The bottom-up integration testing as its name implies begins construction and testing with
atomic modules that is modules at the lowest in the program structure.
In this system only, bottom-up integration testing has been considered and tested. While
integrating the modules all the errors in the interfaces and the errors in passing and receiving
the parameters have been identified and eliminated.
The database and the database processes should be tested as separate system. These systems
should be tested with database access contains like number of simultaneous users, the volume
of data support.
Test objective
Ensure database access methods and process function properly and without data corruption.
Technique
Invoke each database access method and process seeding each with valid and invalid data.
Completion criteria
All database access methods and process function as designed and without any data corruption.
Special consideration
Test for data retrieval and modification to check whether there is any particular constraint in
these operations.
48
S.No Test case Normal input Expected result Actual result
Description
49
5.4 SYSTEM TESTING
The software, which has been developed, has to be tested to prove its validity. Testing is
considered at the least creative phase of the whole cycle of system design. In the real sense it
is the phase of the whole cycle of system design. In the real sense it is the phase which helps
to bring out the creativity of the other phases and makes it shine.
System Testing is designed to uncover weaknesses that were not found in earlier tests. This
includes forced system failure and validation of the system as its users in operational
environment will implement it. Generally, it begins with low volumes of transactions based
on live data. The volume in increased until the maximum level for each transaction type is
reached. The total system is also tested recovery and fall back after various to ensure that no
data is lost during the emergency.
Inadequate testing or non-testing leads to errors that may be costly when appear months later.
Effective testing translates into cost saving from reduced errors. Test data may be artificial or
live (taken from the user’s files). In either case, they should provide all combination of values
or all test logic and transaction path subroutines.
The system testing is aimed at testing whether the system is able to start all the requirements
with desired performance and ease of use.
Test objective
Technique
Execute each use case giving both valid and invalid data and verify whether the navigation and
the error handling function well.
Completion criteria
All tests have been executed and deflects have been handled.
50
Special consideration
result
Description
of blood champs
Donors can
champs. uploaded.
register them.
viewed.
stored in the
Submitted.
database.
5.5 CONCLUSION
The processes of uncovering the errors in the given code are tested and removed them by
various types of testing and the next chapter describes about the conclusion of the project.
51
VI. CONCLUSION
6.1 SUMMARY
WEB PORTAL FOR ONLINE BLOOD BANK in web application that keeps the details of
the Blood need. All the information of this blood donor’s website which can be stored and
retrieved. This application helps the admin to maintain database and user can view the donors
list.
6.1.1 ADVANTAGES
6.1.2 DISADVANTAGES
Our future work in add the additional security for access the website by adding one-time
password generation algorithm. The blood champ newly conducted send to the corresponding
mobile no or mail id. In this manner the exiting blood donor can easier know.
6.4 CONCLUSION
This chapter concludes with the advantages, disadvantages and future enhancements of this
web application.
52
APPENDIX - A
PROJECT PROPOSAL
The “online blood bank for sacred heart college” is an online application. The objective of
this web application is to reduce the manual work of human beings. In reducing the manual
work, it brings out the importance of time saving and time consummation. Since the present
world is techno-free world, it enables the people make sure the availability of every opportunity
especially the internet access. Here the benevolent persons those who are willing to donate
blood can use this web application. Thus, it is very essential that makes impact on the daily
living.
INTRODUCTION
minority institution, established and administered by the Salesians of Don Bosco (SDB) and
This is Chinnappa Raj working on this project, doing II M.Sc. Computer Science Sacred Heart
College Tirupattur.
The duration of the project is 6 months starting from June to November 2018.
53
PROBLEM STATEMENT
The ONLINE BLOOD BANK WEB PORTAL is very useful the system is developing due
to the problems that exist when using the manual system. There is some problem arise
especially for the maintaining database, and giving unique codes and inserting new blood
donors. And also, time consuming is main weakness in existing system. Existing system is very
expensive method as lot of paper work has to be done and lot of wastage of manpower.
PROPOSED SOLUTION
The proposed system is designed to provide a solution for the drawbacks of present system..
Service oriented software Blood Donors are used in the system which functions are very
efficient.
Available Input
Home
About Us
Admin Login
Organizer Login
Registration
Expected output
Process Logic
4. Report generating
54
Stakeholders
1. Admin
2. Organizers
3. Blood Donors
End Users:
1. Blood Accepters
2. Blood Needler’s
TECHONOLOGY REQUIREMENTS
2. Database : MYSQL
7. Hardware/Software Requirements:
1. Hardware
Connection.
2. Operating System
55
Windows XP, 7, 8, 8.1
B. Client Specification
1. Hardware
2. Operating System
3. Software
1. Project Duration: The duration of the academic project is six months of the
even semester.
2. Project Initiation: Student upon receiving approval from the Project Guide
shall start the requirement study and analysis and complete it as per the project
Signature: Signature:
Date: Date:
56
57