Worse, the license agreement
392 TOOLS FOR DSM
(since amended) demanded that no code generated from DSM tools built with DSL
Tools may ever be run on a non-Microsoft platform:
Code Generation and Optimization Tools. You and your end users may not use any code
generation or optimization tools included in the [Visual Studio SDK] or Visual Studio
(such as compilers, linkers, assemblers, runtime code generators, or code generating
design and modeling tools) to create programs, object code, libraries, assemblies, or
executables to run on a platform other than Microsoft Platforms.
From an early stage, Microsoft decided that MOF and UML were unsuitable for
describing modeling languages, stating clear arguments similar to those we have
discussed elsewhere. While this could be imagined to be a thrust against the IBM??“
Eclipse??“OMG trinity, many of the leading DSLTools ?¬?gures were previously closely
involved with UML and the OMG. Indeed, the core of the team seems to have been
brought in from outside Microsoft: Jack Green?¬?eld was a Chief Architect at Rational,
Keith Short was CTO at Texas Instruments, Steve Cook was a Chief Architect at IBM.
The resulting meta-metamodel is not, however, all that different from MOF, and
indeed shares many of its failings. There is no clear concept of multiple graphs, no
n-ary relationships, roles and ports are not ?¬?rst-class elements, and reuse is hampered
by the requirement that each element be a child of exactly one strict aggregation.
Pages:
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757