Most
importantly it shows which kind of applications you could develop in the future.
This information is not visible from the models alone but is seen from the
metamodel and partly from the generators. These showthe possible combinations of
model elements based on the metamodel. If we rely again on the mobile phone
example from Chapter 1, the metamodel would reveal how many physical displays
LEVERAGE EXPERTISE 33
the mobile phones can have, howmany views individual applications can have, how
many softkey buttons are available, and so on.
Introducing DSM concepts and tools to development teams is a process that
involves a paradigm shift. Team members who have been working at a low level of
abstraction, writing code, are now able to work at a higher level of abstraction and
develop the models from which code, tests, documentation, and so on, are generated
automatically. This change is nothing new: our industry made a similar shift when
moving from assembly to third generation languages (3GLs). Such a change is not
always easy to introduce. Application developers may also reject DSM as it changes
their work too much and may prefer to use a traditional approach. For example, in the
study of a telecom company 2 developers out of the 17 interviewed preferred using the
old manual coding approach instead of DSM (Ruuska, 2001).
Pages:
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86