当前位置: X-MOL 学术arXiv.cs.FL › 论文详情
Our official English website, www.x-mol.net, welcomes your feedback! (Note: you will need to create a separate account there.)
Validation Obligations: A Novel Approach to Check Compliance between Requirements and their Formal Specification
arXiv - CS - Formal Languages and Automata Theory Pub Date : 2021-02-11 , DOI: arxiv-2102.06037
Atif Mashkoor, Michael Leuschel, Alexander Egyed

Traditionally, practitioners use formal methods pre-dominately for one half of the quality-assurance process: verification (do we build the software right?). The other half -- validation (do we build the right software?) -- has been given comparatively little attention. While verification is the core of refinement-based formal methods, where each new refinement step must preserve all properties of its abstract model, validation is usually postponed until the latest stages of the development, when models can be automatically executed. Thus mistakes in requirements or in their interpretation are caught too late: usually at the end of the development process. In this paper, we present a novel approach to check compliance between requirements and their formal refinement-based specification during the earlier stages of development. Our proposed approach -- "validation obligations" -- is based on the simple idea that both verification and validation are an integral part of all refinement steps of a system.

中文翻译:

验证义务:一种检查需求与形式规范之间符合性的新颖方法

传统上,从业人员主要在质量保证过程的一半中使用形式化方法:验证(我们是否正确构建软件?)。另一半-验证(我们是否构建了正确的软件?)却很少受到关注。验证是基于优化的形式化方法的核心,其中每个新的优化步骤都必须保留其抽象模型的所有属性,而验证通常会推迟到开发的最新阶段,此时可以自动执行模型。因此,需求或其解释中的错误被发现为时已晚:通常是在开发过程的最后。在本文中,我们提出了一种新颖的方法,可以在开发的早期阶段检查需求与其基于正式改进的规范之间的符合性。
更新日期:2021-02-12
down
wechat
bug