Not only have they
had more experience with DSMand your solution than others, but also they have been
more exposed to the internals of the solution and the process involved in creating it.
The size of the DSM solution team will largely be dependent on the DSM
environment or framework you use. A high-level DSM environment will keep the
amount of work low enough that the evolution of the DSM solution will require less
than one person??™s full-time work, even for a large language. Lower-level frameworks
will require a few full-time staff, possibly even several people. In addition to these,
you may need one or more people working on the domain framework: whether these
are considered part of the DSM solution team or your general in-house components
team is perhaps a matter of taste.
If your organization has more than one domain for which DSM seems applicable,
there is also the question of the next DSM project. Certainly the ?¬?rst DSM solution
team will have plenty of experience that can be used bene?¬?cially on the next project.
How best to use it is however dependent on the particular situation: how much the
domains are related, what the people in the ?¬?rst DSM team want, how mature the ?¬?rst
DSM solution is, and what kinds of people are available in the new domain.
In some ways, an external DSM consultant may still be the best solution for the
second project.
Pages:
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672