CN114327377A

CN114327377A - Method and device for generating demand tracking matrix, computer equipment and storage medium

Info

Publication number: CN114327377A
Application number: CN202210245843.2A
Authority: CN
Inventors: 赵璐; 黄玉飞
Original assignee: Zhejiang Taimei Medical Technology Co Ltd
Current assignee: Zhejiang Taimei Medical Technology Co Ltd
Priority date: 2022-03-14
Filing date: 2022-03-14
Publication date: 2022-04-12
Anticipated expiration: 2042-03-14
Also published as: CN114327377B

Abstract

The embodiment of the specification provides a method and a device for generating a requirement tracking matrix of software, computer equipment and a storage medium. The method comprises the steps of acquiring a product name and a version number, inquiring a demand entry identifier according to the product name and the version number, inquiring a function entry identifier associated with the demand entry identifier according to the demand entry identifier, thereby acquiring a target operation confirmation identifier and a target performance confirmation identifier associated with the function entry identifier, completing the acquisition of identification data required by a demand tracking matrix template, further performing structure adjustment on the identification data required by the demand tracking matrix template according to a data structure of the demand tracking matrix template to obtain target identification data adapted to the data structure of the demand tracking matrix template, finally filling the target identification data into cells of the demand tracking matrix template to generate a demand tracking matrix, generating the demand tracking matrix in an automatic mode, and improving the efficiency of generating verification files.

Description

Method and device for generating demand tracking matrix, computer equipment and storage medium

Technical Field

The embodiment of the specification relates to the technical field of computers, in particular to a method and a device for generating a requirement tracking matrix of software, computer equipment and a storage medium.

Background

According to the GxP quality control System requirement, the computer System must be verified by a CSV (computer System validation) to verify that the product meets the intended use, thereby ensuring public safety, data integrity and product quality. The CSV verification activity runs through the whole process of software product development, and file records in the software product development process form important components of verification files.

In the conventional technology, after the verification work is started, a specially-assigned person is required to perform manual association and manual integration on the data generated in the software development process so as to generate all parts in the verification file, such as a requirement tracking matrix and a software test document. The generation process of the verification document usually takes a month or more. Therefore, the generation efficiency of the verification file in the conventional technology needs to be improved.

Disclosure of Invention

In view of this, embodiments of the present disclosure are directed to providing a method and an apparatus for generating a requirement tracking matrix of software, a computer device, a storage medium, and a computer program product, so as to solve the technical problem in the conventional art that the generation efficiency of a verification file needs to be improved.

The implementation mode of the specification provides a method for generating a requirement tracking matrix of software, wherein a data structure of a requirement tracking matrix template comprises a requirement item identification data column, a requirement description data column, a function item identification data column, an operation confirmation identification data column and a performance confirmation identification data column; the method comprises the following steps: acquiring a product name and a version number; inquiring requirement items in a verification file data source according to the product name and the version number to obtain a corresponding requirement item data set; the requirement item data set comprises a requirement item identifier and requirement description data corresponding to the requirement item identifier; the verification file data source is obtained by collecting data generated by design operation, development operation and test operation through a development management system in the development process of the software and is used for generating a verification file; the development management system is a platform system used for following the design operation, the development operation and the test operation of the software; inquiring function items in the verification file data source according to the requirement item identification to obtain a corresponding function item data set; wherein the function item dataset comprises a function item identification associated with the requirement item identification; acquiring a target operation confirmation identifier and a target performance confirmation identifier which are associated with the function item identifier; according to a data structure of a demand tracking matrix template, performing data splicing on the demand entry identification, demand description data corresponding to the demand entry identification, a function entry identification associated with the demand entry identification, the target operation confirmation identification and the target performance confirmation identification to obtain target identification data adaptive to the data structure; correspondingly filling the target identification data into cells of the demand tracking matrix template to generate a demand tracking matrix; wherein the requirement tracking matrix is used as a part of the verification file; the identification data filled into each cell in the demand tracking matrix is provided with a corresponding document hyperlink; the identification data in the cells is identification information of a document associated with the document hyperlink, and the document hyperlink is used for accessing the associated document.

The implementation mode of the specification provides a device for generating a requirement tracking matrix of software, wherein a data structure of a requirement tracking matrix template comprises a requirement item identification data column, a requirement description data column, a function item identification data column, an operation confirmation identification data column and a performance confirmation identification data column; the device comprises: the name version number acquisition module is used for acquiring the name and the version number of the product; the requirement item query module is used for querying requirement items in a verification file data source according to the product name and the version number to obtain a corresponding requirement item data set; the requirement item data set comprises a requirement item identifier and requirement description data corresponding to the requirement item identifier; the verification file data source is obtained by collecting data generated by design operation, development operation and test operation through a development management system in the development process of the software and is used for generating a verification file; the development management system is a platform system used for following the design operation, the development operation and the test operation of the software; the function item query module is used for querying function items in the verification file data source according to the requirement item identification to obtain a corresponding function item data set; wherein the function item dataset comprises a function item identification associated with the requirement item identification; the confirmation identifier acquisition module is used for acquiring a target operation confirmation identifier and a target performance confirmation identifier which are associated with the function item identifier; the identification data splicing module is used for performing data splicing on the requirement item identification, the requirement description data corresponding to the requirement item identification, the function item identification associated with the requirement item identification, the target operation confirmation identification and the target performance confirmation identification according to the data structure of the requirement tracking matrix template to obtain target identification data adaptive to the data structure; the identification data filling module is used for correspondingly filling the target identification data into the cells of the demand tracking matrix template so as to generate a demand tracking matrix; wherein the requirement tracking matrix is used as a part of the verification file; the identification data filled into each cell in the demand tracking matrix is provided with a corresponding document hyperlink; the identification data in the cells is identification information of a document associated with the document hyperlink, and the document hyperlink is used for accessing the associated document.

The present specification provides a computing device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the method steps of the above embodiments when executing the computer program.

The present specification provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor implements the method steps in the above embodiments.

The present specification embodiments provide a computer program product, which includes instructions that, when executed by a processor of a computer device, enable the computer device to perform the method steps in the above embodiments.

In the embodiment of the specification, by acquiring the product name and the version number, inquiring the requirement item identifier according to the product name and the version number, inquiring the function item identification associated with the requirement item identification according to the requirement item identification so as to obtain a target operation confirmation identification and a target performance confirmation identification associated with the function item identification, complete the acquisition of identification data required by the requirement tracking matrix template, further, according to the data structure of the demand tracking matrix template, the identification data required by the demand tracking matrix template is subjected to structure adjustment to obtain target identification data adapted to the data structure of the demand tracking matrix template, and finally, the target identification data is filled into the cells of the demand tracking matrix template, the method and the device have the advantages that the requirement tracking matrix is generated, the requirement tracking matrix is generated in an automatic mode, the probability of missing or error of the document is reduced, and the accuracy of the verification file is improved. Furthermore, the document content related to the verification file is clearly presented to the user through the requirement tracking matrix, the readability and the readability of the verification file are improved, and the operation cost of the user for looking up the verification file is reduced.

Drawings

FIG. 1a is a diagram illustrating an application environment of a method for generating a demand tracking matrix in an example scenario provided by an embodiment.

FIG. 1b is a diagram illustrating a verification document creation interface in an example scenario provided by an embodiment.

FIG. 1c is a diagram illustrating a document adding interface in an exemplary scenario according to an embodiment.

FIG. 1d is a diagram illustrating an application environment of the method for generating a demand tracking matrix according to an embodiment.

Fig. 2a is a schematic flow chart illustrating a method for generating a demand tracking matrix according to an embodiment.

FIG. 2b is a diagram illustrating a demand tracking matrix according to an embodiment.

FIG. 2c is a schematic diagram of a demand tracking matrix according to an embodiment.

Fig. 3 is a flowchart illustrating a method for generating a demand tracking matrix according to an embodiment.

Fig. 4a is a flowchart illustrating a method for generating a demand tracking matrix according to an embodiment.

FIG. 4b is a diagram illustrating a statistical result for the demand module according to an embodiment.

Fig. 5 is a flowchart illustrating a method for generating a demand tracking matrix according to an embodiment.

Fig. 6a is a flowchart illustrating a method for generating a demand tracking matrix according to an embodiment.

FIG. 6b is a diagram illustrating a demand tracking matrix according to an embodiment.

Fig. 7 is a flowchart illustrating a method for generating a demand tracking matrix according to an embodiment.

Fig. 8 is a flowchart illustrating a method for generating a demand tracking matrix according to an embodiment.

Fig. 9 is a block diagram of a structure of a demand trace matrix generation apparatus according to an embodiment.

Fig. 10 is an internal structural diagram of a computer device according to an embodiment.

Detailed Description

The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art without any inventive work based on the embodiments in the present specification belong to the protection scope of the present specification.

Please refer to fig. 1 a. In a specific scenario example, a business expert, a product manager, a technician, a tester, and a verifier may all access the software development work management platform. When a new piece of software needs to be developed or the software needs to be updated, the service expert can access the software development work management platform. And receiving requirement data input by a business expert, such as software product names, modules needing to be developed and the like, through the software development work management platform. Wherein each module includes a number of requirement entries. The software development work management platform can store requirement item identification, requirement description data corresponding to the requirement item identification, requirement item creating time and other requirement data.

Illustratively, the software product name is EDC software (Electronic Data Capture System, clinical trial Electronic Data acquisition System). The EDC software comprises modules including a login module, a compliance module, a signature service module and a configuration management module. The configuration management module is taken as an example to explain the requirement data, and the configuration management module is correspondingly provided with a plurality of requirement items. Such as the execution environment configuration of the clinical trial project, the trial type configuration of the clinical trial project, the custom configuration of the subject information, the configuration of the approval node, etc. Each requirement item has requirement item identification and requirement description data. For example, the requirement item identifier of "execution environment configuration of clinical trial project" may be denoted as "UR-Gamp 5-64". The requirement description data of "the execution environment configuration of the clinical trial project" may be written as "the project and the execution environment that the user can select to execute". As another example, the requirement item identifier for "trial type configuration for clinical trial items" may be denoted as "UR-Gamp 5-65". The requirement description data of "test type configuration of clinical test item" may be recorded as "initial entry item may select test type: simple, multiple queues, complex.

When the software development work management platform receives the functional design data input by the product manager, the product manager is required to pre-specify the requirement items which need to be associated with the functional design data, namely, the requirement items and the functional items have corresponding relations. The functional design of the software is described by taking a compliance module as an example. And the product manager performs function design on the demand data of the compliance module and divides the compliance module into a plurality of corresponding function items. Wherein each function item has a function item identifier and corresponding function description data. It should be noted that the co-scale block may have at least one requirement entry corresponding thereto, and the requirement entry corresponding to the co-scale block and the function entry corresponding to the co-scale block have a corresponding relationship therebetween. One requirement entry corresponding to the co-scale block may correspond to one function entry, and one requirement entry corresponding to the co-scale block may correspond to a plurality of function entries. The software development work management platform may store function item identifiers and function description data corresponding to the function item identifiers, and function design data such as time for creating the function items.

After the product manager completes the function design aiming at the required data, the technical personnel writes the codes to realize the function required by the user, and the codes written by the technical personnel can be reviewed in the process of writing the codes by the technical personnel. During evaluation, the code evaluation data can be recorded into the code evaluation template, and a code evaluation report is generated. Or a code review report template can be preset, when the codes are reviewed, code review data aiming at the codes are collected, the code review data are adjusted according to the data structure of the code review report template, and the adjusted code review data are written into the code review report template to obtain a code review report.

After the technician completes the code writing work, the tester is required to run the relevant test cases on the software development work management platform. Specifically, a tester may pre-formulate a test plan, where the test plan includes a plurality of test cases. Each test case corresponds to a test name. And in the running process of each test case, in order to record the test result, screenshot is carried out on the test interface to obtain the screenshot of the test interface. And counting and recording the results of the test cases to obtain the test results and the statistical results. When writing a test case, a function entry may be designated, and the test case is associated with the function entry, so that the function entry identifier and the test case identifier may have a correspondence relationship. Further, each test case has its own test name and test procedure. The test name of the test case can be recorded as name data of the test case, and the test step of the test case can be recorded as test step data of the test case. The test result may be a pass or a fail, a "pass" indicating that the function or performance of the test passed the test. "fail" means that the function or performance of the test failed. The software development work management platform can store test data such as a test plan, identification information of the test plan, test cases included by the test plan, identification information of the test cases, test step data of the test cases, test results, test interface screenshots, name data and statistical results.

When the software is verified by the verifier, the verifier can access the software development work management platform, and the software development work management platform can be provided with a verification file creation interface. Please refer to fig. 1 b. The verification file creation interface is provided with a product name input box and a version number input box, the input product name is received through the product name input box, and the input version number is received through the version number input box. The software development work management platform can also be provided with a document adding interface. The document adding interface is also provided with a document type drop-down column box. Referring to fig. 1c, in response to a trigger operation on the document type drop-down box, a document type list is displayed, and a user requirement specification, a functional design specification, a performance confirmation report, a functional confirmation report, and a verification file are displayed in the document type list.

Illustratively, in the case that the user selects the user requirement specification, the requirement data for generating the user requirement specification is acquired according to the input product name and version number, the requirement specification document template is acquired, and the acquired requirement data is written into the requirement specification document template to obtain the user requirement specification (which may also be called as a requirement specification document).

Illustratively, in the case where the user selects a functional design specification, the functional design data for generating the functional design specification is acquired from the input product name and version number, and a functional design document template is acquired, and the acquired functional design data is written in the functional design document template to obtain the functional design specification (which may also be referred to as a functional design document).

Illustratively, under the condition that a user selects a performance confirmation report, the identification information, the test step data, the test result and the test interface screenshot of a test case for generating the performance confirmation report are obtained according to the input product name and the version number, a performance confirmation document template is obtained, and the identification information, the test step data, the test result and the test interface screenshot of the test case are filled into the performance confirmation document template according to the data structure of the performance confirmation document template to obtain a performance confirmation document.

Illustratively, under the condition that the user selects the function confirmation report, according to the input product name and version number, the identification information, the statistical result and the name data of the test case for generating the function confirmation report are obtained, the operation confirmation document template is obtained, and according to the data structure of the operation confirmation document template, the identification information, the statistical result and the name data of the test case are filled into the operation confirmation document template to obtain the operation confirmation document.

Illustratively, the validation file includes a user requirement specification, a functional design specification, a code review report, an installation confirmation report, a performance confirmation report, a functional confirmation report, a tracking matrix due to the collection of a series of documents when validating the file. The generation of the verification file depends on a verification file data source, and the verification file data source is obtained by recording data generated by design operation, development operation and test operation in the development process of software. The generation process of the verification file is exemplarily described below, and in the present exemplary scenario example, in the case where the user only needs to input the product name and version number and select the verification file, the verification file including the user requirement specification, the functional design specification, the performance confirmation report, the functional confirmation report, and the requirement tracking matrix may be automatically generated. The data structure of the demand tracking matrix template comprises a demand item identification data column, a demand description data column, a function item identification data column, an operation confirmation identification data column and a performance confirmation identification data column;

specifically, under the condition that the user selects the verification file, the query of the requirement item is carried out in the verification file data source according to the input product name and version number, and a corresponding requirement item data set is obtained. The requirement item data set comprises a requirement item identifier and requirement description data corresponding to the requirement item identifier. Further, extracting requirement data corresponding to a data column included in the requirement description document template from the requirement item data set; performing structure adjustment on the extracted demand data according to the data structure of the demand specification document template to obtain target demand data; and filling the target requirement data into a requirement description document template to generate a requirement description document. Wherein the requirements specification document is part of the verification file.

And inquiring the function items in the verification file data source according to the requirement item identification to obtain a corresponding function item data set. Wherein the function item dataset comprises a function item identification associated with the requirement item identification. Further, extracting functional design data corresponding to a data column included in the functional design document template from the functional item data set; performing structural adjustment on the extracted functional design data according to the data structure of the functional design document template to obtain target functional design data; and filling the target functional design data into a functional design document template to generate a functional design document. Wherein the functional design document is part of the verification file.

And acquiring a target operation confirmation identification and a target performance confirmation identification which are associated with the function item identification. Further, inquiring the test plan in the verification file data source according to the product name and the version number to obtain the identification information of the corresponding test plan; inquiring the identification information of the test case, the test step data, the test result and the test interface screenshot which are included in the test plan according to the identification information of the test plan; filling the identification information of the test case, the test step data, the test result and the test interface screenshot into the performance confirmation document template according to the data structure of the performance confirmation document template to obtain a performance confirmation document; filling the identification information, the statistical result and the name data of the test case into the operation confirmation document template according to the data structure of the operation confirmation document template to obtain an operation confirmation document; wherein the performance validation document, the run validation document are part of the verification file.

And according to the data structure of the requirement tracking matrix template, performing data splicing on a requirement item identifier, requirement description data corresponding to the requirement item identifier, a function item identifier associated with the requirement item identifier, a target operation confirmation identifier and a target performance confirmation identifier to obtain target identification data adaptive to the data structure.

Correspondingly filling the target identification data into cells of a demand tracking matrix template to generate a demand tracking matrix; wherein, the demand tracking matrix is used as a part of the verification file; the identification data filled into each cell in the demand tracking matrix is provided with a corresponding document hyperlink; the identification data in the cells is identification information of a document associated with the document hyperlink, and the document hyperlink is used for accessing the associated document.

So far, a user requirement specification, a function design specification, a performance confirmation report, a function confirmation report, and a requirement tracking matrix are automatically generated according to the input product name and version number, and these documents can be used to constitute a verification file as a part of the verification file. In the scene example, the verification file can be automatically generated only by inputting the product name and the version number and selecting the verification file by a user, so that the workload of verification personnel is reduced, the generation efficiency of the verification file is improved, the probability of omission or errors in the manual association and manual arrangement process is reduced, and the accuracy of the verification file is ensured.

Referring to fig. 1d, an embodiment of the present disclosure provides a verification file generation system for software, and the method for generating a requirement tracking matrix for software provided by the present disclosure is applied to the verification file system. By the method for generating the requirement tracking matrix of the software, the automatically generated requirement tracking matrix is used as a part of the verification file. The verification file system may include a hardware environment formed by the terminal 110 and the server 120. The terminal 110 communicates with the server 120 through a network. The terminal 110 may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices. The server 120 may be implemented as a stand-alone server or a server cluster composed of a plurality of servers. With the development of scientific technology, new computing devices, such as quantum computing servers, may be developed, and may also be applied to the embodiments of the present specification.

Referring to fig. 2a, an embodiment of the present disclosure provides a method for generating a requirement tracking matrix of software. The method for generating the requirement tracking matrix of the software can comprise the following steps.

Step S210: and acquiring the product name and the version number.

The product name may be a name of the software, and the product name may also correspond to a project name of a project to which the software belongs. The version number may be a version identification number of software adapted to different operating environments, or may be a version identification number of new software obtained by correcting or correcting a change requirement after a software product is put into use. Specifically, the terminal is provided with a verification file newly added page, receives a product name and a version number input by a user through the verification file newly added page, sends the product name and the version number to the server, and receives the product name and the version number. Illustratively, the product name may be an EDC system and the version number may be 5.3.1.

Step S220: and inquiring the requirement items in the verification file data source according to the product names and the version numbers to obtain a corresponding requirement item data set.

The requirement item data set comprises a requirement item identifier and requirement description data corresponding to the requirement item identifier. The software can be divided into a plurality of demand modules, and different demand modules can be split into a plurality of demand items. Each requirement item has a requirement item identifier, and the requirement item identifier is used for uniquely representing the requirement item. The requirement entry identification may be a requirement number. Because the requirement item identification cannot directly express the requirement of the user, each requirement item has corresponding requirement description data. The requirement description data may be represented in the form of text data.

The verification file data source is obtained by collecting data generated by design operation, development operation and test operation through a development management system in the development process of the software and is used for generating a verification file. Wherein the development management system is a platform system for following the design operation, development operation and test operation of the software, such as the aforementioned software development work management platform. The software development work management platform can be provided with a design operation interface, a development operation interface and a test operation interface. The development work management platform can collect and store data generated by design operation, development operation and test operation to form a verification file data source. When the verification work needs to be executed, the data needing to be written in the template is obtained from the verification file data source so as to obtain the document or the report in the verification file. Illustratively, the design operation may be understood as analysis of user requirements by a business expert, and sending data related to the user requirements to a software development work management platform, which may collect and store data generated by the design operation. The software development work management platform can adopt a JIRA tool which is used in the work fields of defect tracking, customer service, demand collection, process approval, task tracking, project tracking, agility management and the like.

Specifically, in some embodiments, the terminal may generate a data query statement according to the product name and the version number, the terminal sends the data query statement to the server, the server executes the data query statement, and executes query of the requirement entry in the verification file data source to obtain a requirement entry data set corresponding to the product name and the version number, where the requirement entry data set includes a requirement entry identifier and requirement description data corresponding to the requirement entry identifier. Illustratively, the terminal generates JQL query statements based on the product name and version number, the terminal sends JQL statements to the server, and the server executes JQL query statements in the JIRA data source to obtain the requirement entry dataset.

In some embodiments, the requirement module entry of each requirement module is queried in the verification file data source according to the product name and the version number, and the original requirement entry of the sub-module of the requirement module entry with the type of the original requirement is recursively queried according to the requirement module entry to obtain a corresponding requirement entry data set.

Step S230: and inquiring the function items in the verification file data source according to the requirement item identification to obtain a corresponding function item data set.

Wherein the function item dataset comprises a function item identification associated with the requirement item identification. The function item can be obtained by the product manager through designing the function aiming at the requirement module. The function item identification is used to uniquely identify the function item. The function entry identification may be a function number. Specifically, a requirement item needs to be specified before a product manager performs function design, the function item to be subjected to function design is associated with the requirement item, and in response to an association operation between the function item and the requirement item, the terminal sends a corresponding relationship between the function item and the requirement item to the server. And the server receives and stores the corresponding relation between the function item and the requirement item. It is understood that the corresponding relationship between the function entry and the requirement entry is data generated by a design operation in a software development process, and can be used as a part of a verification file data source. Therefore, the functional items are inquired in the verification file data source according to the requirement item identification to obtain a plurality of functional item identifications corresponding to the requirement item identification, and the plurality of functional item identifications form a functional item identification data set.

Step S240: and acquiring a target operation confirmation identification and a target performance confirmation identification which are associated with the function item identification.

The operation confirmation identifier may be identification information of an operation confirmation (OQ) test case. For example, the running confirmation identifier may be the number of the OQ test case. The performance validation flag may be flag information of a performance validation (PQ) test case. For example, the performance validation identifier may be the number of the PQ test case. Specifically, when a tester writes an OQ test case, the OQ test case needs to be associated with a function entry, that is, a correspondence relationship is established between a function entry identifier and an operation confirmation identifier. Similarly, when writing a PQ test case, a tester needs to associate the PQ test case with a function entry, that is, a correspondence relationship is established between a function entry identifier and a performance verification identifier. The server stores the corresponding relationship between the function item identification and the operation confirmation identification, and the corresponding relationship between the function item identification and the performance confirmation identification. Therefore, the function item identifier is used for matching in the corresponding relation between the function item identifier and the operation confirmation identifier, and the target operation confirmation identifier associated with the function item identifier is obtained. And matching the corresponding relation between the function item identification and the performance confirmation identification by using the function item identification to obtain a target performance confirmation identification associated with the function item identification.

Step S250: and according to the data structure of the requirement tracking matrix template, performing data splicing on a requirement item identifier, requirement description data corresponding to the requirement item identifier, a function item identifier associated with the requirement item identifier, a target operation confirmation identifier and a target performance confirmation identifier to obtain target identification data adaptive to the data structure.

The requirement tracking matrix template is a template file used for generating a requirement tracking matrix. The requirement tracking matrix template comprises a plurality of data columns, such as a requirement item identification data column, a requirement description data column, a function item identification data column, a target operation confirmation identification data column and a target performance confirmation identification data column. Illustratively, the demand tracking matrix may take the form of a table as shown in FIG. 2 b. The data columns included in the requirement tracking matrix template can be URS number, URS description, FDS number, OQ case number and PQ case number. It is understood that the URS may be understood as the english acronym for the user requirements specification. FDS may be understood as the english acronym for user demand specification.

The terminal sends a verification file generation request to the server, and the server receives the verification file generation request. Since which documents or reports the verification file includes has been set in advance, the corresponding document template or report template can be acquired according to the verification file generation request. For example, if the preset verification file includes the requirement tracking matrix, the requirement tracking matrix template is acquired according to the verification file generation request. If the preset verification file comprises a requirement specification document, a function design document and a requirement tracking matrix, a requirement specification document template, a function design document template and a requirement tracking matrix template are obtained according to a verification file generation request.

Specifically, the demand tracing matrix template has a data structure, and the data structure of the demand tracing matrix template depends on the actual situation of the demand tracing matrix template. The data structure of the demand tracking matrix template may include columns of data included in the demand tracking matrix template. The requirement tracking matrix template is provided with a plurality of placeholders, and the data structure of the requirement tracking matrix template can also comprise the sequencing mode of each placeholder in the requirement tracking matrix template. The data structure of the requirement tracking matrix template can comprise a requirement item identification data column, a requirement description data column, a function item identification data column, an operation confirmation identification data column, a performance confirmation identification data column and an ordering mode of placeholders of the data columns. The method comprises the steps that a requirement item identification, requirement description data corresponding to the requirement item identification, a function item identification associated with the requirement item identification, a target operation confirmation identification and a target performance confirmation identification are obtained according to a product name and a version number sent by a terminal, therefore, according to a data column included in a requirement tracking matrix template and the position in each data column, structural adjustment is carried out on data required by the requirement tracking matrix template, and the obtained data which are associated with each other are subjected to data splicing to obtain target identification data which are adaptive to a data structure. Illustratively, referring to FIG. 2c, the data columns and placeholders in the requirement tracking matrix template correspond.

Step S260: and correspondingly filling the target identification data into the cells of the requirement tracking matrix template to generate the requirement tracking matrix.

Wherein, the demand tracking matrix is used as a part of the verification file; the identification data filled into each cell in the demand tracking matrix is provided with a corresponding document hyperlink; the identification data in the cells is identification information of a document associated with the document hyperlink, and the document hyperlink is used for accessing the associated document. The identification data in each cell in the demand tracking matrix may be any one of a demand entry identification, demand description data, a function entry identification, a target operation confirmation identification, and a target performance confirmation identification.

Specifically, the cells in the requirement tracking matrix template have corresponding placeholders, and each identification data (such as a requirement entry identifier, requirement description data, a function entry identifier, a target operation confirmation identifier, and a target performance confirmation identifier) includes a field and a field value. And matching the field of the requirement item identifier with the placeholder of the cell, and replacing the placeholder of the cell by using the field value if the field of the requirement item identifier is matched with the placeholder of the cell, namely filling the corresponding target identifier into a requirement tracking matrix template to generate a requirement tracking matrix. It should be noted that, if the demand trace matrix includes only the data columns, the demand trace matrix can be obtained. If the demand tracing matrix further includes other data columns besides the data columns, the identification data of the other data columns may be filled in the demand tracing matrix by a manual adjustment. For example, the other data columns may be TDS numbered data columns. TDS is an english acronym for technical design specifications. The TDS number and the URS number can be associated in advance, the TDS number can be obtained by inquiring the URS number, and the TDS number obtained by inquiring is filled into the demand tracking matrix template according to the position of the TDS number data column in the demand tracking matrix template to generate the demand tracking matrix.

With continued reference to FIG. 2b, the table structure shown in FIG. 2b may be mapped to the data structure of the requirement tracking matrix template. Illustratively, the placeholder for a cell in the demand tracking matrix template may be { { tableUR } } [ model ]; the field identified by the requirement entry may be a model, and the field value may be XX-UR-536. And matching the field model identified by the requirement entry with the placeholder { { tableUR } } [ model ], and if the field model is matched with the placeholder { { tableUR } } [ model ], replacing { { tableUR } } [ model ] by using a field value XX-UR-536 to fill XX-UR-536 in the requirement tracking matrix template.

Illustratively, the header in fig. 2b includes the data column URS number, description (i.e., the requirement description data), FDS number, OQ use case number, and PQ use case number. And acquiring the URS number URS-0001 with respect to the data in the first row in the figure 2b, and acquiring corresponding requirement description data 'system support user and authority management' according to the URS-0001. The data of the other data columns is empty. Then "URS-0001" and "system support user and rights management" correspond to the URS numbered data column and the description data column populated to the first row of the requirements tracking matrix template.

Illustratively, with respect to the data of the second row in FIG. 2b, URS number URS-0001.01 is obtained, and corresponding requirement description data "user can set roles of original materials registrant, medical reviewer, etc. is obtained according to URS-0001.01". Obtaining corresponding FDS numbers FD-SM-0001, FD-SM-0002 and FD-SM-0003 according to URS-0001.01; and obtaining the numbers TC-OQ-SM-0007, TC-OQ-SM-0008, TC-OQ-SM-0009, TC-OQ-SM-0010 and TC-OQ-SM-0011 of OQ use cases according to the FDS numbers FD-SM-0001, FD-SM-0002 and FD-SM-0003. PQ case Nos. TC-PQ-SM-0003 and TC-PQ-SM-0004 were obtained from FDS Nos. FD-SM-0001, FD-SM-0002 and FD-SM-0003. The data is correspondingly filled into each data column of the second row of the demand tracking matrix template.

The method for generating the demand tracking matrix of the software comprises the steps of acquiring a product name and a version number, inquiring a demand entry identifier according to the product name and the version number, inquiring a function entry identifier associated with the demand entry identifier according to the demand entry identifier, thereby acquiring a target operation confirmation identifier and a target performance confirmation identifier associated with the function entry identifier, completing the acquisition of identification data required by a demand tracking matrix template, further performing structure adjustment on the identification data required by the demand tracking matrix template according to the data structure of the demand tracking matrix template to obtain target identification data adapted to the data structure of the demand tracking matrix template, finally filling the target identification data into cells of the demand tracking matrix template to generate the demand tracking matrix, and inquiring by utilizing the product name and the version number to generate the demand tracking matrix in an automatic mode, the probability of missing or error of the document is reduced, and the generation efficiency and accuracy of the verification file are improved. Furthermore, the document content related to the verification document is clearly presented to the user through the requirement tracking matrix, the readability and the readability of the verification document are improved, and the operation cost of the user for looking up each document in the verification document is reduced.

In some embodiments, referring to fig. 3, obtaining the target operation confirmation identifier and the target performance confirmation identifier associated with the function entry identifier may include the following steps.

Step S310: and inquiring the test data in the verification file data source according to the product name and the version number to obtain a corresponding test case data set.

The test case data set comprises an operation confirmation identification and a performance confirmation identification. Specifically, before a tester tests software, a test plan interface provided by the software development work management platform can be accessed, a test case and a test control of the test case are displayed in the test plan interface, and the test case is run to test the software under the condition that the test control is triggered, so that test data is obtained, wherein the test data comprises a run confirmation identifier, a performance confirmation identifier, a test result of the run confirmation case, a test result of the performance confirmation case and the like. The server obtains the test data of a plurality of test cases to form a test case data set. The test case data set has a corresponding relation with the product name and the version number. The test case data set and the correspondence are part of a verification document data source. And the terminal sends a verification file generation request to the server, wherein the verification file generation request is attached with a product name and a version number. And the server inquires the test data in the verification file data source according to the product name and the version number to obtain a corresponding test case data set.

Step S320: and matching in the test case data set according to the function item identification to obtain a target operation confirmation identification and a target performance confirmation identification which are associated with the function item identification.

Specifically, the test case dataset includes a plurality of operation confirmation identifiers and a plurality of individual performance confirmation identifiers. And matching in the test case data set according to the function item identification to obtain a target operation confirmation identification associated with the function item identification. And matching in the test case data set according to the function item identification to obtain a target performance confirmation identification associated with the function item identification.

In the embodiment, the target operation confirmation identifier and the target performance confirmation identifier associated with the function entry identifier are obtained, the target operation confirmation identifier and the target performance confirmation identifier are filled in the cell of the demand tracking matrix template, and the target operation confirmation identifier, the target performance confirmation identifier and the association relation are visually displayed through the demand tracking matrix template, so that a user can conveniently and quickly check corresponding test related data, and the processing speed of verification work is increased.

In some embodiments, referring to fig. 4a, the method for generating the requirement tracking matrix of the software may further include the following steps.

Step S410: and inquiring the test plan in the verification file data source according to the product name and the version number to obtain the identification information of the corresponding test plan.

Step S420: and inquiring the identification information, the test step data, the test result and the test interface screenshot of the test case included in the test plan according to the identification information of the test plan.

Step S430: and filling the identification information of the test case, the test step data, the test result and the test interface screenshot into the performance confirmation document template according to the data structure of the performance confirmation document template to obtain a performance confirmation document.

Step S440: and filling the identification information, the statistical result and the name data of the test case into the operation confirmation document template according to the data structure of the operation confirmation document template to obtain an operation confirmation document.

Wherein the performance validation document, the run validation document are part of the verification file. Specifically, the verification file data source includes a test plan, and the test plan includes a plurality of test cases. The test plan has identification information, and the test cases included in the test plan have identification information. The test case has identification information, name data, test step data, test results, test interface screenshots and statistical results.

The statistical result may be for the demand module, and the number of each type of defect may be counted for each demand module. As shown in fig. 4b, the defect type may be fatal, severe, general, and suggestive.

And inquiring the test plan in the verification file data source according to the product name and the version number to obtain the identification information of the corresponding test plan. And determining the identification information of the test case included in the test plan according to the identification information of the test plan. According to the identification information of the test case, the test step data in the test case, the test result of the test case and the test interface screenshot generated in the test process can be determined.

When the verification file needs to be generated, and the performance verification document and the operation verification document are part of the verification file, a data structure of the performance verification document template and a data structure of the operation verification document template need to be acquired. And the performance confirmation document template is provided with placeholders, and the identification information of the test case, the test step data, the test result and the test interface screenshot are filled into the performance confirmation document template according to the placeholders in the performance confirmation document template to obtain a performance confirmation document. And the operation confirmation document template is provided with placeholders, and the identification information, the statistical result and the name data of the test case are filled into the operation confirmation document template according to the placeholders in the operation confirmation document template to obtain the operation confirmation document.

In the present embodiment, the performance verification document and the operation verification document are generated and used as part of the verification file. The performance confirmation document is provided with a running confirmation mark, the running confirmation document is provided with a performance confirmation mark, the target running confirmation mark and the target performance confirmation mark which are associated with the function item mark are displayed in the requirement tracking matrix, and the performance confirmation document and the running confirmation document can be accessed through corresponding document hyperlinks, so that test case data in the performance confirmation document and the running confirmation document can be conveniently checked.

In some embodiments, referring to fig. 5, the step of obtaining the screenshot of the test interface may include the following steps.

Step S510: and receiving a test interface screenshot sent by the test terminal.

Step S520: and generating the identification information of the test interface screenshot based on the identification information of the test case generating the test interface screenshot, the number of the current step of the test case generating the test interface screenshot and the screenshot sequence number of the test interface screenshot in the current step.

Step S530: and storing the test interface screenshots according to the dimensions of the test cases.

Specifically, in the software testing process, the testing terminal performs screenshot operation on a software interface in the testing process to obtain a testing interface screenshot, and the testing terminal sends the testing interface screenshot to the server. And the server receives the test interface screenshot. In order to ensure uniqueness of the test interface screenshot, identification information of the test interface screenshot needs to be generated. The number of the test interface screenshots generated when a certain step of the corresponding test case is run during the test interface screenshots can be more than or equal to 1. Each test interface screenshot has a screenshot number, for example, the number of the test interface screenshot is 1 in the first screenshot, and the number of the test interface screenshot is 2 in the second screenshot. Therefore, the identification information of the test interface screenshot can be generated based on the identification information of the test case, the number of the current step of the test case and the screenshot sequence number.

In order to generate a performance confirmation document and obtain an accurate test interface screenshot when the confirmation document is operated, the test interface screenshot is stored according to the dimension of the test case, and the test interface screenshot generated when the test case is operated is stored in a folder named by the test case.

In some embodiments, the step of obtaining the test interface screenshot may further include: and obtaining test operation time corresponding to the test interface screenshot. And rendering the test operation time to a preset position in the test interface screenshot to obtain the test interface screenshot with the timestamp.

In the embodiment, the screenshot of the test interface is realized in an automatic mode, the unique identification is carried out on the screenshot of the test interface, the screenshot of the test interface is stored according to the dimension of the test case, the software test efficiency can be improved, the screenshot of the test interface is obtained according to the test case when the performance confirmation document is generated and the performance confirmation document is operated, the document does not need to be manually arranged, and the workload of verification personnel is greatly reduced.

In some embodiments, referring to fig. 6a, the method for generating the requirement tracking matrix of the software may further include the following steps.

Step S610: and acquiring a technical implementation identifier corresponding to the function item identifier.

Step S620: and correspondingly filling the technical implementation identifier into the requirement tracking matrix template according to the position of the functional item identifier data column in the requirement tracking matrix template so as to generate the requirement tracking matrix.

Wherein the technical implementation identifier is used for representing a technical implementation design document corresponding to the product function represented by the function item identifier. The technical implementation design document may also be referred to as a Technical Design Specification (TDS). Specifically, a technical implementation design document is stored in the server, and the technical implementation design document has a technical implementation identifier. The technical implementation identifier and the function item identifier have a corresponding relationship. After the function item identification is determined, matching is carried out in the corresponding relation between the technical implementation identification and the function item identification according to the function item identification, and the technical implementation identification corresponding to the function item identification is obtained. The data columns of the demand tracking matrix template include technology implementation identification data columns. Aiming at any function item identification, the requirement tracking matrix template has corresponding cells in the technical implementation identification data column, and the technical implementation identification is filled into the corresponding cells in the requirement tracking matrix template to generate the requirement tracking matrix. For example, referring to fig. 6b, the demand tracking matrix includes data columns TDS, which are identification data columns for implementing the technology.

In the embodiment, the technical implementation identifier is filled into the requirement tracking matrix template to generate the requirement tracking matrix, so that the information content of the requirement tracking matrix is enriched, and the document hyperlink of the technical implementation identifier is convenient for a user to check technical implementation design documents.

In some embodiments, referring to fig. 7, the method for generating the requirement tracking matrix of the software may further include the following steps.

Step S710: demand data corresponding to a data column included in a demand specification document template is extracted from a demand entry data set.

Step S720: and performing structure adjustment on the extracted demand data according to the data structure of the demand specification document template to obtain target demand data.

Step S730: filling the target requirement data into a requirement description document template to generate a requirement description document; wherein the requirements specification document is part of the verification file.

Specifically, since the requirement specification document is part of the verification file, the requirement specification document template can be acquired upon receiving the verification file generation request. The requirement specification document template comprises a plurality of data columns. And extracting corresponding requirement data from the requirement item data set according to the data columns included in the requirement specification document template. The requirement data can be a requirement module to which the requirement item identifier belongs, a requirement item identifier and requirement description data corresponding to the requirement item identifier. And sequencing the demand module, the demand item identifier and the demand description data according to the data structure of the demand specification document template to obtain target demand data, correspondingly filling the target demand data into the demand specification document template, and generating a demand specification document.

In the embodiment, the requirement description document can be accessed through the document hyperlink identified by the requirement item, so that a user can conveniently check the requirement description document.

In some embodiments, referring to fig. 8, the method for generating the requirement tracking matrix of the software may further include the following steps.

Step S810: functional design data corresponding to a data column included in the functional design document template is extracted from the functional entry data set.

Step S820: and performing structure adjustment on the extracted functional design data according to the data structure of the functional design document template to obtain target functional design data.

Step S830: and filling the target functional design data into a functional design document template to generate a functional design document.

Wherein the functional design document is part of the verification file. Specifically, since the functional design document is part of the verification file, the functional design document template can be acquired upon receiving the verification file generation request. The functional design document template includes a number of data columns. And extracting corresponding functional design data from the functional item data set according to the data columns included in the functional design document template. The function design data can be a requirement module to which a requirement item identifier associated with the function item identifier belongs, the function item identifier, and function description data corresponding to the function item identifier. And sequencing the demand module, the function item identification and the function design description data according to the data structure of the function design document template to obtain target function design data, correspondingly filling the target function design data into the function design document template, and generating a function design document.

In the embodiment, the functional design document can be accessed through the document hyperlink identified by the functional item, so that a user can conveniently check the functional design document.

It should be understood that, although the steps in the above-described flowcharts are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the above-mentioned flowcharts may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the steps or the stages is not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a part of the steps or the stages in other steps.

Referring to fig. 9, an embodiment of the present disclosure provides a device for generating a requirement tracking matrix of software. The device for generating the requirement tracking matrix of the software comprises a name version number acquisition module, a requirement item query module, a function item query module, a confirmation identifier acquisition module, an identifier data splicing module and an identifier data filling module.

And the name version number acquisition module is used for acquiring the name and the version number of the product.

The requirement item query module is used for querying requirement items in the verification file data source according to the product names and the version numbers to obtain a corresponding requirement item data set; the requirement item data set comprises a requirement item identifier and requirement description data corresponding to the requirement item identifier; the verification file data source is obtained by collecting data generated by design operation, development operation and test operation through a development management system in the development process of the software and is used for generating a verification file; the development management system is a platform system used for following the design operation, the development operation and the test operation of the software.

The function item query module is used for querying function items in the verification file data source according to the required item identification to obtain a corresponding function item data set; wherein the function item dataset comprises a function item identification associated with the requirement item identification.

And the confirmation identifier acquisition module is used for acquiring the target operation confirmation identifier and the target performance confirmation identifier which are associated with the function item identifier.

And the identification data splicing module is used for performing data splicing on the requirement item identification, the requirement description data corresponding to the requirement item identification, the function item identification associated with the requirement item identification, the target operation confirmation identification and the target performance confirmation identification according to the data structure of the requirement tracking matrix template to obtain target identification data adaptive to the data structure.

The identification data filling module is used for correspondingly filling the target identification data into the cells of the requirement tracking matrix template so as to generate a requirement tracking matrix; wherein, the demand tracking matrix is used as a part of the verification file; the identification data filled into each cell in the demand tracking matrix is provided with a corresponding document hyperlink; the identification data in the cells is identification information of a document associated with the document hyperlink, and the document hyperlink is used for accessing the associated document.

For specific limitations of the requirement tracking matrix generation device for software, reference may be made to the above limitations of the requirement tracking matrix generation method for software, and details are not described here. The modules in the software requirement tracking matrix generating device can be wholly or partially realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In some embodiments, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in fig. 10. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a method for generating a demand tracking matrix for software. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.

Those skilled in the art will appreciate that the architecture shown in fig. 10 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing device to which the disclosed aspects apply, and that a computing device may in particular include more or less components than those shown, or combine certain components, or have a different arrangement of components.

In some embodiments, a computer device is provided, comprising a memory having a computer program stored therein and a processor that, when executing the computer program, performs the method steps of the above embodiments.

In some embodiments, a computer-readable storage medium is provided, on which a computer program is stored, which when executed by a processor implements the method steps in the above-described embodiments.

In some embodiments, a computer program product is also provided, which comprises instructions that are executable by a processor of a computer device to implement the method steps in the above-described embodiments.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the various embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.

The features of the above embodiments may be arbitrarily combined, and for the sake of brevity, all possible combinations of the features in the above embodiments are not described, but should be construed as being within the scope of the present specification as long as there is no contradiction between the combinations of the features.

The above description is only for the purpose of illustrating the preferred embodiments of the present disclosure and is not to be construed as limiting the present disclosure, and any modifications, equivalents and the like that are within the spirit and principle of the present disclosure are intended to be included within the scope of the present disclosure.

Claims

1. A method for generating a requirement tracking matrix of software is characterized in that a data structure of a requirement tracking matrix template comprises a requirement item identification data column, a requirement description data column, a function item identification data column, an operation confirmation identification data column and a performance confirmation identification data column; the method comprises the following steps:

acquiring a product name and a version number;

inquiring requirement items in a verification file data source according to the product name and the version number to obtain a corresponding requirement item data set; the requirement item data set comprises a requirement item identifier and requirement description data corresponding to the requirement item identifier; the verification file data source is obtained by collecting data generated by design operation, development operation and test operation through a development management system in the development process of the software and is used for generating a verification file; the development management system is a platform system used for following the design operation, the development operation and the test operation of the software;

inquiring function items in the verification file data source according to the requirement item identification to obtain a corresponding function item data set; wherein the function item dataset comprises a function item identification associated with the requirement item identification;

acquiring a target operation confirmation identifier and a target performance confirmation identifier which are associated with the function item identifier;

according to a data structure of a demand tracking matrix template, performing data splicing on the demand entry identification, demand description data corresponding to the demand entry identification, a function entry identification associated with the demand entry identification, the target operation confirmation identification and the target performance confirmation identification to obtain target identification data adaptive to the data structure;

filling the target identification data into cells of the demand tracking matrix template to generate a demand tracking matrix; wherein the requirement tracking matrix is used as a part of the verification file; the identification data filled into each cell in the demand tracking matrix is provided with a corresponding document hyperlink; the identification data in the cells is identification information of a document associated with the document hyperlink, and the document hyperlink is used for accessing the associated document.

2. The method of claim 1, wherein obtaining the target operation confirmation identification and the target performance confirmation identification associated with the function entry identification comprises:

inquiring test data in the verification file data source according to the product name and the version number to obtain a corresponding test case data set; the test case data set comprises an operation confirmation mark and a performance confirmation mark;

and matching in the test case data set according to the function item identification to obtain a target operation confirmation identification and a target performance confirmation identification which are associated with the function item identification.

3. The method of claim 1, further comprising:

inquiring a test plan in the verification file data source according to the product name and the version number to obtain identification information of the corresponding test plan;

inquiring the identification information, the test step data, the test result and the test interface screenshot of the test case included in the test plan according to the identification information of the test plan;

filling the identification information of the test case, the test step data, the test result and the test interface screenshot into the performance confirmation document template according to the data structure of the performance confirmation document template to obtain a performance confirmation document;

filling the identification information, the statistical result and the name data of the test case into the operation confirmation document template according to the data structure of the operation confirmation document template to obtain an operation confirmation document; wherein the performance validation document and the operation validation document are part of the verification file.

4. The method of claim 3, wherein the step of obtaining the test interface screenshot comprises:

receiving a test interface screenshot sent by a test terminal;

generating identification information of the test interface screenshot based on the identification information of the test case generating the test interface screenshot, the number of the current step of the test case generating the test interface screenshot and the screenshot sequence number of the test interface screenshot in the current step;

and storing the test interface screenshot according to the dimension of the test case.

5. The method of claim 4, wherein the step of obtaining the test interface screenshot further comprises:

acquiring test operation time corresponding to the test interface screenshot;

and rendering the test operation time to a preset position in the test interface screenshot to obtain the test interface screenshot with a timestamp.

6. The method of claim 1, further comprising:

acquiring a technical implementation identifier corresponding to the function item identifier; wherein the technical implementation identifier is used for representing a technical implementation design document corresponding to the product function represented by the function item identifier;

and correspondingly filling the technical implementation identifier into the requirement tracking matrix template according to the position of the functional item identifier data column in the requirement tracking matrix template to generate the requirement tracking matrix.

7. The method of claim 1, further comprising:

extracting requirement data corresponding to a data column included in a requirement description document template from the requirement item data set;

performing structure adjustment on the extracted demand data according to the data structure of the demand specification document template to obtain target demand data;

filling the target requirement data into the requirement specification document template to generate a requirement specification document; wherein the requirement specification document is included as part of the verification file.

8. The method of claim 1, further comprising:

extracting functional design data corresponding to a data column included in a functional design document template from the functional entry dataset;

performing structural adjustment on the extracted functional design data according to the data structure of the functional design document template to obtain target functional design data;

filling the target function design data into the function design document template to generate a function design document; wherein the functional design document is part of the verification file.

9. The device for generating the requirement tracking matrix of the software is characterized in that a data structure of a requirement tracking matrix template comprises a requirement item identification data column, a requirement description data column, a function item identification data column, an operation confirmation identification data column and a performance confirmation identification data column; the device comprises:

the name version number acquisition module is used for acquiring the name and the version number of the product;

the requirement item query module is used for querying requirement items in a verification file data source according to the product name and the version number to obtain a corresponding requirement item data set; the requirement item data set comprises a requirement item identifier and requirement description data corresponding to the requirement item identifier; the verification file data source is obtained by collecting data generated by design operation, development operation and test operation through a development management system in the development process of the software and is used for generating a verification file; the development management system is a platform system used for following the design operation, the development operation and the test operation of the software;

the function item query module is used for querying function items in the verification file data source according to the requirement item identification to obtain a corresponding function item data set; wherein the function item dataset comprises a function item identification associated with the requirement item identification;

the confirmation identifier acquisition module is used for acquiring a target operation confirmation identifier and a target performance confirmation identifier which are associated with the function item identifier;

the identification data splicing module is used for performing data splicing on the requirement item identification, the requirement description data corresponding to the requirement item identification, the function item identification associated with the requirement item identification, the target operation confirmation identification and the target performance confirmation identification according to the data structure of the requirement tracking matrix template to obtain target identification data adaptive to the data structure;

the identification data filling module is used for correspondingly filling the target identification data into the cells of the demand tracking matrix template so as to generate a demand tracking matrix; wherein the requirement tracking matrix is used as a part of the verification file; the identification data filled into each cell in the demand tracking matrix is provided with a corresponding document hyperlink; the identification data in the cells is identification information of a document associated with the document hyperlink, and the document hyperlink is used for accessing the associated document.

10. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 8.

11. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 8.