Professional Documents
Culture Documents
LBSQ
LBSQ
CHAPTER 1
INTRODUCTION
1.1 Introduction
We propose a scalable low-latency approach for processing LBSQs in broadcast
environments. Our approach leverages ad hoc networks to share information among mobile
clients in a peer-to-peer (P2P) manner. The rationale behind our approach is based on the
following observations:
when a mobile user launches a nearest neighbor (NN) query, in many situations, she
would prefer an approximate result that arrives with a short response time rather than an
accurate result with a long latency.
P2P approaches can be valuable for applications where the response time is an important
concern. Through mobile cooperative caching of the result sets, query results can be
efficiently shared among mobile clients.
The results of spatial queries often exhibit spatial locality. For example, if two MHs are
close to each other, the result sets of their spatial queries may overlap significantly.
1 .2 Purpose
User mobility and data exchange through wireless communication give LBSQs some
unique characteristics that traditional spatial query processing in centralize databases does not
address. Novel query processing techniques must be devised to handle these new challenges.
1. Mobile query semantics. In a mobile environment, a typical LBSQ is of the form “find the top-
three nearest hospitals.” The result of the query depends on the location of its requester. Caching
and sharing of query results must take into consideration the location of the query issuer.
2. High workload. The database resides in a centralized server, which typically serves a large
mobile user community through wireless communication. Consequently, bandwidth constraints
and scalability become the two most important design concerns of LBSQ algorithms [2].
3. Query Promptness and Accuracy. Due to users’ mobility, answers to an LBSQ will lose their
relevancy if there is a long delay in query processing or in communication. For example, answers
to the query “find the top-three nearest hospitals” received after five minutes of high-speed
driving will become meaningless.
1 .3 Scope
The scope of the project is to reduce the latency considerably in answering LBSQs. Our
approach is based on peer-to-peer sharing, which enables us to process queries without delay at a
mobile host by using query results cached in its neighboring mobile peers.
r
r ve MH4
d Se
e
a liz
n tr
Ce
MH3
MH1
MH2
MH-Mobile Host
1.5 References
Wikipedia
How Stuff Works
www.gaspricewatch.com.
www.dot.ca.gov/hq/traffops/saferesr/trafdata/...
IEEE Papers
1.6 Overview
This subsection should describe what the rest of the SRS contains and explain how the
document is organized.
CHAPTER 2
PROJECT PREREQUISITE
CHAPTER 3
SRS DOCUMENT
3.1. Introduction
3.1.1 Purpose
It is a user mobility and data exchange through wireless communication gives LBSQs
some unique characteristics that traditional spatial query processing in centralize databases does
not address. Novel query processing techniques must be devised to handle these new challenges.
The primary purpose of the LBSQs is to bring the desired information to the user in least
time. Spatial queries that retrieve information based on mobile user’s current location.
3.1.2 Document Conventions
3.1.5 References
Wikipedia
How Stuff Works
www.gaspricewatch.com.
www.dot.ca.gov/hq/traffops/saferesr/trafdata/...
IEEE Papers
CHAPTER 4
SOFTWARE DESIGN SPECIFICATION
4.1 Introduction
Our approach is based on peer-to-peer sharing, which enables us to process queries
without delay at a mobile host by using query results cached in its neighboring mobile peers. We
demonstrate the feasibility of our approach through a probabilistic analysis, and we illustrate the
appeal of our technique through extensive simulation results.
a map can be visualized as a graph, with cities as nodes and the highways between them as edged
between the nodes. Many real-world problems can be abstractly defined in terms of graphs,
thereby making graphs an often-used data structure.
Use Case
<<includes>>
<<includes>>
BPSQ_Main
Search for point of interest in <<includes>>
+ String node_name
verified nodes Return the point of interest
Node +int node_number
+String query
+node_list()
+Find_neighbor()
<<includes>> <<extends>>
Year 2010-11 Search nearest +query_forward()
neighbors again14
in Group No. 58
unverified region Compute the retrieval time
Department of Computer Engg. Location-based spatial query processing in
Path_finder POI_Finder
wireless
+String path +String node_name
+String node_name +int POI
+CalculatePath() +Search_POI()
4.3.1.1 Architecture diagram / UML Diagrams
+ identifyNode() +CalculateTime()
+return_POI()
Activity Diagram +Find_node()
Compute the nearest path to reach source node from every node
If not
Master_page. Default.aspx
aspx
node.aspx
CHAPTER 5
PROJECT PLAN AND RISK ANALYSIS
task which is feasible only when the constituent processes possess a certain level
of modularity (i.e., independence or non-interaction).
Project breakdown
1) Effort estimate table
Task Effort Deliverables Milestones
weeks
Analysis of existing systems & compare 4 weeks
with proposed one
Literature survey 1 week
DEC/10
JAN/11
SEP/10
OCT/10
Date
Phase
Phase 1
Phase 2
Phase 3
Phase 4
Phase 5
Phase 6
5.6 Test Plan
A test plan documents the strategy that will be used to verify and ensure that a product or
system meets its design specifications and other requirements. A test plan is usually prepared by
or with significant input from Test Engineers. Depending on the product and the responsibility of
the organization to which the test plan applies, a test plan may include one or more of the
following:
There are two test plans :
1.Automated Testing
2.Manual Testing
Automated Testing:-
A complex system may have a high level test plan to address the overall requirements and
supporting test plans to address the design details of subsystems and components.
Test plan document formats can be as varied as the products and organizations to which they
apply. There are three major elements that should be described in the test plan: Test Coverage,
Test Methods, and Test Responsibilities. These are also used in a formal test strategy.
Test coverage in the test plan states what requirements will be verified during what stages of the
product life. Test Coverage is derived from design specifications and other requirements, such as
safety standards or regulatory codes, where each requirement or specification of the design
ideally will have one or more corresponding means of verification. Test coverage for different
product life stages may overlap, but will not necessarily be exactly the same for all stages. For
example, some requirements may be verified during Design Verification test, but not repeated
during Acceptance test. Test coverage also feeds back into the design process, since the product
may have to be designed to allow test access.
Test methods in the test plan state how test coverage will be implemented. Test methods may be
determined by standards, regulatory agencies, or contractual agreement, or may have to be
created new. Test methods also specify test equipment to be used in the performance of the tests
and establish pass/fail criteria. Test methods used to verify hardware design requirements can
range from very simple steps, such as visual inspection, to elaborate test procedures that are
documented separately.
Test responsibilities include what organizations will perform the test methods and at each stage
of the product life. This allows test organizations to plan, acquire or develop test equipment and
other resources necessary to implement the test methods for which they are responsible. Test
responsibilities also includes, what data will be collected, and how that data will be stored and
reported (often referred to as "deliverables"). One outcome of a successful test plan should be a
record or report of the verification of all design specifications and requirements as agreed upon
by all parties.
Manual Testing:
It checks the testing operation like :
GO button : working properly (Yes) or (No)
REFRESH :working (yes) or (No)
STOP : working (yes) or (No)
FORWARD : (yes) or (No)
BACKWORD : working (yes) or (No)
Non-Functional Requirements
Run-Time Usability Describes the ease with which the system can be
learned or used.
Requirements
A typical usability requirement might state:
1) Understandability
The interface elements should be easy to
understand e.g. menus.
Ambiguous naming should be avoided.
2) Learnability
The user documentation and help should be
complete
The help should be context sensitive and
explain how to achieve common tasks
REFERENCE