1011121314151613 of 18
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Combining User Feedback and Monitoring Data to Support Evidence-based Software Evolution
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.
2020 (English)Doctoral thesis, comprehensive summary (Other academic)
Place, publisher, year, edition, pages
Karlskrona: Blekinge Tekniska Högskola, 2020.
Series
Blekinge Institute of Technology Doctoral Dissertation Series, ISSN 1653-2090 ; 4
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-19397ISBN: 978-91-7295-402-1 (print)OAI: oai:DiVA.org:bth-19397DiVA, id: diva2:1427500
Supervisors
Available from: 2020-04-30 Created: 2020-04-29 Last updated: 2020-05-19Bibliographically approved
List of papers
1. How do Users Characterise Feedback Features of an Embedded Feedback Channel?
Open this publication in new window or tab >>How do Users Characterise Feedback Features of an Embedded Feedback Channel?
Show others...
2020 (English)In: Article in journal (Refereed) Submitted
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-19475 (URN)
Available from: 2020-05-18 Created: 2020-05-18 Last updated: 2020-05-19Bibliographically approved
2. The effect of requests for user feedback on Quality of Experience
Open this publication in new window or tab >>The effect of requests for user feedback on Quality of Experience
2018 (English)In: Software quality journal, ISSN 0963-9314, E-ISSN 1573-1367, Vol. 26, no 2, p. 385-415Article in journal (Refereed) Published
Abstract [en]

Companies are interested in knowing how users experience and perceive their products. Quality of Experience (QoE) is a measurement that is used to assess the degree of delight or annoyance in experiencing a software product. To assess QoE, we have used a feedback tool integrated into a software product to ask users about their QoE ratings and to obtain information about their rationales for good or bad QoEs. It is known that requests for feedback may disturb users; however, little is known about the subjective reasoning behind this disturbance or about whether this disturbance negatively affects the QoE of the software product for which the feedback is sought. In this paper, we present a mixed qualitative-quantitative study with 35 subjects that explore the relationship between feedback requests and QoE. The subjects experienced a requirement-modeling mobile product, which was integrated with a feedback tool. During and at the end of the experience, we collected the users' perceptions of the product and the feedback requests. Based on the users' rational for being disturbed by the feedback requests, such as "early feedback," "interruptive requests," "frequent requests," and "apparently inappropriate content," we modeled feedback requests. The model defines feedback requests using a set of five-tuple variables: "task," "timing" of the task for issuing the feedback requests, user's "expertise-phase" with the product, the "frequency" of feedback requests about the task, and the "content" of the feedback request. Configuration of these parameters might drive the participants' perceived disturbances. We also found that the disturbances generated by triggering user feedback requests have negligible impacts on the QoE of software products. These results imply that software product vendors may trust users' feedback even when the feedback requests disturb the users.

Place, publisher, year, edition, pages
SPRINGER, 2018
Keywords
Quality of experience, QoE, User feedback, User perception, Human factors
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-16526 (URN)10.1007/s11219-017-9373-7 (DOI)000433521200007 ()
Available from: 2018-06-18 Created: 2018-06-18 Last updated: 2020-05-18Bibliographically approved
3. KPIs for software ecosystems: A systematic mapping study
Open this publication in new window or tab >>KPIs for software ecosystems: A systematic mapping study
2014 (English)In: Software Business: Towards Continuous Value Delivery, Springer, 2014Conference paper, Published paper (Refereed)
Abstract [en]

To create value with a software ecosystem (SECO), a platform owner has to ensure that the SECO is healthy and sustainable. Key Performance Indicators (KPI) are used to assess whether and how well such objectives are met and what the platform owner can do to improve. This paper gives an overview of existing research on KPI-based SECO assessment using a systematic mapping of research publications. The study identified 34 relevant publications for which KPI research and KPI practice were extracted and mapped. It describes the strengths and gaps of the research published so far, and describes what KPI are measured, analyzed, and used for decision-making from the researcher's point of view. For the researcher, the maps thus capture stateof- knowledge and can be used to plan further research. For practitioners, the generated map points to studies that describe how to use KPI for managing of a SECO.

Place, publisher, year, edition, pages
Springer, 2014
Series
Lecture Notes in Business Information Processing, ISSN 1865-1348 ; 182
Keywords
Digital ecosystem, KPI, PerDigital ecosystem, KPI, Performance indicator, Software ecosystem, Success factor, Systematic mappingformance indicator, Software ecosystem, Success factor, Systematic mapping
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-6340 (URN)10.1007/978-3-319-08738-2 (DOI)000348362700016 ()9783319087382 (ISBN)
Conference
International Conference on Software International Conference on Software Business (ICSOB), Paphos, Cyprus
Available from: 2015-05-26 Created: 2014-11-24 Last updated: 2020-05-18Bibliographically approved
4. Software analytics for planning product evolution
Open this publication in new window or tab >>Software analytics for planning product evolution
2016 (English)In: Lecture Notes in Business Information Processing, Springer, 2016, Vol. 240, p. 16-31Conference paper, Published paper (Refereed)
Abstract [en]

Evolution of a software product is inevitable as product context changes and the product gradually becomes less useful if it is not adapted. Planning is a basis to evolve a software product. The product manager, who carries responsibilities of planning, requires but does not always have access to high-quality information for making the best possible planning decisions. The current study aims to understand whether and when analytics are valuable for product planning and how they can be interpreted to a software product plan. The study was designed with an interview-based survey methodology approach through 17 in-depth semi-structured interviews with product managers. Based on results from qualitative analysis of the interviews, we defined an analytics-based model. The model shows that analytics have potentials to support the interpretation of product goals while is constrained by both product characteristics and product goals. The model implies how to use analytics for a good support of product planning evolution.

Place, publisher, year, edition, pages
Springer, 2016
Series
Lecture Notes in Business Information Processing, ISSN 1865-1348 ; 240
Keywords
Data processing, High quality information; Product characteristics; Product evolution; Product planning; Qualitative analysis; Semi structured interviews; Software products; Survey methodology, Managers
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-13226 (URN)10.1007/978-3-319-40515-5_2 (DOI)000387544500002 ()2-s2.0-84976648991 (Scopus ID)978-3-319-40515-5 (ISBN)
Conference
7th International Conference on Software Business (ICSOB), Ljubljana
Available from: 2016-10-03 Created: 2016-10-03 Last updated: 2020-05-18Bibliographically approved
5. Quality Requirements Elicitation based on Inquiry of Quality-Impact Relationships
Open this publication in new window or tab >>Quality Requirements Elicitation based on Inquiry of Quality-Impact Relationships
2014 (English)In: Proceedings of International Requirements Engineering, IEEE , 2014, p. 303-312Conference paper, Published paper (Refereed)
Abstract [en]

Quality requirements, an important class of non functional requirements, are inherently difficult to elicit. Particularly challenging is the definition of good-enough quality. The problem cannot be avoided though, because hitting the right quality level is critical. Too little quality leads to churn for the software product. Excessive quality generates unnecessary cost and drains the resources of the operating platform. To address this problem, we propose to elicit the specific relationships between software quality levels and their impacts for given quality attributes and stakeholders. An understanding of each such relationship can then be used to specify the right level of quality by deciding about acceptable impacts. The quality-impact relationships can be used to design and dimension a software system appropriately and, in a second step, to develop service level agreements that allow re-use of the obtained knowledge of good-enough quality. This paper describes an approach to elicit such quality-impact relationships and to use them for specifying quality requirements. The approach has been applied with user representatives in requirements workshops and used for determining Quality of Service (QoS) requirements based the involved users’ Quality of Experience (QoE). The paper describes the approach in detail and reports early experiences from applying the approach. Index Terms-Requirement elicitation, quality attributes, non-functional requirements, quality of experience (QoE), quality of service (QoS).

Place, publisher, year, edition, pages
IEEE, 2014
Series
Proceedings of International Requirements Engineering, ISSN 1097-0592
Keywords
Quality Requirements Elicitation, Quality-Impact Relationships
National Category
Telecommunications Software Engineering Business Administration
Identifiers
urn:nbn:se:bth-6515 (URN)10.1109/RE.2014.6912272 (DOI)000363280400031 ()978-1-4799-3031-9 (ISBN)
Conference
22nd IEEE International Requirements Engineering Conference, Karlskrona
Available from: 2014-12-02 Created: 2014-12-01 Last updated: 2020-05-18Bibliographically approved
6. FAME: Supporting continuous requirements elicitation by combining user feedback and monitoring
Open this publication in new window or tab >>FAME: Supporting continuous requirements elicitation by combining user feedback and monitoring
Show others...
2018 (English)In: Proceedings - 2018 IEEE 26th International Requirements Engineering Conference, RE 2018, Institute of Electrical and Electronics Engineers Inc. , 2018, p. 217-227Conference paper, Published paper (Refereed)
Abstract [en]

Context: Software evolution ensures that software systems in use stay up to date and provide value for end-users. However, it is challenging for requirements engineers to continuously elicit needs for systems used by heterogeneous end-users who are out of organisational reach. Objective: We aim at supporting continuous requirements elicitation by combining user feedback and usage monitoring. Online feedback mechanisms enable end-users to remotely communicate problems, experiences, and opinions, while monitoring provides valuable information about runtime events. It is argued that bringing both information sources together can help requirements engineers to understand end-user needs better. Method/Tool: We present FAME, a framework for the combined and simultaneous collection of feedback and monitoring data in web and mobile contexts to support continuous requirements elicitation. In addition to a detailed discussion of our technical solution, we present the first evidence that FAME can be successfully introduced in real-world contexts. Therefore, we deployed FAME in a web application of a German small and medium-sized enterprise (SME) to collect user feedback and usage data. Results/Conclusion: Our results suggest that FAME not only can be successfully used in industrial environments but that bringing feedback and monitoring data together helps the SME to improve their understanding of end-user needs, ultimately supporting continuous requirements elicitation. © 2018 IEEE.

Place, publisher, year, edition, pages
Institute of Electrical and Electronics Engineers Inc., 2018
Keywords
Data collection, Feedback acquisition, Feedback gathering, Requirements, Requirements elicitation, Software evolution, Usage monitoring, User feedback, User involvement, Human computer interaction, Requirements engineering, Monitoring
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-17412 (URN)10.1109/RE.2018.00030 (DOI)2-s2.0-85056819919 (Scopus ID)9781538674185 (ISBN)
Conference
26th IEEE International Requirements Engineering Conference, RE 2018, Banff, Canada, 20 August 2018 through 24 August 2018
Available from: 2018-12-13 Created: 2018-12-13 Last updated: 2020-05-18Bibliographically approved
7. A Method for Gathering Evidence from Software in Use to Support Software Evolution
Open this publication in new window or tab >>A Method for Gathering Evidence from Software in Use to Support Software Evolution
2020 (English)In: Journal of Empirical Software Engineering, ISSN 1382-3256, E-ISSN 1573-7616Article in journal (Refereed) Submitted
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-19474 (URN)
Available from: 2020-05-18 Created: 2020-05-18 Last updated: 2020-05-19Bibliographically approved

Open Access in DiVA

fulltext(4571 kB)20 downloads
File information
File name FULLTEXT03.pdfFile size 4571 kBChecksum SHA-512
355e78447d974bebb87453545d4c5d1b48c7c8cab3ae06b9bc0c5e991f7ebe63022c28057eec0f84173d5f3f70fc7e9cb5d19adb71ef3415ed0c8a0f24f63b48
Type fulltextMimetype application/pdf

Authority records BETA

Fotrousi, Farnaz

Search in DiVA

By author/editor
Fotrousi, Farnaz
By organisation
Department of Software Engineering
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar
Total: 22 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

isbn
urn-nbn

Altmetric score

isbn
urn-nbn
Total: 210 hits
1011121314151613 of 18
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf