— Scott McNealy, Sun Microsystems Chairman, President and ceo

get to know the 
Java API 
you are here
4
141
What needs to change?
We have three classes that need to change: the 
DotCom class (which is now called DotCom instead of 
SimpleDotCom), the game class (DotComBust) and the 
game helper class (which we won’t worry about now).
A
DotCom class 
§
Add a name variable 
to hold the name of the DotCom 
(“Pets.com”, “Go2.com”, etc.) so each Dot-
Com can print its name when it’s killed (see 
the output screen on the opposite page).
DotComBust class continued...
§
Put the DotComs on a grid rather than 
just a single row, and do it for all three 
DotComs.
This step is now way more complex than 
before, if we’re going to place the DotComs 
randomly. Since we’re not here to mess 
with the math, we put the algorithm for 
giving the DotComs a location into the 
GameHelper (Ready-bake) class.
§
Check each user guess with all three 
DotComs, instead of just one.
§
Keep playing the game (i.e accepting 
user guesses and checking them with the 
remaining DotComs) until there are no more 
live DotComs.
§
Get out of main. We kept the simple one in 
main just to... keep it simple. But that’s not 
what we want for the real game.
DotComBust
The game class. 
Makes DotComs, 
gets user input, 
plays until all Dot-
Coms are dead
DotCom
The actual 
DotCom objects.

DotComs know their 

name, location, and 
how to check a user 
guess for a match.
3 Classes:
GameHelper
The helper class 
(Ready-Bake).
It knows how to 
accept user com-
mand-line input, 
and make DotCom 
locations.
5 Objects:
DotComBust
DotCom
DotCom
DotCom
GameHelper
use
s f
or p
layer
input
and to 
m
ak
e 
D
otCom lo
ca
t
ions
crea
tes and plays
with