Semantic Slicing of Architectural Change Commits

Mondal, Amit Kumar; Roy, Chanchal K.; Schneider, Kevin A.; Roy, Banani; Nath, Sristy Sumana

doi:10.1145/3475716.3484487

Cited by 2 publications

(3 citation statements)

References 32 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For example, the major release notes include significant architectural changes and information on software refactoring. Mondal et al 21 proposed a tool that can detect and decompose semantic slices of a commit containing architectural instances, and this tool helps in release note generation process. Additionally, software test engineers get the benefit of knowing about the test activity from release notes.…”

Section: Results Analysismentioning

confidence: 99%

See 1 more Smart Citation

Practitioners' expectations on automated release note generation techniques

Sumana Nath,

Roy

2024

J Software Evolu Process

Self Cite

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

Section: Results Analysismentioning

confidence: 99%

“…For example, the major release notes include significant architectural changes and information on software refactoring. Mondal et al 21 T A B L E 7 Common usages and issues of release notes.…”

Section: Study 3: Online Survey Studymentioning

confidence: 99%

Practitioners' expectations on automated release note generation techniques

Sumana Nath,

Roy

2024

J Software Evolu Process

Self Cite

View full text Add to dashboard Cite

show abstract

“…Formal verifications, such as model checking and operation semantics, are used to verify its properties and are explicit for the efficient specification and proof of systems (Jbeli & Sbai, 2021). Complex software design and development can be decomposed into multiple dimensions, with subdimensions defined for semantic relationships across various domains (Mondal et al, 2021;Opdebeeck et al, 2021;Tamine & Goeuriot, 2021).…”

Section: Introductionmentioning

confidence: 99%

Software Development for Educational Information Services Using Multilayering Semantics Adaptation

Rukhiran

Buaroong

Netinant

2022

International Journal of Service Science, Management, Engineering, and Technology

View full text Add to dashboard Cite

Electronic information services are robust platforms that impact daily life and facilitate new research. Increasing software modularity and reusability saves time and money. Numerous designs and programming are challenging when developing a complex educational information system. This article proposes a new paradigm of multi-dimensional information layers, aspects, functional data, and composition rules in software development to create practical educational information platforms. The proposed approach uses aspect orientation throughout educational information's software development life cycle, from planning to implementation and evaluation. Finally, the authors demonstrate and evaluate the design model's modularity and adaptation through fine-granularity design and class reuse. The result reduces invasive changes, promotes modularity and reuse, and eliminates duplication in component-based software design.

show abstract

Semantic Slicing of Architectural Change Commits

Cited by 2 publications

References 32 publications

Practitioners' expectations on automated release note generation techniques

Practitioners' expectations on automated release note generation techniques

Software Development for Educational Information Services Using Multilayering Semantics Adaptation

Contact Info

Product

Resources

About