Wiley Encyclopedia of Computer Science and Engineering 2007
DOI: 10.1002/9780470050118.ecse330
|View full text |Cite
|
Sign up to set email alerts
|

Program Transformation: What, How, and Why

Abstract: Transformation can be viewed as a philosophy on how to achieve change. A rigorous treatment of transformation has its roots in equational reasoning —the idea that equals can be substituted for equals. This article explores transformation as it applies to the manipulation of software.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1

Citation Types

0
4
0

Year Published

2012
2012
2015
2015

Publication Types

Select...
2
2

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(4 citation statements)
references
References 19 publications
0
4
0
Order By: Relevance
“…(3) The dimensions of software change in the context of software evolution and maintenance (Buckley et al, 2003;Benestad et al, 2009). By comparing taxonomies of Benestad et al (2009), Buckley et al (2003) with the ones of Visser (2001), Winter (2004), we conclude that two terms (i.e., change and transformation) define the same issue but from different perspectives and scope (e.g., development and evolution). The following observation is important to state in this context: the nature of software evolution now is shifting to "a continuous process, in which there's no neat boundary between development and evolution" (Boehm, 2010).…”
Section: Related Workmentioning
confidence: 98%
See 1 more Smart Citation
“…(3) The dimensions of software change in the context of software evolution and maintenance (Buckley et al, 2003;Benestad et al, 2009). By comparing taxonomies of Benestad et al (2009), Buckley et al (2003) with the ones of Visser (2001), Winter (2004), we conclude that two terms (i.e., change and transformation) define the same issue but from different perspectives and scope (e.g., development and evolution). The following observation is important to state in this context: the nature of software evolution now is shifting to "a continuous process, in which there's no neat boundary between development and evolution" (Boehm, 2010).…”
Section: Related Workmentioning
confidence: 98%
“…(1) The levels of abstraction before and after transformation, and preservation of semantics during transformation (Visser, 2001). The semantics-preserving changes correspond to the well-known concept of software re-factoring (Fowler, 1999;Winter, 2004).…”
Section: Related Workmentioning
confidence: 99%
“…The key to study these approaches is first to look at the program transformation taxonomy [Win04] and model transformation taxonomy [MCG06]. This is left as a separate research topic.…”
Section: Reuse As a Technologymentioning
confidence: 99%
“…Visser [13] presents a taxonomy that considers two major groups of transformations: translation and rephrasing. Winter [38] identifies seven major bidirectional goals of program transformation: clarity, efficiency, computability, simplicity, functionality, translation, and computation. Cordy and Sarkar [18] demonstrate that meta-programs can be derived from higher-level specifications using second order source transformations.…”
Section: Related Workmentioning
confidence: 99%