User Interface Manager

The user interface manager provides the user interface and, allows the user to configure, control and monitor the database operations. The user maintains the integrity and security of the transactions at a time. One or more defined transactions are associated in a ‘script’ in the DCM. Through the user interface manager, the user controls the DCM application by starting and selecting the option in the processing screen and then clicking the required option to perform the operations. The user can employee the UIM to monitor the status of operations by viewing the transaction status screen.

 
Transaction Manager

The TM manages the transmission of transactions to XML reports. The TM will read configuration data from the database and generate the transactions as required by a script definition. The TM will communicate to the database through OLEDB template objects and where applicable shall reuse any objects that are need for the GUI.

The primary responsibility of TM will be to scan the database for the required transactions, generate the data structures with valid data, then make and mange the list of transactions and send to XML reports. It must also manage the receive responses and generate the status for transactions on demand..
 
 
 
Database

The DCM will contain several categories of Modifying and maintaining the integrity of the data

Constraints

The GM will provide the facility to track the data base tables, which are lacking in additional constraints to maintain the integrity of the database. Hence the DCM will have necessary scripts generated to implement new constraints on the tables required.

Base Entity data

The GM will allow the users to create the new entities as required and defining the relations between different entities of the database and integrate the subset of entities when required.
 
Performance Tuning

The DCM provides the option for the fine-tuning the performance of the database. Once the user identifies the performance degradation tables and specifies in the GM. The DCM will create additional bit map or tree indexes on the tables and when required.

Optimization

The DCM has the capability to tune the optimizer mode of the database depending on the operation performed on the database. The optimization option in the DCM constantly switches the optimizer mode of the database from chooses to all rows or cost based to rule based.

Integrity

The DCM will identify the duplicates in the selected tables and remove the duplicates to maintain the integrity of the database.
 
Import/Export

The DCM has different options of importing and exporting data from sample data files in to the database using SQL loader and the import/export facility is built with different options like from user to user and row to row and table to table.

User interface module

This User Interface of the DCM Provides the options to define new constraints, import and export of data, query optimization, tuning of operations, database mapping and transformations, creating additional db triggers and procedures, normalization of the database structure, table partitioning, deletion of the duplicates from the tables, the below GUI will be used to provide inputs and build the transactions for this script.

 
The main GUI has been divided into four parts

1) Normalization

2) Database Cleaning

3) Table Management and

4) Utilities
 
Normalization

The DCM has the scripts build to check for the normalized state of the database and inform the user regarding the status and also has built in scripts to alter the structure to make the database to normalized state.
 
Database Cleaning

Database cleaning is another complicated functionality of the application. As and when the database is being increased over the period of time, it is acceptable the there can be 20 percent of the records in database are duplicates or not being used at all. Many times these duplicate records will be caused to give the fault outputs and many other complications during the runtime. And also it causes to slowdown the performance of the application.

The DCM will have the capability to scan throughout the database and identify if there are any kind of duplicates in the database. It also will have the capability to erase the redundant records and clean the database. Using the UI facility of DCM, individual records can be inserted or deleted using if necessary. The database cleaning manager’s user interface is shown below.

It is decided that, in the current system development, Database Cleaning will have


1) Find duplicates

2) Erase Duplicates

3) Erase a record from database and

4) Insert a record into database.

The functionality and UI facility for each of them has been described briefly.
 
Find Duplicates

These features of the DCM will facilitates the operator or system administrators to check database periodically whether there are any duplicate records are being inserted due to enormous transaction that will be happening every day. When user clicks this button, the following UI screen will be appeared asking for detailed input from the user to process the request.
 
Erase Duplicates

The Erase Duplicates feature of DCM will facilitate the operator to find and erase the all-duplicate records from the specified database. As operator hits the “Erase Duplicates” button, the following UI will be displayed for more input from the operator.
 
Erase Record

The Erase Record features of the DCM will facilitate the operator to select the single record and delete it from the database. If operator clicks the Erase Record button on Figure 5, the application will pops up the following UI asking the operator for more input process the query.
 
Insert Record

The insert record feature will facilitate the operator to insert the single record into specific table in the specified database. It will eliminate the operator’s burden to write the separate scripts with large queries manually to insert the records in to the database during the trouble shooting the database. The DCM also will provide a facility to operator to insert the record based on specific conditions. In this case, operator must write the database query specifying the conditions to insert the record into the database. The following UI screen will be appeared if operator clicks the “Insert Record” button.
 
Table Management

This is the unique feature of the application, using which operator will able to manage the individual tables in specified database from UI. Operator can insert new table into the specified database, delete the table from the specified database, split the table into two or more tables and normalize them.

Also operator can inset or delete the individual records into from the database tables.

The proposed GUI for Table Management is shown as follows.
 
 
Insert Table

This feature allows the operator insert the new table into the database. On clicking the “Insert Table” button, the following UI screen will be appeared asking more input from the operator.
 
Delete Table

The Delete Table feature of the OSG DCM will allow the operator to delete the specified table from specified database. On clicking the “Delete Table” button on the GUI, it pos up the following UI screen asking more information from the operator to process the query.
 
Insert Entry and Delete Entry

The Insert Entry and Delete Entry features of DCM allow the operator insert the new entry (new column) into the specific record or delete the entry (column) from the list of existing columns from the record. On clinking the “Insert Entry” or “ Delete entry” button on the GUI, the following UI screen will be appeared for additional input from the operator.
 
Table Merge

Using this feature operator can merge two tables into single table in specified database. The user interface for this feature is under design.

Table Split

Using this feature of DCM, operator will be allowed to split the table in specified database into two ore more table for easy of transactions. The UI screen for this feature is under design.
 
Index Map

This feature of DCM allows the operator to map the index of the one table with index of the other record, so that operator can perform the operations on both the table using one query. This is purely for administrator use only. The user interface for this feature is under design.

Utilities

The DCM also provides the other utilities such as exporting the database table into file in specified format such as CSV or txt format. And also it will provide the felicity where operator can import the data from the external files such as CSV or txt into specified database tables.

Database Export

This is one of the crucial aspects of the entire application design. Using this feature, operator can export the entire database from all tables into a specified file. This exported file can be taken as backup of entire database instead of taking the database itself as backup, which is more error prone. On clicking the “Database Export” button, it brings up the following UI asking for more input from the operator.
 
Database Import

This is also one of the most crucial aspects of the entire application design. Using which, operator can import the complete database from either CSV file or from a plain text file, which is being exported to. In other words, if the complete database has been exported already, operator will be creating new database along with complete data. In other words, operator can restore the data, which is taken as backup by exporting the data. In this case also, operator can import the entire database if it is already exported, or operator can import the records into selected tables in the database. If the database is partially exported, the full database import is not allowed. But partial database import is allowed from the full database exported file.
 
Test Process

The entire DCM Tool can be tested using the test database, performing each and every function of DCM executes on the test data available in the test database.

Data Base cleaning

The Data base cleaning function of the DCM can be executed by finding the tables with duplicate values. The DCM once installed and connected to the specified user in the oracle database, the DCM when the user click on the find duplicates part then DCM pop ups the message returning the table name and row ids of the duplicate.
 
Table Management

The Table Management part of the DCM is also can be tested on a test database. The different options are provided to perform the DML operations. When the user presses the insert table option the DCM pops up another detailed screen where the user can define the columns of the table and presses ok to define the table in the database.

All the options available in the DCM should be tested manually on the test database before implementation of the DCM. Hence no separated test cases for each option are provided in the specification. Full flow of all the options needs to be tested on the implementation database.
 
Key Tools and Frame Works
 
 
« Previous
 
© 2005 Objectsoft Group Inc. All Rights Reserved