| 
|
QuoteRef: guttJV9_1985
topics >
all references >
ThesaHelp:
references g-h
Group:
requirement specification
Topic:
theorem proving systems
Topic:
design documentation
Topic:
abstract data type
Topic:
requirement specification by function
Topic:
programming with a database of modules
Topic:
programming environment
Topic:
interface type
Topic:
separate a module's interface specification from its implementation
Topic:
names as rigid designators
Topic:
importance of information hiding for requirement specification
Reference
Guttag, J.V., Horning, J.J., Wing, J.M., "The Larch family of specification languages", IEEE Software, September 1985, pp. 24-36. Google
24 ;;Quote: Larch shared and interface languages for incremental construction of readable specifications from other specifications; includes theorem prover for semantic checking
25 ;;Quote: the Larch Shared Language specifies traits; i.e., operators, their properties, and their constraints; may be an abstract data type
28 ;;Quote: reuse traits in Larch to standardize notation, save time, and avoid errors
30 ;;Quote: need tools for formal specifications; maintain consistency, browse, derive interactions and consequences, teach methodology
31 ;;Quote: a Larch interface specification has the type name, public routines, a trait, mapping of types to the trait, and routine specifications
31+;;Quote: a Larch routine interface specification has its name, its parameter names and types, a trait for describing its operators, pre-conditions, and post-conditions
32 ;;Quote: names in a Larch interface specification tie together traits in the Shared language and programs in the programming language
ThesaHelp: references g-h (299 items)
Group: requirement specification (11 topics, 306 quotes)
Topic: theorem proving systems (20 items)
Topic: design documentation (43 items)
Topic: abstract data type (64 items)
Topic: requirement specification by function (20 items)
Topic: programming with a database of modules (94 items)
Topic: programming environment (46 items)
Topic: interface type (50 items)
Topic: separate a module's interface specification from its implementation (86 items)
Topic: names as rigid designators (43 items)
Topic: importance of information hiding for requirement specification (23 items)