A static inspection system and method for semi-formal requirements of rail transit vehicle-mounted software

Abstract

The invention relates to a static inspection system and method for semi-formal requirements of rail transit vehicle-mounted software, and the system comprises a grammatical analysis module which carries out the inspection and analysis of the requirements input into the grammatical analysis module, and generates an abstract syntax tree after the analysis is passed; an influence relationship analysis module taking the demand abstract syntax tree generated by the grammatical analysis module as input to analyze influence relationships among the demands; a type checking module used for analyzing type conversion among the demand variables and analyzing whether different types of demand variable assignment conditions exist or not if the types of the demand variables are defined in advance; and ifthe dimension of the demand variable is defined in advance, a dimension inspection module analyzing dimension conversion among the demand variables and analyzes whether variable assignment conditionsof different dimensions exist or not. Compared with the prior art, the method has the advantages that the demand verification efficiency can be improved, the time is saved, and the cost is reduced.

Description

technical field [0001] The invention relates to a static inspection system and method, in particular to a static inspection system and method for rail transit vehicle-mounted software semi-formal requirements. Background technique [0002] In the process of software development, requirements are a contract between users and product providers, or system analysts and development teams, and their quality affects the development progress and quality of the final product. An accurate, complete, consistent, and traceable requirements specification can avoid developers' understanding deviations and greatly help subsequent design, coding, and testing work; and, through detailed requirements analysis, potential problems can be found in the early stages of development , Repair in time, reduce the cost of dealing with the problem. [0003] In recent years, with the rapid development of my country's rail transit industry, the functional requirements of on-board controller software have...

AI Technical Summary

Problems solved by technology

[0006] (1) Relying on personal experience and lacking fixed quantitative standards; safety requires professionalism in software requirements description, and the semi-formal description method is relatively obscure. Inspectors must not only be proficient in business but also be familiar with the requirements description method. At the same time, the currently sampled Tools such as checklists tend to be qualitative and general;

[0007] (2) Heavy workload, easy omissions; safety-demanding software requirements Due to its accuracy requirements, there are many items and the content includes engineering calculations, the workload of manual inspection is heavy, and the cost is high. With the increase of the inspection cycle, the error rate often increases synchronously ;

[0008] (3) The cycle is long and cannot be checked online; a complete round of manual inspection often lasts for several weeks, and it is impossible to check every demand upgrade

Images