Symbolic evaluation of programs

Abstract

The past several years have witnessed a growing concern with the high cost of software development and maintenance. The usual reaction to this has been administrative—to organize programming activities better (the Chief Programmer Team); to improve the structure of programming languages, and thus, hopefully, the programs written in them; or to propose that formal “specifications” be developed for a program before the coding of it in some programming language commences.