Emergent knowledge patterns in verification artifacts

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

Systems Engineering Pub Date : 2024-06-13 DOI:10.1002/sys.21771

Sukhwan Jung, A. Salado

引用次数: 0

Abstract

Knowledge graphs have recently been introduced to the verification strategy field successfully representing the complexity of verification in real‐life applications. This format provides a scale‐free analysis of verification strategies compared to the more traditional verification artifacts such as requirement traceability matrices and verification matrices. Complexities can be observed visually and numerically both in terms of the problem scope and the entity interdependencies. In this paper, we retrieve verification strategy information patterns representing different aspects of verification. This is achieved by tapping into the network properties of knowledge graphs. They are dissected to detect knowledge patterns emerging from different parts of the verification artifacts. Similarities and differences between the two verification strategies are explained numerically and semantically. Seemingly unrelated requirements and verification activities are connected through indirect connections, and orthogonalities between independent requirements are analyzed. These findings validate the scalability of verification planning and assessment based on knowledge graphs.

查看原文本刊更多论文

验证工件中的新兴知识模式

知识图谱最近被引入验证策略领域，成功地体现了现实应用中验证的复杂性。与需求可追溯性矩阵和验证矩阵等更传统的验证工件相比，这种格式提供了对验证策略的无标度分析。可以从问题范围和实体相互依存关系两方面直观地观察和计算复杂性。在本文中，我们检索了代表验证不同方面的验证策略信息模式。这是通过挖掘知识图谱的网络属性实现的。我们对知识图谱进行剖析，以检测从验证工件的不同部分中产生的知识模式。从数字和语义上解释两种验证策略的异同。通过间接连接将看似不相关的需求和验证活动联系起来，并分析独立需求之间的正交性。这些发现验证了基于知识图谱的验证规划和评估的可扩展性。

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

求助全文

约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.