In addition to the MOF elements described above, Association, Generalization,
and Dependency relationships were implemented from MOF types. Similarly, an
AssociationEnd role type was implemented and used as a supertype for the domainspeci
?¬?c role types different objects can take when connected to other modeling
objects.We describe their use in more detail later when presenting the metamodel for
the modeling language.
122 INSURANCE PRODUCTS
The requirement to apply MOF, however, was later noticed to lead to an
unnecessarily complex modeling language. For example, associations and their role
names were provided in the language, since they came withMOF, but were not used at
all. The requirement to follow the standard for metamodeling also caused additional
delay in the DSM creation: In the middle of the DSM implementation, the company
realized that the version of MOF had changed, and they needed to recheck the
de?¬?nitions made in the domain model. Following the newerMOFreleases was seen as
relevant since the target environment used for storing the information about the
?¬?nancial products was expected to change along with new MOF versions. However,
for language creation, it was not relevant since the domain-speci?¬?c language could
have been implemented without any relation to MOF. However, to satisfy the
company policy for following standards, some terms were changed to the existing
implementation of MOF (Fig.
Pages:
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249