Object-Oriented Reengineering
|
|
|
The documentation is missing or obsolete, and the
original developers have departed. Your team has limited
understanding of the system, and unit tests are missing for
many, if not all, of the components. When you fix a bug in
one place, another bug pops up somewhere else in the
system. Long rebuild times make any change difficult. All
of these are signs of software that is close to the
breaking point.
Many systems can be upgraded or simply thrown away if they
no longer serve their purpose. Legacy software, however, is
crucial for operations and needs to be continually
available and upgraded. How can you reduce the complexity
of a legacy system sufficiently so that it can continue to
be used and adapted at acceptable cost?
Based on the authors' industrial experiences, this book is
a guide on how to reverse engineer legacy systems to
understand their problems, and then reengineer those
systems to meet new demands. Patterns are used to clarify
and explain the process of understanding large code bases,
hence transforming them to meet new requirements. The key
insight is that the right design and organization of your
system is not something that can be evident from the
initial requirements alone, but rather as a consequence of
understanding how these requirements evolve.
Conseillez cet ouvrage à un ami
Pour votre veille bibliographique :
Des services gratuits pour être informé des nouveautés qui vous intéressent...
Abonnez-vous !
eyrolles.com est un service de la Librairie Eyrolles - 61, boulevard Saint-Germain - 75005 Paris
© 1999-2009 Groupe Eyrolles
