Using Formal Transformations to Construct a Component Repository
Production of software is costly and error prone and the most important means of production (good programmers) are scarce. Therefore, there exists a need to circumvent this costly manual production process. Analogies from classical engineering suggest that by building up a catalogue of standard components and construction techniques whose characteristics are well documented, can greatly reduce the cost of new construction projects. The bridge builder knows under what conditions a “suspension bridge” is the right approach and has a collection of standard girders, cables, nuts, bolts etc. which she can use in the design. This has lead to the notion of a component repository which will reduce the effort involved in constructing new software.
Unable to display preview. Download preview PDF.
- Back RJR. Correctness Preserving Program Refinements. Mathematisch Centrum, Mathematical Centre Tracts 131, 1980Google Scholar
- Morgan CC. The Specification Statement. ACM TOPLAS 1988 10;:403–419Google Scholar
- Stallman RM. Using and Porting GNU CC. Free Software Foundation, Inc., 1989Google Scholar
- Ward M. Transforming a Program into a Specification. Durham University, Technical Report 88 /1, 1988Google Scholar
- Ward M. Proving Program Refinements and Transformations. PhD Thesis, University of Oxford, 1989Google Scholar
- Ward M. A Model for Partial Programs. Submitted to Journal of the ACM, 1989;Google Scholar
- Ward M, Calliss FW, Munro M. The Maintainer’s Assistant. Conference on Software Maintenance 1989, Miami Florida, 1989Google Scholar
- Ward M. Derivations of Sorting Algorithms. Forthcoming, 1990Google Scholar