These latter two are described
in the metamodel represented in Fig. 6.5.
LANGUAGE FOR MODELING INSURANCES 129
Model Checking Not all domain rules could be included in the metamodel since
their checking would not make sense at modeling time. For example, each insurance
product needs to include at least one elementary product cover, but this kind of rule
can??™t be checked at modeling time, since immediately after adding a product object to
the model the design would be invalid. Various generators were implemented for
checking such rules. These included, for example, that every Product cover needs to
refer to a Risk object and that each Product bundle must refer to at least one Product.
Although these model checking topics were detected while creating the metamodel,
they were implemented last when it was possible to test them by using the language to
specify some insurance products. The available models then acted as test material for
the model checking generators. In addition to model checking, additional generators
weremade for producing documentation and generating an overviewinHTMLformat.
6.3.3 Modeling Notation
Since the modelers were not software developers, language visualization (e.g., the
visual appearance of the notation), ease of use, and user friendliness were emphasized.
To gain better acceptance for the introduced language, the notational symbols were
asked to be de?¬?ned by the users of the language, the insurance experts.
Pages:
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258