A DSM language can grow, but it can also evolve in other ways. If a change
needs to be made, it can be: there may be some pain associated with it, but the gain to
the organization can be seen to be greater.With a generic language, such a change will
often be left undone through fear??”and well-grounded fear at that. If the language
changes, will the third-party tool vendors update their tools to support the new
language, and provide a way to update models to match the new language? The tool
vendors must face a similar fear: if we update the tool, will users choose to stay with
the old version?
While a DSMsolution will remain viable in its domain, even as that domain evolves,
there is also the question of the viability of the domain itself. Businesses change, and it
may be that at some point customers are no longer asking for products in that domain.
Companies must also use their limited resources to best effect, and sometimes this
may mean even a viable domain is shut down, and the developers are moved to a
different project that offers a better return on investment or promise of growth.
Unfortunately, we must also take into account the possibility that a new manager or
owner may feel the need to assert themselves by making radical changes??”even where
those changes are not merited by the situation.
Pages:
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674