Content deleted Content added
→See also: GOP |
m →See also: sort |
||
Line 15:
A book that describes this concept, with examples, is ''Building Better Applications: a Theory of Efficient Software Development''.<ref>Dunlavey 1994.</ref> It takes the approach to capture requirements in the user's terms, and then to try to create an implementation language as isomorphic as possible to the user's descriptions, so that the mapping between requirements and implementation is as direct as possible. A measure of the closeness of this [[isomorphism]] is the "redundancy" of the language, defined as the number of editing operations needed to implement a stand-alone change in requirements. It is not assumed ''a-priori'' what is the best language for implementing the new language. Rather, the developer can choose among options created by analysis of the information flows — what information is acquired, what its structure is, when it is acquired, from whom, and what is done with it. See [[Linguistic Method]].
==
* [[Model Driven Engineering]]▼
* [[Domain Specific Language]]s▼
* [[Aspect-oriented programming]]
* [[Generative programming]]▼
* [[Intentional Programming]]▼
* [[Concept programming]]▼
* [[Code generation]]
* [[
* [[Dialecting]]
▲* [[Domain Specific Language]]s
* [[Metalinguistic abstraction]]▼
* [[Linguistic Method]]▼
* [[Fourth-generation programming language]]
▲* [[Generative programming]]
▲* [[Intentional Programming]]
▲* [[Linguistic Method]]
* [[Macro (computer science)#Lisp macros|LISP macros]]
▲* [[Metalinguistic abstraction]]
▲* [[Model Driven Engineering]]
==References==
| |||