Domain-specific modeling: Difference between revisions

Revision as of 12:12, 23 June 2014

Revision as of 18:31, 25 November 2014

Line 10:

Having the modeling language and generator built by the organization that will use them allows a tight fit with their exact ___domain and needs. It also reduces the time needed for developers to learn the modeling language, since it can use familiar terms and concepts. Finally, since only one organization's requirements need be taken into account, it is easier for the modeling language to evolve in response to changes in the ___domain.

Domain-specific language languages can usually cover a range of abstraction levels for a particular ___domain. For example, a ___domain-specific language language for mobile phones could allow users to specify high-level abstractions for the [[user interface]], as well as lower-level abstractions for storing data such as phone numbers or settings. Likewise, a ___domain-specific language language for financial services could permit users to specify high-level abstractions for clients, as well as lower-level abstractions for implementing stock and bond trading algorithms.

== Domain-specific modeling topics ==