Systems reengineering patterns

ABSTRACT

The reengineering of legacy systems --- by which we mean those that have value and yet "significantly resist modification and evolution to meet new and constantly changing business requirements" --- is widely recognised as one of the most significant challenges facing software engineers. The problem is widespread, affecting all kinds of organisations; serious, as failure to reengineer can hamper an organisation's attempts to remain competitive; and persistent, as there seems no reason to be confident that today's new systems are not also tomorrow's legacy systems.This paper argues1. that the main problem is not that the necessary expertise does not exist, but rather, that it is hard for software engineers to become expert;2. that the diversity of the problem domain poses problems for conventional methodological approaches;3. that an approach via systems reengineering patterns can help.We support our contention by means of some candidate patterns drawn from our own experience and published work on reengineering. We discuss the scope of the approach, how work in this area can proceed, and in particular how patterns may be identified and confirmed.

REFERENCES

• 1: Appleton, Brad, "Patterns for conducting process improvement" In Proceedings of PLoP'97.
• 2: Beedle, Michael "Pattern Based Reengineering", Object Magazine, 1997
• 3: Bergey, John K., Northrup, Linda M., and Smith, Dennis B. "Enterprise Framework for the Disciplined Evolution of Legacy Systems", Technical Report CMU/SEI- 97-TR-007 (1997)
• 4: Michael L. Brodie , Michael Stonebraker, Migrating legacy systems: gateways, interfaces & the incremental approach, Morgan Kaufmann Publishers Inc., San Francisco, CA, 1995
• 5: Brown, Alan W., Morris, Ed J., and Tilley, Scott R. 'Assessing the Evolvability of a Legacy System", CMU SE1 draft white paper, 1996
• 6: Frank Buschmann , Regine Meunier , Hans Rohnert , Peter Sommerlad , Michael Stal, Pattern-oriented software architecture: a system of patterns, John Wiley & Sons, Inc., New York, NY, 1996
• 7: Coplien, James O., "A Development Process Generative Pattern Language", in Proceedings of PLOP'95
• 8: Cunningham, Ward. "EPISODES: A Pattern Language of Competitive Development", available &om http://vvv.c2.com/ppr/titles.html.
• 9: Ducasse, S., Nebbe, R. and Richner, T. "Type-Check Elimination: Two Reengineering Patterns", presented at EuroPLOP'98.
• 10: Erich Gamma , Richard Helm , Ralph Johnson , John Vlissides, Design patterns: elements of reusable object-oriented software, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1995
• 11: Ivar Jacobson , Fredrik Lindström, Reengineering of old systems to an object-oriented architecture, Conference proceedings on Object-oriented programming systems, languages, and applications, p.340-350, October 06-11, 1991, Phoenix, Arizona, United States
• 12: Opdyke, William Object-Oriented "Refactoring, Legacy Constraints and Reuse", presented at 8th Workshop on Institutionalizing Software Reuse (1996)
• 13: OrganizationalPatterns web page, administered by Jim Coplien. http://wuu. bell-labs. com/cgi-user/ OrgPattexns/ClrgPattems
• 14: J. Ransom , I. Sommerville , I. Warren, A Method for Assessing Legacy Systems for Evolution, Proceedings of the 2nd Euromicro Conference on Software Maintenance and Reengineering ( CSMR'98), p.128, March 08-11, 1998
• 15: "The RENAISSANCE project" information and some documents available from http://uuw.comp.lancs.ac.uk/ computing/reseaxch/cseg/projects/renaissance/ RenaissanceWeb.
• 16: "Software Reengineering Assessment Handbook v3.0" available from http://stsc.hill.af.mil/RENG/

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.7 Distribution, Maintenance, and Enhancement
          Subjects: Restructuring, reverse engineering, and reengineering

Additional Classification:
  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.3 Software Management
          Subjects: Software development

General Terms:
Design, Performance, Theory