TY - GEN
T1 - User interface engineering for software product lines: the dilemma between automation and usability
AU - Pleuss, Andreas
AU - Hauptmann, Benedikt
AU - Dhungana, Deepak
AU - Botterweck, Goetz
N1 - DBLP License: DBLP's bibliographic metadata records provided through http://dblp.org/ are distributed under a Creative Commons CC0 1.0 Universal Public Domain Dedication. Although the bibliographic metadata records are provided consistent with CC0 1.0 Dedication, the content described by the metadata records is not. Content may be subject to copyright, rights of privacy, rights of publicity and other restrictions.
PY - 2012/6/25
Y1 - 2012/6/25
N2 - 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.
AB - 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.
KW - Computer systems
KW - Concrete products
KW - Usability engineering
KW - Feature models
KW - High quality
KW - Interactive applications
KW - Interface engineering
KW - Model driven development
KW - Product derivation
KW - Product families
KW - Software Product Line
KW - Software product lines
KW - Software products
KW - User interfaces
KW - User interface engineering
KW - Model-driven development
UR - http://www.scopus.com/inward/record.url?scp=84864048375&partnerID=8YFLogxK
U2 - 10.1145/2305484.2305491
DO - 10.1145/2305484.2305491
M3 - Conference contribution
SN - 9781450311687
T3 - EICS'12 - Proceedings of the 2012 ACM SIGCHI Symposium on Engineering Interactive Computing Systems
SP - 25
EP - 34
BT - EICS'12 - Proceedings of the 2012 ACM SIGCHI Symposium on Engineering Interactive Computing Systems
PB - ACM
ER -