MétaCan
Menu
Back to cohort
Record W4387124006 · doi:10.1109/re57278.2023.00060

Leveraging User Feedback for Requirements Through Trend and Narrative Analysis

2023· article· en· W4387124006 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicOpen Source Software Innovations
Canadian institutionsUniversity of Victoria
Fundersnot available
KeywordsNarrativeComputer scienceUser storyLeverage (statistics)PerceptionWork (physics)User requirements documentPlan (archaeology)Knowledge managementData scienceSoftwareSoftware developmentEngineeringPsychology

Abstract

fetched live from OpenAlex

With the rapid rise of new mediums and surge of user discussion regarding software products, it is increasingly important to consider these user concerns to fulfill user needs, otherwise users may opt for alternatives. Traditional requirements elicitation approaches relied on interviews and surveys with stakeholders to elicit key and important requirements. Despite the advances from recent studies to leverage the “crowd” via increased involvement of crowd based discussions, we still lack empirical structured guidance and approaches to handle feedback from multiple sources and synthesize the themes that emerge from these sources. As providing feedback becomes more accessible for users, managing the volume of feedback is correspondingly challenging. Since development resources are often limited, organizations need to make trade-offs between different user concerns. Gaining more insights on the themes and the trends of these themes from feedback should help organizations conduct these requirement trade-offs. To better explain the emergent trends of user feedback, I use the concept of narratives from economics to explain the phenomenon of what and when users change in their user discussions. Narrative analysis can help explain the causes of feedback trends, which can support organizations determining the priority and validity of various themes from feedback. In this work, I describe my preliminary findings which indicate the profound role that trends and narratives in user feedback have on user perception and concerns. My work has shown that feedback sources, like social media, can provide an avenue to identify requirements. Finally, I outline my plan towards developing a framework to identify trends and narratives, and a tool to support automated identification of requirements in the form of user stories.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.698
Threshold uncertainty score0.346

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.003
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.070
GPT teacher head0.336
Teacher spread0.266 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Quick stats

Citations0
Published2023
Admission routes1
Has abstractyes

Explore more

Same topicOpen Source Software InnovationsFrench-language works237,207