Martin P. Robillard

Martin P. Robillard

Auto-generated profile, based on publicly available information

Martin P. Robillard

McGill University

Research Focus & Metrics

Academic Career Length

18Years (2009-Present)

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

Representative Publications

View All Publications
14 December 2010 in Empirical Software Engineering
Verified
Journal Article
Closed access
PDF file
MRMartin P. Robillard
Martin P. Robillard
RDRobert DeLine
Robert DeLine

15 July 2014 in Empirical Software Engineering
Verified
Journal Article
Closed access
PDF file
MRMartin P. Robillard
Martin P. Robillard
YCYam B. Chhetri
Yam B. Chhetri

4 June 2024 in ACM Transactions on Software Engineering and Methodology
Verified
Journal Article
Open access
MRMartin P. Robillard
Martin P. Robillard
DADeeksha M. Arya
Deeksha M. Arya
NENeil A. Ernst
Neil A. Ernst
JGJin L. C. Guo
Jin L. C. Guo
MLMaxime Lamothe
Maxime Lamothe
KSKlaas-Jan Stol
Klaas-Jan Stol
Reflecting on the limitations of a study is a crucial part of the research process. In software engineering studies, this reflection is typically conveyed through discussions of study limitations or threats to validity. In current practice, such discussions seldom provide sufficient insight to understand the rationale for decisions taken before and during the study, and their implications. We revisit the practice of discussing study limitations and threats to validity and identify its weaknesses. We propose to refocus this practice of self-reflection to a discussion centered on the notion of trade-offs . We argue that documenting trade-offs allows researchers to clarify how the benefits of their study design decisions outweigh the costs of possible alternatives. We present guidelines for reporting trade-offs in a way that promotes a fair and dispassionate assessment of researchers’ work.

18 August 2021
Verified
Conference Paper
Open access
MRMartin P. Robillard
Martin P. Robillard
When contributors to a software project leave, the knowledge they hold may become lost, thus impacting code quality and team productivity. Although well-known strategies can be used to mitigate knowledge loss, these strategies have to be tailored to their target context to be effective. To help software development organizations mitigate turnover-induced knowledge loss, we sought to better understand the different contexts in which developers experience this knowledge loss, and the resulting implications. We conducted qualitative interviews with 27 professional developers and managers from three different companies that provide software products and services. Leveraging the experience of these practitioners, we contribute a framework for characterizing turnover-induced knowledge loss and descriptions of the implications of knowledge loss, synthesized into 20 observations. These observations about knowledge loss in practice are organized into four themes, validated by the participants, and discussed within the context of the research literature in software engineering.

19 March 2020 in IEEE Transactions on Software Engineering
Verified
Journal Article
Closed access
SBSebastian Baltes
Sebastian Baltes
CTChristoph Treude
Christoph Treude
MRMartin P. Robillard
Martin P. Robillard
Software engineering is knowledge-intensive and requires software developers to continually search for knowledge, often on community question answering platforms such as Stack Overflow. Such information sharing platforms do not exist in isolation, and part of the evidence that they exist in a broader software documentation ecosystem is the common presence of hyperlinks to other documentation resources found in forum posts. With the goal of helping to improve the information diffusion between Stack Overflow and other documentation resources, we conducted a study to answer the question of how and why documentation is referenced in Stack Overflow threads. We sampled and classified 759 links from two different domains, regular expressions and Android development, to qualitatively and quantitatively analyze the links’ context and purpose, including attribution, awareness, and recommendations. We found that links on Stack Overflow serve a wide range of distinct purposes, ranging from citation links attributing content copied into Stack Overflow, over links clarifying concepts using Wikipedia pages, to recommendations of software components and resources for background reading. This purpose spectrum has major corollaries, including our observation that links to documentation resources are a reflection of the information needs typical to a technology domain. We contribute a framework and method to analyze the context and purpose of Stack Overflow links, a public dataset of annotated links, and a description of five major observations about linking practices on Stack Overflow. Those observations include the above-mentioned purpose spectrum, its interplay with documentation resources and applications domains, and the fact that links on Stack Overflow often lack context in form of accompanying quotes or summaries. We further point to potential tool support to enhance the information diffusion between Stack Overflow and other documentation resources.

7 June 2021 in IEEE Transactions on Software Engineering
Verified
Journal Article
Closed access
MNMathieu Nassif
Mathieu Nassif
AHAlexa Hernandez
Alexa Hernandez
ASAshvitha Sridharan
Ashvitha Sridharan
MRMartin P. Robillard
Martin P. Robillard
Software projects capture redundant information in various kinds of artifacts, as specifications from the source code are also tested and documented. Such redundancy provides an opportunity to reduce development effort by supporting the joint generation of different types of artifacts. We introduce a tool-supported technique, called DScribe, that allows developers to combine unit test and documentation templates, and to invoke these templates to generate documentation and unit tests. DScribe supports the detection and replacement of outdated documentation, and the use of templates can encourage extensive test suites with a consistent style. Our evaluation of 835 specifications revealed that 85 percent were not tested or correctly documented, and DScribe could be used to automatically generate 97 percent of the tests and documentation. An additional study revealed that tests generated by DScribe are more focused and readable than those written by human testers or generated by state-of-the-art automated techniques.