Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Umme Ayman Koana

dblp:325/4448 · DBLP profile ↗
← Back
4ranked-venue papers
3as first author
4since 2021 · last 2025
0000-0001-8839-2560ORCID · corroborated

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 4 · 3 first-author · 4 since 2021

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Empirical software engineering · 87% Software maintenance and evolution · 13%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Empirical software engineering › mining software repositories › developer activity analysis
code ownership
0.712023
Ownership in the Hands of Accountability at Brightsquid: A Case Study and a Developer Survey · ESEC/SIGSOFT FSE 2023
Empirical software engineering
developer studies
0.712023
Ownership in the Hands of Accountability at Brightsquid: A Case Study and a Developer Survey · ESEC/SIGSOFT FSE 2023
Software maintenance and evolution
code change analysis
0.212023
Ownership in the Hands of Accountability at Brightsquid: A Case Study and a Developer Survey · ESEC/SIGSOFT FSE 2023

Methods — techniques the papers use, named apart from their topics

survey · 0.7code change analysis · 0.7
YearPublicationVenuePosition
2025 Correction to: Examining ownership models in software teams
Umme Ayman Koana, Quang Hy Le, Shadikur Raman, Chris Carlson, Francis Chew, Maleknaz Nayebi
Empir. Softw. Eng.1
2024 Examining ownership models in software teams
Umme Ayman Koana, Quang Hy Le, Shadikur Raman, Chris Carlson, Francis Chew, Maleknaz Nayebi
Empir. Softw. Eng.1
2023 Ownership in the Hands of Accountability at Brightsquid: A Case Study and a Developer Survey
abstract
The COVID−19 pandemic has accelerated the adoption of digital health solutions. This has presented significant challenges for software development teams to swiftly adjust to the market needs and demand. To address these challenges, product management teams have had to adapt their approach to software development, reshaping their processes to meet the demands of the pandemic. Brighsquid implemented a new task assignment process aimed at enhancing developer accountability toward the customer. To assess the impact of this change on code ownership, we conducted a code change analysis. Additionally, we surveyed 67 developers to investigate the relationship between accountability and ownership more broadly. The findings of our case study indicate that the revised assignment model not only increased the perceived sense of accountability within the production team but also improved code resilience against ownership changes. Moreover, the survey results revealed that a majority of the participating developers (67.5%) associated perceived accountability with artifact ownership.
Umme Ayman Koana, Francis Chew, Chris Carlson, Maleknaz Nayebi
ESEC/SIGSOFT FSE1
2022 Example Driven Code Review Explanation
abstract
Background: Code reviewing is an essential part of software development to ensure software quality. However, the abundance of review tasks and the intensity of the workload for reviewers negatively impact the quality of the reviews. The short review text is often unactionable. Aims: We propose the Example Driven Review Explanation (EDRE) method to facilitate the code review process by adding additional explanations through examples. EDRE recommends similar code reviews as examples to further explain a review and help a developer to understand the received reviews with less communication overhead. Method: Through an empirical study in an industrial setting and by analyzing 3,722 Code reviews across three open-source projects, we compared five methods of data retrieval, text classification, and text recommendation. Results: EDRE using TF-IDF word embedding along with an SVM classifier can provide practical examples for each code review with 92% F-score and 90% Accuracy. Conclusions: The example-based explanation is an established method for assisting experts in explaining decisions. EDRE can accurately provide a set of context-specific examples to facilitate the code review process in software teams.
Shadikur Rahman, Umme Ayman Koana, Maleknaz Nayebi
ESEM2