Peer Review History

Original SubmissionSeptember 4, 2020
Decision Letter - Talib Al-Ameri, Editor

PONE-D-20-27912

Knowledge Reuse in Software Projects: Retrieving Software Development Q&A Posts Based on Project Task Similarity

PLOS ONE

Dear Dr. Melo,

Thank you for submitting your manuscript to PLOS ONE. After careful consideration, we feel that it has merit but does not fully meet PLOS ONE’s publication criteria as it currently stands. Therefore, we invite you to submit a revised version of the manuscript that addresses the points raised during the review process.

==============================

ACADEMIC EDITOR:

==============================

Please submit your revised manuscript by Nov 20 2020 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org. When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file.

Please include the following items when submitting your revised manuscript:

  • A rebuttal letter that responds to each point raised by the academic editor and reviewer(s). You should upload this letter as a separate file labeled 'Response to Reviewers'.
  • A marked-up copy of your manuscript that highlights changes made to the original version. You should upload this as a separate file labeled 'Revised Manuscript with Track Changes'.
  • An unmarked version of your revised paper without tracked changes. You should upload this as a separate file labeled 'Manuscript'.

If you would like to make changes to your financial disclosure, please include your updated statement in your cover letter. Guidelines for resubmitting your figure files are available below the reviewer comments at the end of this letter.

If applicable, we recommend that you deposit your laboratory protocols in protocols.io to enhance the reproducibility of your results. Protocols.io assigns your protocol its own identifier (DOI) so that it can be cited independently in the future. For instructions see: http://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols

We look forward to receiving your revised manuscript.

Kind regards,

Talib Al-Ameri, Ph.D

Academic Editor

PLOS ONE

Journal Requirements:

When submitting your revision, we need you to address these additional requirements.

1. Please ensure that your manuscript meets PLOS ONE's style requirements, including those for file naming. The PLOS ONE style templates can be found at

https://journals.plos.org/plosone/s/file?id=wjVg/PLOSOne_formatting_sample_main_body.pdf and

https://journals.plos.org/plosone/s/file?id=ba62/PLOSOne_formatting_sample_title_authors_affiliations.pdf

2. We noted in your submission details that a portion of your manuscript may have been presented or published elsewhere.

[Main results of precision and accuracy are published in Melo, G., Oliveira, T., Alencar, P., & Cowan, D. (2019). Retrieving curated stack overflow posts from project task similarities. In International Conference on Software Engineering Knowledge Engineering (pp. 415-418).]

Please clarify whether this [conference proceeding or publication] was peer-reviewed and formally published. If this work was previously peer-reviewed and published, in the cover letter please provide the reason that this work does not constitute dual publication and should be included in the current manuscript.

[Note: HTML markup is below. Please do not edit.]

Reviewers' comments:

Reviewer's Responses to Questions

Comments to the Author

1. Is the manuscript technically sound, and do the data support the conclusions?

The manuscript must describe a technically sound piece of scientific research with data that supports the conclusions. Experiments must have been conducted rigorously, with appropriate controls, replication, and sample sizes. The conclusions must be drawn appropriately based on the data presented.

Reviewer #1: Yes

**********

2. Has the statistical analysis been performed appropriately and rigorously?

Reviewer #1: Yes

**********

3. Have the authors made all data underlying the findings in their manuscript fully available?

The PLOS Data policy requires authors to make all data underlying the findings described in their manuscript fully available without restriction, with rare exception (please refer to the Data Availability Statement in the manuscript PDF file). The data should be provided as part of the manuscript or its supporting information, or deposited to a public repository. For example, in addition to summary statistics, the data points behind means, medians and variance measures should be available. If there are restrictions on publicly sharing data—e.g. participant privacy or use of data from a third party—those must be specified.

Reviewer #1: Yes

**********

4. Is the manuscript presented in an intelligible fashion and written in standard English?

PLOS ONE does not copyedit accepted manuscripts, so the language in submitted articles must be clear, correct, and unambiguous. Any typographical or grammatical errors should be corrected at revision, so please note any specific errors here.

Reviewer #1: Yes

**********

5. Review Comments to the Author

Please use the space provided to explain your answers to the questions above. You may also include additional comments for the author, including concerns about dual publication, research ethics, or publication ethics. (Please upload your review as an attachment if it exceeds 20,000 characters)

Reviewer #1: This paper focused on software knowledge reuse on Stack Overflow based on project task similarity. Two research questions were conducted.

There are some issues that the authors might consider:

(1) The manuscript suffers from how to generalize the proposed approach to other datasets or other domains. This paper focused on a domain-specific problem. The article fails to provide insights and give generalized suggestions to more diversified readers in this regard.

(2) Some figures and tables are not clear and are not friendly for readability. The authors should consider using vector graphics such as eps and pdf.

(3) Some recently related works should be included.

LinkLive: discovering Web learning resources for developers from Q&A discussions

Learning to answer programming questions with software documentation through social context embedding

Leveraging Official Content and Social Context to Recommend Software Documentation

To Do or Not To Do: Distill crowdsourced negative caveats to augment api documentation

**********

6. PLOS authors have the option to publish the peer review history of their article (what does this mean?). If published, this will include your full peer review and any attached files.

If you choose “no”, your identity will remain anonymous but your review may still be made public.

Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy.

Reviewer #1: No

[NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files.]

While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/. PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email PLOS at figures@plos.org. Please note that Supporting Information files do not need this step.

Revision 1

PONE-D-20-27912

Knowledge Reuse in Software Projects: Retrieving Software Development Q&A Posts Based on Project Task Similarity

PLOS One

In this document, we are addressing the reviewers' comments. We thank the reviewers for the additional comments and willingness to improve the quality of the publication with a very helpful review. We have made changes in the manuscript, addressing each of the reviewers’ comments.

Journal Requirements:

When submitting your revision, we need you to address these additional requirements.

1. Please ensure that your manuscript meets PLOS ONE's style requirements, including those for file naming. The PLOS ONE style templates can be found at https://journals.plos.org/plosone/s/file?id=wjVg/PLOSOne_formatting_sample_main_body.pdf and https://journals.plos.org/plosone/s/file?id=ba62/PLOSOne_formatting_sample_title_authors_affiliations.pdf

>Answer: We have reviewed the template specifications.

2. We noted in your submission details that a portion of your manuscript may have been presented or published elsewhere.

[Main results of precision and accuracy are published in Melo, G., Oliveira, T., Alencar, P., & Cowan, D. (2019). Retrieving curated stack overflow posts from project task similarities. In International Conference on Software Engineering Knowledge Engineering (pp. 415-418).]

Please clarify whether this [conference proceeding or publication] was peer-reviewed and formally published. If this work was previously peer-reviewed and published, in the cover letter please provide the reason that this work does not constitute dual publication and should be included in the current manuscript.

>Answer: (This answer is also in the Cover Letter as requested). A preliminary and shorter version (4 pages) of this paper was peer-reviewed and formally published in the International Conference on Software Engineering Knowledge Engineering (SEKE 2019). This previous paper was extended to 35 pages in several ways. First, the process model description is extensively detailed to support an exact and accurate replication of the proposed model. Second, a completely new and unpublished systematic mapping study was introduced. This systematic mapping study answers research questions regarding current proposals that associate Stack Overflow with the development environment. Third, the experimental studies have been extended by the additional distance and similarity algorithm calculations. Also, the paper has been significantly enhanced by extensions that provide additional details about the background, related work, case studies, and the analysis of the results. Given that the first publication is published as a short paper, we believe that the findings presented in our paper will appeal to the PLOS One Readers and academic community who subscribe to PLOS One. Our findings will allow your readers to accurately reproduce our proposed model, as we have included details about the implementation. Besides, the novel systematic mapping study advances the state-of-the-art by providing integrated information regarding current proposals that associate Stack Overflow and software development.

Reviewer #1: This paper focused on software knowledge reuse on Stack Overflow based on project task similarity. Two research questions were conducted.

There are some issues that the authors might consider:

(1) The manuscript suffers from how to generalize the proposed approach to other datasets or other domains. This paper focused on a domain-specific problem. The article fails to provide insights and give generalized suggestions to more diversified readers in this regard.

>Answer:

We have added the following paragraph to the manuscript, in the Discussion Section.

“With respect to the application of the proposed approach in other domains, we argue knowledge bases can be a useful asset in diverse domains such as language studies, health or mathematics. We believe these and other domains could use similar approaches to discover and reuse knowledge through automated tools and methods. Although the approach presented in our paper focuses on software development, the general principles of the proposed approach could be applied to knowledge bases in many additional domains. Of course, new approaches would require data from the experts using these knowledge bases. For example, in the case of health, physicians could take advantage of specific health information already curated by other experts that have used those knowledge bases. The approach could use clinical guideline tasks instead of software development tasks, and instead of Stack Overflow, the approach in health care could use a medical knowledge base Q&A website such as medhelp.org. The proposed approach could also be applied to knowledge bases in domains other than health such as mathematics math.stackexchange.com and the law avvo.com.”

Regarding our dataset, although we have relied on one dataset in the software engineering domain, the dataset is diverse and considers multiple projects (five) of the company in an extended period of time (around 7 years), not only one project. The projects in the dataset have different characteristics, such as (1) legacy project with few maintenance tasks, (2) project that is new and uses modern programming languages for front-end, back-end and database - Ruby on Rails, NodeJS and MongoDB, (3) main project in the company, that had in 2018 been in production for over 8 years and lastly, a (4) project created to coordinate the migration of the application server. We have added this project characterization to the manuscript. This dataset, which considers multiple projects, covers a diversity of cases in the software engineering domain.

(2) Some figures and tables are not clear and are not friendly for readability. The authors should consider using vector graphics such as eps and pdf.

>Answer: We have converted all the figures to .eps for improved quality.

(3) Some recently related works should be included.

LinkLive: discovering Web learning resources for developers from Q&A discussions

Learning to answer programming questions with software documentation through social context embedding

Leveraging Official Content and Social Context to Recommend Software Documentation

To Do or Not To Do: Distill crowdsourced negative caveats to augment api documentation

>Answer: We have added the recommended references in the Related Work Section.

Attachments
Attachment
Submitted filename: Plos One Rebuttal - PONE-D-20-27912.pdf
Decision Letter - Talib Al-Ameri, Editor

Knowledge Reuse in Software Projects: Retrieving Software Development Q&A Posts Based on Project Task Similarity

PONE-D-20-27912R1

Dear Dr. Melo,

We’re pleased to inform you that your manuscript has been judged scientifically suitable for publication and will be formally accepted for publication once it meets all outstanding technical requirements.

Within one week, you’ll receive an e-mail detailing the required amendments. When these have been addressed, you’ll receive a formal acceptance letter and your manuscript will be scheduled for publication.

An invoice for payment will follow shortly after the formal acceptance. To ensure an efficient process, please log into Editorial Manager at http://www.editorialmanager.com/pone/, click the 'Update My Information' link at the top of the page, and double check that your user information is up-to-date. If you have any billing related questions, please contact our Author Billing department directly at authorbilling@plos.org.

If your institution or institutions have a press office, please notify them about your upcoming paper to help maximize its impact. If they’ll be preparing press materials, please inform our press team as soon as possible -- no later than 48 hours after receiving the formal acceptance. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information, please contact onepress@plos.org.

Kind regards,

Talib Al-Ameri, Ph.D

Academic Editor

PLOS ONE

Additional Editor Comments (optional):

Reviewers' comments:

Reviewer's Responses to Questions

Comments to the Author

1. If the authors have adequately addressed your comments raised in a previous round of review and you feel that this manuscript is now acceptable for publication, you may indicate that here to bypass the “Comments to the Author” section, enter your conflict of interest statement in the “Confidential to Editor” section, and submit your "Accept" recommendation.

Reviewer #1: All comments have been addressed

**********

2. Is the manuscript technically sound, and do the data support the conclusions?

The manuscript must describe a technically sound piece of scientific research with data that supports the conclusions. Experiments must have been conducted rigorously, with appropriate controls, replication, and sample sizes. The conclusions must be drawn appropriately based on the data presented.

Reviewer #1: Yes

**********

3. Has the statistical analysis been performed appropriately and rigorously?

Reviewer #1: Yes

**********

4. Have the authors made all data underlying the findings in their manuscript fully available?

The PLOS Data policy requires authors to make all data underlying the findings described in their manuscript fully available without restriction, with rare exception (please refer to the Data Availability Statement in the manuscript PDF file). The data should be provided as part of the manuscript or its supporting information, or deposited to a public repository. For example, in addition to summary statistics, the data points behind means, medians and variance measures should be available. If there are restrictions on publicly sharing data—e.g. participant privacy or use of data from a third party—those must be specified.

Reviewer #1: Yes

**********

5. Is the manuscript presented in an intelligible fashion and written in standard English?

PLOS ONE does not copyedit accepted manuscripts, so the language in submitted articles must be clear, correct, and unambiguous. Any typographical or grammatical errors should be corrected at revision, so please note any specific errors here.

Reviewer #1: Yes

**********

6. Review Comments to the Author

Please use the space provided to explain your answers to the questions above. You may also include additional comments for the author, including concerns about dual publication, research ethics, or publication ethics. (Please upload your review as an attachment if it exceeds 20,000 characters)

Reviewer #1: (No Response)

**********

7. PLOS authors have the option to publish the peer review history of their article (what does this mean?). If published, this will include your full peer review and any attached files.

If you choose “no”, your identity will remain anonymous but your review may still be made public.

Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy.

Reviewer #1: No

Formally Accepted
Acceptance Letter - Talib Al-Ameri, Editor

PONE-D-20-27912R1

Knowledge Reuse in Software Projects: Retrieving Software Development Q&A Posts Based on Project Task Similarity

Dear Dr. Melo dos Santos:

I'm pleased to inform you that your manuscript has been deemed suitable for publication in PLOS ONE. Congratulations! Your manuscript is now with our production department.

If your institution or institutions have a press office, please let them know about your upcoming paper now to help maximize its impact. If they'll be preparing press materials, please inform our press team within the next 48 hours. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information please contact onepress@plos.org.

If we can help with anything else, please email us at plosone@plos.org.

Thank you for submitting your work to PLOS ONE and supporting open access.

Kind regards,

PLOS ONE Editorial Office Staff

on behalf of

Dr. Talib Al-Ameri

Academic Editor

PLOS ONE

Open letter on the publication of peer review reports

PLOS recognizes the benefits of transparency in the peer review process. Therefore, we enable the publication of all of the content of peer review and author responses alongside final, published articles. Reviewers remain anonymous, unless they choose to reveal their names.

We encourage other journals to join us in this initiative. We hope that our action inspires the community, including researchers, research funders, and research institutions, to recognize the benefits of published peer review reports for all parts of the research system.

Learn more at ASAPbio .