Finally, now is a good time to complete any refactoring on the generator
de?¬?nitions. This will obviously help you later in maintaining the generators, but will
also make it easier to evolve the modeling language.
It will hopefully go without saying that you should also have whatever
documentation is appropriate for the internals of the DSM solution itself. The project
may be your baby now, but what about when you get that big promotion on the basis of
your results here? Spare a thought for the poor soul who is given the task of taking over
the DSM solution??”and for yourself, if the project crashes and burns behind you.
Do you really think you can spin it so it looks like you were 100% a hero and the new
guy 100% a villain?
13.6.3 Introduction and Evolution Process
One of the more frustrating things for developers is the sheer amount of work that still
remains to do once the product is ???ready.??? Polishing the product is one part, but even
after this there is still the installer, download or other distribution system, user
documentation, and training material. Introducing the DSM solution to your
organization follows this pattern, with a few minor differences.
Because of the importance of evolution in DSM, we want to plan the distribution
mechanism for the DSM solution before we ?¬?nalize the user documentation.
Pages:
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662