For example, we may have a stop state that ends the application and another kind of
stop that just ends the current function but not the whole application. These
alternatives should also be made visible in the model by giving them different
notation.
Usually, notation de?¬?nition starts from the main modeling concepts but it is also
reasonable to start with those symbols that come most naturally, giving a style that
forms a basis for notation for other concepts too. When inspecting the other language
concepts, you may ?¬?nd that they can use similar representations. Using a traf?¬?c sign
for one concept may lead to considering other traf?¬?c signs for other concepts. Since
notation can be richer than just showing basic design information, it is often best to
de?¬?ne ?¬?rst the main notation and later add extensions that indicate special
information, such as having a consistent symbol element to indicate that a model
element is not completely de?¬?ned, has errors, is described in more detail in a
submodel, is reused from a library, and so on. Remember that notation can help the
258 DSM LANGUAGE DEFINITION
reader and it can change based on the properties it has or even based on the
connections it has.
Each concept of the modeling technique should normally have one identifying
representation. You should ?¬?nd representations that differentiate the concepts.
Pages:
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473