This is the document submitted to my guide about status of my project up to first review.

1. Query Management System-First Review
Existing System:
The Microsoft Outlook Exchange Server is one of the existing of system
Query Management system.
The BPO(Backend Process Outsourcing) companies such as using this
application for ticketing the queries from their customers.
The processing model of such BPO's are
1. The customer's queries are received by Process Executives(PE) of an
organization.
2. The PE is the person handle the queries from the customers, he tagging the
queries in to different categories based on the content inside.
3. The solved queries are closed immediatly, otherwise the employees still work
towards the solution.

2. Problem occurs in the Existing system are:
1.The customer can't track the attender of their queries during the time of enqire.
2.The status of the queries are not identified by the customer.
3.There is no assurance to customers from the company about the time-span of
processing queries.
4.Even the companies had difficulties to verify their employees performance.
Proposed System:
The problems occur in the Existing Microsoft outlook Exchange service system
should be rectified in my project “Query Management System”. They are,
In this project, people to team mapping concept is used to identify the person, who
handling particular query?. Which is very helpful to the customers by knowing the name
and destination of the employee handling his problem as well as the management moniter
the performance of an individual employee.
The clear hierachical order of an employees in an organization, will provide the
clear view to mapping the employees and their destination.
The several types of packages provided to the customers for their conviniance to
access the service from the company, based on cost and time.
If the committed query is not solved with in the mentioned time then it should
reported to the next level of superior to the current employee. It is done by an automated
time lap concept, which is based on the package selected by the customer. It differ from one
package to another.
An automated will helpful to make the working process faster in between the
employees and also satisfy the customers that the query process is still alive.
The tagging process of a query will be very clear then other application. It is done
on the basis of the contents of the query.
System Analysis:
Cost Analysis: The expected cost of the Query Management System project is 3-4
lakhs. And with in the time period of 6 Months.
Feasibility Study: Done on user story being a inhouse project mock business object
is created and the development fully compriesed with Test Driven Development.
User-Interface: Built on Jquery 1.4.2.

3. Software Requirements:
Operating System : LINUX - UBUNTU 10.04
Scripting Language : RUBY 1.8.7
Framework : RAILS 3.0.3
Database : Mysql
Web Browser :Firefox, Chromium and etc.,
Hardware Requirements:
Ram Capacity :1GB
Hard disk :80GB
Processor :P4 processor
Automated bug tracking: the promise and the pitfalls
McLaughlin, L.;
This paper appears in: Software, IEEE
Issue Date: Jan-Feb 2004
Volume: 21 Issue:1
On page(s): 100 - 103
ISSN: 0740-7459
INSPEC Accession Number: 7949999
Digital Object Identifier: 10.1109/MS.2004.1259245
Date of Current Version: 09 August 2004
IEEE Computer Society
Sponsored by:
Abstract
Bug tacking systems give developers a unique and clear view into user's everyday
product experiences. Adding some statistical analysis and software teams can efficiently
improve product quality. It's hard to tell precisely how well the error reporting system
working, but this seems to be a bug weapon that has landed a permanent spot in microsoft's
arsenal. Automated bug tracking, combined with statistical reporting, plays a key role for
developers at the Mozilla Foundations, best known for its open source Web browser and
email software. The sparse, random sampling approach produces enough data for the team
to do what it call "statistical debugging"-bug detection through statistical analysis.