Because of time constraints, the system calls were
left free-form: the modeler had to know to use one of several possible assembler
commands.
From 11:40 to around 12:00, the code generator was extended to handle the
normal usage of these new concepts. The basic rules for how elements could be
connected in the models were already speci?¬?ed along with the concepts, but there
was no time for even the more obvious ?¬?ner rules or checks. With an hour left until
the meeting, there was time to ?¬?nalize the example model, eat a hurried lunch, and
prepare slides for the presentation to management.
7.2.3 Further Development
After the meeting, there was a little time left to refactor the DSM solution. The
modeling language was split into two diagram types, with the top level showing
DEVELOPMENT PROCESS 143
the voice menu and DTMF interactions. Each voice element there exploded to a
lower-level diagram showing how it was built from static text fragments, varied by
system calls. After the proof of concept workshop, the consultant ?¬?nished this
refactoring. He also added the missing parts of the code generator based on the sample
code provided and sent the results to Domatic. These additions after the workshop
took at total of two hours.
7.3 HOME AUTOMATION MODELING LANGUAGE
This particular DSM solution was never taken into wider use at Domatic, and thus has
not experienced the normal evolution and rounding off of sharp corners.
Pages:
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282