Final DBJExplorerDocumentation

DB JExplorer
AN INDUSTRIAL MINI PROJECT REPORT ON

DB JEXPLORER
SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS
FOR THE AWARD OF THE DEGREE OF
BACHELOR OF TECHNOLOGY
IN
INFORMATION TECHNOLOGY
BY
1.CH.Tejaswini(06U51A1230).
2.V.HarithaNaga(06U51A1242).
3. R.Jayasree (06U51A1210).
UNDER GUIDENCE OF
V.ANAND
PROFESSOR ASSOCIATE
DEPARTMENT OF INFORMATION TECHNOLOGY

DRK COLLEGE OF ENGINEERING AND TECHNOLOGY
(Affiliated to JNTU, Hyderabad)
Bowrampet (V), Via Air Force Academy,
Hyderabad-500 043.
2009
1
DB JExplorer
DRK COLLEGE OF ENGINEERING AND TECHNOLOGY

(Affiliated to JNTU- Hyderabad)
HYDERABAD, AP
2009
CERTIFICATE
This is to certify that the project entitled “DB JExplorer” is the bonafide
work carried out by CH.Tejaswini, V.Haritha Naga, R.Jayasree bearing roll no
06U51A1230,06U51A1242,06U51A1210 in partial fulfillment for the award of
degree of Bachelor of technology during the academic year 2009-2010.
Project Guide Head of the

department
V.Anand Mr. Rajasekar
External examiner
2
DB JExplorer
ACKNOWLEDGMENTS
We are extremely grateful to Mr. M.Rajasekar, Head of Department for

Information Technology, DRK College of Engineering and Technology.
Our heart full gratitude to my guide V.Anand for his valuable suggestions
and guidance in the preparation of the project
We thank one and all of team for the cheerful encouragement and unstinted
support rendered to us by their professional knowledge for the successful
completion of project.
We will be failing in duty if we do not acknowledge with grateful thanks to

the authors of the references and other literatures referred to in this project.
Lastly but not the least, we express our thanks to all staff members and
friends for all the help and co-ordination extended in bringing out this project
successfully in time.
By Project Associates
1.V.HarithaNaga(06U51A1242).
2.CH.Tejaswini(06U51A1230).
3. R.Jayasree (06U51A1210).
3
DB JExplorer
ABSTRACT
Objective:
The DB JExplorer is an interface from which requested information can be
accessed from a database. If you are requesting that information from a SQL
database (or from a database accessed via ODBC), your query must be written
using the Structured Query Language (SQL). The SQL is not difficult to learn, but
mastering the fine points of creating and retrieving data with SQL can take quite a
while. Since the db Jexplorer eliminates the need to understand SQL, it can get you
building effective queries right away.
The JExplorer has been designed to meet the needs of individuals with little
or no query background, as well as, the needs of experienced SQL professionals.
If you are new to querying, you will enjoy the way the JExplorer helps you
create queries. By answering a few questions on a set of sequential tabs, you'll give
the program all the information needed to generate a query that fits your needs. The
program will do all the work for you.
If you are an SQL professional, you will appreciate the facility that enables
you to fine-tune the queries that the JExplorer generates. If you are more
comfortable writing your own SQL queries, you will find it easy to enter the queries
directly or even paste them in from another source.
The DB JExplorer can be a powerful tool for many of your information

gathering needs.
The DB JExplorer can only access data stored in an ODBC data source. Any
SQL or other type of database mentioned in the query topics must be accessed
through an ODBC data source.
4
DB JExplorer
Why use a query

Query files provide a means of off-loading much of the data generating
tasks normally performed by DB Jexplorer on to an SQL. The set of data returned
represents a subset of the actual data in the database - only the data you specifically
need.
If you are an experienced SQL programmer, the DB JExplorer allows you to

reuse your existing queries, quickly and easily. All of your existing queries become
convenient query files that you can use to design reports with DB JExplorer.
The DB JExplorer supports powerful SQL pass-through reporting, it does

not support the full SQL language or allow you to edit every part of an SQL
statement. When using the DB JExplorer to create data sets on which to base your
reports, you get all of the power of SQL, including complex sorts, and aggregate
functions.
Using the DB Jexplorer
The JExplorer has two primary uses:

1. Designing and developing data sets for building reports, and
2. Retrieving and analyzing current information on an "as needed" basis to facilitate
informed decision making.
5
DB JExplorer
Index
1 Introduction 8
1.1 About the organization 8
1.2 Existing system 12
1.3 Drawbacks of the existing system 12
2 System Analysis 14
2.1 Problem Definition 17
2.2 Problem System 18
2.3 Selection of Software Structure 21
2.4 Selection of Hardware Structure 21
3 Software Requirements Specification 22
3.1 Introduction 22
3.2 Overall Description 26
3.3 System Features 26
3.4 External Interface Requirement 36
3.5 Other Requirement 37
3.6 Advantage 41
4 System Design 41
4.1 Design Methodology 41
4.2 UML Diagrams 43
4.3 Database Design 68
4.4 Input Design 70
5 System Implementation 82
5.1 System Testing 85
6 Documentation 93
6.1 How to Operate the Package 93
7 Future Scope and Conclusion 95
8 References 97
6
DB JExplorer
9 Bibliography 98
7
DB JExplorer
1. Introduction
1.1 Organizational Profile:
LiveTech, a software development and consulting company, as one of the fast
developing firm mainly specialized in IT and IT Enabled Services sector training
and consultancy. LiveTech is a global one stop-shop to meet all HR requirements-
senior-level Search, Database Selection, Turn-key Recruitment, On-site sourcing
and corporate training.
The spirit of LiveTech has been largely defined and embodies by the dedicated and
tireless pursuit of excellence by our Principal Consultants. Each of them is high in
their senior management experience skills having not only the specialized Skills
that clients need, but also the ability to understand the bigger picture.
We have a vast database, which we do get from Ads and Headhunting, which is of
administrative, Communications, Engineering, Information Systems and
Technology and Computer Security.
We partner with organizations to unleash human potential, enhancing the net worth
of their human capital. We bring passion and professional rigor to address stated as
well as latent needs of our customers. Our Customers will experience us as warm,
deeply human and trustworthy.
Manpower Outsourcing Services/Corporate Training
LiveTech delivers IT resources to esteemed organizations quickly and efficiently

by giving you the Brainpower of highly trained IT consultants.
We offer our software services in multi-technology and in multi-business domains
that almost covers the major spectrum of Information Technology. The unit has
wide range of skill set resources. The companies’ scope of ‘’The Analysis, design
8
DB JExplorer
and development of software and the manpower outsourcing services’’ and with the
quality advantage.
One of the major strengths of the unit that contributed for the fast growth is its
scalability of the operations, which is directly linked with the sourcing of suitable
manpower and the HR policies of the company.
We have an established HR department headed by a well-experienced professional

in the area. The department is on continuous scouting for the best software
professionals in different technical domains, for regular recruitment.
We are interested in sharing our efforts, and can offer our manpower outsourcing
services to meet the requirement of skilled personnel to your esteemed organization,
either on contract or on consultancy basing on your condition,
A Vision of Excellence
Given the mix of collective skills & experience, Commitment to deadlines and a
strong Culture of ethics. LiveTech has been able to grow at a pace of over 100%
every year since inception LiveTech has ably adapted to the fast-changing business
environment and customer Expectations, and has built a 70 plus person strong
organization.
The company is supported by a dynamic second rung of consultants. In keeping

with the current industry Requirements, LiveTech has developed a mix of
professionals with domain and functional experience, which act, as a like-minded
sounding board to the customer-who could be an organization or a candidate. The
educated approach provides a platform for the customer to identify the necessary
competitive edge.
LiveTech team-based work culture ensures that employees have the opportunity to
learn, develop new skills or skills or pick up new competencies relevant for the
company’s growth.
9
DB JExplorer
LiveTech respects the stringent expectations of highly competitive, new economy

firms who value commitment and quality from their business partner’s. LiveTech
strives To meet their expectations and is proud to be associated with such clients.
LiveTech Backed by strong entrepreneurs with a knack for identifying

Opportunities. Where they are quick to notice the shortcomings of existing HR
consulting firms and the unique manpower Needs of the booming IT sector. Our
vision has led to the creation of a sustained learning culture, which has generated
rich dividends to its own and clients alike.
Services:
As any HR Manager knows, the most important resource of his / her organization is
the Human resource their core foundation and backbone, Human resource
represents the single most costly asset, consuming up to 40% of total operating
costs for most organizations.
The scenario has become all the more complex in the last decade with global
opportunities, rapid growth and extreme competition. Good human resources are
also becoming increasingly difficult to hire, cultivate and retain.
Business needs and deliverables have evolved in a manner that demand flexible
recruiting options, It is imperative that your organization has suitable processes in
place for proper functioning & work satisfaction levels.
LiveTech is a one – stop solution provider who can help modern organizations to
overcome their business challenge. LiveTech understands the complexity of human
resource issues presented by the ever-changing global economy.
Staff Augmentation is “the “answer when you wish to maximize control and
manage your own project, but need experienced professionals to follow your Lead.
Keeping our consultants ahead of the technology curve is the cornerstone of our
10
DB JExplorer
Methodology. The utilization of various training methods, certification programs,

and development seminars assures the Excellence of our consultants. LiveTech
provides System Architects, Project managers, Project Leaders, and programmers
and functional consultants in the areas of:
 Microsoft Technologies
 Java Technologies
 ERP
 Databases
 Data Warehousing
 Testing
 Staffing Process
LiveTech 10-step fulfillment process is the culmination of experience in the IT

talent industry.
Permanent Staffing
LiveTech is a skilled and knowledgeable recruiter of Executive talent.

LiveTech have the ability to understand the uniqueness of a position and devise
appropriate recruitment strategy. This includes trying out fresh ideas. Out-of-the-
box thinking and flexibility to meet the exact recruitment of the client.
LiveTech follows a methodical process in its executive search practice. Based on

the given brief, LiveTech conducts a search for top-notch candidates from its rich
database, pre-screens him/her, sets up interviews (at LiveTech office or the
client’s), and continues the process till the client organization finds the right
individual. This option includes a Service Level Agreement with the replacement
guarantee, if the selects candidates do not mat up to expectations.
11
DB JExplorer
LiveTech has evolved with the changing needs of the industry, globally and locally,
and has built solid and far-reaching relationships with clients and candidates. The
firm has built name recognition and a reputation for its grasp of cultural factors,
changing demographics and professional environments.
The preeminent stringent practice adopted to recruit candidates for our clients
encompasses.
 Executive Search
 Campus Selection
 Research mapping
 Generic Resourcing
Our Clients:
In Touch Technologies ltd, Hyderabad
Lara Technologies, Bangalore
Liberty Solutions, Hyderabad
Bio-Minds, Hyderabad
1.2 Existing System

The purpose of this project is to develop an efficient and system based
information retrieval package for various information.
1.3 Drawbacks of the existing System:
The following observations are made in the existing system
 In the existing system each and every query need to be processed by the user.
 A mistyped query yields an error and the query need to be retyped again.
 It may be confusing for the users when they are processing the aggregate
functions and some SQL Expressions. There may be a chance of making mistakes.
12
DB JExplorer
The proposed system is looking for a solution to overcome the above

limitations. Hence the system is studied to solve the above problems.
Need of the product

 The proposed system is user friendly and it can be used in a multi user
environment.
 Increases the efficiency of the information retrieved from the database.
 There won’t be any mistyping of the queries because, it automatically generates

a query according to the user specification.
 Ease of retrieval of information.
13
DB JExplorer
2. System Analysis
 Analysis is about predicting the future – not documenting the past.

 How do we do this?
o Recognize that a target may be viewed as a dynamic system
o Systems may be analyzed statically or dynamically
o Systems need to be represented as separate functional and physical
models.
o System functions change slowly with time while physical elements
may change.
o dramatically
 The model provides evidence of how well the target is understood.
 The model is reverse-engineered from multi-source, sampled data.
 Total analysis is never completed.
Systems Analysis Phase

Work performed
by/
Systems Analyst
deliverables written
by
System Specification: everything about what the
Deliverables proposed system will do, nothing about how it is to
be built
Audiences who 1. Sponsoring users
read, understand, 2. Chief programmer
and accept the (or Software Architect
deliverables or Lead developer
14
DB JExplorer
System Analysis is a process of examining the current system in order to

develop the software design tool through better procedures and methods. It is the
process of gathering and interpreting facts, diagnosing the problems and using the
information to recommend approaches in the system.
System analysis is done to understand the problem, which the new system is
going to solve. Such analysis typically requires a thorough understanding of
existing system, and the part, which must be automated. Understanding the existing
system is usually the starting activity in problem analysis. The goal of this activity
is to understand the requirement of the new system that is to be developed.
The major steps followed in System Analysis are:

• Problem evaluation and synthesis.
• Proposed System.
• Software Requirements Specification.
• Feasibility study.
Feasibility Study
All projects are feasible given unlimited resources and infinite time. But in
reality both resources and time are scare. Projects should confirm to time bounds
and should be optimal in their consumption of resources. This places a constant
approval of any project. After problem is clearly understood and the solutions are
proposed the next step is the part of system analysis. The main objective of this
study is to determine whether the proposed system is feasible or not.
Feasibility as applied to our system pertains to the following areas.

 Operational feasibility
 Technical feasibility
 Economical feasibility
15
DB JExplorer
Operational feasibility
Operational feasibility is willingness and ability of the employers in the

organization to use and support the proposed system. As concerned to the
organization the staff working here are willing to use the proposed system. So the
proposed system is operationally feasible.
The proposed system will no way interior than the existing manual system
and it yields better results than the manual system. This system will give good
support and makes the service easy because
 The system has a user interface enabling an easier usage of the software.
 No special training is necessary for users to use this system.
Technical feasibility
A study of resource availability that may affect to achieve an acceptable

system. The technical feasibility is frequently the most difficult area to ensure at
this stage. It is essential that the process of analysis and definition to be conducted
in parallel with an assessment of technical feasibility.
The consideration that is normally associated with technical feasibility

includes the resources availability of the organization where the project is to be
developed and implemented. By taking these into consideration, the resources
available at Nutrine Confectionery Company Private Ltd were observed and found
that the company has enough resources to develop any kind of project.
16
DB JExplorer
Economic feasibility
Economic feasibility is concerned with the cost savings, increased profits and
reductions in effort. It shows how much beneficial is the new development system
over the existing system.
Even though project development is some what cost in the long term the
system will reduce human work and it becomes more economical. The benefits of
the development system are
 Reduced human effort

 Increases in performance
 Reliable, accurate information is available
 Increased speed of processing
 Proper maintenance and easy retrieval of data.
2.1 Problem Definition
The DB JExplorer Designer

17
DB JExplorer
gathering needs.
2.2 Proposed System

To overcome the above said limitations with the existing system, the need of
a new system arises, which should be more advantageous than the existing system.
Advantages of the proposed system
environment.

The DB JExplorer Designer

18
DB JExplorer
gathering needs.
Why use a query

Query files provide a means of off-loading much of the data generating
tasks normally performed by DB Jexplorer on to an SQL. The set of data returned
represents a subset of the actual data in the database - only the data you specifically
need.
If you are an experienced SQL programmer, the DB JExplorer allows you to

reuse your existing queries, quickly and easily. All of your existing queries become
convenient query files that you can use to design reports with DB JExplorer.
19
DB JExplorer
The DB JExplorer supports powerful SQL pass-through reporting, it does

not support the full SQL language or allow you to edit every part of an SQL
statement. When using the DB JExplorer to create data sets on which to base your
reports, you get all of the power of SQL, including complex sorts, and aggregate
functions.
Using the DB Jexplorer

The JExplorer has two primary uses:
1. Designing and developing data sets for building reports, and
2. Retrieving and analyzing current information on an "as needed" basis to facilitate
informed decision making.
Jexplorer Reports and Query Data Sets

Jexplorer Reports allows you to design a report based on a query data set
rather than tables and fields. Since the query contains a predefined set of data, the
tables and fields necessary for the report are already included.
The set of data produced by the SQL query works just like a database table
when you design your report. The name of the query, along with fields it accesses,
appear in the Text box. Aggregate functions and SQL expressions act like fields,
providing data values corresponding to each record in the SQL query.
Data Analysis and Decision Making

You may not always need to produce finished reports based on your data;
sometimes you just need numbers in a hurry (to prepare for a meeting, to help make
projections, etc.). The JExplorer makes it easy to get the information you need.
Sometimes you may need to retrieve the same data on a recurring basis (weekly,
every month end, etc.). By setting up and saving a single query, you can retrieve
updated data quickly, whenever you need it, with minimal effort.
20
DB JExplorer
2.3 Software and Hardware Requirements
The user is expected to ensure that the minimum requirements for running
the product are satisfied. The hardware and software environment in which this
product was developed is specified. It is necessary to make sure that the hardware
and software the consumer uses is compatible to the specification given below.
Hardware Requirements
Computer : Assembled
Processor : Pentium 80386 microprocessor or higher
Main Memory : 128 MB or higher
Hard Disk : 4.3 GB or higher
Floppy Drive : 3 ½ inch
Monitor : SVGA color monitor
Mouse : 2 or 3 button mouse
Keyboard : 108 keys or higher
Software Requirements
Operating System : Windows 2000
Backend : MS-Access
Front-end : Java, Servlets, JSP, HTML, and Java Script.
Web Server : Tomcat 4.1.29
21
DB JExplorer
3. Software Requirements Specification
3.1 Introduction
Java
Initially the language was called as “oak” but it was renamed as “Java” in 1995.
The primary motivation of this language was the need for a platform-independent
(i.e., architecture neutral) language that could be used to create software to be
embedded in various consumer electronic devices.
 Java is a programmer’s language.
 Java is cohesive and consistent.
 Except for those constraints imposed by the Internet environment, Java gives
the programmer, full control.
Finally, Java is to Internet programming where C was to system programming.
Importance of Java to the Internet
Java has had a profound effect on the Internet. This is because; Java expands
the Universe of objects that can move about freely in Cyberspace. In a network, two
categories of objects are transmitted between the Server and the Personal computer.
They are: Passive information and Dynamic active programs. The Dynamic, Self-
executing programs cause serious problems in the areas of Security and probability.
But, Java addresses those concerns and by doing so, has opened the door to an
exciting new form of program called the Applet.
Java can be used to create two types of programs:
Applications and Applets:
An application is a program that runs on our Computer under the operating
system of that computer. It is more or less like one creating using C or C++. Java’s
ability to create Applets makes it important. An Applet is an application designed to
be transmitted over the Internet and executed by a Java –compatible web browser.
An applet is actually a tiny Java program, dynamically downloaded across the
22
DB JExplorer
network, just like an image. But the difference is, it is an intelligent program, not
just a media file. It can react to the user input and dynamically change.
Swing
Swing is a large set of components ranging from the very simple, such as labels,
to the very complex, such as tables, trees, and styled text documents. Almost all
Swing components are derived from a single parent called JComponent which
extends the AWT Container class. Thus, Swing is best described as a layer on
top of AWT rather than a replacement for it. Figure 1.2 shows a partial
JComponent hierarchy. If you compare this with the AWT Component hierarchy
of figure 1.1 you will notice that for each AWT component there is a Swing
equivalent with prefix “J”. The only exception to this is the AWT Canvas class,
for which JComponent, JLabel, or JPanel can be used as a replacement (in section
2.8 we discuss this in detail). You will also notice many Swing classes with no
AWT counterparts.
Figure 1.2 represents only a small fraction of the Swing library, but this fraction
consists of the classes you will be dealing with most. The rest of Swing exists to
provide extensive support and customization capabilities for the components
these classes define.
23
DB JExplorer
MVC architecture
MVC is a well known object-oriented user interface design decomposition that

dates back to the late 1970s. Components are broken down into three parts: a
model, a view, and a controller. Each Swing component is based on a more
modern version of this design. Before we discuss how MVC works in Swing, we
need to understand how it was originally designed to work.
24
DB JExplorer
Client Server
Over view:
With the varied topic in existence in the fields of computers, Client Server
is one, which has generated more heat than light, and also more hype than reality.
This technology has acquired a certain critical mass attention with its dedication
conferences and magazines. Major computer vendors such as IBM and DEC, have
declared that Client Servers is their main future market. A survey of DBMS
magazine reveled that 76% of its readers were actively looking at the client server
solution. The growth in the client server development tools from $200 million in
1992 to more than $1.2 billion in 1996.
Client server implementations are complex but the underlying concept is
simple and powerful. A client is an application running with local resources but
able to request the database and relate the services from separate remote server. The
software mediating this client server interaction is often referred to as
MIDDLEWARE.
The typical client either a PC or a Work Station connected through a
network to a more powerful PC, Workstation, Midrange or Main Frames server
usually capable of handling request from more than one client. However, with some
configuration server may also act as client. A server may need to access other server
in order to process the original client request.
25
DB JExplorer
The key client server idea is that client as user is essentially insulated from
the physical location and formats of the data needs for their application. With the
proper middleware, a client input from or report can transparently access and
manipulate both local database on the client machine and remote databases on one
or more servers. An added bonus is the client server opens the door to multi-vendor
database access indulging heterogeneous table joins.
What is Client Server?
Two prominent systems in existence are client server and file server
systems. It is essential to distinguish between client servers and file server systems.
Both provide shared network access to data but the comparison dens there! The file
server simply provides a remote disk drive that can be accessed by LAN
applications on a file by file basis. The client server offers full relational database
services such as SQL-Access, Record modifying, Insert, Delete with full relational
integrity backup/ restore performance for high volume of transactions, etc. the client
server middleware provides a flexible interface between client and server, who does
what, when and to whom.
3.2 Overall Description
3.3System Features
Security
Every time you that you download a “normal” program, you are risking a
viral infection. Prior to Java, most users did not download executable programs
frequently, and those who did scan them for viruses prior to execution. Most users
still worried about the possibility of infecting their systems with a virus. In addition,
another type of malicious program exists that must be guarded against. This type of
program can gather private information, such as credit card numbers, bank account
balances, and passwords. Java answers both these concerns by providing a
“firewall” between a network application and your computer.
26
DB JExplorer
When you use a Java-compatible Web browser, you can safely download
Java applets without fear of virus infection or malicious intent.
Portability
For programs to be dynamically downloaded to all the various types of
platforms connected to the Internet, some means of generating portable executable
code is needed .As you will see, the same mechanism that helps ensure security also
helps create portability. Indeed, Java’s solution to these two problems is both
elegant and efficient.
The Bytecode
The key that allows the Java to solve the security and portability problems is
that the output of Java compiler is Bytecode. Bytecode is a highly optimized set of
instructions designed to be executed by the Java run-time system, which is called
the Java Virtual Machine (JVM). That is, in its standard form, the JVM is an
interpreter for bytecode.
Translating a Java program into bytecode helps makes it much easier to run
a program in a wide variety of environments. The reason is, once the run-time
package exists for a given system, any Java program can run on it.
Although Java was designed for interpretation, there is technically nothing
about Java that prevents on-the-fly compilation of bytecode into native code. Sun
has just completed its Just in Time (JIT) compiler for bytecode. When the JIT
compiler is a part of JVM, it compiles bytecode into executable code in real time,
on a piece-by-piece, demand basis. It is not possible to compile an entire Java
program into executable code all at once, because Java performs various run-time
checks that can be done only at run time. The JIT compiles code, as it is needed,
during execution.
Java Virtual Machine (JVM)
Beyond the language, there is the Java virtual machine. The Java virtual
machine is an important element of the Java technology. The virtual machine can be
embedded within a web browser or an operating system. Once a piece of Java code
is loaded onto a machine, it is verified. As part of the loading process, a class loader
is invoked and does byte code verification makes sure that the code that’s has been
27
DB JExplorer
generated by the compiler will not corrupt the machine that it’s loaded on. Byte
code verification takes place at the end of the compilation process to make sure that
is all accurate and correct. So byte code verification is integral to the compiling and
executing of Java code.
Java programming uses to produce byte codes and executes them. The first
box indicates that the Java source code is located in a. Java file that is processed
with a Java compiler called javac. The Java compiler produces a file called a. class
file, which contains the byte code. The Class file is then loaded across the network
or loaded locally on your machine into the execution environment is the Java virtual
machine, which interprets and executes the byte code.
Java Architecture
Java architecture provides a portable, robust, high performing environment
for development. Java provides portability by compiling the byte codes for the Java
Virtual Machine, which is then interpreted on each platform by the run-time
environment. Java is a dynamic system, able to load code when needed from a
machine in the same room or across the planet.
Compilation of code
When you compile the code, the Java compiler creates machine code (called
byte code) for a hypothetical machine called Java Virtual Machine (JVM). The
JVM is supposed to execute the byte code. The JVM is created for overcoming the
issue of
Z-order
Swing components are referred to as lightweights while AWT components are
referred to as heavyweights. The difference between lightweight and
heavyweight components is z-order: the notion of depth or layering. Each
heavyweight component occupies its own z-order layer. All lightweight
components are contained inside heavyweight components and maintain their
28
DB JExplorer
own layering scheme defined by Swing. When we place a heavyweight inside

another heavyweight container it will, by definition, overlap all lightweights in
that container.
What this ultimately means is that we should avoid using both heavyweight and
lightweight components in the same container whenever possible. This does not
mean that we can never mix AWT and Swing components successfully. It just
means we have to be careful and know which situations are safe and which are
not. Since we probably won’t be able to completely eliminate the use of
heavyweight components anytime soon, we have to find ways to make the two
technologies work together in an acceptable way.
The most important rule to follow is that we should never place heavyweight
components inside lightweight containers that commonly support overlapping
children. Some examples of these containers are JInternalFrame, JScrollPane,
JLayeredPane, and JDesktopPane. Secondly, if we use a popup menu in a container
holding a heavyweight component, we need to force that popup to be heavyweight.
To control this for a specific JPopupMenu instance we can use its
setLightWeightPopupEnabled () method.
Alternatively we can call JPopupMenu’s static

setDefaultLightWeightPopupEnabled () method, and pass it a value of false to force
all popups in a Java session to be heavyweight. Note that this will only affect popup
menus created after this call is made. It is therefore a good idea to call this method
early within initialization.
29
DB JExplorer
Platform independence
The most remarkable thing about Swing components is that they are written in
100% Java and do not depend on peer components, as most AWT components
do. This means that a Swing button or text area will look and function
identically on Macintosh, Solaris, Linux, and Windows platforms. This design
eliminates the need to test and debug applications on each target platform.
Swing package overview
javax.swing
Contains the most basic Swing components, default component models,
and interfaces. (Most of the classes shown in Figure 1.2 are contained in
this package.)
javax.swing.border
Classes and interfaces used to define specific border styles. Note that
borders can be shared by any number of Swing components, as they are
not components themselves.
javax.swing.colorchooser
Classes and interfaces supporting the JColorChooser component, used for
color selection. (This package also contains some interesting
undocumented private classes.)
javax.swing.event
The event package contains all Swing-specific event types and listeners.
Swing components also support events and listeners defined in
java.awt.event and java beans.
javax.swing.filechooser
Classes and interfaces supporting the JFileChooser component, used for
file selection.
javax.swing.plaf
Contains the pluggable look-and-feel API used to define custom user
interface components. Most of the classes in this package are abstract.
30
DB JExplorer
They are subclassed and implemented by look-and-feel implementations

such as metal, motif, and basic. The classes in this package are intended
for use only by developers who, for one reason or another, cannot build
on top of existing look-and-feels.
javax.swing.plaf.basic
Consists of the Basic look-and-feel implementation which all look-and-
feels provided with Swing are built on top of. We are normally expected
to subclass the classes in this package if we want to create our own
customized look-and-feel.
javax.swing.plaf.metal
Metal is the default look-and-feel of Swing components. It is the only
look-and-feel that ships with Swing not designed to be consistent with a
specific platform.
javax.swing.plaf.multi
This is the Multiplexing look-and-feel. This is not a regular look-and-feel
implementation in that it does not define the actual look or feel of any
components. Rather, it provides the ability to combine several look-and-
feels for simultaneous use. A typical example might be using an audio-
based look-and-feel in combination with metal or motif. Currently Java 2
does not ship with any multiplexing look-and-feel implementations
(however, rumor has it that the Swing team is working on an audio look-
and-feel as we write this).
javax.swing.table
Classes and interfaces supporting the JTable control. This component is
used to manage tabular data in spreadsheet form. It supports a high
degree of customization without requiring look-and-feel enhancements.
javax.swing.text
Classes and interfaces used by the text components including support for
plain and styled documents, the views of those documents, highlighting,
caret control and customization, editor actions and keyboard
31
DB JExplorer
customization.
javax.swing.text.html
This extension of the text package contains support for HTML text
components. (HTML support was being completely rewritten and
expanded upon while we were writing this book. Because of this our
coverage of it is regretably limited.)
javax.swing.text.html.parser
Support for parsing HTML.
javax.swing.text.rtf
Contains support for RTF documents.
javax.swing.tree
Classes and interfaces supporting the JTree component. This component
is used for the display and management of hierarchical data. It supports a
high degree of customization without requiring look-and-feel
enhancements.
javax.swing.undo
The undo package contains support for implementing and managing
undo/redo functionality.
Figure 1.3 Model-view-controller architecture
<<File figure1-3.gif>>
32
DB JExplorer
1. Model
The model is responsible for maintaining all aspects of the component state.
This includes, for example, such values as the pressed/unpressed state of a push
button, a text component’s character data and information about how it is
structured, etc. A model may be responsible for indirect communication with the
with the view and the controller. By indirect we mean that the model does not
‘know’ its view and controller--it does not maintain or retrieve references to
them. Instead the model will send out notifications or broadcasts (what we
know as events). In figure 1.3 this indirect communication is represented by
dashed lines.
2. View
The view determines the visual representation of the component’s model. This is
a component’s “look.” For example, the view displays the correct color of a
component, whether the component appears raised or lowered (in the case of a
button), and the rendering of a desired font. The view is responsible for keeping
its on-screen representation updated and may do so upon receiving indirect
messages from the model, or direct messages from the controller.
3. Controller
The controller is responsible for determining whether the component should

react to any input events from input devices such as the keyboard or mouse. The
controller is the “feel” of the component, and it determines what actions are
performed when the component is used. The controller can receive direct
messages from the view, and indirect messages from the model.
For example, suppose we have a checked (selected) checkbox in

our interface. If the controller determines that the user has
performed a mouse click it may send a message to the view. If the
view determines that the click occurred on the checkbox it sends a
33
DB JExplorer
message to the model. The model then updates itself and

broadcasts a message, which will be received by the view(s), to
tell it that it should update itself based on the new state of the
model. In this way, a model is not bound to a specific view or
controller, allowing us to have several views and controller’s
manipulating a single model.
Custom view and controller

One of the major advantages MVC architecture provides is the ability to
customize the “look” and “feel” of a component without modifying the model.
Figure 1.4 shows a group of components using two different user interfaces. The
important point to make about this figure is that the components shown are
actually the same, but they are shown using two different look-and-feel
implementations (different views and controllers -- discussed below).
Figure 1.4 Malachite and Windows look-and-feels of the same components
<<File figure1-4.gif>>
Some Swing components also provide the ability to customize specific parts of a
component without affecting the model. More specifically, these components
allow us to define custom cell renderers and editors used to display and accept
34
DB JExplorer
specific data respectively. Figure 1.5 shows the columns of a table containing
stock market data rendered with custom icons and colors. We will examine how
to take advantage of this functionality in our study of Swing combo boxes, lists,
tables, and trees.
Custom models
Another major advantage of Swing’s MVC architecture is the ability customize

and replace a component’s data model. For example, we can construct our own
text document model that enforces the entry of a date or phone number in a very
specific
form. We can also associate the same data model with more than one component
(as we discussed above in looking at MVC). For instance, two JTextAreas can
store their textual content in the same document model, while maintaining two
different views of that information.
Why Client Server
Client server has evolved to solve a problem that has been around since
the earliest days of computing : how best to distribute your computing, data
generation and data storage resources in order to obtain efficient, cost effective
departmental an enterprise wide data processing. During mainframe era choices
were quite limited. A central machine housed both the CPU and DATA (cards,
tapes, drums and later disks). Access to these resources was initially confined to
batched runs that produced departmental reports at the appropriate intervals. A
strong central information service department ruled the corporation. The role of the
rest of the corporation limited to requesting new or more frequent reports and to
35
DB JExplorer
provide hand written forms from which the central data banks were created and
updated. The earliest client server solutions therefore could best be characterized as
“SLAVE-MASTER”.
Time-sharing changed the picture. Remote terminal could view and even change
the central data, subject to access permissions. And, as the central data banks
evolved in to sophisticated relational database with non programmer query
languages, online users could formulate adhoc queries and produce local reports
with out adding to the MIS applications software backlog. However remote access
was through dumb terminals, and the client server remained subordinate to the
Slave\Master.
3.4 External Interface Requirement
Software Interfaces
Development End : Java, Servlets, JSP, HTML, and Java Script,MS-

Access
Web Server : Tomcat 4.1.29
Data Base Server : Oracle10g/OracleXE, Windows
Hardware Interfaces
Processor : Pentium 80386 microprocessor or higher
Main Memory : 128 MB or higher
Hard Disk : 4.3 GB or higher
Floppy Drive : 3 ½ inch
36
DB JExplorer
3.5 Other Requirements
Software Development Life Cycle

The stage of planning the development process involves defining a define, develop,
test, deliver, operate, and maintain a software product. Different lifecycle models
emphasize different aspects of the lifecycle and no single lifecycle model is suitable
for all software products. A lifecycle model that is understood and accepted by all
concerned parties improves project communication and enhances project
manageability, resource allocation, cost control, and product quality.
The Phased Life Cycle Model

The phased lifecycle model represents software lifecycle as a series of successive
activities. Each phase requires well-defined input information, utilizes well-defined
processes and results in well-defined products. The phased model consists of
following phases, they are Analysis, Design, Implementation, System Testing and
Maintenance. This model is sometimes called the Waterfall Chart, the implication
being that the products cascade from one level to another in smooth progression.
Analysis Design Implementation System Maintenance

Testing
Planning,
User Design
needs Details
Definitio Code, debug
n and Test
Integration
&
Acceptance Enhance,
Fix Adapt
Fig 2.5.1 SDLC Chart
37
DB JExplorer
The Analysis Stage consists of Planning and Requirements definition, major

include understanding the customer’s problem, performing A feasibility study,
developing a recommended solution strategy, determining the acceptance criteria
and planning development process. The products of planning are a System
definition and a project plan.
Fig 2.5.2 Analysis Stage
The Software Design follows analysis. Design is concerned with its software
components, specifying relationships among components specifying some structure,
maintaining a record of design decisions and providing blueprint implementation
phase. Design consists of detailed design and Architectural design.
38
DB JExplorer
Fig 2.5.3 Designing Stage

The implementation phase of software development involves translation design
specification into source code, and debugging, documentation and unit testing the
source code. To enhance the quality of the software the methods are structured
control constructs, built in and user defined data types, flexible scope rules
exception handling mechanism, concurrency constructs and separates compilation
modules.
Fig 2.5.4 Implementation Stage
39
DB JExplorer
System Testing involves two kinds of testing integration testing and acceptance
testing. Developing a strategy for integrating the components of a software system
into a functioning whole requires careful planning so that modules are available for
integration when needed. Acceptance testing involves planning and execution of
various tests in order to demonstrate that the implemented system satisfies the
requirements document.
Testing involves selection of test cases on the basis of two methods. Functional
testing, which involves selection test cases for testing the specifications of the
system or the module. Structural testing, which involves testing the internal
structure of the system or module. The goal of the testing is to select the test cases
such that maximum number of errors can be detected.
40
DB JExplorer
Fig 2.5.5 Testing Phase
The Maintenance phase comes after the acceptance by the customer and release of
the system for production work. Maintenance activities include enhancements of
capabilities, adaptation of software to new processing environments, and correction
of software bugs. This project follows the Phased Life Cycle Model or the Water
fall model to a large extent.
3.6 Advantages
environment.
4. System Design
4.1 Design Methodology
The Design Document combines specifications, concepts, analyses,

diagrams, and schematics to convey the technical and operational requirements of
an IT system.
41
DB JExplorer
The System Design Document describes how to transform the

requirements and the functional design into more technical system design
specifications
System Design Phase

Work perforCla by/ Chief programmer
deliverables written (or Software architect
by or Lead developer)
System Architecture: platform choice,
Deliverables database design, program design, user
interface design, etc.
Audiences who read,
understand, and Programmers and
accept the technical specialists
deliverables
1. Purpose of the system

System design document is used to decompose the main system in to sub
Systems. The purpose of this project is to develop an efficient and internet based
information retrieval package for various information Systems.
2. Design Goals
42
DB JExplorer
The basic goal of this document is to subdivide the project into sub Systems
and to give a more appropriate view of the project. The main goal is to automate the
Searching Process.
This in turn implies in order to design each subsystem of the main system to
reach the specific goals.
3. DEFINATION, acronyms, and abbreviations:

All the definitions and acronyms used in RAD are used here.
4. References:
The systematic view of the project is accessed in system design by

Extracting the significant features of the system from requirements elicitation
documentation process i.e. RAD
5. Over view:
The system design document gives a brief over view of the whole
project by subdividing into subsystems in which each subsystem takes it’s own
whole as a main system functionality.
4.2 UML Diagrams
The Uniform Modeling Language (UML) is one of the most exciting tools
in the world of system development today. The UML enables system builders to
create blue prints that capture their vision in a standard, ease – to – understand way
and communicate them to others.
The UML is the brain child of Greedy Booch, James Rumbaugh and
Jacobson. The UML has become the de facto standard in the software industry and
it continuous to evolve.
43
DB JExplorer
The Components of UML
The UML consists of a number of graphical elements that combine to form

diagram. Because it is a language the UML has used for combining these elements.
The purpose of the diagram is to present multiple views of a system and this set of
multiple views is called a model. It is important to note that a UML model describes
what system is supported to do. It doesn’t tell how to implement the system. The
most important diagram of the UML is Class diagram.
Class Diagram
A class is a category or group of things that have similar attributes and common
behaviors. Class diagram provides the representations that developers work from.
Class diagram help on the analysis side too. They enable analysts to talk to clients
in the client’s terminology and then simulate the clients to relieve important details
about the problems they solved.
An example of the UML notation that captures these attributes and
behavior of washing machine is shown below. Rectangle is the icon that represents
the class. It is divided in to three areas. The upper most area contains the name, the
middle area holds the attributes and the lower area shows the operation. A class
diagram consist number of these rectangles connected by two lines that show how
the classes relate to one another.
Object Diagram
Object is an instance of a class – a specific thing that has specific values of
the attributes and behavior.
44
DB JExplorer
Use Case Diagram

A usecase diagram is a description of a system behavior from users
standpoint for system developers, this is a valuable tool. It is a true technique
gathering system requirements from a user’s point of view
Sequence Diagram
Class diagram and Object diagrams represent static information. The UML
Sequence diagram shows the time based dynamic of the interaction.
State diagram
At any given time an object is in a particular state. A person can be a
newborn, infant, adolescent, teenager or adult. This diagram has the start state at the
top and stop state at bottom.
Collaboration Diagram
The elements of a system work together to accomplish the system’s

objectives and a modeling language must have a way of representing this. The
UML collaboration diagram is designed for this purpose.
Component Diagram
The net component diagram is geared expressly toward computer

system .A component diagram contains - approximately enough – components,
interface and relations. Modern software development proceeds as in a component,
which is particularly important in team based development effort.
Activity Diagram
45
DB JExplorer
It is an extension of the state diagram. The activity diagram

highlights the activities. A rounded a rectangle – narrowed and more over shaped
than a state icon represents each activity. An arrow represents the transaction from
one activity to next.
46
DB JExplorer
Deployment Diagram
The UML deployment diagram shows the physical architecture of a

computer based system. It can depict the computer and devices. Show their
connection with one another and show the software that sits on each machine. A
cube represents each computer with interactions between computers drawn as lines
connecting the cubes.
Analysis is the process of transforming a problem definition from a fuzzy

set of facts and myths into a coherent statement of a system’s requirements. The
main objective of the analysis is to capture a complete, unambiguous, and
consistent picture of the requirements of the system and what the system must do to
satisfy the user’s requirements.
The object-oriented analysis (OOA) phase of the unified approach uses

actors and use cases to describe the system from the user’s perspective. The actors
are external factors that interact with the system; use cases are scenarios that
describe how actors use the system. The use cases identified here will be involved
throughout the development process.
The OOA process consists of the following steps:

1. Identify the actors.
2. Develop a simple business process model using UML activity diagram.
3. Develop the use case.
4. Prepare interaction diagrams.
5. Classification-develop a static UML class diagrams.
47
DB JExplorer
Develop use Identify classes,

cases, activity Develop relationships
diagrams Interaction attributes, and
diagrams methods.
Identify Actors
The object oriented analysis process in the Unified Approach (UA).
Identify the actors
The actors are the external factors that interact with the system. To identify the
actor we need to know
 Who is using the system
 Or, in the case of new system, who will be using the system.
48
DB JExplorer
<<DB Administrator>>
<>Actor>>
<<EDP Manager>>
Fig: Actors of the System
49
DB JExplorer
Business Processing Model
During this phase of analysis, processes and the applications that support
them are modeled. These activities would been enhanced and supported by using
the activity diagram. The main idea behind this phase is to get a basic model
without spending too much time in the process. The advantage of developing a
business process model is that it makes you more familiar with the system and
therefore the user requirements and also aids in developing use cases.
For the current system, the activities that the user can do are,
 How the user enters into the system.

 How the user selects the table.
 How the user process the Queries.
 How the user views the reports.
The activity diagram illustrating above activities is shown as in the diagram
50
DB JExplorer
User Logins into

the System Displays the
Tables
Select a table
Select table
Is valid table.
No
Select a Valid Table
Yes from the List.
Displays the
Query Generator
For Mathematical functions
Select the Select the enter the click

OK to
Fields Math ope value Build
Query
Conditional Operators
51
DB JExplorer
Select the select the enter the press ok

to
Field operator value Build
Query
Exit Click on show to display

the records for the generated
query.
52
DB JExplorer
.Use Case Model
Use Cases are scenarios for understanding system requirements. A use case model
can be instrumental in project development, planning, and documentation of system
requirements. A use case is an interaction between users and a system; it captures
the goal of the users and the responsibility of the system to its users. The use-case
model describes the uses of the system and shows the course of events that can be
performed. In other words, it shows a system in terms of its users and how it is
being used from a user point of view. Furthermore, it defines what happens in the
system when the use case is performed.
Use cases and their descriptions for the current applications are.
Use Case Name: Login Form

Displays the Uid’s to the Actor who uses the system.
Use Case Name: CheckValidUser
Checks for whether the user is valid or not.
Use Case Name: Table Form
Displays the tables of the users who logged in.
Use Case Name: SelectForm
Displays the users with a screen to perform some manipulation on the fields they
need.
Use Case Name: Reports

Displays the query generated and prints the appropriate records.
Use case model is shown in the figure.
53
DB JExplorer
Login
Authentication
<<Users with
in the Org>>
View Tables
Query Generator
Records
Use-case model for the System
Interaction Diagrams
54
DB JExplorer
Interaction diagrams are diagrams that describe how groups of objects of

objects collaborate to get the job done. Interaction diagrams capture the behavior of
a single Use Case, showing the pattern of interaction among objects. The diagram
shows a number of example objects and the message passed between those objects
with in the use case. One kind of interaction diagram is sequence Diagram.
Sequence diagrams are an easy and intuitive way of describing the behavior
of a system by viewing the interaction between the system and its environment. A
sequence diagram shows an interaction arranged in a time sequence. It shows the
objects participating in the interaction by their life times and messages they
exchange, arranged in time sequence.
A sequence diagram has two dimensions: the vertical dimension represents
time, the horizontal dimension represents different objects. The vertical line is
called the Object’s lifeline. The lifeline represents the object’s existence during the
interaction. An object is shown as a box at the top of a dashed line, the lifeline.
Each message is represented by an arrow between the lifelines of two
objects. The order in which these messages occur is shown top to bottom on the
page.
The sequence diagram is very simple and has immediate visual appeal. A
sequence diagram is an alternative way to understand the overall flow of the control
of a program.
55
DB JExplorer
Further
Login Form Check Valid User
requests.
User requests to display the Login Form
Login Form displays the uid in the database
User selects the id and enters the password

Login form sends the user
and its password for checking
User is valid
Login form displays connected to SQL.
Sequence Diagram to connect to the data base by supplying appropriate user

and password.
56
DB JExplorer
UML Diagrams
Classification is the process of checking to see if an object belongs to a

category or a class. Classes are an important mechanism for classifying objects. The
chief role of a class is to define the attributes, methods, and applicability of its
instances.
The UML class diagram, also referred to as object modeling, is main static
analysis diagram. A class diagram is a collection of static modeling elements, such
as classes and their relationships, connected as a graph to each other and to their
contents. Class diagrams do not show temporal information. Object modeling is the
process by which the logical objects in the real world are represented by actual
objects in the program. The visual representation of the objects, their relationships,
and their structures is for ease of understanding.
A class is drawn as a rectangle with three components separated by

horizontal lines. The top name compartment holds the class name, other general
properties of the class, such as attributes, are in the middle compartment and the
bottom compartment holds a list of operations.
For the current application classes identified during this phase of analysis are,
 Login Form
 Check Valid User
 Table Form
 Select Form
 Build Table
The attributes identified in the classes are,
57
DB JExplorer
Class Login Form:

 User Id
 Password
Class Table Form:
 Table Names
 Fields
Class Select Form:
 Fields
 Mathematical operations
 Relational operations
 Aggregate functions
 Logical Operators.
The classes along with their attributes and methods identified during this phase
of analysis for the current project are represented in the static UML class diagram.
58
DB JExplorer
Login Form
User Id,
Password
CheckPassword ()
CheckValidUser
IsValid ()
Table form
Tables
, fields
DisplayTableFields ()
SelectForm BuildTable
Fields, math, fields, types

Logical, Relational
operations, aggfun
Build Query() display Table ()
59
DB JExplorer
EA 4.10 1Unregistered
.USECASE DIAGRAM:
Trial Version EA 4.10 Unregistered Trial Version EA 4.10 Unregistered T
EA 4.10 Unregistered Trial Version EA 4.10 Unregistered Trial Version EA 4.10 Unregistered T
ud Use Case Model
EA 4.10 Unregistered Trial Version EA 4.10login

Unregistered Trial Version EA 4.10 Unregistered T
user select
EA 4.10 Unregistered Trial Version EA 4.10 insert

Unregistered Trial Version
database EA 4.10 Unregistered T
explorer
database
EA 4.10 Unregistered Trial Version EA 4.10 delete
Unregistered Trial Version EA 4.10 Unregistered T
60
DB JExplorer
5.2 SEQUENCE DIAGRAM:
E A 4 . 1 s0d I Un t e nr a rc eti ogn sis t e r e d ET Ar ia4l . V1 0e r Us ion rne g is t e r e d ET Ar ia4l . V1 0e r Us ion rn
E A 4 . 1 0 U uns er re g is t e r e d ET Ar ia4l . V1de 0aex taprlUbosar ioesnre rne g is t e r e d ET Ardiaa 4t al b. V1a s0ee r Us ion rn
E A 4 . 1 0 U n r e g is t e r e d ET Ar ia4l . V1 0e r Us ion rne g is t e r e d ET Ar ia4l . V1 0e r Us ion rn

lo g in

v e ri f i c a t i o n
E A 4 . 1 0 U n r e g is t ed irsep l ady oETp tAri oian 4s l . V1 0e r Us ion rne g is t e r e d ET Ar ia4l . V1 0e r Us ion rn
E A 4 . 1 0 U n r e g is t ec hr oeo dse EoTp Atri oian4l . V1 0e r Us ion rne g is t e r e d ET Ar ia4l . V1 0e r Us ion rn
E A 4 . 1 0 U n r e g is t e r e d ET Ar ia4l . V1 0e r Us ion rne gp ise r f to erm r eo pdt i o EnT Ar ia4l . V1 0e r Us ion rn

a c kn o w l e d g e m e n t
E A 4 . 1 0 U n r e g is t e r e d ET Ar ia4l . V1 0estroUsp ion rne g is t e r e d ET Ar ia4l . V1 0e r Us ion rn
E A 4 . 1 0 U n r e g is t e r e d ET Ar ia4l . V1 0e r Us ion rne g is t e r e d 61ET Ar ia4l . V1 0e r Us ion rn

DB JExplorer
5.3 COLLABORATION DIAGRAM:
62
DB JExplorer
5.4 ACTIVITY DIAGRAM
63
DB JExplorer
E A 4.10 U nregistered T rial Version
EA 4.10 U nregistered T rial Version
EA 4.10 U nr
a d Ac tiv ity Dia gra m
EA 4.10 U nr

E A 4.10 U nregistered
sta rt T rial Version
EA 4.10 U nr

EA 4.10 U nr
login

EA 4.10 U nr
dis p la y
option s T rial Version
EA 4.10 U nr

EA 4.10 U nr
s e le c top tions
EA 4.10 U nr

EA 4.10 U nr

EA 4.10 U nr
E A 4.10 U nregistered Tsrial

e le c t Version
ins e rt T rial Version
EA 4.10 Udenregistered
le te
T rial Version
EA 4.10 U nr

EA 4.10 U nr

EA 4.10 U nr

EA 4.10 U nr

pe rform
T rial Version
EA 4.10 U nr
option

EA 4.10 U nr

EA 4.10 U nr
re s pons e

EA 4.10 U nr

EA 4.10 U nr

EA 4.10 U nr
sto p

EA 4.10 U nr

EA 4.10 U nr

EA 4.10 U nr

EA 4.10 U nr
5.5 CLASS DIAGRAM
EA 4.10 U nr

EA 4.10 U nr

EA 4.10 U nr
64
EA 4.10 U nr

EA 4.10 U nr
DB JExplorer
CLASS DIAGRAM1:
65
DB JExplorer
66
DB JExplorer
Data Dictionary
A data dictionary is a catalog- a repository- of the elements in the system.

As the name suggests, these elements center around data and the way they are
structures to meet user requirements and the organization needs. A data dictionary
is a collection of data about data. The basic idea is to provide information on the
definition, structure and the use of the element an organization uses, the data
element is a unit of data that can’t be decomposed.
Data dictionary is used

- To manage the details in the large system.
- To communicate a common meaning for all system elements.
- To document the features of the system.
- To facilitate analysis of the details in order to evaluate characteristics
and determine where system changes could be made.
- To locate errors and omission in the system.
OBJECT ORIENTED DESIGN
Design is the first step in development phase for any engineering product or
system. It may be defined as “the process of applying various techniques and
principles for the purpose of defining a device, a process, or a system insufficient
detail to permit its physical realization”.
Software design is an interactive process through which requirements are

translated into ‘blue print’ for constructing the software. The design is represented
at high level of abstraction.
Designing Classes
67
DB JExplorer
Object-oriented design requires taking the object identified during object-

oriented analysis and designing classes to represent them. Once the classes and their
attributes for the application are identified, the design process begins.
The process ‘Designing Class’ consists the following activities.

1. Apply design axioms to design classes, their attributes, method, associations,
structures and protocols.
Refine and complete the static UML class diagram by adding details to the diagram.
1.1.1. Refine Attributes.
1.1.2. Design methods and the protocols by utilizing a UML activity diagram.
1.1.3. Refine the associations between the classes (if required).
1.1.4. Refine the class hierarchy and design with inheritance (if required).
Iterate and refine.
Object-oriented design axioms
An axiom is a fundamental truth that always is observed to be valid and for

which there is no counterexample or exception. Object-oriented design axioms are,
Axiom 1. The independence axiom: It states that, during the design process, as we
go from requirement and use case to a system component, each component must
satisfy that requirement without affecting other requirements.
Axiom 2. The information axiom: It states to minimize the information content of

the design in order to represent the facts with a minimum complexity and maximum
simplicity.
UML Attribute Presentation:
68
DB JExplorer
The following is the attribute presentation suggested by UML:

Visibility name: type-expression=initial value
Where visibility is one of the following:
+ Public visibility (accessibility to all classes).

# protected visibility (accessibility to subclasses and operations of the class).
- Private visibility (accessibility only to operations of the class).
Refining Attributes for the system

In this phase of designing, the attributes identified classes are refined as shown.
Refining attributes for the LoginForm Class:
During the analysis phase the attributes identified for this class are
• Login User
• Password
• Total users
The refined attributes after adding information of visibility, implemented type
• +Login User: String

• +Password: String
4.3 Database Design
69
DB JExplorer
The goal of data design is to generate a set of relation schema’s that allows
us to store information without unnecessary redundancy and allows us to retrieve
information easily. We can achieve optimization, ease of use in maintenance by
designing the database using relational model in which data is stored in the form of
tables and their exists a relation between or among the tables.
The design objectives must be

• To reduce redundancy.
• To arrive at loss-less join.
• To reduce the time as compared to the present system.
• To reduce the number or errors.
NORMALIZATION
Normalization is a step-by-step reversible process of converting given

collection of relations to some desirable form in which the relations have a
progressively simpler and more regular structure. No information is lost in
normalization process.
First Normal Form: a relation R is said to be in 1NF if all underlying

domains contain atomic values only.
Second Normal Form: a relation R is said to be in 2NF if and only if it is in

1NF and every non-key attribute is irreducibly dependent on the primary key.
Third Normal Form: a relation R is said to be in 3NF if and only if it is in

2NF and every non-key attribute is non-transitively dependent on the primary key.
70
DB JExplorer
In this project you can enter in to any login and can access any of the tables
as you like. Here you are not creating any tables to store information, the concept of
Normalization does not play a major role in this system.
User Interface Design:
A graphical user interface (GUI) uses icons to represent objects, a pointing

device to select operations, and graphic imaginary to represent relationships.
Once the analysis is complete, developers can start designing the user
interfaces for the objects and determining how these objects are to be presented.
The main goal of the user interface is to display and obtain needed information in
an accessible, efficient manner. The design of the software’s interface, more than
any thing else, affects how a user interacts and therefore experiences an application.
It is important for a design to provide users the information the they need and
clearly tell them how to successfully complete the task. A well-designed UI has
visual appeal that motivates users to use the application. In addition it should use
the limited screen space efficiently.
71
DB JExplorer
4.4 Input Design
72
DB JExplorer
73
DB JExplorer
74
DB JExplorer
75
DB JExplorer
76
DB JExplorer
77
DB JExplorer
78
DB JExplorer
79
DB JExplorer
80
DB JExplorer
81
DB JExplorer
82
DB JExplorer
83
DB JExplorer
5. System Implementation
Introduction:
Testing is performed after the coding phase. It is a major software quality
control measure employed during software development. It’s basic function is to
detect the errors in the software. The goal of the testing is to uncover required
design and coding errors in the programs. The input phase of the testing is the
written code. Testing is performed with unit testing which detects errors in each
module. These modules are integrated into subsystems and tested for integration.
Eventually the overall system is tested which is called system testing. At the end,
the system is tested with the real data at the place of installation called as
acceptance testing.
Testing involves selection of test cases on the basis of two methods.
Functional testing, which involves selection test cases for testing the specifications
of the system or the module. Structural testing, which involves testing the internal
structure of the system or module. The goal of the testing is to select the test cases
such that maximum number of errors can be detected by making use of minimum
number of test cases. For this reason we generate the test cases on the basis of the
test criteria.
A criterion is valid if any error in the software can be revealed by the same
test case satisfying the criteria.
Testing Process:
Testing performs a very critical role for quality assurance and
ensuring the reliability of the software. During testing, the program to be tested is
executed with a set of test cases and output of the program for the test case is
evaluated to determine if the program is performing as it is expected to.
• Testing is a process of executing a program with the intent of finding errors.
84
DB JExplorer
• A good test case is one that has a high probability of finding as yet
undiscovered error.
• A successful test is one yet uncovers as yet-undiscovered error.
Testing
Testing means quality test. Testing is a process of executing a program with
the intent of finding an error. A good test case is one that has a high probability of
finding an as yet undiscovered error. Objective should be to design test that
systematically uncovers different classes of error. And to do with a minimum
amount of time and effort. Testing cannot show the absence of Defects, it can only
show that soft wear defects are present. It is important to keep this statement in one
of these ways knowing the specific function that a product has been designed to
perform, test can be conducted that demonstrate each function is fully operational.
This approach is called ‘black box testing’. Knowing the internal working of the
product, test can be conducted to ensure that “all gears mesh” that internal operation
of the product performs according to specification and all internal components have
been adequately exercised. This Approach is call “white box testing”.
85
DB JExplorer
Test Plans
• Overall test process

• Relationship of test documentation
1. Overview of Test
• Definitions
Documentation
• Good plans and good tests
• Risk assessment
2. Analyzing the • Schedule constraints
Application
• Resource constraints
• Basic test plan structure

• Using a master test plan
3. Documentation Options • Using checklists
• Creating your own standards
• Unit testing
• Functional testing
• System testing
4. Different Testing Types,
• Performance testing
Different Documentation
• Configuration testing
• Regression testing
• Which test types to apply

5. Coverage and Estimation
• When are you done?
• Coverage techniques
• Estimating the effort
5.1 System Testing
86
DB JExplorer
Unit Testing:
A program unit is usually small enough that the programmer who developed
it can test it in grate detail than will be possible when the unit is integrated into an
evolving soft wear product.
Functional testing:
Functional Testing Specifies the operating condition, input values and
expected result .The function should be designed to take care of the situation.
Performance testes-should be designed to verify response time, execution time,
throughput and Secondary memory utilization.
Stress testing is designed to overload a system in various ways. The
purpose of the stress test is to determine the limitation of the system. Structural
stresses are conducted with examining the internal processing logic of the Software
system.
System testing:
A system is tested for online responses, volume of transactions, stress
Recover from failure and usability. System testing involves two kinds of activities
integration testing and acceptance testing.
Integrated testing:
Bottom –up integration is the traditional strategy used to integrate the
components of software system into a functional whole. Bottom-up integration
consists of unit testing followed by sub system testing of entire system. Unit testing
has the goal of discovering Errors in the goal of discovering errors in the individual
modules of the systems. The primary purpose of subsystems testing is to verify
operation of the interfaces between modules in the system. System testing is
concerned with the designing logic, control flow, recovery procedures, and
throughput, capacity and timing characteristics of the Entire structure.
87
DB JExplorer
Top-down integration starts with the main routine and or low immediate
subordinated routines in the systems structure.
System integration is distributed throughout the implementation phases:

Modules are integrated as they are developed.
Top-level interfaces are tested first.
The top-level routing provides a natural harness for low-level routines.
Error is localized to the new modules and interfaces that are being added.
It involves planning and execution of functional tests, performance tests and
Stress tests in order to demonstrate that implemented systems satisfy its
requirements.
Testing Types:
Black box Testing focuses on the input/output behavior of the component.
Black box tests do not deal with the internal aspects of the component nor with the
behavior or the structure of the component.
White box Testing focuses on the internal structure of the component. A

white box test makes sure that every state in the dynamic model of the object and
interactions among the objects are tested.
Client Needs Acceptance Testing
Requirements System Testing
Design Integration Testing
Code Unit Testing
Issues in Testing Classes:
88
DB JExplorer
Testing classes brings in some new issues that are not present in testing
functions. First, a class can’t be tested directly, only an instance of a class can be
tested. This means that we at least a class indirectly by testing its instances, of the
class and list them to test the class.
In Object Oriented programs, control flow is characterized by message
passing among object, and the control flow switches from one object to another by
inter object communication. Consequently there is no sequential control flow with
in a class like in functions. This lack of sequential control flow with in a class
requires different approaches for testing.
Thirdly, new issues are introduced due to inheritance. There are basically
tow reasons for problems that arise from inheritance .The structure of inheritance
hierarchy and the kind of inheritance.
Overall, testing of objects can be defined as the process of exercising the
routines provided by an object with the goal of uncovering error in the
implementation of the routines or state of the object or both .To test an object, we
have to test the interaction between the methods provided on the object. For this,
the problem for finding the patterns of method invocation of the object under test
with different arguments, which will yield error .In some sense, by executing
various patterns, we are testing the communication between the different methods
of the object.
89
DB JExplorer
Testing Process
Test plan:
Testing commences with a test plan and terminated with acceptance testing.
A test plan is a general document for the entire project that defines the scope and
approach to be taken, and schedule of testing as well as identifies the test items for
the entire testing process and the personal responsible for the different activities.
Test planning can be done well before the actual testing commences and can be
done in parallel with the coding and the design phases. The inputs for forming the
test plan are
1. Project plan
2. Requirements document
A test should contain the following:
Test unit specification: A test unit is a set of one or more modules together
with associated data, that are from a single computer program and that are the
object of testing. A test unit may be a module, a few modules or a complete system.
In this project we will perform tests on the following units.
1. Connecting to Web server.
2. Selecting the Company Details.
3.Validation of the Employee Bills.
4. Selecting the Details.
5. Disconnect.
Features to be tested:
This includes all software features and combinations of features that should
be tested. A soft features is a software characteristic specified or implied by the
requirements or design documents. These may include functionality, performance,
design constraints and attributes. In this project all the functional features specified
in the requirements documents will be tested.
90
DB JExplorer
Testing Types
Acceptance Testing the system with the intent of confirming readiness of

Testing the product and customer acceptance.
Testing without a formal test plan or outside of a test plan.

With some projects this type of testing is carried out as an
adjunct to formal testing. If carried out by a skilled tester, it
can often find problems that are not caught in regular testing.
Ad Hoc
Sometimes, if testing occurs very late in the development
Testing
cycle, this will be the only kind of testing that can be
performed. Sometimes ad hoc testing is referred to as
exploratory testing.
Testing after code is mostly complete or contains most of the

functionality and prior to users being involved. Sometimes a
select group of users are involved. More often this testing will
Alpha Testing
be performed in-house or by an outside testing firm in close
cooperation with the software engineering department.
Software testing that utilizes a variety of tools to automate the

testing process and when the importance of having a person
manually testing is diminished. Automated testing still requires
Automated
a skilled quality assurance professional with knowledge of the
Testing
automation tool and the software being tested to set up the
tests.
Testing after the product is code complete. Betas are often

widely distributed or even distributed to the public at large in
Beta Testing
hopes that they will buy the final product when it is released.
Black Box Testing software without any knowledge of the inner

Testing workings, structure or language of the module being tested.
Black box tests, as most other kinds of tests, must be written
91
DB JExplorer
from a definitive source document, such as a specification or

requirements document..
Testing used to determine whether other system software

Compatibility components such as browsers, utilities, and competing
Testing software will conflict with the software being tested.
Testing to determine how well the product works with a broad

Configuration range of hardware/peripheral equipment configurations as well
Testing as on different operating systems and software.
Testing two or more modules together with the intent of

finding defects, demonstrating that defects are not present,
Functional verifying that the module performs its intended functions as
Testing stated in the specification and establishing confidence that a
program does what it is supposed to do.
The process of exercising software with the intent of ensuring

that the software system meets its requirements and user
Independent
expectations and doesn't fail in an unacceptable manner. The
Verification
individual or group doing this work is not part of the group or
and
organization that developed the software. A term often applied
Validation
to government work or where the government regulates the
(IV&V)
products, as in medical devices.
Testing with the intent of determining if the product will install

Installation
on a variety of platforms and how easily it installs.
Testing
Integration Testing two or more modules or functions together with the
Testing intent of finding interface defects between the modules or
functions. Testing completed at as a part of unit or functional
testing, and sometimes, becomes its own standalone test phase.
On a larger level, integration testing can involve a putting
together of groups of modules and functions with the goal of
completing and verifying that the system meets the system
92
DB JExplorer
requirements. (see system testing)
Testing with the intent of determining how well the product

handles competition for system resources. The competition
Load Testing may come in the form of network traffic, CPU utilization or
memory allocation.
Testing with the intent of determining how quickly a product

handles a variety of events. Automated test tools geared
Performance
specifically to test and fine-tune performance are used most
Testing
often for this type of testing.
Testing that involves the users just before actual release to

ensure that users become familiar with the release contents and
ultimately accept it. Often is considered a Move-to-Production
Pilot Testing activity for ERP releases or a beta test for commercial
products. Typically involves many users, is conducted over a
short period of time and is tightly controlled. (see beta testing)
Testing with the intent of determining if bug fixes have been

successful and have not created any new problems. Also, this
Regression
type of testing is done to ensure that no degradation of baseline
Testing
functionality has occurred.
Testing of database and network software in order to keep

Security company data and resources secure from mistaken/accidental
Testing users, hackers, and other malevolent attackers.
The process of exercising software with the intent of ensuring

that the software system meets its requirements and user
expectations and doesn't fail in an unacceptable manner. The
Software organization and management of individuals or groups doing
Testing this work is not relevant. This term is often applied to
commercial products such as internet applications. (contrast
with independent verification and validation)
93
DB JExplorer
Testing with the intent of determining how well a product

performs when a load is placed on the system resources that
Stress Testing
nears and then exceeds capacity.
Testing a specific hardware/software installation. This is

System typically performed on a COTS (commercial off the shelf)
Integration system or any other system comprised of disparate parts where
Testing custom configurations and/or unique installations are the norm.
User
See Acceptance Testing.
Acceptance
Testing
Testing in which the software tester has knowledge of the
White Box
inner workings, structure and language of the software, or at
Testing
least its purpose.
6. Documentation
6.1 How to operate the package
1. Install JDK 1.5 software and observe location C:\Program
Files\Java\jdk1.5.0_07
2. Set class path
My computer - right click-Properties-Advanced- Environmental Variables - In User
variables - [NEW]
Variable _name : JAVA_HOME
94
DB JExplorer
variable_value : C:\Program Files\Java\jdk1.5.0_07

Click on [NEW]
Variable _name : PATH
variable_value : C:\Program Files\Java\jdk1.5.0_07\bin;.;
To test go to cmd and enter javac
3. Install Oracle 10g software
Very important Note:
1. Enter password as "tiger"
2. At end of installation click on [Password Management] and enter system
password as "manager" and retype password as "manager" and
Unlock the Scott user and enter new password as "tiger"
4. Copy the code Folder in your local System
5. DSN Creation
Open Start \ Settings\Control Panel \ Adminstrative Tools \ DataSources for
ODBC \
Click On [Add] and Select Oracle in Ora Home Driver and Click [Finish]
DSN Name : "oracle" (Without Cotes)
User Id : system and Click on [Test Connection]

Password : manager
Click on OK
It should display a PopUp saying that Connection Successfull.
Click on OK, Again OK
6. In your code Folder, click On Login.bat file.
7. Create Own database using below tables

connect system/manager
95
DB JExplorer
drop user Nagarjuna cascade;

create user nagarjuna identified by nagarjuna;
grant create session, unlimited tablespace, create table to nagarjuna;
grant connect,resource to nagarjuna;
connect nagarjuna / nagarjuna
drop table levels;
CREATE TABLE levels

(levelname VARCHAR2(20) NOT NULL,
levelno NUMBER(3) NOT NULL,
CONSTRAINT pk_levels_levelno PRIMARY KEY (levelno) ) ;
insert into levels values('Basic', 1) ;

insert into levels values('Intermediate', 2) ;
insert into levels values('Advanced', 3) ;
commit;
8. In your code Folder, click On Login.bat file.
96
DB JExplorer
7.Future scope and Conclusion
Even though the project was completed to the original requirements, there are a few
features that we could add or improve on, if time allowed. We could look at other DBMS
file systems to get a better idea on how to design a more efficient and space conserving
system. Also, the creating of tables and updating tables to made more efficient.
Otherwise, we are happy with the performance of our project.
Reliability:
The project performs its intended functions with required precision, hence is
very reliable.
Flexibility:
The project is very flexible and any modification can be made to the existing
system to suit changes that can take place in future.
Easily Understandable with minimum knowledge:
The forms/screens are designed in such a way that any end user can easily
understand Less effort is required to learn, Operate, repair the input and interpret
outputs with less strain.
(1) Security is the most important feature of the proposed system. In this some
security measures are taken to avoid the mishandling of the database.
(2) Constraints are defined to avoid the wrong entries.
(3) With this automated system, we can easily generate required reports.
(4) Redundant data is reduced with normalization.
(5) The system displays error messages if any error occurs.
97
DB JExplorer
Conclusion
This project Internet Banking on DB JEXPLORER model is implemented using java with
oracle as database. This project overcomes the disadvantages that are present with the
existing system.
This project is developed to provide user-friendly access to the customer and to make the
customer satisfy.It is successfully tested.
98
DB JExplorer
8.REFERENCES
Books
Software engineering -R. Pressmen
Computer networks -A.S.Tanenbaum
99
DB JExplorer
9.Bibliography
1. Software Engineering - Practitioner’s Approach by Roger S. Pressman,

McGraw Hill International Edition.
2. Java Script from W3Schools.com.
3. An Introduction to Database System by C. J. Date.
4. Java Complete References by Patrik Nortan.
5. Thinking in Java (BPB Publication) by Bruce Ekkel.
6. CORE Servlets & JSP from sun micro systems by MARTHALL
7. UML in 24 Hours - SAMS outline by JOSEPH SCHMULLER.
100
DB JExplorer
101

Final DBJExplorerDocumentation

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Final DBJExplorerDocumentation

Caricato da

Copyright:

Formati disponibili

DB JExplorer

AN INDUSTRIAL MINI PROJECT REPORT ON

DEPARTMENT OF INFORMATION TECHNOLOGY

DRK COLLEGE OF ENGINEERING AND TECHNOLOGY

Project Guide Head of the

We are extremely grateful to Mr. M.Rajasekar, Head of Department for

We will be failing in duty if we do not acknowledge with grateful thanks to

The DB JExplorer can be a powerful tool for many of your information

Why use a query

If you are an experienced SQL programmer, the DB JExplorer allows you to

The DB JExplorer supports powerful SQL pass-through reporting, it does

The JExplorer has two primary uses:

Manpower Outsourcing Services/Corporate Training

LiveTech delivers IT resources to esteemed organizations quickly and efficiently

We have an established HR department headed by a well-experienced professional

The company is supported by a dynamic second rung of consultants. In keeping

LiveTech respects the stringent expectations of highly competitive, new economy

LiveTech Backed by strong entrepreneurs with a knack for identifying

Methodology. The utilization of various training methods, certification programs,

LiveTech 10-step fulfillment process is the culmination of experience in the IT

LiveTech is a skilled and knowledgeable recruiter of Executive talent.

LiveTech follows a methodical process in its executive search practice. Based on

1.2 Existing System

1.3 Drawbacks of the existing System:

The following observations are made in the existing system

The proposed system is looking for a solution to overcome the above

Need of the product

 There won’t be any mistyping of the queries because, it automatically generates

 Analysis is about predicting the future – not documenting the past.

Systems Analysis Phase

System Analysis is a process of examining the current system in order to

The major steps followed in System Analysis are:

Feasibility as applied to our system pertains to the following areas.

Operational feasibility is willingness and ability of the employers in the

A study of resource availability that may affect to achieve an acceptable

The consideration that is normally associated with technical feasibility

 Reduced human effort

2.1 Problem Definition

The DB JExplorer Designer

2.2 Proposed System

Advantages of the proposed system

 There won’t be any mistyping of the queries because, it automatically generates

The DB JExplorer Designer

Why use a query

If you are an experienced SQL programmer, the DB JExplorer allows you to

The DB JExplorer supports powerful SQL pass-through reporting, it does

Using the DB Jexplorer

Jexplorer Reports and Query Data Sets

Data Analysis and Decision Making

2.3 Software and Hardware Requirements

3. Software Requirements Specification

MVC is a well known object-oriented user interface design decomposition that

3.2 Overall Description

own layering scheme defined by Swing. When we place a heavyweight inside

Alternatively we can call JPopupMenu’s static

Swing package overview

They are subclassed and implemented by look-and-feel implementations

The controller is responsible for determining whether the component should

For example, suppose we have a checked (selected) checkbox in

message to the model. The model then updates itself and

Custom view and controller

Figure 1.4 Malachite and Windows look-and-feels of the same components

Another major advantage of Swing’s MVC architecture is the ability customize