Simplicity principles for plug-in development: The jABC approach

Naujokat, Stefan; Lamprecht,; Steffen,; Jorges,; Margaria, Tiziana

doi:10.1109/topi.2012.6229816

Cited by 7 publications

(6 citation statements)

References 27 publications

(24 reference statements)

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

“…For example, additional SIBs can be added to the current modeling project, which introduces additional user interface elements and only works if the files containing additional SIB libraries are located within the project structure. Additionally, jABC can be extended with completely new modules by means of "plugins" (Naujokat, Lamprecht, Steffen, Jörges, & Margaria, 2012). Files containing plugins again have to be placed in special locations and furthermore have to be "registered" in a configuration dialog, necessitating an application restart.…”

Section: Adding Complexity Only Where Neededmentioning

confidence: 99%

Simplicity Driven Application Development

Merten

Steffen

2013

Journal of Integrated Design and Process Science

Self Cite

View full text Add to dashboard Cite

In this article we discuss a simplicity-oriented approach to application development along a case study for engineering a web platform for orchestrating predefined service modules. Focus here is the growing demand for agility: 1) earlier solutions typically economically outperform later, more mature solutions, and 2) the half-value times of applications are drastically shrinking. Our simplicity-oriented approach therefore addresses both, the ease of application development, exploiting the so-called 80/20 principle, and the ease of take-up, aiming at removing potential hurdles for user adoption. We will discuss how this reflects on design decisions, in particular concerning the sweet spot where to change from adopting and adapting existing software to custom development.

show abstract

“…E.g., Lamprecht et al reflect over some simplicity principles elicited by many years' experience in plug-in development [12], but do not provide a methodology. We speculate that there is not much published work because plug-in development was not the focus of scientists until recently.…”

Section: Related Workmentioning

confidence: 99%

A rigorous methodology for analyzing and designing plug-ins

Fasie

Haxthausen

Kiniry

2013

2013 3rd International Workshop on Developing Tools as Plug-Ins (TOPI)

View full text Add to dashboard Cite

Abstract-Today, GUI plug-ins development is typically done in a very ad-hoc way, where developers dive directly into implementation. Without any prior analysis and design, plugins are often flaky, unreliable, difficult to maintain and extend with new functionality, and have inconsistent user interfaces. This paper addresses these problems by describing a rigorous methodology for analyzing and designing plug-ins. The methodology is grounded in the Extended Business Object Notation (EBON) and covers informal analysis and design of features, GUI, actions, and scenarios, formal architecture design, including behavioral semantics, and validation. The methodology is illustrated via a case study whose focus is an Eclipse environment for the RAISE formal method's tool suite.

show abstract

Simplicity principles for plug-in development: The jABC approach

Cited by 7 publications

References 27 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

Simplicity Driven Application Development

A rigorous methodology for analyzing and designing plug-ins

Contact Info

Product

Resources

About