A document bidirectional tracing method and related device

Abstract

The application discloses a document bidirectional tracing method and a related device. The method comprises the following steps: obtaining a first task and a second task with a bidirectional tracing relationship, the first task comprising a plurality of first documents, and the second task comprising a plurality of second documents; obtaining a tracing identifier in each first document, matching each tracing identifier with the plurality of second documents, determining at least one second document corresponding to each first document, and taking the relationship between each first document and the at least one second document corresponding thereto as a first tracing relationship; based on each first document and the at least one second document corresponding to each first document, determining at least one first document corresponding to each second document, and taking the relationship between each second document and the at least one first document corresponding thereto as a second tracing relationship; and generating a bidirectional tracing list based on the first tracing relationship and the second tracing relationship. In this way, the efficiency of bidirectional tracing is improved, and the accuracy of bidirectional tracing is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, in particular to a document bidirectional tracing method and related device. BACKGROUND

[0002] Currently, different tasks are set in software production, for example, system requirement, system architecture, software requirement, software architecture, detailed design, coding, unit testing, integration testing, system testing and the like. In order to ensure the high quality and reliability of the developed software, bidirectional tracing needs to be performed for each task. For example, task A is software requirement, task B is software architecture, and task B needs to be bidirectionally traced with task A, that is, task B confirms that the development for software requirement is completed, and task A needs to confirm that task B does not miss anything for product development.

[0003] In the related art, manual bidirectional tracing is generally performed for each task link. However, when the number of tasks is large, the efficiency of manual bidirectional tracing is low, and errors are prone to occur. SUMMARY

[0004] Based on the above problems, the present application provides a document bidirectional tracing method and related device, aiming at solving the problems of low efficiency and prone to errors of manual bidirectional tracing.

[0005] The embodiments of the present application disclose the following technical solutions:

[0006] In a first aspect, the embodiments of the present application provide a document bidirectional tracing method, which comprises:

[0007] obtaining a first task and a second task; the first task and the second task are tasks in a target project; the first task and the second task have a bidirectional tracing relationship; the first task comprises a plurality of first documents, and the second task comprises a plurality of second documents;

[0008] obtaining a tracing identifier in each first document;

[0009] matching each tracing identifier with the plurality of second documents, determining at least one second document corresponding to each first document, and taking the relationship between each first document and the corresponding at least one second document as a first tracing relationship;

[0010] based on each first document and the at least one second document corresponding to each first document, determining at least one first document corresponding to each second document, and taking the relationship between each second document and the corresponding at least one first document as a second tracing relationship;

[0011] generating a bidirectional tracing list based on the first tracing relationship and the second tracing relationship.

[0012] Optionally, before the first task and the second task are acquired, the method further comprises:

[0013] acquiring a target project; the target project comprises a plurality of tasks;

[0014] selecting at least two tasks from the plurality of tasks as target tasks; wherein the first task and the second task are any two adjacent tasks in the target tasks; there is a trace-back relationship between the two adjacent tasks in the at least two target tasks.

[0015] Optionally, the plurality of documents in each target task are obtained by:

[0016] creating an entry according to the determined document type of the target document to be created; the entry comprises at least one of a name, a description or a use of the target document; the target document is any one of the documents in any one of the target tasks;

[0017] configuring a unique identifier of the target document;

[0018] determining a trace-back document having a trace-back relationship with the target document, and determining a trace-back identifier based on the trace-back document;

[0019] creating the target document according to the entry, the unique identifier and the trace-back identifier.

[0020] Optionally, after the bidirectional trace-back list is generated based on the first trace-back relationship and the second trace-back relationship, the method further comprises:

[0021] determining whether the bidirectional trace-back list is consistent with a historical bidirectional trace-back list; the historical bidirectional trace-back list is obtained based on each first historical trace-back relationship and each second historical trace-back relationship; the first historical trace-back relationship indicates a relationship between each first historical document and at least one corresponding second historical document; the second historical trace-back relationship indicates a relationship between each second historical document and at least one corresponding first historical document; each first historical document is a document of the first task at a historical time; each second historical document is a document of the second task at the historical time;

[0022] if the bidirectional trace-back list is consistent with the historical bidirectional trace-back list, a historical trace-back report corresponding to the historical bidirectional trace-back list is taken as a trace-back report of the bidirectional trace-back list;

[0023] if the bidirectional trace-back list is not consistent with the historical bidirectional trace-back list, a corresponding trace-back report is determined based on the bidirectional trace-back list.

[0024] In a second aspect, an embodiment of the present application provides a document bidirectional trace-back device, which comprises:

[0025] The first obtaining module is configured to obtain a first task and a second task; the first task and the second task are tasks in a target project; the first task and the second task have a bidirectional traceability relationship; the first task includes a plurality of first documents, and the second task includes a plurality of second documents;

[0026] The second obtaining module is configured to obtain a traceability identifier in each first document;

[0027] The first traceability module is configured to match each traceability identifier with the plurality of second documents, determine at least one second document corresponding to each first document, and determine a relationship between each first document and the at least one corresponding second document as a first traceability relationship;

[0028] The second traceability module is configured to determine at least one first document corresponding to each second document based on each first document and the at least one second document corresponding to each first document, and determine a relationship between each second document and the at least one corresponding first document as a second traceability relationship;

[0029] The bidirectional traceability module is configured to generate a bidirectional traceability list based on the first traceability relationship and the second traceability relationship.

[0030] Optionally, before the first obtaining module, the method further includes a screening module configured to:

[0031] Obtain a target project; the target project includes a plurality of tasks;

[0032] Screen at least two tasks from the plurality of tasks as target tasks; wherein the first task and the second task are any two adjacent tasks in the target tasks; the at least two target tasks have a traceability relationship between the two adjacent tasks.

[0033] Optionally, the plurality of documents in each target task are obtained by the following method:

[0034] A creating unit is configured to determine a document type of a target document to be created, and create a corresponding entry according to the document type; the entry includes at least one of a name, a description, or a use of the target document; the target document is any one of the documents in any one of the target tasks;

[0035] A configuration unit is configured to configure a unique identifier of the target document;

[0036] A determination unit is configured to determine a traceability document having a traceability relationship with the target document, and determine a traceability identifier based on the traceability document;

[0037] A document creating unit is configured to create the target document according to the entry, the unique identifier, and the traceability identifier.

[0038] Optionally, after the bidirectional traceability module, the method further includes:

[0039] a judging module, configured to judge whether the bidirectional trace list is consistent with a historical bidirectional trace list, the historical bidirectional trace list being obtained based on each first historical trace relationship and each second historical trace relationship, the first historical trace relationship indicating a relationship between each first historical document and at least one corresponding second historical document, the second historical trace relationship indicating a relationship between each second historical document and at least one corresponding first historical document, each first historical document being a document of a first task at a historical time, each second historical document being a document of a second task at the historical time;

[0040] a report generating module, configured to, if the bidirectional trace list is consistent with the historical bidirectional trace list, take a historical trace report corresponding to the historical bidirectional trace list as a trace report of the bidirectional trace list, and if the bidirectional trace list is not consistent with the historical bidirectional trace list, determine a corresponding trace report based on the bidirectional trace list.

[0041] In a third aspect, an embodiment of the present application provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the document bidirectional trace method in the first aspect is implemented.

[0042] In a fourth aspect, an embodiment of the present application provides a computer readable storage medium, and the computer readable storage medium stores instructions, and when the instructions are executed on a terminal device, the terminal device executes the document bidirectional trace method in the first aspect.

[0043] Compared with the prior art, the present application has the following beneficial effects:

[0044] The document bidirectional trace method provided by the embodiment of the present application includes the following steps: obtaining a first task and a second task that exist in a bidirectional trace relationship, wherein the first task and the second task are both tasks in a target project, the first task includes a plurality of first documents, and the second task includes a plurality of second documents; obtaining a trace identifier in each first document, matching each trace identifier with the plurality of second documents, determining at least one second document corresponding to each first document, and taking a relationship between each first document and the at least one corresponding second document as a first trace relationship; based on each first document and the at least one second document corresponding to each first document, determining at least one first document corresponding to each second document, and taking a relationship between each second document and the at least one corresponding first document as a second trace relationship; and further generating a bidirectional trace list based on the first trace relationship and the second trace relationship.

[0045] Therefore, by the traceable identification of the first document, the first traceable relationship is determined according to the traceable identification of the at least one second document corresponding to the first document, the document traceable from the first task to the second task is realized, the second traceable relationship is determined according to the reverse traceable of the at least one first document corresponding to the second document according to the first traceable relationship, the document traceable from the second task to the first task is realized, and the bidirectional traceable list is determined according to the first traceable relationship and the second traceable relationship, thereby realizing the bidirectional traceable between the first task and the second task. Unlike the manual processing in the prior art, the present scheme can realize automatic processing, improve the efficiency of bidirectional traceable, and improve the accuracy of bidirectional traceable. BRIEF DESCRIPTION OF DRAWINGS

[0046] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed to be used in the embodiments or the prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0047] Figure 1 A flowchart of a document bidirectional traceable method provided by an embodiment of the present application;

[0048] Figure 2a A schematic diagram of a document bidirectional traceable method provided by an embodiment of the present application;

[0049] Figure 2b A schematic diagram of another document bidirectional traceable method provided by an embodiment of the present application;

[0050] Figure 3 A structural schematic diagram of a document bidirectional traceable device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0051] At present, different tasks are set in the software architecture. In order to ensure the high quality and reliability of the developed software, bidirectional traceable needs to be performed for each task. For example, task A is software requirement, task B is software architecture, and task B needs to be bidirectionally traced with task A, that is, task B confirms that the development for software requirement is completed, and task A needs to confirm that task B does not miss the software architecture.

[0052] In the related art, manual bidirectional traceable needs to be performed for each task link. However, when the number of tasks is large, for example, a task includes 10 documents, and each document may have several hundred pages or even thousands of pages (such as detailed design), manual bidirectional traceable needs to be performed for the 10 documents one by one, which leads to low efficiency of manual bidirectional traceable and is prone to errors.

[0053] To solve the above problems, the embodiment of the present application provides a document bidirectional tracing method and a related device. The method comprises: obtaining a first task and a second task having a bidirectional tracing relationship, wherein the first task and the second task are tasks in a target project, the first task comprises a plurality of first documents, and the second task comprises a plurality of second documents; then obtaining a tracing identifier in each first document, matching each tracing identifier with the plurality of second documents, determining at least one second document corresponding to each first document, and taking the relationship between each first document and the at least one second document corresponding thereto as a first tracing relationship; based on each first document and the at least one second document corresponding to each first document, determining at least one first document corresponding to each second document, and taking the relationship between each second document and the at least one first document corresponding thereto as a second tracing relationship; and further generating a bidirectional tracing list based on the first tracing relationship and the second tracing relationship.

[0054] In this way, by means of the tracing identifier of the first document, the at least one second document corresponding to the first document is determined according to the tracing identifier, the first tracing relationship is determined, the document tracing from the first task to the second task is realized, the at least one first document corresponding to the second document is reversely traced according to the first tracing relationship, the second tracing relationship is determined, the document tracing from the second task to the first task is realized, and the bidirectional tracing list is determined by means of the first tracing relationship and the second tracing relationship, thereby realizing the bidirectional tracing between the first task and the second task. Different from the manual processing in the prior art, the present application can realize automatic processing, improve the efficiency of bidirectional tracing, and improve the accuracy of bidirectional tracing.

[0055] To make the personnel in the technical field better understand the present application, the technical solutions in the embodiments of the present application will be described clearly and completely in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by the personnel in the field without creative labor fall within the scope of protection of the present application.

[0056] Referring to Figure 1 The figure is a flowchart of a document bidirectional tracing method provided by the embodiment of the present application.

[0057] In conjunction with Figure 1 the embodiment of the present application provides a document bidirectional tracing method, which can comprise:

[0058] S101: obtaining a first task and a second task.

[0059] It should be understood that in the embodiments of the present application, the target project means a project to be processed, for example, the target project is to develop a software. The target project can include a plurality of tasks, and there is a trace relationship between two adjacent tasks in the plurality of tasks. As an example, assuming that the target project includes four tasks, namely task A, task B, task C and task D, there can be a bidirectional trace relationship between task A and task B, a bidirectional trace relationship between task B and task C, and a bidirectional trace relationship between task C and task D.

[0060] In the embodiments of the present application, the first task and the second task are tasks in the target project; the first task and the second task have a bidirectional trace relationship; the first task includes a plurality of first documents, and the second task includes a plurality of second documents. It should be understood that in the embodiments of the present application, each task can include one or more documents, and the document types of the plurality of documents under one task can be the same or different, which is not specifically limited again. As an example, assuming that the first task includes four documents, namely document A, document B, document C and document D, document A and document B can be documents of the same type, and document C and document D can be documents of different types.

[0061] The bidirectional trace relationship means that the documents corresponding to the two tasks can be confirmed and viewed bidirectionally, for example, task A includes three documents a, b and c, and task B includes two documents d and e. When task B traces task A, document d corresponds to document a, and document e corresponds to documents b and c. When task A traces task B, document a corresponds to document d, document b corresponds to document e, and document c corresponds to document e.

[0062] In a possible implementation, before S101 is performed, the method can further include:

[0063] A1: obtaining a target project.

[0064] The target project includes a plurality of tasks. It should be understood that in the embodiments of the present application, the bidirectional trace is performed between the plurality of tasks in the same project, and therefore, all the tasks in the target project need to be obtained.

[0065] A2: selecting at least two tasks from the plurality of tasks as target tasks.

[0066] The first task and the second task are any two adjacent tasks in the target tasks; and there is a trace relationship between the two adjacent tasks in the at least two target tasks.

[0067] It should be understood that in an embodiment of the present application, the target project may include tasks that do not require two-way traceability. In order to improve the efficiency of two-way traceability, multiple tasks can be screened to select tasks that require two-way traceability. For example, the target project includes design tasks, management tasks, and R&D tasks. Management tasks do not require two-way traceability, so management tasks can be filtered out and design tasks and R&D tasks can be used as target tasks.

[0068] It should be noted that in some possible implementations, tasks may be screened based on their importance, a weight threshold may be set, and tasks whose weight in the target project is greater than the weight threshold may be selected as target tasks.

[0069] It should be understood that there may be multiple target projects. To ensure data consistency and facilitate subsequent tracing, multiple documents in each target task can be obtained in the following ways:

[0070] B1: Determine the document type of the target document to be created, and create a corresponding entry according to the document type.

[0071] The entry includes at least one of the name, description or purpose of the target document; the target document is any document in any target task in each target task.

[0072] Document type refers to the type of document created. Document types may include requirement documents, design documents, test documents, user manuals, installation guides, etc. Different documents have their own specific structure and content requirements.

[0073] An entry is a directory that contains basic information about a document, such as its name, description, or purpose. An entry helps you quickly understand the content and purpose of a document.

[0074] It should be understood that determining the document type and creating corresponding entries is conducive to improving the standardization of document management and ensuring that each type of document complies with the corresponding standards and formats.

[0075] B2: Configure the unique identifier of the target document.

[0076] Unique identification involves assigning a unique identifier (such as a document number or version number) to each target document, ensuring that it can be uniquely identified within the target project. In one possible implementation, project management tools or document management systems can be used to automatically assign and track these unique identifiers. This avoids confusion and misuse between documents and improves document management accuracy.

[0077] B3: Determine a traceability document that has a traceability relationship with the target document, and determine a traceability identifier based on the traceability document.

[0078] It should be understood that in the software architecture, one document can have a dependency or reference relationship with other documents, for example, a design document can refer to some requirements in the requirement document. Such dependency or reference relationship is referred to as a trace relationship. In order to be able to quickly find the association between them when needed, it is necessary to assign a trace identifier to these related documents. Improving traceability between documents helps to quickly locate the cause when problems occur. At the same time, it promotes the cooperation between documents and ensures the consistency and integrity of the target project.

[0079] B4: Create a target document according to the entry, unique identifier and trace identifier.

[0080] In the project management tool or document management system, according to the entry, unique identifier and trace identifier created in the previous steps, the target document can then be formally created. Among them, the document content is filled in according to the requirements of the document type, ensuring that the structure of the document is clear and easy to understand.

[0081] S102: Obtain the trace identifier in each first document.

[0082] The trace identifier means an identifier used to indicate the dependency or reference relationship between documents (i.e. the trace relationship). By obtaining the trace identifier of the first document, the corresponding second document can be determined according to the trace relationship indicated by the trace identifier.

[0083] S103: Match each trace identifier with a plurality of second documents, determine at least one second document corresponding to each first document, and take the relationship between each first document and the corresponding at least one second document as a first trace relationship.

[0084] It should be understood that matching the trace identifier with the plurality of documents corresponding to the second task can determine the corresponding second document. If there is no corresponding second document, a matching failure information can be output to indicate that the first document trace fails, indicating that there is a redundant first document in the first task.

[0085] S104: Determine at least one first document corresponding to each second document based on each first document and the at least one second document corresponding to each first document, and take the relationship between each second document and the corresponding at least one first document as a second trace relationship.

[0086] It should be understood that after determining the respective first trace relationship, the first document in the first task can also be traced back from the second document of the second task based on the first trace relationship (i.e., the respective first document and the at least one second document corresponding to the respective first document), that is, after the first task traces the second task, there is a first trace relationship from the first task to the second task, and further combined with the known first trace relationship, the second trace relationship from the second task to the first task can be further traced back in reverse to realize bidirectional tracing.

[0087] If there is no first document corresponding to the second document, it indicates that the first document for the second document is missing in the first task, and the matching failure information can be output to indicate that the second document fails to trace.

[0088] S105: generating a bidirectional trace list based on the first trace relationship and the second trace relationship.

[0089] It should be understood that after determining the first trace relationship and the second trace relationship, the bidirectional trace list can be generated to realize bidirectional tracing between the first task and the second task. In some possible implementations, the matching failure information output in the process of determining the first trace relationship (referred to as first failure information) and the matching failure information output in the process of determining the second trace relationship (referred to as second failure information) can be synchronously integrated in the bidirectional trace list, facilitating subsequent analysis by researchers.

[0090] In the embodiments of the present application, the trace identifier of the first document is determined, and then at least one second document corresponding to the first document is determined according to the trace identifier, the first trace relationship is determined, the document trace from the first task to the second task is realized, further at least one first document corresponding to the second document can be traced back in reverse according to the first trace relationship, the second trace relationship is determined, the document trace from the second task to the first task is realized, and then the bidirectional trace list is determined by the first trace relationship and the second trace relationship, and bidirectional tracing between the first task and the second task is realized. Different from the manual processing in the prior art, the present scheme can realize automatic processing, improve the efficiency of bidirectional tracing, and improve the accuracy of bidirectional tracing.

[0091] Based on the document bidirectional tracing method provided in the above embodiments, in a possible implementation manner, after step S105, the method can further include: judging whether the bidirectional trace list is consistent with a historical bidirectional trace list.

[0092] The historical bidirectional tracing list is obtained based on each first historical tracing relationship and each second historical tracing relationship, the first historical tracing relationship indicates a relationship between each first historical document and at least one corresponding second historical document, the second historical tracing relationship indicates a relationship between each second historical document and at least one corresponding first historical document, each first historical document is a document of the first task at a historical time, and each second historical document is a document of the second task at the historical time.

[0093] It should be understood that, in the embodiment of the present application, there can be a historical bidirectional tracing list of the previous time (i.e., the historical time) for bidirectional tracing. In order to avoid repeated analysis, the bidirectional tracing list of the current time can be compared with the historical bidirectional tracing list of the historical time. If the bidirectional tracing list is consistent with the historical bidirectional tracing list, the historical tracing report corresponding to the historical bidirectional tracing list is used as the tracing report of the bidirectional tracing list, and it is not necessary to calculate again. If the bidirectional tracing list is not consistent with the historical bidirectional tracing list, the corresponding tracing report is determined based on the bidirectional tracing list.

[0094] In the embodiment of the present application, whether to use the historical tracing report of the historical time or to calculate the tracing report based on the bidirectional tracing list is determined by comparing the bidirectional tracing list with the historical bidirectional tracing list, so that repeated calculation is avoided, and the efficiency of bidirectional tracing is improved.

[0095] Based on the document bidirectional tracing method provided in the above embodiment, referring to Figure 2a , the figure is a schematic diagram of another document bidirectional tracing method provided in the embodiment of the present application, and in combination with Figure 2a , the document bidirectional tracing method provided in the embodiment of the present application can include the following steps.

[0096] Step 1: Establish a project.

[0097] It should be understood that, in the embodiment of the present application, different projects can be determined according to different research and development needs, such as developing software, developing new functions, and the like.

[0098] Step 2: Perform task clipping according to the situation of the project to obtain a target project.

[0099] Performing task clipping according to the situation of the project means that the situation of the bidirectional tracing demand between each task in the project is used to delete or retain the tasks in the project. If there is no bidirectional tracing demand between task A and task B, task A and task B can be deleted. If there is a bidirectional tracing demand between task B and task C, task A can be deleted, and task B and task C can be retained.

[0100] It should be understood that multiple tasks are included in the target project, the importance of each task is different, and there is a need for bidirectional traceability between some tasks, so it is necessary to formulate the tasks needed to be performed in the target project process, delete the tasks that do not need to be bidirectionally traced, and improve the efficiency of bidirectional traceability.

[0101] Step 3: Formulate the document template of the corresponding process and the traceability relationship.

[0102] It should be noted that the configuration process of the document template and the traceability relationship in the embodiments of the present application is described in the above embodiments, and will not be described here.

[0103] Step 4: After the document template is formulated, the target project is configured.

[0104] For example, configure the document information that needs to be bidirectionally traced in the project, configure the ID information of each document, configure the traceability relationship information of each file, data that does not participate in identification (such as data with deletion lines does not participate in traceability, data with field Status as Invalid does not participate in traceability Status, Invalid is a configuration item), when one-to-many traceability, separator information of multiple IDs, template for generating reports and position of report generation result in the template, file name format for generating reports, whether case sensitive when tracing, and start and end identification information of the content to be traced of each document. The example configuration is as follows:

[0105]

[0106]

[0107]

[0108] Step 5: The tool containing the target project configuration or the configuration is issued to the user who needs to perform bidirectional traceability.

[0109] It should be understood that after the target project configuration is completed, the tool containing such configuration or the configuration can be issued to the user who needs to perform bidirectional traceability, so as to realize bidirectional traceability.

[0110] Step 6: The user confirms the position of the material that needs to be traced based on the target project configuration, and can use the tool to bidirectionally trace the document and the upstream document during the process of writing the current document, so as to ensure that there is no omission in design execution.

[0111] It should be understood that the user can write the document according to the target project configuration, for example, the target project configuration presets the number of the document, so the user can select the number corresponding to the current document according to the target project configuration, so as to facilitate subsequent traceability.

[0112] Step 7: Task completion.

[0113] It should be understood that when the task is completed, the bidirectional traceability result can be displayed in the form of Table 1 as follows:

[0114] Table 1: Bidirectional traceability result

[0115] Document ID 1 for Task 1 Document ID 2 for Task 2 Bidirectional traceability result RD-BSC-001 SD-BWU-07 OK RD-BSC-002 SD-BWU-10 OK RD-BSC-003 SD-BWU-07 NG RD-MP-001 SD-BWU-MP-02 OK

[0116] Wherein, task 1 represents the first task, the document ID of task 1 represents the traceability identifier corresponding to each first document in task 1, task 2 represents the second task, the document ID of task 2 represents the identifier of each second document, the relationship between ID1 and ID2 is the first traceability relationship, the traceability relationship between ID2 and ID1 is the second traceability relationship, OK represents that the bidirectional traceability result is correct, and NG represents that the bidirectional traceability result is incorrect.

[0117] Based on the document bidirectional traceability method provided in the above embodiment, referring to Figure 2b , the user can perform bidirectional traceability according to the following manner:

[0118] Step 1: The user loads the target project configuration.

[0119] Wherein, after the target project configuration in the above step 4 is completed, the target project configuration can be sent to the user, and the user can load the target project configuration.

[0120] Step 2: Load the user configuration according to the target project configuration.

[0121] For example, the location of the document to be traced, the trace to be performed, the module name, the report output directory, etc.

[0122] Step 3: Analyze the traceability relationship between the first document and the second document into a two-dimensional table according to the target project configuration.

[0123] Wherein, if the first document or the second document has been analyzed and has no change, it will not be analyzed repeatedly. The two-dimensional table means a table used to indicate the traceability relationship between the plurality of first documents of the first task and the plurality of second documents of the second task.

[0124] Step 4: Generate a bidirectional traceability report using the data of the two-dimensional table.

[0125] Wherein, the two-dimensional table includes the first traceability relationship and the second traceability relationship, and based on the first traceability relationship and the second traceability relationship, a bidirectional traceability list (i.e., a bidirectional traceability report) can be generated, which can be referred to Table 1 above.

[0126] Step 5: The user proofreads the bidirectional traceability report and corrects the first document or the second document.

[0127] It should be understood that, in order to ensure the correctness of the traceability, a manual secondary check can be further performed according to the bidirectional traceability report, and the first document or the second document is revised based on the check result.

[0128] Step six: end the process, or re-execute step two.

[0129] It should be understood that, if the bidirectional traceability report indicates that the bidirectional traceability relationship between the first document and the second document is correct, the process can be ended; if the bidirectional traceability report indicates that the bidirectional traceability relationship (the first traceability relationship and / or the second traceability relationship) between the first document and the second document is incorrect, the first document and / or the second document can be modified, and step two can be re-executed until the bidirectional traceability report indicates that it is correct.

[0130] Based on the document bidirectional traceability method provided in the above embodiment, an embodiment of the present application further provides a document bidirectional traceability device, which is shown in Figure 3 , which is a structural schematic diagram of the document bidirectional traceability device provided by the embodiment of the present application, and in combination with Figure 3 , the document bidirectional traceability device 300 provided by the embodiment of the present application can include:

[0131] The first acquisition module 301 is configured to acquire a first task and a second task; the first task and the second task are tasks in a target project; the first task and the second task have a bidirectional traceability relationship; the first task includes a plurality of first documents, and the second task includes a plurality of second documents;

[0132] The second acquisition module 302 is configured to acquire a traceability identifier in each first document;

[0133] The first traceability module 303 is configured to match each traceability identifier with the plurality of second documents, determine at least one second document corresponding to each first document, and determine a relationship between each first document and the corresponding at least one second document as a first traceability relationship;

[0134] The second traceability module 304 is configured to determine at least one first document corresponding to each second document based on each first document and the at least one second document corresponding to each first document, and determine a relationship between each second document and the corresponding at least one first document as a second traceability relationship;

[0135] The bidirectional traceability module 305 is configured to generate a bidirectional traceability list based on the first traceability relationship and the second traceability relationship.

[0136] In a possible implementation, before the first acquisition module 301, there further includes a screening module configured to:

[0137] acquire a target project; the target project includes a plurality of tasks;

[0138] select at least two tasks from the plurality of tasks as target tasks; wherein the first task and the second task are any two adjacent tasks in the target tasks; and there is a trace relationship between any two adjacent tasks in the at least two target tasks.

[0139] In a possible implementation, the plurality of documents in each target task are obtained by:

[0140] The creating unit is configured to create an entry corresponding to the document type of the target document to be created according to the determination; the entry includes at least one of a name, a description, or a use of the target document; and the target document is any one of the documents in any one of the target tasks.

[0141] The configuring unit is configured to configure a unique identifier of the target document.

[0142] The determining unit is configured to determine a trace document having a trace relationship with the target document, and determine a trace identifier based on the trace document.

[0143] The document creating unit is configured to create the target document according to the entry, the unique identifier, and the trace identifier.

[0144] In a possible implementation, after the bidirectional trace module 305, the apparatus further includes:

[0145] The judging module is configured to judge whether the bidirectional trace list is consistent with a historical bidirectional trace list; the historical bidirectional trace list is obtained based on each first historical trace relationship and each second historical trace relationship; the first historical trace relationship indicates a relationship between each first historical document and at least one second historical document corresponding to the first historical document; the second historical trace relationship indicates a relationship between each second historical document and at least one first historical document corresponding to the second historical document; each first historical document is a document of the first task at a historical time point; and each second historical document is a document of the second task at the historical time point.

[0146] The report generating module is configured to, if the bidirectional trace list is consistent with the historical bidirectional trace list, take a historical trace report corresponding to the historical bidirectional trace list as a trace report of the bidirectional trace list; and if the bidirectional trace list is not consistent with the historical bidirectional trace list, determine a corresponding trace report based on the bidirectional trace list.

[0147] The document bidirectional trace apparatus provided by the embodiments of the present application has the same beneficial effects as the document bidirectional trace method provided by the above embodiments, and thus will not be described again.

[0148] The embodiments of the present application also provide a corresponding device and a computer storage medium for implementing the schemes provided by the embodiments of the present application.

[0149] The device includes a memory and a processor. The memory is configured to store instructions or codes. The processor is configured to execute the instructions or codes, so that the device performs the document bidirectional tracing method according to any one of the embodiments of the present application.

[0150] The computer storage medium stores codes. When the codes are executed, a device executing the codes implements the document bidirectional tracing method according to any one of the embodiments of the present application.

[0151] It should be noted that each of the embodiments in the present specification is described in a progressive manner, and the same or similar parts of each of the embodiments can be referred to. Each of the embodiments focuses on the differences from other embodiments. In particular, the device and equipment embodiments are described more simply because they are basically similar to the method embodiments. The relevant parts can be referred to the part of the description of the method embodiments. The device and equipment embodiments described above are only illustrative, and the units described as separate components can or can not be physically separated, and the components indicated as units can or can not be physical units, that is, they can be located in one place or distributed on multiple network units. Part or all of the modules can be selected to achieve the purpose of the embodiments according to actual needs. Those skilled in the art can understand and implement without creative labor.

[0152] The "first" and "second" in the names mentioned in the embodiments of the present application are only used for name identification, and do not represent the first and second in order.

[0153] From the above description of the embodiments, those skilled in the art can clearly understand that all or part of the steps of the above-mentioned embodiment methods can be implemented by means of software plus a general hardware platform. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product. The computer software product can be stored in a storage medium, such as a read-only memory (English: read-only memory, ROM) / RAM, a magnetic disk, an optical disk, etc., and includes a number of instructions to make a computer device (which can be a personal computer, a server, or a network communication device such as a router) execute the method described in each embodiment or some parts of the embodiments of the present application.

[0154] The above is only one specific embodiment of the present application, but the protection scope of the present application is not limited thereto. Any changes or replacements within the technical scope disclosed in the present application can be easily thought of by those skilled in the art, and should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A bidirectional document tracing method, characterized in that: The method comprises: Obtain a first task and a second task; the first task and the second task are both tasks in a target project; there is a bidirectional traceability relationship between the first task and the second task; the first task includes multiple first documents, and the second task includes multiple second documents; Obtaining a traceability identifier in each of the first documents; matching each of the traceability identifiers with a plurality of the second documents, determining at least one second document corresponding to each of the first documents, and using the relationship between each of the first documents and the corresponding at least one second document as a first traceability relationship; determining, based on each of the first documents and the at least one second document corresponding to each of the first documents, at least one first document corresponding to each of the second documents, and using the relationship between each of the second documents and the corresponding at least one first document as a second traceability relationship; generating a bidirectional tracing list based on the first tracing relationship and the second tracing relationship; Determining whether the bidirectional tracing list is consistent with a historical bidirectional tracing list; the historical bidirectional tracing list is obtained based on each first historical tracing relationship and each second historical tracing relationship, wherein the first historical tracing relationship indicates the relationship between each first historical document and the corresponding at least one second historical document, and the second historical tracing relationship indicates the relationship between each second historical document and the corresponding at least one first historical document, each first historical document is a document of the first task at a historical moment, and each second historical document is a document of the second task at the historical moment; If the two-way tracing list is consistent with the historical two-way tracing list, the historical tracing report corresponding to the historical two-way tracing list is used as the tracing report of the two-way tracing list; If the bidirectional tracing list is inconsistent with the historical bidirectional tracing list, a corresponding tracing report is determined based on the bidirectional tracing list.

2. The method according to claim 1, characterized in that Before obtaining the first and second tasks, it also includes: Acquire a target project; the target project includes multiple tasks; At least two tasks are selected from the plurality of tasks as target tasks; wherein the first task and the second task are any two adjacent tasks among the target tasks; and a traceability relationship exists between at least two adjacent tasks among the target tasks.

3. The method according to claim 2, characterized in that The multiple documents in each of the target tasks are obtained in the following manner: Determining a document type of a target document to be created, and creating a corresponding entry according to the document type; the entry includes at least one of a name, a description, or a purpose of the target document; the target document is any document in any target task in each of the target tasks; Configuring a unique identifier for the target document; Determining a traceability document that has a traceability relationship with the target document, and determining a traceability identifier based on the traceability document; The target document is created according to the entry, the unique identifier and the traceability identifier.

4. A bidirectional document tracing device, characterized in that: The device comprises: A first acquisition module is configured to acquire a first task and a second task; the first task and the second task are both tasks in a target project; there is a bidirectional traceability relationship between the first task and the second task; the first task includes a plurality of first documents, and the second task includes a plurality of second documents; A second acquisition module, configured to acquire a traceability identifier in each of the first documents; a first tracing module configured to match each of the tracing identifiers with a plurality of the second documents, determine at least one second document corresponding to each of the first documents, and use the relationship between each of the first documents and the corresponding at least one second document as a first tracing relationship; a second tracing module configured to determine, based on each of the first documents and the at least one second document corresponding to each of the first documents, at least one first document corresponding to each of the second documents, and use the relationship between each of the second documents and the corresponding at least one first document as a second tracing relationship; a bidirectional tracing module, configured to generate a bidirectional tracing list based on the first tracing relationship and the second tracing relationship; a judgment module, configured to judge whether the bidirectional tracing list is consistent with a historical bidirectional tracing list; the historical bidirectional tracing list is obtained based on each first historical tracing relationship and each second historical tracing relationship, wherein the first historical tracing relationship indicates the relationship between each first historical document and the corresponding at least one second historical document, and the second historical tracing relationship indicates the relationship between each second historical document and the corresponding at least one first historical document, wherein each first historical document is a document of the first task at a historical moment, and each second historical document is a document of the second task at the same historical moment; The report generating module is configured to use the historical tracing report corresponding to the historical bidirectional tracing list as the tracing report of the bidirectional tracing list if the bidirectional tracing list is consistent with the historical bidirectional tracing list; and to determine the corresponding tracing report based on the bidirectional tracing list if the bidirectional tracing list is inconsistent with the historical bidirectional tracing list.

5. The device according to claim 4, characterized in that Before the first acquisition module, it also includes: a screening module for: Acquire a target project; the target project includes multiple tasks; At least two tasks are selected from the plurality of tasks as target tasks; wherein the first task and the second task are any two adjacent tasks among the target tasks; and a traceability relationship exists between at least two adjacent tasks among the target tasks.

6. The device according to claim 5, characterized in that The multiple documents in each of the target tasks are obtained in the following manner: a creation unit, configured to determine a document type of a target document to be created and create a corresponding entry according to the document type; the entry includes at least one of a name, a description, or a purpose of the target document; the target document is any document in any target task in each of the target tasks; A configuration unit, configured to configure a unique identifier for the target document; a determining unit, configured to determine a traceability document having a traceability relationship with the target document, and determine a traceability identifier based on the traceability document; A document creation unit is configured to create the target document according to the entry, the unique identifier, and the traceability identifier.

7. A computer device, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the bidirectional document tracing method according to any one of claims 1 to 3 is implemented.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions, and when the instructions are executed on a terminal device, the terminal device executes the document bidirectional tracing method according to any one of claims 1 to 3.

Images