Document bidirectional tracing method and related device

By obtaining and matching the traceability identifiers in the task document and generating a two-way traceability list, the problems of low efficiency and error-prone manual two-way traceability are solved, and efficient and accurate automated two-way traceability are achieved.

CN119624475AActive Publication Date: 2025-03-14NEUSOFT REACH AUTOMOBILE TECH (SHENYANG) CO LTD

Patent Information

Application Number
CN202411687241.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-11-22
Publication Date
2025-03-14
Estimated Expiration
2044-11-22

AI Technical Summary

Technical Problem

In the prior art, manual bidirectional traceability is inefficient and prone to errors, especially when the number of tasks is large.

Method used

By obtaining tasks and documents with two-way traceability relationships, obtaining the traceability identifier in the document, and matching it with other documents, determining the two-way traceability relationship between documents, and generating a two-way traceability list.

Benefits of technology

Automatic processing is realized, improving the efficiency and accuracy of two-way traceability and reducing manual errors.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119624475A_ABST
    Figure CN119624475A_ABST
Patent Text Reader

Abstract

The invention discloses a document bidirectional tracing method and related devices.The method comprises the steps that a first task and a second task which have a bidirectional tracing relation are obtained, the first task comprises a plurality of first documents, and the second task comprises a plurality of second documents; obtaining a traceability identifier in each first document, matching each traceability 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 corresponding at least one second document as a first traceability relationship; based on each first document and 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 corresponding at least one first document as a second tracing relationship; and generating a bidirectional tracing list based on the first tracing relation and the second tracing relation. Therefore, the efficiency of bidirectional tracing is improved, and the accuracy of bidirectional tracing is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a document bidirectional tracing method and related devices. Background Art

[0002] At present, different tasks are set in software production, such as system requirements, system architecture, software requirements, software architecture, detailed design, coding, unit testing, integration testing, system testing, etc. In order to ensure the high quality and reliability of the developed software, two-way traceability is required for each task. For example, Task A is the software requirement, and Task B is the software architecture. Task B needs to be traced back to Task A in both directions, that is, Task B confirms that the development of the software requirements is completed, and Task A needs to confirm that there are no omissions in Task B's product development.

[0003] In the related art, manual two-way tracing of each task link is generally required. However, when the number of tasks is large, manual two-way tracing is inefficient and prone to errors. Summary of the invention

[0004] Based on the above problems, the present application provides a document bidirectional tracing method and related devices, aiming to solve the problem that manual bidirectional tracing is inefficient and prone to errors.

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

[0006] In a first aspect, an embodiment of the present application provides a document bidirectional tracing method, the method comprising:

[0007] Acquire a first task and a second task; the first task and the second task are both tasks in the 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;

[0008] Obtaining a traceability identifier in each first document;

[0009] Matching each traceability identifier with a 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 traceability relationship;

[0010] Based on each first document and 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] A bidirectional tracing list is generated based on the first tracing relationship and the second tracing relationship.

[0012] Optionally, before obtaining the first task and the second task, the method further includes:

[0013] Get the target project; the target project includes multiple tasks;

[0014] At least two tasks are selected from a 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 traceability relationship between two adjacent tasks in at least two target tasks.

[0015] Optionally, multiple documents in each target task are obtained by:

[0016] Determine the document type of the target document to be created, and create a corresponding entry according to the document type; 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;

[0017] Configure the unique identifier of the target document;

[0018] Determine a traceability document that has a traceability relationship with the target document, and determine a traceability identifier based on the traceability document;

[0019] Create target documents based on entries, unique identifiers and traceability identifiers.

[0020] Optionally, after generating the bidirectional tracing list based on the first tracing relationship and the second tracing relationship, the method further includes:

[0021] Determine whether the bidirectional tracing list is consistent with the historical bidirectional tracing list; 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 the relationship between each first historical document and the corresponding at least one second historical document, 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 a historical moment;

[0022] 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 will be used as the tracing report of the two-way tracing list;

[0023] If the two-way tracing list is inconsistent with the historical two-way tracing list, the corresponding tracing report is determined based on the two-way tracing list.

[0024] In a second aspect, an embodiment of the present application provides a document bidirectional tracing device, the device comprising:

[0025] A first acquisition module is used to acquire a first task and a second task; the first task and the second task are both tasks in the 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;

[0026] A second acquisition module is used to acquire the traceability identifier in each first document;

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

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

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

[0030] Optionally, before the first acquisition module, it further includes: a screening module, which is used to:

[0031] Get the target project; the target project includes multiple tasks;

[0032] At least two tasks are selected from a 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 traceability relationship between two adjacent tasks in at least two target tasks.

[0033] Optionally, multiple documents in each target task are obtained by:

[0034] A creation unit, configured to determine the 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 the name, description or purpose of the target document; the target document is any document in any target task in each target task;

[0035] A configuration unit, used to configure a unique identifier of a target document;

[0036] A determination unit, used to determine a traceability document that has a traceability relationship with a target document, and determine a traceability identifier based on the traceability document;

[0037] The document creation unit is used to create a target document according to the entry, the unique identifier and the traceability identifier.

[0038] Optionally, after the bidirectional tracing module, it also includes:

[0039] A judgment module is used to judge whether the bidirectional tracing list is consistent with the historical bidirectional tracing list; 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 the relationship between each first historical document and the corresponding at least one second historical document, 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 a historical moment;

[0040] The report generation module is used to use the historical tracing report corresponding to the historical two-way tracing list as the tracing report of the two-way tracing list if the two-way tracing list is consistent with the historical two-way tracing list; if the two-way tracing list is inconsistent with the historical two-way tracing list, determine the corresponding tracing report based on the two-way tracing list.

[0041] In a third aspect, an embodiment of the present application provides a computer device, comprising: 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 document bidirectional tracing method as described in the first aspect is implemented.

[0042] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which instructions are stored. When the instructions are executed on a terminal device, the terminal device executes the document bidirectional tracing method as described in the first aspect.

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

[0044] The document bidirectional tracing method provided by the embodiment of the present application obtains a first task and a second task having a bidirectional tracing relationship, wherein the first task and the second task are both tasks in a target project, the first task includes multiple first documents, and the second task includes multiple second documents; then obtains a tracing identifier in each first document, matches each tracing identifier with the multiple second documents, determines at least one second document corresponding to each first document, and uses the relationship between each first document and the corresponding at least one second document as a first tracing relationship; based on each first document and the at least one second document corresponding to each first document, determines at least one first document corresponding to each second document, and uses the relationship between each second document and the corresponding at least one first document as a second tracing relationship; and then generates a bidirectional tracing list based on the first tracing relationship and the second tracing relationship.

[0045] In this way, through the traceability identification of the first document, at least one second document corresponding to the first document is determined according to the traceability identification, and the first traceability relationship is determined to achieve document tracing from the first task to the second task. Further, at least one first document corresponding to the second document can be reversely traced according to the first traceability relationship to determine the second traceability relationship to achieve document tracing from the second task to the first task. Then, a two-way traceability list is determined through the first traceability relationship and the second traceability relationship to achieve two-way traceability between the first task and the second task. Different from the manual processing in the prior art, this solution can achieve automated processing, improve the efficiency of two-way tracing, and improve the accuracy of two-way tracing. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

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

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

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

[0050] Figure 3 A schematic diagram of the structure of a document bidirectional tracing device provided in 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, two-way traceability is required for each task. For example, Task A is the software requirement, and Task B is the software architecture. Task B needs to be traced two-way with Task A, that is, Task B confirms that the development of the software requirements is completed, and Task A needs to confirm that there is no omission in Task B regarding the software architecture.

[0052] In the related art, manual two-way tracing is generally required for each task link. However, when the number of tasks is large, for example, a task includes 10 documents, and each document may have hundreds or even thousands of pages (such as detailed design), then manual two-way tracing is required for these 10 documents one by one, resulting in low efficiency and error-prone manual two-way tracing.

[0053] In order to solve the above problems, the embodiment of the present application provides a document bidirectional tracing method and related devices. The method includes: obtaining a first task and a second task that have a bidirectional tracing relationship, wherein the first task and the second task are both tasks in the target project, the first task includes multiple first documents, and the second task includes multiple second documents; then obtaining the tracing identifiers in each first document, matching each tracing identifier with multiple 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 the 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 corresponding at least one first document as the second tracing relationship; and then generating a bidirectional tracing list based on the first tracing relationship and the second tracing relationship.

[0054] In this way, through the traceability identification of the first document, at least one second document corresponding to the first document is determined according to the traceability identification, and the first traceability relationship is determined to achieve document tracing from the first task to the second task. Further, at least one first document corresponding to the second document can be reversely traced according to the first traceability relationship to determine the second traceability relationship to achieve document tracing from the second task to the first task. Then, a two-way traceability list is determined through the first traceability relationship and the second traceability relationship to achieve two-way traceability between the first task and the second task. Different from the manual processing in the prior art, this solution can achieve automated processing, improve the efficiency of two-way tracing, and improve the accuracy of two-way tracing.

[0055] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0056] See also Figure 1 , which is a flow chart of a document bidirectional tracing method provided in an embodiment of the present application.

[0057] Combination Figure 1 As shown, the bidirectional document tracing method provided in the embodiment of the present application may include:

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

[0059] It should be understood that in the embodiment 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 may include multiple tasks, and there is a traceability relationship between two adjacent tasks in the multiple tasks. As an example, assuming that the target project includes 4 tasks, namely task A, task B, task C and task D, then there may be a two-way traceability relationship between task A and task B, a two-way traceability relationship between task B and task C, and a two-way traceability relationship between task C and task D.

[0060] In the embodiment of the present application, the first task and the second task are both tasks in the 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. It should be understood that in the embodiment of the present application, each task may include one or more documents, and the document types of multiple documents under a task may be the same or different, and again there is no specific limitation. As an example, assuming that the first task includes 4 documents, namely document A, document B, document C, and document D, document A and document B may be documents of the same type, and document C and document D may be documents of different types.

[0061] A bidirectional traceability relationship means that the documents corresponding to two tasks can be confirmed and viewed in both directions. For example, task A includes three documents a, b, and c, and task B includes two documents d and e. When task B traces back to task A, document d corresponds to document a, and document e corresponds to documents b and c; when task A traces back to 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 executing S101, the following steps may also be included:

[0063] A1: Get the target item.

[0064] The target project includes multiple tasks. It should be understood that in the embodiment of the present application, two-way tracing is performed between multiple tasks in the same project, so all tasks in the target project need to be obtained.

[0065] A2: Select at least two tasks from multiple 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 traceability relationship between two adjacent tasks in at least two target tasks.

[0067] It should be understood that in the embodiments 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 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 according to their importance, a weight threshold may be set, and tasks whose weight in the target project is greater than the weight threshold may be taken 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 creation. Document types may include requirement documents, design documents, test documents, user manuals, installation guides, etc. Different documents have their 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 by determining the document type and creating corresponding entries, it is helpful to improve the standardization of document management and ensure 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 means assigning a unique identifier (such as document number, version number, etc.) to each target document to ensure that the document can be uniquely identified in the target project. In one possible implementation, a project management tool or document management system can be used to automatically assign and track these unique identifiers. This avoids confusion and misuse between documents and improves the accuracy of document management.

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

[0078] It should be understood that in software architecture, a document may have a dependency or reference relationship with other documents. For example, a design document may reference certain requirements in a requirement document. This type of dependency or application relationship is called a traceability relationship. In order to be able to quickly find the relationship between them when needed, it is necessary to assign traceability identifiers to these related documents. Improving the traceability between documents helps to quickly locate the cause when a problem occurs. At the same time, it promotes collaborative work between documents and ensures the consistency and integrity of the target project.

[0079] B4: Create target documents based on entries, unique identifiers and traceability identifiers.

[0080] In the project management tool or document management system, according to the entries, unique identifiers and traceability identifiers created in the previous steps, the target document can then be formally created. The document content is filled in according to the requirements of the document type to ensure that the structure of the document is clear and easy to understand.

[0081] S102: Acquire the traceability identifier in each first document.

[0082] The traceability identifier refers to an identifier used to indicate a dependency or reference relationship (ie, a traceability relationship) between documents. By acquiring the traceability identifier of a first document, the corresponding second document can be determined according to the traceability relationship indicated by the traceability identifier.

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

[0084] It should be understood that by matching the traceability identifier with multiple documents corresponding to the second task, the corresponding second document can be determined. If the corresponding second document does not exist, a matching failure message can be output to indicate that the first document traceability failed, indicating that there is a redundant first document in the first task.

[0085] S104: Based on each first document and at least one second document corresponding to each first document, determine at least one first document corresponding to each second document, and use the relationship between each second document and the corresponding at least one first document as a second tracing relationship.

[0086] It should be understood that after determining each first tracing relationship, it is also possible to trace back the first document in the first task from the second document of the second task based on the first tracing relationship (i.e., each first document and at least one second document corresponding to each first document). That is, after the first task is traced back to the second task, there is a first tracing relationship from the first task to the second task. Furthermore, combined with the known first tracing relationship, the second tracing relationship from the second task to the first task can be further traced back to achieve 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 matching failure information may be output to indicate that the second document tracing fails.

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

[0089] It should be understood that after determining the first tracing relationship and the second tracing relationship, a bidirectional tracing list can be generated to achieve bidirectional tracing between the first task and the second task. In some possible implementations, the matching failure information output in the first tracing relationship determination process (referred to as the first failure information) and the matching failure information output in the second tracing relationship determination process (referred to as the second failure information) can also be synchronously integrated in the bidirectional tracing list to facilitate subsequent analysis by R&D personnel.

[0090] In an embodiment of the present application, through the traceability identification of the first document, at least one second document corresponding to the first document is determined according to the traceability identification, and a first traceability relationship is determined to achieve document tracing from the first task to the second task. Further, at least one first document corresponding to the second document can be reversely traced according to the first traceability relationship to determine the second traceability relationship to achieve document tracing from the second task to the first task. Then, a two-way traceability list is determined through the first traceability relationship and the second traceability relationship to achieve two-way traceability between the first task and the second task. Different from the manual processing in the prior art, this solution can achieve automated processing, improve the efficiency of two-way tracing, and improve the accuracy of two-way tracing.

[0091] Based on the document bidirectional tracing method provided in the above embodiment, in a possible implementation, after step S105, the method may further include: determining whether the bidirectional tracing list is consistent with the historical bidirectional tracing list.

[0092] Among them, 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 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 a historical moment.

[0093] It should be understood that in the embodiment of the present application, there may be a historical two-way tracing list for two-way tracing at the previous moment (that is, the historical moment). In order to avoid repeated analysis, the two-way tracing list at the current moment can be compared with the historical two-way list 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, and there is no need to calculate again; if the two-way tracing list is inconsistent with the historical two-way tracing list, the corresponding tracing report is determined based on the two-way tracing list.

[0094] In the embodiment of the present application, whether to use the historical tracing report or calculate the tracing report based on the two-way tracing list is determined by checking whether the two-way tracing list is consistent with the historical two-way tracing list, thereby avoiding repeated calculations and improving the efficiency of two-way tracing.

[0095] Based on the document bidirectional tracing method provided in the above embodiment, see Figure 2a , which is a schematic diagram of another document bidirectional tracing method provided by an embodiment of the present application, combined with Figure 2a As shown, the bidirectional document tracing method provided in the embodiment of the present application may include:

[0096] Step 1: Create a project.

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

[0098] Step 2: Tailor the tasks according to the project situation to obtain the target project.

[0099] Task tailoring according to the project situation means deleting or retaining tasks in the project based on the need for two-way traceability between tasks in the project. If there is no need for two-way traceability between Task A and Task B, Task A and Task B can be deleted. If there is a need for two-way traceability 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 the target project will include multiple tasks, each of which has different levels of importance and there is a need for two-way traceability between some tasks. Therefore, it is necessary to formulate the tasks that need to be performed during the target project, delete the tasks that do not require two-way traceability, and improve the efficiency of two-way traceability.

[0101] Step 3: Develop document templates and traceability relationships for the corresponding processes.

[0102] It should be noted that the configuration process of the document template and traceability relationship in the embodiment of the present application refers to the relevant explanations of the above embodiment and will not be repeated here.

[0103] Step 4: After the document template is developed, configure the target project.

[0104] For example, configure the document information for bidirectional traceability of 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 deleted lines does not participate in traceability, data with field Status as Invalid does not participate in traceability Status, Invalid is a configuration item), delimiter information for multiple IDs during one-to-many traceability, configure the template for generating reports and the location of the generated report results in the template, the file name format for generating reports, whether the case is sensitive during traceability, and the start and end identification information of the content to be traced in each document. Example configurations are as follows:

[0105]

[0106]

[0107]

[0108] Step 5: Send the tool or configuration containing the target project configuration to the user with the bidirectional traceability task.

[0109] It should be understood that after the target project configuration is completed, the tool or configuration containing such configuration can be distributed to the user who needs to perform two-way traceability to achieve two-way traceability.

[0110] Step 6: The user confirms the location of the materials that need to be traced based on the target project configuration. When writing the document for the current task, the user can use tools to perform two-way traceability on the document and the upstream document to ensure that there are no omissions in the design execution.

[0111] It should be understood that the user can write the document according to the target project configuration. For example, if the target project configuration presets the document number, the user can select the number corresponding to the current document according to the target project configuration to facilitate subsequent tracing.

[0112] Step 7: Mission accomplished.

[0113] It should be understood that when the task is completed, the bidirectional tracing results can be presented in the form of the following Table 1:

[0114] Table 1: Bidirectional traceability results

[0115] Document ID 1 for Task 1 Document ID 2 for Task 2 Bidirectional traceability results 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] Among them, task 1 represents the first task, the document ID of task 1 represents the traceability identification corresponding to each first document in task 1, task 2 represents the second task, the document ID of task 2 represents the identification of each second document in task 2, the relationship from ID1 to ID2 is the first traceability relationship, the traceability relationship from ID2 to ID1 is the second traceability relationship, OK indicates that the bidirectional traceability result is correct, and NG indicates that the bidirectional traceability result is incorrect.

[0117] Based on the document bidirectional tracing method provided in the above embodiment, see Figure 2b , users can perform two-way tracing in the following ways:

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

[0119] After the target project configuration in step 4 is completed, the target project configuration may be sent to the user, and the user may load the target project configuration.

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

[0121] For example, the location of the document to be traced, the traceback to be performed, the module name, the report output directory, and so on.

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

[0123] If the first document or the second document has been parsed and has no change, the parsing is not repeated. The two-dimensional table is used to indicate the 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 two-way traceability report using the data in the two-dimensional table.

[0125] The two-dimensional table includes a first tracing relationship and a second tracing relationship. Based on the first tracing relationship and the second tracing relationship, a two-way tracing list (ie, a two-way tracing report) can be generated, as shown in 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 proofreading may be further performed based on the bidirectional traceability report, and the first document or the second document may be revised based on the proofreading result.

[0128] Step 6: End the process or re-execute step 2.

[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 terminated; if the bidirectional traceability report indicates that there is an error in the bidirectional traceability relationship (the first traceability relationship and / or the second traceability relationship) between the first document and the second document, 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 tracing method provided in the above embodiment, the present application embodiment also provides a document bidirectional tracing device, see Figure 3 , which is a schematic diagram of the structure of the document bidirectional tracing device provided in the embodiment of the present application, combined with Figure 3 As shown, the document bidirectional tracing device 300 provided in the embodiment of the present application may include:

[0131] The first acquisition module 301 is used to acquire a first task and a second task; the first task and the second task are both tasks in the 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;

[0132] The second acquisition module 302 is used to acquire the traceability identification in each first document;

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

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

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

[0136] In a possible implementation, before the first acquisition module 301, it further includes: a screening module, which is used to:

[0137] Get the target project; the target project includes multiple tasks;

[0138] At least two tasks are selected from a 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 traceability relationship between two adjacent tasks in at least two target tasks.

[0139] In a possible implementation, multiple documents in each target task are obtained in the following manner:

[0140] A creation unit, configured to determine the 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 the name, description or purpose of the target document; the target document is any document in any target task in each target task;

[0141] A configuration unit, used to configure a unique identifier of a target document;

[0142] A determination unit, used to determine a traceability document that has a traceability relationship with a target document, and determine a traceability identifier based on the traceability document;

[0143] The document creation unit is used to create a target document according to the entry, the unique identifier and the traceability identifier.

[0144] In a possible implementation, after the bidirectional tracing module 305, the following is further included:

[0145] A judgment module is used to judge whether the bidirectional tracing list is consistent with the historical bidirectional tracing list; 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 the relationship between each first historical document and the corresponding at least one second historical document, 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 a historical moment;

[0146] The report generation module is used to use the historical tracing report corresponding to the historical two-way tracing list as the tracing report of the two-way tracing list if the two-way tracing list is consistent with the historical two-way tracing list; if the two-way tracing list is inconsistent with the historical two-way tracing list, determine the corresponding tracing report based on the two-way tracing list.

[0147] The document bidirectional tracing device provided in the embodiment of the present application has the same beneficial effects as the document bidirectional tracing method provided in the above embodiment, so it will not be described in detail.

[0148] The embodiments of the present application also provide corresponding devices and computer storage media for implementing the solutions provided by the embodiments of the present application.

[0149] The device includes a memory and a processor, the memory is used to store instructions or codes, and the processor is used to execute the instructions or codes so that the device executes the document bidirectional tracing method described in any embodiment of the present application.

[0150] The computer storage medium stores codes, and when the codes are executed, the device executing the codes implements the bidirectional document tracing method described in any embodiment of the present application.

[0151] It should be noted that each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and equipment embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments. The device and equipment embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components indicated as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. A person of ordinary skill in the art can understand and implement it without paying creative labor.

[0152] The "first" and "second" in the names such as "first" and "second" (if any) mentioned in the embodiments of the present application are only used as name identifiers and do not represent the first or second in order.

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

[0154] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A bidirectional document tracing method, characterized in that: The method comprises: 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; 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 taking the relationship between each of the first documents and the corresponding at least one second document as a first traceability relationship; Based on each of the first documents and at least one second document corresponding to each of the first documents, determining at least one first document corresponding to each of the second documents, and taking the relationship between each of the second documents and the corresponding at least one first document as a second tracing relationship; A bidirectional tracing list is generated based on the first tracing relationship and the second tracing relationship.

2. The method according to claim 1, characterized in that Before obtaining the first task and the second task, it also includes: Acquire a target project; the target project includes multiple tasks; At least two tasks are selected from the multiple tasks as target tasks; wherein the first task and the second task are any two adjacent tasks among the target tasks; and there is a traceability relationship 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: Determine the document type of the target document to be created, and create a corresponding entry according to the document type; 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 of the target tasks; Configure the unique identifier of 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. The method according to claim 1, characterized in that After generating a bidirectional tracing list based on the first tracing relationship and the second tracing relationship, the method further includes: Determine whether the bidirectional tracing list is consistent with the historical bidirectional tracing list; 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 the relationship between each first historical document and the corresponding at least one second historical document, 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.

5. A bidirectional document tracing device, characterized in that: The device comprises: A first acquisition module is used 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, used to acquire the 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; The bidirectional tracing module is used to generate a bidirectional tracing list based on the first tracing relationship and the second tracing relationship.

6. The method according to claim 5, characterized in that Before the first acquisition module, it also includes: a screening module, which is used to: Acquire a target project; the target project includes multiple tasks; At least two tasks are selected from the multiple tasks as target tasks; wherein the first task and the second task are any two adjacent tasks among the target tasks; and there is a traceability relationship between at least two adjacent tasks among the target tasks.

7. The method according to claim 6, characterized in that The multiple documents in each of the target tasks are obtained in the following manner: A creation unit, configured to determine the 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 the name, description or purpose of the target document; the target document is any document in any target task in each of the target tasks; A configuration unit, used to configure the unique identifier of 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 used to create the target document according to the entry, the unique identifier and the traceability identifier.

8. The method according to claim 5, characterized in that After the bidirectional traceability module, it also includes: a judgment module, used to judge whether the bidirectional tracing list is consistent with the historical bidirectional tracing list; 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 the relationship between each first historical document and the corresponding at least one second historical document, 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; The report generating module is used for, if the bidirectional tracing list is consistent with the historical bidirectional tracing list, using 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 inconsistent with the historical bidirectional tracing list, determining the corresponding tracing report based on the bidirectional tracing list.

9. 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 document bidirectional tracing method according to any one of claims 1 to 4 is implemented.

10. 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 4.

Citation Information

Patent Citations

  • Tracing method and tracing system

    CN112214555A

  • Demand information source tracing method and device, computer equipment and storage medium

    CN114063983A

  • Project management method and device, equipment and storage medium

    CN114331110A

  • Document state management system, document state management method and program

    JP2019071055A

  • Method and System for Bi-Directionally Synchronizing Tracing Relationships Between A Requirements Repository and Textual Requirements Documents

    US20080301156A1

Cited By

  • Material file management method and device, computer equipment and storage medium

    CN121070877A

  • Material file management method and device, computer device and storage medium

    CN121070877B