Content deleted Content added
m Reverted edits by 2603:6011:D409:BB6C:85EB:7CD9:EC1F:43C4 (talk) (HG) (3.4.11) |
Citation bot (talk | contribs) Add: isbn, series, authors 1-1. Removed parameters. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by SemperIocundus | #UCB_webform |
||
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|
== Topics ==
| |||