MétaCan
Menu
Back to cohort
Record W2547621596 · doi:10.1109/ms.2016.147

Cyclomatic Complexity

2016· article· en· W2547621596 on OpenAlexaff
Christof Ebert, James Cain, Giuliano Antoniol, Steve Counsell, Phillip A. Laplante

Bibliographic record

VenueIEEE Software · 2016
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsPolytechnique Montréal
FundersEngineering and Physical Sciences Research Council
KeywordsCyclomatic complexityComputer sciencePopularityMetric (unit)Software metricSoftware engineeringCode (set theory)Object (grammar)SoftwareSimple (philosophy)Software developmentProgramming languageData scienceTheoretical computer scienceSoftware qualityArtificial intelligenceEngineeringSet (abstract data type)Political scienceEpistemology

Abstract

fetched live from OpenAlex

The cyclomatic complexity (CC) metric measures the number of linearly independent paths through a piece of code. Although Thomas McCabe developed CC for procedural languages, its popularity has endured throughout the object-oriented era. That said, CC is one of the most controversial metrics, shunned for the most part by academia for certain theoretical weaknesses and the belief that it's no more useful than a simple “lines of code” metric. However, most metrics collection tools support its collection, and, paradoxically, industry uses it extensively. So, why is this the case? This question also leads to fundamental perennial questions about industry's exposure to academic opinion and whether academic research fails to take account of software development's daily practicalities. Maybe industry is simply looking for straightforward, widely understood metrics?

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.002
metaresearch head score (Gemma)0.015
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.017
Threshold uncertainty score0.057

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.015
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0050.005
Science and technology studies0.0020.006
Scholarly communication0.0100.011
Open science0.0020.004
Research integrity0.0020.003
Insufficient payload (model declined to judge)0.0170.004

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.038
GPT teacher head0.274
Teacher spread0.237 · 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

Citations128
Published2016
Admission routes1
Has abstractyes

Explore more

Same venueIEEE SoftwareSame topicSoftware Engineering ResearchFrench-language works237,207