PC Compiler
Macintosh
Compiler
SPARC
Compiler
Java
Byte code
(Platform
Independe
nt)
Java
Interpreter
(PC)
Java
Interpreter
(Macintosh)
Java
Interpreter
(Spare)
.b6ect3.riented
;ava was not designed to be source$code compatible with any other language This
allowed the ;ava team the #reedom to design with a blank slate &ne outcome o# this was
a clean usable" pragmatic approach to ob?ects The ob?ect model in ;ava is simple and
easy to e%tend" while simple types" such as integers" are kept as high$per#ormance non$
ob?ects
Robust
The multi$plat#orm environment o# the Web places e%traordinary demands on a
program" because the program must e%ecute reliably in a variety o# systems The ability
to create robust programs was given a high priority in the design o# ;ava ;ava is strictly
typed languageJ it checks your code at compile time and run time
;ava virtually eliminates the problems o# memory management and de$allocation" which
is completely automatic !n a well$written ;ava program" all run time errors can Oand
should Obe managed by your program
@A:A S;IN>
A S$ing Architecture .vervie$
Most ,wing developers know by now that ,wing components have a
separable model$and$view design And many ,wing users have run across articles
saying that ,wing is based on something called a Lmodi#ied MC( (model$view$
controller) architectureL
@ut accurate e%planations o# how ,wing components are designed" and how
their parts all #it together" have been hard to come by until now
43
The silence ends with the publication o# this article" a ma?or white paper on
,wing component design !t provides a comprehensive technical overview o# ,wingKs
modi#ied MC( structure and demysti#ies many other #acets o# ,wing component
architecture as well
This document presents a technical overview o# the ,wing component
architecture !n particular" it covers the #ollowing areas in detail>
0esign goals
3oots in MC(
,eparable model architecture
.luggable look$and$#eel architecture
*esign >oals
The overall goal for the S$ing pro6ect $as
To build a set o# e%tensible E9! components to enable developers to more
rapidly develop power#ul ;ava #ront ends #or commercial applications
To this end" the ,wing team established a set o# design goals early in the pro?ect
that drove the resulting architecture These guidelines mandated that ,wing would>
@e implemented entirely in ;ava to promote cross$plat#orm consistency and
easier maintenance
.rovide a single A.! capable o# supporting multiple look$and$#eels so that
developers and end$users would not be locked into a single look$and$#eel
Enable the power o# model$driven programming without re*uiring it in the
highest$level A.!
44
Adhere to ;ava@eans design principles to ensure that components behave
well in !0Es and builder tools
.rovide compatibility with AWT A.!s where there is overlapping" to leverage
the AWT knowledge base and ease porting
Roots in 8:C
,wing architecture is rooted in the model$view$controller (MC() design that
dates back to ,mallTalk MC( architecture calls #or a visual application to be
broken up into three separate parts>
A mode l that represents the data #or the application
The view that is the visual representation o# that data
A controller that takes use input on the view and translates that to changes
in the model
Early on" MC( was a logical choice #or ,wing because it provided a basis #or
meeting the #irst three o# our design goals within the bounds o# the latter two
The #irst ,wing prototype #ollowed a traditional MC( separation in which each
component had a separate model ob?ect and delegated its look$and$#eel implementation
to separate view and controller ob?ects
The delegate
45
We *uickly discovered that this split didnKt work well in practical terms because
the view and controller parts o# a component re*uired a tight coupling (#or
e%ample" it was very di##icult to write a generic controller that didnKt know speci#ics
about the view) ,o we collapsed these two entities into a single 9! (user$inter#ace)
ob?ect" as shown in this diagram>
(The 9! delegate ob?ect shown in this picture is sometimes called a delegate
ob?ect" or 9! delegate The 9! delegate used in ,wing is described in more detail in
the .luggable look$and$#eel section o# this article" under the subheading LThe 9!
delegateL)
As the diagram illustrates" ,wing architecture is loosely based O but not strictly
based $$ on the traditional MC( design !n the world o# ,wing " this new *uasi$
MC( design is sometimes re#erred to a separable model architecture
,wingKs separable model design treats the model part o# a component as a
separate element " ?ust as the MC( design does @ut ,wing collapses the view and
controller parts o# each component into a single 9! (user$inter#ace) ob?ect
Separable "odel architecture
!t is generally considered good practice to center the architecture o# an
application around its data rather than around its user inter#ace To support this
paradigm" ,wing de#ines a separate model inter#ace #or each component that has a
logical data or value abstraction This separation provides programs with the option
o# plugging in their own model implementations #or ,wing components
46
The #ollowing table shows the component$to$model mapping #or ,wing
Co"ponent 8odel Interface 8odel T(pe
;@utton @uttonModel E9!
;Toggle@utton @uttonModel E9!Idata
;(heck@o% @uttonModel E9!Idata
;3adio@utton @uttonModel E9!Idata
;Menu @uttonModel E9!
;Menu!tem @uttonModel E9!
;(heck@o%Menu!tem @uttonModel E9!Idata
;3adio@uttonMenu!tem @uttonModel E9!Idata
;(ombo@o% (ombo@o%Model data
;.rogress@ar @ounded3angeModel E9!Idata
;,croll@ar @ounded3angeModel E9!Idata
;,lider @ounded3angeModel E9!Idata
;Tabbed.ane ,ingle,electionModel E9!
;1ist 1istModel data
;1ist 1ist,electionModel E9!
;Table TableModel data
;Table Table(olumnModel E9!
47
;Tree TreeModel data
;Tree Tree,electionModel E9!
;Editor.ane 0ocument data
;Te%t.ane 0ocument data
;Te%tArea 0ocument data
;Te%t2ield 0ocument data
;.assword2ield 0ocument data
!n ,wing " classes that represent E9! components have names beginning with
the letter ; ,ome e%amples are ;@utton" ;1abel" and ;,lider Altogether there are
more than '6: new classes and 56 inter#aces in ,wing P twice as many as in
AWT
@ava S$ing class hierarch(
The class @Co"ponent" descended directly #rom (ontainer" is the root class #or most
o# ,wing=s user inter#ace components
48
,wing contains co"ponents that you=ll use to build a E9! ! am listing you some
o# the commonly used ,wing components To learn and understand these swing
programs" AWT .rogramming knowledge is not re*uired
@ava S$ing 15a"ples
@elow is a ?ava swing code #or the traditional Hello World program
@asically" the idea behind this Hello World program is to learn how to create
a ?ava program" compile and run it To create your ?ava source code you can use any
editor( Te%t padIEdit plus are my #avorites) or you can use an !0E like 1clipse
import ?ava%swing;2rameJ
import ?ava%swing;1abelJ
IIimport statements
II(heck i# window closes automatically &therwise add suitable code
public class HelloWorld2rame e%tends ;2rame Q
49
public static void main(,tring argsRS) Q
new HelloWorld2rame()J
T
HelloWorld2rame() Q
;1abel ?lbHelloWorld U new ;1abel(LHello WorldL)J
add(?lbHelloWorld)J
thisset,iBe(+::" +::)J
II pack()J
setCisible(true)J
T
T
&utput
Note? @elow are some links to ?ava swing tutorials that #orms a helping hand to
get started with ?ava programming swing
;.anel is ,wing=s version o# the AWT class .anel and uses the same de#ault
layout" 2low1ayout ;.anel is descended directly #rom ;(omponent
;2rame is ,wing=s version o# 2rame and is descended directly #rom that class
The components added to the #rame are re#erred to as its contentsJ these are
50
managed by the content.ane To add a component to a ;2rame" we must use its
content.ane instead
;!nternal2rame is con#ined to a visible area o# a container it is placed in !t
can be iconi#ied " ma%imiBed and layered
;Window is ,wing=s version o# Window and is descended directly #rom that
class 1ike Window" it uses @order1ayout by de#ault
;0ialog is ,wing=s version o# 0ialog and is descended directly #rom that class
1ike 0ialog" it uses @order 1ayout by de#ault 1ike ;2rame and ;Window"
;0ialog contains a root.ane hierarchy including a content.ane" and !t allows
layered and glass panes All dialogs are modal" which means the current
thread is blocked until user interaction with it has been completed ;0ialog class
is intended as the basis #or creating custom dialogsJ however " some o# the most
common dialogs are provided through static methods in the class ;&ption.ane
;1abel" descended #rom ;(omponent" is used to create te%t labels
The abstract class Abstract@utton e%tends class ;(omponent and provides a
#oundation #or a #amily o# button classes"including ;@utton
;Te%t2ield allows editing o# a single line o# te%t New #eatures include the ability to
?usti#y the te%t le#t" right" or center" and to set the te%t=s #ont
;.assword2ield (a direct subclass o# ;Te%t2ield) you can suppress the display o#
input Each character entered can be replace by an echo characterThis allows
con#idential input #or passwords" #or e%ample @y de#ault" the echo character is the
asterisk" V
;Te%tArea allows editing o# multiple lines o# te%t ;Te%tArea can be used in
con?unction with class ;,croll.ane to achieve scrolling The underlying ;,croll.ane
can be #orced to always or never have either the vertical or horiBontal scrollbarJ
;@utton is a component the user clicks to trigger a speci#ic action
;3adio@utton is similar to ;(heckbo%" e%cept #or the de#ault icon #or each class A set
o# radio buttons can be associated as a group in which only one button at a time can
be selected
51
;(heck@o% is not a member o# a checkbo% group A checkbo% can be selected and
deselected" and it also displays its current state
,wing is a widget toolkit #or ?ava The main characteristics o# the ,wing toolkit are
plat#orm independent" customiBable" e%tensible" con#igurable and lightweight !t has a
rich set o# widgets 2rom basic widgets like @uttons" 1abels" ,crollbars to advanced
widgets like Trees and Tables
,wing is a part o# ;2(" ;ava 2oundation (lasses !t is a collection o# packages #or
creating #ull #eatured desktop applications ;2( consists o# AWT" ,wing" and
Accessibility" ;ava '0" and 0rag and 0rop
@Co"ponent
All ,wing components whose names begin with L;L descend #rom the ?component
A.! class 2or e%ample" ;.anel" ;,croll.ane" ;@utton" and ;Table all inherit #rom
;(omponent However" ;2rame doesnKt because it implements a top$level container The
;(omponent class e%tends the (ontainer api class" which itsel# e%tends (omponent api
The (omponent class includes everything #rom providing layout hints to supporting
painting and events The (ontainer class has support #or adding components to the
container and laying them out
@Panel
The ;.anel class provides general$purpose containers #or lightweight components
@y de#ault" panels do not add colors to anything e%cept their own backgroundJ however"
you can easily add borders to them and otherwise customiBe their painting
@0ra"e
;2rame is ,wingKs version o# 2rame and is descended directly #rom that class !t is
used to create Windows in a ,wing program The components added to the #rame are
re#erred to as its contentsJ these are managed by the content.ane To add a component to
a ;2rame" we must use its content.ane instead
@Button
52
The ;@utton ob?ect generally consists o# a te%t label andIor image icon that
describes the purpose o# the button " an empty area around the te%tIicon and border
@%abel
;1abel" descended #rom ;(omponent" is used to create te%t labels !t can display
te%t but images as well
@Te5tArea
;Te%tArea component is used to accept several lines o# te%t #rom user ;Te%tArea
can be used in con?unction with class ;,croll.ane to achieve scrolling The underlying
;,croll.ane can be #orced to always or never have either the vertical or horiBontal
scrollbar
@%ist
;1ist provides a scrollable set o# items #rom which one or more may be selected
;1ist can be populated #rom an Array or Cector ;s1ist does not support scrolling directly"
instead" the list must be associated with a scrollpane The view port used by the scroll
pane can also have a user$de#ined border ;1ist actions are handled using
1ist,election1istener
The S$ing 8essage Bo5
Windowing environments commonly contain a standard set o# message bo%es that
allow you to *uickly post in#ormation to the user or to capture in#ormation #rom the user
!n ,wing" these message bo%es are contained in ;&ption.ane sophisticated)" but the ones
most commonly used are probably the message dialog and con#irmation dialog" invoked
using the static ;&ption.aneshowMessage0ialog( ) and ;&ption.ane
show(on#irm0ialog( )
@ScrollPane
53
;,croll.ane is a ?*uery plugin which allows you to replace the browsers de#ault
vertical scrollbars on any block level element with an over#low>auto style ?,croll.ane is
crossbrowser" working on all browsers that support ?*uery and it also degrades grace#ully
!# a userKs browser doesnKt support ?Wuery or has ;ava,cript turned o## then they will see
the browsers de#ault scrollbars !# the mouse wheel plugin is included in the page then the
scroll panes will respond to mouse wheel events as well ?,croll.ane is built on top o# the
awesome ?Wuery library and utilises the dimensions plugin and (optionally) the mouse
wheel plugin
To place a component in one o# the corners o# the ;,croll.ane" call set(orner(,tring
key" (omponent corner) key is
;,croll.ane1&WE3X1E2TX(&3NE3"
;,croll.ane1&WE3X3!EHTX(&3NE3"
;,croll.ane9..E3X1E2TX(&3NE3" or
;,croll.ane9..E3X3!EHTX(&3NE3
@Creator
;(reator is a power#ul !0E #or ?ava ;(reator is the best development tool #or
programming !t is #aster" more e##icient and more reliable than other !0E=s There#ore it
is the per#ect tool #or programmers o# every level" #rom learning programmer to ;ava$
specialist
;(reator provides the user with a wide range o# #unctionality such as .ro?ect
management" pro?ect templates" code$completion" debugger inter#ace" editor with synta%
highlighting" wiBards and a #ully customiBable user inter#ace
54
With ;(reator you can directly compile or run your ;ava program without
activating the main document #irst ;(reator will automatically #ind the #ile with the main
method or the html #ile holding the ?ava applet" then it will start the appropriate tool
;(reator is written entirely in (NNC which makes it #ast and e##icient compared to
the ;ava based editorsI!0EKs
C2APT1R3-
S=ST18 T1STIN>
55
,o#tware Testing is the process used to help identi#y the correctness" completeness"
security and *uality o# developed computer so#tware Testing is a process o# technical
investigation" per#ormed on behal# o# stakeholders" that is intended to reveal *uality$
related in#ormation about the product with respect to the conte%t in which it is intended to
operate !n general" so#tware engineers distinguish so#tware #aults #rom so#tware #ailures
&ur pro?ectL Cisual cryptography 2or (heating .reventionM is tested with the #ollowing
testing methodologies
*eveloping 8ethodologies
The test process begins by developing a comprehensive plan to test the general
#unctionality and special #eatures on a variety o# plat#orm combinations ,trict *uality
control procedures are used The process veri#ies that the application meets the
re*uirements speci#ied in the system re*uirements document and is bug #ree The
#ollowing are the considerations used to develop the #ramework #or developing the test
methodologies
Ac!uire and stud( the test strateg(
A team very #amiliar with the business risks associated with the so#tware normally
develops test strategy" the test team develops tactics Thus the test team needs to ac*uire
and study the test strategy The test tactics are analyBed and studied #or #inding our
various test #actors" risks and e##ects The risk involved in our pro?ect is implementing
the acknowledgement scheme ,o" the proper knowledge about the testing strategies
should be gained in order to avoid such high level risks
*eter"ine the t(pe of develop"ent pro6ect
The type o# the development re#ers to the plat#orm or methodology #or developing
the pro?ect As it is been a simulation pro?ect we go #or the prototyping The prototypes
are simply prede#ined structure or model" which can be used #or #urther modeling @y
using the prototypes we can modi#y the e%isting module o# the application #or some other
speci#ic operations Here the test tactics is to veri#y that all the tools are used properly
and to test #unctionality
56
*eter"ine the t(pe of soft$are s(ste"
The type o# so#tware system relates to the type o# processing which will be
encountered by the system !n this pro?ect" the so#tware system we pre#er to use is ;ava
We have chosen ;ava #or its portability and its support to graphics < #lash speci#ically #or
simulation
*eter"ine the scope of the soft$are s(ste"
The scope o# the pro?ect re#ers to the overall activities or operation to be included
into the system being tested The scope o# the new system varies #rom that o# the e%isting
one !n the e%isting system" a large overhead occurs in sending acknowledgements !n this
pro?ect" the acknowledgement transmission is optimal because only #raction o# data
packet is transmitted as acknowledgement rather than #ull packet
Identif( the tactical ris9s
The tactical risk is the subsets at a lower level o# the strategic risks The risks
related to the application and its methodologies are identi#ied The risk involved in our
pro?ect is implementing the identi#ying the misbehaving link
*eter"ine $hen the testing should occur
!n the above processes we have identi#ied the type o# processing" scope and risks
associated with our pro?ect The testing can occur throughout all the phases o# the pro?ect
0uring the analysis phase" the testing strategy and re*uirements are determined !n design
phase" the comple%ities in design with respect to the re*uirements are determined and
structural and #unctional test conditions are also tested 0uring implementation" the
design consistency is determined !n test phase" the overall testing o# the application is
being done and previously the ade*uacy o# the testing plan is also determined !n
maintenance phase" the testing #or modi#ying and reusing the system is done
Build the s(ste" test plan
The test plan o# the pro?ect should provide all the in#ormation on the application
that is being tested The test plan is simply a model that has to be #ollowed during the
57
progression o# the testing The test plan consists o# the se*uential set o# procedures to test
the application !nitially" the identi#ication process o# misbehaving links are tested Then
the test is carried out #or 'ack scheme
Build the unit test plan
!n this case we are dividing the system into three di##erent components or units
each having speci#ic #unctions The three di##erent components o# the system are
connection establishment" nodes events handling and change the connection These units
have their own test plan The main purpose o# the unit test plan is to eliminate the errors
and bugs during the initial stage o# the implementation As the errors get debugged in the
initial stage" the less comple% the overall testing a#ter integrating all the units o# the
system The unit testing plan can be either simple or comple% based on the #unctionality
o# that unit
Testing Techni!ue D Tool selection Process
!n this process the appropriate testing process is selected #rom various testing
methodologies such as prototyping model" water#all model etc and the selection is done
by the means o# analyBing the nature o# the pro?ect We go #or Water#all model
Select test factor
This phase selects the appropriate test #actor The particular module o# the pro?ect
which is essential #or the testing methodologies is sorted out #irst This will help the
testing process to be completed within time The test #actors #or our pro?ect include
encoding" veri#ication and decoding process
*eter"ine S*%C phase
This phase involves the structural testing o# the pro?ect which will be used #or
easy implementations o# the #unctions Though structural testing is so much associated
with the coding phase" the structural testing should be carried out at all the phases o# the
li#ecycle These evaluates that all the structures are tested and sound
Identif( the criteria to test
58
!n this phase the testing unit is trained with the necessary constraints and limit
with which the pro?ect is to be tested !n our pro?ect the testing unit is trained to test
whether all the misbehaving nodes are correctly identi#ied or not
Select t(pe of test
!ndividual responsible #or testing may pre#er to select their own techni*ue and
tool based on the test situation 2or selecting the appropriate testing process the pro?ect
should be analyBed with the #ollowing three testing concepts>
,tructural versus #unctional testing
0ynamic versus static testing
Manual versus automatic testing
A#ter analyBing through the above testing concepts we divided to test our pro?ect
in Water#all model testing methodology
59
2ig 5+ Testing techni*ue and tool selection process
Structural Testing
,tructural analysis based test sets are tend to uncover errors that occur during
coding o# the program The properties o# the test set are to re#lect the internal structure o#
the program ,tructural testing is designed to veri#y that the developed system and
programs work as speci#ied in the re*uirement The ob?ective is to ensure that the product
is designed structurally sound and will #unction correctly
0unctional Testing
2unctional testing ensures that the re*uirements are properly satis#ied by the
application system The #unctions are those tasks that the system is designed to
accomplish This is not concerned with how processing occurs but rather with the results
o# the processing The #unctional analysis based test sets tend to uncover errors that
occurred in implementing re*uirements or design speci#ications
Select techni!ue
A#ter selecting the appropriate testing methodology we have to select the
necessary testing techni*ue such as stress testing" e%ecution testing" recovery testing"
operation testing" compliance testing and security testing We are per#orming operation
testing by testing whether all the components per#orm its intended operations
Select test "ethod
We have to select the testing method which is to be carried out throughout the
li#ecycle The two di##erent methods are static and dynamic 0ynamic testing needs the
program to be e%ecuted completely be#ore testing This is a traditional concept where the
#aults detected at the end will be very hard to recti#y !n static process the program is
tested #or each and every line and the testing process is allowed to pass through only a#ter
recti#ying the occurred #ault These make this process more e%pensive" so a combination
o# both static and dynamic testing method
8ode of testing
60
!t is necessary to select the test mode in which the testing method to be carried
out The two di##erent modes are manual and automated tool The real time pro?ects
needs #re*uent interactions ,o" it is impossible to carry out the testing process by
means o# automated tool &ur pro?ect uses manual testing
4nit test techni!ue
This phase e%amines the techni*ues" assessment and management o# unit testing
and analysis Testing and analysis strategies are categoriBed according to whether they
goal is #unctional or structural or combination o# these !t will assist a so#tware engineer
to de#ine" conduct and evaluate unit tests and to assess new unit test techni*ues
S(ste" Testing
&nce the entire system has been built then it has to be tested against the L,ystem
,peci#icationL to check i# it delivers the #eatures re*uired !t is still developer #ocused"
although specialist developers known as systems testers are normally employed to do it
!n essence ,ystem Testing is not about checking the individual parts o# the design" but
about checking the system as a whole !n e##ect it is one giant component ,ystem testing
can involve a number o# specialist types o# test to see i# all the #unctional and non$
#unctional re*uirements have been met
Regression Testing
This involves assurance that all aspects o# an application system remain
#unctional a#ter testing The introduction o# change is the cause o# problems in previously
tested segments !t is retesting unchanged segments o# the application system !t normally
involves rerunning tests that have been previously e%ecuted to ensure that the same
results can be achieved currently as achieved when the segments were last tested
61
C2APT1R3&
.4TP4T SCR11NS
Status *ispla( Page
62
4ser %oign Page
63
*ata 0ro" Source page
64
0ile 0ro" S(ste" page
65
<e( :alue page
66
<e( >eneration Page
67
68
69
C.NC%4SI.NS
Mobile Ad Hoc Networks (MANETs) have been an area #or active research over the
past #ew years due to their potentially widespread application in military and civilian
communications ,uch a network is highly dependent on the cooperation o# all o# its
members to per#orm networking #unctions This makes it highly vulnerable to sel#ish
nodes &ne such misbehavior is related to routing When such misbehaving nodes
participate in the 3oute 0iscovery phase but re#use to #orward the data packets" routing
per#ormance may be degraded severely
We have proposed and evaluated a techni*ue" termed 'A()" to detect and mitigate
the e##ect o# such routing misbehavior The 'A() techni*ue is based on a simple '$hop
acknowledgment packet that is sent back by the receiver o# the ne%t$hop link (ompared
with other approaches to combat the problem" such as the overhearing techni*ue" the
'A() scheme overcomes several problems including ambiguous collisions" receiver
collisions" and limited transmission powers The 'A() scheme can be used as an add$on
techni*ue to routing protocols such as 0,3 in MANETs E%tensive simulations o# the
'A() scheme have been per#ormed to evaluate its per#ormance &ur simulation results
show that the 'A() scheme maintains up to 8+ percent packet delivery ratio even when
there are /: percent misbehaving nodes in the MANETs t The regular 0,3 scheme can
only o##er a packet delivery ratio o# /: percent &ne advantage o# the 'A() scheme is its
#le%ibility to control overhead with the use o# the 3ack parameter
70
04RT21R 1N2ANC181NTS
!n this work" we have #ocused only on link misbehavior !t is more di##icult to
decide the behavior o# a single node This is mainly due to the #act that communication
takes place between two nodes and is not the sole e##ort o# a single node There#ore" care
must be taken be#ore punishing any node associated with the misbehaving links When a
link misbehaves" either o# the two nodes associated with the link may be misbehaving !n
order to decide the behavior o# a node and punish it" we may need to check the behavior
o# links around that node This is a potential direction #or our #uture work. The 'A()
scheme has been implemented on top o# 0,3 !t is also possible to implement the 'A()
scheme over other routing schemes The main challenge is how to derive the triplet
in#ormation so that the 'A() sender and the observing node are in#ormed o# such
in#ormation )nowledge o# topology o# the '$hop neighborhood may be used !n our
#uture work" we will investigate how to add the 'A() scheme to other types o# routing
schemes and open networks Theoretical analysis o# the per#ormance gain o# the 'A()
scheme is o# interest as well
71
R101R1NC1S,BIB%I.>RAP2=
Here we have mentioned various re#erences #rom which we collected our problem
and several others that supported us to design the solution #or our problem These
re#erences include either books" papers published through some standards and several
websites links with 931=s>$
+) )e?un 1iu" ;ing 0eng" Member" !EEE" .ramod ) Carshney" 2ellow"
!EEE" and )ashyap @alakrishnan" Member" !EEE
') 1 @uttyan and ;$. Hubau%" A,timulating (ooperation in ,el#$&rganiBing
Mobile Ad Hoc Networks"M A(MI)luwer Mobile Networks and
Applications" vol 7" no 6" '::-
-) ) @alakrishnan is with the ,ecurity ,ervices Eroup" 0eloitte and Touche
11." +56: Tysons @oulevard" ,uite 7::" Mc1ean" CA ''+:'
E$mail> kbalakrishnanYdeloittecom
/) , Marti" T Eiuli" ) 1ai" and M @aker" AMitigating 3outing Misbehavior
in Mobile Ad Hoc Networks"M .roc Mobi(om" Aug ':::
6) C$N .admanabhan and 0$3 ,imon" A,ecure Traceroute to 0etect 2aulty
or Malicious 3outing"M ,!E(&MM (omputer (omm 3ev" vol --" no +"
;an '::-
4) C ,rinivasan" . Nuggehalli" (2 (hiasserini" and 33 3ao" A(ooperation
in Wireless Ad Hoc Networks"M .roc !N2&(&M" Mar$Apr '::-
5) 0 ;ohnson" 0 MaltB" Z( Hu" and ; ;etcheva" AThe 0ynamic ,ource
3outing .rotocol #or Mobile Ad Hoc Networks (0,3)"M !nternet dra#t"
2eb '::'
72