MétaCan
Menu
Back to cohort
Record W4395105081 · doi:10.29327/1298728.24-9

The Philosophy Behind IRES, an Intentional Requirements Engineering Strategy

2021· article· en· W4395105081 on OpenAlexafffund
Antônio de Pádua Albuquerque Oliveira, Vera Maria B. Werneck, Luiz Marcio Cysneiros, Julio César Sampaio do Prado Leite

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsYork University
FundersNatural Sciences and Engineering Research Council of CanadaConselho Nacional de Desenvolvimento Científico e Tecnológico
KeywordsComputer science

Abstract

fetched live from OpenAlex

Intentionality is considered particularly important in several facets of social context. For example, police investigation usually starts based on “the why”, which is searching for a motive. The search for a motive is also frequent in the anamnesis process in medicine, as well as in investigative journalism. In a criminal investigation, early discovery of motive usually provides a track to identify a crime's perpetrators. When in the doctor's office, the usual first question a patient has to answer is why he/she is there. In the same way, no one disagrees that software utility is the backbone of construction success. Since the task of discovering “the why” (goals) is abstract, subjective, and complicated, we delineate a thinking process frame, a philosophy, for guiding Requirements Engineers into focusing on intentions for the elicitation of goals. The philosophy, at the beginning of the IRES (Intentional Requirements Engineering Strategy), provides a backbone to the requirements process. It is composed of four topics (Necessity, Motivation, Goal, Action), and is linked by the intentionality and their interconnections in a given State of Affairs. The goal of this paper is to explain how this frame helps the construction of well-anchored models.

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.000
Version: codex-gemma-dda1882f352aValidation 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: Methods · Consensus signal: none
Teacher disagreement score0.827
Threshold uncertainty score0.348

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
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.041
GPT teacher head0.289
Teacher spread0.248 · 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 designTheoretical or conceptual
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

Citations0
Published2021
Admission routes2
Has abstractyes

Explore more

Same topicSoftware Engineering Techniques and PracticesFrench-language works237,207