Cascaded refactoring for framework

ABSTRACT

Refactoring of source code has been studied as a preliminary step in the evolution of object-oriented software. We extend the concept of refactoring to the whole range of models used to describe a framework in our methodology: feature model, use case model, architecture, design, and code. We view framework evolution as a two-step process: refactoring and extension. The refactoring step is a set of refactorings, one for each model, that cascades through them. The refactorings chosen for a model become the rationale or constraints for the choice of refactorings of the next model. The cascading of refactorings is aided by the alignment of the models. Alignment is a traceable mapping between models that preserves the commonality-variability aspects of the models.

REFERENCES

• 1: Jay Banerjee , Won Kim , Hyoung-Joo Kim , Henry F. Korth, Semantics and implementation of schema evolution in object-oriented databases, Proceedings of the 1987 ACM SIGMOD international conference on Management of data, p.311-322, May 27-29, 1987, San Francisco, California, United States
• 2: Ira D. Baxter, Design maintenance systems, Communications of the ACM, v.35 n.4, p.73-89, April 1992 [doi>10.1145/129852.129859]
• 3: Ira Baxter, DMS (transformational software maintenance by reuse): a production research system? (keynoted talk), Proceedings of the 1999 symposium on Software reusability, p.163, May 21-23, 1999, Los Angeles, California, United States [doi>10.1145/303008.303076]
• 4: G. Butler. Developing frameworks by aligning requirements, design, and code. In Proceedings of 9th Workshop on Software Reuse (WISR-9), 1999.
• 5: P. Clements and L. Northrop. A framework for software product line practice | version 2.0. Technical report, SEI, CMU, 1999.
• 6: Serge Demeyer , Theo Dirk Meijler , Oscar Nierstrasz , Patrick Steyaert, Design guidelines for “tailorable” frameworks, Communications of the ACM, v.40 n.10, p.60-64, Oct. 1997 [doi>10.1145/262793.262805]
• 7: Desmond F. D'Souza , Alan Cameron Wills, Objects, components, and frameworks with UML: the catalysis approach, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1998
• 8: Mohamed E. Fayad , Douglas C. Schmidt , Ralph E. Johnson, Building application frameworks: object-oriented foundations of framework design, John Wiley & Sons, Inc., New York, NY, 1999
• 9: Refactoring: improving the design of existing code, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1999
• 10: M. L. Griss , J. Favaro , M. d' Alessandro, Integrating Feature Modeling with the RSEB, Proceedings of the 5th International Conference on Software Reuse, p.76, June 02-05, 1998
• 11: Ivar Jacobson , Martin Griss , Patrik Jonsson, Software reuse: architecture, process and organization for business success, ACM Press/Addison-Wesley Publishing Co., New York, NY, 1997
• 12: R. E. Johnson and B.Foote. Designing reusable classes. Journal of Object-Oriented Programming, pages 22-35, July 1988.
• 13: Kyo C. Kang , Sajoong Kim , Jaejoon Lee , Kijoo Kim , Euiseob Shin , Moonhang Huh, FORM: A feature-oriented reuse method with domain-specific reference architectures, Annals of Software Engineering, 5, p.143-168, 1998
• 14: Philippe Kruchten, The 4+1 View Model of Architecture, IEEE Software, v.12 n.6, p.42-50, November 1995 [doi>10.1109/52.469759]
• 15: P. Madany, R. Campbell, V. Russo, and D. Leyens. A class hierarchy for building stream-oriented file systems. In Proceedings of ECOOP'89, pages 311-328, 1989.
• 16: Kai-Uwe Mätzel , Walter R. Bischofberger, Designing object systems for evolution, Theory and Practice of Object Systems, v.3 n.4, p.265-283, 1997 [doi>10.1002/(SICI)1096-9942(1997)3:4<265::AID-TAPO4>3.0.CO;2-R]
• 17: G. Miller, J. McGregor, and M. Major. Capturing framework requirements.InM. E. Fayad, D. C. Schmidt, and R. E. Johnson, editors, Building Application Frameworks: Object-Oriented Foundations of Framework Design. Wiley, 1999.
• 18: William F. Opdyke, Refactoring object-oriented frameworks, University of Illinois at Urbana-Champaign, Champaign, IL, 1992
• 19: Colin Potts , Kenji Takahashi , Annie I. Antón, Inquiry-Based Requirements Analysis, IEEE Software, v.11 n.2, p.21-32, March 1994 [doi>10.1109/52.268952]
• 20: Wolfgang Pree, Design patterns for object-oriented software development, ACM Press/Addison-Wesley Publishing Co., New York, NY, 1995
• 21: Bjorn Regnell Lund , Michael Andersson , Johan Bergstrand, A Hierarchical Use Case Model with Graphical Representation, Proceedings of the IEEE Symposium and Workshop on Engineering of Computer Based Systems, p.270, March 11-15, 1996
• 22: Don Roberts , John Brant , Ralph Johnson, A refactoring tool for Smalltalk, Theory and Practice of Object Systems, v.3 n.4, p.253-263, 1997 [doi>10.1002/(SICI)1096-9942(1997)3:4<253::AID-TAPO3>3.3.CO;2-I]
• 23: Don Roberts , Ralph Johnson, Patterns for evolving frameworks, Pattern languages of program design 3, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1997
• 24: Han Albrecht Schmid, Systematic framework design by generalization, Communications of the ACM, v.40 n.10, p.48-51, Oct. 1997 [doi>10.1145/262793.262803]
• 25: Mary Shaw , David Garlan, Software architecture: perspectives on an emerging discipline, Prentice-Hall, Inc., Upper Saddle River, NJ, 1996
• 26: STARS. Organization domain modeling (ODM) guidebook | version 2.0. Technical report, Lockheed Martin Tactical Defense Systems, 1996.
• 27: Lance Tokuda , Don Batory, Evolving Object-Oriented Designs with Refactorings, Proceedings of the 14th IEEE international conference on Automated software engineering, p.174, October 12-15, 1999
• 28: L. Tokuda and D. Batory. Automating software evolution via design pattern transformations. In 3rd International Symposium on Applied Corporate Computing, October 1995.
• 29: L. Tokuda and D. Batory. Automating three modes of evolution for object-oriented software architectures. In 5th USENIX Conference onObject-Oriented Technologies (COOTS'99), May 1999.
• 30: David M. Weiss , Chi Tau Robert Lai, Software product-line engineering: a family-based software development process, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1999

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.11 Software Architectures
            Subjects: Domain-specific architectures

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.3 Coding Tools and Techniques
          Subjects: Object-oriented programming
  D.3 PROGRAMMING LANGUAGES
      D.3.3 Language Constructs and Features
          Subjects: Frameworks

General Terms:
Design, Languages, Performance, Theory

Keywords:
architecture, design pattern, domain analysis, evolution, feature model, framework, hotspot, refactoring, role, use case