MétaCan
Menu
Back to cohort
Record W2156479366 · doi:10.5555/2820668.2820675

Recommending features and feature relationships from requirements documents for software product lines

2015· article· en· W2156479366 on OpenAlexaff
Mostafa Hamza, Robert J. Walker

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsComputer scienceSoftware product lineSoftware engineeringFeature modelHeuristicsSoftwareCategorizationFeature (linguistics)Product (mathematics)Software requirements specificationSoftware systemSoftware developmentData miningSoftware constructionArtificial intelligenceProgramming language

Abstract

fetched live from OpenAlex

Feature models are a key element in software product lines, representing the supported features and their interrelationships within a family of software products. Recommendation systems for software engineering (RSSEs) are potentially useful in supporting the extraction, maintenance, and categorization of feature models. This paper focuses on the design and implementation of an RSSE to automatically recommend features for software product lines, the types of these features, and how they could be related to each other. Such a recommender should save time and tedium over doing the work manually. We present FFRE, a prototype recommendation tool for the extraction of features and their relationships from software requirements specification (SRS) documents. FFRE is based on natural language processing (NLP) techniques and heuristics. FFRE is evaluated qualitatively from four SRS documents and compared against other tools and approaches.

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.002
metaresearch head score (Gemma)0.021
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.009
Threshold uncertainty score0.019

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.021
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0060.003
Science and technology studies0.0010.000
Scholarly communication0.0010.002
Open science0.0010.000
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0040.002

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.156
GPT teacher head0.352
Teacher spread0.195 · 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 designSimulation or modeling
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

Citations15
Published2015
Admission routes1
Has abstractyes

Explore more

Same topicAdvanced Software Engineering MethodologiesFrench-language works237,207