MétaCan
Menu
Back to cohort
Record W4404589801 · doi:10.4108/eetsis.6061

Exploring the Landscape of Multicriteria Decision Making in Software Project Management: Trends, Challenges, and Future Directions

2024· article· en· W4404589801 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueICST Transactions on Scalable Information Systems · 2024
Typearticle
Languageen
FieldDecision Sciences
TopicConstruction Project Management and Performance
Canadian institutionsUniversity Canada West
Fundersnot available
KeywordsMultiple-criteria decision analysisScopusManagement scienceComputer scienceSoftwareSoftware project managementProject managementEngineering managementProcess managementSystems engineeringEngineeringSoftware developmentOperations researchSoftware construction

Abstract

fetched live from OpenAlex

INTRODUCTION: This critical review investigates the utilization trends of Multicriteria Decision Making (MCDM) in software project management, emphasizing its applications, implementation challenges, and emerging trends.OBJECTIVES: The study explores recent literature published between 2019 and 2024, utilizing a systematic methodology to analyze the effectiveness and limitations of MCDM techniques in software project planning, selection, and execution.METHODS: A Boolean search strategy on Scopus was employed to identify relevant literature. The systematic methodology involved analyzing the identified literature to discern patterns, gaps, and recommendations for integrating MCDM methodologies within software engineering projects.RESULTS: The review identifies key patterns, challenges, and emerging trends in adopting MCDM techniques in software project management, providing insights and recommendations for future research and practice.CONCLUSION: This critical review offers valuable insights into the landscape of MCDM utilization in software project management, highlighting areas for improvement and future exploration.

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.

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.002
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: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.990
Threshold uncertainty score0.657

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0030.002
Science and technology studies0.0000.000
Scholarly communication0.0010.003
Open science0.0000.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.107
GPT teacher head0.329
Teacher spread0.222 · 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