Common Database Browser & Data Manipulation Tool

Abstract:

Common Database Browser & Data Manipulation Tool which provides an easy to use Web-

Based based common interface for viewing, adding, editing, or deleting entries in almost all the

databases. The user should never have to write SQL to view the data although a SQL window is

provided. All user tables and basic data type fields are available for access in the selected

database.

As technology advances we tend to switch to new ways of accomplishing the same tasks. Faster

machines and better software increase our overall computing and information processing speed

as well as overall comfort and reliability. New solutions sometimes offer expanded functionality

and increased performance. It is a database-independent application that defines a common

interface to provide fast access to SQL database servers.

This tool can be used to build, test, and debug PL/SQL packages, procedures and functions.

Using these users can create and edit database objects such as tables, views, indexes,

constraints, and users. Database Interface's SQL editor provides an easy and efficient way to

write and test scripts and queries, and its powerful data grids provide an easy way to view and

edit data related to any DBMS or RDBMS.

Features:

Connects to any database

Get the meta-data regarding database product, databases, tables

It gives the structure information regarding a database or a table

He can browse through the table data.

It allows us to export or import a database or a table

It allows us to perform different SQL operations (like insert, update, delete etc).

Search for a keyword in the database.

EXISTING SYSTEM & DISADVANTAGES:

In the existing system, all the database application developers are using client

software’s to managing the databases. For example to manage the oracle database,

oracle database vendor providing one stand alone client software. In the same way

all the database vendors are providing their own client software to manage the

databases. So here we have a disadvantage is always we have to install all the client

software’s inside our systems. And in the existing system we have to write queries to

create / alter / drop / delete / insert like operations. In this system we are

disadvantages like installing all client software’s in all system in the organization,

developers have to write all queries at all times and it is a standalone application.

PROPOSED SYSTEM & ITS ADVANTAGES:

Common Database Browser & Data Manipulation Tool is an industry-standard tool for

application development. Using Database Interface, developers can interact with any back end

software (i.e. Oracle, SQL Server, MS-Access, My-SQL etc). The Common Database Browser &

Data Manipulation Tool can be used to build, test, and debug PL/SQL packages, procedures and

functions. Common Database Browser & Data Manipulation Tool users can create and edit

database objects such as tables, views, indexes, constraints, and users. Database Interface's

SQL Editor provides an easy and efficient way to write and test scripts and queries, and its

powerful data grids provide an easy way to view and edit data related to any DBMS/RDBMS

tool.

SOFTWARE REQUIREMENTS&HARDWARE REQUIREMENTS:

SOFTWARE REQUIREMENTS:

Operating System : Windows

Technology : Java/j2ee (JDBC, Servlet, JSP)

Web Technologies : Html, JavaScript, CSS

Web Server : Tomcat

Database : Oracle, MySql, MS-Access

Software’s : J2SDK1.5, Tomcat, Oracle, MySql

HARDWARE REQUIREMENTS:

Hardware : Pentium based systems with a minimum of P4

RAM : 256MB (minimum)

Feasibility 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 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

Economical Feasibility

TECHNICAL FEASIBILITY

The technical issue usually raised during the feasibility stage of the investigation includes

the following:

Does the necessary technology exist to do what is suggested?

Do the proposed equipments have the technical capacity to hold the data required to

use the new system?

Will the proposed system provide adequate response to inquiries, regardless of the

number or location of users?

Can the system be upgraded if developed?

Are there technical guarantees of accuracy, reliability, ease of access and data security?

ECONOMIC FEASILITY:

The computerized system takes care of the present existing system’s data flow and

procedures completely and should generate all the reports of the manual system besides a host

of other management reports.

It should be built as a web based application with separate web server and database

server. This is required as the activities are spread throughout the organization customer wants

a centralized database. Further some of the linked transactions take place in different locations.

Open source software like TOMCAT, JAVA, Mysql and Linux is used to minimize the cost for the

Customer.

Functional Requirements:

The main purpose of functional requirements within the requirement specification

document is to define all the activities or operations that take place in the system. These are

derived through interactions with the users of the system.

1. This system should allow the user to interact with any database.

2. This system should allow the user to view list of all tables which are present in the

current/selected user.

3. This system should allow the user to browse and view the structure of an existing database

object.

4. This system should allow the user to design new database objects

5. This system should allow the user to view entire information about database like database

product name, product version etc. to the user.

6. This system should allow the user to use and implement different kinds of SQL statements.

The result of the SQL statement will be displayed immediately after executing the

statement.

7. This system should allow the user to import any database structure along with data.

8. This system should allow the user to export database structure along with data

9. This system should allow the user to perform some operations on tables of any Database

like create table, alter table, rename table and drop table.

10. This system should allow the user can search any keywords which are related to data in

database.

11. This system should allow the user to view list of all columns which are present in the

selected table.

12. This system should allow the user can change the table settings like display settings etc

13. This system should allow the user can insert data in to any table directly by giving values

from user interface.

14. This system should allow user to perform some operations on columns of any table like

alter column, rename column, drop column and empty column.

15. This system should allow the user to search any keywords which are related to data in

database.

16. This system should allow the administrator will get different types of reports regarding all

the users who are registered in this portal.

Nonfunctional requirements:

Nonfunctional requirements describe user-visible aspects of the system that are

not directly related to functionality of the system.

User Interface and Human factors:

The proposed system should provide a user- friendly interface to database users and

as well as Administrator with ease of use. The user interface must be suitable for easy and

fast data entry from all the tables from a single application. With the help of this interface,

users even without adequate knowledge of all SQL Clients would complete their tasks.

Documentation:

The proposed system requires proper documentation, user level documentation

which helps the users and administrator how to interact with the system. This

documentation includes how to fill the forms provided and get reports that can be

generated by the system. In the proposed system help link provides the user level

documentation. The RAD prepared during analysis phase helps the developer in-order to

develop the system as per client’s requirements. The system design documentation

prepared during development process provides information regarding design goals and

about subsystems into the proposed system which also helps in testing process. In

addition to user level and development level documentation proposed system also

requires technical documentation for maintainers of the system. This technical

documentation includes the port number on which server is running and listening clients

requests and also includes any other configuration required for maintainers.

Hardware Consideration:

Hardware Considerations includes the virtual machine on which the system should

be built. Virtual machine includes operating system and any software components needed.

Virtual machine minimum required for web server is WINDOWS xp system and web

browser is IE 6.0.And the system is compatible with Linux, Unix based systems.

Performance Characteristics:

The proposed system is server applications and server applications are inherently

multi-threaded. Every request creates new thread hence the system supports any no of

concurrent users. Hence this system offers good performance and easy solutions to

problems. This is the static requirement. The Dynamic requirement is system response. As the

proposed system developed using JavaServerPages which reduces response problems.

Error handling and Extreme conditions:

The proposed system should handle exceptions that originate at low level

components and exceptions at high level components. The high level components in

proposed system should handle exceptions that occur while connecting to

databaseserver,IOExceptions etc. The end user should not be bother about exceptions at

low-level. When low level Exceptions arises user should be shown with appropriate

message. Errors that arises during data entry should be handled by performing client side

validations. In the proposed system all client side validations will be done using

JavaScript.

Quality Issues:

Quality issues refers to how reliable and robust should the system be? While

developing the proposed system the developer must be able to guarantee the reliability

transactions so that they will be processed completely and accurately.

The ability of system to detect failures and recovery from those failures refers to

the availability of system. Robustness of system refers to the capability of system

providing information when concurrent users requesting for information.

As the proposed system’s capability of handling various exception it is reliable

and it will be developed using JSP which supports multithreading. Hence it satisfies the

requests from concurrent users. So it is robust.

System modification:

As the proposed is not implementing employee hikes information so it can be

extended and this updation can be done by any developer familiar with specified

hardware and software constraints followed for development of proposed system.

Security Issues:

Security and confidentiality are the top most concerns of the client. The proposed

system should provide the following.

Administrator should be provided with id and password for secured access of

information regarding all users.

Each user should give certain parameters to interact with a databases

System Design:

SYSTEM DESIGN phase follows system analysis phase. Design is maintaining record

proof design divisions and providing a blueprint for the implementation phase. Design is the

bridge between system analysis and system implementation.

System design is transition from a user oriented, document oriented to programmers or

database personnel. The design is a solution, a “how to” approach to the creation a new

system. This is composed of several steps. It provides the understanding and procedural

details necessary for implementing the system recommended in the feasibility study. Design

goes through logical and physical stages of development, logical design reviews the present

physical system, prepare input and output specifications, detail the implementation plan, and

prepare a logical design walkthrough.

OBJECTIVES OF DESIGN

System design is like a blue print for a building, it specifies all the features that are to be

in the finished product. Design states how to accomplish objectives determined in the analysis

phase.

Modules Description:

This application consist four modules:

1. User Module

2. Database level

3. Table level

4. Reports Module

1. User Module:

This module tells all about users who are using UNIVERSAL DATABASE MANAGEMENT

AND APPLICATION DEVELOPMENT INTERFACE as user interface to interact with any

database. While developing applications user need to get the data from the database.

2. Database level Module:

This module tells about the database, this module is categorized into the following

functionalities:

Structure: This module gives the list of all tables which are present in the current/selected

user. This module is used to browse and view the structure of an existing database object. It

can also be used to design new database objects.

Properties:

The properties functionality will gives entire information about database like database

product name, product version etc. to the user.

SQL:

By using this functionality, we can use and implement different kinds of SQL statements.

The result of the SQL statement will be displayed immediately after executing the statement.

Import:

By using this functionality any database structure along with data can be imported in this

portal.

Export:

By using this functionality any database structure along with data can be exported from

this portal.

Operations:

By using this functionality user can do some operations on tables of any Database like

create table, alter table, rename table and drop table.

Search:

By using this functionality user can search any keywords which are related to data in

database.

3. Table level Module:

Structure:

It gives the list of all columns which are present in the selected table. This module is used

to browse and view the structure of an existing database object. It can also be used to design

new database objects

Browse:

By using Browse functionality user can change the table settings like display settings of

information in the portal etc.

SQL:

By using this functionality, we can use and implement different kinds of SQL statements.

The result of the SQL statement will be displayed immediately after executing the statement.

Insert:

By using this functionality user can insert data in to any table directly by giving values from

user interface.

Export:

By using this functionality any database structure along with data can be exported from

this portal.

Operations:

By using this functionality user can do some operations on columns of any table like alter

column, rename column, drop column and empty column.

Search:

By using this functionality user can search any keywords which are related to data in

database.

4. Reports Module:

In this module administrator will get different types of reports regarding all the users who are registered in this portal..