Improving Domain-Specific Language Reuse with Software Product Line Techniques July/August 2009 (vol. 26 no. 4) pp. 47-53
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2009.95
Developing a domain-specific language (DSL) or a composition of DSLs to model a system concern, such as deploying and configuring software components to meet real-time scheduling constraints, is time consuming. Ideally, developers should be able to reuse DSLs and DSL compositions across projects to amortize development effort. Reusing DSLs is hard, however, because they're often designed to precisely describe a single domain or concern. A new approach uses techniques from software product lines (SPLs) to improve the reusability of a DSL, DSL composition, or supporting tool by providing traceability of language concepts to DSL design. A case study of four DSLs demonstrates the need for—and benefits of—applying SPL reuse techniques to DSLs. 1. M. Mernik, J. Heering, and A.M. Sloane, "When and How to Develop Domain-Specific Languages," ACM Computing Surveys, vol. 37, no. 4, 2005, pp. 316–344.
Index Terms:
feature models, domain-specific languages, reuse, software product lines, domain analysis, domain hierarchy, software engineering
Citation:
Jules White, James H. Hill, Jeff Gray, Sumant Tambe, Aniruddha S. Gokhale, Douglas C. Schmidt, "Improving Domain-Specific Language Reuse with Software Product Line Techniques," IEEE Software, vol. 26, no. 4, pp. 47-53, July/Aug. 2009, doi:10.1109/MS.2009.95 Usage of this product signifies your acceptance of the Terms of Use. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||