The Community for Technology Leaders
Green Image
Issue No. 05 - Sept.-Oct. (2015 vol. 32)
ISSN: 0740-7459
pp: 30-36
Joao Brunet , Federal University of Campina Grande
Gail C. Murphy , University of British Columbia
Dalton Serey , Federal University of Campina Grande
Jorge Figueiredo , Federal University of Campina Grande
ABSTRACT
Over time, source code tends to drift from the intended software architecture, often resulting in the loss of desired software qualities. To help keep code aligned with the intended architecture, the developers of core parts of the open source Eclipse platform introduced API Tools to express and check architectural rules. Researchers analyzed five years of Eclipse architecture-checking reports that API Tools produced. They investigated what kinds of rules the developers found helpful to check, how code diverged from the intended architecture, and how the developers dealt with architectural violations over time. This article is part of a special issue on Software Architecture.
INDEX TERMS
Computer architecture, Software architecture, Software engineering, Documentation, Software maintenance, Computer science,software engineering, architecture checking, empirical software engineering, Eclipse, software development
CITATION
Joao Brunet, Gail C. Murphy, Dalton Serey, Jorge Figueiredo, "Five Years of Software Architecture Checking: A Case Study of Eclipse", IEEE Software, vol. 32, no. , pp. 30-36, Sept.-Oct. 2015, doi:10.1109/MS.2014.106
169 ms
(Ver 3.3 (11022016))