An approach for the systematic development of domain‐specific languages

Strembeck, Mark; Zdun, Uwe

doi:10.1002/spe.936

Cited by 82 publications

(116 citation statements)

References 38 publications

Supporting

Mentioning

115

Contrasting

Order By: Relevance

“…Many, but not all domain-specific constraints could have been implemented with XML-Schema. This confirms the results of [4,5] showing that expressing the static semantics is never straightforward within only a structured metamodel. -Implementing model transformations in Prolog to express static analyses allows us to write concise and declarative analyses.…”

Section: Introductionsupporting

confidence: 87%

See 1 more Smart Citation

Model-Driven Engineering of Machine Executable Code

Eichberg

Monperrus

Kloppenburg³

et al. 2010

Modelling Foundations and Applications

View full text Add to dashboard Cite

Abstract. Implementing static analyses of machine-level executable code is labor intensive and complex. We show how to leverage model-driven engineering to facilitate the design and implementation of programs doing static analyses. Further, we report on important lessons learned on the benefits and drawbacks while using the following technologies: using the Scala programming language as target of code generation, using XML-Schema to express a metamodel, and using XSLT to implement (a) transformations and (b) a lint like tool. Finally, we report on the use of Prolog for writing model transformations.

show abstract

Section: Introductionsupporting

confidence: 87%

“…4 XSLT is a pragmatic and good choice to express most of the static semantics of a metamodel implemented with XML-Schema. 5 The need for expliciting the static semantics has a positive impact on the metamodel structure. 6 Using Scala as target language of a code generator ends up in a more readable, maintainable and concise generator.…”

Section: Related Workmentioning

confidence: 99%

Model-Driven Engineering of Machine Executable Code

Eichberg

Monperrus

Kloppenburg³

et al. 2010

Modelling Foundations and Applications

View full text Add to dashboard Cite

show abstract

“…Thus, a testing mechanism for policy-based systems must enable the testing of runtime behavior induced by dynamically changing policies. 1 Similar to the fact that each (non-trivial) software system has an architecture, no matter if the architecture is "good" or "bad", each language is based on a corresponding language (meta) model that defines the language's elements/alphabet and grammar, at least implicitly (see, e.g., [23,26,33 Because policies and scenarios are complementary artifacts (see [24]), scenario-based testing (see, e.g., [16,20,25]) is well-suited to meet the testing demands of dynamic policy-based systems. Scenarios describe action and event sequences and make process descriptions explicit.…”

Section: Policy Language(s) Policy Rulesmentioning

confidence: 99%

“…Each policy language is in essence a domain-specific language (DSL) (see, e.g., [23,26,33]) that enables the definition of policy rules. Policy languages thus combine the advantages of DSLs and policy-based system management.…”

Section: Introductionmentioning

confidence: 99%

Testing Policy-based Systems with Scenarios

Strembeck¹

2011

Parallel and Distributed Computing and Networks / 720: Software Engineering

Self Cite

View full text Add to dashboard Cite

Policy-based systems consist of interacting software artifacts and, at first glance, can be tested as any other software system. In a policy-based system, however, the behavior of system entities may change dynamically and frequently, depending on the policy rules governing this behavior. Therefore, policy-based systems demand for a testing approach that especially allows for the testing of dynamically changing system behavior. Thus, testing of policy rules has to check if the behavior that is actually enforced by a set of policies, conforms to the intended behavior of the corresponding system entities. Scenarios are an important means to specify behavior of software entities. In this paper, we introduce an approach to test policybased systems with scenarios, and present an (embedded) domain-specific language for scenario-based testing.

show abstract

“…Due to its versatility, MDD can be applied as an approach for the systematic specification of information system security properties (see, e.g., [13,14,15,16]). In the context of MDD, domain-specific languages (DSLs) are tailor-made (computer) languages for a specific problem domain (see, e.g., [17,18,19]). In general, a DSL can be defined as a standalone language or as a domain-specific extension to a pre-existing (modeling or programming) language.…”

Section: Introductionmentioning

confidence: 99%

A UML Extension for the Model-Driven Specification of Audit Rules

Hoisl

Strembeck

2012

Lecture Notes in Business Information Processing

Self Cite

View full text Add to dashboard Cite

Abstract. In recent years, a number of laws and regulations (such as the Basel II accord or SOX) demand that organizations record certain activities or decisions to fulfill legally enforced reporting duties. Most of these regulations have a direct impact on the information systems that support an organization's business processes. Therefore, the definition of audit requirements at the modeling-level is an important prerequisite for the thorough implementation and enforcement of corresponding policies in a software system. In this paper, we present a UML extension for the specification of audit properties. The extension is generic and can be applied to a wide variety of UML elements. In a model-driven development (MDD) approach, our extension can be used to generate corresponding audit rules via model transformations.

show abstract

An approach for the systematic development of domain‐specific languages

Abstract: Abstract

Cited by 82 publications

References 38 publications

Model-Driven Engineering of Machine Executable Code

Model-Driven Engineering of Machine Executable Code

Testing Policy-based Systems with Scenarios

A UML Extension for the Model-Driven Specification of Audit Rules

Contact Info

Product

Resources

About