Demand entry automatic generation, matching and detection method based on process run-through

Abstract

The invention belongs to the field of task planning, and particularly relates to a demand entry automatic generation, matching and detection method based on process run-through, which comprises the following steps of: 1, obtaining a demand specification description and a design specification description; step 2, analyzing the demand document, and performing visual display; the database background design is divided into four data tables which are respectively used for storing demand records and accumulating a big data algorithm library; 3, generating a test result comparison table, and displaying the test result comparison table on a software interface; and 4, supplementing the demand according to a comparison result. According to the method, the problems of inconsistent technology and software product cycle and high cost of design, development, development and user requirements in the existing product development process can be solved.

Description

Technical Field

[0001] This invention belongs to the field of task planning, specifically relating to a method for the automatic generation, matching, and detection of requirement items based on process flow. Background Technology

[0002] In recent years, both domestic and international authorities have introduced numerous important measures for each stage of the software development process, reflecting a strong emphasis on efficiency and quality. Internationally, several top-level guidelines for testing and evaluation explicitly require the establishment of efficient and rigorous testing strategies through scientific experimental design to improve testing efficiency. Domestically, China has witnessed rapid development and significant achievements in the field of complex software testing. The nation's vigorous promotion of informatization and the development of high-end product manufacturing has injected strong momentum into the research and application of software testing technology by domestic research institutions and enterprises, resulting in continuous growth in R&D investment. Regarding standards development, my country has formulated a series of national and military standards covering all aspects of software testing, such as GJB 2725A-2001 "General Requirements for Testing and Calibration Laboratories," which standardizes the personnel qualifications, equipment conditions, and testing procedures of software testing organizations, ensuring the scientific and standardized nature of software testing work.

[0003] While product development is progressing rapidly, software testing also faces numerous challenges. First, test case design is difficult, making it hard to guarantee the sufficiency and effectiveness of software testing. Complex software has numerous and complex functions, a large number of interfaces, and constantly changing operating environments, making test case design extremely difficult. Traditional test case design methods, such as equivalence class partitioning and boundary value analysis, often fail to comprehensively cover all possible scenarios and boundary conditions when dealing with such complex software systems, easily overlooking potential software defects. Manually designing test cases is almost impossible to exhaustively cover all subsystem interaction scenarios, resulting in numerous blind spots in software testing and severely impacting the sufficiency and effectiveness of testing. Second, the accuracy and reliability of models are difficult to assess. Existing software reliability assessment methods largely rely on historical data and statistical models. However, the operating environment of complex software is full of uncertainty, and the failure modes of software in actual operation may differ significantly from historical data. Furthermore, the reliability requirements of complex software vary significantly at different task stages. Traditional reliability assessment methods struggle to assess software reliability in real-time and accurately based on dynamic changes at different task stages, failing to provide precise basis for software maintenance and upgrades. Summary of the Invention

[0004] (a) Technical problems to be solved The technical problem to be solved by this invention is: how to provide a method for automatic generation, matching and detection of requirement items based on process integration.

[0005] (II) Technical Solution To address the aforementioned technical problems, this invention provides a method for the automatic generation, matching, and detection of requirement items based on process integration. The inputs of this method include: 1) User requirements: Software requirements documents generated through communication with users; 2) Design understanding: Based on the user requirements document, designers create software functional design documents; The output of the method is: A list of requirements; results of the matching test between requirements and functional design. The method includes the following steps: Step 1: Obtain the requirements specification and design specification; Step 2: Parse the requirements document and visualize it; the database backend design consists of four data tables, which are used to store requirement records and accumulate big data algorithm libraries. Step 3: Generate a test result comparison table and display it on the software interface; Step 4: Based on the comparison results, supplement the requirements.

[0006] Step 1: The user writes the requirement specification and design specification according to the standard specifications.

[0007] In step 1, the requirements specification includes functional requirements, performance requirements, interface requirements, and other requirements.

[0008] In step 1, the design specifications include functional design, performance design, and interface design. Step 2 involves: inputting the requirement documents into the system database using information system software; parsing the documents using algorithms and displaying them visually on the system interface; and designing the database backend with four data tables, which are used to store requirement records and accumulate big data algorithm libraries.

[0009] Step 2 includes: Step 2.1: System Database Design Specification Database table 1: Used to store the requirement document, document name, author, version, and entry time; Database Table 2: Used to record aspects included in different versions of the requirements document; Database Table 3: Records the content of different functional requirements; Database Table 4: Generated requirements itemized document; Step 2.2: Generate a visual interface for the requirement itemization system, such as... Figure 2 As shown.

[0010] In step 3: after the document import is completed, the background algorithm model automatically parses the document, generates a test result comparison table, and displays it at the bottom of the software interface; the functional, performance and other indicator requirements of the requirements document are automatically compared with the relevant design in the software design document or the test cases in the test document. For "compliant items" that can be effectively tracked, "compliant" is displayed in the comparison results and marked in green; for items that cannot be effectively tracked, such as missing items or inconsistencies, "failed" is displayed in the comparison results and marked in red.

[0011] In step 4: Based on the comparison results, supplement the requirements, check the items in the requirements document that have not been effectively tracked, click the "Adopt and Generate Form" button, pop up the form generation dialog box, and based on the form results, the designer revises and updates the requirements document. The requirement compliance testing software's traceability matrix generation function can automatically associate requirement items with the requirement-design-test traceability generation results, and automatically generate a requirement traceability matrix. The requirement traceability matrix mainly includes requirement items, requirement status, software functions, software design status, test case codes, test status, etc. Project developers can manually annotate the requirement status, software design status, and test status, and can export the traceability matrix file.

[0012] (III) Beneficial Effects Compared with existing technologies, this invention addresses the problems of inconsistencies between design, research, development, and user requirements in the existing product development process, as well as the long software product cycle and high cost. It provides a software system that can automatically generate multiple system solutions required by the user by using a method that automatically generates, matches, and detects requirement items based on a process-oriented approach, after the user imports the requirement documents. The generated system is of great significance for improving the quality of software product development and shortening the cycle.

[0013] Key points of the invention This invention is a functional requirements compliance detection technology based on Natural Language Processing (NLP) and knowledge graph technologies. It utilizes NLP to automatically align requirements documents, functional designs, and test cases, and employs knowledge graph technology to construct a relationship graph between requirements, functional modules, and test cases. Coverage is tracked through graph query technology. This invention provides an automated fusion analysis and generation processing system for software testing used in the software requirements, design, and development phases—functional requirements compliance detection software.

[0014] To address the issues of inaccurate requirement modeling and chaotic logical structure, this invention proposes building an algorithm asset management library. It utilizes algorithm management and evaluation technologies to effectively assess algorithm performance. Model management and deployment technologies are employed, with version control software recording different versions of algorithm models. Containerization technology enables automated and rapid algorithm deployment. Algorithm-related knowledge, such as algorithm principles, application scenarios, and performance metrics, is constructed into a knowledge graph. Natural language processing technology is then used to achieve intelligent retrieval of algorithm assets.

[0015] The beneficial effects of this invention are as follows: By using the method of this invention, it is possible to quickly and accurately realize the itemized table of requirements and the matching degree of requirements design functions, and ultimately effectively reduce the requirement iteration in the software design and development process, and avoid the situation of untimely, incomplete and inaccurate requirement tracking caused by frequent requirement iteration.

[0016] The following verification approach was adopted based on the assessment results of the two groups, with Group A serving as the control group and Group B as the experimental group: Group A: The control group project was Project-0, which was similar to Project-2 in the experimental group in terms of system type and software scale. Through surveys and visits to the original project team, and by reviewing coordination minutes, the project team recorded the requirement coordination cycle, the number of requirement coordination rounds, and the number of inconsistencies between software functions and requirements discovered during the process. This information served as a control for the experimental group.

[0017] Group B: Project-2 in the experimental group is a newly developed project. This experiment only assesses the consistency of understanding between the requirements of each professional level and the system designers, the consistency of understanding between the system designers and the software designers, and the consistency of understanding between the system designers and the simulated users.

[0018] During the validation experiment on the consistency of understanding, the quantitative indicators of consistency of understanding between group A (control group) and group B (experimental group) were statistically analyzed. The statistical results are as follows: Figure 5 As shown.

[0019] Analysis shows that for other technical personnel and end users who lack or have not deeply mastered task planning expertise, using the method of this invention for relevant theoretical learning can effectively improve the accuracy of requirements formulation. This not only significantly reduces the requirements coordination cycle but also effectively reduces software design problems caused by inconsistencies in requirements understanding. Specifically, the requirements coordination cycle is reduced by approximately (15-3) / 15 = 80.0%; the number of requirements coordination sessions is reduced by approximately (9-3) / 9 = 66.7%; and the number of problems caused by inconsistencies in requirements understanding is reduced by approximately [(11+17+3)-(2+2+0)] / (11+17+3) = 87.1%.

[0020] Based on the above statistics and analysis, the "Automatic Fusion Analysis and Generation Processing System for Software Testing" can significantly improve the efficiency of requirements matching during the requirements matching process. At the same time, its implicit value is more prominent, which can effectively improve the consistency of requirements understanding and the comprehensive ability of personnel, laying a good professional foundation for subsequent work. Attached Figure Description

[0021] Figure 1 This is a flowchart of the present invention.

[0022] Figures 2-5 This is a schematic diagram illustrating the process and results of the present invention. Detailed Implementation

[0023] To make the objectives, contents, and advantages of the present invention clearer, the specific embodiments of the present invention will be described in further detail below with reference to the accompanying drawings and examples.

[0024] To address the aforementioned technical problems, this invention provides a method for the automatic generation, matching, and detection of requirement items based on process integration. The inputs of this method include: 1) User requirements: Software requirements documents generated through communication with users; 2) Design understanding: Based on the user requirements document, designers create software functional design documents; The output of the method is: A list of requirements; results of the matching test between requirements and functional design. The method includes the following steps: Step 1: Obtain the requirements specification and design specification; Step 2: Parse the requirements document and visualize it; the database backend design consists of four data tables, which are used to store requirement records and accumulate big data algorithm libraries. Step 3: Generate a test result comparison table and display it on the software interface; Step 4: Based on the comparison results, supplement the requirements.

[0025] Step 1: The user writes the requirement specification and design specification according to the standard specifications.

[0026] In step 1, the requirements specification includes functional requirements, performance requirements, interface requirements, and other requirements.

[0027] In step 1, the design specifications include functional design, performance design, and interface design. Step 2 involves: inputting the requirement documents into the system database using information system software; parsing the documents using algorithms and displaying them visually on the system interface; and designing the database backend with four data tables, which are used to store requirement records and accumulate big data algorithm libraries.

[0028] Step 2 includes: Step 2.1: System Database Design Specification Database table 1: Used to store the requirement document, document name, author, version, and entry time; Database Table 2: Used to record aspects included in different versions of the requirements document; Database Table 3: Records the content of different functional requirements; Database Table 4: Generated requirements itemized document; Step 2.2: Generate a visual interface for the requirement itemization system, such as... Figure 2 As shown.

[0029] In step 3: after the document import is completed, the background algorithm model automatically parses the document, generates a test result comparison table, and displays it at the bottom of the software interface; the functional, performance and other indicator requirements of the requirements document are automatically compared with the relevant design in the software design document or the test cases in the test document. For "compliant items" that can be effectively tracked, "compliant" is displayed in the comparison results and marked in green; for items that cannot be effectively tracked, such as missing items or inconsistencies, "failed" is displayed in the comparison results and marked in red.

[0030] In step 4: Based on the comparison results, supplement the requirements, check the items in the requirements document that have not been effectively tracked, click the "Adopt and Generate Form" button, pop up the form generation dialog box, and based on the form results, the designer revises and updates the requirements document. The requirement compliance testing software's traceability matrix generation function can automatically associate requirement items with the requirement-design-test traceability generation results, and automatically generate a requirement traceability matrix. The requirement traceability matrix mainly includes requirement items, requirement status, software functions, software design status, test case codes, test status, etc. Project developers can manually annotate the requirement status, software design status, and test status, and can export the traceability matrix file.

[0031] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the technical principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for automatic generation, matching, and detection of requirement items based on process integration, characterized in that, The inputs to the method include: 1) User requirements: Software requirements documents generated through communication with users; 2) Design understanding: Based on the user requirements document, designers create software functional design documents; The output of the method is: A list of requirements; results of the matching test between requirements and functional design. The method includes the following steps: Step 1: Obtain the requirements specification and design specification; Step 2: Parse the requirements document and visualize it; the database backend design consists of four data tables, which are used to store requirement records and accumulate big data algorithm libraries. Step 3: Generate a test result comparison table and display it on the software interface; Step 4: Based on the comparison results, supplement the requirements.

2. The method for automatic generation, matching, and detection of requirement items based on process integration as described in claim 1, characterized in that, Step 1: The user writes the requirement specification and design specification according to the standard specifications.

3. The method for automatic generation, matching, and detection of requirement items based on process integration as described in claim 2, characterized in that, In step 1, the requirements specification includes functional requirements, performance requirements, interface requirements, and other requirements.

4. The method for automatic generation, matching, and detection of requirement items based on process integration as described in claim 3, characterized in that, In step 1, the design specifications include functional design, performance design, and interface design.

5. The method for automatic generation, matching, and detection of requirement items based on process integration as described in claim 1, characterized in that, Step 2: Input the requirement documents into the system database through the information system software; the system software parses the documents through algorithms and displays them visually on the system interface; the database backend design is divided into four data tables, which are used to store requirement records and accumulate big data algorithm library.

6. The method for automatic generation, matching, and detection of requirement items based on process integration as described in claim 5, characterized in that, Step 2 includes: Step 2.1: System Database Design Specification Database table 1: Used to store the requirement document, document name, author, version, and entry time; Database Table 2: Used to record aspects included in different versions of the requirements document; Database Table 3: Records the content of different functional requirements; Database Table 4: Generated requirements itemized document; Step 2.2: Generate a visual interface for the requirements itemization system.

7. The method for automatic generation, matching, and detection of requirement items based on process integration as described in claim 6, characterized in that, Step 3: After the document import is completed, the background algorithm model automatically parses the document, generates a test result comparison table, and displays it at the bottom of the software interface. The functional, performance, and other indicator requirements of the requirements document are automatically compared with the relevant designs in the software design document or the test cases in the test document. For "compliant items" that can be effectively tracked, "compliant" is displayed in the comparison results and marked in green. For items that cannot be effectively tracked, such as missing items or inconsistencies, "failed" is displayed in the comparison results and marked in red.

8. The method for automatic generation, matching, and detection of requirement items based on process integration as described in claim 7, characterized in that, Step 4: Based on the comparison results, supplement the requirements, check the items in the requirements document that have not been effectively tracked, click the "Adopt and Generate Form" button, a pop-up form generation dialog box will appear, and the designer will revise and update the requirements document based on the form results; The requirement compliance testing software's traceability matrix generation function can automatically associate requirement items with the requirements-design-test traceability generation results, and automatically generate a requirement traceability matrix. The requirement traceability matrix mainly includes requirement items, requirement status, software functions, software design status, test case codes, test status, etc. Project developers can manually annotate the status of requirements, software design, and testing, and export the traceability matrix file.

9. The method for automatic generation, matching, and detection of requirement items based on process integration as described in claim 8, characterized in that, The method described belongs to the field of task planning.

10. The method for automatic generation, matching, and detection of requirement items based on process integration as described in claim 8, characterized in that, The method described above can solve the problems of inconsistency between design, research and development and user needs in the existing product development process, as well as the problems of long software product cycles and high costs.

Images