As always, version comments can also provide a vital record of
the design rationale behind decisions.
At the end of the pilot project, you will have your ?¬?rst working application built
with DSM. You will also have a fully working and proven DSM solution, and a fair
idea of what kind of use process works well with it. The pilot project also has a major
role to play in the process of organizational change. It acts as both a marketing vehicle,
showing management and other developers that your DSM solution works, and as an
educational program, producing the ?¬?rst small crop of users who are familiar with
building applications using DSM.
It is thus important to wrap up the pilot project properly. If there were any
changes to the modeling language that you had to postpone, make them now. You
should also apply these changes to the pilot project models, both for testing and also
since you want them to be at the same version level as the models, both built during the
next phase of wider deployment. Write up and present the experiences of the pilot
teamas a project retrospective, and also record the experiences of theDSMteam: what
kinds of evolution worked well, and what kinds gave problems for either the tools or
their users.
While the special nature of the pilot project makes it less productive than later
use, you can still gather some statistics on the time taken to create the product
compared to code-based development.
Pages:
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655