|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
ABSTRACT
Computer programs are operational schemes. Many programmers design, describe, and justify their programs while solely thinking "operationally". Yet, an operational perspective is insufficient. For many years, the important role of an assertional perspective is advocated. However, this perspective is debated [5]. Many are deterred from employing it, possibly because it is displayed with formal notations and mathematical logic. The objective of this paper is to offer the elaboration of this perspective through a natural, informal embedment of assertions in the design process. The essential, revealing, and instructive role of informal, yet concise and accurate assertions is motivated and elaborated; first through three stimulating illustrations, and then with a general instructional approach. 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.
INDEX TERMS
Primary Classification:
General Terms:
REVIEW
"Anany Levitin : Reviewer"
This paper advocates the systematic use of an "assertion perspective" in algorithm/program design. This means the embedding of informal, but mathematically rigorous assertions that pinpoint important properties of the problem at hand, and lead to
more...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||