Editing Domain-specific language (section)

===Software engineering uses===
There has been much interest in domain-specific languages to improve the productivity and quality of [[software engineering]].  Domain-specific language could possibly provide a robust set of tools for efficient software engineering. Such tools are beginning to make their way into the development of critical software systems.

The Software Cost Reduction Toolkit<ref>{{cite book |first=C. |last=Heitmeyer |year=1999 |chapter=Using the SCR* toolset to specify software requirements |chapter-url=http://chacs.nrl.navy.mil/publications/CHACS/1998/1998heitmeyer-WIFT.pdf |title=Proceedings. 2nd IEEE Workshop on Industrial Strength Formal Specification Techniques |publisher=IEEE |isbn=0-7695-0081-1 |pages=12–13 |doi=10.1109/WIFT.1998.766290|s2cid=16079058 |archive-url=https://web.archive.org/web/20040719135712/http://chacs.nrl.navy.mil/publications/CHACS/1998/1998heitmeyer-WIFT.pdf |archive-date=2004-07-19 }}</ref> is an example of this. The toolkit is a suite of utilities including a specification editor to create a [[Software Requirements Specification|requirements specification]], a dependency graph browser to display variable dependencies, a [[consistency checker]] to catch missing cases in [[well-formed formula]]s in the specification, a [[model checker]] and a [[Automated theorem prover|theorem prover]] to check program properties against the specification, and an invariant generator that automatically constructs invariants based on the requirements.

A newer development is [[language-oriented programming]], an integrated software engineering [[Methodology (software engineering)|methodology]] based mainly on creating, optimizing, and using domain-specific languages.