1.4.2 Automation with Generators
While making a design before starting implementation makes a lot of sense, most
companies want more from the models than just throwaway speci?¬?cation or
documentation that often does not re?¬‚ect what is actually built. UML and other
code-level modeling languages often just add an extra stepping stone on the way to
the ?¬?nished product. Automatically generating code from the UML designs
(automating step three) would remove the duplicate work, but this is where UML
generally falls short. In practice, it is possible to generate only very little usable
code from UML models.
Rather than having extra stepping stones and requiring developers to master
the problem domain, UML, and coding, a better situation would allow developers to
specify applications in terms they already know and use and then have generators
take those speci?¬?cations and produce the same kind of code that developers used to
write by hand. This would raise the abstraction level signi?¬?cantly, moving
away from programming with bits and bytes, attributes, and return values and
toward the concepts and rules of the problem domain in which developers are
working. This new ???programming??? language then essentially merges steps one and
two and completely automates step three. That raised abstraction level coupled with
automatically-generated code is the goal of Domain-Speci?¬?c Modeling.
Pages:
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51