An important goal was therefore the ability to quickly
create a new DSM solution, including the modeling language, generator, and tool
support.
Domatic used no speci?¬?c method for software development. Their developers
would sometimes draw simple ?¬‚owcharts or state diagrams, either before or after they
wrote the code. Reuse of code from older projects followed the ???industry standard???
practice of simply copying whole code ?¬?les and changing parts. Recognizing the
problems inherent in this approach, Domatic hoped that DSM solutions would
increase the consistency of their software development and the reusability of designs
and code.
As their current development relied largely on ad hoc or post hoc documentation
and testing, Domatic were also interested in the fact that DSM models were at a high
enough level of abstraction to serve as a communication medium with clients. The
models could serve as the formal requirements speci?¬?cation, and at the same time as
internal design documentation. Through code generation, the models could also be
immediately tested.
7.2 DEVELOPMENT PROCESS
The DSM solution was developed in MetaEdit+ 3.0 by a consultant from MetaCase
and an expert developer from Domatic. The consultant supplied the DSM know-how
and actually built the metamodel and generators. Domatic supplied the understanding
of the domain and the required code, and also made an extension to their spreadsheet
assembler.
Pages:
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279