Specify symbols for types, whether graphically, declaratively, or in code,
. Ability for a generator to access the models,
. From these speci?¬?cations, create a basic modeling tool.
The modeling tool thus created must offer modelers at least the following facilities:
. Store and retrieve a model from disk,
. Create new instances in models by choosing a type and ?¬?lling in properties,
. Link objects via relationships,
. Lay out the objects and relationships, either by dragging or automatic layout,
. Edit properties of existing objects and relationships,
. Delete objects and relationships
The history of tool development contains numerous instances of small research
projects creating this kind of prototype DSM environment (or metaCASE tool, in
1990s terms). Developing such a tool to the stage where you can produce screenshots
for an article is relatively simple: 1??“3 man-years is enough, depending on
implementation technology and previous experience.
With the recent realization of the bene?¬?ts of model-driven development, and the
need for its modeling languages to be domain-speci?¬?c, we are currently seeing a new
explosion of such tools. Most of these are again from research projects, or their
WHAT IS NEEDED IN A DSM ENVIRONMENT 365
modern-day distributed cousin, open source projects, but a few are also commercial
projects.
Pages:
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697