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

Bimpe Ayoola

dblp:338/9113 · DBLP profile ↗
← Back
2ranked-venue papers
1as first author
2since 2021 · last 2025
0000-0002-1802-9819ORCID · corroborated

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

Software engineering, systems software and programming languages · 2 · 1 first-author · 2 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
2 papers
Software maintenance and evolution · 41% Requirements engineering and software design · 30% Empirical software engineering · 29%

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution
software sustainability
1.522025
User Personas Improve Social Sustainability by Encouraging Software Developers to Deprioritize Antisocial Features · ICSE 2025
Sustainability is Stratified: Toward a Better Theory of Sustainable Software Engineering · ICSE 2023
Empirical software engineering
developer studies
0.912025
User Personas Improve Social Sustainability by Encouraging Software Developers to Deprioritize Antisocial Features · ICSE 2025
Requirements engineering and software design › requirements elicitation
stakeholder analysis
0.912025
User Personas Improve Social Sustainability by Encouraging Software Developers to Deprioritize Antisocial Features · ICSE 2025
Requirements engineering and software design › requirements management
requirements prioritization
0.312025
User Personas Improve Social Sustainability by Encouraging Software Developers to Deprioritize Antisocial Features · ICSE 2025

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

randomized controlled factorial experiment · 0.9cumulative link mixed model regression · 0.9scoping review · 0.7meta-synthesis · 0.7
YearPublicationVenuePosition
2025 User Personas Improve Social Sustainability by Encouraging Software Developers to Deprioritize Antisocial Features
abstract
Background: Sustainable software development involves creating software in a manner that meets present goals without undermining our ability to meet future goals. In a software engineering context, sustainability has at least four dimensions: ecological, economic, social, and technical. No interventions for improving social sustainability in software engineering have been tested in rigorous lab-based experiments, and little evidence-based guidance is available. Objective: The purpose of this study is to evaluate the effectiveness of two interventions—stakeholder maps and persona models—for improving social sustainability through software feature prioritization. Method: We conducted a randomized controlled factorial experiment with 79 undergraduate computer science students. Participants were randomly assigned to one of four groups and asked to prioritize a backlog of prosocial, neutral, and antisocial user stories for a shopping mall's digital screen display and facial recognition software. Participants received either persona models, a stakeholder map, both, or neither. We compared the differences in prioritization levels assigned to prosocial and antisocial user stories using Cumulative Link Mixed Model regression. Results: Participants who received persona models gave significantly lower priorities to antisocial user stories but no significant difference was evident for prosocial user stories. The effects of the stake-holder map were not significant. The interaction effects were not significant. Conclusion: Providing aspiring software professionals with well-crafted persona models causes them to de-prioritize antisocial software features. The impact of persona modelling on sustainable software development therefore warrants further study with more experience professionals. Moreover, the novel methodological strategy of assessing social sustainability behavior through backlog prioritization appears feasible in lab-based settings.
Bimpe Ayoola, Miikka Kuutila, Rina R. Wehbe, Paul Ralph
ICSE1
2023 Sustainability is Stratified: Toward a Better Theory of Sustainable Software Engineering
abstract
Background: Sustainable software engineering (SSE) means creating software in a way that meets present needs without undermining our collective capacity to meet our future needs. It is typically conceptualized as several intersecting dimensions or “pillars”-environmental, social, economic, technical and in-dividual. However; these pillars are theoretically underdeveloped and require refinement. Objectives: The objective of this paper is to generate a better theory of SSE. Method: First, a scoping review was conducted to understand the state of research on SSE and identify existing models thereof. Next, a meta-synthesis of qualitative research on SSE was conducted to critique and improve the existing models identified. Results: 961 potentially relevant articles were extracted from five article databases. These articles were de-duplicated and then screened independently by two screeners, leaving 243 articles to examine. Of these, 109 were non-empirical, the most common empirical method was systematic review, and no randomized controlled experiments were found. Most papers focus on ecological sustainability (158) and the sustainability of software products (148) rather than processes. A meta-synthesis of 36 qualitative studies produced several key propositions, most notably, that sustainability is stratified (has different meanings at different levels of abstraction) and multisystemic (emerges from interactions among multiple social, technical, and sociotechnical systems). Conclusion: The academic literature on SSE is surprisingly non-empirical. More empirical evaluations of specific sustainability interventions are needed. The sustainability of software development products and processes should be conceptualized as multisystemic and stratified, and assessed accordingly.
Sean McGuire, Erin Schultz, Bimpe Ayoola, Paul Ralph
ICSE3