Construct · 1 fields · 1 citations

bloated dependencies: a standalone construct

One name. One construct. A landmark on the map.

● anchor · a standalone construct Nearest construct by meaning·not indexed
bloateddependencies1 CONSTRUCTBloated dependenciesSOTO-VALERO · SOFTWARE

A single standalone construct; nearby constructs are located against it in the Collider. Tap a field for its definition, unit, and measures.

Software engineering

declared or inherited library dependencies that a project does not actually need to compile or run, measured across an ecosystem.

In software engineering, bloated dependencies refers to declared or inherited library dependencies that a project does not actually need to compile or run, measured across an ecosystem. This meaning comes from Soto-Valero (2021) in Empirical Software Engineering.[1]

Unit
Recovery means
Measured by

Next

Run it through the Collider, or take the citations with you.

See how bloated dependencies sits against neighbouring constructs in the Collider, or export every reference on this page in one click.

Open in ColliderExport BibTeXReport this entry

Nearby constructs

ecosystem3 fields · 5 citationsjingle · one word, three constructslibrary1 fields · 1 citationsanchor · a standalone constructneed3 fields · 4 citationsjingle · one word, three constructs

References

  1. Soto-Valero, C., Harrand, N., Monperrus, M., & Baudry, B. (2021). A comprehensive study of bloated dependencies in the Maven ecosystem. Empirical Software Engineering, 26(3). https://doi.org/10.1007/s10664-020-09914-8

Cited on this page?

Confirm your construct, or correct us.

If your work is cited behind one of these entries, you know better than we do whether we captured the meaning right. Confirm it, suggest an edit, or dispute it, and your name goes on the entry as an author who has checked it, linked to your ORCID.

Claim your construct