Strategies for Translating UML/OCL Design Models to JAVA/JML Designs

Abstract

The Object Constraint Language OCL is a textual notation that can be used for making UML models more precise by expressing formal constraints on the modelling elements that occur in UML diagrams. OCL can be used to specify invariants on classes and preconditions and postconditions of operations and methods. The Java Modeling Language JML is a behavioural interface specification language for specifying Java classes and interfaces. Like OCL, JML can be used to specify invariants and preconditions and postconditions. However JML explicitly targets Java, whereas OCL is not specific to any one programming language. This paper deals with the translation of some aspects of UML design models with OCL constraints to Java classes and interfaces annotated with JML assertions. Rather than giving a particular translation, the paper proposes different translation strategies that would be possible. A set of defaults for all the decisions would be adopted which would allow translation to be automated, for example by a tool that could take the UML/OCL model and translate it directly into an initial JML/Java design that could later be modified as desired.