| 
|
QuoteRef: bartW12_1977
topics >
all references >
Topic:
requirement specification by behaviors
Topic:
specification is infeasible
Reference
Bartussek, W., Parnas, D.L., "Using assertions about traces to write abstract specifications for software modules", University of North Carolina at Chapel Hill, TR 77-012, December 1977, pp. 111-130. Google
Other Reference
9-28 in Hoffman, D.M., Weiss, D.M. (eds.), Software Fundamentals. Collected Papers of David L. Parnas, Boston: Addison-Wesley, 2001
11 ;;Quote: a specification is complete and consistent if every legal trace of a module's function calls yields only one value
19 ;;Quote: abstract specification is difficult; e.g., specifying a simple table/list module led to non-intuitive problems
Topic: requirement specification by behaviors (16 items)
Topic: specification is infeasible (46 items)