ACM Home Page
Please provide us with feedback. Feedback
On the inevitable intertwining of specification and implementation
Full text PdfPdf (370 KB)
Source
Communications of the ACM archive
Volume 25 ,  Issue 7  (July 1982) table of contents
Pages: 438 - 440  
Year of Publication: 1982
ISSN:0001-0782
Authors
William Swartout  Univ. of Southern California, Marina del Rey, CA
Robert Balzer  Univ. of Southern California, Marina del Rey, CA
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 8,   Downloads (12 Months): 69,   Citation Count: 52
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/358557.358572
What is a DOI?

ABSTRACT

Contrary to recent claims that specification should be completed before implementation begins, this paper presents two arguments that the two processes must be intertwined. First, limitations of available implementation technology may force a specification change. For example, deciding to implement a stack as an array (rather than as a linked list) may impose a fixed limit on the depth of the stack. Second, implementation choices may suggest augmentations to the original specification. For example, deciding to use an existing pattern-match routine to implement the search command in an editor may lead to incorporating some of the routine's features into the specification, such as the ability to include wild cards in the search key. This paper elaborates these points and illustrates how they arise in the specification of a controller for a package router.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Balzer, R. M. Dataless programming. Full Joint Computer Conference, 1967, pp. 535-545.
 
2
 
3
Balzer, R. M., and N. M. Goldman. Principles of good software specification and their implications for specification languages. Proceedings of the Specifications of Reliable Software Conference, Boston, Massachusetts, April, 1979, pp. 58-67. (Also presented at the National Computer Conference, 1981.)
 
4
Balzer, R. M. Transformational implementation: An example. IEEE Trans. Software Engineering 7, 1 (Jan. 1981), 3-14. Also published as USC/Information Sciences Institute RR-79-79, May 1981.
 
5
6
 
7
Dijkstra, E. W. Notes on structured programming. In Structured Programming, Academic Press, New York, 1972.
 
8
Hommel, G. (Ed.) Vergleich verschiedener Spezifikationsverfahren am Beispiel einer Paketverteilanlage. Kernforschungszentrum Karlsruhe GmbH, August, 1980. PDV- Report, KfK-PDV 186, Part 1.
9
10
11

CITED BY  52

Collaborative Colleagues:
William Swartout: colleagues
Robert Balzer: colleagues