Controlling Software Architecture Erosion¶
de Silva, L., & Balasubramaniam, D. (2012). Controlling Software Architecture Erosion: A Survey. Journal of Systems and Software, 85(1), 132-151.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Mechanisms¶
- Architecture Blueprint
- A blueprint asserts how the system is meant to be arranged, not how it is; left unmaintained it drifts from what was actually built, until it describes a system that no longer exists.
This sourceExplains how accumulated implementation changes can produce a mismatch between an intended architecture and the system actually built.
- A blueprint asserts how the system is meant to be arranged, not how it is; left unmaintained it drifts from what was actually built, until it describes a system that no longer exists.
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Not recorded. The single citation of this work carries no recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:3cd078190d2e · see in the full table