Although most of the history of the DSM solution development will be under
version control, there may well be extra information that is only stored in the email
folders or on the hard disks of the DSM solution team. A quick trawl through the
relevant locations should turn up some useful gems to record for posterity.
In many ways, closing down aDSMproject is more like putting it in mothballs than
killing it off. With a traditional hand-coded project, changes in libraries, platforms,
and even programming languages will quickly render the old code useless.WithDSM
models, the modeling language and models would remain valid even in the face of
DSM AS A CONTINUOUS PROCESS IN THE REAL WORLD 355
such major changes: new generator and domain framework are all that would be
needed. The same forces that resulted in the domain being retired could just as easily
result in its resurrection. While a full-scale revival may be unlikely, the ability to
quickly churn out a couple more products in the old range next year may be a useful
option from a business point of view. In particular if a newmanager??™s demand to revert
to a ???standard??? programming and generic modeling approach is inexplicably taking
longer than expected to produce results!
13.8 SUMMARY
This chapter has seen your DSM solution evolve from an initial idea to a full solution
in production, re?¬‚ected throughout in experience of its use.
Pages:
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676