On the inevitable intertwining of specification and implementation

  • Authors:

  • William Swartout;Robert Balzer

  • Affiliations:

  • Univ. of Southern California, Marina del Rey, CA;Univ. of Southern California, Marina del Rey, CA

  • Venue:
  • Communications of the ACM
  • Year:
  • 1982

Quantified Score

Hi-index 48.25

Visualization

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.