The
reasons for not following the manually written code were twofold: the manually
written code was unnecessarily long and inconsistent. The latter was especially
relevant since similar kinds of features were sometimes written differently even inside
the same insurance product. This was partly expected since the company had only
speci?¬?ed a few insurance products, and both Java as a programming language and the
way to implement them were new. The code was also unnecessarily complex since
many classes where implemented in the code by ?¬?rst declaring them and then later
de?¬?ning them. For these reasons, the reference applications were uni?¬?ed to followone
set of best practices instead of using different styles and personal preferences. Let??™s
look next at the structure of the code generator and then samples of the generated
Java code.
6.5.1 Generator Structure
Figure 6.8 illustrates the structure of the ?¬?nal generator by describing the generator
modules and call structures between them. The numbers on the lines connecting the
generator modules indicate the execution order of the generator modules: the ?¬?rst, 1,
produces the main class based on the package, and the last, 12, the associations
between model elements.
Implementation of the generator, however, did not follow the execution order.
Pages:
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263