MétaCan
Menu
Back to cohort
Record W1990031879 · doi:10.1109/coginf.2005.1532645

Measuring dependency constraint satisfaction in software release planning using dissimilarity of fuzzy graphs

2005· article· en· W1990031879 on OpenAlexaff
An Ngo‐The, Moshood Omolade Saliu

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsDependency (UML)Fuzzy logicFuzzy setComputer scienceFuzzy set operationsDependency graphMathematical optimizationFuzzy numberGraphMathematicsArtificial intelligenceTheoretical computer science

Abstract

fetched live from OpenAlex

Release planning is a cornerstone problem in incremental software development. It deals with the assignment of requirements to sequence of releases in order to maximize profit, minimize the delay of feedback and return of investment in such a way that dependency and resource constraints are met. Release planning decisions are required at an early stage in the development cycle, when uncertainty is unavoidable in the project estimates. Recently, there are some works concerning the use of fuzzy theory to address issues concerning the uncertainty in the release planning problem: fuzzy effort constraints and fuzzy dependency constraints. In this paper, we study the application of fuzzy theory to handle the uncertainty concerning dependency constraints from a holistic perspective, i.e. the whole set of fuzzy dependency constraints is considered as a fuzzy graph. The satisfaction of dependency constraints in a solution plan is measured by the distance between this plan and an ideal plan (in terms of the dependency constraints). The distance is materialized as the distance between two fuzzy graphs. This is considered to be an essential support for the actual decision-making. All the concepts and the complete approach are illustrated by a case study example.

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

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0030.016
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0030.002
Science and technology studies0.0010.001
Scholarly communication0.0010.002
Open science0.0010.001
Research integrity0.0010.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.055
GPT teacher head0.288
Teacher spread0.234 · 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 designSimulation or modeling
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

Citations14
Published2005
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering Techniques and PracticesFrench-language works237,207