from object-z specification to groovy implementation

So far, valuable researches have been conducted on mapping objectoriented specification notations, such as object-z, to different objectoriented programming languages, such as c++. however, the results of selecting jvmbased programming languages for mapping have not covered most of basic object-z structures. in this paper, the groovy language, as a dynamic jvmbased language, is selected to overcome some of the existing limitations. as the main contribution, the rules required for mapping object-z specifications to executable groovy code are introduced. the proposed rules cover notions such as multiple inheritance, inverse specification of functions, functions defined on generic definitions, and free type constructors. these notions have not been covered in previous methods for formal program development from objectoriented specifications, regardless of the selected formal specification language and target programming language. in addition, in this paper, the parallel composition construct is mapped to a parallel, executable code to improve the faithfulness of the final code to the initial specification. we also introduce a mapping rule for the class union construct, which has not yet been provided for any jvmbased language. unlike previous works, instead of presenting the mapping rules in terms of natural languages, we present them in terms of some formal mapping rules.