In particular, looking at older versions of
models in this situation is problematic: you will need to install the complete,
correct old version of the tool. If the tool does not allow multiple versions to be
installed simultaneously, this is something of a disaster. The situation becomes even
worse if the tool is tightly coupled with your IDE or operating system version:
350 DSM DEFINITION PROCESS
reinstalling the required compatible version of those is unlikely to be anyone??™s
favorite pastime.
Whatever the situation for your particular case, you must identify the components
you need to distribute to developers initially and when upgrading. For upgrades,
consider which parts of theDSMsolution may change, and whether you want to allow
an upgrade just for that part or for a set of parts together. Use your experience from
upgrades during the pilot project to come up with a scheme that makes sense for your
situation. Remember that at the start the rate of evolution will still be fairly high,
although not at the extremes seen in the pilot project: the DSM solution is now more
mature, and the larger number of developers adds some inertia.
As you build a mechanism and process for distributing updates to developers, do
not forget the importance of a communication channel in the other direction.
Developers need a way to submit feedback about the DSM solution.
Pages:
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664