Focusing on
a narrow area of interest makes it possible to map a language closer to the
actual problem and makes full code generation realistic??”something that is dif?¬?cult,
if not impossible, to achieve with general-purpose modeling languages.
For instance, UML was developed to be able to model all kinds of application
domains (Rumbaugh et al., 1999), but it has not proven to be successful in truly
model-driven development. If it would, the past decade would have demonstrated
hundreds of successful cases. Instead, if we look at industrial cases and different
application areas where models are used effectively as the primary development
artifact, we recognize that the modeling languages applied were not generalpurpose
but domain-speci?¬?c. Some well-known examples are languages for
database design and user interface development. Most of the domain-speci?¬?c
6 INTRODUCTION
languages are made in-house and typically less widely publicized. They are,
however, generally more productive, having a tighter ?¬?t to a narrower domain, and
easier to create as they need only satisfy in-house needs. Reported cases include
various domains such as automotive manufacturing (Long et al., 1998), telecom
(Kieburtz et al., 1996; Weiss and Lai, 1999), digital signal processing (Sztipanovits
et al., 1998), consumer devices (Kelly and Tolvanen, 2000), and electrical utilities
(Moore et al.
Pages:
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36