English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

Automatic bug reports assignment to fixers is an important activity for software quality assurance. Existing approaches consider either the bug fixing or source commit activities which may result in inactive or inexperienced developers suggestions. Considering only one of the information can not compensate another leading to reduced accuracy of developer suggestion. An approach named BSBA is proposed, which combines the expertise and recency of both bug fixing and source commit activities. Firstly, BSBA collects the source code and commit logs to construct an index, mapping the source entities with their commit time, which presents developers’ source code activities. Secondly, it processes the fixed bug reports to build another index which connects the report keywords to the fixing time. Finally, on arrival of new reports, BSBA queries the two indexes, and combines the query results using tf-idf weighting technique to measure a BSBA score for the developers. The top scored developers are suggested as appropriate fixers. BSBA is applied on two open source projects Eclipse JDT and SWT, and is compared with three existing techniques. The results show that BSBA obtains the actual fixer at Top 1 position in 45.67%, and 47.50% cases for Eclipse JDT and SWT respectively, which is higher than the existing approaches. It also shows that BSBA improves the accuracy of existing techniques on average by 3%-60%.

A Bug Assignment Approach Combining Expertise and Recency of Both Bug Fixing and Source Commits