OOA—Analysis and Mission - Programming GPS and OpenStreetMap Applications with Java - page 31

3.8 The Mission

The end of the analysis phase marks the beginning of the programming
project. This topic only indicates how to apply OOA methodologies and
the reader is advised to discuss these ideas with other programmers in order
to develop their own visions of the framework.
The most important aspect of the mission is to define the end of a
project|to have a well-dened goal. Without an actual implementation,
the definition of the end may be fuzzy. The phase from the first lines of
code to a running demonstration platform is the mission of this topic. We
describe the process in order to hopefully establish a development life cycle
for an online community at www.roaf.de .
A technique for rapid development might be described as \minimum
implementation with maximum abstraction." Object-oriented development
enables architects to work on different levels of granularity, similar to filling
a large hole. At first big rocks are used to roughly fit the shape, then smaller
rocks fill the space between the big ones, and finally fine sand is added to
fill remaining gaps.
On page 9, a car was introduced as an object participating in different
scenarios with other cars. This simple setting can easily serve as a sample
scenario: A car (or vehicle) is a special type of RO, many cars make up
trac, and the ROApp scenario is a given area (i.e., city) on the globe.
By defining a reference application (or presentation prototype) the
project manager denes a goal|together with the software customer. The
customer is probably not interested in whether the software is object ori-
ented. He can perhaps understand that different cars can be simulated on
client machines, while they are represented on a server frontend|a map.
From here on, the customer's view (cars, trac, city) are decoupled from
the programmer's perspective (RO client, ROApp server).
Of course, the scenario is still vague, but for programmers it is much
more useful than the initial vision. Programmers can begin concrete coding
without additional details.
The mission of this topic is
ˆ to create a distributed client-server application with
{the clients representing vehicles (players). . .
ˆ to populate a server application (game observer) with
{a map scenario (game board) and a ruleset (controller).

In other words, the topic will provide a prototype roafv1.0 , which
marks the end of the initial coding from scratch and the beginning of an
evolutionary life-cycle development. The prototype makes communication
between all parties much easier, including product definition, customer
presentations, and marketing research.