MétaCan
Menu
Back to cohort
Record W2295659559

An Initial Approach to Reuse Non-Functional Requirements Knowledge

2015· article· en· W2295659559 on OpenAlexaff
Rodrigo Veleda, Luiz Marcio Cysneiros

Bibliographic record

VenueiStar · 2015
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsYork University
Fundersnot available
KeywordsComputer scienceNon-functional requirementReuseInterdependenceSoftware engineeringFunctional requirementSoftwareRisk analysis (engineering)Data miningSoftware developmentProgramming languageEngineering
DOInot available

Abstract

fetched live from OpenAlex

Non-Functional Requirements (NFR) can be seen as qualities that software should deliver to cope with the stakeholders' demands. NFRs are fuzzy in nature and hence hard to identify. Despite the fact that both developers and users may value NFRs, they frequently do not identify the need for an NFR. Even when an NFR is identified as required, possible solutions to implement this NFR may be hard to fig- ure out. Furthermore, interdependencies among NFRs may implicate that a solution for one NFR may, at the same time, bring synergy to one NFR while conflicting with another. One approach to deal with that is to use Softgoal Interdependency Graphs (SIG) to capture knowledge describing alternatives to implement NFRs. We have ob- tained empirical evidence that using catalogues can help eliciting NFRs despite the fact that catalogues do not scale too well. To address this question, we have investi- gated the use of ontologies and semantic web techniques to represent SIGs in a ma- chine readable format. We have produced a tool (NDR) that starts to use these con- cepts. In its current form, the NDR tool only allows very basic queries done manual- ly. The NDR tool is part of the NDR framework which will facilitate the reuse of NFR knowledge on Alternatives to incorporate NFRs into the design of target sys-

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.017
metaresearch head score (Gemma)0.051
Version: metacan-v3-hybrid-931329e0061cValidation 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: Empirical · Consensus signal: none
Teacher disagreement score0.017
Threshold uncertainty score0.088

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0170.051
Meta-epidemiology (narrow)0.0030.003
Meta-epidemiology (broad)0.0020.006
Bibliometrics0.0100.006
Science and technology studies0.0030.004
Scholarly communication0.0100.013
Open science0.0070.010
Research integrity0.0050.008
Insufficient payload (model declined to judge)0.0120.006

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.205
GPT teacher head0.382
Teacher spread0.178 · 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 designTheoretical or conceptual
Domainnot available
GenreEmpirical

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

Citations3
Published2015
Admission routes1
Has abstractyes

Explore more

Same venueiStarSame topicAdvanced Software Engineering MethodologiesFrench-language works237,207