MétaCan
Menu
Back to cohort
Record W2060241165 · doi:10.1109/esem.2009.5316049

Does explanation improve the acceptance of decision support for product release planning?

2009· article· en· W2060241165 on OpenAlexaffabout
Gengshen Du, Guenther Ruhe

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsProduct (mathematics)Computer scienceEmpirical researchProduct planningNew product developmentDecision support systemKnowledge managementArtificial intelligenceMarketingMathematicsStatisticsBusiness

Abstract

fetched live from OpenAlex

Objective: Decision support provided to users is often lack of acceptance. One of the reasons is a deficit in understanding where the suggestions come from and how they come. This essentially is not a technical problem, but a technology adoption problem. This situation was also analyzed as a result of former empirical studies conducted on ReleasePlanner <sup xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">TM</sup> , a decision support tool for planning product releases. To overcome this situation, three machine learning techniques have been applied to mine the tool's solutions, and the mining results are presented to the tool users as explanations. This paper presents the evaluation on the generated explanations as a means to improve the user acceptance of the tool. Method: A three-stage controlled experiment was designed and carried out with a group of ten graduate students at the University of Calgary and another group of five project managers from the IT industry. Two research goals were addressed to (i) evaluate the impact of the explanations generated from these three applied techniques, and (ii) compare some of the findings from this study with the ones from our previous experiments. Results: Our findings for the first research goal indicated that the explanations generated from the three techniques contributed to the improvement of the subjects' confidence in the tool solutions and trust of the tool, and therefore an overall better user acceptance of the tool. Meanwhile, no significant differences were found among the impacts of the three techniques. For the second research goal, we found that some of the findings from this study were consistent with the ones from our previous experiments.

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.

How this classification was reachedexpand

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.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.952
Threshold uncertainty score0.143

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.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.016
GPT teacher head0.301
Teacher spread0.286 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designOther design
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations9
Published2009
Admission routes2
Has abstractyes

Explore more

Same topicSoftware Engineering ResearchFrench-language works237,207