Object-Oriented Software Construction

Meyer, B. (1997). Object-Oriented Software Construction. Prentice Hall.

Type

Book

Intellectual base

Textbook

Year

1997

Link

https://bertrandmeyer.com/wp-content/upLoads/OOSC2.pdf

Cited by

6 citations across 5 artifacts.

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

Domain-specific

• Command–query separation
  • Command–query separation is a design principle requiring each method either to change state as a command or return information as a query that causes no observable state change, but not both.
• Postcondition
  • A postcondition relates the operation’s inputs, pre-state, outputs, and post-state and forms the consequent of a Hoare-style contract.
  • … from A canonical instance directly demonstrates that for every execution admitted by the precondition and semantics that terminates normally, the resulting state satisfies the stated predicate. to An applied instance preserves the same invariant under a changed scale, notation, jurisdiction, or implementation..

Mechanisms

• Command–Query Separation
  • Its strength is local reasoning: once queries are truly pure, a caller can invoke, compose, cache, and retry them without fear of hidden mutation, and the entire write surface collapses to the command side where it can be governed.

    This sourceSeparates state-changing commands from side-effect-free queries to improve reasoning and control intermodule state changes.

• Interface Contract Design
  • A real anchor grounds the discipline: design by contract, where preconditions, postconditions, and invariants form an explicit agreement between caller and provider.

    This sourceDefines Design by Contract through caller preconditions, provider postconditions, and invariants.

• Invariant Propagation Test
  • It formalizes the same instinct as design by contract

    This sourceDefines design by contract through preconditions, postconditions, and invariants that must hold at specified program points.

Verification

Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.

Does it back the claim? Not recorded. Neither this nor any other of the 6 citations of this work carries a recorded support check.

Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.

See how references were verified.

Links previously used in the corpus

Before the registry existed this work was also linked 2 other ways.

• https://bertrandmeyer.com/oosc2/ ×2
• https://bertrandmeyer.com/OOSC2/ ×1

Registry ID ref:de8dcc2caacc · see in the full table