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¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Registry ID ref:3cd078190d2e · see in the full table