Nowis the time to make sure that the
necessary rules are in place.You are not trying to stop the developer from doing things,
more to prevent her from making models that the code generator does not support.
There will still be a large number of models that can be made which make little sense.
Trying to prevent all of these is impossible and also undesirable. Some of them will
turn out to be perfectly good ideas: creative ways of using the language that had not
occurred to you yet.
You should also make sure that your rules do not make the language hard to use.
There may be certain states of a model that are illegal, but would occur frequently on
the shortest path for editing a model from one legal state to another. It is better to
implement such rules as checking reports, which can be run by the user on demand or
automatically when generating code.
If your organization has a strong requirement or tradition of documentation
in Word ?¬?les or similar, you will probably need a way to generate the models, their
elements, and properties as a document. Good tools will offer you this already,
DSM DEPLOYMENT 349
but even then you may want to edit the styles and layout to match existing standards.
If the DSM environment provider has not done this work for you, and you need
Word ?¬?les rather than plain text or HTML, be aware that this can be a signi?¬?cant
amount of work.
Pages:
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661