Completeness in Software Requirements Specifications for Process Control Systems

这项工作的目标是提供一个严格的基础， 一组给定的软件需求是否在内部 完成. 这需要确定个人的类型 提供完整的功能和 性能规格沿着正式符号， 推理规则的发展和推导的闭合准则 要求. 这个问题对于经济和安全都很重要 原因 纠正要求的高成本和难度 软件开发后期的规范错误 过程意味着可以通过以下方法获得更大的杠杆作用， 有助于及早发现问题。 此外，大量与软件相关的 事故可以追溯到需求问题， 需求条款往往是一个偶然因素。 此外，正式 安全软件行为的分析不能通过测试来保证 单独;需要分析系统的指定行为 并且如果行为规范不完整，则这是不可能的。 重点将放在软件需求的各个方面 以前没有充分处理规范 包括时序抽象、人/机接口，以及 鲁棒性

The goal of this work is to provide a rigorous basis for ascertaining whether or not a given set of software requirements is internally complete. This will require determining the types of individual requirements that are necessary to provide complete functional and performance specifications along with a formal notation that will allow the development of rules of inference and closure criteria for derived requirements. This problem is important both for economic and safety reasons. The high cost and difficulty of correction requirements specification errors in the later stages of the software development process implies that great leverage can be obtained by methods that help to find problems early. Also, a large number of software-related accidents can be traced to requirements problems, and incompleteness in terms of requirements is often a casual factor. Furthermore, formal analysis of safe software behavior cannot be guaranteed by testing alone; analysis of the specified behavior of the system is necessary and this is not possible if the behavioral specification is incomplete. Emphasis will be placed on aspects of software requirements specification that have not previously been adequately handled including timing abstractions, the man/machine interface, and robustness.