On the basis of our experience over several dozen such workshops, generally over
two days, we can give some rough indications of the timetable. On the ?¬?rst morning,
we generally spend about 45 minutes getting to know people and making sure they
understand the main principles of DSM. The rest of the morning is spent sketching out
various decompositions of the information of the domain in general, and the sample
application in particular. This gives us some possible starting points for the modeling
language??”or, if the domain seems to require it, modeling languages.We look at the
code of the sample application to recognize parts that are repeated, common to many
applications, or variable depending on the application. At this stage, we are not
thinking about code generation but about making sure that the modeling language will
be able to capture the information we need.
TABLE 13.2 (Continued )
3.4 Sample user??™s manual
If the code will have a human user present when run, either using or monitoring the
application, give user instructions for that person using this code.
4. Rough modeling language sketches
Draw the diagrams below in whatever is the easiest format: hand drawn is ?¬?ne.
4.1 Product contents
Often a product (or range of products) consists of several parts (features, modules,
etc.
Pages:
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631