Focus Areas, Themes, and Objectives of Non-Functional Requirements in DevOps: A Systematic Mapping Study

Haindl, Philipp; Plösch, Reinhold

doi:10.1109/seaa51224.2020.00071

Cited by 6 publications

(10 citation statements)

References 91 publications

(137 reference statements)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In this work, we presented the results from an online survey with practitioners to assess the practical relevance of 61 metrics for particular value criteria and also identify possible sources for their measurement. The metrics were extracted from the papers analysed in our systematic mapping study [12], which unveiled the lack of empirical data regarding the practical relevance of value-oriented metrics. In order to define the metrics using common terminology and regard particularities important in practice, we also conducted a complementary narrative literature search.…”

Section: Discussionmentioning

confidence: 99%

“…The metrics were identified through our preceding systematic mapping study examining NFRs, as indicators of the stakeholders' value considerations [12].…”

Section: Categorisation Of Metricsmentioning

confidence: 99%

“…Based on these aspects, we grouped the metrics examined in the survey according to four main perspectives: financial and market performance , customer satisfaction , value creation , and value proposition . The metrics were identified through our preceding systematic mapping study examining NFRs, as indicators of the stakeholders' value considerations [12].…”

Section: Categorisation Of Metricsmentioning

confidence: 99%

“…To address this challenge and to identify the metrics relevant for the stakeholders' value appraisal of software, we conducted a systematic mapping study about NFRs in DevOps [12]. Thereby, we carved out recurrent focus areas and themes of NFRs in DevOps that reflect relevant value considerations of stakeholders and derived quality metrics thereof.…”

Section: Related Workmentioning

confidence: 99%

“…This paper seeks to close this research gap by presenting a concrete list and categorisation of practically relevant value‐oriented quality metrics. The metrics are based on our former systematic mapping study of over 140 papers [12] and a complementary narrative literature review. The relevance and completeness of these metrics were assessed based on the results from a survey with 41 practitioners who have different roles in the software product lifecycle.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Value‐oriented quality metrics in software development: Practical relevance from a software engineering perspective

Haindl

Plösch

2021

IET Software

Self Cite

View full text Add to dashboard Cite

When following the principles of value-based software engineering, business, customer satisfaction, and engineering considerations need to be balanced to develop and operate the software so that it satisfies the different stakeholders' expectations. This, however, requires knowing the relevant quality metrics covering these value-oriented expectations and potential sources for their measurement. In this work, a categorisation of valueoriented quality metrics that are practically relevant is presented. Therefore, the authors conducted an online survey with practitioners who assessed the relevance of 61 value-oriented metrics, gathered from a preceding systematic mapping study. The authors grouped these metrics into 10 categories, based on financial, customer satisfaction, value proposition, and creation perspectives. Also, the authors examined the frequency of particular steps at which these measures accrue and identified their most relevant data sources. The participants rated metrics for feature reliability, performance, as well as test and development efficiency as most relevant for value orientation. According to the participants, the authors' collection covers all relevant metrics for addressing financial and market and feature usability aspects. The authors' categorisation and the metrics' relevance assessments shall support software engineers in selecting relevant metrics and their sources for software product development. K E Y W O R D S software development management, software engineering, software metrics, software qualityThis is an open access article under the terms of the Creative Commons Attribution-NonCommercial License, which permits use, distribution and reproduction in any medium, provided the original work is properly cited and is not used for commercial purposes.

show abstract

Section: Discussionmentioning

confidence: 99%

“…The metrics were identified through our preceding systematic mapping study examining NFRs, as indicators of the stakeholders' value considerations [12].…”

Section: Categorisation Of Metricsmentioning

confidence: 99%

Section: Categorisation Of Metricsmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Value‐oriented quality metrics in software development: Practical relevance from a software engineering perspective

Haindl

Plösch

2021

IET Software

Self Cite

View full text Add to dashboard Cite

show abstract

DevOps Challenges in Organizations: Through Professional Lens

Azad

Hyrynsalmi

2022

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

DevOps is a set of organizational practices as well as a culture which tries to eliminate the barriers between the Devs and Ops teams, improve the collaboration and communication among teammates. DevOps is used in different organizations because it supports quicker production, stability and reliability for software development. While the success factors of DevOps adoption have been studied in the extant literature, also the perceived challenges that a company faces during the adoption are crucial to discover. This paper explores and highlights these challenges through an open ended survey (N=15) and in-depth interviews with DevOps professionals (N=16). According to the findings, there are various challenges while implementing DevOps in the organizations. The research suggests that (i) lack of team coordination, (ii) risky change and development, (iii) team members expertise level, (iv) lack of focus or differences in development, (v) test and production environment, (vi) poorly defined functional and technical requirements, (vii) poor integration and test process, (viii) pipeline execution problems, (ix) tools integration challenges, (x) people challenges and silo-ed thinking, (xi) debugging challenges due to remote execution, (xii) feature release challenges, (xiii) integrating new standards, (xiv) challenges with clients, (xv) knowledge sharing, (xvi) responsibility distribution issues are the challenges while using DevOps. The founded list of perceived challenges will help future research to suggest mitigation and risk management strategies for successful use of DevOps.

show abstract

Requirements management in DevOps environments: a multivocal mapping study

2023

View full text Add to dashboard Cite

Attention is currently being focused on DevOps, which aims to reduce software development time by means of close collaboration between the development and operations areas. However, little effort has been made to determine the role of requirements management in DevOps. The objective of this study is to help both researchers and practitioners by providing an overview of the best practices regarding requirements engineering in DevOps and identifying which areas still need to be investigated. A multivocal mapping study has, therefore, been carried out in order to study which methodologies, techniques and tools are used to support requirements management in DevOps environments. After applying the review protocol, 37 papers from formal literature and 14 references from grey literature were selected for analysis. The general conclusions obtained after analysing these papers were that, within DevOps, more attention should be paid to: (1) the reuse of requirements in order to identify systems and software artefacts that can serve as a basis for the specification of new projects; (2) the communication of requirements between the different areas of an organisation and the stakeholders of a project; (3) the traceability of requirements in order to identify the relationship with other requirements, artefacts, tasks and processes; (4) non-functional requirements in order to identify the requirements of the operations area in the early phases of a project; and finally (5) specific requirements tools that should be seamlessly integrated into the DevOps toolchain. All these issues must be considered without ignoring the agile and continuous practices of development, operations and business teams. More effort must also be made to validate new methodologies in industry so as to assess and determine their strengths and weaknesses.

show abstract

Focus Areas, Themes, and Objectives of Non-Functional Requirements in DevOps: A Systematic Mapping Study

Cited by 6 publications

References 91 publications

Value‐oriented quality metrics in software development: Practical relevance from a software engineering perspective

Value‐oriented quality metrics in software development: Practical relevance from a software engineering perspective

DevOps Challenges in Organizations: Through Professional Lens

Requirements management in DevOps environments: a multivocal mapping study

Contact Info

Product

Resources

About