The executable model will fail compiling when doing comparisons between primitives of some types, mainly between float and integer types.

While the dynamic model will work for all comparison types.

given a method like public float getFloatValue(){...} on a class, the dynamic model will work with a rule that does something like:

ClassWithValue( floatValue != 5 )

But the executable model will require the value check to be specified as a float like so or it will cause a compilation error:

ClassWithValue( floatValue != 5f )