Domain-specific modeling: Difference between revisions

Revision as of 14:33, 2 November 2016

Revision as of 21:52, 14 December 2016

Line 29:

Using a ___domain-specific language environment can significantly lower the cost of obtaining tool support for a ___domain-specific language language, since a well-designed ___domain-specific language environment will automate the creation of program parts that are costly to build from scratch, such as ___domain-specific editors, browsers and components. The ___domain expert only needs to specify the ___domain specific constructs and rules, and the ___domain-specific language environment provides a modeling tool tailored for the target ___domain.

Most existing ___domain-specific language takes place with ___domain-specific language environments, either commercial such as [[MetaEdit+]] or [[Actifsource]], open source such as [[Generic Eclipse Modeling System|GEMS]], or academic such as [[Generic Modeling Environment|GME]]. The increasing popularity of ___domain-specific language has led to ___domain-specific language frameworks being added to existing IDEs, e.g. [http://www.eclipse.org/modeling/ Eclipse Modeling Project] (EMP) with [[Eclipse Modeling Framework|EMF]] and [[Graphical Modeling Framework|GMF]], or in Microsoft's [https://web.archive.org/web/20060423095834/http://msdn.microsoft.com:80/vstudio/DSLToolsdsltools/ DSL Tools] for [[Software factory|Software Factories]].

== Domain-specific language and UML ==