This paper is concerned with the practical usability of the Object Constraint Language (OCL). Pitfalls for untrained software developers are uncovered, and strategies for avoiding them are discussed. These strategies are not restricted to OCL-specific problems but give insights into how to handle formal specification, modeling, implementation, and verification issues within a single framework. The implementation of the identified strategies and their integration into a widely used commercial CASE tool is currently under way within the KeY project
To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.