| 
|
QuoteRef: meyeB1_1985
topics >
all references >
ThesaHelp:
references m-o
Group:
requirement specification
Topic:
importance of information hiding for requirement specification
Topic:
good requirement specifications
Topic:
separate a module's interface specification from its implementation
Topic:
specification errors
Topic:
specification is infeasible
Reference
Meyer, B., "On formalism in specifications", IEEE Software, pp. 6-26, January 1985. Google
6 ;;Quote: software specification is overlooked or confused with definition of objectives or design
7 ;;Quote: a specification should only contain relevant information; no noise, remorse or redundancy
7 ;;Quote: a specification should discuss every feature of the problem
7 ;;Quote: a specification should only concern features of the problem and not features of possible solutions
7 ;;Quote: a specification should not contain contradictions
7 ;;Quote: a specification should not be ambiguous
7 ;;Quote: a specification should not contain forward references to undefined features
7 ;;Quote: a specification should only contain realistic features that can be validated
10 ;;Quote: remorse in a specification is adding to the description of a feature outside of its definition
11 ;;Quote: identification of specification errors in a published specification
22 ;;Quote: software specification requires a more rigorous formalism than natural language
ThesaHelp: references m-o (268 items)
Group: requirement specification (11 topics, 306 quotes)
Topic: importance of information hiding for requirement specification (23 items)
Topic: good requirement specifications (36 items)
Topic: separate a module's interface specification from its implementation (86 items)
Topic: specification errors (10 items)
Topic: specification is infeasible (46 items)