How to Debug Inclusivity Bugs? A Debugging Process with Information Architecture
How to Debug Inclusivity Bugs? A Debugging Process with Information Architecture
复制标题
如何调试包容性错误?
DOI:
10.1109/icse-seis55304.2022.9794009
复制
发表时间:
2022
期刊:
影响因子:
--
通讯作者:
Sarma, Anita
中科院分区:
文献类型:
--
作者:
Guizani, Mariam;Steinmacher, Igor;Emard, Jillian;Fallatah, Abrar;Burnett, Margaret;Sarma, Anita
Although some previous research has found ways tofindinclusivity bugs (biases in software that introduce inequities), little attention has been paid to how to go aboutfixingsuch bugs. Without a process to move from finding to fixing, acting upon such findings is an ad-hoc activity, at the mercy of the skills of each individual developer. To address this gap, we createdWhy/Where/Fix, a systematic inclusivity debugging process whose inclusivity fault localization harnesses Information Architecture(IA)---the way user-facing information is organized, structured and labeled. We then conducted a multi-stage qualitative empirical evaluation of the effectiveness of Why/Where/Fix, using an Open Source Software (OSS) project's infrastructure as our setting. In our study, the OSS project team used the Why/Where/Fix process to find inclusivity bugs, localize the IA faults behind them, and then fix the IA to remove the inclusivity bugs they had found. Our results showed that using Why/Where/Fix reduced the number of inclusivity bugs that OSS newcomer participants experienced by 90%.Diverse teams have been shown to be more productive as well as more innovative. One form of diversity, cognitive diversity --- differences in cognitive styles --- helps generate diversity of thoughts. However, cognitive diversity is often not supported in software tools. This means that these tools are not inclusive of individuals with different cognitive styles (e.g., those who like to learn through process vs. those who learn by tinkering), which burdens these individuals with a cognitive "tax" each time they use the tool. In this work, we present an approach that enables software developers to: (1) evaluate their tools, especially those that are information-heavy, to find "inclusivity bugs" - cases where diverse cognitive styles are unsupported, (2) find where in the tool these bugs lurk, and (3) fix these bugs. Our evaluation in an open source project shows that by following this approach developers were able to reduce inclusivity bugs in their projects by 90%.
登录
查看更多内容
DOI:
10.1145/2597073.2597129
发表时间:
2014
期刊:
2019 IEEE/ACM 2nd International Workshop on Gender Equality in Software Engineering (GE)
影响因子:
--
作者:
G. Robles;L. Reina;Alexander Serebrenik;Bogdan Vasilescu;Jesus M. Gonzalez
通讯作者:
Jesus M. Gonzalez
影响因子:
5
作者:
D. Nafus
通讯作者:
D. Nafus
DOI:
--
发表时间:
2017
期刊:
IEEE Symposium on Visual Languages / Human-Centric Computing Languages and Environments
影响因子:
--
作者:
M. Burnett;Robin Counts;Ronette Lawrence;Hannah Hanson
通讯作者:
Hannah Hanson
DOI:
10.1518/hfes.46.1.104.30390
发表时间:
2004
期刊:
Human Factors: The Journal of Human Factors and Ergonomics Society
影响因子:
--
作者:
M. Resnick;Julian Sanchez
通讯作者:
Julian Sanchez
DOI:
10.1145/2479787.2479824
发表时间:
2013
期刊:
Inf. Syst.
影响因子:
--
作者:
Josep Maria Brunetti
通讯作者:
Josep Maria Brunetti