MétaCan
Menu
Back to cohort
Record W2593015694

Downsizing EPMcreate to Lighter Creativity Techniques for Requirements Elicitation.

2017· article· en· W2593015694 on OpenAlexfundno aff
Luisa Mich, Victoria Sakhnini, Daniel M. Berry

Bibliographic record

VenueInstitutional Research Information System (Università degli Studi di Trento) · 2017
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsnot available
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsRequirements elicitationCreativityPhoto elicitationComputer scienceEngineeringRequirements analysisKnowledge managementPsychologySoftwareSocial psychology
DOInot available

Abstract

fetched live from OpenAlex

EPMcreate is a creativity technique for requirements elicitation based on a 16-step process. These steps suggest focusing on requirements related to every combination of two different target users or viewpoints. A series of experiments confirmed its feasibility; its applicability, both as individual and group technique; and its greater effectiveness than brainstorming. However, analysts involved in some of the experiments highlighted the large number of steps as a limitation of the technique. Recent experiments tested a variant of the EPMcreate, named Power-Only EPMcreate, based on 4 of the 16 steps. The experiments showed that it works better than EPMcreate for at least website requirements. Nevertheless, the question of whether any other combination of the steps of the original technique could work is still open. This paper illustrates a number of criteria for generating lighter creativity techniques, each based on a subset of the 16 steps of EPMcreate.

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 machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.011
metaresearch head score (Gemma)0.054
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.011
Threshold uncertainty score0.058

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0110.054
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0030.002
Science and technology studies0.0010.002
Scholarly communication0.0020.003
Open science0.0020.005
Research integrity0.0010.003
Insufficient payload (model declined to judge)0.0040.001

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.150
GPT teacher head0.401
Teacher spread0.250 · 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 source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
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

Citations2
Published2017
Admission routes1
Has abstractyes

Explore more

Same venueInstitutional Research Information System (Università degli Studi di Trento)Same topicSoftware Engineering Techniques and PracticesFrench-language works237,207