论文标题
针对软件强化系统的正式和半字体和技术要求建模的系统识别
A Systematic Identification of Formal and Semi-formalLanguages and Techniques for Software-intensiveSystems-of-Systems Requirements Modeling
论文作者
论文摘要
软件密集型系统系统(SOS)是指管理和操作独立系统(即组成系统)的安排,该系统在实现全球任务时协同工作。由于某些SO是针对关键领域(例如医疗保健和运输)开发的,因此越来越需要达到更高质量水平,这通常可以证明可以通过采用正式和半正式方法(即语言和技术)来建模的额外费用。已经采用了各种方法,但是仍然缺少详细的景观,尚不清楚它们是否适合解决SOS的固有特征。本文的主要贡献是通过报告SOS需求建模中的最新技术来介绍这一格局。该景观是通过系统的映射构建的,并显示了从基于模型到属性为导向的正式和半正式方法。它们中的大多数已经在安全关键领域进行了测试,其中正式的方法(例如有限状态机器)针对关键的系统零件,而半正式方法(例如,UML和I*)解决了非关键部件。尽管形式和半正式建模是一项重要活动,但SOS要求的质量不仅依赖于使用哪种形式主义,而且还依赖于支持工具/机制的可用性,例如,允许沿SOS LifeCycle的要求验证
Software-intensive Systems-of-Systems (SoS) refer to an arrangement of managerially and operationally independent systems(i.e., constituent systems), which work collaboratively towards the achievement of global missions. Because some SoS are developed for critical domains, such as healthcare and transportation, there is an increasing need to attain higher quality levels, which often justifies additional costs that can be incurred by adopting formal and semi-formal approaches (i.e., languages and techniques) for modeling requirements. Various approaches have been employed, but a detailed landscape is still missing, and it is not well known whether they are appropriate for addressing the inherent characteristics of SoS. The main contribution of this article is to present this landscape by reporting on the state of the art in SoS requirements modeling. This landscape was built by means of a systematic mapping and shows formal and semi-formal approaches grouped from model-based to property-oriented ones. Most of them have been tested in safety-critical domains, where formal approaches such as finite state machines are aimed at critical system parts, while semi-formal approaches (e.g., UML and i*) address non-critical parts. Although formal and semi-formal modeling is an essential activity, the quality of SoS requirements does not rely solely on which formalism is used, but also on the availability of supporting tools/mechanisms that enable, for instance, requirements verification along the SoS lifecycle