Although the above list is extensive, most roles dealing with DSM creation are
handled by just a few people. In fact, it is not exceptional that a single person de?¬?nes
the language, generator, and domain framework. In practice, several people
participate somewhat even then by giving requirements and testing theDSMsolution.
There are several reasons for this. It is unlikely that a single person can ?¬?nd the right
abstraction and develop the necessary architectural elements for DSM. A larger
development team also makes sense from a human resource point of view: the DSM
90 ARCHITECTURE OF DSM
solution becomes one of the most valuable assets of the organization and it is good that
several people understand it intimately.
4.6.2 DSM De?¬?nition Process
TheDSMprocess can perhaps best be viewed as consisting of four main phases: initial
development, deployment, use, and maintenance.
The Proof of Concept As the domain-speci?¬?c approach is often being applied
for the ?¬?rst time in the company, it may be necessary to ?¬?rst demonstrate the feasibility
of DSM as an approach. For such a demonstration, a narrow and well-known area is
usually selected so that the proof of concept can be done quickly. Also, the DSM
solution is not necessarily large but just large enough to give a concrete demonstration
within the domain.
Pages:
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196