Abstract
In reengineering legacy code it is frequently useful to introduce a design pattern in order to add clarity to the system and thus facilitate further program evolution. We show that this type of transformation can be automated in a pragmatic manner and present a methodology for the development of design pattern transformations. We address the issues of the definition of a starting point for the transformation, the decomposition of a pattern into mini-patterns and the development of corresponding mini-transformations that can introduce these mini-patterns to a program. We argue that behaviour preservation is a key issue and develop a rigorous argument of this for each mini-transformation we discover. The architecture of an existing software prototype is also discussed and the results of applying this methodology to develop a transformation for the Factory Method pattern are presented.
Original language | English |
---|---|
Title of host publication | Proceedings IEEE International Conference on Software Maintenance |
Subtitle of host publication | Software Maintenance for Business Change, 1999 (ICSM'99). |
Place of Publication | United States |
Publisher | IEEE, Institute of Electrical and Electronics Engineers |
Pages | 1-10 |
Number of pages | 10 |
ISBN (Print) | 0769500161 |
DOIs | |
Publication status | Published - 1999 |
Externally published | Yes |
Event | IEEE International Conference on Software Maintenance-1999 (ICSM ’ 99) - Keble College, Oxford, United Kingdom Duration: 30 Aug 1999 → 3 Sept 1999 |
Conference
Conference | IEEE International Conference on Software Maintenance-1999 (ICSM ’ 99) |
---|---|
Abbreviated title | ICSM 99 |
Country/Territory | United Kingdom |
City | Oxford |
Period | 30/08/99 → 3/09/99 |