| Ira D. Baxter. Design (Not Code!) Maintenance. In Proceedings of VIII Brazilian Symposium on Software Engineering (SBES), Curitiba, Brazil, October 25-28, 1994. |
....substantial effort is still necessary to interconnect a group of components into a working system. 6. 4 Transformation systems Transformation systems are tools for converting abstract program specifications into concrete program implementations by applying semantics preserving substitutions [Bax94]. A variety of such systems exist; each has a different suite of available transforms, and a different representation for the input specification and the output implementation. Draco [Nei89] is a noteworthy transformation system which employs a network of related languages to represent the ....
Ira Baxter. Design (not code!) maintenance. In Proceedings of Brazilian Software Engineering Conference VIII, October 1994.
....for small algebraic specifications, in which functionality deltas have been propagated through both optimization transformations, and abstraction refinement transformations. A functional language example may be found in [Bax92a] A more practical example in a procedural language is provided in [Bax95]. Scaling to practice While we have theory, we have little experience with scaling up. As an example, the present theory represents derivation histories in a simple, theoretically correct but rather inefficient way: a linear chain. The revision of an N step linear derivation history can be an ....
Design (Not Code!) Maintenance, Ira D. Baxter, Proceedings of the ICSE-17 Workshop on Program Transformation for Software Evolution, Seattle, Washington, April 20-22, 1995.
No context found.
Ira D. Baxter. Design (Not Code!) Maintenance. In Proceedings of VIII Brazilian Symposium on Software Engineering (SBES), Curitiba, Brazil, October 25-28, 1994.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC