A practical high volume software product line
Companion to the 22nd ACM SIGPLAN conference on Object-oriented programming systems and applications companion
Rapid UI development for enterprise applications: combining manual and model-driven techniques
MODELS'10 Proceedings of the 13th international conference on Model driven engineering languages and systems: Part I
Variability issues in the evolution of information system ecosystems
Proceedings of the 5th Workshop on Variability Modeling of Software-Intensive Systems
Model-Driven Development of Advanced User Interfaces
Model-Driven Development of Advanced User Interfaces
User interface engineering for software product lines: the dilemma between automation and usability
Proceedings of the 4th ACM SIGCHI symposium on Engineering interactive computing systems
Model-driven development and evolution of customized user interfaces
Proceedings of the 5th ACM SIGCHI symposium on Engineering interactive computing systems
Using document-oriented GUIs in dynamic software product lines
Proceedings of the 12th international conference on Generative programming: concepts & experiences
Managing the evolution and customization of database schemas in information system ecosystems
CAiSE'13 Proceedings of the 25th international conference on Advanced Information Systems Engineering
| Hi-index | 0.00 |
Software Product Lines (SPL) enable efficient derivation of products. SPL concepts have been applied successfully in many domains including interactive applications. However, the user interface (UI) part of applications has barely been addressed yet. While standard SPL concepts allow derivation of functionally correct UIs, there are additional non-functional requirements, like usability, which have to be considered. This paper presents a case study investigating UI variability found in variants of the commercial web-based information system HIS-GX/QIS. We analyze which aspects of a UI vary and to which degree. The results show that just tweaking the final UI (e.g., using stylesheets) is not sufficient but there is a need for more customization which must be supported by, e.g., UI-specific models.