Toward Standardised Model to Text Transformations

Oldevik, Jon; Neple, Tor; Grønmo, Roy; Aagedal, Jan Øyvind; Berre, Arne-J.

doi:10.1007/11581741_18

Cited by 61 publications

(42 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…One of the foremost applications of string origins is relating (sub)strings of the output back to the input of a transformation [12,10]. Applications of this information include embedding links back to the source program in generated code, inspectors, debuggers (e.g., using SourceMaps [15]), or translating back errors produced by further transformations (e.g., general-purpose language compiler errors).…”

Section: Hyperlinking Generated Artifactsmentioning

confidence: 99%

“…In particular, DSL compilers are often structured as a sequence of transformations, starting with an input program and eventually generating code. It is well-known that origin tracking [16] and model traceability [1,8,12,13,14] provide valuable information for debugging, error reporting and visualization.…”

Section: Introductionmentioning

confidence: 99%

“…• Totality: Unlike existing work in origin tracking and model traceability [12], string origins induce an origin relation which is total. That is, the origin relation maps every character in the output text of a transformation back to its origin.…”

Section: Introductionmentioning

confidence: 99%

“…As in the case of [8], the transformation conveys the traceability information explicitly. To overcome this, [12] and [13] introduce an alternative technique for managing traceability in MOFScript, a language for defining model to text transfor-…”

mentioning

confidence: 99%

See 3 more Smart Citations

Tracing Program Transformations with String Origins

Inostroza

Storm

Erdweg

2014

Theory and Practice of Model Transformations

View full text Add to dashboard Cite

Abstract. Program transformations play an important role in domain-specific languages and model-driven development. Tracing the execution of such transformations has well-known benefits for debugging, visualization and error reporting. In this paper, we introduce string origins, a lightweight, generic and portable technique to establish a tracing relation between the textual fragments in the input and output of a program transformation. We discuss the semantics and the implementation of string origins using the Rascal meta programming language as an example. We illustrate the utility of string origins by presenting data structures and operations for tracing generated code, implementing protected regions, performing name resolution and fixing inadvertent name capture in generated code.

show abstract

Section: Hyperlinking Generated Artifactsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

mentioning

confidence: 99%

See 2 more Smart Citations

Tracing Program Transformations with String Origins

Inostroza

Storm

Erdweg

2014

Theory and Practice of Model Transformations

View full text Add to dashboard Cite

show abstract

“…Esta información recoge íntegramente el modelo creado con la herramienta y permite su posterior transformación a texto aplicando plantillas en lenguaje MOFScript (Oldevik et al, 2005), mediante las cuales es posible generar código a cualquier lenguaje de propósito general. Una vez transformado este fichero XMI al lenguaje que se desee, la aplicación resultante podrá ser desplegada en la plataforma escogida para su utilización.…”

Section: Caso De Estudiounclassified

Modelado específico de procedimientos en el dominio de la Administración Electrónica

Hernández

Pérez²,

Fuente

2012

RISTI

View full text Add to dashboard Cite

Resumen: Debido a la complejidad que reviste el dominio de la Administración Electrónica (AE), las desarrolladas deberán ser capaces de integrarse con la multitud de plataformas y sistemas que componen dicho dominio. El impacto de esta integración además mejorar la tramitación de procedimientos. En el presente trabajo se propone un lenguaje de modelado gráfico (DSL) para la tramitación de procedimientos en el dominio específico de la AE. Este lenguaje parte de la definición de un metamodelo de AE que identifica sus principales entidades y define sus relaciones. Además se construyó una herramienta gráfica de modelado la cual fue probada con dos casos de estudio reales. aplicaciones Palabras clave: Administración Electrónica; Metamodelo; DSL Abstract: Due to the complexity involved in E-Government domain applications, the developed ones should be able to interoperate with the growing number of emerging management platforms. The impact of this integration has among its main goals to improve the procedure management task, which suffers an important lack of technological proposals. This work proposes a graphical domain specific language (DSL) for procedure management in E-Government domain. This language came from the definition of a metamodel that states the principle EGovernment elements and defines its relations. A further graphical modeling tool was developed to implement the DSL and was tested with two actual case studies.

show abstract

An MDD‐based method for building context‐aware applications with high reusability

Paspallis

2019

J Software Evolu Process

View full text Add to dashboard Cite

Adding context -awareness capabilities to modern mobile and pervasive computing applications (apps) is becoming a mainstream activity in the software engineering community. In this respect, many context models and middleware architectures have been proposed with the aim to provide the developers with tools and abstractions that make it easier to produce context-aware applications. However, current solutions suffer from relatively low reusability and lack ease-of-use. In this paper, we propose a two-layer approach based on model-driven development: At the higher layer, we introduce the design of reusable context plug-ins, which can be used to monitor low-level context data and to infer higher-level information about the users, their computing infrastructure, and their interaction. At the lower layer, the plug-ins themselves are synthesized using more elementary, reusable components. We argue that this development approach provides significant advantages to the developers, as it enables them to design, implement, reuse, and maintain the codebase of context-aware apps more efficiently.To evaluate this approach, we demonstrate it in the context of a two-part example application and assess it both qualitatively and quantitatively. KEYWORDScode generation, context awareness, MDD, middleware, plug-in, reusability INTRODUCTIONContext awareness is one of the most sought-after features for modern mobile and pervasive computing applications. Understanding and using context allows applications to identify and predict intention, thus allowing for better and richer human-computer interaction.Researchers have proposed various approaches to ease the task of designing and implementing applications that are context-aware and self-adaptive. At their core, many of these build on reusable code, ranging from the early works of Dey 1 to more recent, plug-in-based architectures such as those described in the previous studies. 2-5 These approaches are designed to allow the applications, which are using them to inquire and access arbitrary context data types. In this respect, the context-awareness and context-inferring parts are separated from the functional logic of the applications by means of reusable context plug-ins (ie, individually deployable units, which provide mechanisms for collecting and processing context data, and inferring higher-level context information). At the same time, many context models and middleware architectures were proposed and documented in the literature. 6,7 Software reuse is at the core of many of those approaches. At a higher level, reuse covers all software engineering phases and ''can be supported by different types of methods, including ad hoc, opportunistic, adaptive, systematic, black-box, whitebox, etc.'' 8 A common drawback in these approaches is that the developers are required to invest a significant amount of time to develop customized components, which are used for collecting, processing, inferring, storing, querying, and accessing context data. Moreover, the developed components are then harder...

show abstract

Toward Standardised Model to Text Transformations

Cited by 61 publications

References 0 publications

Tracing Program Transformations with String Origins

Tracing Program Transformations with String Origins

Modelado específico de procedimientos en el dominio de la Administración Electrónica

An MDD‐based method for building context‐aware applications with high reusability

Contact Info

Product

Resources

About