1 (Continued )
* Only for large customers ??2 DSM can integrate many of these
bespoke cases back into the
mainstream software artifacts,
bene?¬?ting both large and
small customers
* Often but only in limited ways ??1 Possible small language to describe
con?¬?guration
* Little or not at all 0 Useful only if DSM will be used for the
main application
Do you have good source code examples available, for example for teaching
new staff?
* Yes ??3 Offers a basis for the generator and is
indicative of a mature domain where
development is managed well
* No, but we are always saying
we should make some
0 Basis exists, DSM can help bring about
wanted change, but process will be harder
* Some available, but out of date
and from different times
1 Often indicative of a lack of stability and
of reworking upon reworking, and hack
upon hack. DSM may be an effective
way out if there is a strong expert
developer
* No, our staff are all expert
developers
3 if said by manager
??1 if said by developer
Do you have an in-house application framework?
* Yes, with established guidelines,
best practices and sample code
??3 Clear existing framework, expected code
generator output, domain concepts
* Yes, the previous version is the
guideline
??2 Domain concepts clear, framework quite
easy to build from existing code
* No, but we try to reuse legacy
components
2 Would have to de?¬?ne the framework,
domain concepts probably also unclear
* No, we develop everything
from scratch
Abort ???First of a kind??? development, not worth
targeting
332 DSM DEFINITION PROCESS
patterns for mapping combinations of those concepts into code, and a good knowledge
of the existing framework and platform.
Pages:
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622