Method, system, device, medium and program for automatically auditing safety of expected function
Through the automated audit method, the SOTIF-related documents of the autonomous driving system are reviewed using keywords in the functional safety database, solving the problems of low efficiency and unstable quality of manual audits, and achieving efficient and accurate audit and evaluation.
Patent Information
- Application Number
- CN202510109895.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-01-23
- Publication Date
- 2025-06-13
AI Technical Summary
The SOTIF audit of existing autonomous driving systems relies on manual operations, resulting in large workload and inefficient work. The audit quality is low and the stability is poor due to subjective factors.
Provide an expected functional safety automated audit method, which can review the file name and text content of the target functional safety file by calling keywords in the functional safety database, generate audit results for integrity and content integrity, and realize automated audit evaluation.
Through automated means, a comprehensive and efficient audit and evaluation of target functional safety documents has been improved, and the audit efficiency and stability have been ensured, the accuracy and consistency of audits have been ensured, and the unified implementation of audit standards has been ensured.
Smart Images

Figure CN120145385A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of automated audit technology, and particularly to an automated audit method, system, device, medium and program for expected functional safety. Background Art
[0002] With the continuous progress of autonomous driving technology and the in-depth development of pilot access work, the research and development of high-level autonomous driving systems must follow the strict standards of SOTIF (Safety of the Intended Functionality). For this reason, China has issued the standard GB / T 43267-2023 "Road Vehicles - Expected Functional Safety", which details the development requirements and implementation guidelines of SOTIF, providing a clear reference framework for enterprises to develop autonomous driving systems.
[0003] In the access management of autonomous driving systems, specific and clear requirements are put forward for SOTIF to ensure that the system can safely and reliably perform its intended functions in the actual operating environment. To achieve this goal, third-party testing agencies undertake important audit and evaluation responsibilities, aiming to help enterprises improve their SOTIF-related capabilities.
[0004] In related technologies, it mainly relies on manual operations, which not only leads to a large workload and low efficiency, but also easily causes inconsistencies in the implementation of standards due to human factors, resulting in low audit quality and poor stability. Summary of the Invention
[0005] This application provides an automated audit method, system, device, medium and program for expected functional safety to solve the problems in related technologies such as large workload and low efficiency caused by relying on manual audits, and low audit quality and poor stability due to subjective factors.
[0006] In a first aspect embodiment of this application, an automated audit method for expected functional safety is provided, including the following steps: obtaining the file name and text content of at least one target functional safety file; calling all first target keywords in the functional safety database to audit the file name of the target functional safety file to generate an audit result of the file name; if the audit of the file name of at least one target functional safety file is successful, determining at least one second target keyword according to the first target keyword corresponding to the file name of the target functional safety file with a successful audit, and auditing the text content of the target functional safety file according to each second target keyword to generate an audit result of the text content; generating an audit result of the target functional safety file according to the audit result of the file name and the audit result of the text content.
[0007] Optionally, generating an audit result of the file name by auditing the file name of the target functional safety file according to the first target keyword includes: querying the file name of the target functional safety file with each first target keyword as an index; if each first target keyword does not match the file name of the target functional safety file, the audit of the file name of the target functional safety file fails; if there is at least one first target keyword that matches the file name of the target functional safety file, identifying all the first target keywords that do not match successfully; if each first target keyword matches at least one of the file names, the audit of the file name is successful.
[0008] Optionally, after identifying all the first target keywords that do not match successfully, it includes: querying the functional safety database with all the first target keywords that do not match successfully as an index to obtain the corresponding file names; generating a list of missing file names according to the file names corresponding to all the first target keywords that do not match successfully.
[0009] Optionally, generating an audit result of the text content by auditing the text content of the target functional safety file according to each second target keyword includes: querying the text content of the target functional safety file with each second target keyword as an index; if the text content contains each second target keyword, the audit of the text content is successful; if the text content does not completely contain each second target keyword, the audit of the text content fails.
[0010] Optionally, after the audit of the text content fails, it includes: identifying the second target keywords not included in the text content; generating a list of missing keywords according to the second target keywords not included in the text content.
[0011] Optionally, generating an audit result of the target functional safety file according to the audit result of the file name and the audit result of the text content includes: if both the audit result of the file name and the audit result of the text content are successful, outputting an integrity audit report of the target functional safety file; if the audit of the file name fails and / or the audit of the text content fails, outputting a corresponding audit report according to the list of missing file names and / or the list of missing keywords of the target functional safety file.
[0012] The second aspect of the present application provides an expected functional safety automated audit system, including: a file import module for importing at least one target functional safety file into a rule editing module; a rule editing module for calibrating a corresponding functional safety database according to the type of the target functional safety file, where the functional safety database includes a first preset table and a second preset table; a problem identification module for calling all first target keywords in the functional safety database to audit the file name of the target functional safety file to generate an audit result of the file name; if the file name audit of at least one target functional safety file is successful, determining at least one second target keyword according to the first target keyword corresponding to the file name of the successfully audited target functional safety file, and auditing the text content of the target functional safety file according to each second target keyword to generate an audit result of the text content; generating an audit result of the target functional safety file according to the audit result of the file name and the audit result of the text content; a report generation module for generating an evaluation audit report according to the audit result of the target functional safety file output by the problem identification module.
[0013] The third aspect of the present application provides a host computer, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, and the processor executes the program to perform the expected functional safety automated audit method as described in the above embodiments.
[0014] The fourth aspect of the present application provides a computer-readable storage medium, on which a computer program is stored, and the program is executed by a processor to perform the expected functional safety automated audit method as described in the above embodiments.
[0015] The fifth aspect of the present application provides a computer program product, including a computer program or instruction, characterized in that when the computer program or instruction is executed, it realizes the expected functional safety automated audit method as described in the above embodiments.
[0016] Therefore, the present application has at least the following beneficial effects:
[0017] The embodiments of the present application can call all the first target keywords in the functional safety database to audit the file names of the target functional safety files and generate the audit results of the file names. If the file names of at least one target functional safety file are successfully audited, at least one second target keyword is determined according to the first target keyword corresponding to the file name of the successfully audited target functional safety file, and the text content of the target functional safety file is audited according to each second target keyword to generate the audit results of the text content. The audit results of the target functional safety file are generated according to the audit results of the file names and the audit results of the text content, and the target functional safety file is comprehensively and efficiently audited and evaluated by means of automation. The integrity of the target functional safety file and the integrity of the corresponding technical points in the file are audited according to the first target keyword and the second target keyword, so as to help the development team clarify which files and the text content corresponding to the technical points need to be supplemented, which not only improves the audit efficiency, but also improves the stability, accuracy and consistency of the audit, and at the same time can ensure the unified implementation of the audit standards to ensure that the enterprise system meets the requirements of the expected functional safety standards in the processes of design, verification and validation, etc.
[0018] Additional aspects and advantages of the present application will be given in part in the following description, become apparent in part from the following description, or be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] The above and / or additional aspects and advantages of the present application will become apparent and be readily understood from the following description of the embodiments in conjunction with the drawings, wherein:
[0020] Figure 1 is a flowchart of an expected functional safety automation audit method according to an embodiment of the present application;
[0021] Figure 2 is a schematic diagram of the audit content according to an embodiment of the present application;
[0022] Figure 3 is a flowchart of the audit evaluation according to an embodiment of the present application;
[0023] Figure 4 is an example diagram of an expected functional safety automation audit system according to an embodiment of the present application;
[0024] Figure 5 is a tool architecture diagram according to an embodiment of the present application;
[0025] Figure 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0026] Embodiments of the present application will be described in detail below. Examples of the embodiments are shown in the accompanying drawings, where the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to explain the present application, and should not be construed as a limitation of the present application.
[0027] The expected functional safety automated audit method, system, electronic device, storage medium and program of the embodiments of the present application will be described below with reference to the accompanying drawings.
[0028] Specifically, Figure 1 is a schematic flow chart of an expected functional safety automated audit method provided by an embodiment of the present application.
[0029] As Figure 1 shown, the expected functional safety automated audit method includes the following steps:
[0030] In step S101, the file name and text content of at least one target functional safety file are obtained.
[0031] Among them, the target functional safety files include enterprise capability-related files and product development-related files, and no specific limitations are made.
[0032] It can be understood that the embodiments of the present application can obtain the file name and text content of at least one target functional safety file, so as to subsequently audit the file name of the target functional safety file using the first target keyword and audit the text content of the target functional safety file using the second target keyword.
[0033] It should be noted that the present application supports the import of multiple file formats. For example, the multiple file formats are:.txt,.xls,.xlsx,.doc,.docx,.jpg,.png,.gif,.pdf format files.
[0034] Specifically, as Figure 2 shown, the content of the expected functional safety automated audit proposed by the present application is divided into two major parts, namely the enterprise capability part and the product technology part; the audit objectives of each part also include file integrity, content integrity and unity.
[0035] The enterprise capability-related files of the present application are mainly the files related to the expected functional safety process system of the enterprise; the product technology-related files are mainly the files related to the expected functional safety development of the autonomous driving system; in addition, the present application can import one or more target functional safety files, and by automatically extracting the file name and text content of the target functional safety files, the entire audit cycle can be greatly shortened and the audit efficiency can be improved.
[0036] In step S102, the file names of the target functional safety files are audited by calling all the first target keywords in the functional safety database to generate the audit results of the file names.
[0037] It can be understood that the embodiments of the present application can call the file names of all the first target keywords in the functional safety database to audit the file names of the target functional safety files. By keyword matching, the consistency and accuracy of the file names are ensured, and the integrity of the target functional safety files and whether they meet the requirements of the expected functional safety standards can be clarified, reducing the subjective judgment errors that may be brought by manual auditing and improving the auditing efficiency.
[0038] In the embodiments of the present application, generating the audit results of the file names by auditing the file names of the target functional safety files according to the first target keywords includes: using each first target keyword as an index to query the file names of the target functional safety files; if each first target keyword does not match the file name of the target functional safety file, the audit of the file name of the target functional safety file fails; if there is at least one first target keyword that matches the file name of the target functional safety file, identify all the first target keywords that have not been successfully matched; if each first target keyword matches at least one file name, the audit of the file name is successful.
[0039] It can be understood that the embodiments of the present application match each first target keyword with the file names of each target functional safety file one by one, clarify the integrity of the target functional safety files according to the matching results, and the automated auditing can quickly process a large number of files, improving the auditing efficiency to ensure that all file names meet the requirements of the expected functional safety, and improving the overall safety and reliability of the product.
[0040] Specifically, the functional safety database of the embodiments of the present application includes a first preset table and a second preset table. The first preset table is mainly the enterprise ability files and examples of audit points, as shown in Table 1 below. The second preset table is mainly the product development files and examples of audit points, as shown in Table 2 below.
[0041] It should be noted that the first target keywords of the embodiments of the present application correspond to the file integrity audit keywords in the first preset table and the second preset table, and the first preset table and the second preset table can be set according to actual needs without specific limitations.
[0042] Table 1 Examples of enterprise ability files and audit points
[0043]
[0044]
[0045]
[0046] Table 2 Example of Product Development Documents and Key Points for Review
[0047]
[0048]
[0049] In the embodiment of the present application, after identifying all the first target keywords that do not match successfully, it includes: using all the first target keywords that do not match successfully as an index to query the functional safety database to obtain the corresponding file names; generating a list of missing file names according to the file names corresponding to all the first target keywords that do not match successfully.
[0050] It can be understood that in the embodiment of the present application, using all the first target keywords that do not match successfully as an index to query the functional safety database to obtain the corresponding file names; generating a list of missing file names according to the file names corresponding to all the first target keywords that do not match successfully, so as to determine the list of missing file names for the files imported this time, which helps the development team clarify which files need to be supplemented, not only improving the review efficiency, but also ensuring the consistency of the review results between different batches.
[0051] Specifically, as Figure 3 shown, after the file name matching of the target functional safety file is completed, determine all the first target keywords that do not match successfully, and query the first preset table according to the first target keywords to generate the corresponding missing file names as shown in Table 1 above.
[0052] For example, after the file name matching of the target functional safety file is completed, the determined first target keywords that do not match successfully are "safety plan" and "distributed development". By looking up Table 1 above, it is determined that the corresponding list of missing file names is: safety plan and distributed development management.
[0053] In step S103, if the file name review of at least one target functional safety file is successful, then determine at least one second target keyword according to the first target keyword corresponding to the file name of the target functional safety file with a successful review, and review the text content of the target functional safety file according to each second target keyword to generate the review result of the text content.
[0054] It is understandable that if the file name review of at least one target functional safety file in the embodiments of the present application is successful, at least one second target keyword is determined according to the first target keyword corresponding to the file name of the target functional safety file with successful review. The text content of the target functional safety file is reviewed according to each second target keyword to generate a review result of the text content, and the integrity of the technical key points in the target functional safety file is clarified, so as to further review the missing items in the text content of the target functional safety file, help the development team improve the document content, and thus ensure that both the file name and the text content of the target functional safety file meet the requirements of the expected functional safety.
[0055] For example, if the file name reviews of multiple target functional safety files are successful, the corresponding first target keywords are: "management process" and "safety plan". Then, according to the first target keywords, the first preset table is queried. As shown in Table 1 above, the second target keywords are determined to be: "expected functional safety regulations", "expected functional safety processes", "version management", "personnel and responsibilities", "deliverable requirements", and the purpose, preconditions, outputs, responsible persons, start time, end time, and status of safety activities.
[0056] In the embodiments of the present application, the text content of the target functional safety file is reviewed according to each second target keyword to generate a review result of the text content, including: querying the text content of the target functional safety file with each second target keyword as an index; if the text content contains each second target keyword, the text content review is successful; if the text content does not completely contain each second target keyword, the text content review fails.
[0057] It is understandable that in the embodiments of the present application, the text content of the target functional safety file is queried with each second target keyword as an index; if the text content contains each second target keyword, the text content review is successful; if the text content does not completely contain each second target keyword, the text content review fails, so as to comprehensively check whether the text content meets the requirements of the expected functional safety, ensure the consistency of the review criteria between different files, avoid differences caused by human factors, and improve the stability and consistency of the review.
[0058] Specifically, as Figure 3 shown, it is to query whether the text content of the target functional safety file includes all keywords according to the second target keyword. For example, if the text content of the target functional safety file contains "expected functional safety regulations", "expected functional safety processes", "version management", "personnel and responsibilities", but lacks "deliverable requirements", then the content review fails.
[0059] In the embodiment of the present application, after the text content review fails, it includes: identifying a second target keyword not included in the text content; generating a missing keyword list based on the second target keyword not included in the text content.
[0060] It can be understood that the embodiment of the present application can identify the second target keyword not included in the text content; generate a missing keyword list based on the second target keyword not included in the text content, thereby providing specific improvement suggestions for the development team to help them improve the document content, ensure that all necessary information is covered, and ensure that both the file name and text content of the target functional safety file meet the requirements of the expected functional safety.
[0061] In step S104, the review result of the target functional safety file is generated according to the review result of the file name and the review result of the text content.
[0062] It can be understood that the embodiment of the present application can generate the review result of the target functional safety file according to the review result of the file name and the review result of the text content, and conduct a comprehensive and efficient review and evaluation of the target functional safety file through automated means, which not only improves the review efficiency and accuracy, but also ensures the unified implementation of the review criteria and improves the stability of the review.
[0063] In the embodiment of the present application, generating the review result of the target functional safety file according to the review result of the file name and the review result of the text content includes: if the review results of both the file name and the text content are successful, outputting a completeness review report of the target functional safety file; if the review of the file name fails and / or the review of the text content fails, outputting a corresponding review report according to the missing file name list and / or the missing keyword list of the target functional safety file.
[0064] It can be understood that in the embodiment of the present application, if the review results of both the file name and the text content are successful, a completeness review report of the target functional safety file is output; if the review of the file name fails and / or the review of the text content fails, a corresponding review report is output according to the missing file name list and / or the missing keyword list of the target functional safety file, thereby providing specific improvement suggestions for the development team to help them improve the document content, ensure that all necessary information is covered, and ensure that both the file name and text content of the target functional safety file meet the requirements of the expected functional safety.
[0065] According to the expected functional safety automated auditing method proposed by the embodiments of the present application, all first target keywords in the functional safety database are called to audit the file name of the target functional safety file to generate the audit result of the file name. If the file name audit of at least one target functional safety file is successful, at least one second target keyword is determined according to the first target keyword corresponding to the file name of the successfully audited target functional safety file, and the text content of the target functional safety file is audited according to each second target keyword to generate the audit result of the text content. The audit result of the target functional safety file is generated according to the audit result of the file name and the audit result of the text content, and the target functional safety file is comprehensively and efficiently audited and evaluated by automated means, and the integrity of the target functional safety file and the integrity of the corresponding technical points in the file are audited according to the first target keyword and the second target keyword, so as to help the development team clarify which files and the text content corresponding to the technical points need to be supplemented, which not only improves the audit efficiency, but also improves the stability, accuracy and consistency of the audit, and at the same time can ensure the unified implementation of the audit standard to ensure that the enterprise system meets the requirements of the expected functional safety standard in the processes of design, verification and validation, etc.
[0066] Next, the expected functional safety automated auditing system proposed by the embodiments of the present application is described with reference to the accompanying drawings.
[0067] Figure 4 It is a block diagram of the expected functional safety automated auditing system of the embodiments of the present application.
[0068] As Figure 4 shown, the expected functional safety automated auditing system 10 includes: a file import module 100, a rule editing module 200, a problem identification module 300, and a report generation module 400.
[0069] Among them, the file import module 100 is used to import at least one target functional safety file into the rule editing module; the rule editing module 200 is used to calibrate the corresponding functional safety database according to the type of the target functional safety file, where the functional safety database includes a first preset table and a second preset table; the problem identification module 300 is used to call all first target keywords in the functional safety database to audit the file name of the target functional safety file to generate an audit result of the file name; if the file names of at least one target functional safety file are successfully audited, at least one second target keyword is determined according to the first target keyword corresponding to the file name of the successfully audited target functional safety file, and the text content of the target functional safety file is audited according to each second target keyword to generate an audit result of the text content; an audit result of the target functional safety file is generated according to the audit result of the file name and the audit result of the text content; the report generation module 400 is used to generate an evaluation audit report according to the audit result of the target functional safety file output by the problem identification module.
[0070] It should be noted that the foregoing explanation of the embodiments of the expected functional safety automated audit method is also applicable to the expected functional safety automated audit system of this embodiment, and will not be elaborated here.
[0071] According to the expected functional safety automated audit system proposed in the embodiments of the present application, all first target keywords in the functional safety database are called to audit the file name of the target functional safety file to generate an audit result of the file name; if the file names of at least one target functional safety file are successfully audited, at least one second target keyword is determined according to the first target keyword corresponding to the file name of the successfully audited target functional safety file, and the text content of the target functional safety file is audited according to each second target keyword to generate an audit result of the text content; an audit result of the target functional safety file is generated according to the audit result of the file name and the audit result of the text content, and the target functional safety file is comprehensively and efficiently audited and evaluated by automated means, and the integrity of the target functional safety file and the integrity of the corresponding technical points in the file are audited according to the first target keyword and the second target keyword, so as to help the development team clarify which files and the text content corresponding to the technical points need to be supplemented, which not only improves the audit efficiency, but also improves the stability, accuracy and consistency of the audit, and at the same time can ensure the unified implementation of the audit standard to ensure that the enterprise system meets the requirements of the expected functional safety standard in the processes of design, verification and validation.
[0072] Next, Figure 5 The expected functional safety automated audit system and method of the present application will be elaborated in detail as follows:
[0073] In view of the problems and deficiencies of manual review, this application provides an automated review system for expected functional safety, which comprehensively and efficiently reviews and evaluates the enterprise's expected functional safety process system and the expected functional safety development process of the autonomous driving system through automated means, ensuring that the system meets the requirements of the SOTIF standard during the processes of design, verification, and validation. Among them, the automated review system for expected functional safety is equivalent to an automated review and evaluation tool for expected functional safety.
[0074] First of all, the content reviewed by the automated review and evaluation system for expected functional safety proposed in this application is divided into two major parts, namely the enterprise ability part and the product technology part. The review objectives of each part also include document integrity, content integrity, and unity.
[0075] Among them, the enterprise ability part reviews whether the enterprise's expected functional safety process system is perfect, while product technology focuses on the documents related to the expected functional safety development of the autonomous driving system. When reviewing, first check whether the relevant documents that should be included are present to complete the review of document integrity; secondly, check whether the documents contain the necessary content to complete the review of content integrity.
[0076] The automated review tools mainly adopted by the automated review system for expected functional safety include a file import module, a rule editing module, a problem identification module, and a report generation module. Specifically:
[0077] (1) File import module
[0078] Supports the import of files in the formats of.txt,.xls,.xlsx,.doc,.docx,.jpg,.png,.gif,.pdf.
[0079] (2) Rule editing module
[0080] In the rule editing module, set the target text file name and the keywords in the file content for rule setting.
[0081] The following Table 1 and Table 2 are respectively examples of the content included in the enterprise ability part and the product technology part, which can be set according to requirements and are not specifically limited.
[0082] Table 1 Examples of enterprise ability files and review key points
[0083]
[0084]
[0085]
[0086] Table 2 Examples of product development files and review key points
[0087]
[0088] (3) Problem identification module (such as Figure 3 )
[0089] First, conduct a file integrity review process on the submitted materials; according to the expected functional safety process system and the list of critical file names required for product development, such as "Specification Definition and Design Template", "Hazard Analysis and Risk Assessment Guidebook", "Change Management", etc., the system automatically extracts the file names from the uploaded files and matches them with the preset keyword list (Table 1 or Table 2 above), and outputs the corresponding missing file names in the problem record section for the matched files.
[0090] Secondly, conduct a review of content integrity, delve into the interior of the document, and conduct a detailed keyword retrieval review on key elements such as chapter titles and body content according to the expected functional safety development requirements. Taking the product hazard analysis and risk assessment work as an example, keywords such as "Design Operating Range", "Task Privilege Level", "SOTIF Strategy at the Vehicle Level", etc. will be used to accurately retrieve and compare the relevant content in the document, and output the missing key points.
[0091] (4) Report generation module
[0092] The report generation module presents all the missing items identified in the file integrity and content integrity during the review process, forms a list of files not provided or not meeting the requirements, and the missing situation of key development content (such as risk assessment, verification test report, etc.), ensuring the accuracy of the review results and providing a basis for subsequent improvement.
[0093] In summary, this application conducts a review and evaluation of the expected functional safety process system and product development by automatically comparing and retrieving the keyword list, significantly improving the efficiency of the review and evaluation, reducing the time and cost of manual operations, and at the same time, reducing errors and omissions caused by human factors.
[0094] Figure 6 It is a schematic structural diagram of the host computer provided for the embodiment of this application. The host computer may include:
[0095] A memory 601, a processor 602, and a computer program stored on the memory 601 and executable on the processor 602.
[0096] When the processor 602 executes the program, it implements the expected functional safety automation review method provided in the above embodiment.
[0097] Furthermore, the host computer further includes:
[0098] A communication interface 603 for communication between the memory 601 and the processor 602.
[0099] A memory 601 for storing a computer program that can run on a processor 602.
[0100] The memory 601 may include a high-speed RAM memory and may also include non-volatile memory, such as at least one disk memory.
[0101] If the memory 601, the processor 602, and the communication interface 603 are implemented independently, the communication interface 603, the memory 601, and the processor 602 can be interconnected via a bus and communicate with each other. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of simplicity of representation, Figure 6 only a thick line is shown in the figure, but it does not mean that there is only one bus or one type of bus.
[0102] Optionally, in a specific implementation, if the memory 601, the processor 602, and the communication interface 603 are integrated on a single chip, the memory 601, the processor 602, and the communication interface 603 can communicate with each other through an internal interface.
[0103] The processor 602 may be a Central Processing Unit (CPU), or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.
[0104] The embodiments of the present application also provide a computer-readable storage medium, on which a computer program or instruction is stored. When the computer program or instruction is executed by a processor, the expected functional safety automation audit method as described above is implemented.
[0105] The embodiments of the present application also provide a computer program product, including a computer program or instruction, characterized in that when the computer program or instruction is executed, the expected functional safety automation audit method as described above is implemented.
[0106] In the description of this specification, the descriptions referring to terms such as "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. mean that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of this application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in a suitable manner in any one or N embodiments or examples. In addition, without contradiction, those skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples.
[0107] In addition, the terms "first" and "second" are used for descriptive purposes only and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include at least one of such features. In the description of this application, the meaning of "N" is at least two, such as two, three, etc., unless otherwise specifically and clearly defined.
[0108] Any process or method description in a flowchart or described in other ways herein can be understood to represent a module, segment, or portion of code including one or N executable instructions for implementing a customized logical function or process, and the scope of the preferred embodiments of this application includes additional implementations, where the functions can be executed in a substantially simultaneous manner or in a reverse order according to the functions involved, rather than in the order shown or discussed, which should be understood by those skilled in the technical field to which the embodiments of this application belong.
[0109] It should be understood that each part of this application can be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one or a combination of the following techniques well known in the art: discrete logic circuits with logic gate circuits for implementing logical functions on data signals, application specific integrated circuits with appropriate combinational logic gate circuits, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), etc.
[0110] Those of ordinary skill in the art of this technology can understand that all or part of the steps carried by the methods of the above embodiments can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiments.
Claims
1. An automated audit method for expected functional safety, characterized in that: The following steps are involved: Obtaining a file name and text content of at least one target functional safety file; Calling all first target keywords in the functional safety database to review the file name of the target functional safety file and generate a review result of the file name; If there is at least one target functional safety file whose file name is successfully reviewed, determining at least one second target keyword according to the first target keyword corresponding to the file name of the successfully reviewed target functional safety file, and reviewing the text content of the target functional safety file according to each second target keyword to generate a review result of the text content; The audit result of the target functional safety file is generated according to the audit result of the file name and the audit result of the text content.
2. The method for automated review of expected functional safety according to claim 1, characterized in that: The step of reviewing the file name of the target functional safety file according to the first target keyword to generate the review result of the file name includes: Using each first target keyword as an index, query the file name of the target functional safety file; If each first target keyword does not match the file name of the target functional safety file, the file name review of the target functional safety file fails; If there is at least one first target keyword that matches the file name of the target functional safety file, identifying all first target keywords that have not been successfully matched; If each first target keyword matches at least one of the file names, the file name review is successful.
3. The method for automated review of expected functional safety according to claim 2, characterized in that: After identifying all the first target keywords that have not been successfully matched, the method includes: Using all the first target keywords that have not been successfully matched as indexes, query the functional safety database to obtain the corresponding file names; A missing file name list is generated according to the file names corresponding to all the first target keywords that have not been successfully matched.
4. The method for automated review of expected functional safety according to claim 1, characterized in that: The step of reviewing the text content of the target functional safety file according to each second target keyword to generate a review result of the text content includes: Using each second target keyword as an index, querying the text content of the target functional safety file; If the text content contains each second target keyword, the text content review is successful; If the text content does not completely include each second target keyword, the text content review fails.
5. The method for automated review of expected functional safety according to claim 4, characterized in that: After the said text content audit fails, including: identifying a second target keyword not included in the text content; A missing keyword list is generated according to second target keywords not included in the text content.
6. The method for automated review of expected functional safety according to claim 3 or 5, characterized in that: Generating the audit result of the target functional safety file according to the audit result of the file name and the audit result of the text content includes: If the audit results of the file name and the audit results of the text content are both successful, then outputting the integrity audit report of the target functional safety file; If the audit of the file name fails and / or the audit of the text content fails, a corresponding audit report is output according to the missing file name list and / or the missing keyword list of the target functional safety file.
7. An automated review system for expected functional safety, characterized in that: include: A file import module, used for importing at least one target functional safety file into the rule editing module; A rule editing module, used to calibrate a corresponding functional safety database according to the type of the target functional safety file, wherein the functional safety database includes a first preset table and a second preset table; A problem identification module is used to call all first target keywords in a functional safety database to review the file name of the target functional safety file and generate a review result of the file name; if there is at least one target functional safety file whose file name is successfully reviewed, determine at least one second target keyword according to the first target keyword corresponding to the file name of the successfully reviewed target functional safety file, and review the text content of the target functional safety file according to each second target keyword to generate a review result of the text content; generate a review result of the target functional safety file according to the review result of the file name and the review result of the text content; The report generation module is used to generate an assessment audit report based on the audit results of the target functional safety file output by the problem identification module.
8. A host computer, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the method for automated review of expected functional safety as described in any one of claims 1 to 6.
9. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed by a processor, it is used to implement the method for automated review of expected functional safety as described in any one of claims 1 to 6.
10. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed, the method for automated review of expected functional safety as described in any one of claims 1 to 6 is implemented.
Citation Information
Cited By
Safety auditing method and device based on artificial intelligence function, medium and equipment
CN121389141A