Earlier, Chapters 10??“12 have
focused on individual parts of the solution, and the case studies in Chapters 5??“9 have
described what happened in speci?¬?c instances. Here, we will give an overview of the
process as a whole and also look at the various groups and roles involved.
The ?¬?rst steps are to identify a good area in which to apply DSM (Section 13.1)
and assemble a team to carry out the work (Section 13.2). The choice of domain
can be tested through a proof of concept implementation of part of the DSM
solution (Section 13.3). If all looks good, a full DSM solution can be built for that
domain (Section 13.4) and tried out in a real-life pilot project (Section 13.5). You
can then polish and update the DSM solution based on feedback from the pilot
project and deploy it to your organization (Section 13.6). The deployment will
already have involved planning for the evolution of the DSM solution (Section
13.6.3), and this evolution will continue throughout the usage of the DSM solution
(Section 13.4).
13.1 CHOOSING AMONG POSSIBLE CANDIDATE DOMAINS
Deciding whether to applyDSM in a given domain should take into account a number
of factors. The domain itself has surprisingly little effect: the whole idea of DSM
means it is highly adaptable to different domains. Similarly, the target platform is
Domain-Speci?¬?c Modeling: Enabling Full Code Generation, Steven Kelly and Juha-Pekka Tolvanen
Copyright # 2008 John Wiley & Sons, Inc.
Pages:
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618