An evaluation of a multiple interface design solution for bloated software
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Proceedings of the 20th annual international conference on Computer documentation
Rules and Tools for Software Evolution Planning and Management
Annals of Software Engineering
Functional Paleontology: The Evolution of User-Visible System Services
IEEE Transactions on Software Engineering
A comparison of static, adaptive, and adaptable menus
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Measuring the conceptual fitness of an application in a computing ecosystem
Proceedings of the 2004 ACM workshop on Interdisciplinary software engineering research
Analyzing software evolution through feature views: Research Articles
Journal of Software Maintenance and Evolution: Research and Practice
A field evaluation of an adaptable two-interface design for feature-rich software
ACM Transactions on Computer-Human Interaction (TOCHI)
Studying the evolution of the Eclipse Java editor
Proceedings of the 2007 OOPSLA workshop on eclipse technology eXchange
CASCON '09 Proceedings of the 2009 Conference of the Center for Advanced Studies on Collaborative Research
User acceptance of the microsoft Ribbon user interface
DNCOCO'10 Proceedings of the 9th WSEAS international conference on Data networks, communications, computers
Design and evaluation of a command recommendation system for software applications
ACM Transactions on Computer-Human Interaction (TOCHI)
AppMap: exploring user interface visualizations
Proceedings of Graphics Interface 2011
Hi-index | 0.00 |
The evolution and enhancement of features during system evolution can have significant effects on its coherence as well as its internal architecture. Studying the evolution of system features and concepts across a product line from an external or problem domain perspective can inform the process of identifying and designing future features. We show how we derive three primary views, morphological, functional, and an object view, from the user-level structures and operations of a system, using a case study of Microsoft Word's evolution. We show how these views illustrate feature evolution over three versions of Word. Lastly, we discuss the lessons learned from our study of feature evolution.