If you are able to ?¬?nd aDSMsolution that ?¬?ts your domain, it is most likely a better
choice than developing the same functionality manually with general-purpose
modeling languages. However, although a DSM solution can be found for a given
domain, it is not guaranteed that it can be readily applied. It can be based on somewhat
different concepts, use different rules, and generate different programming languages
or, at least, in a different way than is preferred.We have been involved in a number of
mobile phone applications and found that, although the domain is clearly the same, the
modeling language, generators, and underlying target environment are different. For
example, in a phone the main user interface elements are called and speci?¬?ed
differently by the companies. In some companies, a domain concept can be called a
viewwhereas others call it a book or panel and give somewhat different characteristics
for them. The code to be generated is seen to have even more signi?¬?cant differences
than the modeling languages. Aworking DSM solution, if publicly available, would
not therefore necessarily be suitable for any of the companies. For example,
development of TETRA phones at EADS, once part of Nokia, could start by using the
same target environment and DSM solution as Nokia??™s consumer phones used.
Pages:
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90