Searched for: author%3A%22Romano%2C+D.%22
(1 - 13 of 13)
document
Huijgens, H.K.M. (author), Lamping, Robert (author), Stevens, Dick (author), Rothengatter, Hartger (author), Gousios, G. (author), Romano, D. (author)
ING Bank, a large Netherlands-based internationally operating bank, implemented a fully automated continuous delivery pipeline for its software engineering activities in more than 300 teams, that perform more than 2500 deployments to production each month on more than 750 different applications. Our objective is to examine how strong metrics for...
conference paper 2017
document
Vassallo, Carmine (author), Schermann, Gerald (author), Zampetti, Fiorella (author), Romano, D. (author), Leitner, Philipp (author), Zaidman, A.E. (author), Di Penta, Massimiliano (author), Panichella, Sebastiano (author)
Continuous Integration (CI) and Continuous Delivery (CD) are widespread in both industrial and open-source software (OSS) projects. Recent research characterized build failures in CI and identified factors potentially correlated to them. However, most observations and findings of previous work are exclusively based on OSS projects or data from a...
conference paper 2017
document
Vassalo, Carmine (author), Zampetti, Fiorelli (author), Romano, D. (author), Beller, M.M. (author), Panichella, A. (author), Di Penta, Massimiliano (author), Zaidman, A.E. (author)
Continuous Delivery is an agile software develop- ment practice in which developers frequently integrate changes into the main development line and produce releases of their software. An automated Continuous Integration infrastructure builds and tests these changes. Claimed advantages of CD include early discovery of (integration) errors,...
conference paper 2016
document
Romano, D. (author)
Analyzing the Change-Proneness of APIs and web APIs APIs and web APIs are used to expose existing business logic and, hence, to ease the reuse of functionalities across multiple software systems. Software systems can use the business logic of legacy systems by binding their APIs and web APIs. With the emergence of a new programming paradigm...
doctoral thesis 2015
document
Romano, D. (author), Raemaekers, S. (author), Pinzger, M. (author)
Recent studies have shown that the violation of the Interface Segregation Principle (ISP) is critical for maintaining and evolving software systems. Fat interfaces (i.e., interfaces violating the ISP) change more frequently and degrade the quality of the components coupled to them. According to the ISP the interfaces’ design should force no...
report 2014
document
Romano, D. (author), Pinzger, M. (author)
The relevance of the service interfaces’ granularity and its architectural impact have been widely investigated in literature. Existing studies show that the granularity of a service interface, in terms of exposed operations, should reflect their clients’ usage. This idea has been formalized in the Consumer-Driven Contracts pattern (CDC)....
report 2014
document
Romano, D. (author), Pinzger, M. (author)
Version: Accepted for publication in the Proceedings of the International Conference on Software Maintenance (ICSM), 2013, IEEE Computer Society. Doi: http://dx.doi.org/10.1109/ICSM.2013.49 Q&A sites have become popular to share and look for valuable knowledge. Users can easily and quickly access high quality answers to common questions. The...
report 2013
document
Romano, D. (author)
Antipatterns and code smells have been widely proved to affect the change-proneness of software components. However, there is a lack of studies that propose indicators of changes for service-oriented systems. Like any other software systems, such systems evolve to address functional and non functional requirements. In this research, we...
report 2013
document
Romano, D. (author), Raila, P. (author), Pinzger, M. (author), Khomh, F. (author)
Preprint of paper published in: WCRE 2012 - Proceedings of the 19th Working Conference on Reverse Engineering, 15-18 October 2012; doi:10.1109/WCRE.2012.53 Antipatterns are poor solutions to design and implementation problems which are claimed to make object oriented systems hard to maintain. Our recent studies showed that classes with...
report 2012
document
Romano, D. (author), Pinzger, M. (author)
Preprint of paper published in: ICWS 2012 - IEEE 19th International Conference on Web Services, 24-29 June 2012; doi:10.1109/ICWS.2012.29 In the service-oriented paradigm web service interfaces are considered contracts between web service subscribers and providers. However, these interfaces are continuously evolving over time to satisfy changes...
report 2012
document
Romano, D. (author), Pinzger, M. (author), Bouwers, E. (author)
Service Oriented Architecture (SOA) enables organizations to react to requirement changes in an agile manner and to foster the reuse of existing services. However, the dynamic nature of service oriented systems and their agility bear the challenge of properly understanding such systems. In particular, understanding the dependencies among...
report 2011
document
Romano, D. (author), Di Penta, M. (author), Antoniol, G. (author)
Uncaught exceptions, and in particular null pointer exceptions (NPEs), constitute a major cause of crashes for software systems. Although tools for the static identification of potential NPEs exist, there is need for proper approaches able to identify system execution scenarios causing NPEs. This paper proposes a search-based test data...
report 2011
document
Romano, D. (author), Pinzger, M. (author)
Recent empirical studies have investigated the use of source code metrics to predict the change- and defect-proneness of source code files and classes. While results showed strong correlations and good predictive power of these metrics, they do not distinguish between interface, abstract or concrete classes. In particular, interfaces declare...
report 2011
Searched for: author%3A%22Romano%2C+D.%22
(1 - 13 of 13)