6 Conference registration application
AN EXAMPLE: MODELING WITH A GENERAL-PURPOSE LANGUAGE 13
adding elements to the model and linking them together to follow the ?¬‚ow of
navigation and application control.
The Domain-Speci?¬?c Modeling language also includes domain rules that prevent
us from making illegal designs. For example, after sending an SMS message, only
one UI element or phone service can be triggered. The modeling language ???knows???
this rule and won??™t let us draw another ?¬‚ow from an SMS element. If a relevant part of
the design is still missing, for example, the application never reaches a certain widget,
model checking reports warn us about incomplete parts. This means that we do not
need to master the details of the software architecture and required programming
model, and we can focus instead on ?¬?nding the solution using the phone concepts.
As can be seen from this DSM example, all the implementation concepts are
hidden from the models and are not even necessary to know. This shows that the
level of abstraction in models is clearly higher. Once the design, or a relevant part of
it, is done, we can generate and execute the conference registration application in a
phone. There is no need to map the solution manually to implementation concepts
in code or in UML models visualizing the code.
Pages:
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45