Mini Project - DSpace at CUSAT - Cochin University of Science and ...

Mini Project

ROAD STAR – CAR RACING GAME BASED ON JAVA
SUDHEESH V.S
Register No: 95580054
SUBMITTED IN FULLFILLMENT OF THE REQUIREMENTS FOR THE FOURTH
SEMESTER MINI PROJECT
JUNE 2010
DEPARTMENT OF COMPUTER APPLICATION
COCHIN UNIVERSITY OF SCIENCE AND TECHNOLOGY
COCHIN -22

Mini Project Work
(Fourth Semester)
ROAD STAR – CAR RACING GAME BASED ON JAVA
Submitted By
SUDHEESH V.S
Register No: 95580054
SUBMITTED IN FULLFILLMENT OF THE REQUIREMENTS FOR THE FOURTH
SEMESTER MINI PROJECT
JUNE 2010
Faculty Guide Head of the Department
Internal Examiner External Examiner
Submitted On:

ACKNOWLEDGEMENT
SYNOPSIS
1.INTRODUCTION
2. SYSTEM ANALYSIS
3.SYSTEM SPECIFICATION
4.SQA PLANPURPOSE
5.SYSTEM DESIGN
6.DATA DESIGN
7.SYSTEM TESTING
8.IMPLEMENTATION
9. FUTURE ENHANCEMENT
10.CONCLUSION
11.BIBLIOGRAPHY

ACKNOWLEDGEMENT
1

ACKNOWLEDGEMENT
This Project itself is an acknowledgement to the inspiration, drive and technical
assistance contributed by many individuals. This project would have never seen the
light of this day with out the help and guidance I have received.
I am pleased to acknowledge my indebtedness to the Head of the Department
of Computer Application, Dr. K.V Pramod for gracious encouragement and proper
guidance.
I would like to express my profound thanks to Mrs. Malathi S, Dr.B.Kannan,
Mr.Sreekumar and other faculty members for their help and guidance throughout my
project tenure.
I owe an incalculable debt to all staffs of Department of Computer Application
for their direct and indirect help.
I extend my heartfelt thanks to my parents, friends and well wishers for their
support and timely help
Above all I thank the Almighty for His blessing and providing mercies at all
stages of my work.
Sudheesh V.S
2

SYNOPSIS
3

SYNOPSIS
The project entitled “ROAD STAR – CAR RACING GAME BASED ON JAVA” is an
entertainment game developed in java platform. This game is a car racing game. We
can play this racing car game by a car provided. The game graphics let us to feel like
we are in a real racing environment. The arrow keys in the key board is the controlling
keys in this game.
The game have the following sections
1. Selecting the options for the game
On the start up of this game there will be a main menu from
where we can choose our tasks. There will be options for new game start
by which we can start our game, there will be another option for score
board to show the scored by the previous players, there will be option
for help to understand the game easily, there will be another option to
know about the developer of the game, and also there will be a quit
option to terminate the game. We need to choose any one of the option
given here to proceed to the next stages of the game
2. Game playing section
Here in this section we are ready to play a game. We will be
provided with a car of our own, we can control it using arrow keys in the
key board. By getting the green signal we have to move ahead. During
the play we gets points for our performance. For moving ahead we need
to catch the fuel tanks in the screen when they appeared. One thing we
need to taken care is that we must not hit to the other cars in the game
otherwise we will be out from the game. When we get at the end
successively we will be declared as “RoadStar” and there is an option to
put our name in the game database. So that our name will remain in the
system and others can view it. The all are obtained using a timer in java
and painting concepts of java by which we can control the game. For
keeping the names and scores of the players, here we are using a simple
text file.
4

3. Game Repeating section
Here we can repeat the game after completing the game loop.
For this purpose we use the concept of restarting the timer used, so we
can play the game repeatedly for so many times
5

INTRODUCTION
6

1.INTRODUCTION
1.1 INTRODUCTION TO COMPUTER GAMES
Computer games is a large business industry spread across the world. From the
first generation of computers there is a role of computer games in providing
entertainment to the people. In which racing games are favorite to a quarter of the
total population playing computer games.
1.2 PROJECT DESCRIPTION
“RodStar” is a car racing game developed using java. This game allow the user
to interact with the real time racing game environment. Here user gets the arial
views of the game so that user get more control over the game. By clicking a single jar
file we car start the game, it also shows the simplicity of the game
On starting the game a splash show will be displayed in the screen to show the
title of the game for a while. After that title show there will be appearing a window
with five options namely new game, score board, help, about us, quit. We can study
the options dentally in the next session
I) The first menu item is the start game, As the name implies it is used to start
a new game. On clicking in this option we will go to another menu known as
type of the game, There will be tow options displayed here, They are simple
and hard. As the name implies it will represent the two type of games they
are easy and difficult. If we choose the easy option then it will be less
difficult to achieve the goal. The second option for a difficult type is given
for some dearing persons those who need some adventures to do in order
to reach the goal. By choosing any one of the options we can get in to the
game. There will be one car for us in the screen. After turning the lights of
signal in to green we an start the game, There will be one “Go” display in
the screen which indicates that we must move the car using the arrow keys.
On moving through the road there we will met other cars, If we hit any of
them it will be the end of that session. Then a score board will be displayed
in the screen showing the score of our play. Otherwise if we move with out
hitting to it then we must catch the fuel tanks appearing in the screen in
order to continue our play, Other wise it will be stopped during the play by
7

showing a command that “Out of Fuel”. If we move overcoming these
difficulties if we reach at the end of the track then we will be decleared as
“Road Star” and then we can put our name in the score board. So that
others playing this game can view it . There will be a route map to show the
current position of the car and to show the remaining sections of the game.
II) The second option is the score board, Which will display all of the score
entered in it during the game. This names gives us names of the players
who won the game earlier.
III) Next is a help option by clicking to it we can understand the working of the
game, This is written in simple English.
IV) Next is an about us option by clicking this option we can understand the
details of the developer.
V) Finally there will be quit menu, Which is used to get out of the game easily.
8

SYSTEM ANALYSIS
9

2. SYSTEM ANALYSIS
System analysis deals with the study of the current system. System analysis is
the most critical process of information development. It can be defined as problem
solving which consist of our phases they can be successfully completed by applying
appropriate each dimensions of the information system.
The problem solving aspects of system analysis can be augmented through a
special frame work called pieces categories problem and opportunities problem and
groups, performances, information and data, economy and cost, controls and security
and service.
The purpose of preliminary study phase is to determine the initial feasibility of
a project work. The product of this phase is a feasibility survey that is presented to a
steering committee for a decision on whether the project should be developed. If the
project is approved the next phase is the study of the current system. The purpose of
this phase is to learn how the current system operates. The analyst also identifies the
problem, limitation constraints and brain forms preliminary solutions finally estimates
and present the findings as a problem statement for formal study of phase reports.
The third phase of the system analysis is to define end user requirements for a
new system. The purpose of this phase is to identify what the new and improved
information system must be able to do. The product of this phase is the requirement
statement
The fourth phase is to select a feasible solution from alternative are evaluated
in terms of operational, technical and economic feasibility. The analyst will
recommend the best solution to management for approval. A cost-benefit analysis
determines if the expected systems development and file time costs for a new system
will offset by the benefits of new system.
2.1 Existing system
In the existing system of computer games, there are lots of high end high definition
games but they are high in the case of requirements also. They have greater cost and
greater system requirements like greater random access memory and graphic cards.
So there must be a system with a high definition in look, in performance, in lowest
10

cost development and simple. So being the Road Star has been developed in java we
get all these from Road Star. So the Road Star is recommended here.
Limitations
a. High cost
b. High System requirements(like High RAM, graphic and sound cards etc)
c. More complex
d. Need more size to store
2.2 Proposed System
In our propose system there are real digital images are used so it will provide a high
definition look. It has been developed in java, so it will be features which are
favorable for a proposed system. These are the features of the proposed system
a. Low System requirements
b. Low cost development cost
c. Low disc size requirements
d. Simple
2.3 Feasibility Study
All projects are feasible when given unlimited recourses and infinite time. It is both
necessary and prudent to evaluate the feasibility of a project at the earliest possible
time. A feasibility of a project at the earliest possible time. A feasibility study is not
warranted for a system in which economic justification is obvious, technical risk is
low, few legal problems are expected and no reasonable alternative exists. The study
will decide if the proposed system will be cost effective from business point of view
and if it can be developed in the given existing budgetary constraints. The feasibility
study should be relatively cheap and quick.
Feasibility study may be documented as a separated report to higher officials of toplevel
management and can be included as an appendix to the system specification.
Feasibility and risk analysis is related in many ways. If there is more project risk then
the feasibility of producing the quality software is reduced.
The study is done in three ways
11

a. Operational feasibility
b. Technical feasibility
c. Economical feasibility
Operational feasibility
Proposed project are beneficial only if they can be turned into information systems
that will meet the organization’s operating requirements. Simply started, this test of
feasibility asks if the system will work when it is developed and installed. Are there
major barriers to implementation? Here are questions that will help the operational
feasibility of the project:
Is there support for the project from management?
Are current business methods acceptable to the users?
Have the users been involved in the planning and development of their work?
Will the proposed system cause harm?
The purpose of the operational feasibility study determine whether the new system
will be resistance from users that will undermine the possible Application benefits.
Technical Feasibility
A study of function, performance and containments may improve the ability to create
an acceptable system. Technical feasibility is frequently the most difficult area to
achieve at the stage of product engineering process.
The technical feasibility normally associate with
a. Development risk
b. Recourse availability
c. Technology
Technical feasibility study deals with the hardware as well as software requirements.
The scope was whether the work for the project is done with the current equipments
and existing software technology has to be examined in the feasibility study. The
outcome was found to be positive.
Software feasibility
12

Event though this game is developed in a very high software environment, it will be
supported by many other platforms and environments with minimum changes
Hardware Feasibility
This can be viewed with the resource already existing. Here the consideration is that
the existing hardware resource support the technologies that are to be used by the
new system. No hardware was newly bought for the project and hence peer network
runner software is said to achieve hardware feasibility
Economical feasibility
A cost evaluation is weighted against the ultimate income or benefit derived from the
developed system or product. Economic justification is generally the “bottom-line”
considerations that includes cost benefit analysis, long term corporate income
strategies, impact on the other profit centers or products, cost of resources needed
for development end potential market growth.
13

SYSTEM SPECIFICATION
14

3.SYSTEM SPECIFICATION
3.1 HARDWARE SPECIFICATION
3.2 SOFTWARE SPECIFICATION
RAM -128 Mb or higher
PROCESSOR-Pentium 133 MHz
HARD DISK-10GB
OPERATING SYSTEM-Windows XP/2000/Vista/Windows 7
FRONT END- Java
3.3 SOFTWARE DESCRIPTION
Java
The first release of Java in 1996 generated an incredible amount of excitement, not
just in the computer press, but in mainstream media such as The New York Times, The
Washington Post, and Business Week. Java has the distinction of being the first and
only
programming language that had a ten-minute story on National Public Radio. A
$100,000,000 venture capital fund was set up solely for products produced by use of
aspecific computer language.
Java goes back to 1991, when a group of Sun engineers, led by Patrick Naughton and
Sun Fellow (and all-around computer wizard) James Gosling, wanted to design a small
computer language that could be used for consumer devices like cable TV
switchboxes.
Because these devices do not have a lot of power or memory, the language had to be
small and generate very tight code. Also, because different manufacturers may
choose
different central processing units (CPUs), it was important that the language not be
tied
to any single architecture. The project was code-named “Green.”
The requirements for small, tight, and platform-neutral code led the team to
resurrect
the model that some Pascal implementations tried in the early days of PCs. Niklaus
Wirth, the inventor of Pascal, had pioneered the design of a portable language that
generated
15

intermediate code for a hypothetical machine. (These are often called virtual
machines—hence, the Java virtual machine or JVM.) This intermediate code could
then
be used on any machine that had the correct interpreter. The Green project engineers
used a virtual machine as well, so this solved their main problem.
The Sun people, however, come from a UNIX background, so they based their
language
on C++ rather than Pascal. In particular, they made the language object oriented
rather
than procedure oriented. But, as Gosling says in the interview, “All along, the
language
was a tool, not the end.” Gosling decided to call his language “Oak” (presumably
because he liked the look of an oak tree that was right outside his window at Sun).
The
people at Sun later realized that Oak was the name of an existing computer language,
so
they changed the name to Java. This turned out to be an inspired choice.
In 1992, the Green project delivered its first product, called “*7.” It was an extremely
intelligent remote control. (It had the power of a SPARCstation in a box that was 6
inches by 4 inches by 4 inches.) Unfortunately, no one was interested in producing
this
at Sun, and the Green people had to find other ways to market their technology.
However,
none of the standard consumer electronics companies were interested. The group
then bid on a project to design a cable TV box that could deal with new cable services
such as video on demand. They did not get the contract. (Amusingly, the company
that
did was led by the same Jim Clark who started Netscape—a company that did much
to
make Java successful.)
The Green project (with a new name of “First Person, Inc.”) spent all of 1993 and half
of
1994 looking for people to buy its technology—no one was found. (Patrick Naughton,
one of the founders of the group and the person who ended up doing most of the
marketing,
claims to have accumulated 300,000 air miles in trying to sell the technology.)
First Person was dissolved in 1994.
While all of this was going on at Sun, the World Wide Web part of the Internet was
growing bigger and bigger. The key to the Web is the browser that translates the
hypertext page to the screen. In 1994, most people were using Mosaic, a
noncommercial
16

web browser that came out of the supercomputing center at the University of Illinois
in 1993. (Mosaic was partially written by Marc Andreessen for $6.85 an hour as an
undergraduate student on a work-study project. He moved on to fame and fortune
as one of the cofounders and the chief of technology at Netscape.)
In the SunWorld interview, Gosling says that in mid-1994, the language developers
realized
that “We could build a real cool browser. It was one of the few things in the client/
server mainstream that needed some of the weird things we’d done: architecture
neutral,
real-time, reliable, secure—issues that weren’t terribly important in the workstation
world. So we built a browser.”
The actual browser was built by Patrick Naughton and Jonathan Payne and evolved
into the HotJava browser. The HotJava browser was written in Java to show off the
power of Java. But the builders also had in mind the power of what are now called
applets, so they made the browser capable of executing code inside web pages. This
“proof of technology” was shown at SunWorld ‘95 on May 23, 1995, and inspired the
Java craze that continues today.
Sun released the first version of Java in early 1996. People quickly realized that Java
1.0
was not going to cut it for serious application development. Sure, you could use Java
1.0
to make a nervous text applet that moved text randomly around in a canvas. But you
couldn’t even print in Java 1.0. To be blunt, Java 1.0 was not ready for prime time. Its
successor, version 1.1, filled in the most obvious gaps, greatly improved the reflection
capability, and added a new event model for GUI programming. It was still rather
limited, though.
The big news of the 1998 JavaOne conference was the upcoming release of Java 1.2,
which replaced the early toylike GUI and graphics toolkits with sophisticated and
scalable
versions that come a lot closer to the promise of “Write Once, Run Anywhere”
than its predecessors. Three days after (!) its release in December 1998, Sun’s
marketing
department changed the name to the catchy Java 2 Standard Edition Software
Development
Kit Version 1.2.
Besides the Standard Edition, two other editions were introduced: the Micro Edition
for
embedded devices such as cell phones, and the Enterprise Edition for server-side
processing.
This book focuses on the Standard Edition.
17

Versions 1.3 and 1.4 of the Standard Edition are incremental improvements over the
initial
Java 2 release, with an ever-growing standard library, increased performance, and,
of course, quite a few bug fixes. During this time, much of the initial hype about Java
applets and client-side applications abated, but Java became the platform of choice
for
server-side applications.
Version 5.0 is the first release since version 1.1 that updates the Java language in
significant
ways. (This version was originally numbered 1.5, but the version number jumped
to 5.0 at the 2004 JavaOne conference.) After many years of research, generic types
(which are roughly comparable to C++ templates) have been added—the challenge
was
to add this feature without requiring changes in the virtual machine. Several other
useful
language features were inspired by C#: a “for each” loop, autoboxing, and metadata.
Language changes are always a source of compatibility pain, but several of these new
language
features are so seductive that we think that programmers will embrace them
eagerly.
Key features of java
a. Architecture Neutral
b. Simple
c. Portable
d. Object Oriented Interpreted
e. Network-Savvy
f. High Performance
g. Robust
h. Multithreaded
i. Secure
j. Dynamic
18

SOFTWARE QUALITY ASSURANCE PLAN
19

4.SQA PLANPURPOSE
The purpose of this plan is to define “Road Star” software quality assurance
organization, SQA tasks and responsibilities; provide reference documents and
guidelines to perform the SQA activities ; provide the standards, practices and
conventions used in carrying out SQA activities; and provide the tools, techniques,
and methodologies to support SQA activities, and SQA reporting.
SCOPE
This plan establishes the SQA activities performed throughout the life cycle of the
“Road Star”. Specifically, this SQA plan will show that the SQA group has a reporting
channel to senior management that is independent of the project manager, the
project’s software engineering group, and software related groups that include
Software configuration Management (SCM), System and Software Test, and Logistics.
The goal of the SQA program is to verify that all software and documentation to
be delivered meet all technical requirements. The SQA procedures defined herein
shall be used to examine all deliverable software and documentation to determine
compailence with technical and performance requirements
SYSTEM OVERVIEW
The “Road Star” is a car racing game, the below figure identifies the CIs within each
subsystem and highlights those to which this SQA plans applies
Software Life Cycle Activities
SOFTWAE LIFECYCLE ACTIVITIES
Project Planning and Oversight
Software Development Environment
System Requirements Analysis
System Design
Software Requirement Analysis
Software Design
Software Implementation and Unit Testing
Unit Integration and Testing
CI Qualification Testing
CI/Hardware Configuration Item(HWCI)
20

DOCUMENT OVERVIEW
Integration and Testing
System Qualification Testing
Software Use Preparation
Software Transition Preparation
Life Cycle Maintanance
This document identifies the organizations and procedures to be used to perform
activities related to the “Road Star”. Section 1 identifies the system to which this SQA
plan applies; provides an overview of the system and its software functions;
summarizes the purpose and contents of the SQA plan; and describes the relationship
of the SQA plan to other management plans and lists all documents referenced
referenced in SQA plan.
STANDARDS,PRACTICES,CONVENTIONS AND METRICES
To verify the delivery of a fully conforming, high-quality product, every individual
assigned to the project will participate in quality assurance. This section describes the
procedures used by SQA to verify that the quality assurance provisions of SQA plan
and applicable standard, practices, conventions, and matrices are met.
SOFTWARE QUALITY PROGRAM
To verify the delivery of a fully conformating , high-quality product, every individual
assigned to the project will participate in quality assurance. This section describes the
procedures used by SQA to verify that the quality assurance provisions of this SQA
plan and applicable standards, practices, conventions, and matrices are met.
METRICES
The following measurements will be made and used to determine the cost and
schedule staus of the SQA activities: SQA milestone dates(planned)
a. SQA milestone dates(Completed)
b. SQA work scheduled(planned)
c. SQA work completed(actual)
d. SQA effort expanded(Planned)
e. SQA effort expended(actual)
21

f. SQA funds expended(actual)
g. SQA funds expended(planned)
h. Number of non compailance item open
i. Number of non compailence item closed
j. Total number of noncompailence items
SQA is resposable for reporting these measurements to the project Manager on a
monthly basis.
TOOLS,TECHNIQUES,AND METHODOLOGIES
Tools-SQA software tool include, but are not limited to, operating system utilities,
debugging aids, documentation aids, checklists, structuring preprocessors, file
comparators, structure analyzers, code analyzers, standard auiditors, simulators,
execution analyzers, performance monitors, statistical analysis packages, software
development folder/files, software traceablity matrices, test drivers, test case
generators, static or dynamic test tools, and information engineering CASE tools
Techniques-techniques includes review of the use of standards, software inspections,
requirements tracing, requirements and design verifications, reliability
measurements, and assessments, and rigorous logic analysis.
Methodologies-methadologies are an integrated set of the above tools and
techniques. The methodologies should be well documented for accomplishing the
task or activity and provide description of the process to be used
Where applicable, SQA will use SEPO organizational process and tailor the processes
specific to the project
APPENDICES
AI Action Item
CDR Critical Design Review
CMM Capability Maturity Model
CMU Carnegie-Mellon University
CRLCMP Computer Resources Life Cycle Management Plan
CI Configuration Item
22

DBDD Data Item Description
DCR Document Change Request
DID Data Item Description
EIA Electronic Industries Association
FCA Functional Configuration Audit
FQR Formal Qualification Review
HB Handbook
HWCI Hardware Configuration Item
IDD Interface design Description
IEEE Institute of Electrical and Electronics Engineers
IRS Interface Requirement Specification
KPA Key Process Areas
SU Software Unit
STD Standard
23

SYSTEM DESIGN
24

5.SYSTEM DESIGN
Design is the first step in development phase of every engineered product or
system. In the case of computer games design is an important thing. The design phase
consist of may other phases
a. Option design
The first part of the design process is the option design. Which is used to define
the menu options for this we use digital images
b. Track Design
The most important phase of the computer game design is the track design in
which we can design the trcks in which the cars are moving. For this we use the
digital images.
c. Action design
In this phase we will discuss about the actions performed by the game like
collision and hitting etc
d. Score Board Design
In this phase we design the score board in which the scores to be displayed. For
this purpose we use digital images
e. Over all Design
The overall design phase include in which the other options are designed with
the digital images
25

DATA DESIGN
26

6.DATA DESIGN
Class Diagrams
bug
About
27

Car
28

GameOver
help
29

HighScore
MainGame
30

PanelSplash
Register
31

settings
splash
32

signal
33

Signal1
34

Main
35

SYSTEM TESTING
36

7.SYSTEM TESTING
Software testing is a critical element of quality assurance and represents the
ultimate preview of specifications, design and coding. Testing represents an
interesting anomaly for the software. Doing the earlier definition and development
phase it was attempted to buid a software from an abstract concept to a tangiable
implementation. The various types of testing done on the system is
a. Unit testing
b. Integration Testing
c. Validation Testing
Unit testing
A unit focuses verification effort on the smallest limit of software
design. Using the unit test plan prepared in the design phases of the system,
important control paths are tested to uncover the errors within the module.
This testing was carried out during the coding itself.
Integration Testing
Integration testing is the systematic technique for constructing the
program structure while at the same time conducting test to uncover errors
associated with the interfaces. The objective is to take unit tested modules
and build the program structure that has been dictated by design. All
modules are combined in this testing step.
Validation Testing
At the end of integration testing, software is completely assembled as a
package, interfacing errors have been uncovered and corrected and final
series of software validation and testing begins
Debugging
Debugging is the process of isolating and correcting the cause of known
errors. Success at debugging requires highly developed problems skills.
Commonly used debugging methods include induction, deduction and
backtracking. Debugging by induction involves the following steps
Collect the following information
37

a. Tools for patters
b. From one or more hypothesis
c. Prove or disprove each hypothesis
d. Implement the appropriate correction
e. Verify the correction
f. Debugging the deductive involves
g. List Possible cause for the observed failure
h. Elaborate the remaining hypothesis
38

IMPLEMENTATION
39

8.IMPLEMENTATION
Implementation is the stage of the project where the theoretical design is turned
in to a working system. At this stage, one main work load, the greatest upheaval and
the major impact on existing practices shifts to the user department. If the
implementation is not carefully planned and controlled it can cause chaos and
confusions. Thus it can be considered as the most critical stage in achieving a
successful new system and in giving the users confidence that the new system will
work effective. The major tasks performed in this phase are
a. Training the system users
b. Developing Operating procedures to repair and enhancing the system
c. Evaluating the final system to check for its time and budget constraints
To achieve the objective and benefits expected from the
computer based system it is essential for the people who will be involved to be
confident of their role in the new system. This involve them in understanding the
system and in effects on the organization and in being able to carry out effectively the
specific task. As a system become more complex the need for educating and training
is more important
40

FUTURE ENHANCEMENT
41

9. FUTURE ENHANCEMENT
In future we can enhance this “Road Star Game” using new technologies
because its codes are so simple that a lay man can understand. Since this is
developed in java which is truly object oriented language it support the future
additions and eliminations in the code. We can increase the flexibility with
adding new levels to the game and new items in the appearance of the game.
So “Road Star” is developed not only for today but also for tomorrow
42

CONCLUSION
43

10.CONCLUSION
“Road star ” is a simple game developed using java concepts. Its simplicity is
very useful in now a days because tablet computers are becoming popular now
a days, So “RoadStar” like game have great future
44

SCREEN SHOTS
45

10.SCREEN SHOTS
Splash Screen
46

Main Menu
47

Type of game
48

Game
49

Game
50

Game
51

Game Finished
52

BIBLIOGRAPHY
53

11.BIBLIOGRAPHY
Core Java. Volume I, Fundamentals / Cay S. Horstmann, Gary Cornell. —8th ed.
Killer game programming in java Tom Harrisom, Killy Wood
54