Automobile electronic and electrical architecture document publishing method and device and computer program product

By automatically triggering concurrent correlation coverage checks in the development of automotive electronic and electrical architectures, the problem of low inspection efficiency is solved, rapid release and efficient data verification are achieved, and user experience and system efficiency are improved.

CN119045974APending Publication Date: 2024-11-29GUANGZHOU AUTOMOBILE GROUP CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411198281.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-28
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

During the development of automotive electronic and electrical architectures, it is difficult for the existing technology to complete the correlation coverage check in a short time, resulting in users needing to wait for real-time inspection results or wait for timing tasks to run, affecting release efficiency and real-timeness.

Method used

When the user initiates the review and release process of the document to be published, the association coverage check task will be automatically triggered, including document entry association check and upstream demand management coverage check, and the release process will be continued after the inspection is passed, providing concurrent checks and background tasks to run Shorten the waiting time.

Benefits of technology

Concurrent audit and correlation coverage checks are carried out shorten user waiting time, improve work efficiency, ensure data accuracy and completeness, and allow users to understand the inspection situation in real time, improving the flexibility and convenience of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119045974A_ABST
    Figure CN119045974A_ABST
Patent Text Reader

Abstract

The invention discloses an automobile electronic and electrical architecture document publishing method and device and a computer program product, and the method comprises the steps: automatically triggering and operating an associated coverage inspection task when a user initiates an auditing and publishing process of a to-be-published document, and meanwhile, pausing the to-be-published document to jump to the auditing and publishing process; the association coverage inspection task comprises document entry association inspection and upstream demand management coverage inspection; judging whether the check is passed or not according to the document entry association check result and the upstream demand management coverage check result; and if the check is passed, continuing the auditing and publishing process of the to-be-published document. According to the invention, through concurrence of auditing and associated coverage checking, the waiting time of the user is effectively shortened, and the working efficiency is improved; and the data release is limited by checking the state attribute, so that the data can be released only after the data verification is passed, the time for manually confirming the data checking state is shortened, and the working efficiency is further improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of automotive electronics technology, and in particular to a method, device and computer program product for publishing automotive electronic and electrical architecture documents. Background Art

[0002] At present, in the process of developing automotive electronic and electrical architecture, it is necessary to verify the item association coverage when publishing. In addition to these information checks stored in the data object itself, some information does not exist on the data object itself, and it is necessary to find the associated data for verification. With the increasing number of development processes, requirements and associated data, and the increasing amount of data, it is difficult to control the time taken to run some checks in a short time. At this time, users either wait for real-time check results when publishing, or the system runs the check task regularly; in the former, users need to wait for the check results in the publishing interface every time, which takes a long time and cannot be conducted concurrently with other audits. In addition, for the web version, if the web page is accidentally closed, the real-time check needs to be re-run; in the latter, the real-time performance is poor, and all data can only be released after the scheduled task is run before the next step can be carried out. When the problem is modified and released again, it is necessary to wait for the next scheduled check, and the publishing cycle is extended. Summary of the invention

[0003] The technical problem to be solved by the embodiments of the present invention is to provide a method, device and computer program product for publishing automotive electronic and electrical architecture documents to improve inspection efficiency and real-time performance.

[0004] In order to solve the above technical problems, the present invention provides a method for publishing an automotive electronic and electrical architecture document, comprising the following steps:

[0005] When a user initiates the review and release process of a document to be released, the associated coverage check task is automatically triggered, and the document to be released is paused and jumped to the review and release process; the associated coverage check task includes document item association check and upstream demand management coverage check;

[0006] Determine whether the check has passed based on the document item association check results and upstream requirements management coverage check results;

[0007] If the check passes, the review and release process of the document to be released will continue.

[0008] Preferably, when automatically triggering the execution of the associated coverage check task, it also includes automatically creating a new task check work item to record the associated coverage check task.

[0009] Preferably, the upstream demand management coverage check specifically includes:

[0010] The document entry association check specifically includes:

[0011] If all valid requirements in the document to be released are associated with upstream input requirements, the Document Item Association Check Status field on the Task Check work item is set to Passed;

[0012] If there are valid requirements in the document to be released that are not associated with the upstream input requirements, the document item association check status field on the task check work item will be set to failed, and the unassociated requirement ID will be stored in the task check work item.

[0013] Preferably, the upstream demand management coverage check specifically includes:

[0014] If all upstream requirements are associated with valid requirements in the document to be released, set the Upstream Requirements Management Coverage field on the Task Check work item to Pass;

[0015] If there are upstream requirements that are not associated with valid requirements in the document to be released, the upstream requirement management coverage field on the task inspection work item will be set to failed, and the requirement ID of the unassociated upstream requirement will be stored in the task inspection work item.

[0016] Preferably, judging whether the check is passed based on the document item association check result and the upstream demand management coverage check result specifically includes:

[0017] If the document item association check result and the upstream requirement management coverage check result are all failed or one of them is failed, the data review field of the task check work item is set to failed check;

[0018] If there is no failure in the inspection result, the data review field of the task inspection work item is set to passed.

[0019] Preferably, if the inspection fails, a link is provided in the inspection result attribute, and in response to a user's click, the link jumps to a specific inspection question item.

[0020] Preferably, the task inspection work item specifically includes: basic task information, document association information, inspection points and rules, inspection results and related party information.

[0021] The present invention also provides a device for publishing automotive electronic and electrical architecture documents, comprising:

[0022] The trigger module is used to automatically trigger the associated coverage check task when the user initiates the review and release process of the document to be released, and at the same time suspend the document to be released and jump to the review and release process;

[0023] A checking module, used to execute the association coverage checking task, wherein the association coverage checking task includes document item association checking and upstream requirement management coverage checking;

[0024] The judgment module is used to judge whether the inspection is passed according to the document item association inspection results and the upstream demand management coverage inspection results;

[0025] The control module is used to control the document to be released to continue to execute the review and release process after the judgment module determines that the associated coverage check has passed.

[0026] The present invention also provides a device for publishing automotive electronic and electrical architecture documents, comprising:

[0027] one or more processors;

[0028] Memory;

[0029] One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, and the one or more applications are configured to execute the automotive electronic and electrical architecture document publishing method.

[0030] The present invention also provides a computer program product, comprising computer instructions, wherein the computer instructions instruct a computer device to execute operations corresponding to the method.

[0031] The implementation of the present invention has the following beneficial effects: the present invention effectively shortens the user's waiting time and improves work efficiency by performing audit and associated coverage check concurrently; limits data release by checking the verification of status attributes to ensure that data can be released only after the verification is passed, which not only ensures the accuracy and completeness of the data, but also shortens the time for manual confirmation of the data verification status, further improving work efficiency; further, the concurrent execution of associated coverage check and content audit allows users to understand the status of the associated coverage check in real time while waiting for the audit results, thereby greatly improving the user experience; in addition, the associated coverage check runs as a background task at the time of release, and there is no need to re-check the data even if the user closes the page, which saves the user's time and improves the convenience of the system; finally, real-time associated coverage check is performed on demand for data release, so that the system can respond to user needs more flexibly and efficiently, further improving the operating efficiency of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the embodiments of the present invention 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 invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0033] Figure 1 It is a flowchart of a method for publishing an automotive electronic and electrical architecture document according to a first embodiment of the present invention.

[0034] Figure 2 It is a specific flow chart of a method for publishing an automotive electronic and electrical architecture document according to a first embodiment of the present invention. DETAILED DESCRIPTION

[0035] The following descriptions of the embodiments refer to the accompanying drawings to illustrate specific embodiments in which the present invention may be implemented.

[0036] Please refer to Figure 1 As shown, a first embodiment of the present invention provides a method for publishing an automotive electronic and electrical architecture document, comprising the following steps:

[0037] When a user initiates the review and release process of a document to be released, the associated coverage check task is automatically triggered, and the document to be released is paused and jumped to the review and release process; the associated coverage check task includes document item association check and upstream demand management coverage check;

[0038] Determine whether the check has passed based on the document item association check results and upstream requirements management coverage check results;

[0039] If the check passes, the review and release process of the document to be released will continue.

[0040] It can be seen from the above steps that the document in the embodiment of the present invention performs association coverage checks concurrently on demand during review, rather than waiting for the check to pass before reviewing, which shortens the user's waiting time and improves the system's operating efficiency; moreover, the association coverage check runs in the background, and the user does not need to re-check the data when closing the page.

[0041] Specifically, please combine Figure 2 As shown, the specific process of the embodiment of the present invention is as follows:

[0042] Step S1, the user completes editing of the document to be published, changes the document status, and initiates the document review process. At this time, the associated coverage check task is automatically triggered, and a new task check work item is created.

[0043] The association coverage check task can ensure the integrity and consistency of the document content. The association coverage check task mainly includes two checks: document item association check and upstream requirement management coverage check. The main purpose of the document item association check is to verify whether the valid requirements in the document to be released have been correctly associated with the corresponding upstream input requirements to ensure the accuracy and traceability of the document content. The main purpose of the upstream requirement management coverage check is to verify whether all upstream input requirements have been associated with the valid requirements in the document to be released to ensure that the upstream requirements are fully responded to and utilized.

[0044] By performing related coverage check tasks concurrently during the review, we can ensure that the data is verified before it can be released.

[0045] In step S1, creating a new task check work item specifically means that when the user completes the editing of the document to be published and changes the document status to initiate the document review and release process, a new task check work item will be automatically created to record and manage subsequent related coverage check tasks. In this embodiment, the task check work item generally includes the following information:

[0046] Basic task information: such as task name, task type (associated coverage check), task status (usually "pending check" or "not started" when newly created), task creation time, etc.

[0047] Document association information: records the association between the task inspection work item and the document to be released, including the document name, document number, document version, etc., so that the specific document content can be traced back later.

[0048] Check points and rules: Preset rules and templates to guide the execution of associated coverage check tasks. Task check work items can contain references or links to these rules.

[0049] Check result recording: As the associated coverage check task proceeds, the task check work item will be used to record the check results, including the results of the document item associated check and the results of the upstream requirements management coverage check.

[0050] Stakeholder information: Task inspection work items can also include information about all parties related to the task, such as the task leader, participants, reviewers, etc., in order to clarify their respective responsibilities and collaboration methods.

[0051] By creating a new task check work item, a structured framework can be provided to manage and track the execution process of the associated coverage check tasks, ensuring that the documents to be released are fully reviewed and verified before they are officially released. It is understandable that the content and format of the above task check work items are only examples and may vary depending on different systems or platforms.

[0052] Step S2, when the associated coverage check task is running, the data review field of the task check work item is "Inspecting", which is used to inform all relevant parties of the status of the current task, indicating that the task is in the process of inspection. During the running of the inspection task, although the ability of the document to be released to jump to the next step of the review and release process is suspended, the relevant parties (such as document editors, reviewers, etc.) can still access and view the document content and confirm it item by item, that is, the relevant parties can review the document during the inspection process to ensure its accuracy and completeness. However, before the associated coverage check task is completed, the document to be released is not allowed to jump to the next step of the review and release process. This constraint ensures that all associated coverage checks have been completed and passed before the document is further reviewed and released, which helps to ensure the accuracy and consistency of the document and prevent documents that have not been fully checked from being mistakenly released or further processed.

[0053] In addition, the current running status of the associated coverage check task is queried in real time or periodically, and based on the query results, the specific value of the associated coverage check task status attribute is determined (indicating whether the task is running, whether it has been completed, whether an error has occurred, etc.) to prompt the user to check whether the task is completed.

[0054] In step S3, the association coverage check task needs to first find all upstream input requirements related to the document to be released in the ALM (Application Lifecycle Management) system. There are two search rules for upstream input requirements: (1) the upstream input requirements come from a specific type of document in the same space; (2) the upstream input requirements come from the value of a specific field in the space where the document to be released is located. The association coverage check task runs the check logic according to the type of document to be released, that is, presets or allows users to configure the source method of upstream requirements.

[0055] As mentioned above, the association coverage check task includes document item association check and upstream demand management coverage check. In step S4, the document item association check is first performed, that is, all valid requirements in the document to be published are traversed to determine whether each valid requirement is associated with the above upstream input requirement. Specifically, it includes:

[0056] Step S41, if all valid requirements in the document to be released are associated with upstream input requirements, the document item association check status field on the task check work item is set to passed;

[0057] Step S42: If there are valid requirements in the document to be published that are not associated with the upstream input requirements, the document item association check status field on the task check work item is set to fail, and the unassociated requirement ID is stored in the task check work item for subsequent viewing and modification by the user.

[0058] In step S5, the upstream requirement management coverage check in the association coverage check task is continued to determine whether all upstream input requirements are associated with the valid requirements in the document to be published. Specifically, it includes:

[0059] Step S51, if all upstream requirements are associated with valid requirements in the document to be released, then the upstream requirement management coverage field on the task check work item is set to passed;

[0060] Step S52: If there is an upstream requirement that is not associated with a valid requirement in the document to be published, the upstream requirement management coverage field on the task inspection work item is set to fail, and the requirement ID of the unassociated upstream requirement is stored in the task inspection work item.

[0061] When the associated coverage check task is completed, step S6 determines whether the check is passed based on the document item associated check result and the upstream demand management coverage check result, thereby determining the data review field result of the task check work item. Specifically, it includes:

[0062] Step S61, if all or one of the inspection results fails, the data review field of the task inspection work item is set to fail inspection;

[0063] Step S62: If there is no failure in the inspection result, the data review field of the task inspection work item is set to passed.

[0064] After the associated coverage check task is completed, if the data review field of the task check work item is not passed, the check result is processed through step S7, and the specific operation of providing feedback to the user is carried out. Specifically, it includes:

[0065] In the task check work item, clearly list the valid requirement IDs that have not been successfully associated with the upstream input requirements. These IDs represent the requirements in the to-be-released document that have not yet found the corresponding upstream source or basis. At the same time, the requirement IDs of the upstream input requirements that are not associated with any valid requirements in the to-be-released document are also listed. These IDs represent upstream input requirements that are not explicitly responded to or covered in the to-be-released document.

[0066] By displaying these unassociated and unassociated requirement IDs on the task inspection work items, users can clearly understand the specific problem items in the documents to be released, which helps users quickly locate and solve these problems to ensure the accuracy and completeness of the documents.

[0067] In addition, an embodiment of the present invention also provides a link to jump to view inspection problem items, that is, a link is provided in the data inspection result attributes, and users can directly jump to view specific inspection problem items by clicking on these links, which greatly facilitates users to perform subsequent data modification and review work, and lays the foundation for subsequent review and release processes.

[0068] If the data review field of the task inspection work item is checked as passed, then the document is allowed to proceed to the subsequent review and release process through step S8, that is, the review and release process of the previously suspended document to be released is continued.

[0069] Corresponding to the method for publishing an automotive electronic and electrical architecture document described in the first embodiment of the present invention, the second embodiment of the present invention further provides an apparatus for publishing an automotive electronic and electrical architecture document, including:

[0070] The trigger module is used to automatically trigger the associated coverage check task when the user initiates the review and release process of the document to be released, and at the same time suspend the document to be released and jump to the review and release process;

[0071] A checking module, used to execute the association coverage checking task, wherein the association coverage checking task includes document item association checking and upstream requirement management coverage checking;

[0072] The judgment module is used to judge whether the inspection is passed according to the document item association inspection results and the upstream demand management coverage inspection results;

[0073] The control module is used to control the document to be released to continue to execute the review and release process after the judgment module determines that the associated coverage check has passed.

[0074] Corresponding to the method for publishing an automotive electronic and electrical architecture document described in the first embodiment of the present invention, the third embodiment of the present invention further provides an apparatus for publishing an automotive electronic and electrical architecture document, including:

[0075] one or more processors;

[0076] Memory;

[0077] One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, and the one or more applications are configured to execute the automotive electronic and electrical architecture document publishing method described in the aforementioned embodiment 1 of the present invention.

[0078] Corresponding to the method for publishing automotive electronic and electrical architecture documents described in the aforementioned embodiment 1 of the present invention, embodiment 4 of the present invention also provides a computer program product, including computer instructions, and the computer instructions instruct a computer device to perform operations corresponding to the method for publishing automotive electronic and electrical architecture documents described in the aforementioned embodiment 1 of the present invention.

[0079] Preferably, the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor. The processor is the control center of the device, and various parts of the device are connected using various interfaces and lines.

[0080] The memory mainly includes a program storage area and a data storage area, wherein the program storage area can store an operating system, an application required for at least one function, etc., and the data storage area can store related data, etc. In addition, the memory can be a high-speed random access memory, or a non-volatile memory, such as a plug-in hard disk, a smart memory card (SmartMedia Card, SMC), a secure digital (Secure Digital, SD) card, and a flash card (Flash Card), etc., or the memory can also be other volatile solid-state storage devices.

[0081] It should be noted that the above-mentioned device may include but is not limited to a processor and a memory, which can be understood by those skilled in the art.

[0082] For the working principle and process of the above embodiment, please refer to the description of the above embodiment of the present invention, which will not be repeated here.

[0083] From the above description, it can be seen that compared with the prior art, the beneficial effects of the present invention are: the present invention effectively shortens the user's waiting time and improves work efficiency by performing audit and associated coverage check concurrently; restricts data release by checking the verification of status attributes to ensure that data can be released only after the verification is passed, which not only ensures the accuracy and completeness of the data, but also shortens the time for manual confirmation of the data verification status, further improving work efficiency; further, the concurrent execution of associated coverage check and content audit allows users to understand the status of associated coverage check in real time while waiting for the audit results, thereby greatly improving the user experience; in addition, the associated coverage check runs as a background task at the time of release, and there is no need to re-check the data even if the user closes the page, which saves the user's time and improves the convenience of the system; finally, real-time associated coverage check is performed on demand for data release, so that the system can respond to user needs more flexibly and efficiently, further improving the operating efficiency of the system.

[0084] The above disclosure is only the preferred embodiment of the present invention, which certainly cannot be used to limit the scope of the present invention. Therefore, equivalent changes made according to the claims of the present invention are still within the scope of the present invention.

Claims

1. A method for publishing automotive electronic and electrical architecture documents, characterized in that: The following steps are involved: When a user initiates the review and release process of a document to be released, the associated coverage check task is automatically triggered, and the document to be released is paused and jumped to the review and release process; The association coverage check task includes document item association check and upstream demand management coverage check; Determine whether the check has passed based on the document item association check results and upstream requirements management coverage check results; If the check passes, the review and release process of the document to be released will continue.

2. The method according to claim 1, characterized in that When the associated coverage check task is automatically triggered to run, it also includes automatically creating a new task check work item to record the associated coverage check task.

3. The method according to claim 2, characterized in that The upstream demand management coverage check specifically includes: The document entry association check specifically includes: If all valid requirements in the document to be released are associated with upstream input requirements, the Document Item Association Check Status field on the Task Check work item is set to Passed; If there are valid requirements in the document to be released that are not associated with the upstream input requirements, the document item association check status field on the task check work item will be set to failed, and the unassociated requirement ID will be stored in the task check work item.

4. The method according to claim 3, characterized in that The upstream demand management coverage check specifically includes: If all upstream requirements are associated with valid requirements in the document to be released, set the Upstream Requirements Management Coverage field on the Task Check work item to Pass; If there are upstream requirements that are not associated with valid requirements in the document to be released, the upstream requirement management coverage field on the task inspection work item will be set to failed, and the requirement ID of the unassociated upstream requirement will be stored in the task inspection work item.

5. The method according to claim 4, characterized in that The step of judging whether the check is passed based on the document item association check result and the upstream demand management coverage check result specifically includes: If the document item association check result and the upstream requirement management coverage check result are all failed or one of them is failed, the data review field of the task check work item is set to failed check; If there is no failure in the inspection result, the data review field of the task inspection work item is set to passed.

6. The method according to claim 5, characterized in that If the check fails, a link is provided in the check result attribute, and in response to a user click, the user is directed to the specific check problem item.

7. The method according to claim 2, characterized in that The task inspection work items specifically include: basic task information, document related information, inspection points and rules, inspection results and related party information.

8. A device for publishing automotive electronic and electrical architecture documents, characterized in that: include: The trigger module is used to automatically trigger the associated coverage check task when the user initiates the review and release process of the document to be released, and at the same time suspend the document to be released and jump to the review and release process; A checking module, used to execute the association coverage checking task, wherein the association coverage checking task includes document item association checking and upstream requirement management coverage checking; A judgment module is used to judge whether the check is passed based on the document item association check results and the upstream demand management coverage check results; The control module is used to control the document to be released to continue to execute the review and release process after the judgment module determines that the associated coverage check has passed.

9. A device for publishing automotive electronic and electrical architecture documents, characterized in that: include: one or more processors; Memory; One or more applications, wherein the one or more applications are stored in the memory and are configured to be executed by the one or more processors, and the one or more applications are configured to execute the automotive electronic and electrical architecture document publishing method as described in any one of claims 1 to 7.

10. A computer program product, characterized in that The method comprises computer instructions, wherein the computer instructions instruct a computer device to execute operations corresponding to the method according to any one of claims 1 to 7.