Initial Algebra Semantics and Continuous Algebras
Journal of the ACM (JACM)
Abstract data types and the development of data structures
Communications of the ACM
Monitors: an operating system structuring concept
Communications of the ACM
A technique for software module specification with examples
Communications of the ACM
Communications of the ACM
On the criteria to be used in decomposing systems into modules
Communications of the ACM
HYDRA: the kernel of a multiprocessor operating system
Communications of the ACM
Operating system principles
PASCAL user manual and report
Towards the construction of verifiable software systems
Proceedings of the 1976 conference on Data : Abstraction, definition and structure
Restricted data types, specification and enforcement of invariant properties of variables
Proceedings of an ACM conference on Language design for reliable software
Report on the programming language Euclid
ACM SIGPLAN Notices
Integrity of electronic patient records
EGOV'11 Proceedings of the 10th IFIP WG 8.5 international conference on Electronic government
| Hi-index | 0.00 |
In the definition of an abstract data type, much attention is given to specifying how instances of the type are to behave when they are used as intended. Such specifications are used to guide the choice of a representation for the type, and to verify that an implementation is correct. An equally important task, but one that has been relatively overlooked until now, is to specify clearly what are the circumstances of intended use of the type. These specifications must also be made use of if one is to certify that an implementation will produce the behavior that is anticipated. This paper addresses the specification of the environment and the mode of use to be made of instances of an abstract type, and shows how these can be incorporated into the type definition itself.