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?
This text 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.
- Front Matter
- 1: Reengineering Patterns
- 2: Setting Direction
- 3: First Contact
- 4: Initial Understanding
- 5: Detailed Model Capture
- 6: Tests — Your Life Insurance!
- 7: Migration Strategies
- 8: Detecting Duplicated Code
- 9: Redistribute Responsibilities
- 10: Transform Conditionals to Polymorphism
- 11: Appendix A – Thumbnail Patterns
- Back Matter
Thumbnail photo by Ilya Pavlov on Unsplash.