Simplicity‐first model‐based plug‐in development

Naujokat, Stefan; Neubauer, Johannes; Lamprecht, Anna-Lena; Steffen, Bernhard; Jörges, Sven; Margaria, Tiziana

doi:10.1002/spe.2243

Cited by 11 publications

(3 citation statements)

References 29 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Also aiming directly at model‐based plug‐in development, Naujokat et al propose a method to enable a graphical modeling framework—namely, jABC—to capture plug‐in development in a domain‐specific setting. The main contribution of this work is that “the intended plug‐in functionality can itself be modeled conveniently in terms of graphical workflows, which then can be translated fully automatically to running code.” While our approach builds on standard UML modeling tools such as Enterprise Architect and the more traditional transformation tool‐chain MOFScript , the work by Naujokat et al is based on their custom‐tailored modeling framework jABC and Genesys transformation tool …”

Section: Discussionmentioning

confidence: 99%

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

Section: Discussionmentioning

confidence: 99%

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

show abstract

“…2.3. Basically, such a plugin is a Java class that implements a particular interface (see [24] for more details on the Genesys Code Generator Generator and the jABC Plugin's architecture).…”

Section: Testing On Multiple Meta-levelsmentioning

confidence: 99%

Back-To-Back Testing of Model-Based Code Generators

Jörges

Steffen

2014

Leveraging Applications of Formal Methods, Verification and Validation. Technologies for Mastering Change

Self Cite

View full text Add to dashboard Cite

Abstract. In this paper, we present the testing approach of the Genesys code generator framework. The employed approach is based on back-toback-testing, which tests the translation performed by a code generator from a semantic perspective rather than just checking for syntactic correctness of the generation result. We describe the basic testing framework and show that it scales in three dimensions: parameterized tests, testing across multiple target platforms and testing on multiple meta-levels.In particular, the latter is only possible due to the fact that Genesys code generators are constructed as models. Furthermore, in order to facilitate simplicity, Genesys consistently employs one single notation for all artifacts involved in this testing approach: Test data, test cases, the code generators under test, and even the testing framework itself are all modeled using the same graphical modeling language.

show abstract

“…Naujokat et al discussed the advantages of using the jABC framework for plug‐in development. The jABC, which is a graph‐drawing plug‐in framework, has been evolving during the last 10 years.…”

Section: About This Special Issuementioning

confidence: 99%

Developing tools as plug‐ins: TOPI 2012 special issue

Garbervetsky¹,

Kim

2014

Softw Pract Exp

View full text Add to dashboard Cite

SUMMARYOur knowledge as to how to solve software engineering problems is increasingly being encapsulated in tools. These tools are at their strongest when they operate in a preexisting development that can provide integration with existing elements such as compilers, debuggers, profilers, and visualizers as well as numerous other development and, often, runtime tools. However, building tools as plug-ins can be challenging and raise many questions: How do they interact with the core environment? How do they interact with other existing plug-ins, especially as each developer may choose a different set of plug-ins. How can we share tools across different and future core development environments? How do we evaluate the usefulness of the tools? The series of workshops on Developing Tools as Plug-ins (TOPI) tries to address these questions. ABOUT THIS SPECIAL ISSUEThe International Workshop on Developing Tools as Plug-Ins (TOPI) is a venue for researchers and practitioners interested in plug-in development. The main interest is understanding the opportunities and challenges of developing tools as plug-ins, and thus, we seek for discussions regarding the characteristics of good plug-ins, interoperability requirements to making tools available across platforms, recent successful tools as plug-ins, and foreseen medium-term and long-term challenges of tools as plug-ins.The 2nd Workshop on Tools as Plug-ins (TOPI 2012) [1] was held in Zurich, Switzerland on June 3, 2012. We received 32 submissions from authors of 17 different countries. These papers were reviewed by at least three members of our program committee, composed by 13 experts from academia and industry. After the reviewing process, we ended up accepting 14 submissions as full papers and four as short papers. The short papers had to present their work during a demo session.In addition, the authors of accepted full papers who presented concrete plug-ins or tools were also invited to showcase them during the demo session. The final program comprised position papers, including new proposals for plug-in-aware architectures, discussions about plug-in ecosystems, and interaction with their development environments and runtimes. We also accepted papers explaining the design and implementation of different kind of tools as plug-ins.

show abstract

Simplicity‐first model‐based plug‐in development

Cited by 11 publications

References 29 publications

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

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

Back-To-Back Testing of Model-Based Code Generators

Developing tools as plug‐ins: TOPI 2012 special issue

Contact Info

Product

Resources

About