Program evolution: processes of software change
Program evolution: processes of software change
Does Code Decay? Assessing the Evidence from Change Management Data
IEEE Transactions on Software Engineering
A Metrics Suite for Object Oriented Design
IEEE Transactions on Software Engineering
Avoiding Architectural Degeneration: An Evaluation Process for Software Architecture
METRICS '02 Proceedings of the 8th International Symposium on Software Metrics
Does the Code Match the Design? A Process for Architecture Evaluation
ICSM '02 Proceedings of the International Conference on Software Maintenance (ICSM'02)
Characterizing software architecture changes: A systematic review
Information and Software Technology
| Hi-index | 0.00 |
Software systems often undergo changes. Changes are necessary not only to fix defects but also to accommodate new features demanded by users.ost of the time, changes are made under schedule and budget constraints and developers lack time to study the softwarearchitecture and select the best way to implement the changes. As a result, the code degenerates, making it differ from the planned design. The time spent on the planned design to create an architecture to satisfy certain properties is lost, and the systems may not satisfy those properties anymore. This paper describes an approach to systematically detect and correct deviations from the planned design as soon as possible based on architectural guidelines. The paper also describes a case study, in which the process was applied.