Graphical user interfaces are so called because we use mouse to point at graphical objects such as windows, menus, icons, buttons and other tools on the screen these graphical tools all represent different types of commands the GUI enables us to issue commands to the computer by using visual objects instead of typing commands this is one of the key advantage of the Graphical User Interface it frees us from memorizing and typing text commands

SCOPE OF THE PROJECT

The scope of the project lies in creating an interface in JAVA for a GUI tool and main objective of the project is to develop a GUI tool for Oracle installation
We use three concepts of Java they are SWINGS, JDBC, AWTâ„¢s and also an interface Oracle (SQL PLUS).
A GUI tool would be the best thing to implement as it is more users friendly and must to people who have used a computer have used a GUI in some form or other wise most will not have used a command line interface.

EXISTING SYSTEM

¢ In this we use SQL PLUS as a tool provided by the Oracle for data base installation
¢ Since it provides the user full access to the database ,it is a command line interface
¢ Using SQL PLUS tool we can access through a terminal window on a unix / linux machine or a telnet window on a PC with in the organization.
¢ So people who are not having any computer knowledge it is a difficult task to learn and use it
PROPOSED SYSTEM
¢ In this we provide a GUI tool for Oracle installation
¢ This GUI tool is more user friendly compared to SQL PLUS
¢ Using this GUI tool the user can easily access the tables with in their data base and create, edit or delete data or tables themselves with in their own database
¢ So it is easier to adapt GUI tool for accessing the database rather than command line interface.

MODULE DESCRIPTION

There is only one module in this application Administrator and user.
The user is prompted for a username and password. Once these are entered the user is able to access the tables within their database, and create, edit or delete data or tables themselves with in their database.
The Administrator do not allow the users to access the other databases or to any of the functions used to administer the database it self.

USERS

1. USER
2. ADMINISTRATOR

PRODUCT FEATURES

SQL PLUS tool can be accessed through a telnet window on a PC within the organization. The method of connecting is a command typed in by the user and then prompted for a username and password. Once these are entered the user is able to access the tables within their database and can create, edit , or delete data or tables themselves, with in their own database. The permissions for users to access the database are provided by Administrator who checks the database, modifies etc.

HARDWARE REQUIREMENTS

System:
P III 500 Mz or above
125 MB RAM
100 MB Free Hard Disk space
STD Color monitor

SOFTWARE REQUIREMENTS

Operating System used:
Window XP : In this we have features like digital media support, advanced Networking and communications, advanced mobile computing added with efficient security.
Frond End : JAVA Technology ie both a programming language and a platform

Back End : DBMS is a soft ware tool that enables us to add, view and work with the data in a database.

[attachment=4563]

---

---

[attachment=11959]
ABSTRACT:
Title: A GUI Oracle Interface.
Objective:
Graphical user interfaces are so called because we use mouse to point at graphical objects such as windows, menus, icons, buttons and other tools on the screen these graphical tools all represent different types of commands the GUI enables us to issue commands to the computer by using visual objects instead of typing commands this is one of the key advantage of the Graphical User Interface it frees us from memorizing and typing text commands
SCOPE OF THE PROJECT:
The scope of the project lies in creating an interface in JAVA for a GUI tool and main objective of the project is to develop a GUI tool for Oracle installation
We use three concepts of Java they are SWINGS, JDBC, AWT’s and also an interface Oracle (SQL PLUS). A GUI tool would be the best thing to implement as it is more users friendly and must to people who have used a computer have used a GUI in some form or otherwise most will not have used a command line interface.
 This application can provide the user to create the table with relations also.
 The Normal user has a facility to perform the DDL, DML, DCL Commands of oracle by using the attractive graphical user interface.
 The Admin user has a facility to create the new user and provide the permitions to normal clients in different categories.
INTRODUCTION
Oracle GUI: Oracle can be accessed using Oracle GUI “client” that provides access to the data mining functions and structured templates called Mining Activities that automatically prescribe the order of operations, perform required data transformations, and set model parameters. The user interface also allows the automated generation of Java and/or SQL code associated with the oracle activities. The Java Code Generator is an extension to Oracle JDeveloper. There is also an independent interface:
A graphical user interface (GUI) is a type of user interface which allows people to interact with electronic devices such as computers; hand-held devices such as MP3 Players, Portable Media Players or Gaming devices; household appliances and office equipment with images rather than text commands. A GUI offers graphical icons, and visual indicators, as opposed to text-based interfaces, typed command labels or text navigation to fully represent the information and actions available to a user. The actions are usually performed through direct manipulation of the graphical elements.
The term GUI is historically restricted to the scope of two-dimensional display screens with display resolutions capable of describing generic information, in the tradition of the computer science research at Palo Alto Research Center (PARC). The term GUI earlier might have been applicable to other high-resolution types of interfaces that are non-generic, such as videogames, or not restricted to flat screens, like volumetric displays.
SYSTEM ANALYSIS
The first step in developing anything is to state the requirements. This applies just as much to leading edge research as to simple programs and to personal programs, as well as to large team efforts. Being vague about your objective only postpones decisions to a later stage where changes are much more costly.
The problem statement should state what is to be done and not how it is to be done. It should be a statement of needs, not a proposal for a solution. A user manual for the desired system is a good problem statement. The requestor should indicate which features are mandatory and which are optional, to avoid overly constraining design decisions. The requestor should avoid describing system internals, as this restricts implementation flexibility. Performance specifications and protocols for interaction with external systems are legitimate requirements. Software engineering standards, such as modular construction, design for testability, and provision for future extensions, are also proper.
Many problems statements, from individuals, companies, and government agencies, mixture requirements with design decisions. There may sometimes be a compelling reason to require a particular computer or language; there is rarely justification to specify the use of a particular algorithm. The analyst must separate the true requirements from design and implementation decisions disguised as requirements. The analyst should challenge such pseudo requirements, as they restrict flexibility. There may be politics or organizational reasons for the pseurequirements, but at least the analyst should recognize that these externally imposed design decisions are not essential features of the problem domain.
A problem statement may have more or less detail. A requirement for a conventional product, such as a payroll program or a billing system, may have considerable detail. A requirement for a research effort in a new area may lack many details, but presumably the research has some objective, which should be clearly stated.
Most problem statements are ambiguous, incomplete, or even inconsistent. Some requirements are just plain wrong. Some requirements, although precisely stated, have unpleasant consequences on the system behavior or impose unreasonable implementation costs. Some requirements seem reasonable at first but do not work out as well as the request or thought. The problem statement is just a starting point for understanding the problem, not an immutable document. The purpose of the subsequent analysis is to fully understand the problem and its implications. There is no reasons to expect that a problem statement prepared without a fully analysis will be correct.
The analyst must work with the requestor to refine the requirements so they represent the requestor’s true intent. This involves challenging the requirements and probing for missing information. The psychological, organizational, and political considerations of doing this are beyond the scope of this book, except for the following piece of advice: If you do exactly what the customer asked for, but the result does not meet the customer’s real needs, you will probably be blamed anyway.