By : G. H. AHMAD ABBAS

1601-12-862-017

Under the guidance of :

SRI GNR PRASAD

Introduction

Users are increasingly pursuing complex task-oriented goals on the Web, such as making travel arrangements, managing finances or planning purchases.

To this end, they usually break down the tasks into a few co-dependent steps and issue multiple queries around these steps repeatedly over long periods of time.

To better support users in their long-term information quests on the Web, search engines keep track of their queries and clicks while searching online. We propose a more robust approach that leverages search query logs

EXISTING SYSTEM

In this, query groups are identified by treating every query in a user’s history as a singleton query group, and then merge these singleton groups in an iterative fashion. However, this is impractical for two reasons. First, it may have the undesirable effect of changing a user’s existing query groups, potentially undoing the user’s own manual efforts in organizing history. Second, it involves a high computational cost, since it would have to repeat a large number of query group similarity computations for every new query.

The existing system motivated a method to perform query grouping in a dynamic fashion in order to ensure good performance while avoiding disruption of existing user-defined query groups.

The method shows how signals from search logs such as clicks can be used together to determine the relevance among query groups. Two potential ways of using clicks in order to enhance this process (1) by adding the queries into query set by text similarity (2) by expanding the query set when computing relevance to other queries with similar clicked URLs.

PROJECT SCOPE :

1. Organize user search histories in the

form of groups.

2. Query suggestions to user for

respective query entered.

3. Dynamic Grouping of user search

history.

4. Result ranking of query

suggestions.

OBJECTIVES :

Implement a full fledged user history

organizer and handler that allow you

to organize user history and can

perform various operations such as

view previous, recent histories, and

search financial related data.

FEASIBLITY 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

Technical Feasibility

Operation Feasibility

Economical Feasibility

System Architecture

Login with username and password

Is Correct?

NO

User Enters Search Query

Is Admin?

Upload New Results

Query Grouping and Result Display using groups

YES

NO

YES

1.

2.

3.

4.

5.

6.

7.

Add Financial Details

View Groups

Login

Registered User

System Admin

Change Password

Register

View Recent History

Unregistered User

Search Financial Data

CLASS DIAGRAM

ER DIAGRAM :

Financial

User

Admin

Password Username

Url

User

MobileHistory

Date

Time

Description

Query

PasswordUsername

Group

Title

Email

Group Title

Url

Searches

Organizes

Maintains Contains

Different Modules of the

SystemThe system is proposed to have the

following modules :

1. Admin Module

2. Registered User module

3. Unregistered User module

ADMIN MODULE

Admin is allowed to

add financial details into

financial table, view user

details, delete users, and

view groups. The admin

must already have a user

id and password to login.

REGISTERED USER MODULE

•Registered user is allowed to view his previous

and recent history and search financial related

details.

•The registered user must already have a user id

and password to login.

Unregistered User module

Unregistered user is

allowed to view recent

history and search

financial related

details.

SOFTWARE AND HARDWARE REQUIREMENTSSoftware Requirements :Operating System : Windows95/98/2000/XP Application Server : Tomcat5.0/6.X

Front End : HTML, Java, JSPScripts : JavaScript.Server side Script : Java Server Pages.Database Connectivity : Mysql.

Hardware Requirements :Processor : Pentium –IIISpeed : 1.1 GhzRAM : 256 MB(min)Hard Disk : 20 GB

WHY THIS TECHNOLOGY IS CHOSEN ?

Simple

Object-Oriented

Platform Independent

secured

Robust

Architecture Neutral

Portable

High Performance

Distributed

Multi-threaded

We show how such information can be used

effectively for the task of organizing user

search histories into query groups. As future

work, we intend to investigate the usefulness

of the knowledge gained from these query

groups in various applications such as

providing query suggestions and biasing the

ranking of search results.

Ahmad Abbas Khan…

MCA, C.B.I.T ,

Hyderabad

Thank you…