As the modeling concepts
were largely taken directly from the UI elements, it was also natural to take the
symbols from the actual phone UI. This created a powerful semantic mapping from
the model to the running application. Figure 8.5 illustrates symbol de?¬?nitions for the
Form, Query, and SMS sending concepts. Form and Query are identical to their
appearance in an executable application. Form includes its own compartment for the
Options menu, from which users could draw connections to add menu items for the
connected application elements. Query shows a prompt and an optional initial value as
FIGURE 8.5 De?¬?ning the notational elements for language concepts Form, Query,
and SendSMS
LANGUAGE FOR APPLICATION MODELING 173
well as an icon for text entry, number entry, or Boolean entry, as speci?¬?ed by the Query
type. Text message sending was shown by an envelope symbol showing the complete
message content and recipient number.
Other modeling concepts were de?¬?ned in a similar way and their appearance is
illustrated in the example model (Fig. 8.6). Navigation was illustrated using directed
arrows: normal navigation with a solid line with an arrow and canceling with a dotted
line and ???Cancel??? text in the relationship. Menu items were also speci?¬?ed via
relationships, but those were connected to the bottom left port compartment in the
main UI control.
Pages:
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328