MétaCan
Menu
Back to cohort
Record W2083442948 · doi:10.4236/ti.2011.21004

Benefits of DfX in Requirements Engineering

2011· article· en· W2083442948 on OpenAlexvenueno aff
Jari Lehto, Janne Härkönen, Harri Haapasalo, Pekka Belt, Matti Möttönen, Pasi Kuvaja

Bibliographic record

VenueTechnology and Investment · 2011
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsnot available
FundersITEA
KeywordsProcess managementInformation and Communications TechnologyWork (physics)BusinessCompetitive advantageComputer scienceSupply chainKnowledge managementEngineering managementSystems engineeringEngineeringMarketing

Abstract

fetched live from OpenAlex

Information and communications technology (ICT) companies have realised how acknowledging the needs of both internal and external customers is a necessity for successful requirements engineering. Design for X (DfX) is a potential management approach for coordinating & communicating requirements emerging from both internal functions and external supply chain partners. This article studies the potential of DfX for improved requirements engineering. Qualitative interviews are utilised to analyse how different organisations implement the concept, including designers’ actual work, methods & tools, and organisational aspects. The results include viewing DfX as means to achieve relevant competitive goals, and describing how different companies organise these activities, together with their benefits for modern ICT companies. This study highlights how the DfX concept can be used to manage, prioritise and to better communicate

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.054
metaresearch head score (Gemma)0.079
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.054
Threshold uncertainty score0.286

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0540.079
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0030.003
Science and technology studies0.0020.007
Scholarly communication0.0050.013
Open science0.0020.010
Research integrity0.0030.004
Insufficient payload (model declined to judge)0.0040.001

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.037
GPT teacher head0.236
Teacher spread0.200 · 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 designNot applicable
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

Citations28
Published2011
Admission routes1
Has abstractyes

Explore more

Same venueTechnology and InvestmentSame topicSoftware Engineering Techniques and PracticesFrench-language works237,207