In Part IV, the various parts of a DSM
solution may all be the responsibility of one person, or then they may be split between
two or more people. Chapters 11 and 12, and to a slightly lesser extent Chapters 14
and 15, will make most sense to experienced programmers. Chapters 10 and 13 may
interest those in more of an architect or project management role.
The book web site at http://dsmbook.com contains updates, the modeling languages
from Part III, and a free MetaEdit+ demo.
PREFACE xv
ACKNOWLEDGMENTS
With the solid base we had to build on, subsequent years of work with colleagues and
customers, and great interactions with our peers in this community, it is clear that we
are indebted to far too many people to mention even a representative sample of them
here. Even just the OOPSLA workshops on DSM account for several hundreds of
authors over the past seven years: seeing so many others coming to similar conclusions
and achieving similar successes played a major role in encouraging us on this
path.
Some people however simply must be mentioned, so we shall ?¬?rst return to the
beginnings of DSM to thank RichardWelke, Kalle Lyytinen, and Kari Smolander for
the research that we built on, and for an environment where what was right mattered
more than who was right. From that MetaPHOR project to the present day Pentti
Marttiin and Matti Rossi have played a central role in keeping us sane, amused, and at
least tolerably ?¬?t, not to mention an innumerable amount of discussions ranging over
all possible metalevels.
Pages:
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27