320 ;;Quote: built an exact duplicate of the A-7E flight software; hard real-time program to process and display flight data; tight memory and time constraints

321 ;;Quote: information hiding minimizes the cost of software by estimating the likelihood of change; likely changes should be easily made

321 ;;Quote: restrict data structures to a module; all other modules must call access programs

322 ;;Quote: each module's structure should be simple enough to be understood fully

322 ;;Quote: change a module's implementation without knowledge of the implementation of other modules and without affecting the behavior of other modules

322 ;;Quote: except for interface changes, allow independent changes to individual modules; mix and match combinations of old and new versions

322 ;;Quote: module decomposition produces many small modules; software module guide for completeness, convincing arguments, software maintenance

323 ;;Quote: module decomposition into submodules without overlapping or missing responsibilities

323 ;;Quote: a software engineer should understand a module's responsibilities without understanding its internal design; should easily identify relevant modules without looking at their components

324 ;;Quote: for information hiding, describe module structure by the roles played, the secrets held, or the facilities provided

324+;;Quote: a module specification tells you how to use the module and what it must do

324 ;;Quote: module guide for the A-7 OFP flight software

324+;;Quote: the A-7E flight software consists of a hardware-hiding module (hardware interfaces), a behavior-hiding module, and a software decision module (performance-related decisions)

335 ;;Quote: secrets are more important than interfaces or roles; secrets clarify the responsibilities of a module