This
principle minimizes the overload of notational constructs and guarantees that all
domain concepts can be distinguished in the models. Accordingly, the completeness
of representations (Batani et al., 1992; Venable, 1993) or representational ?¬?delity
(Weber and Zhang, 1996), that is, availability of exactly one notational construct for
each concept, is a well-known criterion for dealing with interpretations between
modeling concepts and notations. If you have a lot of similar kinds of concepts that are
still different in the modeling language (e.g., have different rules, connections,
properties) you may use the same shapes, colors, fonts, and so on to identify their kind.
This approach was used, for example, in CPL (Chapter 5). You may also de?¬?ne
notational elements so that they visually show the same aspect, subdomain, reuse,
origin, or architectural role. For example, in the watch case (Chapter 9) colors are used
to show the MVC (Model-View-Controller) architecture.
Selecting a Representational Form The concrete syntax, how we represent
the models, is not limited to symbols.We can choose among different representational
styles too. The example models in this book illustrate representations of different
graphical modeling languages where the symbols and icons represent different
modeling concepts.
Pages:
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474