Sustainability Design and Software: The Karlskrona Manifesto

Sustainability has emerged as a broad concern for society. Many engineering disciplines have been grappling with challenges in how we sustain technical, social and ecological systems. In the software engineering community, for example, maintainability has been a concern for a long time. But too often, these issues are treated in isolation from one another. Misperceptions among practitioners and research communities persist, rooted in a lack of coherent understanding of sustainability, and how it relates to software systems research and practice. This article presents a cross-disciplinary initiative to create a common ground and a point of reference for the global community of research and practice in software and sustainability, to be used for effectively communicating key issues, goals, values and principles of sustainability design for software-intensive systems. The centrepiece of this effort is the Karlskrona Manifesto for Sustainability Design, a vehicle for a much needed conversation about sustainability within and beyond the software community, and an articulation of the fundamental principles underpinning design choices that affect sustainability. We describe the motivation for developing this manifesto, including some considerations of the genre of the manifesto as well as the dynamics of its creation. We illustrate the collaborative reflective writing process and present the current edition of the manifesto itself. We assess immediate implications and applications of the articulated principles, compare these to current practice, and suggest future steps

Requirements: The Key to Sustainability

Software's critical role in society demands a paradigm shift in the software engineering mind-set. This shift's focus begins in requirements engineering. This article is part of a special issue on the Future of Software Engineering

Sustainability Debt: A Metaphor to Support Sustainability Design Decisions

Sustainability, the capacity to endure, is fundamental for the societies on our planet. Despite its increasing recognition in software engineering, it remains difficult to assess the delayed systemic effects of decisions taken in requirements engineering and systems design. To support this difficult task, this paper introduces the concept of sustainability debt. The metaphor helps in the discovery, documentation, and communication of sustainability issues in requirements engineering. We build on the existing metaphor of technical debt and extend it to four other dimensions of sustainability to help think about sustainability-aware software systems engineering. We highlight the meaning of debt in each dimension and the relationships between those dimensions. Finally, we discuss the use of the metaphor and explore how it can help us to design sustainability-aware software intensive systems

Mind the Gap: Bridging the Sustainable Software Systems Research Divide

Sustainability is a major concern to humanity as a result of the consequences of the rapid consumption of the planets finite natural resources, combined with exponential economic and population growth. Principally associated with the field of ecology, sustainability has emerged as an important area of research in a number of sub-fields within the domain of computing including human-computer interaction. While these communities have attempted to address the challenges of sustainability from their different perspectives, there is a severe lack of common understanding of the fundamental concepts of sustainability and how they relate to software systems. As a result, there is a need for a common ground and consistent terminology to reduce the replication of effort. This paper presents the Karlskrona Manifesto for Sustainabilty Design as a mechanism for initiating a conversation between the different communities in addressing the challenges of developing sustainable software systems

Sustainability design in requirements engineering: state of practice

Sustainability is now a major concern in society, but there is little understanding of how it is perceived by software engineering professionals and how sustainability design can become an embedded part of software engineering process. This paper presents the results of a qualitative study exploring requirements engineering practitioners’ perceptions and attitudes towards sustainability. It identifies obstacles and mitigation strategies regarding the application of sustainability design principles in daily work life. The results of this study reveal several factors that can prevent sustainability design from becoming a first class citizen in software engineering: software practitioners tend to have a narrow understanding of the concept of sustainability; organizations show limited awareness of its potential opportunities and benefits; and the norms in the discipline are not conducive to sustainable outcomes. These findings suggest the need for focused efforts in sustainability education, but also a need to rethink professional norms and practices

Characterising Sustainability Requirements: A New Species, Red Herring, or Just an Odd Fish?

Abstract—Requirements articulating the needs of stakeholders are critical to successful system development and key to influ-encing their long-term effects. As the concept of sustainability has entered the discourse of a number of software-related computing fields, so has the term ‘sustainability requirement’. However, it is unclear whether sustainability requirements are and should be different from how we already understand software requirements. This paper presents the results of a corpus-assisted discourse analysis study that explored the concept of sustainability requirements in order to understand how the term is being used in software and requirements engineering and related fields. The results of this study reveal that the term ‘sustainability requirement’ is generally used ambiguously and reveals significant segmentation across different fields. Our detailed analysis of selected influential papers highlights the segmented use of the term and suggests key focus questions that need to be addressed to establish a shared operative understanding of the term

Temporal Discounting in Software Engineering : A Replication Study

Background: Many decisions made in Software Engineering practices are intertemporal choices: trade-offs in time between closer options with potential short-term benefit and future options with potential long-term benefit. However, how software professionals make intertemporal decisions is not well understood. Aim: This paper investigates how shifting time frames influence preferences in software projects in relation to purposefully selected background factors. Method: We investigate temporal discounting by replicating a questionnaire-based observational study. The replication uses a changed-population and -experimenter design to increase the internal and external validity of the original results. Results: The results of this study confirm the occurrence of temporal discounting in samples of both professional and student participants from different countries and demonstrate strong variance in discounting between study participants. We found that professional experience influenced discounting. Participants with broader professional experience exhibited less discounting than those with narrower experience. Conclusions: The results provide strong empirical support for the relevance and importance of temporal discounting in SE and the urgency of targeted interdisciplinary research to explore the underlying mechanisms and their theoretical and practical implications. The results suggest that technical debt management could be improved by increasing the breadth of experience available for critical decisions with long-term impact. In addition, the present study provides a methodological basis for replicating temporal discounting studies in software engineering.Peer reviewe

The Karlskrona manifesto for sustainability design

Sustainability is a central concern for our society, and software systems increasingly play a central role in it. As designers of software technology, we cause change and are responsible for the effects of our design choices. We recognize that there is a rapidly increasing awareness of the fundamental need and desire for a more sustainable world, and there is a lot of genuine goodwill. However, this alone will be ineffective unless we come to understand and address our persistent misperceptions. The Karlskrona Manifesto for Sustainability Design aims to initiate a much needed conversation in and beyond the software community by highlighting such perceptions and proposing a set of fundamental principles for sustainability design