On the other hand, the
developers will probably not be accustomed to using a graphical modeling language
to actually build products, as opposed to simply designing or documenting them. Part
of the function of the learning material and training will thus be to help ease this shift
in mindset.
Clearly, the most important element to teach developers about is the DSM
language. Good DSM environments will allow you to document the individual
language concepts inside the tool itself. This will serve as a good online reference to
the modeling language, as well as providing context-sensitive help about each of the
concepts. Additionally, it is often useful to have the language described in a more
familiar format, either on paper or in some electronic document format.
Since the developers will not be metamodelers, it is probably not so useful to
provide an actual metamodel of the modeling language. Instead, try to build an
DSM DEPLOYMENT 351
example model or models that illustrate all the concepts and the way they are
used. You can then describe the model and the way it works in the text. This tends to
be more useful than a list of the concepts and their descriptions. Such a list can
be added at the end as a reference, although keeping this documentation in the tool
itself puts it closer to the developers and also reduces the risk that it will become out
of date.
Pages:
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666