The evolution of the DSM
solution has been a major factor, but the evolution of your organization has been even
more important. The developers have learned to use the DSM solution to good effect,
shifting their thinking to a higher level of abstraction, closer to the requirements and to
the end users. The DSM solution team have had their ?¬?rst experience of creating,
introducing, and maintaining their own domain-speci?¬?c modeling language and
generators, taking control possibly for the ?¬?rst time of their own development process,
tools, and languages. No longer will the offerings of third-party vendors and outside
organizations seem like the only possible ???real??? choices, with in-house solutions seen
as little hacks. There will also probably be a change in attitude toward such third-party
tools and solutions: any unrealistic feelings of their unassailable authority and
superiority will have evaporated; any unrealistic demands for perfect solutions will
have been replaced with some measure of respect for the trade offs those vendors are
forced to make.
There will also be an increased maturity in the overall issue of introducing new
technology to your organization. In someways, the ?¬?rstDSMproject will be the major
change; in other ways, each subsequent DSM project will be its own change process.
Pages:
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677