9.3.8 Notation for Watch Applications
To model an application in suf?¬?cient detail to allow full code generation generally
requires several different kinds of information. In general-purpose modeling
languages each kind of information would be separated into its own language. A clear
problem with this approach is that it is hard to get a complete view of the application,
as it is split over several diagrams. Such an approach also requires a fair amount of
duplication, as objects (or references to them) must be reused in several different
diagrams, in order to provide the full information about the object from all viewpoints.
This leads to another problem: the dif?¬?culty of keeping all the diagrams synchronized.
To avoid these problems, a domain-speci?¬?c modeling language often includes
several different viewpoints within one language. Because the language constructs
needed for each viewpoint are only a domain-speci?¬?c subset of those needed for that
viewpoint in a generic modeling language, the resulting language remains of a
manageable size. Itdoeshowevercontain avariety of different kinds of information,and
one way to use notation is to help separate the different kinds of information visually.
The Watch Application modeling language contains three main types of
information, corresponding to the three parts of MVC that Secio had decided to
use.
Pages:
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381