Even keeping part of the class diagram
FIGURE 1.5 Activity diagram specifying steps while unregistering from a conference
12 INTRODUCTION
up-to-date in parallel with the code does not help much since it just describes the
implementation code.
1.3.2 DSM Usage Scenario
Next let??™s contrast the above UML approach to DSM. Here the modeling language
is naturally made for developing applications for mobile phones. Figure 1.6 shows a
model that describes the conference registration application. If you are familiar with
some phone applications, like a phone book or calendar, you most likely already
understand what the application does. This model also describes the application
suf?¬?ciently unambiguously, that it can be generated from this high-level
speci?¬?cation. Take a look of the modeling in Fig. 1.6 and then compare it to UML
models that did not get even close to having something running.
In Domain-Speci?¬?c Modeling we would start modeling by directly using the
domain concepts, such as Note, Pop-up, SMS, Form, and Query. These are speci?¬?c
to the mobile phone??™s services and its user-interface widgets. The same concepts are
also language constructs. They are not new or extra concepts as we must always
apply these regardless of how the mobile application is implemented. With this
modeling language, we would develop the conference registration application by
FIGURE 1.
Pages:
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44