ViDI, Vici. In Proceedings of SANER’15, pp. 151-160, IEEE, 2015 Y. Tymchuk, A. Mocci, and M. Lanza. Vidi: The Visual Design Inspector. In Proceedings of ICSE’15, to be published, IEEE, 2015
ViDI, Vici. In Proceedings of SANER’15, pp. 151-160, IEEE, 2015 Y. Tymchuk, A. Mocci, and M. Lanza. Vidi: The Visual Design Inspector. In Proceedings of ICSE’15, to be published, IEEE, 2015
O. Nierstrasz. Domain-speci!c program checking. In Proceedings of TOOLS’10, pp. 213-232, 2010 A. C. Hora. Assessing and Improving Rules to Support Software Evolution. PhD diss., Université Lille 1-Sciences et Technologies, 2014
Nierstrasz. Domain-speci!c program checking. In Proceedings of TOOLS’10, pp. 213-232, 2010 A. C. Hora. Assessing and Improving Rules to Support Software Evolution. PhD diss., Université Lille 1-Sciences et Technologies, 2014
Can deprecation / API changes be enhanced by quality rules? What are the con#icts for dedicated rules of dependent projects? Is the importance of a critic related to a software lifecycle period? BL OC vs
Can deprecation / API changes be enhanced by quality rules? What are the con#icts for dedicated rules of dependent projects? Is the importance of a critic related to a software lifecycle period? Do developer/teem dedicated rules perform better than generic? Can the cost/value of critic resolution be derived from history? (Dedicated technical debt) BL OC vs
A E E L V Supervisor: Michele Lanza In order to build helpful software quality tools, we need an underlying model that 1) facilitates “smart” rules (that aid in critic resolution) 2) allows adaptation of rules for a speci"c scope 3) is aware of software scopes and lifecycle