On the Role of User Feedback in Software Evolution: a Practitioners’ Perspective

Author(s):  
Simon van Oordt ◽  
Emitza Guzman
2020 ◽  
Vol 20 (2) ◽  
pp. 171-175
Author(s):  
Amanat Moldokeeva ◽  
◽  
Aliya Asanbekova ◽  

Today’s most successful companies are committed to understanding the desired outcomes of their customers, and they’re designing experiences to help their customers achieve those outcomes. In other words, they’re focused on customer success. Most of companies in developed countries are understanding importance of Customer success methodology. Their experience could be useful for Kyrgyzstan market also. CSM is a customer representative in a company. Success Manager works ahead to prevent user problems. And its main goal is to show the value of the product to the client and transfer user feedback to the development and product teams.


2019 ◽  
Vol 18 (01) ◽  
pp. A03 ◽  
Author(s):  
Ulrike Sturm ◽  
Martin Tscholl

In citizen science, user-centred development is often emphasised for its potential to involve participants in the development of technology. We describe the development process of the mobile app “Naturblick” as an example of a user-centred design in citizen science and discuss digital user feedback with regard to the users' involvement. We have identified three types of digital user feedback using qualitative content analysis: general user feedback, contributory user feedback and co-creational user feedback. The results indicate that digital user feedback can link UCD techniques with more participatory design approaches.


2022 ◽  
Vol 40 (3) ◽  
pp. 1-47
Author(s):  
Ameer Albahem ◽  
Damiano Spina ◽  
Falk Scholer ◽  
Lawrence Cavedon

In many search scenarios, such as exploratory, comparative, or survey-oriented search, users interact with dynamic search systems to satisfy multi-aspect information needs. These systems utilize different dynamic approaches that exploit various user feedback granularity types. Although studies have provided insights about the role of many components of these systems, they used black-box and isolated experimental setups. Therefore, the effects of these components or their interactions are still not well understood. We address this by following a methodology based on Analysis of Variance (ANOVA). We built a Grid Of Points that consists of systems based on different ways to instantiate three components: initial rankers, dynamic rerankers, and user feedback granularity. Using evaluation scores based on the TREC Dynamic Domain collections, we built several ANOVA models to estimate the effects. We found that (i) although all components significantly affect search effectiveness, the initial ranker has the largest effective size, (ii) the effect sizes of these components vary based on the length of the search session and the used effectiveness metric, and (iii) initial rankers and dynamic rerankers have more prominent effects than user feedback granularity. To improve effectiveness, we recommend improving the quality of initial rankers and dynamic rerankers. This does not require eliciting detailed user feedback, which might be expensive or invasive.


Author(s):  
Randeep Singh ◽  
Amit Bindal ◽  
Ashok Kumar

Code smells are the fragments in the source code that indicates deeper problems in the underlying software design. These code smells can hinder software evolution and maintenance. Out of different code smell types, the God Class (GC) code smell is one of the many important code smells that directly affects the software evolution and maintenance. The GC is commonly defined as a much larger class in systems that either know too much or do too much as compared to other classes in the system. God Classes are generally accidentally created overtime during software evolution because of the incremental addition of functionalities to it. Generally, a GC indicates a bad design choice and it must be detected and mitigated in order to enhance the quality of the underlying software. However, sometimes the presence of a GC is also considered a good design choice, especially in compiler design, interpreter design and parser implementation. This makes the developer’s feedback important for the correct classification of a class as a GC or a normal class. Therefore, this paper proposes a new approach that detects and proposes refactoring opportunities for GC code smell. The proposed approach makes use of different code metrics in combination along with utilizing user feedback as an important aspect while correctly identifying the GC code smell. The proposed approach that considers combined use of code metrics, is based on two newly proposed code metrics in this paper. The first newly proposed metric is a new approach of measuring the connectivity of a given class with other classes in the system (also termed as coupling). The second newly proposed code metric is proposed to measure the extent to which a given classes make use of foreign member variables. Finally, the proposed approach is also empirically evaluated on two standard open-source commonly used software systems. The obtained result indicates that the proposed approach is capable of correctly identifying the GC code smell.


2020 ◽  
Vol 13 (3) ◽  
pp. 16
Author(s):  
M.Redwan aljannan ◽  
Manal A. Ismail ◽  
Akram Salah

End-user feedback has an essential role in the requirement’s identification, prioritization, and management of the software evolution process. Several approaches are proposed for utilizing user-pushed feedback collected from social media, forums, and review systems. The collected feedback via the online channels contains a variety of information. Thus, the researchers proposed analytical approaches to classify feedback according to the data it holds. Still, recent results indicate that no single classifier works best for all feedback types and information sources. Also, online feedback does not have a direct mapping to the requirements, and it does not contain user context data. This causes wasting in developers’ effort in understanding and analyzing feedback. On the other hand, online feedback cannot be used to explore user satisfaction and acceptance of the implemented and planned requirements. Likewise, the developer cannot collect feedback from a specific segment of the users. To overcome the deficiency of online feedback, this paper proposes a novel approach that utilizes pulling feedback from users while using the software. The proposed approach consists of a model and process for structuring feedback requests, linking feedback to the requirements, embedding feedback with the user context information, specifying the target audience for the feedback request, analyzing collected feedback depending on predefined interpretation rules, which provide insights that support developers in release planning. The feedback request model and process are implemented by a tool called FeatureEcho which was evaluated in a software company by conducting a case study for upgrading a governmental internet portal. The results indicate that FeatureEcho is a valuable step towards increasing the understanding of the end-users needs which supports the decision-making procedure of software evolution.


Sign in / Sign up

Export Citation Format

Share Document