Like other communities, sustainability in and for software design is a grand research and development challenge. Current research focuses on eliciting the meanings of sustainability and on building approaches for its engineering and integration into the mainstream software development lifecycle. However, few concrete guidelines that software designers can apply effectively are available. A guideline aims to streamline the design processes according to a set of well-known research routines or sound industry practices. Such guidelines can help software developers in the elicitation of sustainability requirements and testing software against these requirements. This paper introduces a sustainability design catalogue (SSDC) comprising a series of guidelines. It aims to assist software developers and managers in eliciting sustainability requirements, and then in measuring and testing software sustainability. The catalogue is based on reviews of the current and past research on sustainability in software engineering, which are the grounds for the development of the catalogue. Four different case studies were analyzed using the Karlskrona manifesto principles on sustainability design. A pilot framework is also proposed that includes a set of sustainability goals, concepts and methods. It exemplifies how to apply and quantify sustainability.

No abstract

Academic research and existing implementations of various systems and services identify instances of conflict between security and usability. Engineering the right trade-offs between security and usability is often not an easy task. Engineering of such trade-offs is mainly reliant on developers' skills, who are either experts in security or usability. This research aims to assist the developers in engineering the right trade-offs by proposing the use of patterns. Patterns provide benefits like means of common vocabulary, shared documentation, reuse, among others. The use of patterns can assist security and usability developers by influencing their decision-making abilities when dealing with conflicts in other but similar context of use. For the identification of such patterns, the paper presents a three-stage methodology. To instantiate the methodology, a case study was conducted whose results are also presented in the paper.

In this paper, we propose when and how to perform sustainability assessment during software product and service inception, development, and evolution.We explain the challenge of right timings for sustainability assessments, how they are often delayed due to missing focus on values during the early development phases. We refer to a current solution, called SusAF, and discuss some of its challenges.We wrap up by advocating for a legal regulation supporting the actual implementation of sustainability assessments alike with how they are required in civil engineering.

Software engineering as a discipline has recognized that software systems can have an impact on sustainability and researchers have started to investigate this topic. New knowledge is being created and methods and tools that support software engineering for sustainability are emerging. Several universities have started to train their students in software engineering for sustainability. But what about the millions of SE practitioners who are already designing and developing future software systems -how would they know about making systems sustainable? Currently, there is a lack of consolidated guidance. In this paper, we promote the idea of developing a standardized curriculum and handbook as a basis for training and certification of practitioners in sustainable software development. This would not only increase their market value, but would also have a positive impact on their companies and could help to satisfy customers who demand sustainable software systems.