). Sketch a (partial) typical product along with its parts and subparts. Mark which
parts stay largely the same between products (e.g., existing code libraries, components)
and which parts are to be modeled in the other diagrams below.
4.2 Product behavior
Sketch a diagram of a typical feature (possibly the sample feature above) as might be
drawn by designers on a whiteboard at an initial design session. Try to avoid ???standard???
design languages such as UML, which concentrate on the resulting code components,
and use informal concepts commonly used and understood by designers. Sometimes
there may need to be more than one diagram at this level, for example, one for the user
interface and one for the behavior.
5. Other relevant material
PROOF OF CONCEPT 337
After lunch, we decide on a sketch of the modeling language and draw a sketch
model for the sample application. As we get close to something that seems to work, we
start de?¬?ning the concepts of the modeling language: their names and the information
that each has to store. So far, even with the fastest DSM tools, the work has generally
been so likely to change in major ways that the most effective representation medium
has been a whiteboard or paper. The whiteboard has the advantage that you can erase
minor mistakes to keep things readable; ?¬‚ip charts are a little messier but give you
effectively unlimited space, as you can tear off pages and stick them to walls.
Pages:
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632