Software non-functional requirements address a multitude of objectives, expectations, and even liabilities that must be considered during development and operation. Typically, these non-functional requirements originate from different domains and their concrete scope, notion, and demarcation to functional requirements is often ambiguous. In this study we seek to categorize and analyze relevant work related to software engineering in a DevOps context in order to clarify the different focus areas, themes, and objectives underlying non-functional requirements and also to identify future research directions in this field. We conducted a systematic mapping study, including 142 selected primary studies, extracted the focus areas, and synthesized the themes and objectives of the described NFRs. In order to examine non-engineering-focused studies related to non-functional requirements in DevOps, we conducted a backward snowballing step and additionally included 17 primary studies. Our analysis revealed 7 recurrent focus areas and 41 themes that characterize NFRs in DevOps, along with typical objectives for these themes. Overall, the focus areas and themes of NFRs in DevOps are very diverse and reflect the different perspectives required to align software engineering with technical quality, business, compliance, and organizational considerations. The lack of methodological support for specifying, measuring, and evaluating fulfillment of these NFRs in DevOps-driven projects offers ample opportunities for future research in this field. Particularly, there is a need for empirically validated approaches for operationalizing non-engineering-focused objectives of software.
Enhancing Educational Efficiency: Generative AI Chatbots and DevOps in Education 4.0
State University of Novi Pazar（新帕扎尔国立大学）；University of Criminal Investigation and Police Studies（刑事侦查与警察研究大学）；Higher Technical Professional School in Zvečan（兹韦钱高等技术专业学院）；Academy Of Technical And Art Applied Studies Belgrade（贝尔格莱德技术与艺术应用研究学院）
AI Techniques in the Microservices Life-Cycle: A Systematic Mapping Study
Tampere University（塔尔皮奥大学）；University of Oulu（奥卢大学）；Technical University of Denmark（丹麦技术大学）；University of Bologna/INRIA（博洛尼亚大学/INRIA）；Inria（法国国家信息与自动化技术研究院）；Vrije Universiteit Amsterdam（阿姆斯特丹自由大学）；Pegaso Digital University（佩加索数字大学）；University of Pisa（比萨大学）；KU Leuven（鲁汶大学）
Tailoring Stakeholder Interests to Task-Oriented Functional Requirements
Without a specific functional context, non-functional requirements can only be approached as cross-cutting concerns and treated uniformly across all features of an application. This neglects, however, the heterogeneity of non-functional requirements that arises from stakeholder interests and the distinct functional scopes of software systems, which mutually influence how these non-functional requirements have to be satisfied. Earlier studies showed that the different types and objectives of non-functional requirements result in either vague or unbalanced specification of non-functional require…
A Systematic Analysis of Higher Education on Software Engineering in the Netherlands
Open University（开放大学）；Eindhoven University of Technology（埃因霍温理工大学）；University of Florence（佛罗伦萨大学）；University of Twente（特文特大学）；Utrecht University（乌得勒支大学）
Integrating Human-Centric Approaches into Undergraduate Software Engineering Education: A Scoping Review and Curriculum Analysis in the Australian Context
