INTRUSION DETECTION: AN ENERGY EFFICIENT APPROACH

IN HETEROGENEOUS WSN

ABSTRACT:

Intrusion detection plays an important role in the area of security in WSN. Detection of
any type of intruder is essential in case of WSN. WSN consumes a lot of energy to detect an
intruder. Therefore we derive an algorithm for energy efficient external and internal intrusion
detection. We also analyze the probability of detecting the intruder for heterogeneous WSN. This
paper considers single sensing and multi sensing intruder detection models. It is found that our
experimental results validate the theoretical results. Work towards maximizing the life time of
WSN has been studied in many research works. Some of them lead to the need of heterogeneous
WSN deployment. Analyze heterogeneous deployments both mathematically and through
simulations in different deployment environments and network operation models investigate
some fundamental questions for hybrid deployment of sensor.

Introduction:
A Wireless Sensor Network (WSN) is a collection of spatially deployed wireless sensors by
which to monitor various changes of environmental conditions (e.g., forest fire, air pollutant
concentration, and object moving) in a collaborative manner without relying on any underlying
infrastructure support .Recently, a number of research efforts have been made to develop sensor
hardware and network architectures in order to effectively deploy WSNs for a variety of
applications. Due to a wide diversity of WSN application requirements, however, a generalpurpose WSN design cannot fulfill the needs of all applications. Many network parameters such
as sensing range, transmission range, and node density have to be carefully considered at the
network design stage, according to specific applications. To achieve this, it is critical to capture
the impacts of network parameters on network performance with respect to application
specifications. Intrusion detection (i.e., object tracking) in a WSN can be regarded as a
monitoring system for detecting the intruder that is invading the network domain.

The intrusion detection application concerns how fast the intruder can be detected by the
WSN. If sensors are deployed with a high density so that the union of all sensing ranges covers
the entire network area, the intruder can be immediately detected once it approaches the network
area. However, such a high-density deployment policy increases the network investment and
may be even unaffordable for a large area. In fact, it is not necessary to deploy so many sensors
to cover the entire WSN area in many applications, since a network with small and scattered void
areas will also be able to detect a moving intruder within a certain intrusion distance. In this case,
the application can specify a required intrusion distance within which the intruder should be
detected. As shown in Fig. 1, the intrusion distance is referred as D and defined as the distance
between the points the intruder enters the WSN, and the point the intruder is detected by the
WSN system. This distance is of central interest to a WSN used for intrusion detection. In this
paper, we derive the expected intrusion distance and evaluate the detection probability in
different application scenarios.. For example, given an expected detection distance ED, we can
derive the node density with respect to sensors sensing range, thereby knowing the total number
of sensors required for WSN deployment.

In a WSN, there are two ways to detect an object (i.e., an intruder): single-sensing detection
and multiple-sensing detection. In the single-sensing detection, the intruder can be successfully
detected by a single sensor. On the contrary, in the multiple-sensing detection, the intruder can
only be detected by multiple collaborating sensors .In some applications, the sensed information
provided by a single sensor might be inadequate for recognizing the intruder. It is because
individual sensors can only sense a portion of the intruder. For example, the location of an
intruder can only be determined from at least three sensors sensing.
In view of this, we analyze the intrusion detection problem under two application scenarios:
single-sensing detection and multiple-sensing detection. According to the capability of sensors,
we consider two network types: homogeneous and heterogeneous WSNs We define the sensor
capability in terms of the sensing range and the transmission range. In a heterogeneousWSN
some sensors have a larger sensing range and more power to achieve a longer transmission
range. In this paper, we show that the heterogeneous WSN increases the detection probability for
a given intrusion detection distance. This motivates us to analyze the network connectivity in this
paper. Furthermore, in a heterogeneous WSN, high capability sensors usually undertake more
important tasks (i.e., broadcasting power management information or synchronization
information to all the sensors in the network),it is also desirable to define and examine the
broadcast reachability from high-capability sensors. The network connectivity and broadcast
reachability are important conditions to ensure the detection probability in WSNs. They are
formally defined and analyzed in this paper. To the best of our knowledge, our effect is the first
to address this issue in a heterogeneous WSN.

Literature Survey
1Intrusion detection
An Intrusion detection system (IDS) is software and/or hardware designed to detect
unwanted attempts at accessing, manipulating, and/or disabling of computer mainly through a
network, such as the Internet. These attempts may take the form of attacks, as examples, by
crackers,, malwarer and/or disgruntled employees. IDS cannot directly detect attacks within
properly encrypted traffic.
An intrusion detection system is used to detect several types of malicious behaviors that
can compromise the security and trust of a computer system. This includes network attacks
against vulnerable services, data driven attacks on applications, host based attacks such as
privilege escalation, unauthorized logins and access to sensitive files, and viruses
IDS can be composed of several components: Sensors which generate security events, a
Console to monitor events and alerts and control the sensors, and a central Engine that records
events logged by the sensors in a database and uses a system of rules to generate alerts from
security events received. There are several ways to categorize an IDS depending on the type and
location of the sensors and the methodology used by the engine to generate alerts. In many
simple IDS implementations all three components are combined in a single device or appliance.
Wireless Sensor Network (WSN).
A wireless sensor network (WSN) is a wireless network consisting of spatially distributed
autonomous devices using sensors to cooperatively monitor physical or environmental
conditions, such as temperature, sound, vibration, pressure, motion or pollutants, at different
locations The development of wireless sensor networks was originally motivated by military
applications such as battlefield surveillance. However, wireless sensor networks are now used in
many civilian application areas, including environment and habitat monitoring, healthcare
applications, home automation, and traffic control

In addition to one or more sensors, each node in a sensor network is typically equipped
with a radio transceiver or other wireless communications device, a small microcontroller, and
an energy source, usually a battery. The envisaged size of a single sensor node can vary from
shoebox-sized nodes down to devices the size of grain of dust although functioning 'motes' of
genuine microscopic dimensions have yet to be created. The cost of sensor nodes is similarly
variable, ranging from hundreds of dollars to a few cents, depending on the size of the sensor
network and the complexity required of individual sensor nodes. Size and cost constraints on
sensor nodes result in corresponding constraints on resources such as energy, memory,
computational speed and bandwidth.

A sensor network normally constitutes a wireless ad-hoc network, meaning that each sensor
supports a multi-hop routing algorithm (several nodes may forward data packets to the base
station).

System Analysis

Existing System:
1 single-sensing detection, the intruder can be successfully detected by a single sensor
2 Previous work was according to homogeneous single sensor in wireless sensor network
3 It is because individual sensors can only sense a portion of the intruder.

Proposed System:

1. Intrusion detection in heterogeneous WSNs by characterizing intrusion detection with respect

to the network parameters

Two detection models are:

Single-sensing detection
Multiple-sensing detection models
These are two detection models

2. We are detecting the intruder both single sensor and multiple sensor heterogeneous wireless
sensor network.

Disadvantage:

1 The sensed information provided by a single sensor might be inadequate for recognizing
the intruder.
2 So that there is no guarantee for our information has been sent securely.

Advantage:

1 Through sensing the network we able to find possible node in the wireless Sensor
network.
2 By finding the intruders we can send our information in a secured manner.

System Requirements:

Hardware:

PROCESSOR

: PENTIUM IV 2.6 GHz

RAM

: 512 MB DD RAM

MONITOR

: 15 COLOR

HARD DISK

: 20 GB

CDDRIVE
KEYBOARD
MOUSE

: LG 52X
: STANDARD 102 KEYS
: 3 BUTTONS

Software:

FRONT END

: Java

TOOL USED

: JFrameBuilder

OPERATING SYSTEM : Windows Xp

System Design

Data Flow Diagram

Heterogeneous:

Detec1

Detec2

S1

S2
Detec3

Sending packet from source S to D

Homogeneous:

Data Flow

Intruder

Rec1

Rec 3

Detector

Rec 2
Source

Filter

Modules:
1 Constructing Sensor Network
2 Packet Creation
3 Find authorized and un authorized port
4 Constructing Inter-Domain Packet Filters
5 Receiving the valid packet

Modules Descriptions:
Module-1:
In this module, we are going to connect the network .Each node is connected the
neighboring node and it is independently deployed in network area. And also deploy the each
port no is authorized in a node.
Module-2:

In this module, browse and select the source file. And selected data is converted into fixed
size of packets. And the packet is send from source to detector.
Module-3:
The intrusion detection is defined as a mechanism for a WSN to detect the existence of
inappropriate, incorrect, or anomalous moving attackers. In this module check whether the path
is authorized or unauthorized. If path is authorized the packet is send to valid destination.
Otherwise the packet will be deleted. According port no only we are going to find the path is
authorized or Unauthorized.

Module-4:
If the packet is received from other than the port no it will be filtered

and discarded.

This filter only removes the unauthorized packets and authorized packets send to destination.

Module-5:
In this module, after filtering the invalid packets all the valid
the destination.

Packets will reach

SYSTEM STUDY:
FEASIBILITY STUDY:
The feasibility of the project is analyzed in this phase and business proposal is put forth
with a very general plan for the project and some cost estimates. During system analysis the
feasibility study of the proposed system is to be carried out. This is to ensure that the proposed
system is not a burden to the company. For feasibility analysis, some understanding of the major
requirements for the system is essential.
Three key considerations involved in the feasibility analysis are

ECONOMICAL FEASIBILITY

TECHNICAL FEASIBILITY

SOCIAL FEASIBILITY

ECONOMICAL FEASIBILITY:
This study is carried out to check the economic impact that the system will have on
the organization. The amount of fund that the company can pour into the research and
development of the system is limited. The expenditures must be justified. Thus the developed
system as well within the budget and this was achieved because most of the technologies used
are freely available. Only the customized products had to be purchased.

TECHNICAL FEASIBILITY:
This study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high demand on the available
technical resources. This will lead to high demands on the available technical resources. This

will lead to high demands being placed on the client. The developed system must have a modest
requirement, as only minimal or null changes are required for implementing this system.

SOCIAL FEASIBILITY:
The aspect of study is to check the level of acceptance of the system by the user. This
includes the process of training the user to use the system efficiently. The user must not feel
threatened by the system, instead must accept it as a necessity. The level of acceptance by the
users solely depends on the methods that are employed to educate the user about the system and
to make him familiar with it. His level of confidence must be raised so that he is also able to
make some constructive criticism, which is welcomed, as he is the final user of the system.

SYSTEM TESTING:

The purpose of testing is to discover errors. Testing is the process of trying to discover
every conceivable fault or weakness in a work product. It provides a way to check the
functionality of components, sub assemblies, assemblies and/or a finished product It is the
process of exercising software with the intent of ensuring that the Software system meets its
requirements and user expectations and does not fail in an unacceptable manner. There are
various types of test. Each test type addresses a specific testing requirement.

TYPES OF TESTS:

Unit testing:

Unit testing involves the design of test cases that validate that the internal program logic is
functioning properly, and that program inputs produce valid outputs. All decision branches and
internal code flow should be validated. It is the testing of individual software units of the
application .it is done after the completion of an individual unit before integration. This is a
structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform
basic tests at component level and test a specific business process, application, and/or system
configuration. Unit tests ensure that each unique path of a business process performs accurately
to the documented specifications and contains clearly defined inputs and expected results.

Integration testing:

Integration tests are designed to test integrated software components to determine if they
actually run as one program. Testing is event driven and is more concerned with the basic
outcome of screens or fields. Integration tests demonstrate that although the components were
individually satisfaction, as shown by successfully unit testing, the combination of components is

correct and consistent. Integration testing is specifically aimed at

exposing the problems that

arise from the combination of components.

Functional test:

Functional tests provide systematic demonstrations that functions tested are available as
specified by the business and technical requirements, system documentation, and user manuals.
Functional testing is centered on the following items:
Valid Input

identified classes of valid input must be accepted.

Invalid Input

identified classes of invalid input must be rejected.

Functions

identified functions must be exercised.

Output

identified classes of application outputs must be exercised.

Systems/Procedures: interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key

functions, or special test cases. In addition, systematic coverage pertaining to identify Business
process flows; data fields, predefined processes, and successive processes must be considered for
testing. Before functional testing is complete, additional tests are identified and the effective
value of current tests is determined.

System Test:

System testing ensures that the entire integrated software system meets requirements. It tests a
configuration to ensure known and predictable results. An example of system testing is the

configuration oriented system integration test. System testing is based on process descriptions
and flows, emphasizing pre-driven process links and integration points.

White Box Testing:

White Box Testing is a testing in which in which the software tester has knowledge of the
inner workings, structure and language of the software, or at least its purpose. It is purpose. It is
used to test areas that cannot be reached from a black box level.

Black Box Testing:

Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of tests,
must be written from a definitive source document, such as specification or requirements
document, such as specification or requirements document. It is a testing in which the software
under test is treated, as a black box .you cannot see into it. The test provides inputs and
responds to outputs without considering how the software works.

Unit Testing:

Unit testing is usually conducted as part of a combined code and unit test phase of the
software lifecycle, although it is not uncommon for coding and unit testing to be conducted as
two distinct phases.

Test strategy and approach

Field testing will be performed manually and functional tests will be written in detail.

Test objectives:

All field entries must work properly.

Pages must be activated from the identified link.

The entry screen, messages and responses must not be delayed.

Features to be tested:

Verify that the entries are of the correct format

No duplicate entries should be allowed

All links should take the user to the correct page.

Integration Testing:

Software integration testing is the incremental integration testing of two or more

integrated software components on a single platform to produce failures caused by interface
defects.
The task of the integration test is to check that components or software applications, e.g.
components in a software system or one step up software applications at the company level
interact without error.

Test Results: All the test cases mentioned above passed successfully. No defects encountered.

Acceptance Testing:

User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional requirements.

Test Results: All the test cases mentioned above passed successfully. No defects encountered.

SOFTWARE ENVIRONMENT:

Java Technology

Java technology is both a programming language and a platform.

The Java Programming Language

The Java programming language is a high-level language that can be characterized by all
of the following buzzwords:

Simple

Architecture neutral

Object oriented

Portable

Distributed

High performance

Interpreted

Multithreaded

Robust

Dynamic

Secure

With most programming languages, you either compile or interpret a program so that you
can run it on your computer. The Java programming language is unusual in that a program is
both compiled and interpreted. With the compiler, first you translate a program into an
intermediate language called Java byte codes the platform-independent codes interpreted by
the interpreter on the Java platform. The interpreter parses and runs each Java byte code

instruction on the computer. Compilation happens just once; interpretation occurs each time the
program is executed. The following figure illustrates how this works.

You can think of Java byte codes as the machine code instructions for the Java Virtual
Machine (Java VM). Every Java interpreter, whether its a development tool or a Web browser
that can run applets, is an implementation of the Java VM. Java byte codes help make write
once, run anywhere possible. You can compile your program into byte codes on any platform
that has a Java compiler. The byte codes can then be run on any implementation of the Java VM.
That means that as long as a computer has a Java VM, the same program written in the Java
programming language can run on Windows 2000, a Solaris workstation, or on an iMac.

The Java Platform

A platform is the hardware or software environment in which a program runs. Weve already
mentioned some of the most popular platforms like Windows 2000, Linux, Solaris, and MacOS.
Most platforms can be described as a combination of the operating system and hardware. The
Java platform differs from most other platforms in that its a software-only platform that runs on
top of other hardware-based platforms.
The Java platform has two components:

The Java Virtual Machine (Java VM)

The Java Application Programming Interface (Java API)

Youve already been introduced to the Java VM. Its the base for the Java platform and is ported
onto various hardware-based platforms.
The Java API is a large collection of ready-made software components that provide many useful
capabilities, such as graphical user interface (GUI) widgets. The Java API is grouped into
libraries of related classes and interfaces; these libraries are known as packages. The next
section, What Can Java Technology Do? Highlights what functionality some of the packages in
the Java API provide.
The following figure depicts a program thats running on the Java platform. As the figure shows,
the Java API and the virtual machine insulate the program from the hardware.

Native code is code that after you compile it, the compiled code runs on a specific hardware
platform. As a platform-independent environment, the Java platform can be a bit slower than
native code. However, smart compilers, well-tuned interpreters, and just-in-time byte code
compilers can bring performance close to that of native code without threatening portability.

What Can Java Technology Do?

The most common types of programs written in the Java programming language are
applets and applications. If youve surfed the Web, youre probably already familiar with
applets. An applet is a program that adheres to certain conventions that allow it to run within a
Java-enabled browser.

However, the Java programming language is not just for writing cute, entertaining applets
for the Web. The general-purpose, high-level Java programming language is also a powerful
software platform. Using the generous API, you can write many types of programs.

An application is a standalone program that runs directly on the Java platform. A special
kind of application known as a server serves and supports clients on a network. Examples of
servers are Web servers, proxy servers, mail servers, and print servers. Another specialized
program is a servlet. A servlet can almost be thought of as an applet that runs on the server side.
Java Servlets are a popular choice for building interactive web applications, replacing the use of
CGI scripts. Servlets are similar to applets in that they are runtime extensions of applications.
Instead of working in browsers, though, servlets run within Java Web servers, configuring or
tailoring the server.
How does the API support all these kinds of programs? It does so with packages of software
components that provides a wide range of functionality. Every full implementation of the Java
platform gives you the following features:

The essentials: Objects, strings, threads, numbers, input and output, data structures,

system properties, date and time, and so on.

Applets: The set of conventions used by applets.

Networking: URLs, TCP (Transmission Control Protocol), UDP (User Data gram

Protocol) sockets, and IP (Internet Protocol) addresses.

Internationalization: Help for writing programs that can be localized for users

worldwide. Programs can automatically adapt to specific locales and be displayed in the
appropriate language.

Security: Both low level and high level, including electronic signatures, public and

private key management, access control, and certificates.

Software components: Known as JavaBeansTM, can plug into existing component

architectures.

Object serialization: Allows lightweight persistence and communication via Remote

Method Invocation (RMI).

Java Database Connectivity (JDBCTM): Provides uniform access to a wide range of

relational databases.
The Java platform also has APIs for 2D and 3D graphics, accessibility, servers, collaboration,
telephony, speech, animation, and more. The following figure depicts what is included in the
Java 2 SDK.

How Will Java Technology Change My Life?

We cant promise you fame, fortune, or even a job if you learn the Java programming
language. Still, it is likely to make your programs better and requires less effort than other
languages. We believe that Java technology will help you do the following:

Get started quickly: Although the Java programming language is a powerful object-

oriented language, its easy to learn, especially for programmers already familiar with C or C++.

Write less code: Comparisons of program metrics (class counts, method counts, and so

on) suggest that a program written in the Java programming language can be four times smaller
than the same program in C++.

Write better code: The Java programming language encourages good coding practices,

and its garbage collection helps you avoid memory leaks. Its object orientation, its JavaBeans
component architecture, and its wide-ranging, easily extendible API let you reuse other peoples
tested code and introduce fewer bugs.

Develop programs more quickly: Your development time may be as much as twice as

fast versus writing the same program in C++. Why? You write fewer lines of code and it is a
simpler programming language than C++.

Avoid platform dependencies with 100% Pure Java: You can keep your program

portable by avoiding the use of libraries written in other languages. The 100% Pure JavaTM
Product Certification Program has a repository of historical process manuals, white papers,
brochures, and similar materials online.

Write once, run anywhere: Because 100% Pure Java programs are compiled into

machine-independent byte codes, they run consistently on any Java platform.

Distribute software more easily: You can upgrade applets easily from a central server.

Applets take advantage of the feature of allowing new classes to be loaded on the fly, without
recompiling the entire program.

ODBC:

Microsoft Open Database Connectivity (ODBC) is a standard programming interface for

application developers and database systems providers. Before ODBC became a de facto
standard for Windows programs to interface with database systems, programmers had to use
proprietary languages for each database they wanted to connect to. Now, ODBC has made the
choice of the database system almost irrelevant from a coding perspective, which is as it should

be. Application developers have much more important things to worry about than the syntax that
is needed to port their program from one database to another when business needs suddenly
change.

Through the ODBC Administrator in Control Panel, you can specify the particular
database that is associated with a data source that an ODBC application program is written to
use. Think of an ODBC data source as a door with a name on it. Each door will lead you to a
particular database. For example, the data source named Sales Figures might be a SQL Server
database, whereas the Accounts Payable data source could refer to an Access database. The
physical database referred to by a data source can reside anywhere on the LAN.

The ODBC system files are not installed on your system by Windows 95. Rather, they
are installed when you setup a separate database application, such as SQL Server Client or
Visual Basic 4.0. When the ODBC icon is installed in Control Panel, it uses a file called
ODBCINST.DLL. It is also possible to administer your ODBC data sources through a standalone program called ODBCADM.EXE. There is a 16-bit and a 32-bit version of this program
and

each

maintains

separate

list

of

ODBC

data

sources.

From a programming perspective, the beauty of ODBC is that the application can be
written to use the same set of function calls to interface with any data source, regardless of the
database vendor. The source code of the application doesnt change whether it talks to Oracle or
SQL Server. We only mention these two as an example. There are ODBC drivers available for
several dozen popular database systems. Even Excel spreadsheets and plain text files can be
turned into data sources. The operating system uses the Registry information written by ODBC
Administrator to determine which low-level ODBC drivers are needed to talk to the data source
(such as the interface to Oracle or SQL Server). The loading of the ODBC drivers is transparent
to the ODBC application program. In a client/server environment, the ODBC API even handles
many of the network issues for the application programmer.

The advantages of this scheme are so numerous that you are probably thinking there must
be some catch. The only disadvantage of ODBC is that it isnt as efficient as talking directly to

the native database interface. ODBC has had many detractors make the charge that it is too slow.
Microsoft has always claimed that the critical factor in performance is the quality of the driver
software that is used. In our humble opinion, this is true. The availability of good ODBC drivers
has improved a great deal recently. And anyway, the criticism about performance is somewhat
analogous to those who said that compilers would never match the speed of pure assembly
language. Maybe not, but the compiler (or ODBC) gives you the opportunity to write cleaner
programs, which means you finish sooner. Meanwhile, computers get faster every year.

JDBC:

In an effort to set an independent database standard API for Java; Sun Microsystems
developed Java Database Connectivity, or JDBC. JDBC offers a generic SQL database access
mechanism that provides a consistent interface to a variety of RDBMSs. This consistent interface
is achieved through the use of plug-in database connectivity modules, or drivers. If a database
vendor wishes to have JDBC support, he or she must provide the driver for each platform that the
database and Java run on.
To gain a wider acceptance of JDBC, Sun based JDBCs framework on ODBC. As you
discovered earlier in this chapter, ODBC has widespread support on a variety of platforms.
Basing JDBC on ODBC will allow vendors to bring JDBC drivers to market much faster than
developing a completely new connectivity solution.
JDBC was announced in March of 1996. It was released for a 90 day public review that ended
June 8, 1996. Because of user input, the final JDBC v1.0 specification was released soon after.

The remainder of this section will cover enough information about JDBC for you to know
what it is about and how to use it effectively. This is by no means a complete overview of JDBC.
That would fill an entire book.

JDBC Goals:

Few software packages are designed without goals in mind. JDBC is one that, because of
its many goals, drove the development of the API. These goals, in conjunction with early
reviewer feedback, have finalized the JDBC class library into a solid framework for building
database applications in Java.
The goals that were set for JDBC are important. They will give you some insight as to why
certain classes and functionalities behave the way they do. The eight design goals for JDBC are
as follows:

1.

SQL Level API

The designers felt that their main goal was to define a SQL interface for Java. Although
not the lowest database interface level possible, it is at a low enough level for higher-level tools
and APIs to be created. Conversely, it is at a high enough level for application programmers to
use it confidently. Attaining this goal allows for future tool vendors to generate JDBC code
and to hide many of JDBCs complexities from the end user.
2.

SQL Conformance

SQL syntax varies as you move from database vendor to database vendor. In an effort to
support a wide variety of vendors, JDBC will allow any query statement to be passed through it
to the underlying database driver. This allows the connectivity module to handle non-standard
functionality in a manner that is suitable for its users.

3.

JDBC must be implemental on top of common database interfaces

The JDBC SQL API must sit on top of other common SQL level APIs. This goal
allows JDBC to use existing ODBC level drivers by the use of a software interface. This
interface would translate JDBC calls to ODBC and vice versa.

4.

Provide a Java interface that is consistent with the rest of the Java system

Because of Javas acceptance in the user community thus far, the designers feel that they
should not stray from the current design of the core Java system.
5.

Keep it simple

This goal probably appears in all software design goal listings. JDBC is no exception.
Sun felt that the design of JDBC should be very simple, allowing for only one method of
completing a task per mechanism. Allowing duplicate functionality only serves to confuse the
users of the API.

6.

Use strong, static typing wherever possible

Strong typing allows for more error checking to be done at compile time; also, less error

appear at runtime.
7.

Keep the common cases simple

Because more often than not, the usual SQL calls used by the programmer are simple

SELECTs, INSERTs, DELETEs and UPDATEs, these queries should be simple to perform
with JDBC. However, more complex SQL statements should also be possible.
Finally we decided to proceed the implementation using Java Networking.
And for dynamically updating the cache table we go for MS Access database.
Java ha two things: a programming language and a platform.

Java is a high-level programming language that is all of the following

Simple

Architecture-neutral

Object-oriented
Distributed

Portable

High-performance
Interpreted
Robust

multithreaded
Dynamic

Secure

Java is also unusual in that each Java program is both compiled and interpreted.
With a compile you translate a Java program into an intermediate language called Java
byte codes the platform-independent code instruction is passed and run on the
computer.
Compilation happens just once; interpretation occurs each time the program is executed.
The figure illustrates how this works.

Interpreter

Java Program

Compilers

My Program

You can think of Java byte codes as the machine code instructions for the Java
Virtual Machine (Java VM). Every Java interpreter, whether its a Java development
tool or a Web browser that can run Java applets, is an implementation of the Java VM.
The Java VM can also be implemented in hardware.

Java byte codes help make write once, run anywhere possible. You can
compile your Java program into byte codes on my platform that has a Java compiler.
The byte codes can then be run any implementation of the Java VM. For example, the
same Java program can run Windows NT, Solaris, and Macintosh.

Networking TCP/IP stack:

The TCP/IP stack is shorter than the OSI one:

TCP is a connection-oriented protocol; UDP (User Datagram Protocol) is a connectionless

protocol.
IP datagrams:
The IP layer provides a connectionless and unreliable delivery system. It considers each
datagram independently of the others. Any association between datagram must be supplied by
the higher layers. The IP layer supplies a checksum that includes its own header. The header
includes the source and destination addresses. The IP layer handles routing through an Internet. It
is also responsible for breaking up large datagram into smaller ones for transmission and
reassembling them at the other end.

UDP:
UDP is also connectionless and unreliable. What it adds to IP is a checksum for the
contents of the datagram and port numbers. These are used to give a client/server model - see
later.

TCP:
TCP supplies logic to give a reliable connection-oriented protocol above IP. It provides a
virtual circuit that two processes can use to communicate.
Internet addresses
In order to use a service, you must be able to find it. The Internet uses an address scheme for
machines so that they can be located. The address is a 32 bit integer which gives the IP address.
This encodes a network ID and more addressing. The network ID falls into various classes
according to the size of the network address.
Network address:
Class A uses 8 bits for the network address with 24 bits left over for other addressing. Class B
uses 16 bit network addressing. Class C uses 24 bit network addressing and class D uses all 32.
Subnet address:
Internally, the UNIX network is divided into sub networks. Building 11 is currently on one sub
network and uses 10-bit addressing, allowing 1024 different hosts.
Host address:
8 bits are finally used for host addresses within our subnet. This places a limit of 256 machines
that can be on the subnet.
Total address:

The 32 bit address is usually written as 4 integers separated by dots.

Port addresses
A service exists on a host, and is identified by its port. This is a 16 bit number. To send a
message to a server, you send it to the port for that service of the host that it is running on. This
is not location transparency! Certain of these ports are "well known".
Sockets:
A socket is a data structure maintained by the system to handle network connections. A
socket is created using the call socket. It returns an integer that is like a file descriptor. In fact,
under Windows, this handle can be used with Read File and Write File functions.
#include <sys/types.h>
#include <sys/socket.h>
int socket(int family, int type, int protocol);
Here "family" will be AF_INET for IP communications, protocol will be zero, and type will
depend on whether TCP or UDP is used. Two processes wishing to communicate over a network
create a socket each. These are similar to two ends of a pipe - but the actual pipe does not yet
exist.

JFree Chart:

JFreeChart is a free 100% Java chart library that makes it easy for developers to display
professional quality charts in their applications. JFreeChart's extensive feature set includes:
A consistent and well-documented API, supporting a wide range of chart types;
A flexible design that is easy to extend, and targets both server-side and client-side applications;
Support for many output types, including Swing components, image files (including PNG
and JPEG), and vector graphics file formats (including PDF, EPS and SVG);
JFreeChart is "open source" or, more specifically, free software. It is distributed under the
terms of the GNU Lesser General Public Licence (LGPL), which permits use in proprietary
applications.
1. Map Visualizations:

Charts showing values that relate to geographical areas. Some examples include: (a)
population density in each state of the United States, (b) income per capita for each country in
Europe, (c) life expectancy in each country of the world. The tasks in this project include:
Sourcing freely redistributable vector outlines for the countries of the world, states/provinces in
particular countries (USA in particular, but also other areas);
Creating an appropriate dataset interface (plus default implementation), a rendered, and
integrating this with the existing XYPlot class in JFreeChart;
Testing, documenting, testing some more, documenting some more.
2. Time Series Chart Interactivity

Implement a new (to JFreeChart) feature for interactive time series charts --- to display a
separate control that shows a small version of ALL the time series data, with a sliding "view"
rectangle that allows you to select the subset of the time series data to display in the main chart.

3. Dashboards

There is currently a lot of interest in dashboard displays. Create a flexible dashboard

mechanism that supports a subset of JFreeChart chart types (dials, pies, thermometers, bars, and
lines/time series) that can be delivered easily via both Java Web Start and an applet.
4. Property Editors

The property editor mechanism in JFreeChart only handles a small subset of the
properties that can be set for charts. Extend (or reimplement) this mechanism to provide greater
end-user control over the appearance of the charts.

Output