SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 278 | Next

Steven Kelly and Juha-Pekka Tolvanen

"Domain-Specific Modeling"

7.4, but we will stay with the original metamodel for the
purposes of this chapter.
7.3.3 Modeling Notation
As Domatic already used some simple ?¬‚ow chart symbols, the notation took these
as its basis. Start and Stop were gray boxes containing their name, and conditional
points such as DTMF_Input and If were represented as diamonds. In the toplevel
VoiceMenu diagrams, the schematic symbol for a loudspeaker was used to
represent all items containing speech??”VoiceOutput, InvalidInput, and Timeout.
This was partly a concession to time limitations: separating these symbols only
by color might be confusing, particularly since one is an object and two are
relationships.
In VoiceOutput diagrams, speech segments were represented by a cartoon speech
bubble showing the sequence of words or phrases to be spoken. SystemCall sequences
were shown with a traditional ?¬‚owchart symbol: a cut-off rectangle. The lines from If
were labeled as TRUE and FALSE, with TRUE leading to a circle representing the
GotoPoint.
FIGURE 7.4 Alternative metamodel for VoiceOutput
HOME AUTOMATION MODELING LANGUAGE 149
7.4 HOME AUTOMATION MODELING LANGUAGE IN USE
For each home automation system type, there would normally be one set of diagrams
specifying how the user could control it over the phone. At the top level would be a
VoiceMenu diagram, and eachVoiceOutput object in that could be exploded to its own
VoiceOutput diagram.


Pages:
266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290
hotel jelenia góra Russian bride Free English grammar and study guid powiekszenia wielkoformatowe counter strike 1.6