The Vision of a RealWorld Simulator - Programming GPS and OpenStreetMap Applications with Java - page 21

Matrix is the idea of constructing a virtual world to reflect the real world.
This virtual world can be entered and exited with given conditions (fixed
phone lines). Once the RO client (in Matrix jargon, residual self image) has
entered, he can interact with the underlying laws governing other objects,
for example, gravity. The mission is to discern the difference between the
virtual and real world|the ROAF Turing Test. That is, to determine who
of the other people is also remotely connected to the matrix, who is an
agent, or who is a sentient program only existing inside this virtual world
and fighting intruders?
This analogy of the ROAF and the movie, The Matrix, should inspire
a more lively discussion of the vision of this topic|developing the funda-
mental architecture for a real-world simulation.
Conclusion
You should hopefully now know what the vision is all about? Are three
definitions sucient to clearly define software, and can you create software
to realize the vision?
Like most visions, this one is a little fuzzy and it requires effort and
experience to transform it into software. Although the vision was derived
from objects and physical laws, every reader probably has his own idea of
what the RO, ROApps, and ROAF will actually look like. Therefore, the
vision has to be formalized to a more technical level.
Before starting any team development effort, the vision has to be trans-
formed into a concrete mission. To minimize time and costs, standards
have (been) developed to optimize this phase:
Object-oriented Analysis (OOA) and Design (OOD) Methodologies
Object orientation is key for transforming vague visions into isolated work-
ing steps for programmers. The object-oriented paradigm allows software
architects to design small software pieces, which can be developed indepen-
dently in incremental cycles. Central to all methods and tools is the idea
that any system is composed of objects with individual behavior (imple-
mentation) and those objects are able to communicate with other objects
by exchanging information (messages). Experienced project managers can
use high-level (project) tools to visually model software and directly gen-
erate the source code (skeleton).
Even if the implementation varies, the cognitive process should be simi-
lar. The topic describes this process in detail, implemented with the Stan-
dard Java SDK. The reader can, of course, choose his own implementation.