This paper makes the case for the study of human values in Software Engineering (SE) as a highly important emerging area of research with significant societal implications. We offer two key principles in order to advance this research agenda: firstly, the significance of values as distinguished from, though connected to, ethics; and secondly, the need for clear theoretical frameworks for values study. We provide the emerging findings from an initial study (N=12 participants) using a Values Q-Sort tool that was designed in accordance with these two principles. We conclude with discussion around lessons learnt, ongoing challenges, and future directions. CCS CONCEPTS• Social and professional topics → Computing profession; • Software and its engineering;KEYWORDS human values, mixed methods, qualitative study, software industry ACM Reference Format:

This paper reports on the development of ongoing research into the systematic study of human values in software engineering (SE). Firstly, we outline the rationale for this work, highlighting the significance of human values in SE and the need for both a more structured approach to their study and tools to support their articulation in the SE domain. We then explain our theoretical framework, which draws on social psychology research on values. Secondly, we introduce tools designed in line with this framework and the context of their use so far. Our tools adopt a variety of research methods, including structured mixed-method techniques, such as the 'Values Q-Sort' (V-QS), and more open design-based methods, such as the 'Values Probes'. Given the multi-faceted nature of the topic, we argue that a combination of qualitative, quantitative and design thinking techniques is a necessary step for the study of human values in SE; and that these methods should be both a) robust and replicable, and b) creative and provocative. Finally, we highlight the potential applications of our tools in SE industry and education.

No abstract

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;