 |  |  | 4 Structured Specifications |
4 Structured Specifications
Larger specifications should be structured into smaller parts
in order to increase readability and also re-use.
CASL has a number of language constructs allowing to write
specifications in a structured way; we here demonstrate
and explain their use. Parameterized and free specifications
(and how to avoid some pitfalls when using them) are explained
in separate subsections.
CoFI
Note: M-6 -- Version: 0.7 -- June 2002.
Comments to cofi@informatik.uni-bremen.de
 |  |  | 4 Structured Specifications |