DMS®: Program Transformations for Practical Scalable Software Evolution

By I. Baxter, Christopher W. Pidgeon, M. Mehlich. International Workshop on Principles of Software Evolution, 2002

330 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Comparison and evaluation of code clone detection techniques and tools: A qualitative approach (2009, methodology): “b The tool seems to have external dependencies or to be a part of a larger tool set T [86] (PROCSSI), T [92] (recoder), L [29] (PMD), L [84] (CloSpan), L [37] (ConQAT), S [15] (DMS [13]), S [14] (Bauhaus), [20] (CPython, ANTLR), S [111] (Microsoft Phoenix Framework), LS [74] (CodeDOM of .”
When and how to develop domain-specific languages (2005, methodology): “…System Developer ASF+SDF [van den Brand et al. 2001] CWI/University of Amsterdam AsmL [Gl¨Microsoft Research, Redmond asser et al. 2002] DMS [Baxter et al. 2004] Semantic Designs, Inc. Draco [Neighbors 1984] University of California, Irvine Eli [Gray et al. 1992] University of Colorado,…”
Stratego/XT 0.17. A language and toolset for program transformation (2008, methodology): “The Design Maintenance System, DMS [5,4], is a commercially available collection of tools for writing custom program transformation systems.”
RASCAL: A Domain Specific Language for Source Code Analysis and Manipulation (2009, background): “We give an overview of the language and assess its merits by implementing a complex refactoring.”