These typical problems of manual programming
had already become very visible when the company had implemented its ?¬?rst speci?¬?-
cations of existing insurance products.
For the implementation of the DSM language, generator, and related tooling, the
company invited bids from two external companies. The key requirements for the
selection were the time needed to implement the DSM solution and its development
costs. The company decided to use a commercial metamodeling tool and an external
consultant to implement DSM. The actual implementation work took 11 man-days.
The project was started in early August and the DSM solution was delivered to the
company at the end of September. In October a pilot study was conducted with a few
modelers and the DSM solution was introduced to the organization with a 2-day
training course.
Before de?¬?ning the DSM solution began, a target platform had already been
selected: a repository product following theMeta Object Facility (MOF) as a storage
format and interface with other tools. As mentioned, a few product speci?¬?cations
DEVELOPMENT PROCESS 121
were already implemented as Java code. This code was used to test the other
components used, such as the libraries in the framework and the repository. During
DSMcreation, the manually written Java code specifying the fewproducts was used
as a reference for testing the modeling language and the code generator.
Pages:
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246