Property-driven model for finding safety issues文献综述

 2022-07-15 03:07

Property-driven analysis in component-driven models
文献综述

THEME: Property-driven analysis in component-driven models

Abstract: In software engineering process, requirements engineering is a major software engineering activity that begins during the communication activity and continues into the design activity. Requirements builds a bridge to design and construction of software. Most requirements are specified on the assumption that the systemrsquo;s operating environment will behave in an expected manner, while off-normal behaviors (ONB) which are unintended and unusual behaviors can result in critical situations [1]. A causal component model (CCM) approach has been proposed, which can expose ONBs within a set of natural language (NL) requirements.

However, there are some limitations in specifying the scope of a safety issue in CCM model, which does not take the properties of components into account. Ignoring properties might result in incomplete analysis of requirements. Therefore, we want to add the property of the components as a model element to facilitate the model for the ONBs analysis. When adding the property of the components to the CCM, we can expose more safety issues than CCM. In additional, it can help figure out the relations between components, which will be helpful in our future work in reducing the redundancy in rules. The figure 1 shows the difference between CCM and property-driven model.

Keywords:off-nominal behaviors, requirements, property-driven

前言

在软件工程过程中,需求工程是一项主要的软件工程活动,在通信活动期与设计活动期架起了沟通的桥梁。需求分析为软件的设计和构建搭建了桥梁。现存的需求分析大多数是在假设系统的操作环境将以预期方式运行的情况下指定的,而非正常行为(ONB)是非预期和异常行为可能导致危急情况。已经提出了一种因果组件模型(CCM)方法,其可以在一组自然语言(NL)要求中公开ONB。

但是,在CCM模型中指定安全问题的范围存在一些限制,该模型不考虑组件的属性。忽略属性可能导致对需求的分析不完整。因此,我们希望将组件的属性添加为模型元素,以便于ONB分析的模型。将组件的属性添加到CCM时,我们可能会发现比CCM更多的安全问题。另外,它可以帮助找出组件之间的关系,这将有助于我们今后减少规则冗余的工作。图1显示了CCM和属性驱动模型之间的区别。

研究的目的与意义

剩余内容已隐藏,您需要先支付 5元 才能查看该篇文章全部内容!立即支付

以上是毕业论文文献综述,课题毕业论文、任务书、外文翻译、程序设计、图纸设计等资料可联系客服协助查找。