3.1 Sample requirements
Give the requirements for the example functionality, including how it interfaces with
other parts of the system.
3.2 Sample design
Give the design documents, including graphical models and text where available. As far
as possible, the design should be in step with the code below.
3.3 Sample code
Give the code for this example. If there are several ?¬?les then also provide an overview of
what each ?¬?le does.Where possible, comment the code with references to the design documents.
These comments will help in analyzingwhich parts ofmodels could producewhich
parts of code.
336 DSM DEFINITION PROCESS
13.3.2 During the Workshop
The activities during the workshop will unsurprisingly be an application of the
material in Chapters 10 and 11, and to a lesser extent in Chapter 12, following a
miniature version of the process described below in Section 13.4. The key component
is the modeling language, and the key way of judging it is that it captures all the
information needed for the sample application, and that by changing some of that
information you would be able to describe a reasonable range of different but similar
applications. You must resist the temptation to work on the more familiar areas of the
framework or code generation, or to spent too much time on the graphical
representation of the modeling language.
Pages:
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630