Keep in mind, however, that the person specifying the
language into a metamodel and implementing the language into a tool does not
necessarily need to be experienced in the domain.
The candidate concepts for the modeling language can be found in very different
sources. We can identify some of them from the jargon and vocabulary in use.
Frequently used concepts exist with good reason: people ?¬?nd them relevant and
concise when discussing a product and its features. The vocabulary often provides the
best starting point, as it mostly uses natural concepts: people do not think of solutions
immediately in coding terms. Starting from the existing vocabulary also means that
there is no need to introduce a new, unfamiliar set of terms or map existing concepts
and their semantics to those provided by some external languages. What does the
Uni?¬?ed Modeling Language (UML) (or SysML, IDEF, BPMN, etc.) know, for
instance, about banking applications, pacemakers, or applications you are
developing? It is far better to use the concepts of your domain in a language than
map them to external concepts and related semantics.
230 DSM LANGUAGE DEFINITION
Other typical sources for ?¬?nding candidate concepts from the domain include the
following:
. Architecture: A description of the architecture is often a good source since the
architecture usually operates on domain concepts.
Pages:
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417