Since the metamodel knows that these concepts are the same, it is possible to
check them, and when the name needs to be changed in one place, its change can be
propagated elsewhere. The metamodel knows how the languages are integrated.
To achieve the bene?¬?ts of DSM, you should in general always seek the possibility
of having language support. This gives ?¬?rst-hand support allowing errors to be found
and even preventing them early, guiding during development work, supporting reuse,
and so on. Modelers then don??™t need to learn all the details, and it becomes easier to
de?¬?ne a code generator as you can be more sure that the input for code generators,
models, is correct. If you leave domain extensions to modelers, everyone needs to
knowthem??”yet they still do them differently! There are also multiple ways to specify
these extensions, such as naming conventions, annotating and commenting models, or
using additional languages such as constraint languages or action languages. These
choices depend partly on the tool chosen for language speci?¬?cation and language use
(see Chapter 14 for tools).
Mapping Domain Concepts to Different Modeling Concepts Domain
concepts can be mapped into different kinds of concepts in modeling languages. The
usual starting point is that each domain concept maps one-to-one to a modeling
concept.
Pages:
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437