International Journal of Innovative Research in Computer and Communication Engineering
MenuISSN ONLINE(2320-9801) PRINT (2320-9798)
ISSN ONLINE(2320-9801) PRINT (2320-9798)
Ramakrishnan.R 1, Manju.R2, Anitha.S3
|
| Related article at Pubmed, Scholar Google |
Visit for more related articles at International Journal of Innovative Research in Computer and Communication Engineering
This paper proposes the dynamic database creation and query form based on user requirements. In dynamic database, the tables are created dynamically in an iterative process. In the real world database there are heterogeneous data, and the storage and retrieving of those data are complex process. The traditional database is static and they don't satisfy the user needs every time, and this also require huge memory and retrieving time. The static database usually contains fixed number of fields and these predefined fields may not be according to the user requirement. In dynamic database the name of fields and the type of fields are specified by the user in iterative process, at each iteration the fields are raked and these ranked fields are automatically added to the query forms, based on user preferences. The user fills out the query forms and submits the query; the DQF executes the query and provides the results.
Keywords |
| DQF (Dynamic Query Forms), CQF (Customized Query Forms), SQF (Static Query Forms). |
INTRODUCTION |
| Query forms are used for the user interaction with the database. The traditional query forms are static forms. This predefined query forms are designed by the developer or database administrators. Mostly the static forms do not satisfy the user requirements. Most of the static forms cannot use heterogeneous data. The loading time of the static from will be very high and huge database are required. Adding and removing of fields in static query forms and database are complex task. In static forms only simple queries will be available; these simple queries may not satisfy the user need in complex or huge database. |
| 1. User Authentication: In the user authentication module we mainly focus on providing the security to the user profile through the proper user name and password. Here registration is the first step where some details about the user are entered and then that information is stored in the database. |
| 2. Dynamic table creation: In dynamic table creation module, the tables are created dynamically in an iterative process. At each iteration the name of the fields and type of the fields (integer, float, varchar etc.) are given by the user. During this process the fields are ranked automatically and added to the query forms based on the user preferences. |
| 3. Query Execution: In query execution the user fills out the query forms and submits the query and then dynamically generated query form executes the query and provides the results. |
 |
RELATED WORK |
EXISTING SYSTEM |
| Recently proposed automatic approaches to generate the database query forms without user participation presented a data-driven method. It first finds a set of data attributes, which are most likely queried based on the database schema and data instances. Then the query forms are generated based on the selected attributes. |
| One problem of the aforementioned approaches is that, if the database schema is large and complex, user queries could be quite diverse. In that case, even if we generate lots of query forms in advance, there are still user queries that cannot be satisfied by any one of query forms. Another problem is that, when we generate a large number of query forms, how to let users find an appropriate and desired query form would be challenging. A solution that combines keyword search with query form generation is proposed. It automatically generates a lot of query forms in advance. |
| The user inputs several keywords to find relevant query forms from a large number of pre-generated query forms. It works well in the databases which have rich textual information in data tuples and schemas. However, it is not appropriate when the user does not have concrete keywords to describe the queries at the beginning, especially for the numeric attributes. |
PROBLEM RECOGNITION |
| (i)Most of the static forms do not support heterogeneous data: |
| Modern and scientific database usually contain hundreds of heterogeneous data. The real word database contains various relations and attributes. The static forms don’t support heterogeneous data and various relations. Predefined forms contain fixed number of data this may not satisfy the user needs all the times. |
| (ii)Loading time gets delayed: |
| Static tables contains various unused data these data occupies huge memory. So the loading time becomes higher. This paper proposes the creation of dynamic table, in which the user dynamically creates the required fields, hence number of unused data and memory will be reduced which in turn to reduces the loading time. |
| (iii)Database Complexity: |
| The insertion and deletion of fields in static table is a complex task. If we insert or delete fields in static table then the entire table schema should be restructured. Where as in dynamic table the fields are created dynamically, there will not be any complexity in adding and removing of fields. |
PROPASAL SYSTEM |
| We propose a Dynamic Query Form system: DQF, a query interface which is capable of dynamically generating query forms for users. Different from traditional document retrieval, users in database retrieval are often willing to perform many rounds of action (i.e., refining query conditions) before identifying the final candidates. The essence of DQF is to capture user interests during user interactions and to adapt the query form iteratively. |
IMPLEMENTATION |
| The implementation process beings with preparing the plan for the implementation for the dynamic tables and query forms for database queries. This plan involves the actual activities that are to be carried out with the available resources and equipments. This phase is the final and critical stage which gains user’s confidence of working effectively as it developed in the dynamic bases. |
| This paper includes the following functionalities which are segregated into various modules as follows. |
| User Authentication |
| Query Enrichment |
| Query Execution |
RANKING PURPOSE |
| Query forms are designed to return the user’s desired result. There are two traditional measures to evaluate the quality of the query result: precision and recall. Query forms are able to provide different queries by different inputs, and different queries can output different query result and achieve different precision and recalls. |
Query Construction |
| The goodness of the query form is determined by the query results generated from the query form. Based on this, we rank and recommend the potential query form components so that users can refine the query form easily. Based on the proposed metric, we develop efficient algorithms to estimate the goodness of the projection and selection form components. Here efficiency is important because DQF is an online system where users often expect quick response. A lot of research works focus on database interfaces which assist users to query the relational database without SQL. QBE (Query-By-Example) and Query Form are two most widely used database querying interfaces. |
PROPOSED ALGORITHM |
Algorithm |
| Query construction |
| Data: Q= {Q1,Q2,..,} is the set of previous queries executed on Fi. |
| Result: Qone is the query of One-Query |
| begin |
| σone ←− 0 |
| for Q ∈Q do |
| σone ←− σone ∨σQ |
| Aone ←− AFi |
| ∪Ar(Fi) |
| Qone ←− GenerateQuery(Aone,σone) |
| After the expansion of both the events and the geographic terms, the query can be constructed using Boolean Operators. In order to achieve both high precision and recall, we setup four levels of queries, giving different weights for retrieved documents. |
 |
SIMULATION RESULTS |
| EVALUATION |
| The goal of our evaluation is to verify the following hypotheses: |
| H1: Is DQF more useful than existing systems such as customized query form and static query form? |
| H2: Is DQF more effective to rank projection and selection components then the baseline and the random method? |
| H3: Is DQF effective to rank the related query form components in an online user interface? |
| H4: Is DQF more useful for taking a good decision among the resultant values? |
System Experimental Setup: |
| We implemented the dynamic query forms as a web based system using the ASP.NET code begins with C#. We used Ms-SQL Server as the database engine. All experiments were run using a machine with Intel Pentium IV 2.4GHz and running on windows 7. |
Form Generation Approach: |
| We compared three approaches to generate query forms CQF: The Customized Query Form generation used by many existing database such as Microsoft access, Easy Query. |
| SQF: The Static Query Form approach proposed in [1]. A static query one that will be passed to the database and only simple queries should use the static query mechanisms. If you need more complex query means you should use DQF. DQF: The Dynamic Query Form system proposed in this paper. |
User Study Setup: |
| We conducted a user study to evaluate the usability of our approach. We recruited 20 participants of graduate students, UI designers, and software engineers. The system prototype is shown by Fig [2]. The user study contains 2 phases, a query collection phase and a testing phase. In the collection phase, each participant used our system to submit some queries and we collected these queries. These queries were used as query workload to train our system. In the second phase, we asked each participant to complete 12 tasks (none of these tasks appeared in the workload) listed in Table 2. Each participant used all three form generation approaches to form queries. The order of the three approaches was randomized to remove bias. The databases collect a certain amount of historic queries so that we mainly consider the probability estimated from the historic queries. |
 |
User Study Result: |
| In this paper, we include some widely used metrics in Human-computer Interaction and Software Quality for measuring the usability of a system [8]. These metrics are listed in the Table 2. |
 |
| In database query forms, one action means a mouse click or keyboard input for a textbox. One function means a provided option for the user to use, such as a query form or a form component. In a web page based system, FN Max is the total number of UI components in web pages explored by the user. The smaller AC Min, AC, FN Max and FN are the better usability. Similarly, the higher AC Ratio, FN Ratio and Success are the better usability. |
User Study Analysis: |
| Table 1 shows the average result of the usability experiments for those query tasks. As for SQF, we generated 10 static query forms based on the collected user queries for each database. The results show that user did not accomplish querying tasks by SQF. The reason is that, SQF is built from the query workload and may not be able to answer the ad hoc queries in the query tasks. DQF and CQF are capable of assisting users finish all querying tasks. |
Static vs. Dynamic Query Forms: |
| If a query task is covered by historical queries in history, then SQF built on those historical queries can satisfy that query task. But the time and costs of using SQF and DQF to accomplish that task are different. Form complexity was discussed in [1] to evaluate the cost of using a query form. |
| Static execution requires configuring the database to run an SQL statement but delivers more consistent performance. Dynamic execution of SQL statements is more flexible because it does not require any special preparation on the database. |
CONCLUSION AND FUTURE WORK |
| For future enhancement we would like to provide Decision Support System based on the user requirements. We would like to capture user preference as runtime feedback for effective performance. To enhance the query form further we would like to extend the query form even for non relational database and add the keyword search for ad-hoc queries. In this paper we propose dynamic database creation and query forms based on the user requirements. By this dynamic database creation we may reduce the database size and complexity. The key idea of this paper is to generate query forms dynamically using the ranking components. The ranking are done based on the user preference. We capture user preference by user’s frequent usage of queries and feedback. This paper also supports decision making system for end users by taking historical data of user’s database. |
References |
|