Figure 10.2 shows an application design in a language that is clearly based on look
and feel. The language targets the human-machine interface of an automotive
infotainment system, specifying displays and their content together with the
behavioral logic of the applications. If you are familiar with some infotainment
applications, like navigation or setting preferences for traf?¬?c announcements, then
you will most likely understand what the application does just by looking at the model.
Look and feel are represented directly in the language by using as modeling
concepts the actual displays, user interface widgets, and user controls provided by the
system. Having identi?¬?ed modeling concepts for one kind of display, widget type, or
navigation path, the other modeling concepts can be de?¬?ned similarly. It is relevant to
note that, although the underlying framework and way to map these modeling
concepts to individual code may differ among the concepts, it does not matter in the
language creation phase. Basing a language purely on look and feel is not normally
enough: You also need to identify and map non-GUI concepts to other concepts in the
language or ?¬?nd a mapping to other languages.
Variability Space One ef?¬?cient approach to start de?¬?ning a language is to focus
on variability: you de?¬?ne the language so that variability options are captured by the
modeling concepts, and the modeler??™s role is to concentrate on the areas that differ
FIGURE 10.
Pages:
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424