. If the notation aims to follow the real product closely, such as the GUI
functionality described in Chapter 8 for the mobile phone case, different colors,
fonts, and so on can be used to distinguish other model data from elements that
resemble the real product. For example, the Multiquery object type in Chapter 8
uses gray for variable names to indicate that they are not part of the visible UI.
. Make symbols of model elements that may contain other elements transparent
to allow showing parts inside the main symbol. The alternative is to create two
260 DSM LANGUAGE DEFINITION
symbols for the same aggregate concept: one showing information when the
concept is not used as an aggregate and another when other concepts are part of
the element (moved inside the aggregate symbol).
. Use consistent notational elements to improve model readability. For example,
a special icon or text element can indicate if a model element is described in
more detail or from another aspect in another model.
. You may consider using special notational elements, such as an icon or a text
element, to illustrate the status of the model or of its individual model elements.
This typically includes showing an error label for an incorrect model in cases
where it was not feasible to include the error checking rules in the metamodel.
Pages:
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478