Content deleted Content added
No edit summary |
→Overview: add example of ___domain-specific modeling |
||
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 in response to changes in the ___domain.
Domain-specific languages can usually cover a range of abstraction levels for a particular ___domain. For example, a ___domain-specific modeling 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 modeling 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 is also helpful to reason about low-level software artifacts.<ref>{{Citation|last=Eichberg|first=Michael|title=Model-Driven Engineering of Machine Executable Code|date=2010|url=https://hal.archives-ouvertes.fr/hal-01575664/file/Model-driven-Engineering-of-Machine-Executable-Code.pdf|work=Modelling Foundations and Applications|volume=6138|pages=104–115|doi=10.1007/978-3-642-13595-8_10|access-date=2019-03-06|last2=Monperrus|first2=Martin|last3=Kloppenburg|first3=Sven|last4=Mezini|first4=Mira}}</ref>
== Topics ==
| |||