Minimising conflicts among run‐time non‐functional requirements within DevOps

IF 1.6 3区工程技术 Q4 ENGINEERING, INDUSTRIAL

Systems Engineering Pub Date : 2023-08-16 DOI:10.1002/sys.21715

Souvick Das, Novarun Deb, N. Chaki, Agostino Cortesi

引用次数: 0

Abstract

Significant contributions in the existing literature highlight the potential of softgoal interdependency graphs towards analyzing conflicting non‐functional requirements (NFRs). However, such analysis is often at a very abstract level and does not quite consider the run‐time performance statistics of NFR operationalizations. On the contrary, some initial empirical evaluations demonstrate the importance of the run‐time statistics. In this paper, a framework is proposed that uses these statistics and combines the same with NFR priorities for computing the impact of NFR conflicts. The proposed framework is capable of identifying the best possible set of NFR operationalizations that minimizes the impact of conflicting NFRs. A detailed space analysis of the solution framework helps proving the efficiency of the proposed pruning mechanism in terms of better space management. Furthermore, a Dynamic Bayesian Network (DBN) ‐ based system behavioral model that works on top of the proposed framework, is defined and analyzed. An appropriate tool prototype for the framework is implemented as part of this research.

查看原文本刊更多论文

最小化DevOps中运行时非功能需求之间的冲突

现有文献中的重要贡献突出了软目标相互依存图在分析冲突的非功能需求（NFR）方面的潜力。然而，这种分析通常处于非常抽象的水平，并没有完全考虑NFR操作的运行时性能统计。相反，一些初步的实证评估表明了运行时统计数据的重要性。在本文中，提出了一个框架，该框架使用这些统计数据，并将其与NFR优先级相结合，以计算NFR冲突的影响。拟议的框架能够确定尽可能好的NFR操作集，最大限度地减少冲突的NFR的影响。解决方案框架的详细空间分析有助于证明所提出的修剪机制在更好的空间管理方面的效率。此外，在所提出的框架之上，定义并分析了一个基于动态贝叶斯网络（DBN）的系统行为模型。作为本研究的一部分，实现了该框架的适当工具原型。

本文章由计算机程序翻译，如有差异，请以英文原文为准。

求助全文

约1分钟内获得全文求助全文

来源期刊

Systems Engineering 工程技术-工程：工业

CiteScore

5.10

自引率

20.00%

发文量

审稿时长

6 months

期刊介绍： Systems Engineering is a discipline whose responsibility it is to create and operate technologically enabled systems that satisfy stakeholder needs throughout their life cycle. Systems engineers reduce ambiguity by clearly defining stakeholder needs and customer requirements, they focus creativity by developing a system’s architecture and design and they manage the system’s complexity over time. Considerations taken into account by systems engineers include, among others, quality, cost and schedule, risk and opportunity under uncertainty, manufacturing and realization, performance and safety during operations, training and support, as well as disposal and recycling at the end of life. The journal welcomes original submissions in the field of Systems Engineering as defined above, but also encourages contributions that take an even broader perspective including the design and operation of systems-of-systems, the application of Systems Engineering to enterprises and complex socio-technical systems, the identification, selection and development of systems engineers as well as the evolution of systems and systems-of-systems over their entire lifecycle. Systems Engineering integrates all the disciplines and specialty groups into a coordinated team effort forming a structured development process that proceeds from concept to realization to operation. Increasingly important topics in Systems Engineering include the role of executable languages and models of systems, the concurrent use of physical and virtual prototyping, as well as the deployment of agile processes. Systems Engineering considers both the business and the technical needs of all stakeholders with the goal of providing a quality product that meets the user needs. Systems Engineering may be applied not only to products and services in the private sector but also to public infrastructures and socio-technical systems whose precise boundaries are often challenging to define.