Most importantly, arrange a meeting
with management and senior developers for right after the end of the workshop. When
you need to produce concrete results rather than interminable wrangling, there??™s
nothing better than knowing that you and your work will shortly be on public display.
The aim of the workshop is not to get everything right, but to get something working.
Before the workshop, you should make sure that all members of your team
understand the ideas of DSM, that all have seen some real examples of it, and that the
majority have at least basic experience with the tools and languages of your DSM
creation environment.
PROOF OF CONCEPT 335
TABLE 13.2 Proof of Concept Template
Proof of Concept Workshop
The aim of this document is to collect the key elements of your domain for the purposes of the
domain-speci?¬?c modeling language implementation workshop.
The goal of the workshop is to de?¬?ne and implement a small, but still signi?¬?cant, part of your
domain-speci?¬?c modeling language to demonstrate the bene?¬?ts with concrete examples for
executives and product developers. The result of the workshop is a partial modeling and code
generation environment for your organization??™s own domain-speci?¬?c modeling language.
As domains differ widely, not all questions may be strictly applicable in your domain: feel free
to change the questions or omit irrelevant parts.
Pages:
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628