It is, however, certain that there will never be a time when there are no more
immediately pressing issues. While the issues may be more pressing in the short term,
it is unlikely that any of them could bring the return offered by DSM.
Asecond form of not takingDSMsuf?¬?ciently seriously is to start a project, but only
allocate a student, summer intern, or new employee to work on it. For all their brain
power and enthusiasm, these people lack the necessary experience in the domain, the
local code base, and the realities of team development. Because of this ???shallowsoil???,
and the small size of the team, they may be able to build a modeling language quickly:
there will be many things that simply will not occur to them as issues they need to take
into account. Thus while the language may appear quickly, in the hard light of day it
will not stand up to the test. If management or developers are particularly lacking in
perception, this failure may even be perceived to be a failure of DSM in general,
stopping further attempts with a more sensible team from getting off the ground for
years to come.
What then do thorns correspond to? They are the things that are already growing
there, which do not produce much in the way of fruit. In DSM, this generally comes
340 DSM DEFINITION PROCESS
down to existing coding or modeling practices.
Pages:
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639