ARENA: An Approach for the Automated Generation of Release Notes

Moreno, Laura; Bavota, Gabriele; Penta, Massimiliano Di; Oliveto, Rocco; Marcus, Andrian; Canfora, Gerardo

doi:10.1109/tse.2016.2591536

Cited by 83 publications

(57 citation statements)

References 38 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Cortes-Coy et al [35] used method stereotypes to identify the method responsibilities in a class for generating the commit messages and used templates to generate the sentences from the classes. Laura Moreno et al [36] used template-based summarization to generate the natural language summaries for source code changes of a project. One sentence was generated for each change.…”

Section: Abstractive Summarization: An Overview In the Context Of Thementioning

confidence: 99%

“…Conciseness, Content Adequacy, Accuracy Sridhara et al [32] Source Code Intrinsic (HumanBased) Accuracy, Content Adequacy, Conciseness Buse et al [33] Source Code Extrinsic Information, Conciseness Rastkar et al [34] Source Code Intrinsic Cortes Coy et al [35] Source Code Intrinsic Content Adequacy, Conciseness, Expressiveness, Preferability Moreno et al [36] Source Code + Issue Reports + Commit Messages Extrinsic Completeness, Importance, Applicability Kamimura et al [39] Unit Test Cases Intrinsic Li et al [40] Source Code Intrinsic + Extrinsic Conciseness, Expressiveness, Completeness Eddy et al [46] Source Code Intrinsic (Relative Utility) Masudur Rahman et al [29] Question Answering Site Discussions on Source Code Extrinsic Accuracy, Preciseness, Usefulness…”

Section: Extrinsic Evaluationmentioning

confidence: 99%

“…Moreno et al [36] assessed their system using extrinsic evaluation in terms of completeness, importance and applicability. Lotufo et al [4] in second part of their evaluation, assessed the quality of summaries in terms of usefulness while looking for solution around the bug for duplicate bug reports detection, understanding the bug reports in terms of status and open issues, bug prioritization, etc.…”

Section: Extrinsic Evaluationmentioning

confidence: 99%

“…They describe the changes in terms of documentation changes, license changes, code changes and library upgradations, fixed bugs, modified features, etc. ARENA is one approach towards automatic release notes generation where source code changes are integrated with issue tracker to capture the changes [36].…”

Section: Release Notes Generationmentioning

confidence: 99%

“…Automatic documents generation tools which produce documents by summarizing source code are not very expressive [41], work is required to produce more readable and expressive messages. More work on finding what is the most important information to be included in the automatic documents generation summaries and how to classify them is required [36].…”

Section: Source Code Summarizationmentioning

confidence: 99%

See 4 more Smart Citations

Summarization of Software Artifacts : A Review

Gupta¹,

S.K²

2017

IJCSIT

View full text Add to dashboard Cite

Summarization of software artifacts is an ongoing field of research among the software engineering community due to the benefits that summarization provides like saving of time and efforts in various software engineering tasks like code search, duplicate bug reports detection, traceability link recovery, etc. Summarization is to produce short and concise summaries. The paper presents the review of the state of the art of summarization techniques in software engineering context. The paper gives a brief overview to the software artifacts which are mostly used for summarization or have benefits from summarization. The paper briefly describes the general process of summarization. The paper reviews the papers published from 2010 to June 2017 and classifies the works into extractive and abstractive summarization. The paper also reviews the evaluation techniques used for summarizing software artifacts. The paper discusses the open problems and challenges in this field of research. The paper also discusses the future scopes in this area for new researchers.

show abstract

Section: Abstractive Summarization: An Overview In the Context Of Thementioning

confidence: 99%

Section: Extrinsic Evaluationmentioning

confidence: 99%

Section: Extrinsic Evaluationmentioning

confidence: 99%

Section: Release Notes Generationmentioning

confidence: 99%

Section: Source Code Summarizationmentioning

confidence: 99%

See 3 more Smart Citations

Summarization of Software Artifacts : A Review

Gupta¹,

S.K²

2017

IJCSIT

View full text Add to dashboard Cite

show abstract

Practitioners' expectations on automated release note generation techniques

Sumana Nath,

Roy

2024

J Software Evolu Process

View full text Add to dashboard Cite

The software development life cycle relies heavily on the software release note, a crucial document. Various practitioners, including project managers and clients, benefit from release notes as they provide an overview of the latest software release. However, the manual generation of release notes is a time‐consuming and stressful task. Researchers have recently proposed automated techniques to generate release notes, saving developers' time and enhancing their understanding of software projects. Unfortunately, the adoption of these tools in practice remains limited. To address this gap, we have taken steps to understand the expectations and requirements of practitioners regarding release note generation techniques before implementing new automated approaches. Consequently, our approach involves two main stages: First, we conduct a comprehensive review of the relevant literature and analyze existing release notes from GitHub repositories to gain insights into the current practices. Second, we conduct an online survey study to gather input from practitioners and understand their expectations regarding release notes. We have reviewed 16 papers related to release notes and explored 3347 release notes from 21 GitHub repositories. Our analysis revealed key artifacts present in release note contents, including issues (29%), pull requests (32%), commits (19%), and common vulnerabilities and exposures (CVE) issues (6%). Additionally, we conducted a survey study involving 32 professionals to understand the essential information that should be included in release notes based on users' roles. For instance, project managers were more interested in learning about new features rather than less critical bug fixes. Furthermore, we identified gaps in existing systems and essential factors to consider when implementing release notes techniques in software engineering. The insights gained from our study can guide future research directions and assist practitioners in generating release notes with relevant content, thus improving the overall quality of documentation in software development.

show abstract

A Neural Architecture for Detecting Identifier Renaming from Diff

Gu¹,

Ke²

2021

Intelligent Data Engineering and Automated Learning – IDEAL 2021

View full text Add to dashboard Cite

ARENA: An Approach for the Automated Generation of Release Notes

Cited by 83 publications

References 38 publications

Summarization of Software Artifacts : A Review

Summarization of Software Artifacts : A Review

Practitioners' expectations on automated release note generation techniques

A Neural Architecture for Detecting Identifier Renaming from Diff

Contact Info

Product

Resources

About