The most
appropriate architectural structural model would be a centralized model with a
shared repository for route and pricing information. Storing all the
information in a central location allows for changes to be immediately
available to all ticket machines. It’s reasonable to assume that there are
other subsystems used for administrative functions (such as updating the data
in the repository). The centralized system also allows global information (ex
ticket sales) and route use to be collected and processed.
Given the
distributed nature of this application, one might be led to consider a
client/server architecture. If there is only one server (the repository), the
actual structure would be the same (as the repository structure), regardless of
what you call it.
-------------------
·
A computer controlled video conferencing system
which allows video, audio and computer data to be visible to several
participants at the same time
The most
appropriate structure here is a client server model. The client application
would be required to do considerable processing to handle the complex
multimedia data fed to it from the server(s)
--------------
·
A robot floor cleaner that is intended to clean
relatively clear spaces such as corridors. The cleaner must be able to sense
walls and other obstructions
The most
appropriate model is a repository model, with each of the subsystems (Wall and
obstacle sensors, path planning, vision (perhaps), etc) placing information in
the repository for other sub systems to use. Robotic applications are in the
realm of Artificial Intelligence, and for AI systems such as this, a special
kind of repository called a blackboard (where the presence of data activates
particular subsystems) is normally user
