A software quality control method based on research and development evidence chain traceability index

Abstract

The application discloses a software quality control method based on R&D evidence chain tracing indexes, which comprises the following steps: 1. completing the definition of the software R&D evidence chain, and abstracting the definition of the evidence chain objective tracing indexes; 2. completing the definition of the standard working environment used in the software R&D process, stipulating the special attribute marks of the related working products, and standardizing the submission path and format requirements of the working products; 3. according to the special attribute marks of the submitted standard working products, completing the statistics of the objective index data required by the evidence chain, and storing the data in a database; 4. using FineReport software to read the data from the database, classifying and displaying the data, automatically marking the achievement of each index, and completing the identification of the quality and the use boundary. The application can quickly realize the statistics of the evidence chain objective tracing index data based on the standard working environment and the working products in the software R&D process, and quickly evaluate the process and the product quality of the delivered software.

Description

TECHNICAL FIELD

[0001] The present application relates to software engineering, in particular to a software quality control method based on R&D evidence chain traceability index. BACKGROUND

[0002] The aero-engine control system (FADEC) is the brain of the engine, controls the operation of the engine, and is an important part of the aero-engine. The control software, as an important part of the control system, is defined as safety-critical software, and its safe and stable operation is particularly important. The software product quality is invisible in itself. At present, the control of the software product quality is mostly based on the overall test result measurement index such as test defect rate and test case density to evaluate the sufficiency of software testing, and then to evaluate the overall product quality status of the software. The sufficiency of this method for measuring the good and bad of the software product quality based on the relatively single overall index is slightly insufficient.

[0003] Based on the idea that the final product quality is determined by the process quality, combined with the traceability requirements in the airworthiness requirements of airborne software, it is believed that the alignment of the process evidence chain has a decisive influence on the final product quality of the software. However, the transmission of the software R&D process evidence chain at present is mostly through the documentation method. The consistency and traceability between these thousands of pages of documents can only be reviewed manually, which is low in efficiency and difficult to guarantee the effectiveness. SUMMARY

[0004] The purpose of the present application is to provide a software quality control method based on R&D evidence chain traceability index, so as to assist the software quality assurance personnel in releasing the export conditions of the software, and to timely execute the subsequent quality improvement plan.

[0005] Technical scheme: based on the requirements of software engineering, the definition of software R&D evidence chain is completed, and the definition of objective traceability index of evidence chain is abstracted; through the definition of standard working environment, standard working product and special identification attribute of software R&D process, the rapid grabbing of objective traceability index data is completed by using information data statistical script, and the data is stored in the database; the rapid manifestation of software version statistical data and the identification of quality color and use scene constraint are completed by using commercial report platform.

[0006] The software quality control method based on R&D evidence chain traceability index provided by the present application comprises the following steps:

[0007] (1) based on the requirements of software engineering, the definition of software R&D evidence chain is completed, and the definition of objective traceability index of evidence chain is abstracted;

[0008] (2) According to the definition of the index, the definition of the standard working environment used in the software development process is completed, and the special attribute mark of the related working product is agreed, and the submission path and format requirement of the working product are specified;

[0009] (3) According to the special attribute mark of the submitted standard working product, the objective index data required by the evidence chain is completed, and the data is stored in the database;

[0010] (4) Using FineReport software, the data is read from the database for classification display, and the achievement of each index is automatically marked, and the quality color and use boundary are identified according to different combinations of index achievement.

[0011] The step (4) comprises the following steps:

[0012] (4.1) Complete the quality color definition based on the different situations of the evidence chain index;

[0013] (4.2) Edit the development SQL statement to filter the required data unit from the database;

[0014] (4.3) In the FineReport front-end IDE environment, the UI display interface development based on the version quality color definition is completed.

[0015] The software development evidence chain in step (1) is: software development requirement SDTD→software development requirement SRS→code CODE→static analysis scanning→unit test UT→test requirement STR→test case STC.

[0016] The evidence chain objective traceability index in step (1) comprises: The bidirectional traceability percentage, the number of static analysis scanning problems, The bidirectional traceability percentage, The bidirectional traceability percentage of requirement STR, The bidirectional traceability percentage of requirement STR, the number of full regression system test cases STC execution, the number of full regression unit test functions UT execution.

[0017] The attribute mark in step (3) comprises the mark of software requirement analysis process, the mark of design implementation process and the mark of test process.

[0018] A computer storage medium, which stores a computer program, the computer program is executed by a processor to realize the above-mentioned software quality control method based on development evidence chain traceability index.

[0019] A computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the above-described software quality control method based on a research and development evidence chain traceability index.

[0020] Beneficial effects: Compared with the prior art, the present invention has the following advantages:

[0021] 1. It can quickly collect objective traceability data of evidence chain based on the standard working environment and work products in the software development process, and quickly evaluate the process and quality of the delivered software based on these objective statistical data;

[0022] 2. It can assess the risks of software delivery and use based on identified deviations. On the one hand, it can assist software quality assurance personnel in determining the exit conditions for software release and promptly implementing subsequent quality improvement plans; on the other hand, it can clearly convey the quality of the software and usage boundary constraints to the customer, effectively avoiding the risk of software defect leakage at the customer's site. Attached Figure Description

[0023] Figure 1 A schematic diagram illustrating the design of a software quality control method based on R&D evidence chain traceability indicators;

[0024] Figure 2 This is a schematic diagram of the standard working environment catalog;

[0025] Figure 3 This is a schematic diagram illustrating the mutual traceability between SDTD and SRS.

[0026] Figure 4 This is a schematic diagram of the main issues to be identified in the static analysis.

[0027] Figure 5 This is a schematic diagram of a sample product for testing purposes.

[0028] Figure 6 This is a schematic diagram of the software quality assessment results based on the traceability indicators of the R&D evidence chain. Detailed Implementation

[0029] The technical solution of the present invention will be further described below with reference to the accompanying drawings.

[0030] like Figure 1 As shown, a software quality control method based on R&D evidence chain traceability indicators includes the following steps:

[0031] (1) Based on the requirements of software engineering, define the evidence chain of software development and abstract the definition of objective traceability indicators of the evidence chain;

[0032] (2) According to the definition of the index, complete the definition of the standard working environment used in the software development process, and make an agreement on the special attribute marking of the related working products, and standardize the submission path and format requirements of the working products;

[0033] (3) From the submitted standard working products, according to the special attribute marking, complete the statistics of the objective index data required by the evidence chain, and store the data in the database;

[0034] (4) Use FineReport software to read data from the database for classification display, and automatically mark the achievement of each index, and complete the quality color and use boundary identification according to different combinations of index achievement.

[0035] (4.1) Complete the quality color definition based on the evidence chain index under different conditions;

[0036] (4.2) Edit the SQL statement to filter the required data unit from the database;

[0037] (4.3) In the FineReport front-end IDE environment, complete the UI display interface development based on the version quality color definition.

[0038] Embodiment:

[0039] (1) Based on the software engineering research and development evidence chain and traceability index definition.

[0040] Based on the idea of software engineering, software development mainly includes software requirement analysis, software design implementation (including static analysis, unit testing), software integration, and software testing. According to the main output of each process, define a complete software development traceability evidence chain: software development requirements SDTD→software development requirements SRS→code CODE→static analysis scanning→unit testing UT→test requirements STR→test cases STC.

[0041] And abstract the following objective evidence chain traceability index:

[0042] Bidirectional traceability percentage (abbreviation SDTD→SRS): representing the completeness of the traceability coverage from software development requirements SDTD to software development requirements SRS;

[0043] Number of static analysis scanning problems: representing the compliance with coding specification requirements;

[0044] Bidirectional traceability percentage (SRS→Code): representing the completeness of the traceability coverage from source code to software development requirements SRS;

[0045] Bidirectional traceability percentage of STR requirement(abbreviation SDTD→test):characterizes the completeness of test requirement to software development task traceability coverage;

[0046] Test requirement to software development requirement traceability coverage;

[0047] Full regression system test case STC execution number(abbreviation full regression system test):characterizes the completeness of test case execution coverage task book and software requirement;

[0048] Full regression unit test function UT execution number(abbreviation full regression unit test):characterizes that each function unit has been completely unit tested and the traceability relationship has been established.

[0049] (2) Complete the definition of software development process standard working environment.

[0050] According to the definition of software engineering objective traceability index, the organization level completes the definition of standard working directory, and at the project start, through the background script, the creation of standard working environment is automatically completed in the svn. The standard environment directory corresponds to the main process of software development, mainly including software development requirement acquisition(SDTD directory), software requirement analysis(SRS directory), software design(Design directory), software implementation(Code directory), unit test(UT directory), software integration(PI directory), software test(Test directory), project management(PM directory), software change(Changes directory) and the like, as shown in Fig. 1. According to the clear definition, the development personnel will submit the working product of the corresponding process to the specified directory. Figure 2

[0051] (3) From the submitted standard working product, according to the special attribute mark, the statistics of the objective index data required by the development evidence chain are completed, and the data are stored in the database. According to the software development process, the special attribute mark is mainly divided into three categories of software requirement analysis process, design implementation process and test process.

[0052] (3.1) Software requirement analysis process: when carrying out software requirement analysis, the itemized decomposition of software development requirement(SDTD) and software requirement(SRS) is required, a unique ID number is allocated to each requirement(for example, JRJXX.SRS.001), and the attribute is uniformly marked as "Requirment" according to the requirement. And establish the traceability relationship between them. This work is carried out in the organization's specified standard requirement analysis tool DOORS. The established traceability sample is shown in Fig. 2: Figure 3

[0053] (3.2) Design implementation process:

[0054] ​​(3.2.1) In the implementation of software coding, according to the coding specification requirements of the organization, the ID number of the software requirements corresponding to the implementation of the function unit is clearly marked in the annotation content of the function, so as to establish the traceability relationship between each function unit and the software requirements. For example

[0055]

[0056] (3.2.2) For each function unit, complete the static analysis scanning on the server deployed uniformly at the organization level, and analyze each illegal item one by one. The scanning result is shown in Figure 4

[0057] (3.2.3) For each function unit, complete the design of the unit test case script, upload the script to the standard working directory (UT directory) under the svn, and complete the configuration of the automatic timing execution script in the Jekins server. After the batch running is completed, the unit test result file (Excel file) of each function is automatically generated.

[0058] (3.3) Test process:

[0059] (3.3.1) Develop test requirement analysis. The test requirements need to be decomposed and designed in the form of items, and each test requirement is assigned a unique ID number (such as JRJXXv3.05ST90), and the traceability relationship between the test requirements and the software development requirements (SDTD) and the software requirements (SRS) is established. This work is carried out in the standard requirement analysis tool DOORS stipulated by the organization.

[0060] (3.3.2) Develop test case design. According to each test requirement, design the test case in the form of items, and assign a unique ID number (such as JRJXXv3.05ST90.1) to each test case, and mark the test requirement ID number (such as JRJXXv3.05ST90) corresponding to each test case, so as to establish the traceability relationship between the test case and the test requirement. For special cases (according to the user scenario to identify related cases), complete the marking of whether the special attribute is "user scenario". This work can be carried out in the self-developed test tool platform of the organization, or directly in excel.

[0061] (3.3.3) Test case execution. The test case designed in the self-developed test tool platform can be exported as an excel file to complete the execution of each test case. After the execution is completed, the excel file containing the execution record is batched back to the self-developed test tool platform. The execution and result recording of the test case can also be completed directly in the tool platform. The test work product sample is shown in Figure 5

[0062] ​​(3.3.4) Export the test work products in standard format (such as xml format file) from the self-developed tool platform to the test standard svn working directory.

[0063] (3.4) Statistical storage of objective index data required by evidence chain: JAVA is used to develop automatic data statistical scripts based on standard work products, and the data is stored in the background database.

[0064] (4) Use FineReport software to read data from the database for classification and display, and automatically mark the achievement of each index. According to different combinations of index achievement, complete the evaluation of quality color and use boundary.

[0065] (4.1) Complete the definition of quality color and use boundary based on R&D evidence chain traceability index.

[0066] The software delivery quality color is defined as five levels: basic function test, comprehensive bench test, scientific research SF, DXSF, and DX / PC. Different levels require the following definitions of evidence chain traceability indexes:

[0067] Basic function test (orange): the number of static analysis scanning problems is 0;

[0068] Comprehensive bench test (yellow): the number of static analysis scanning problems is 0, The percentage of two-way traceability is 100%, The percentage of two-way traceability is 100% or The percentage of two-way traceability is 100%;

[0069] Scientific research SF (blue): the number of static analysis scanning problems is 0, The percentage of two-way traceability is 100%, The percentage of two-way traceability is 100%, The percentage of two-way traceability is 100%, The percentage of two-way traceability is 100%, and all scenario tests are executed;

[0070] DXSF (light green): the number of static analysis scanning problems is 0, The percentage of two-way traceability is 100%, The percentage of two-way traceability is 100%, The percentage of two-way traceability is 100%, The percentage of two-way traceability is 100%, and all test cases are completed for full regression system test;

[0071] DX / PC (dark green): the number of static analysis scanning problems is 0, The percentage of two-way traceability is 100%, Bidirectional traceability percentage up to 100%, Bidirectional traceability percentage up to 100%, Bidirectional traceability percentage up to 100%, complete all test cases full regression system test, complete all function full regression unit test.

[0072] (4.2) Edit the development of SQL statements, filtering the required data units from the database.

[0073] (4.3) In the FineReport front-end IDE environment, complete the UI display interface development based on version quality color definition. The interface design of UI complies with the operation manual of the tool, and is designed in the EXCEL-like operation mode, as shown in Figure 6 .

Claims

1. A software quality control method based on research and development evidence chain traceability index, characterized by, It comprises the following steps: (1) completing the definition of software development evidence chain based on software engineering requirements, and abstracting the definition of evidence chain objective traceability index; the software development evidence chain is specifically: software development requirement SDTD→software development requirement SRS→code Code→static analysis scanning→unit test UT→test requirement STR→system test case STC; the evidence chain objective traceability index comprises: bidirectional traceability percentage of SDTD and SRS, number of static analysis scanning problems, bidirectional traceability percentage of SRS and Code, bidirectional traceability percentage of SDTD and test requirement STR, bidirectional traceability percentage of SRS and test requirement STR, number of system test case STC execution, number of unit test UT execution; (2) completing the definition of standard working environment used in the software development process according to the index definition, and stipulating the special attribute marking of related working products, and standardizing the submission path and format requirement of working products; (3) from the submitted standard working products, completing the statistics of objective traceability index data required by the evidence chain according to the special attribute marking, and storing the data in a database; (4) using FineReport software to read data from the database for classification display, and automatically marking the achievement of each index, and completing the identification of quality color and use boundary according to different combinations of index achievement; comprising: (4.1) completing the definition of quality color and use boundary based on the development evidence chain traceability index; the software delivery quality color is defined as five levels: basic function test run, comprehensive bench test, scientific research SF, DXSF and DX / PC; different levels meet the following definitions of evidence chain traceability index: basic function test run: the number of static analysis scanning problems is 0; comprehensive bench test: the number of static analysis scanning problems is 0, the bidirectional traceability percentage of SDTD and SRS reaches 100%, the bidirectional traceability percentage of SDTD and test reaches 100% / the bidirectional traceability percentage of SRS and test reaches 100%; scientific research SF: the number of static analysis scanning problems is 0, the bidirectional traceability percentage of SDTD and SRS reaches 100%, the bidirectional traceability percentage of SRS and Code reaches 100%, the bidirectional traceability percentage of SDTD and test reaches 100%, the bidirectional traceability percentage of SRS and test reaches 100%, and all scene tests are executed; DXSF: the number of static analysis scanning problems is 0, the bidirectional traceability percentage of SDTD and SRS reaches 100%, the bidirectional traceability percentage of SRS and Code reaches 100%, the bidirectional traceability percentage of SDTD and test reaches 100%, the bidirectional traceability percentage of SRS and test reaches 100%, and all test cases are completed for full regression system test; DX / PC: static analysis scan problem number is 0, SDTD ↔ SRS bidirectional trace percentage reaches 100%, SRS ↔ Code bidirectional trace percentage reaches 100%, SDTD ↔ test bidirectional trace percentage reaches 100%, SRS ↔ test bidirectional trace percentage reaches 100%, all test case full regression system test is completed, all function full regression unit test is completed; (4.2) editing development SQL statement, screening the required data unit from the database; (4.3) completing the UI display interface development based on version quality color definition in the FineReport front-end IDE environment.

2. The software quality control method based on R&D evidence chain traceability index according to claim 1, characterized in that, The attribute mark in step (3) comprises a mark of a software requirement analysis process, a mark of a design implementation process and a mark of a test process.

3. A computer storage medium having stored thereon a computer program, characterized in that The computer program, when executed by a processor, implements the software quality control method based on the R&D evidence chain traceability index according to any one of claims 1-2.

4. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, The computer program, when executed by a processor, implements the software quality control method based on the R&D evidence chain traceability index according to any one of claims 1-2.

Images