Game Development Reference
Solutions to Bridge
The idea has been to treat legacy systems as a black box and deal with them
at more than arm's length. All of this has made it possible to make many of
these systems look like they were part of the 21st Century, leaving the tough
stuff—the data and the business rules—untouched. If it ain't broke, don't
fix it, right? Well, not exactly. Of course, old systems don't get better by just
being ignored. They get worse.
One of the major goals for software engineering in the past decade has been to
build software that promotes abstracted reusability. Because of this, developers
witnessed the emergence of the object-oriented paradigm, which resulted in the
introduction of reusable object-oriented frameworks. An object-oriented frame-
work can be defined as a set of classes that embody an abstract design for solutions
to a collection of related problems in a given problem domain.
The high reusability of frameworks is quite evident to software engineers, and it
has solved many problems related to the goal of improved component reusability.
With the emergence of new disciplines comes new issues and problems that must
be addressed. Where single frameworks were originally used, we are now seeing a
shift towards multiple frameworks that must communicate with each other in a
cohesive fashion. Often there are problems communicating across dissimilar
domain gaps, especially when each framework is being developed by a different