Construct · 1 fields · 1 citations

modularity violations: a standalone construct

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

● anchor · a standalone construct Nearest construct by meaning·not indexed

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

Software engineering

files that change together in history although the design says they should be independent, flagged as signs of design decay.

In software engineering, modularity violations refers to files that change together in history although the design says they should be independent, flagged as signs of design decay. This meaning comes from Wong (2011) in Proceedings of the 33rd International Conference on Software Engineering.[1]

Unit
Recovery means
Measured by

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

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

Open in Collider Export BibTeX Report this entry

Nearby constructs

decay4 fields · 5 citationsjingle · one word, four constructs modularity4 fields · 7 citationsjingle · one word, four constructs

References

Wong, S., Cai, Y., Kim, M., & Dalton, M. (2011). Detecting software modularity violations. Proceedings of the 33rd International Conference on Software Engineering. https://doi.org/10.1145/1985793.1985850

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