The landscape of Software Engineering evolves rapidly amidst digital transformation and the ascendancy of AI, leading to profound shifts in the role and responsibilities of Software Engineers. This evolution encompasses both immediate changes, such as the adoption of Large Language Model-based approaches to coding, and deeper shifts driven by the profound societal and environmental impacts of technology. Despite the urgency, there persists a lag in adapting to these evolving roles. This roadmap article proposes 10 research challenges to develop a new generation of Software Engineers equipped to navigate the technical and social complexities as well as ethical considerations inherent in their evolving profession. Furthermore, the challenges target role definition, integration of AI, education transformation, standards evolution, and impact assessment to equip future Software Engineers to skillfully and responsibly handle the obstacles within their transforming discipline.

The world faces escalating crises: record-breaking temperatures, widespread fires, severe flooding, increased oceanic microplastics, and unequal resource distribution. Academia introduces courses around sustainability to meet the new demand, but software engineering education lags behind. While software systems contribute to environmental issues through high energy consumption, they also hold the potential for solutions, such as more efficient and equitable resource management. Yet, sustainability remains a low priority for many businesses, including those in the digital sector. Business as usual is no longer viable. A transformational change in software engineering education is urgently needed. We must move beyond traditional curriculum models and fully integrate sustainability into every aspect of software development. By embedding sustainability as a core competency, we can equip future engineers not only to minimise harm but also to innovate solutions that drive positive, sustainable change. Only with such a shift can software engineering education meet the demands of a world in crisis and prepare students to lead the next generation of sustainable technology. This article discusses a set of challenges and proposes a customisable education roadmap for integrating sustainability into the software engineering curricula. These challenges reflect our perspective on key considerations, stemming from regular, intensive discussions in regular workshops among the authors and the community, as well as our extensive research and teaching experience in the field.

Achieving the UN Sustainable Development Goals (SDGs) demands a shift by industry, governments, society, and individuals to reach adequate levels of awareness and actions to address sustainability challenges. Software systems will play an important role in moving towards these targets. Sustainability skills are necessary to support the development of software systems and to provide sustainable IT-supported services for citizens. While there is a growing number of academic bodies including sustainability education in engineering and computer science curricula, there is not yet comprehensive research on the competencies and skills required by IT professionals to develop such systems. This study aims to identify the industrial sustainability needs for education and training from software engineers’ perspective. For this, we answer the following questions: (1) what are the interests of organisations with an IT division with respect to sustainability? (2) what do organisations want to achieve with respect to sustainability, and how? and (3) what are the sustainability-related competencies and skills that organisations need to achieve their sustainability goals? We conducted a qualitative study with interviews and focus groups with experts from twenty-eight organisations with an IT division from nine countries to understand their interests, goals, and achievements related to sustainability, and the skills and competencies needed to achieve their goals. Our findings show that organisations are interested in sustainability, both idealistically and increasingly for core business reasons. They seek to improve the sustainability of software processes and products but encounter difficulties, like the trade-off between short-term financial profitability and long-term sustainability goals or an unclear understanding of sustainability concepts from a software engineering perspective. To fill these gaps, they have promoted in-house training courses, collaborated with universities, and sent employees to external training. The acquired competencies should support translating environmental and social benefits into economic ones and make sustainability an integral part of software development.

To foster a sustainable society within a sustainable environment, we must dramatically reshape our work and consumption activities, most of which are facilitated through software. Yet, most software engineers hardly consider the effects on the sustainability of the IT products and services they deliver. This issue is exacerbated by a lack of methods and tools for this purpose. Despite the practical need for methods and tools that explicitly support consideration of the effects that IT products and services have on the sustainability of their intended environments, such methods and tools remain largely unavailable. Thus, urgent research is needed to understand how to design such tools for the IT community properly. In this article, we describe our experience using design science to create the Sustainability Awareness Framework (SusAF), which supports software engineers in anticipating and mitigating the potential sustainability effects during system development. More specifically, we identify and present the challenges faced during this process. The challenges that we have faced and addressed in the development of the SusAF are likely to be relevant to others who aim to create methods and tools to integrate sustainability analysis into their IT products and services development. Thus, the lessons learned in SusAF development are shared for the benefit of researchers and other professionals who design tools for that end.

The Sustainable Development Goals (SDGs) of the United Nations focus on key issues for the transformation of our world towards sustainability. We argue for stronger integration of the SDGs into requirements and software engineering and for the creation of methods and tools that support the analysis of potential effects of software systems on sustainability in general and on SDGs in particular. To demonstrate one way of undertaking this integration, we report on how the Sustainability Awareness Framework (SusAF -- a tool developed by the authors of this paper) can be mapped to the SDGs, allowing the identification of potential effects of software systems on sustainability and on the SDGs. This mapping exercise demonstrates that it is possible for requirements engineers working on a specific system to consider that system's impact with respect to SDGs.

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.

Integrating novel software systems in our society, economy, and environment can have far-reaching effects. As a result, software systems should be designed in such a way as to maintain or improve the sustainability of the socio-technical system of their destination. However, a paradigm shift is required to raise awareness of software professionals on the potential sustainability effects of software systems. While Requirements Engineering is considered the key to driving this change, requirements engineers lack the knowledge, experience and methodological support for doing so. This paper presents a question-based framework for raising awareness of the potential effects of software systems on sustainability, as the first step towards enabling the required paradigm shift. A feasibility study of the framework was carried out with two groups of computer science students. The results of the study indicate that the framework helps enable discussions about potential effects that software systems could have on sustainability.

It is a fundamental right of every natural person to control which personal information is collected, stored and processed by whom, for what purposes and how long. In fact, many (cloud based) services can only be used if the user allows them broad data collection and analysis. Often, users can only decide to either give their data or not to participate in communities. The refusal to provide personal data results in significant drawbacks for social interaction. That is why we believe that there is a need for tools to control one's own data in an easy and effective way as protection against economic interest of global companies and their cloud computing systems (as data collector from apps, mobiles and services). Especially, as nowadays everybody is permanently online using different services and devices, users are often lacking the means to effectively control the access to their private data. Therefore, we present an approach to manage and distribute privacy settings: PRIVACY-AVARE is intended to enable users to centrally determine their data protection preferences and to apply them on different devices. Thus, users gain control over their data when using cloud based services. In this paper, we present the main idea of PRIVACY-AVARE.

Technical Debt arises from decisions that favour short-term outcomes at the cost of longer-term disadvantages. They may be taken knowingly or based on missing or incomplete awareness of the costs; they are taken in different roles, situations, stages and ways. Whatever technical or business factor motivate such decisions, they always imply a trade-off in time, a 'now vs. later'. How exactly are such decisions made, and how have they been studied?

Requirements Engineering (RE) plays a critical role in software system development and is argued to be the key leverage point for practitioners who want to design sustainable software-intensive systems. However, existing RE methods and tools do not explicitly facilitate the discussion and negotiation of sustainability-related concerns. This leads to insufficient or onedimensional perceptions of sustainability. In this paper, we discuss our understanding of sustainability and its relationship with requirements. Based on the outcomes of this discussion, we have extended the WinWin Negotiation Model by incorporating sustainability concepts so that the negotiation also includes the ability to consider the impact of requirements on sustainability. Applying this negotiation method in an exploratory industrial case study, we have learned that this approach stimulates the discussion on sustainability and its multiple dimensions. It also allows practitioners to reflect on requirements and their effects on sustainability. However, we have also observed that further in-depth requirements analysis is needed to analyse the long-term effects of requirements regarding sustainability.

Continuous requirements elicitation is an essential aspect of software product evolution to keep systems aligned with changing user needs. However, current requirements engineering approaches do not explicitly address sustainability in the evolution of systems. Reasons include a lack of awareness and a lack of shared understanding of the concept of sustainability in the RE community. Identifying and analysing the effects of requirements regarding sustainability is challenging, as these effects can have an impact on multiple stakeholders and manifest themselves in one or more sustainability dimensions at different points in time. We argue that crowd-focused semi-automated requirements engineering allows the engagement of a large number of stakeholders (including users and domain experts) in a continuous cycle of negotiation regarding the potential effects of requirements on sustainability. Based on a motivating scenario, we introduce the idea of a platform for crowd-focused requirements engineering that supports the evolution towards sustainability. For the three key aspects of this platform, we present our ongoing work and discuss early results. We outline how the platform can be utilised to improve the broader awareness and understanding of sustainability, not only for the involved crowd but also for researchers and society in general.

Goal models and business process models are used to document the business requirements. Goal models describe the organizational concepts using a high abstraction level. They are modeling the intentions and strategies of stakeholders. Business process models, on the other hand, provide detailed descriptions on how these organizational goals are to be fulfilled. To ensure consistency among organizational goals and business process models several approaches to derive business processes from goal models have been proposed. However, a key weakness of these approaches is that they don't express quality requirements in business process models. Thus, in this paper we present AAISP a new approach for aligning information systems perspectives. We first define an extended goal model that comprises the relevant stakeholder requirements. Then, we list mapping rules for the extended goal model and the business process concepts and finally, based on these rules we present an algorithm to transform the extended goal model into a BPMN model.

Abstract Knowledge transfer is a critical factor in ensuring the success of offshore outsourcing software development projects and is, in many cases, neglected. Compared to in‐house or co‐located projects, however, such globally distributed projects feature far greater complexity. In addition to language barriers, factors such as cultural differences, time zone variance, distinct methods and practices, as well as unique equipment and infrastructure can all lead to problems that negatively impact knowledge transfer, and as a result, a project's overall success. In order to help minimise such risks to knowledge transfer, we conducted a research study based on expert interviews in six projects. Our study used German clients and focused on offshore outsourcing software development projects. We first identified known problems in knowledge transfer that can occur with offshore outsourcing projects. Then we collected best‐practice solutions proven to overcome the types of problems described. Afterward, we conducted a follow‐up study to evaluate our findings. In this subsequent stage, we presented our findings to a different group of experts in five projects and asked them to evaluate these solutions and recommendations in terms of our original goal, namely to find ways to minimise knowledge‐transfer problems in offshore outsourcing software development projects. Thus, the result of our study is a catalog of evaluated solutions and associated recommendations mapped to the identified problem areas.

In this paper we investigate the current state of work regarding alignment of Business, Architecture, Process, and Organisation (BAPO) perspectives in a software product development context. We planned to do that by conducting a systematic literature study to capture the state of the art in alignment of BAPO in software development. But, as it turned out we found that almost no substantial information is available about the alignment of BAPO in software development. Thus, based on the available literature and a small qualitative study, we defined a conceptual model of the alignment of BAPO including five levels of alignment that can be used as a basis for future empirical studies.

Knowledge transfer is one of the most critical success factors in IT offshore outsourcing projects and in many cases extremely underestimated. Compared to in-house or onsite projects, a much higher complexity appears in globally distributed projects. Not only language barriers but also other challenges such as cultural differences, diverse time-zones, distinct methods and approaches, as well as varied infrastructural equipment, may cause problems which negatively impact knowledge transfer, and in consequence, the overall success of a project. In order to minimize risks during knowledge transfer, we conducted a research study based on a literature review and expert interviews. The result of our study was a collection and description of best practices and the development of recommendations by linking proven solutions to identified problem areas.

Offshoring is a widely used practice in the software development. It is mainly employed to reduce development costs. However, as in a number of studies have been shown, about 40 percent of offshore software development projects are flops. One predominant reason for it is the lack of standardized and practicable methods of risk management due to the inherent complexity of software development offshoring. Therefore, suitable methods and tools for the risk management specific to such projects are required. Firstly, this workshop will provide an insight into various aspects of the risk management of offshore software development. Secondly, tools and methods for the risk management will be discussed and presented. Thirdly, priorities for further research will be identified. The results of this workshop will, on the one hand, benefit companies sharing in the software development offshoring and, on the other hand, academics to identify the demand in the further research.