Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.
About 10,000 papers for “Domain-specific language”
Arie van Deursen, Paul Klint · 2002
A domain-specific language (DSL) provides a notation tailored towards an application domain and is based on the relevant concepts and features of that domain. As such, a DSL is a means to describe and generate members of a family of programs in the domain. A prerequisite
Cited by 0
Anonymous · 2018
Cited by 0Open access
Kevin Backhouse · 2000
ion Facilities . . . . . . . . . . . . . 55 4 Conclusion 56 4.1 Research Goals . . . . . . . . . . . . . . . . . . . . . . . . . . 56 4.1.1 Secondary Goals . . . . . . . . . . . . . . . . . . . . . 57 A Adding Exceptions to an Imperative Language 59 A.1 The Base Language . . . . . . . . . . . . . . . . . . . . . . . . 60 A.1.1 The Grammar . . . . . . . . . . . . . . . . . . . . . . . 60 A.1.2 Imperativelib.mli . . . . . . . . . . . . . . . . . . . 61 A.1.3 Imperativelib.ml . . . . . . . . . . . . . . . . . . . . 61 A.1.4 Internalname.mli . . . . . . . . . . . . . . . . . . . . 63 A.1.5 Internalname.ml . . . . . . . . . . . . . . . . . . . . . 63 A.1.6 compile.ml . . . . . . . . . . . . . . . . . . . . . . . . 64 4 A.1.7 Attribution Rules . . . . . . . . . . . . . . . . . . . . . 64 A.2 The Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 A.2.1 The Grammar Extensions . . . . . . . . . . . . . . . . 69 A.2.2 Attribution Rules . . . . . . . . . . . . . . . . . . . . . 7...
Cited by 0
Alex Rojco, А. Н. Попов · 2024
A broad spectrum of space application domains are increasingly making use of heterogeneous and large volumes of data with varying degrees of human in the loop. Applications include critical areas such as space habitat management, healthcare delivery, and emergency management while the International Space Station Environmental Control and Life Support System (ECLSS) as well as PHM for Human Health and Performance (PHM4HHP) serve as examples of the applications. This paper suggests a discussion on implementation of the Model Driven Engineering paradigm (a.k.a. Model Based Systems Engineering approach) for PHM focusing on HHP on crewed space exploration missions and introduces a conceptual model and framework - the PHM4HHP Domain Specific Language - to support a data-centric and model-driven approach and develop requirements for integration of heterogeneous models and their respective data for the entire life-cycle of the Health Support System (HeSS) being designed to validate on the International Space Station (ISS). While the discussion starts with focusing on PHM4HHP concepts that make the PHM4HHP domain different from conventional healthcare delivery and is to elaborate the PHM foundations for HHP in terms of basic concepts, driving principles, and current practices to employ PHM4HHP on space exploration missions, the second part is an effort to convert the PHM language to a UML-based metamodel in terms of the promising model-driven and data-centric approach including inherent exercises such as profiling, mapping, and building metamodels. The paper also articulates key requirements in terms of predictive diagnostics providing early and actionable real-time warnings of impending health issues that otherwise would have gone undetected.
Cited by 0
Jean‐Philippe Babau, Mickaël Kerbœuf · HAL (Le Centre pour la Communication Scientifique Directe) · 2011
International audience
Cited by 9
Komninos, Nickolas · 2018
Cited by 0
Iozzia, Guglielmo · 2025
Cited by 0
R.A. ten Buuren · 2015
In this report we present a framework for the generation of tests using domain-specific models. These tests can be used to verify the correctness of the artifacts generated using the domain-specific model and systems that use these artifacts. By generating the tests instead of manually developing them, development time is reduced while usability is improved. The test generation process consists of three phases: generalization, generation and specification. In the generation phase the domain-specific model is transformed to an instance of a newly developed generic metamodel, to abstract away from language-specific features. In the generation phase, generic test cases are generated that achieve branch/condition coverage. In the specification phase the generic test cases are transformed to executable test code. By keeping the test cases generic, several types of tests can be generated using the same generic test case. We show that the developed framework supports a multitude of languages and resulting test types. We also discuss several areas where the framework can be extended with addition features. An important lesson learned during the research and development is that a DSL (testing) framework should be setup modular, extensible and small.
Cited by 2
Rahman, Evgeny, Bellmore, Jarrod Thomas · Digital WPI · 2005
Domain-Specific Languages are developed in order to facilitate software reuse and increase the ease of building domain-specific applications. There is no unified approach to the design and development of these languages and as a result many of them are difficult to use and extend. The goal of this project is to create such an approach and test its efficiency by using it to create a sample Domain-Specific Language.
Cited by 0
A. J. Patel, Keshav Kumar, Bishwajeet Kumar Pandey · Apress eBooks · 2025
Domain-specific languages are in contrast to the general-purpose languages—for example, Java or Kotlin—which can be used to develop an application and can be written in multiple parts of an application. DSL is more concise and readable, as it mostly reads like an English statement. An example of DSL is the SQL language, which is readable and expressive rather than another general-purpose language.
Cited by 0
Bernhard Rumpe⋆, Ingo Weisemöller · arXiv (Cornell University) · 2014
Domain specific languages (DSLs) allow domain experts to model parts of the system under development in a problem-oriented notation that is well-known in the respective domain. The introduction of a DSL is often accompanied the desire to transform its instances. Although the modeling language is domain specific, the transformation language used to describe modifications, such as model evolution or refactoring operations, on the underlying model, usually is a rather domain independent language nowadays. Most transformation languages use a generic notation of model patterns that is closely related to typed and attributed graphs or to object diagrams (the abstract syntax). A notation that reflects the transformed elements of the original DSL in its own concrete syntax would be strongly preferable, because it would be more comprehensible and easier to learn for domain experts. In this paper we present a transformation language that reuses the concrete syntax of a textual modeling language for hierarchical automata, which allows domain experts to describe models as well as modifications of models in a convenient, yet precise manner. As an outlook, we illustrate a scenario where we generate transformation languages from existing textual languages.
Cited by 15Open access
Barrett R. Bryant, Jean‐Marc Jezéquél, Ralf Lämmel et al. · Lecture notes in computer science · 2015
Cited by 11
Saman Amarasinghe · OSTI OAI (U.S. Department of Energy Office of Scientific and Technical Information) · 2018
The focus of this project was the development of the infrastructure supporting DSLs. The goal is that DSLs can be built easily and economically to address the requirements of future HPC software development on Exascale architectures. We proposed to use a novel integrated approach to support the lifecycle of DSL development and involve all major players including HPC programmers, domain algorithm experts, DSL designers, implementation experts. The resulting software artifacts and processes will include components supporting application migration, DSL specifications, DSL language parsing, compiler construction, refinement and transformation, performance analysis, runtime support, as well as parameterizing abstract extreme-scale machines.
Cited by 0Open access
Tim Sheard, Zine-el-Abidine Benaissa, Enes Pašalić · 2000
Abstract : The impact of Domain Specific Languages (DSLs) on software design is considerable. They allow programs to be more concise than equivalent programs written in a high-level programming languages. They relieve programmers from making decisions about data-structure and algorithm design, and thus allows solutions to be constructed quickly. Because DSL's are at a higher level of abstraction they are easier to maintain and reason about than equivalent programs written in a high-level language, and perhaps most importantly they can be written by domain experts rather than programmers. The problem is that DSL implementation is costly and prone to errors, and that high level approaches to DSL implementation often produce inefficient systems. By using two new programming language mechanisms, program staging and monadic abstraction, we can lower the cost of DSL implementations by allowing reuse at many levels. These mechanisms provide the expressive power that allows the construction of many compiler components as reusable libraries, provide a direct link between the semantics and the low-level implementation, and provide the structure necessary to reason about the implementation.
Cited by 0
Paladi, I., Frunze, V., Ursu, V. et al. · 2023
Cited by 0Open access
Eric Van Wyk · 2008
Software development is a time-consuming, and error-prone process. A significant part of the problem is caused by the large semantic gap between the programmer’s high-level understanding of the problem and the relatively low-level language in which the problem solutions are encoded. General purpose language features such as generics in object-oriented programming or higher-order functions are helpful in specifying abstractions for a specific problem or domain, but these are limited in that they only provide the functionality of the desired abstractions. Domain-specific languages [6] can provide this same functionality but they also provide language constructs (notations) for the (domain-specific) abstractions and thus help reduce this semantic gap by raising the level of abstraction of the language to that of a specific domain. These languages also provide domain-specific analyses and optimizations that are difficult, if not impossible, to specify for programs written in general purpose languages. But the fundamental issue remains since problems often cross multiple domains and no language contains all of the general-purpose and domain-specific features needed to address every aspect of the problem. Thus, programmers cannot “say what they mean ” but must encode their ideas as programming idioms at a lower level of abstraction. It is our position that extensible languages provide a promising way to improve the software development process and software quality by reducing the semantic gap. An extensible language can easily be extended
Cited by 0
Akshi Kumar · 2024
This chapter presents domain-specific applications of NLP in sectors like healthcare, legal, finance, and education. It illustrates how tailored NLP solutions can address the unique language processing requirements of these industries, from clinical documentation and legal case analysis to financial forecasting and educational tools. The chapter demonstrates the adaptability and impact of NLP across diverse domains.
Cited by 0
Jarrod Thomas Bellmore, Evgeny Rahman · 2005
Cited by 0
Komninos, Nickolas Demitrios George · Institutional Research Information System (University of Udine) · 2020
Cited by 0
Lucie Attout, Steve Majerus · Open Repository and Bibliography (University of Liège) · 2019
editorial reviewed
Cited by 0Open access