MétaCan
Menu
Back to cohort

Acquiring Testable NFRs Utilizing Goal Models Enhancing Application Requirements Analysis in Goal-Driven Software Product Lines

2023· article· en· W4389880439 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
TopicAdvanced Software Engineering Methodologies
Canadian institutionsUniversity of FrederictonUniversity of New Brunswick
Fundersnot available
KeywordsFunctional requirementNon-functional requirementComputer scienceRequirement prioritizationNon-functional testingSoftware product lineRequirementSoftware engineeringRequirements analysisSoftware developmentFunctional specificationSystems engineeringTraceabilitySoftware requirements specificationReliability engineeringRisk analysis (engineering)SoftwareSoftware constructionEngineering

Abstract

fetched live from OpenAlex

Software product line engineering involves reusing development assets to create a family of software systems with common features and few specific differences. Testing is crucial for evaluating software quality, encompassing both functional and non-functional requirements. However, non-functional requirements (NFRs) are often neglected in software product lines, with a primary focus on functional requirements during system configuration. This paper addresses the significance of early testing and the challenges of testing non-functional properties in software product lines. To ensure effective testing of non-functional aspects, clear and testable specifications for non-functional requirements are essential. Current practices often leave non-functional requirements unaddressed until system testing, lacking proper traceability and management. Additionally, systematic approaches are lacking to support non-functional requirements from the early stages of development, hindering their integration into product line development. In this research, we propose an approach that utilizes goal models to enhance application requirements analysis in goal-driven software product lines. By incorporating goal models, our approach enables the acquisition of testable non-functional requirements during the early stages of development. Our approach aims to improve the effectiveness and efficiency of testing non-functional properties and align them with the specified goals.

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.001
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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.342
Threshold uncertainty score0.962

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.005
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0010.001
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.065
GPT teacher head0.327
Teacher spread0.262 · 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