In other words, we have
created another general-purpose modeling language. The ?¬?rst rule of language
de?¬?nition is, therefore, to start with the better understood parts of the domain and
extend the modeling language gradually to cover the full domain??”possibly
integrating with other languages. It is worth remembering thatDSMlanguages should
never be considered to permanently restrict our view of the world because they can be
changed when needed. If the domain changes or our understanding of the domain
changes, we should be able to change the language too.
The language creator needs to ?¬?nd concepts and abstractions that are relevant for a
given development situation. Generally, the main domain concepts map to the main
modeling concepts, while others will be captured as properties, connections,
submodels, or links to models in other languages. While de?¬?ning the languages, the
balance with the generator,domain framework, and available components also needs to
be decided. Next, we describe approaches to identify modeling concepts and map them
to some of the models of computation behind every modeling language. Although
individual modeling concepts are most often applied with one language only, models
are often integrated and reused. The language creator can also identify connections
between modeling concepts and inspect language use situations where existing model
elements could usefully be reused.
Pages:
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412