Abstraction and Specification in Program Development

Liskov, B., & Guttag, J. (1986). Abstraction and Specification in Program Development. MIT Press.

Type

Book

Intellectual base

Review or monograph

Year

1986

Link

https://mitpress.mit.edu/9780262121125/abstraction-and-specification-in-program-development/

Cited from

computer_science, engineering_design

Cited by

2 citations across 2 artifacts.

Each citation links to the sentence it supports in the citing article.

Primes

• Information Hiding
  • The stable public contract is the behavioural promise: put(k,v) then get(k) returns v, in expected constant time — a guarantee that holds regardless of whether the internals later switch from open addressing to chaining, or from one hash function to another.

    This sourceAbstract data types and behavioral specification — a stable contract (e.g., put-then-get returns the value in expected constant time) that holds regardless of the concealed representation.

• Interface
  • A function signature (interface) abstracts the implementation, but the interface itself is what the caller sees and depends upon.

    This sourceDistinguishes abstraction (the cognitive principle of hiding detail) from interface specification (the structural mechanism that realizes abstraction at module boundaries).

Verification

This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.

Registry ID ref:72d4fe2f639d · see in the full table