Transformation of Applicative Specifications into Imperative ...

12.2.3 Optimization of the Transformer
12.2. FURTHER WORK
As described in Chapter 9 the transformation process can in some cases be
very slow. It would be nice if the transformer could be optimized such that
the transformation process for some specifications was a bit faster.
12.2.4 Interactive Transformer
Another extension could be to make the transformer interactive such that
the user can choose which of the occurrences of values and type names of
the types of interest that have to be transformed as such. This would ease
the requirements on the specification style, but it would complicate the use
of the transformer.
12.2.5 Full Verification of the Transformation Rules
In Chapter 7 a proof of the correctness of the transformation rules is outlined.
If this proof was completed, the step from applicative into imperative
specification would be verified automatically if it was done applying the
transformation rules, e.g. by using the transformer. This would mean that
no further work would have to be done in order to verify the development
step, which would ease the development step even further.
12.2.6 Other Extensions
When a specification cannot be transformed it is not specified what and
where the problem is unless the problem is caught by the lexer and parser.
An extension to the transformer could be to improve the error handling.
This would ease the use of the transformer.
127