Background: Supporting sustainability in software engineering is becoming an active area of research and we want to contribute the first SLR in this field. Researchers who are motivated to contribute to that topic need to accumulate a body of knowledge as starting point through time-consuming literature research. Aim: We aim to provide an overview of different aspects of sustainability in software engineer- ing research with regard to research activity, investigated topics, identified limitations, proposed approaches, used methods, available studies, and considered domains. Method: The applied method is a Systematic Literature Review (SLR) in five reliable and commonly-used databases according to the (quasi-standard) protocol by Kitchenham et al. [288]. We assessed the 100 first results of each database ordered by relevance with respect to the search query. Results: Of 500 classified publications, we regard 96 as relevant for our research questions. Most of the excluded publications were ruled out because of an unfitting usage of terms within the search query. We sketch a taxonomy of their topics and domains, and provide lists of used methods and proposed approaches. Conclusions: Currently, there is little research coverage on the different aspects of sustainability in software engineering. Future work includes extending the study by reviewing a higher number of publications, including dedicated journal and workshop searches, and snowballing.

https://mediatum.ub.tum.de/doc/1100401/file.pdf

Sustainability in Software Engineering: A Systematic Literature Review for Building up a Knowledge Base

Crowdsourcing has emerged as a new paradigm for outsourcing simple for humans yet hard to automate tasks to an undefined network of people. Crowdsourcing platforms like Amazon Mechanical Turk provide scalability and flexibility for customers that need to get manifold similar independent jobs done. However, such platforms do not provide certain guarantees for their services regarding the expected job quality and the time of processing, although such guarantees are advantageous from the perspective of Business Process Management. In this paper, we consider an alternative architecture of a crowdsourcing platform, where the workers are assigned to tasks by the platform according to their availability and skills. We propose the technique for estimating accomplishable guarantees and negotiating Service Level Agreements in such an environment.

/pdf/predicting-qos-in-scheduled-crowdsourcing-37md6h2c8f.pdf

Predicting qos in scheduled crowdsourcing

Goal modelling and business process modelling are two techniques that can be used for elicitation of system requirements of an information system. In general, goal-based approaches aim at supporting the objectives that an organization needs to achieve, whereas business process-based approaches aim at supporting the activity of an organization. Consequently, it could be assumed that these two types of approaches represent completely different perspectives for elicitation of system requirements. In this paper we argue that a correspondence exists between the perspectives and that they can be considered equivalent in some operational aspects. Therefore, the use of a perspective also implies support for the other. This argument is based on the definition of a set of guidelines that shows how a goal model can be derived from a business process model. As a result, we discuss when selection of one of the perspectives or their combination would be more suitable for requirements elicitation.

On the Use of Goal Models and Business Process Models for Elicitation of System Requirements

A maturity model for secure requirements engineering

Alignment is a very wide subject that can be used to support an organization’s information system. Many authors have dealt with this topic according to various dimensions, including the operational alignment dimension. Our work aims to review approaches that discuss the operational alignment by reducing the gap between business requirement, business process, and software system. Therefore, this study was conducted by a systematic literature review (SLR). In the first step, we gather 1846 papers relative to the subject. In the last step, we filter those articles and select only the most pertinent ones, which leave us with 63 studies to focus on. These primary studies were analyzed according to 9 quality assessment criteria.

https://downloads.hindawi.com/journals/je/2019/6918105.pdf

Alignment between Business Requirement, Business Process, and Software System: A Systematic Literature Review

https://pure.rug.nl/ws/files/2538598/2011JSystSoftwFrankova.pdf

Florian Gilcher

Papers

Deriving business processes with service level agreements from early requirements