There will
probably still be minor bugs in the domain framework, generated code, and
generators, since these are the most code-like parts of the solution. If the tool support
includes handwritten code, or is produced by a DSM framework that is still under
development, it may well contain outright bugs??”in addition to the certainty in all
tools that individual users may wish some things had been done differently. Finally,
the modeling language itself will have areas for improvement and extension, both
at the start and later as the domain evolves. Developers need to be able to report all of
these, and ideally be informed when the problem is corrected.
At this early stage before the initial deployment of theDSMsolution, it is of course
impossible to create the perfect process for evolution. What is important now is that
there is a tested and documented process that works technically: all developers can
easily upgrade to a newversion of theDSMsolution, and all models update sensibly to
work with the new version. This process itself will evolve over time as you gather
more experience of what works well with your tools, language, and organization.
13.6.4 Learning Material and Training
The developers who will use the DSM solution are faced with a signi?¬?cant learning
curve. The task is made easier since the domain will be familiar, and the modeling
language concepts will normally map directly to the domain.
Pages:
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665