There is also a certain mindset that says it is not
enough to be able to churn out good working application code in the domain time after
time: there must be a higher level way to express applications and automate their
creation. People with this mindset are clearly well suited to the tasks of the DSM
creation team. They are the kind of people who build text editor macros, word
processing templates, and batch ?¬?les or shell scripts. Most useful are those who have
built such things for use by the whole team, as opposed to only for their own use.
Initial trials with the modeling language can happen within theDSMcreation team,
using lightweight formats such as pencil and paper or whiteboards. If there is a good
existing framework and body of example code, and you have a fastDSMenvironment
that supports modeling language evolution, you can move at an early stage to testing
your ideas in practice. One way is to do a short proof of concept project, as described in
the next section, and another way is to do an early version of the DSM pilot project
TABLE 13.1 (Continued )
How would you describe the maturity of your software development process?
* Precisely de?¬?ned and developers
must follow it
0 May be too caught up in CMM and
processes to accept DSM or its
subsequent evolution
* The majority is documented
and we generally follow it
??2 Shows a desire to take the effort to
codify what is known and follow
it as long as it is useful: fertile ground
for DSM
* We have a good idea where
we are at any given time
??1 Developer-led
* No clear process 2 Hard to bring about organizational
change without organization
Can you assign the following kinds of people to the DSM project?
* One of the top three who built
the framework/?¬?rst product
??5
* An experienced developer ??3 Can build code generator
* A small team of normal
developers
??2 Vital for piloting, can build example apps
to be the input for creating generators
* No, but you can have a summer
intern or two
3 May have brains and enthusiasm, but lack
domain knowledge and software
development experience in large teams
and long projects
* No Abort DSM cannot be successful without
the developers??™ experience
ORGANIZING FOR DSM 333
with a DSM use team.
Pages:
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623