At the
same time, we can also cover the initial distribution and introduction process. These
need to be planned and tested well: while it will be a pain to have to install and
uninstall the various components on a few machines, this pain will be nothing
compared to the alternative. Imagine what would happen if you tried to push DSMout
to all developers with a half-baked distribution system with poor instructions.
We have divided the DSM solution into several components in this book: the
modeling language, generators, framework, and tool support. These components may
not, however, match the actual ?¬?les or other elements you need to install for users. For
instance, in some DSM environments the language and generators may normally be
delivered as a single ?¬?le, whereas in others they may be delivered in separate ?¬?les??”or
even a ?¬?le for each diagram type and each generator.
In less mature environments, there may not be a separation between the generic
modeling tool support, which is the same for all organizations using the tool, and the
domain-speci?¬?c language and generators of each company. Instead, the language and
tool support, and possibly the generators, will be lumped together in one large
executable or bytecode package. This is not such a problem for the initial introduction,
but it makes evolution a harder process.
Pages:
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663