goals for a programming system
program proving is infeasible
, in Bates, D. (ed.),
Structured Programming: International State of the Art Report Great Britain, Infotech International, 1976.
|20 ;;Quote: a large programming group may produce instructions at 3 per man day with many errors; why so low?
|QuoteRef: bateD_1976 ;;20 Ramamoorthy '74: "Delay in delivery is commonplace while gross underestimation of the cost by a factor of four is not unusual.
|QuoteRef: bateD_1976 ;;23 Hunke: minimum human effort to use, min. machine effort to perform, min effort to change, min. perturbation (robustness-even to overwrites)
|QuoteRef: bateD_1976 ;;23 Hunke: "This prevents a disturbance in a system of programs from spreading|
|31 ;;Quote: neither structured programming nor proofs of correctness attempt to check the specification itself
|QuoteRef: bateD_1976 ;;74 Miller: on naive subjects found programs with goto's quicker in training time then programs with if-then-else
Group: goals for a programming system (21 topics, 971 quotes)
Topic: goto statement (25 items)
Group: exception handling (12 topics, 305 quotes)
Topic: software management (27 items)
ThesaHelp: references a-b (396 items)
Topic: programmer productivity (57 items)
Topic: program proving is infeasible (46 items)
Topic: specification errors (10 items)