This property was added to the common supertype
Domain class (see Fig. 6.3). Its data type was made an object so that it referred directly
to a Package model element instead of having just a mapping with a string value of the
package name. This package reference was needed only for cases where a product
speci?¬?cation represented in a single diagram had elements from multiple packages.
Otherwise, all elements in a diagram belonged to the same package: the model
hierarchy speci?¬?ed the package and product they belonged to.
FIGURE 6.3 Insurance-speci?¬?c objects inheriting from MOFClass
126 INSURANCE PRODUCTS
6.3.2 Modeling Rules
In addition to object types and property types, various relationships and their related
constraints were identi?¬?ed and de?¬?ned. Depending on their nature, the constraints
were either implemented directly into the metamodel or checked using generators.
Most of the relationships deal with insurance-speci?¬?c rules, such as that insured
objects can be related to risks and that surpluses can be connected to tariff
components. Figure 6.4 illustrates some of these relationships, such as that a Product
bundle can consist of Products, which can further consist of either Elementary product
cover or Tariff elements. This allows us to describe insurance products from a tariffcentric
or a product cover point of view.
Pages:
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254