Although you might fully master the UML models shown in
Chapter 1, the speci?¬?cation made with the domain-speci?¬?c language may better
explain what the application does. This closer alignment with the problem domain
makes the models more usable right from the requirement speci?¬?cation phase.
Customers and domain experts can now more easily participate in the development
and validate the models at the speci?¬?cation phase. They can understand the
application functionality much better from the domain-speci?¬?c models than, for
example, from UML.
The mapping to the problem domain is so close in Fig. 1.6 that the modeling
language could almost be given to phone users to specify their own applications. In
practice, in this domain only a limited percentage of phone owners could use the
language for product development. However, the case of insurance products described
in Chapter 6 illustrates a DSM language that is used directly by domain experts, with
no programming background, to specify applications.
DSM Support for Early Validation In addition to simply reading the models to
validate them, DSM may improve quality if concept demonstrations and early
prototypes can be created from models. Customers and domain experts can then create
partial models or use modeling languages speci?¬?cally made for specifying
requirements.
Pages:
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74