Having found a solution,
we would then map that to a speci?¬?cation in some language (step two). With
traditional programming, here the developers map domain concepts to coding
concepts: ???wait for choice??? maps to a while loop in code. With UML or other
general-purpose modeling languages, developers map the problem domain solution
to the speci?¬?cation with the modeling language: like ???wait for choice??? triggers an
action in activity diagram. Step three then implements the full solution: giving the
right condition and code content for the loop code. However, if general-purpose
modeling languages are used, there is an extra mapping from a model to code. It is
most remarkable that developers still have to perform step one without any tool
Domain
idea
Finished
product
Solve problem in domain terms
Assembler
Map to code, implement
UML model
Map to UML
Generate,
add bodies
Code
Map to code, implement
Domain
framework
Domain
model
Generates code No need
to map!
FIGURE 1.7 Bridging the abstraction gap of an idea in domain terms and its
implementation
16 INTRODUCTION
support, especially when we know that mistakes in this phase of development are
the most costly ones to solve. Most of us will also argue that ?¬?nding the right
solution on this level is exactly what has been the most complex.
Pages:
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50