Static inspection system and method for semi-formal requirements of rail transit vehicle software

Abstract

The invention relates to a static inspection system and method for semi-formal requirements of rail transit vehicle-mounted software. The system includes: a syntax analysis module checks and analyzes the requirements of the input syntax analysis module, and generates an abstract syntax tree after passing the inspection; the influence relationship analysis module uses The requirement abstract syntax tree generated by the syntax analysis module is used as input to analyze the influence relationship between each requirement; the type checking module, if the type of the requirement variable has been defined in advance, then analyze the type conversion between the requirement variables and whether there is a difference Assignment of type demand variables; if the dimension check module has defined the dimension of demand variables in advance, it will analyze the dimensional conversion between demand variables and whether there are variable assignments of different dimensions. Compared with the prior art, the invention has the advantages of improving the efficiency of requirement verification, saving time, reducing costs and the like.

Description

technical field [0001] The invention relates to a static inspection system and method, in particular to a static inspection system and method for semi-formalized requirements of rail transit on-board software. Background technique [0002] In the process of software development, requirements are contracts between users and product providers, or between 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' misunderstandings 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 it in time, and 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 softwar...

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