The development of the DSM solution set out to follow the process for a
proof of concept described in Section 13.3. As we shall see, however, not all went
according to plan.
7.2.1 Before the Workshop and Day 1
Domatic had supplied the consultant with material about their domain and language
three weeks before the workshop. The material covered the whole home automation
domain, focusing on the telecom module. A week before the workshop they
142 HOME AUTOMATION
emphasized a particular description of the whole home automation system and how it
interacted with its sensors, actuators, keypad, screen, data modem, and DTMF voice
control.
The ?¬?rst day of the workshop was spent building up a shared picture of this wider
domain, resulting in a modeling language containing concepts like sensors and
actuators. By the end of the ?¬?rst day, it was apparent that this language was too generic.
Just knowing that there is a sensor called ???smoke detector??? connected to the system,
and an actuator called ????¬?re alarm???, is not enough to generate meaningful code. The
language would thus be useful for describing whole systems, and possibly for
con?¬?guration, but not for demonstrating DSM with full code generation.
7.2.2 Day 2: If at First You Don??™t Succeed. . .
The second day of the workshop had the hard deadline of a meeting at 1 p.
Pages:
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280