Co-evolving application code and design models by exploiting meta-data

ABSTRACT

Evolvability and adaptability are intrinsic properties of today's software applications. Unfortunately, the urgency of evolving/adapting a system often drives the developer to directly modify the application code neglecting to update its design models. Even, most of the development environments support the code refactoring without supporting the refactoring of the design information.

Refactoring, evolution and in general every change to the code should be reflected into the design models, so that these models consistently represent the application and can be used as documentation in the successive maintenance steps. The code evolution should not evolve only the application code but also its design models. Unfortunately, to co-evolve the application code and its design is a hard job to be carried out automatically, since there is an evident and notorious gap between these two representations.

We propose a new approach to code evolution (in particular to code refactoring) that supports the automatic co-evolution of the design models. The approach relies on a set of predefined metadata that the developer should use to annotate the application code and to highlight the refactoring performed on the code. Then, these meta-data are retrieved through reflection and used to automatically and coherently update the application design models.

REFERENCES

• 1: W. Cazzola, A. Cisternino, and D. Colombo. Freely Annotating C#. Journal of Object Technology, 4(10):31--48, Dec. 2005.
• 2: W. Cazzola, A. Ghoneim, and G. Saake. Viewpoint for Maintaining UML Models against Application Changes. In Proc. of ICSOFT 2006, pages 263--268, Sétubal, Portugal, Sept. 2006. Springer.
• 3: W. Cazzola, S. Pini, and M. Ancona. The Role of Design Information in Software Evolution. In Proc. of RAM-SE'05, pp. 59--70, Glasgow, Scotland, July 2005.
• 4: T. D'Hondt, K. De Volder, K. Mens, and R. Wuyts. Co-Evolution of Object-Oriented Software Design and Implementation. In Proc. of ISSACT 2000, pp. 207--224, Twente, The Netherlands, Jan. 2000. Kluwer.
• 5: M. Fowler. Refactoring: Improving the Design of Existing Code. Addison-Wesley, Reading, Massachusetts, June 1999.
• 6: Multi-View Software Evolution: A UML-based Framework for Evolving Object-Oriented Software, Proceedings of the IEEE International Conference on Software Maintenance (ICSM'01), p.386, November 07-09, 2001
• 7: James Gosling , Bill Joy , Guy Steele , Gilad Bracha, Java(TM) Language Specification, The (3rd Edition) (Java (Addison-Wesley)), Addison-Wesley Professional, 2005
• 8: K. Mens, A. Kellens, F. Pluquet, and R. Wuyts. Co-evolving Code and Design Using Intensional Views - A Case Study. Journal of Computer Languages, Systems and Structures, 32(2):140--156, July/Oct. 2006.
• 9: M. Torchiano, F. Ricca, and P. Tonella. A Comparative Study on the Re-Documentation of Existing Software: Code Annotations vs. Drawing Editors. In Proc. of ISESE'05, pp. 277--286, Noosa Heads, Australia, Nov. 2005.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.3 Coding Tools and Techniques

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.7 Distribution, Maintenance, and Enhancement

  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.1 Project and People Management
          Subjects: Systems analysis and design

General Terms:
Design

Keywords:
Co-evolution, meta-data, refactoring, reflection, software evolution