The creators of a DSM solution may feel a bit disappointed seeing that
developers now work much faster and produce better quality products but only give
feedback on notation and symbols. This can be because the other parts of the DSM
solution are not as visible to modelers, and notational issues are always easy targets for
opinions.
A good practice when de?¬?ning the language is to ask users to come up with the
symbols and other representational elements. This increases user involvement,
helps in solving any ???not-invented-here??? attitude, and makes the language easier to
learn and use. By language user, we don??™t mean only those creating the models. The
more models are used for purposes other than designing for code generation, the
more likely we need others??™ involvement. Those who read models, for example, to
validate the speci?¬?cations could participate too. Also, if some models are used to
make product presentations by sales people or create con?¬?guration tools for
deployment, it is good to ask opinions from this larger audience. It is much easier to
introduce them to something they helped de?¬?ne: it has become their language, not
yours.
10.6.1 Selecting Notation and Representational Forms
For de?¬?ning a notation several guidelines can be given. For choosing notation,
Costagliola et al.
Pages:
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470