Modeling method and device for testability analysis, equipment and storage medium

Abstract

The invention provides a modeling method and device for testability analysis, equipment and a storage medium, and the method comprises the steps: carrying out the principle analysis of a to-be-modeled mixed diagnosis model, and determining the structure of each to-be-modeled element; based on the structure of each element to be modeled, an element library is defined, and the element library comprises nodes, connecting lines, images, node attributes of the nodes, connecting line attributes of the connecting lines and graph attributes of the graphs; writing a graph drawing program based on the element library; converting the function and fault information of the hybrid diagnosis model into a data structure corresponding to a preset algorithm; when the model testability information is set, the test information is set based on the graph drawing program, the element library and the data structure. According to the invention, rapid modeling can be carried out based on the to-be-modeled hybrid diagnosis model.

Description

Technical Field

[0001] The present invention relates to the technical field of quality characteristic analysis, and particularly to a modeling method, device, equipment and storage medium for testability analysis. Background Art

[0002] With the continuous development and wide application of electronic technology, the technology, structure and function of various equipment are becoming increasingly complex, and the system integration degree has also increased sharply. The design method relying solely on manual work and intuition can often only solve the fault diagnosis problems of products or airborne equipment with simple cross-linking relationships, and it is difficult to evaluate the testability design effect of equipment with complex structures, diverse functions and complex dependence relationships.

[0003] Testability analysis is to evaluate the possible testability level of a product through inherent testability evaluation, testability prediction and testability cost prediction, and ensure the effective integration and compatibility of testability with other diagnostic elements.

[0004] To solve the above problems, the testability modeling and simulation analysis technology is introduced into the testability professional field. Testability modeling is a process of describing the constituent units, signals, fault modes, failure rates, tests of a system or equipment and their mutual relationships in a standardized form. After describing and expressing the testability design of the system in this way, it is convenient to use a computer for auxiliary analysis, and the testability design can be improved according to the analysis results, and the dependence relationship between the test method and the fault mode and the diagnostic test strategy can be automatically generated, greatly improving the efficiency of testability design.

[0005] However, the modeling process of the current testability analysis method is relatively complex and cannot be modeled quickly. Summary of the Invention

[0006] Embodiments of the present invention provide a modeling method, device, equipment and storage medium for testability analysis to solve the problem that the modeling speed of the current testability analysis method is relatively slow.

[0007] In a first aspect, embodiments of the present invention provide a modeling method for testability analysis, including:

[0008] Performing a principle analysis on the hybrid diagnosis model to be modeled to determine the structures of the components to be modeled;

[0009] Defining a component library based on the structures of the components to be modeled, where the component library includes nodes, connections and images, as well as the node attributes of each node, the connection attributes of each connection and the graphic attributes of each graphic;

[0010] Writing a graphic drawing program based on the component library;

[0011] Convert the functions and fault information of the hybrid diagnostic model into the data structure corresponding to the preset algorithm;

[0012] When setting the testability information of the model, set the test information based on the graphics drawing program, component library, and data structure.

[0013] In a possible implementation manner, when setting the testability information of the model, set the test information based on the graphics drawing program, component library, and data structure, including:

[0014] Determine the input of the functions and fault information of the hybrid diagnostic model based on the node attributes or connection attributes in the component library;

[0015] Based on the input of the functions and fault information of the hybrid diagnostic model, add or update the input information to the variables of the nodes or connections in the component library;

[0016] Based on the input of the test information of the hybrid diagnostic model, read the selected graphics as test point components, and add a test set and test information to the graphics.

[0017] In a possible implementation manner, the node attributes and connection attributes need to be converted into a table form of the same format, and the conversion methods include:

[0018] Convert based on the form of saving and reading excel files; or

[0019] Transfer through the form of a DataSet data table.

[0020] In a possible implementation manner, write a graphics drawing program based on the component library, including:

[0021] Add a System Drawing reference. When initializing the graphics drawing program, create multiple Graphics class objects based on Bimap and Image objects;

[0022] Place various button controls in the component library. When clicking different button controls, call the class object corresponding to the button control; among them, one button control corresponds to one Graphics class object;

[0023] Draw different graphics based on the GDI methods of different Graphics class objects.

[0024] In a possible implementation manner, the basic attributes of each node include graphics attributes, connection attributes, component attributes, fault modes, fault impacts, and test information;

[0025] The graphics attributes are used to define the name, appearance, type, and port information of the target node object;

[0026] The connection attribute is used to define the sequence number of the target node in the node list, the numbers of other nodes connected to the ports of this node, and the number of connection lines included in this node.

[0027] The component attribute is used to define the repair or replacement cost, time, and failure rate after the component fails;

[0028] The failure mode is used to define the failure mode and the failure mode frequency ratio of the target node;

[0029] The failure effect is used to define the failure effect and severity of the component;

[0030] The test information is used to define the test name, the test set to which it belongs, and the type of the test for the target node.

[0031] In a possible implementation manner, the basic attributes of each connection line include graphic attributes, line sequence attributes, component attributes of the connections, and component port attributes of the connections;

[0032] The graphic attributes are used to define the position, appearance, color, and style of the connection line;

[0033] The line sequence attributes are used to define the sequence number of the connection line in the whole line list;

[0034] The component attributes of the connections are used to define the nodes connected by the start point and the end point of the connection line.

[0035] In a possible implementation manner, the modeling of each graphic is implemented based on the drawObject class.

[0036] In a second aspect, an embodiment of the present invention provides a modeling device for testability analysis, including:

[0037] An analysis module, configured to perform a principle analysis on the hybrid diagnosis model to be modeled, and determine the structures of the components to be modeled;

[0038] A definition module, configured to define a component library based on the structures of the components to be modeled, where the component library includes nodes, connection lines, and images, as well as node attributes of each node, connection line attributes of each connection line, and graphic attributes of each graphic;

[0039] A writing module, configured to write a graphic drawing program based on the component library;

[0040] A conversion module, configured to convert the functions and failure information of the hybrid diagnosis model into a data structure corresponding to a preset algorithm;

[0041] A setting module, configured to perform test information setting based on the graphic drawing program, the component library, and the data structure when performing model testability information setting.

[0042] In a third aspect, an embodiment of the present invention provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of the method described in the first aspect above or any possible implementation manner of the first aspect are implemented.

[0043] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the steps of the method described in the first aspect above or any possible implementation manner of the first aspect are implemented.

[0044] An embodiment of the present invention provides a modeling method, device, equipment, and storage medium for testability analysis. In order to determine the structure between the components to be modeled, it is necessary to first perform a principle analysis on the hybrid diagnostic model to be modeled. Then, based on the structure of the components to be modeled, a component library is defined, so that the attributes of nodes, connections, and each graph can be defined. Next, based on the component library, a graph drawing program is written. Then, the functions and fault information of the hybrid diagnostic model are converted into the data structure corresponding to the preset algorithm. Finally, when setting the testability information of the model, based on the graph drawing program, the component library, and the data structure, the test information is set. The modeling method provided by the present invention first defines a component library and writes a graph drawing program based on the component library, so that the modeling can be quickly performed based on the hybrid diagnostic model to be modeled. In addition, by converting the functions and fault information of the hybrid diagnostic model into the data structure corresponding to the preset algorithm, the data structure conversion of the hybrid diagnostic model can be realized. Finally, based on the graph drawing program, the component library, and the data structure, the test information can be set, thereby greatly improving the modeling speed and realizing rapid modeling. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings required for use in the embodiments or the description of the prior art. Obviously, the following drawings are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0046] Figure 1 is a flowchart of the implementation of the modeling method for testability analysis provided by the embodiment of the present invention;

[0047] Figure 2 is a schematic diagram of the function type provided by the embodiment of the present invention;

[0048] Figure 3 is a schematic diagram of the structure of the model information stored in each data table provided by the embodiment of the present invention;

[0049] Figure 4 It is a schematic structural diagram of a modeling device for testability analysis provided by an embodiment of the present invention;

[0050] Figure 5 It is a schematic diagram of an electronic device provided by an embodiment of the present invention. Detailed implementation manners

[0051] In the following description, specific details such as specific system structures and technologies are proposed for the purpose of illustration rather than limitation, so as to thoroughly understand the embodiments of the present invention. However, those skilled in the art should clearly understand that the present invention can also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid unnecessary details from interfering with the description of the present invention.

[0052] To make the purpose, technical solution, and advantages of the present invention clearer, the following will be described through specific embodiments with reference to the accompanying drawings.

[0053] To solve the problems of the prior art, embodiments of the present invention provide a modeling method, device, equipment, and storage medium for testability analysis. First, the modeling method for testability analysis provided by the embodiments of the present invention will be introduced below.

[0054] Refer to Figure 1 , which shows the implementation flowchart of the modeling method for testability analysis provided by the embodiments of the present invention, and is described in detail as follows:

[0055] S110. Conduct a principle analysis on the hybrid diagnostic model to be modeled, and determine the structures of the components to be modeled.

[0056] The hybrid diagnostic model (HDM) is a diagnostic model that combines a function model and a fault mode model in a system model, and it is an extension of the correlation diagnostic model. By integrating the function model and the fault mode model, the hybrid diagnostic model can analyze and diagnose faults in the system more comprehensively. The hybrid diagnostic model performs well in fault analysis and can effectively perform fault reasoning. By combining the function and fault mode models, the hybrid diagnostic model can provide more accurate diagnostic reasoning rules and is applicable to various complex system fault analyses.

[0057] By first conducting a principle analysis on the hybrid diagnostic model to be modeled, the data structure between the components to be modeled can be determined.

[0058] S120. Define a component library based on the structures of the components to be modeled.

[0059] Among them, the component library includes nodes, connections, and images, as well as the node attributes of each node, the connection attributes of each connection, and the graphic attributes of each graphic.

[0060] The component library integrates various models of components in a library for easy management and use. These models include schematic symbol models for drawing schematic diagrams, package models for making PCBs, SPICE models for circuit simulation, and SI models for circuit board signal analysis. Using an integrated component library can make the management of component libraries clearer and more efficient.

[0061] In some embodiments, the data structure of the basic node attributes is implemented through the Node class, where each node is an instance of the Node class. Member variables of the node class are defined in the Node class, which can be divided into several parts: graphic attributes, connection attributes, component attributes, fault modes, fault impacts, and test information.

[0062] In this embodiment, the graphic attributes define basic attributes such as the name, appearance, type, and port information of the node object. The connection attributes define the serial number of the node in the node list, the numbers of other nodes connected to the ports of this node, and the number of wires contained in this node. The component attributes define the repair or replacement cost, time, and failure rate after the component fails. The fault mode attributes define the possible fault modes of this node. The fault mode frequency ratio refers to the ratio of each fault occurring separately, and the sum of the frequency ratios of all faults should be 100%, and this fault affects all functions of the component. The fault impact attributes define the fault impact and severity of this component, that is, the severity index of the possible consequences after the component fails. Finally, the test attributes include the test name located at this node, the test set it belongs to, and the type of the test.

[0063] In some embodiments, the description of the wire-related attributes is implemented in the Line class, and each wire is an instance of the Line class. The wire attributes include graphic attributes, wire sequence attributes, connected component attributes, and connected component port attributes. Among them, the graphic attributes include attributes such as the position, appearance, color, and style of the wire: the wire sequence attributes indicate the serial number of this wire in the entire wire list and the number of coordinate points used for wire positioning. Using this information, each wire stored in the array can be distinguished: the connected component attributes include the nodes connected by the start and end points of the wire, and the component connection attributes indicate the ports of the components connected at the start and end of the wire respectively. These two attributes divide the connection network of the current model into segments with ports as the start and end points, which plays a crucial role in the traversal and analysis of the model.

[0064] In some embodiments, the related functions of graphical modeling are implemented through the drawObject class. This class contains not only data members describing the graphical structure of the model but also functions for the user to process the graphics when drawing.

[0065] In this embodiment, the functions in the drawObject class can be generally divided into several parts as shown in Figure 2 . When the user selects modules from the component library and draws on the design panel, the software creates, deletes, moves, and modifies the appearance of graphic objects by judging the user's mouse operations and the current position of the mouse, and calls different methods according to different operations of the user to process data and display it on the interface. Finally, the drawn graphics are stored in an array classified by components, connections, and text for subsequent calls.

[0066] S130. Write a graphic drawing program based on the component library.

[0067] In some embodiments, when writing the graphic drawing program, the Graphics Device Interface provided by MicroSoft is adopted.

[0068] In Visual C#, the GDI+ (Graphies Device Interface Plus) version can be used to write programs related to graphic drawing. It is an updated interface provided after extending GDI. Compared with GDI, it is more flexible to use, which greatly facilitates the user's programming use and secondary development. The steps to write a graphic interface using GDI+ are as follows:

[0069] First, add a System.Drawing reference in the program. When the program is initialized, first create a Graphics class object using Bimap and Image objects so that the object can be referenced from the events of the control next.

[0070] Then, place Button controls representing different shapes and types in the component library interface. When the user clicks different buttons, their corresponding Click events will be called.

[0071] Finally, use the GDI methods of different Graphics objects in the event to draw various graphics, display text, or implement image processing as needed, such as pictures (Drawlmage), lines (DrawLine), circles (DrawEllipse, FillElipse), writing boards (DrawString), etc.

[0072] S140. Convert the functions and fault information of the hybrid diagnostic model into the data structure corresponding to the preset algorithm.

[0073] The drawFlowControl class converts the functions added by the user to the model and the fault information into corresponding data structures for algorithm calls. The response events of the software main interface menu and buttons are stored in the drawFlowGroup class, and different functions are implemented by calling the functions stored in this class respectively. The interface display of the testability results is also implemented in this class.

[0074] S150. When setting the testability information of the model, based on the graphic drawing program, component library, and data structure, set the test information.

[0075] In some embodiments, first, based on the node attributes or connection attributes in the component library, determine the input of the functions and fault information of the hybrid diagnostic model.

[0076] Then, based on the input of the functions and fault information of the hybrid diagnostic model, add or update the input information to the variables of the nodes or connections in the component library.

[0077] Finally, based on the input of the test information of the hybrid diagnostic model, read the selected graphic as the test point component, and add a test set and test information to this graphic.

[0078] In this embodiment, when setting the testability information of the model, the user realizes the input of the model functions and fault information through the component attribute setting panel at the bottom of the software, including reliability data, fault modes, functions, etc. The information input by the user will be added or updated to the variables of the corresponding Node class object of this component, becoming the data source for a series of subsequent algorithms. The test information setting is similar to the addition of testability information for each module. When the user inputs the test attributes, the program will read the currently selected component as the test point, add a test set and test information to the instance of its Node class, and provide data for the generation of the correlation matrix.

[0079] The variables currently in the Node class or Line class object need to be converted into a table of the same format to facilitate the reading of the underlying algorithm. There are two solutions for the interaction of data between the algorithm and the modeling interface. One is to save and read excel files. It is necessary to reference Microsoft.Office.Interop.Exeel to read and write excel spreadsheet files, instantiate Application, Workbook and WorkSheet respectively, create a new excel process, file and new worksheet, and write the data content into the file in sequence. The other is to pass directly in the form of DataSet data table. Using the System.Data reference in the ADO.NET component library, you can operate the database to establish a DataSet as a temporary database. Adding a temporary data table DataTable is the same as the form of excel table. The advantage of the first solution is that users can view the model data at any time through the saved excel, but the time required to read and write excel files is in seconds. If there are multiple levels in the model, the number of excel files that need to be read and written will increase, which will greatly increase the running time of the software. Therefore, in this system, data tables are directly used for transmission.

[0080] Each data table stores model information such as Figure 3 As shown in the figure, through this information, the structural modeling and functional modeling of the graphics can be clearly described. The structural information table saves the information of the components and ports in the model. The program reads the components in sequence and associates the port-related information with the components to which they belong.

[0081] The modeling method provided by the present invention, in order to determine the data structure between the components to be modeled, needs to firstly analyze the principle of the hybrid diagnostic model to be modeled, and then, based on the structure of each component to be modeled, define the component library, so that the properties of nodes, lines and each graph can be defined. Then, based on the component library, write a graphics drawing program, and then, convert the function and fault information of the hybrid diagnostic model into a data structure corresponding to the preset algorithm, and finally, when setting the model test information, set the test information based on the graphics drawing program, the component library and the data structure. The modeling method provided by the present invention first defines the component library, and writes the graphics drawing program based on the component library, so that the hybrid diagnostic model to be modeled can be quickly modeled. In addition, by converting the function and fault information of the hybrid diagnostic model into a data structure corresponding to the preset algorithm, the data structure conversion of the hybrid diagnostic model can be realized, and finally, the test information can be set based on the graphics drawing program, the component library and the data structure, so that the speed of modeling can be greatly improved and rapid modeling can be achieved.

[0082] It should be understood that the sequence numbers of the steps in the above embodiments do not indicate the order of execution. The order of execution of each process should be determined according to its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

[0083] Based on the modeling method for testability analysis provided in the above embodiments, correspondingly, the present invention also provides a specific implementation manner of a testability analysis modeling device applied to the modeling method for testability analysis. Please refer to the following embodiments.

[0084] As Figure 4 shown, a testability analysis modeling device 400 is provided, and the device includes:

[0085] An analysis module 410, configured to perform a principle analysis on the hybrid diagnostic model to be modeled, and determine the structures of the components to be modeled;

[0086] A definition module 420, configured to define a component library based on the structures of the components to be modeled, where the component library includes nodes, connections, and images, as well as the node attributes of each node, the connection attributes of each connection, and the graphic attributes of each graphic;

[0087] A writing module 430, configured to write a graphic drawing program based on the component library;

[0088] A conversion module 440, configured to convert the functions and fault information of the hybrid diagnostic model into a data structure corresponding to a preset algorithm;

[0089] A setting module 450, configured to perform test information setting based on the graphic drawing program, the component library, and the data structure when performing model testability information setting.

[0090] In a possible implementation manner, the setting module 450 is configured to determine the input of the functions and fault information of the hybrid diagnostic model based on the node attributes or connection attributes in the component library;

[0091] Based on the input of the functions and fault information of the hybrid diagnostic model, add or update the input information to the variables of the nodes or connections in the component library;

[0092] Based on the input of the test information of the hybrid diagnostic model, read the selected graphic as a test point component, and add a test set and test information to the graphic.

[0093] In a possible implementation manner, the node attributes and connection attributes need to be converted into a table form of the same format;

[0094] The setting module 450 is configured to perform the conversion based on the form of saving and reading an excel file; or

[0095] Transmitted in the form of a DataSet data table.

[0096] In a possible implementation, a writing module 430 is used to add a System Drawing reference. When the graphics drawing program is initialized, multiple Graphics class objects are created based on Bimap and Image objects;

[0097] A variety of button controls are placed in the component library. When different button controls are clicked, the class object corresponding to the button control is called; among them, one button control corresponds to one Graphics class object;

[0098] Different graphics are drawn based on the GDI methods of different Graphics class objects.

[0099] In a possible implementation, the basic attributes of each node include graphic attributes, connection attributes, component attributes, failure modes, failure impacts, and test information;

[0100] Graphic attributes are used to define the name, appearance, type, and port information of the target node object;

[0101] Connection attributes are used to define the serial number of the target node in the node list, the numbers of other nodes connected to the ports of this node, and the number of wires contained in this node

[0102] Component attributes are used to define the repair or replacement cost, time, and failure rate after the component fails;

[0103] Failure modes are used to define the failure modes and failure mode frequency ratios of the target node;

[0104] Failure impacts are used to define the failure impacts and severities of the components;

[0105] Test information is used to define the test name, the test set to which it belongs, and the type of the test of the target node.

[0106] In a possible implementation, the basic attributes of each wire include graphic attributes, wire sequence attributes, connected component attributes, and connected component port attributes;

[0107] Graphic attributes are used to define the position, appearance, color, and style of the wire;

[0108] Wire sequence attributes are used to define the serial number of the wire in the entire wire list;

[0109] Connected component attributes are used to define the nodes connected by the start and end points of the wire.

[0110] In a possible implementation, the modeling of each graphic is implemented based on the drawObject class.

[0111] Figure 5 is a schematic diagram of an electronic device provided by an embodiment of the present invention. As Figure 5 shown, the electronic device 5 of this embodiment includes: a processor 50, a memory 51, and a computer program 52 stored in the memory 51 and executable on the processor 50. When the processor 50 executes the computer program 52, it implements the steps in the above-mentioned modeling method embodiments of various testability analyses, such as Figure 1 the steps 110 to 150 shown. Alternatively, when the processor 50 executes the computer program 52, it implements the functions of each module in the above-mentioned device embodiments, such as Figure 4 the functions of the modules 410 to 450 shown.

[0112] Exemplarily, the computer program 52 can be divided into one or more modules. The one or more modules are stored in the memory 51 and executed by the processor 50 to complete the present invention. The one or more modules can be a series of computer program instruction segments capable of performing specific functions, and these instruction segments are used to describe the execution process of the computer program 52 in the electronic device 5. For example, the computer program 52 can be divided into Figure 4 the modules 410 to 450 shown.

[0113] The electronic device 5 may include, but is not limited to, a processor 50 and a memory 51. Those skilled in the art can understand that Figure 5 this is only an example of the electronic device 5 and does not constitute a limitation on the electronic device 5. It may include more or fewer components than shown in the figure, or combine certain components, or different components. For example, the electronic device may further include input / output devices, network access devices, buses, etc.

[0114] The so-called processor 50 may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), 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 also be any conventional processor, etc.

[0115] The memory 51 may be an internal storage unit of the electronic device 5, such as a hard disk or memory of the electronic device 5. The memory 51 may also be an external storage device of the electronic device 5, such as a plug-in hard disk equipped on the electronic device 5, a Smart Media Card (SMC), a Secure Digital (SD) card, a Flash Card, etc. Further, the memory 51 may also include both an internal storage unit and an external storage device of the electronic device 5. The memory 51 is used to store the computer program and other programs and data required by the electronic device. The memory 51 may also be used to temporarily store data that has been output or is to be output.

[0116] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the above division of each functional unit and module is used as an example. In practical applications, the above functions can be assigned to different functional units and modules according to needs, that is, the internal structure of the device is divided into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiment can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. In addition, the specific names of each functional unit and module are only for the convenience of mutual distinction and do not limit the protection scope of this application. The specific working process of the units and modules in the above system can refer to the corresponding process in the foregoing method embodiment and will not be elaborated here.

[0117] In the above embodiments, the descriptions of the respective embodiments have their own emphases. For parts not detailed or recorded in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0118] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or by a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. A professional technician can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present invention.

[0119] In the embodiments provided by the present invention, it should be understood that the disclosed device / electronic device and method can be implemented in other ways. For example, the device / electronic device embodiments described above are merely illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the device or unit can be in electrical, mechanical or other forms.

[0120] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0121] In addition, in each embodiment of the present invention, the functional units can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above integrated units can be implemented in the form of hardware or in the form of software functional units.

[0122] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, to implement all or part of the processes in the above embodiment methods of the present invention, it can also be completed by a computer program instructing relevant hardware. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, the steps of the above-mentioned modeling methods of each testability analysis embodiment can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in the form of source code, object code, executable file or some intermediate form, etc. The computer-readable medium can include: any entity or device that can carry the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disc, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, and software distribution medium, etc.

[0123] The above-described embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A modeling method for testability analysis, characterized in that Including: Conduct a principle analysis on the hybrid diagnostic model to be modeled, and determine the structures of the components to be modeled; Define a component library based on the structures of the components to be modeled, where the component library includes nodes, connections, and images, as well as the node attributes of each node, the connection attributes of each connection, and the graphic attributes of each graphic; Write a graphic drawing program based on the component library; Convert the functions and fault information of the hybrid diagnostic model into the data structures corresponding to the preset algorithms; When setting the testability information of the model, based on the graphic drawing program, the component library, and the data structures, set the test information.

2. The modeling method for testability analysis according to claim 1, wherein The step of when setting the testability information of the model, based on the graphic drawing program, the component library, and the data structures, setting the test information includes: Based on the node attributes or connection attributes in the component library, determine the inputs of the functions and fault information of the hybrid diagnostic model; Based on the inputs of the functions and fault information of the hybrid diagnostic model, add or update the input information to the variables of the nodes or connections in the component library; Based on the input of the test information of the hybrid diagnostic model, read the selected graphic as a test point component, and add a test set and test information to this graphic.

3. The modeling method for testability analysis according to claim 2, wherein The node attributes and the connection attributes need to be converted into a table form of the same format, and the conversion methods include: Converting based on the form of saving and reading excel files; or Transmitting through the form of a DataSet data table.

4. The modeling method for testability analysis according to claim 1, wherein The step of writing a graphic drawing program based on the component library includes: Add a System Drawing reference. When initializing the graphic drawing program, create multiple Graphics class objects based on Bimap and Image objects; Place various button controls in the component library. When different button controls are clicked, call the class objects corresponding to the button controls; among them, one button control corresponds to one Graphics class object; Draw different graphics based on the GDI methods of different Graphics class objects.

5. The modeling method for testability analysis according to any one of claims 1-4, characterized in that, The basic attributes of each node include graphic attributes, connection attributes, component attributes, fault modes, fault impacts, and test information; The graphic attributes are used to define the name, appearance, type, and port information of the target node object; The connection attributes are used to define the serial number of the target node in the node list, as well as the numbers of other nodes connected to the ports of this node and the number of connections included in this node; The component attributes are used to define the repair or replacement cost, time, and failure rate after the component fails; The fault modes are used to define the fault modes and the frequency ratios of the fault modes of the target node; The fault impacts are used to define the fault impacts and severities of the components; The test information is used to define the test name, the test set to which it belongs, and the type of the test of the target node.

6. The modeling method for testability analysis according to any one of claims 1-4, characterized in that, The basic attributes of each connection include graphic attributes, line sequence attributes, the component attributes of the connections, and the component port attributes of the connections; The graphic attributes are used to define the position, appearance, color, and style of the connection; The line sequence attributes are used to define the serial number of the connection in the entire line list; The component attributes of the connections are used to define the nodes connected by the start and end points of the connection.

7. The modeling method for testability analysis according to any one of claims 1-4, characterized in that, The modeling of each of the said graphics is implemented based on the drawObject class.

8. A modeling device for testability analysis, characterized in that It includes: An analysis module, which is used to conduct a principle analysis on the hybrid diagnostic model to be modeled and determine the structures of the components to be modeled. A definition module, which is used to define a component library based on the structures of the components to be modeled. Among them, the component library includes nodes, connections, and images, as well as the node attributes of each node, the connection attributes of each connection, and the graphic attributes of each graphic. A programming module, which is used to write a graphic drawing program based on the component library. A conversion module, which is used to convert the functions and fault information of the hybrid diagnostic model into the data structure corresponding to the preset algorithm. A setting module, which is used to set the test information based on the graphic drawing program, the component library, and the data structure when setting the model testability information.

9. An electronic device, characterized in that, It includes a memory and a processor. The memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to execute the method according to any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it realizes the steps of the method according to any one of claims 1 to 7.

Images