Antonio Silva

Dr. Antonio Silva


Research Focus & Metrics

Academic Career Length

30Years (1997-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
22 February 2011 in Journal of Software Maintenance and Evolution: Research and Practice
Verified
Journal Article
Closed access
PDF file
GBGiorgio Bruno
Giorgio Bruno
FDFrank Dengler
Frank Dengler
BJBen Jennings
Ben Jennings
RKRania Khalaf
Rania Khalaf
SNSelmin Nurcan
Selmin Nurcan
ASAntonio Silva
Antonio Silva

1 December 2006 in Science of Computer Programming
Verified
Journal Article
Closed access
JCJoão Cachopo
João Cachopo
ASAntonio Silva
Antonio Silva

1 June 2012
Verified
Conference Paper
Closed access
MGMário Luís Guimarães
Mário Luís Guimarães
ASAntonio Silva
Antonio Silva
Merge conflicts cause software defects which if detected late may require expensive resolution. This is especially true when developers work too long without integrating concurrent changes, which in practice is common as integration generally occurs at check-in. Awareness of others' activities was proposed to help developers detect conflicts earlier. However, it requires developers to detect conflicts by themselves and may overload them with notifications, thus making detection harder. This paper presents a novel solution that continuously merges uncommitted and committed changes to create a background system that is analyzed, compiled, and tested to precisely and accurately detect conflicts on behalf of developers, before check-in. An empirical study confirms that our solution avoids overloading developers and improves early detection of conflicts over existing approaches. Similarly to what happened with continuous compilation, this introduces the case for continuous merging inside the IDE.


1 March 2020
Verified
Conference Paper
Closed access
NSNuno Santos
Nuno Santos
ASAntonio Silva
Antonio Silva
Monolith applications tend to be difficult to deploy, upgrade, maintain, and understand. Microservices, on the other hand, have the advantages of being independently developed, tested, deployed, scaled and, more importantly, easier to change and maintain. This paper addresses the problem of migrating a monolith to a microservices architecture. Therefore, we address two research questions: (1) Can we define the cost of decomposition in terms of the effort to redesign a functionality, which is implemented in the monolith as an ACID transaction, into several distributed transactions? (2) Considering several similarity measures between domain entities, which provide a better decomposition when they are compared using the proposed complexity metric? To answer the first research question, we propose a complexity metric, for each functionality of the monolith application, that measures the impact of relaxing the functionality consistency on the architecture redesign and implementation. Regarding the second research question, we experiment with four similarity measures, each based on a different type of information collected from monolith functionality implementation. We evaluated our approach with three monolith systems and compared our complexity metric against industry metrics of cohesion and coupling. We also evaluated the different similarity measures in terms of the complexity of the decomposition they produce. We were able to correctly correlate the complexity metric with other metrics of cohesion and coupling defined in other research and we conclude that no single combination of similarity measures outperforms the other, which is confirmed by the existing research. Additionally, we conclude that the approach can help on an incremental migration to microservices, which, actually, is the strategy proposed by the industry experts.