Ideally, those parts of the requirements can be executed immediately
after having speci?¬?ed them into a model.
28 BUSINESS VALUE
Later, the same models can be extended by application developers or they can use
different domain-speci?¬?c languages but now have requirements that can be partially
or completely executed. Naturally, if the execution is complete, further application
development is not needed, but at least in developing embedded applications it is usual
for prototypes specifying and illustrating requirements to be implemented in a
different target environment than the actual product. This is simply done to speed up
the feedback loop and have functionality ?¬?xed earlier. For example, the generated
prototype for a car infotainment system could be some Java code running in a browser
to highlight functionality, whereas the production code needs to be integrated in the
particular car infotainment platform.
2.2.3 Testing with DSM
Rather than handling application quality by conducting testing activities on the code,
DSM addresses errors earlier??”at the modeling stage when speci?¬?cations are created.
This is relevant, as the earlier we can detect errors, the cheaper their correction
becomes. Obviously, DSM does not make testing obsolete: functional testing is still
needed but developers now have more time for this since many typical tests are no
longer needed.
Pages:
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75