Variability issues in the evolution of information system ecosystems

Brummermann, Hendrik; Keunecke, Markus; Schmid, Klaus

doi:10.1145/1944892.1944912

Cited by 18 publications

(22 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…However, in practice, UIs sometimes require manual customization for two reasons [18]: First, for usability reasons. For instance, automatic distribution of UI elements onto presentation units (e.g., screens) is sometimes difficult and can lead to overfull or too empty presentation units [5]. Second, there can be very specific customer requirements beyond generic rules.…”

Section: Ui Customization Within Mddmentioning

confidence: 99%

Model-driven development and evolution of customized user interfaces

Pleuss

Wollny

Botterweck

2013

Proceedings of the 5th ACM SIGCHI Symposium on Engineering Interactive Computing Systems

View full text Add to dashboard Cite

One of the main benefits of model-driven development of User Interfaces (UIs) is the increase in efficiency and consistency when developing multiple variants of a UI. For instance, multiple UIs for different target users, platforms, devices, or for whole product families can be generated from the same abstract models. However, purely generated UIs are not always sufficient as there is often need for customizing the individual UI variants, e.g., due to usability issues or specific customer requirements.In this paper we present a model-driven approach for the development of UI families with systematic support for customizations. The approach supports customizing all aspects of a UI (UI elements, screens, navigation, etc.) and storing the customizations in specific models. As a result, a UI family can be evolved more efficiently because individual UI variants can be re-generated (after some changes have been applied to the family) without losing any previously made customizations. We demonstrate this by thirty highly customized real-world products from a commercial family of web information systems called HIS-GX/QIS.

show abstract

Section: Ui Customization Within Mddmentioning

confidence: 99%

Model-driven development and evolution of customized user interfaces

Pleuss

Wollny

Botterweck

2013

Proceedings of the 5th ACM SIGCHI Symposium on Engineering Interactive Computing Systems

View full text Add to dashboard Cite

show abstract

“…There are two experience reports from in- dustry that mention the UI aspect and which we hence use for our discussion: [2] presents the experience from a company called SystemForge with their model-driven SPL for online shops for small and medium businesses. In [4], the company HIS reports on challenges arising with their product HISinOne, a web-based university management software supporting, e.g., management of students, human resources, and financial accounting. HISinOne is not a SPL in the strict sense (i.e., there is no SPL approach fully applied) but is still a highly variable ecosystem providing different customized products for their customers.…”

Section: The Dilemma Between Automation and Usability -Solution Altermentioning

confidence: 99%

“…For the UI this can mean that usability issues arise after automated product derivation. For instance, removing elements from a screen (as in negative variability) can lead to screens which are almost empty and are no longer useful as screens of their own [4]. To some extent this might be addressed by additional rules or heuristics during the product derivation, e.g., that a screen with very few content is merged with other screens.…”

Section: On the Need For Ui Customizationmentioning

confidence: 99%

“…While this works well for deriving most parts of the product implementation [8,24,25], it has limitations for the product's user interface (UI) part: A high quality UI must not only adhere to certain functionality defined by a product configuration (e.g., the presence or absence of UI elements) but also meet usability requirements like adequate layout, composition into screens, and choice of UI element types. This requires to customize the UI beyond purely automated derivation [15,4]. A simple solution is to design the UI manually for each product [2].…”

Section: Introductionmentioning

confidence: 99%

“…A simple solution is to design the UI manually for each product [2]. However, as practice shows, this can result in serious drawbacks regarding error rate and maintenance [4]. This paper investigates these problems based on real-world examples and analyses the development of product families from a UI perspective.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

User interface engineering for software product lines

Pleuss

Hauptmann

Dhungana

et al. 2012

Proceedings of the 4th ACM SIGCHI Symposium on Engineering Interactive Computing Systems

View full text Add to dashboard Cite

Software Product Lines (SPL) are systematic approach to develop families of similar software products by explicating their commonalities and variability, e.g., in a feature model. Using techniques from model-driven development, it is then possible to automatically derive a concrete product from a given configuration (i.e., selection of features). However, this is problematic for interactive applications with complex user interfaces (UIs) as automatically derived UIs often provide limited usability. Thus, in practice, the UI is mostly created manually for each product, which results in major drawbacks concerning efficiency and maintenance, e.g., when applying changes that affect the whole product family. This paper investigates these problems based on real-world examples and analyses the development of product families from a UI perspective. To address the underlying challenges, we propose the use of abstract UI models, as used in HCI, to bridge the gap between automated, traceable product derivation and customized, high quality user interfaces. We demonstrate the feasibility of the approach by a concrete example implementation for the suggested model-driven development process.

show abstract

Improving Software Engineering Research Through Experimentation Workbenches

Schmid¹,

El-Sharkawy²,

Kröher³

2019

From Software Engineering to Formal Methods and Tools, and Back

Self Cite

View full text Add to dashboard Cite

Experimentation with software prototypes plays a fundamental role in software engineering research. In contrast to many other scientific disciplines, however, explicit support for this key activity in software engineering is relatively small. While some approaches to improve this situation have been proposed by the software engineering community, experiments are still very difficult and sometimes impossible to replicate. In this paper, we propose the concept of an experimentation workbench as a means of explicit support for experimentation in software engineering research. In particular, we discuss core requirements that an experimentation workbench should satisfy in order to qualify as such and to offer a real benefit for researchers. Beyond their core benefits for experimentation, we stipulate that experimentation workbenches will also have benefits in regard to reproducibility and repeatability of software engineering research. Further, we illustrate this concept with a scenario and a case study, and describe relevant challenges as well as our experience with experimentation workbenches.

show abstract

Variability issues in the evolution of information system ecosystems

Cited by 18 publications

References 5 publications

Model-driven development and evolution of customized user interfaces

Model-driven development and evolution of customized user interfaces

User interface engineering for software product lines

Improving Software Engineering Research Through Experimentation Workbenches

Contact Info

Product

Resources

About