Semi-formal requirements verification system and method for vehicle controller software based on smt

Abstract

The present invention relates to a semi-formal requirement verification system and method for vehicle controller software based on SMT. Conjunctive normal form recognized by the SMT solver is input; the constraint condition establishment module M2 is used to extract, summarize and establish constraints for software functions according to the upper-level system requirements and system design; the requirement verification module M3 is used to convert the format The final input software requirements are solved according to the constraints to verify the correctness of the software requirements and the consistency with the superior requirements and design. Compared with the prior art, the present invention has the advantages of accurately and efficiently verifying semi-formalized software requirements by using formalized theoretical tools.

Description

technical field [0001] The invention relates to a semi-formal requirement verification system for rail transit vehicle-mounted controller software, in particular to a semi-formalized requirement verification system and method for vehicle-mounted controller software based on SMT (Satisfiability Model Theory). Background technique [0002] With the rapid development of my country's rail transit industry, the functional requirements of on-board controller software are becoming more and more complex, which brings great pressure to the related software quality assurance work. Industrial data shows that about 50% of product defects are caused by insufficient quality requirements, and about 80% of rework workload can be traced back to requirement defects, especially for high-reliability embedded software such as rail transit on-board controllers , the defects of its requirements specifications will cause immeasurable property losses and casualties; on the other hand, the omissions ...

AI Technical Summary

Problems solved by technology

At present, high-confidence embedded software mostly uses semi-formal description methods such as state machines, truth tables, sequence diagrams, and flow charts, but the corresponding requirements verification methods are mainly document review and prototype demonstration technologies. The experience and sense of responsibility of the personnel are extremely high

[0004] And this method of manually verifying requirements has the following deficiencies: (1) Due to manual inspection, there may be cases where the inspection is not in place, omissions occur, and even the expected verification effect cannot be achieved

(2) The essence of manual verification is still empirical behavior, which has extremely high requirements on the ability of verification personnel. At the same time, there is a lack of unified norms and standards, and there is limited room for improvement in terms of quality and efficiency.

Images