MétaCan
Menu
Back to cohort
Record W2130031345 · doi:10.1109/cere.2006.3

Evaluating the Effectiveness of a Goal-Oriented Requirements Engineering Method

2006· article· en· W2130031345 on OpenAlexaff
Huzam S. F. Al-subaie, Tom Maibaum

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsMcMaster University
Fundersnot available
KeywordsComputer scienceGoal orientationGoal modelingRequirements engineeringDomain (mathematical analysis)Software engineeringSoftwareMathematics

Abstract

fetched live from OpenAlex

As an attempt to answer the need for methods and tools in requirements engineering (RE) which are domain specific and can address the main RE objectives (REOs), and the growing interest in the goal oriented requirements engineering (GORE) approach that overcomes the inadequacy of the traditional systems analysis approaches, we systematically evaluate the KAOS method, and the Objectiver tool, using the major REOs widely accepted as being important attributes of requirements specifications. In addition, we examine whether KAOS and Objectiver meet their own selfdefined objectives. We use two target problems as a basis for the evaluation. The result of the target problems is raw data consisting of error reports and observations that support the evaluator's judgment. The evaluation itself is qualitative, not a statistical experimental evaluation. Its result will help to answer the research questions: (i) How well do KAOS and Objectiver meet the criteria established in the discipline of RE; and (ii) How well do KAOS and Objectiver achieve their own self-defined objectives.

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.074
metaresearch head score (Gemma)0.170
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.074
Threshold uncertainty score0.391

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0740.170
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0030.002
Science and technology studies0.0010.001
Scholarly communication0.0030.003
Open science0.0020.001
Research integrity0.0020.001
Insufficient payload (model declined to judge)0.0010.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.031
GPT teacher head0.365
Teacher spread0.334 · 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 designObservational
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

Citations34
Published2006
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering Techniques and PracticesFrench-language works237,207