Aspiration and complaint system: From literature survey to implementation

Zakia, Irma; Fatahillah, Asep Hikman; Syambas, Nana Rachmana; Setiawati, Asih; Mubarok, Housny

doi:10.1109/tssa.2017.8272952

Cited by 3 publications

(1 citation statement)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Although, as [55] reflects, the confidentiality of disclosures may not prevent discovery of whistleblower by other means. Two items [41,117] critique available whistleblowing platforms ahead of developing or selecting a whistleblowing platform solution. Bodo's paper [9] reports on aspects of privacy enhancing technologies, such as Wikileaks, and how it enables insiders to anonymously share private organisational information.…”

Section: Personal and Socialmentioning

confidence: 99%

A Review of How Whistleblowing is Studied in Software Engineering, and the Implications for Research and Practice

Hunt

Ferrario

2022

2022 IEEE/ACM 44th International Conference on Software Engineering: Software Engineering in Society (ICSE-SEIS)

View full text Add to dashboard Cite

Harmful software has resulted in loss of life, societal and environmental damage alongside economic losses from fines and sales embargoes. When someone perceives their team or organisation is creating or operating harmful software (e.g., defective, vulnerable, malicious or illegal), one way to attempt to change the situation is to "blow the whistle" and disclose the situation internally or externally. Studying harmful situations and the effectiveness of interventions, up to and including whistleblowing, can help identify technical and human successes and failings in software engineering (SE).The aim of this paper is to explore the extent to which whistleblowing is studied in SE with the objective of identifying themes, research approaches, gaps and concerns, and the implications for future SE research and practice.We find that whistleblowing is an under-explored area of SE research, and where research exists, it often takes the view that reporting harm is a matter of individual moral responsibility; we argue this poorly reflects SE collaborative practice where professional responsibilities are distributed across the software development lifecycle. We conclude by 1) recommending approaches that can help a more timely identification and mitigation of harm in SE; 2) suggesting mechanisms for improving the effectiveness and the personal safety of harm-reporting in SE, and 3) reflecting on the role that professional bodies can have in supporting harm reporting, up to and including whistleblowing. CCS CONCEPTS• Software and its engineering → Software creation and management; • Social and professional topics → Codes of ethics;

show abstract

Section: Personal and Socialmentioning

confidence: 99%