Evolution - Programming GPS and OpenStreetMap Applications with Java - page 219

written, produced, and directed by Christopher Nolan and distributed by
Warner Bros. Pictures can be modeled as an ROApp.
Inception is about entering another person's dream world (in this case
without a hard-wired connection to the brain as in the movie, The Matrix ).
One person is hosting other people's mental self-projections in his dream
world. In ROAF terminology, the dreamer is not only providing his RO,
but rather comes with his own ROApp. People entering other people's
dreams are intuitively recognized by the projections of people close to the
dreamer. These projections are nothing but SO agents in his ROApp dream
world, which he can model with his own creativity; like bending physical
laws.
Inception adds more fictitious ROApp layers to the scenario. In a simple
dream, any actor can wake up from the scenario by dying in it. For a dream
in a dream (in a dream), a powerful sedative is needed to stabilize the layers
of the shared dream. In the fractal ROAF, a dream in another dream can be
modeled with one main ROApp. When entering the deeper layer, another
ROApp comes up with another scenario; yet, the second ROApp underlies
the higher ROApps rules and laws. For example, loss of gravity in the
higher level influences the lower level accordingly. This cascade of ROApps
adds technical challenges to the ROApp architect.
In each layer, one person (RO) is creating a dream (ROApp) to travel
further into the initial dreamer's subconscious. The exit rules are complex;
a dreamer has to be \kicked" physically in order to pop out of the current
dream level. This kick has to be set up by a trusted person outside of
the dream world by kicking the physical body to fall and lose his sense of
gravity. Another appealing aspect is the time factor: every dream level has
a subjective time factor of about five to 60 minutes (i.e., 1/12).
So, the ROAF should pose no limits to your imagination.

14.4 RO Classification

Just like a ROApp can reflect almost any (real) world scenario, the RO can
represent any (physical) object in a scenario. In the long run, ROApp and
RO development should be gradually decoupled. Loose coupling implies
that individual objects should reduce unrelated information, while high
cohesion is complementary and provides information connecting objects to
collaborate.
In the ROAF context, the cohesion (framework layer) is provided by re-
ality and scientific knowledge, while individual developments can be loosely
coupled (application layer). Constructing ROs independently for different
ROApps will make them robust in the long run. The object can be tested
in different environments and under different aspects to reduce them to
their core attributes and optimize them for reusability.