Model construction method and device, computer device, and storage medium

Abstract

The application relates to a model construction method and device, computer equipment, a storage medium and a computer program product. The method comprises the following steps: acquiring a system function design model; acquiring an element correspondence relationship between a design model modeling element in the system function design model and a fault model element of a corresponding fault transmission model; analyzing the system function design model into preset language format data, and performing element conversion on the design model modeling element in the system function design model according to the element correspondence relationship to obtain the corresponding fault transmission model. The method can improve the testability modeling efficiency.

Description

Technical Field

[0001] This application relates to the field of equipment failure testing technology, and in particular to a model building method, apparatus, computer equipment, storage medium and computer program product. Background Technology

[0002] With the development of equipment failure testing technology, the integration and complexity of equipment have increased significantly, and the probability of equipment failure has also increased. As a result, model building technology has emerged, which automatically troubleshoots failures based on the constructed testable models, thereby improving the testability of equipment.

[0003] In traditional techniques, testability models include various types such as signal flow graph models, multi-signal flow graph models, and fault propagation models. Fault propagation models are a type of testability model, but they can also be used for reliability analysis. When building a testability model, the most widely used approach is to use a multi-signal flow graph model as the core, analyzing the fault-test correlation matrix for testability analysis. This approach first extracts relevant information for testability modeling through analysis of the system structure and functions, and then establishes the system's multi-signal flow graph model.

[0004] However, in traditional methods, the fault propagation model is entirely constructed by the test designer or general quality characteristic designer, and lacks connection with the previously established system functional design model (the system functional design model is another major category of models that is different from the test model and the fault propagation model). It is difficult to maintain consistency in the model and model-related parameters, and the standardization is poor. This results in high repetition and low efficiency of test modeling and analysis work during the design iteration of the entire life cycle of the test system. Summary of the Invention

[0005] Therefore, it is necessary to provide a model building method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can improve the efficiency of testable modeling in response to the above-mentioned technical problems.

[0006] Firstly, this application provides a model construction method. The method includes:

[0007] Obtain the system functional design model;

[0008] Obtain the element correspondence between the design model modeling elements in the system functional design model and the fault model elements in the corresponding fault transmission model;

[0009] The system functional design model is parsed into preset language format data, and the design model modeling elements in the system functional design model are transformed according to the element correspondence to obtain the corresponding fault transmission model.

[0010] Secondly, this application also provides a model building apparatus. The apparatus includes:

[0011] The design model acquisition module is used to acquire the system functional design model;

[0012] The correspondence acquisition module is used to acquire the element correspondence between the design model modeling elements in the system functional design model and the fault model elements in the corresponding fault transmission model;

[0013] The transmission model generation module is used to parse the system functional design model into data in a preset language format, and to perform element transformation on the design model modeling elements in the system functional design model according to the element correspondence relationship to obtain the corresponding fault transmission model.

[0014] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0015] Obtain the system functional design model;

[0016] Obtain the element correspondence between the design model modeling elements in the system functional design model and the fault model elements in the corresponding fault transmission model;

[0017] The system functional design model is parsed into preset language format data, and the design model modeling elements in the system functional design model are transformed according to the element correspondence to obtain the corresponding fault transmission model.

[0018] The aforementioned model construction method, apparatus, computer equipment, storage medium, and computer program product enable the terminal to acquire the system functional design model and its element correspondences. The system functional design model is then parsed into data in a preset language format. This preset language format data is a low-level data linking the design model's modeling elements to fault model elements. Based on the element correspondence between the design model's modeling elements in the system functional design model and the fault model elements in the fault propagation model, the design model's modeling elements are transformed into corresponding fault model elements, thereby obtaining the corresponding fault propagation model. Since the fault propagation model is constructed with the system functional design model as a reference and through data transformation, a connection is established between the fault propagation model and the system functional design model. This improves standardization, reduces repetitive analysis work during the entire lifecycle design iteration of the test system, and increases the efficiency of testable modeling. Attached Figure Description

[0019] Figure 1 This is a flowchart illustrating a model building method in one embodiment;

[0020] Figure 2 This is a Harmony-SE system design and modeling method in one embodiment;

[0021] Figure 3 This is a view architecture for the SysML language in one embodiment;

[0022] Figure 4 This is a fault propagation model framework constructed within a local unit of the system in one embodiment;

[0023] Figure 5 This is a second correspondence diagram between modeling elements and system information in one embodiment;

[0024] Figure 6 This is a third correspondence diagram between underlying model elements and fault model elements in one embodiment;

[0025] Figure 7 This is a schematic diagram illustrating the system fault state transition and fault propagation in one embodiment;

[0026] Figure 8 This is a flowchart illustrating the model building method in another embodiment;

[0027] Figure 9 This is a data conversion relationship diagram between the system functional design model and the fault propagation model in one embodiment;

[0028] Figure 10 Export the system function design model for one embodiment as an XMI file;

[0029] Figure 11 This is a schematic diagram of the storage format of a "module" in the system functional design model of one embodiment in an XMI file;

[0030] Figure 12 This is a schematic diagram of the storage format of "connections" in the system functional design model of one embodiment in an XMI file;

[0031] Figure 13 This is a schematic diagram of the storage format of "components" in the system functional design model of one embodiment in an XMI file;

[0032] Figure 14 This is a schematic diagram illustrating the conversion of a system functional design model into a fault propagation model in one embodiment;

[0033] Figure 15 This is a schematic diagram illustrating the manual analysis and refinement of a fault propagation model in one embodiment.

[0034] Figure 16This is a flowchart illustrating an automatic correlation matrix generation method in one embodiment;

[0035] Figure 17 This is a structural block diagram of the model building apparatus in one embodiment;

[0036] Figure 18 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0037] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0038] The model building method provided in this application can be applied to a terminal. The terminal's memory can store element correspondences and other related data. The terminal also has modeling software installed, including TEAMS software. In one embodiment, the terminal can build a model using TEAMS software, which is a testable modeling and analysis software. During the construction of the fault transmission model, the terminal can import files to obtain the system functional design model and the element correspondence between the design model elements in the system functional design model and the corresponding fault model elements in the fault transmission model. The system functional design model is then parsed into a preset language format, and the design model elements in the system functional design model are transformed according to the element correspondences to obtain the corresponding fault transmission model. The system functional design model is a model describing system functions; it is a graphical model. The design model elements are the constituent elements of the system functional design model and are graphical. Because the design model elements of the system functional design model are graphical, the resulting fault transmission model is also a graphical model.

[0039] This method is applicable to equipment testing, which is an important characteristic that facilitates testing and diagnosis. It runs through the entire life cycle of equipment, including demonstration, design, production, and use, and has a significant impact on improving equipment maintainability, enhancing availability, and increasing mission reliability.

[0040] The terminal can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc. Portable wearable devices can include smartwatches, smart bracelets, head-mounted devices, etc.

[0041] In one embodiment, such as Figure 1As shown, a model building method is provided, which can be applied to... Figure 1 Taking the terminal in the example, the explanation includes the following steps:

[0042] Step 202: Obtain the system functional design model.

[0043] Among them, the system function design model is a model that describes the system function, and it is a graphical model.

[0044] Specifically, the construction of system functional design models generally follows a modeling process driven by requirements, transforming functional analysis and design synthesis into a system logical architecture. In one embodiment, the system functional design model of this application can be obtained using the Harmony-SE system design modeling method. Figure 3 illustrates one example of the Harmony-SE system design modeling method.

[0045] The specific process can be divided into the following three steps:

[0046] (1) Requirements definition: Using the top-level indicators of the system obtained from the system requirements demonstration and the typical combat scenarios of the equipment as input, define the system requirements items and the task scenario model. At the same time, by identifying the functional requirements in each task process of the system, the system requirements are assigned to the corresponding use cases to form a system requirements graph model.

[0047] (2) Functional Analysis: Starting from the typical task scenarios of the system, through functional analysis and refinement of the task execution process, a system task scenario activity diagram and the relationship between the timing of each activity are formed. At the same time, the state transitions that occur in the system during the activities are analyzed, and a system state transition diagram is established. Based on the system functional model formed at this stage, the conflict between the system state behavior and the timing correspondence can be analyzed and verified.

[0048] (3) Design specific physical architectures to implement the system functions determined in the functional analysis phase. Each system function will be assigned to one or more physical architectures for implementation. At the same time, the logical relationships between system architectures can be determined according to the order in which the functions occur and their correlation, thereby establishing a logical architecture view of the system.

[0049] Step 204: Obtain the element correspondence between the design model modeling elements in the system functional design model and the fault model elements in the corresponding fault transmission model.

[0050] The design model elements are the components of the system functional design model and can be presented graphically. The fault propagation model is a fault correlation model constructed based on the fault correlation relationships between various components or units of the system, and fault location analysis can be performed using relevant testing methods. Fault model elements are the components of the fault propagation model and can be understood as the parts that constitute the fault propagation model. In one embodiment, the correspondence between the system functional design model elements and the elements in the fault propagation model is shown in Table 1:

[0051] Table 1. Correspondence between underlying model elements and design model elements.

[0052]

[0053] Table 1 shows the correspondence between the elements in the system functional design model and the fault propagation model, determined by the functions or properties of the elements in the fault propagation model and the system functional design model. In Table 1, state variables correspond to attributes, interaction variables correspond to ports, project flows, and object flows, while trigger times do not have corresponding system functional design model elements. In one embodiment, this correspondence includes a transformation relationship between the design model elements of the system functional design model and the fault modeling elements of the fault propagation model.

[0054] Step 206: Parse the system functional design model into preset language format data, and perform element transformation on the design model modeling elements in the system functional design model according to the element correspondence to obtain the corresponding fault transmission model.

[0055] The system functional design model was built using the SysML language, a system modeling language developed by the International Committee on Engineering in Systems (INCOSE) in conjunction with the Object Management Group (OMG) based on the Unified Modeling Language (UML), suitable for describing engineering systems. SysML uses three categories and nine types of views (as shown in Figure 4) to formally represent the system's requirements, behavior, structure, parameters, and other elements. SysML is applicable to various activities related to the specification, analysis, design, verification, and validation of systems and between systems. These systems may include hardware, software, information, processes, personnel, and facilities. By unifying and standardizing formal model elements, the differences in expression between different modeling methods are eliminated, facilitating communication among designers and avoiding inconsistencies and confusion in information exchange.

[0056] Preset language format data is an intermediate format used in data conversion. Parsing the system functional design model into preset language format data can be understood as reading the graphical modeling elements—design modeling elements—of the system functional design model and parsing them into a low-level data layer as a transition. In one embodiment, the system functional design model can be converted using XMI technology, and the corresponding preset language format data is XMI format data.

[0057] After obtaining the preset language format data, it is converted according to the element correspondence to convert the preset language format data into the corresponding fault model elements, thus obtaining the fault transmission model.

[0058] In the aforementioned model construction method, the terminal acquires the system functional design model and its element correspondences, parses the system functional design model into data in a preset language format, and this preset language format data is a low-level data linking the fault model elements of the design model. Based on the element correspondence between the design model elements in the system functional design model and the fault model elements in the fault propagation model, the design model elements are transformed into corresponding fault model elements, thereby obtaining the corresponding fault propagation model. Since the fault propagation model is constructed with the system functional design model as a reference and through data transformation, a connection is established between the fault propagation model and the system functional design model. This improves standardization, reduces repetitive analysis work during the entire lifecycle design iteration of the test system, and improves the efficiency of testable modeling.

[0059] For step S204, in one embodiment, it may be to directly obtain the element correspondence between the design model modeling elements in the preset system function design model and the fault model elements in the corresponding fault transmission model.

[0060] The element correspondence between the design model modeling elements in the system functional design model and the fault model elements in the corresponding fault transmission model can be pre-stored in the terminal, and can be directly loaded and run when the fault transmission model needs to be built.

[0061] In another embodiment, step S204 may involve obtaining a first correspondence between the underlying model elements of the fault propagation model and the modeling data requirements, a second correspondence between the design model modeling elements of the system functional design model and the system information, and a third correspondence between the underlying model elements and the fault model elements; determining the correspondence between the underlying model elements and the design model modeling elements based on the degree of matching between each modeling data requirement and the system information; and obtaining the element correspondence between the design model modeling elements in the system functional design model and the fault model elements of the corresponding fault propagation model.

[0062] In one embodiment, the fault propagation model framework built within a local unit of the system is as follows: Figure 4 As shown, on the one hand, within the local components of the system constructed using the SysML language, the system's state variables (normal functional state and failure state) and the triggering events for state transitions are defined to describe the occurrence of a fault in a local unit and the series of transitions from a fault state to a normal state. On the other hand, logic gates (AND, OR, voting, etc.) are used to associate the system state with the input and output variables of the system unit, representing the propagation relationship after a system unit fault occurs. This two-pronged fault propagation modeling can comprehensively represent a series of fault propagation and dynamic failure control behaviors after a system fault occurs.

[0063] The underlying model elements are the fault propagation model represented in mathematical logic. Specifically, the underlying model elements in the fault propagation model include classes, states, events, flow variables, fault state transitions, assertions, sub-modules, and embeddings.

[0064] In this context, the module is the basic unit of the fault propagation model, used to characterize the structural composition of the system.

[0065] State is one of the core elements of fault propagation models, used to define the normal and failure states of system modules in the fault propagation model, i.e., the failure modes of system modules. State is a fundamental element in the dynamic and static modeling of system faults.

[0066] Events trigger system state transitions and are the conditions that initiate dynamic system behavior. Event types can include external events of system modules (such as fault reporting signals and redundancy switching signals), their own behaviors (such as function switching and fault events), and common-cause events. Redundancy switching signals can be used to send a start signal to the corresponding backup device after a primary device failure, initiating a redundancy switch from the primary device to the backup device. Common-cause events refer to events that simultaneously cause state transitions in multiple modules within the system. These can be triggering events for multiple simultaneous faults (such as fires or power outages) or triggering events for multiple fault states to simultaneously transition back to a normal state (such as replacing the entire device, causing multiple components within the device to be repaired to like-new condition).

[0067] Interactive variables include the input (i) and output (o) variables of the basic components of the system. Interactive variables serve as a bridge for data exchange between this module and other modules, and also as a link for fault propagation.

[0068] Fault state transitions are one of the core fault relationships in fault propagation models, used to describe the transition process between the normal and failed states of a system. Each transition is a process that includes a triggering event. Conversion conditions and state assignment operation Three-part triplet Its definition is When the event Trigger and change conditions State assignment operation is performed when the system is established. This is done to change the value of state variables. State transitions are used not only to define the failure process of a system (the process of transitioning from a normal state to a failure state), but also to define transition processes such as fault signal reporting, redundancy switching, module function switching, and queuing for maintenance, depending on the actual failure process of the system unit. Among them, redundancy switching mainly describes the backup device startup process triggered after the primary device fails, which transitions the backup device module from a bypass state to a normal operating state.

[0069] Fault propagation is one of the core fault relationships in the fault propagation model. It describes the relationship between output interaction variables and state variables, as well as input interaction variables. Its basic form is: Where S is the state variable, i is the input variable state, and o is the output variable state. Fault propagation relationships have two main uses: ① to connect two modules, ensuring data transmission between them; ② to define fault propagation relationships within a module by defining the relationship between stream variables and state variables.

[0070] Fault propagation relationships can be further categorized into in-out, in-in, and out-out fault propagation relationships based on the type of connected modules. An in-out fault propagation relationship defines the relationship between output stream variables and state variables and input stream variables within the same module; an in-in fault propagation relationship defines the relationship between input stream variables of an upper-level module and input stream variables of a lower-level module; and an out-out fault propagation relationship defines the relationship between output stream variables of a lower-level module and output stream variables of an upper-level module.

[0071] Submodules describe the hierarchical structure within a module. Submodules are declared by instantiating a module class. The module class refers to the module's `class`. Instantiating a module class means declaring and defining submodules within a selected module class, starting with "sub". For example:

[0072] class block A

[0073] sub a1, a2

[0074] That is, a1 and a2 are defined as submodules of block A.

[0075] Nesting is used to describe a module that is nested within another module, where the inner module is part of the outer module.

[0076] To facilitate designers' understanding and modeling, the fault propagation model, like SysML (System Modeling Language), provides a graphical element modeling method. All formal model elements have corresponding graphical elements, and the modeling process can be completed simply by selecting the appropriate graphical element.

[0077] In one embodiment, the first correspondence between the underlying model elements of the fault propagation model and the modeling data requirements is shown in Table 2:

[0078] Table 2. First Correspondence Between Underlying Model Elements and Modeling Data Requirements

[0079]

[0080] In one embodiment, the underlying model elements include at least a first basic module, a second basic module with sub-modules, state variables, triggering events, fault state transitions, and fault propagation relationships. The first basic module is the basic module in Table 2, and the second basic module with sub-modules is the module with sub-modules in Table 2. The underlying model elements also include interaction variables and sub-modules contained within the module.

[0081] In one embodiment, the second correspondence between the design modeling elements of the system functional design model and the system information is as follows: Figure 5 As shown. System information includes at least modules, components, attributes, and triggering events, as well as ports, connections, project flows, operations, call behaviors, control flows, object flows, derived nodes, connection nodes, decision nodes, and merge nodes.

[0082] like Figure 6 The fault propagation model adopts a formal modeling approach similar to SysML, enabling formal reasoning and analysis of the propagation logic between faults based on the mathematical logic inherent in the formal modeling language itself, greatly improving design analysis efficiency. Simultaneously, the similarity between the models facilitates the consistency between the fault model and the SysML model, laying the foundation for subsequently extracting system functional information from the SysML model to construct the fault model.

[0083] Based on the above formal modeling method, a complete representation of the series of fault propagation and dynamic failure control behaviors after a system failure occurs can be obtained. In one embodiment, a schematic diagram of the system failure state transition and fault propagation is shown below. Figure 7As shown: First, when a fault event triggers a system unit, the system transitions from a normal state to a failed state. After a fault occurs within the system module itself, the state of the module's output stream variables changes according to the fault propagation relationships defined within the module. Finally, the fault is propagated to connected modules according to the fault propagation relationships defined between modules. When the system module returns to a normal state with the intervention of a maintenance event, a series of modules associated with the system module's state will also return to their normal operating state.

[0084] All system state transition processes can be derived from mathematical logic under the definition of formal language. By writing the deduction rules into a computer, the automatic analysis and calculation of the system failure propagation process can be realized.

[0085] In this specific embodiment, the modeling data requirements are a characteristic description of the data needed for the fault transmission model. Based on the modeling data requirements, the types of data required to construct the fault transmission model can be determined. System information is a characteristic description of the corresponding data obtained from the comprehensive analysis of various design model modeling elements in the system functional design model. The element correspondence can also be generated in real time. Specifically, the terminal first obtains the first correspondence between the underlying model elements of the fault transmission model and the modeling data requirements, the second correspondence between the design model modeling elements of the system functional design model and the system information, and the third correspondence between the underlying model elements and the fault model elements. The first and second correspondences can be stored as files on the terminal's hard drive or imported into the modeling software as files via USB flash drive. After obtaining the first and second correspondences, based on the matching degree between the modeling data requirements in the first correspondence and the system information in the second correspondence, the element correspondence between the underlying model elements and the design model modeling elements is determined. The higher the matching degree between each modeling data requirement and the system information, the greater the likelihood of a correspondence between the underlying model elements and the design model modeling elements. In one embodiment, the degree of matching between each modeling data requirement and the system information can be identified through semantic analysis, and a correspondence can be established between each modeling data requirement with a similarity greater than a threshold in the analysis results and the system information.

[0086] In this embodiment, by acquiring the first and second correspondences in real time, and based on the degree of matching between each modeling data requirement and system information, the element correspondence between the underlying model elements and the design model modeling elements can be determined. Based on the acquired third correspondence, the element correspondence between the fault model elements of the fault transmission model and the design model modeling elements can be determined.

[0087] In one embodiment, the correspondence between the underlying model elements and the design model modeling elements is determined based on the degree of matching between each modeling data requirement and the system information. This includes: analyzing the key fields of the system information and the modeling data requirements, setting the correspondence between each system information and the modeling data requirements that are completely matched as a complete mapping, setting the correspondence between each system information and the modeling data requirements that are not completely matched as a partial mapping, and setting the correspondence between each system information and the modeling data requirements that are completely unmatched as non-mapping.

[0088] Key fields refer to crucial information describing system information or modeling data requirements. System information and modeling data requirements each have their own key fields. The element correspondence between the underlying model elements and the design model modeling elements is shown in Table 1 above. Based on the key field analysis results, when the modeling data requirement in the fault transmission model can find completely corresponding system information in the system functional design model, it indicates a complete correspondence, and the correspondence between the modeling data requirement and its corresponding system information can be set to complete mapping. When the modeling data requirement in the fault transmission model can find corresponding but not completely corresponding system information in the system functional design model, it indicates a partial correspondence and partial non-correspondence, and the correspondence between the modeling data requirement and its corresponding system information can be set to partial mapping. When the modeling data requirement in the fault transmission model cannot find any corresponding system information in the system functional design model, it indicates a complete non-correspondence, and the correspondence between the modeling data requirement and its corresponding system information can be set to non-mapping.

[0089] When the mapping is complete, during data transformation and fault propagation model generation, the design model elements corresponding to the system information can be completely mapped to the corresponding fault model elements. When the mapping is partial, during data transformation and fault propagation model generation, only some of the design model elements corresponding to the system information can be mapped to the corresponding fault model elements. When the mapping is non-mapping, during data transformation and fault propagation model generation, the design model elements corresponding to the system information cannot be mapped to the corresponding fault model elements.

[0090] In this embodiment, by analyzing the key fields of each system information and modeling data requirements, and based on the matching and correspondence between the two, appropriate correspondences can be set for the underlying model elements and the design model modeling elements.

[0091] In one embodiment, step S206 above involves converting the design model modeling elements in the system functional design model according to the element correspondence relationship to obtain the corresponding fault transmission model. This includes: during the conversion of the design model modeling elements in the system functional design model according to the element correspondence relationship, mapping the design model modeling elements to the corresponding underlying model elements of the fault transmission model based on the determined correspondence between various underlying model elements and graphical elements of the fault transmission model, and then representing the mapped underlying model elements with the corresponding graphical fault model elements.

[0092] In the process of element conversion, the terminal determines which underlying model element to map the design model modeling element to according to the element correspondence relationship, and represents the mapped underlying model element with the corresponding fault model element according to the third correspondence relationship between the underlying model element and the fault model element, thereby obtaining a graphical representation of the fault transmission model.

[0093] In this embodiment, by mapping the design modeling elements to the corresponding underlying model elements of the fault propagation model according to the correspondence of the elements, the mapped underlying model elements are represented by the corresponding graphical fault model elements, thereby obtaining a graphical fault propagation model, which unifies the modeling specifications of the fault propagation model and the system functional design model.

[0094] In one embodiment, the model building method, such as Figure 8 As shown, it consists of three steps:

[0095] (1) Organize the system functional characteristic design information required to construct a complete fault transmission model, and determine the system functional design model objects to be analyzed, the system design information to be extracted, the system structure composition, and other information. Through analysis, determine the information to be extracted from the system functional design model, including basic system component information, hierarchical relationships between components, system state types, interactive data between system units, system state transition processes, and functional logical relationships between system units. For example... Figure 8 As shown, when the modeling data requirement in the fault propagation model is a basic module, the corresponding system information in the system functional design model is the information of the basic system components and the hierarchical relationship between the components. When the modeling data requirement is a state variable, the corresponding system information is the system state type. When the modeling data requirement is an interaction variable, the corresponding system information is the interaction data between system units. When the modeling data requirement is a triggering event, the corresponding system information is the system state transition process. When the modeling data requirement is a transitive relationship, the corresponding system information is the functional logic relationship between system functional units.

[0096] (2) Analyze the elements of the system functional design model and the fault transmission model, determine the elements of the system functional design model and the organizational relationships between the elements, and establish a data conversion relationship diagram between the system functional design model and the fault transmission model, such as... Figure 9 As shown, the SysML model is a system functional design model built using the SysML modeling language. Figure 9 The leftmost diagram shows a portion of the system functional design model when using the SysML modeling language. In the XML model element diagram, the `package` represents a data package containing data corresponding to various design model elements of the system functional design model. Here, `class` represents a module, `port` represents a port, `property` represents an attribute, and `connector` represents a connection. In the fault propagation model element, the `package` refers to the data package of the fault propagation model, `class` represents a module, `flow` represents the interaction variable, `state` represents the state variable, and `transition` represents the state transition. Other elements are similarly defined. Combining the above element correspondences, information is extracted sequentially according to SysML syntax to generate the corresponding fault propagation model elements, establishing a mapping relationship between the two models, and extracting general quality characteristic information such as embedded objects, fault logic, unit composition, and relationship information.

[0097] (3) Parse the data of the system functional design model using XMI technology. In one embodiment, the various model views of the system functional design model are converted to obtain XMI intermediate files, the system functional design model is converted into XMI intermediate data format, and the XMI format data parsing algorithm is implemented using a computer programming language according to the XMI data format specification provided by the Object Management Group (OMG) to extract the data that needs to be used for general quality characteristics work.

[0098] Regarding the model analysis in step S206 above, in one embodiment, the system functional design model is exported as an XMI file, and the corresponding modeling data requirements are extracted from the XMI file to obtain the converted fault transmission model.

[0099] Specifically, commercial MBSE modeling tools all provide interfaces for exporting system functional design models into XMI / XML format files. By analyzing and exporting the model data that needs to be converted into XMI, input can be provided for generating a fault transmission model. The system functional design model can be exported as an XMI file as follows: Figure 10As shown, (a) is an XMI file exported from Rhapsody software, and (b) is an XML file exported from Magicdraw software.

[0100] Parse the system functional design model data and extract the corresponding modeling data requirements from the XMI file. Based on the formal syntax of the system functional design model, locate the corresponding model elements and their relationships within the XMI file. In one embodiment, such as... Figures 11-13 As shown, the system functional design model stored in the XMI file is presented in terms of "modules," "connections," and "components and attributes." Specifically, Figure 11 In the configuration, the module class ID (id) and the module name (name) are set to Distiller. Figure 12 In the configuration, the connector ID is set, and its visibility is set to public. Figure 13 In the configuration, the part and property partproperty number id are set, as well as the base property base_property.

[0101] Based on the model information extracted from the XMI file, a fault transmission model framework is generated by transforming the system function design model elements and fault transmission model elements according to their correspondence. A schematic diagram is shown below. Figure 14 As shown in the diagram. For system information that can only be partially mapped or cannot be mapped in the system functional design model, further manual analysis can be performed. Based on the manual analysis, information such as the system's fault logic and failure probability distribution parameters can be supplemented and improved to generate a complete fault propagation model. In one embodiment, a schematic diagram of the manually analyzed and improved fault propagation model is shown below. Figure 15 As shown.

[0102] After constructing the fault propagation model, it can be used for fault test analysis. Before conducting the fault test analysis, the correlation judgment rules between faults and tests are first set on the terminal. In one embodiment, faults and tests in the system are correlated. If the fault f i Test t can be deduced from the occurrence of this. j If it fails, it is called fault f. i With test t j Related, if by test t j The fault f can be derived from this. i If it does not occur, it is called test t. j With fault f i Related, if fault f i With test t j If two things can be mutually inferred, then they are said to be cross-correlated, or the test t... j It is a symmetrical test.

[0103] Based on the above theory, the correlation between faults and tests is defined in the MBSE model: After a fault (module failure state) occurs (only this fault occurs, and other modules in the system are normal), if the impact of the fault (causing failure) can be propagated backward along the input and output ports and the connections between modules in the direction of functional execution, reaching a test point, then the fault is considered to be correlated with reachable tests. Here, the test point is the specific location of the test instrument in the system. In the model, this is represented by associating it with the module's output variable, indicating that certain test instruments are deployed at the module's output, and the system fault is determined by testing this output variable.

[0104] Based on the correlation judgment rules defined above, an automatic correlation matrix generation algorithm is constructed. The algorithm analysis process is as follows: Figure 16 As shown.

[0105] Find the failure states of all lowest-level modules in the system and form a failure state set. ;

[0106] Find all test points established in the system model, and combine the tests contained in each test point into a test set. ;

[0107] Select a test T from the test set in sequence. j Begin the analysis;

[0108] Query test T j The corresponding test point is located by connecting the test point to the output port using the line between the test point and the output port.

[0109] Query all failure states contained in the output port, and draw a fault tree with each failure state as the top event to form a fault tree set. ;

[0110] Select a failure state F from the set of failure states in sequence. i Substitute it into all the fault trees in the fault tree set, and call the FMECA fault effect analysis algorithm to determine whether only the failure state F is valid. i If true, will the fault tree top event occur? If the fault tree top event will occur, then the failure state F... i With test T j It has correlation, and the corresponding position ft in the correlation matrix. ij The value of ft is assigned to 1; otherwise, if none of the fault tree top events occur, then ft ij=0;

[0111] FMECA's fault impact analysis algorithm mainly substitutes the failure state values ​​of the module into the model to solve the state values ​​of each output port, which is a kind of fault propagation deduction process.

[0112] Determine the next failure state F in the failure state set. i+1 With test T j The correlation is calculated until all failure states are determined, completing the vector in the j-th column of the correlation matrix. Results analysis.

[0113] Determine the next test case T in the test set. j+1 Correlation with the set of failure states, completing the vector in the (j+1)th column of the correlation matrix. The algorithm continues to analyze the results until all tests in the test set have completed correlation analysis. At this point, the algorithm terminates and generates a correlation matrix in the prescribed format.

[0114] The set of failure states for the lowest-level module is the set of all failure modes in the model to be analyzed for testability. All failure states contained in the output port refer to all failure states within the output port associated with the test point to which test Tj belongs. Drawing a fault tree with each failure state as the top event means, based on the local fault propagation relationships built within each module as mentioned above, and combined with the input and output connections between modules, sequentially querying the failure nodes that lead to the occurrence of a failure state from the failure state back to its source. The top event of the fault tree refers to determining whether a fault can propagate to the model location of the top event by judging whether the top event occurs after the bottom event occurs, thereby determining the test correlation between the test at that location and the fault being analyzed.

[0115] The essence of testability analysis is whether the test can detect the fault when it occurs (i.e., when the failure state is true). By determining whether the fault can propagate to the output port associated with the test when it occurs, we can determine whether the test can detect the fault and establish the correlation between the fault and the test.

[0116] The automatically generated correlation matrix results are shown in Table 3:

[0117] Table 3. Format of Correlation Matrix Results

[0118]

[0119] This invention addresses the problems existing in current mainstream testability models. Using the increasingly popular MBSE model as input, it supplements the classic testability model by constructing local fault propagation relationships and test points, thus improving upon the classic testability model and forming a testability modeling and analysis device based on fault propagation relationships that is consistent with the functional characteristic model. This yields the following effects: the model-based testability modeling and analysis method ensures the standardization of the model, and the use of formal modeling language ensures the convenience of design modification and iterative updates. By replacing the original fault analysis mode that relies on design experience with fault tree logic operations, the modeling efficiency and analysis accuracy of designers are improved.

[0120] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0121] Based on the same inventive concept, this application also provides a model building apparatus for implementing the model building method described above. The solution provided by this apparatus is similar to the solution described in the above method; therefore, the specific limitations in one or more model building apparatus embodiments provided below can be found in the limitations of the model building method described above, and will not be repeated here.

[0122] In one embodiment, such as Figure 17 As shown, a model building apparatus is provided, including: a design model acquisition module 301, a correspondence acquisition module 302, and a transfer model generation module 303, wherein:

[0123] Design model acquisition module 301 is used to acquire the system functional design model;

[0124] The correspondence acquisition module 302 is used to acquire the element correspondence between the design model modeling elements in the system functional design model and the fault model elements in the corresponding fault transmission model.

[0125] The transmission model generation module 303 is used to parse the system functional design model into preset language format data, and to perform element conversion on the design model modeling elements in the system functional design model according to the element correspondence to obtain the corresponding fault transmission model.

[0126] In one embodiment, the correspondence acquisition module is further configured to acquire the element correspondence between the design model modeling elements in the preset system function design model and the fault model elements in the corresponding fault transmission model.

[0127] In another embodiment, the correspondence acquisition module is further configured to acquire a first correspondence between the underlying model elements of the fault transmission model and the modeling data requirements, a second correspondence between the design model modeling elements of the system functional design model and the system information, and a third correspondence between the underlying model elements and the fault model elements; determine the correspondence between the underlying model elements and the design model modeling elements based on the degree of matching between each modeling data requirement and the system information; and acquire the element correspondence between the design model modeling elements in the system functional design model and the fault model elements of the corresponding fault transmission model.

[0128] In one embodiment, the correspondence acquisition module is further configured to analyze the key fields of system information and modeling data requirements, set the correspondence between each system information and modeling data requirements that are completely corresponding as a complete mapping, set the correspondence between each system information and modeling data requirements that are not completely corresponding as a partial mapping, and set the correspondence between each system information and modeling data requirements that are completely non-corresponding as non-mapping.

[0129] In one embodiment, the underlying model elements include at least a first basic module, a second basic module with sub-modules, state variables, triggering events, fault state transitions, and fault propagation relationships.

[0130] In one embodiment, system information includes at least modules, components, attributes, and triggering events.

[0131] In one embodiment, the transfer model generation module is further configured to, during the process of converting the design model modeling elements in the system functional design model according to the element correspondence, map the design model modeling elements to the corresponding underlying model elements of the fault transmission model based on the correspondence between the various underlying model elements of the fault transmission model and the graphical elements, and then represent the mapped underlying model elements with the corresponding graphical fault model elements.

[0132] Each module in the aforementioned model building device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0133] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 18 As shown, the computer device includes a processor, memory, communication interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a model building method. The display screen can be an LCD screen or an e-ink display screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the computer device casing, or an external keyboard, touchpad, or mouse.

[0134] Those skilled in the art will understand that Figure 18 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0135] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0136] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0137] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0138] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0139] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0140] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0141] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A model construction method, characterized in that, The method includes: Obtain the system functional design model; Obtain the element correspondence between the design model modeling elements in the system functional design model and the fault model elements in the corresponding fault transmission model. The fault model elements include basic modules, modules with sub-modules, sub-modules contained in modules, state variables, interaction variables, trigger time, fault state transition, and fault transmission relationship. The system functional design model is parsed into XMI format data, and the modeling elements of the design model are mapped to the corresponding underlying model elements according to the element correspondence relationship. Based on the third correspondence relationship between the underlying model elements and the fault model elements, the mapped underlying model elements are represented by the corresponding graphical fault model elements to obtain the fault propagation model. The fault propagation model is used for test analysis. The step of obtaining the element correspondence between the design model modeling elements in the system functional design model and the fault model elements in the corresponding fault propagation model includes: The first correspondence between the underlying model elements of the fault propagation model and the modeling data requirements, the second correspondence between the design model modeling elements of the system functional design model and the system information, and the third correspondence between the underlying model elements and the fault model elements are obtained. Based on the matching degree of the modeling data requirements in the first correspondence and the system information in the second correspondence, the element correspondence between the underlying model elements and the modeling elements of the design model is determined. The matching degree is based on semantic analysis and identification of each modeling data requirement and each system information to obtain the analysis results. A correspondence is established between the modeling data requirements with similarity greater than a preset threshold and the system information in the analysis results. Based on the third correspondence, the element correspondence between the fault model elements of the fault propagation model and the design model modeling elements in the system functional design model is determined.

2. The method according to claim 1, characterized in that, The step of obtaining the element correspondence between the design model modeling elements in the system functional design model and the fault model elements in the corresponding fault transmission model also includes: Obtain the element correspondence between the design model modeling elements in the preset system functional design model and the fault model elements in the corresponding fault transmission model.

3. The method according to claim 2, characterized in that, Based on the degree of matching between the modeling data requirements in the first correspondence and the system information in the second correspondence, the correspondence between the underlying model elements and the design model modeling elements is determined, including: Based on the analysis of the key fields of the system information and the modeling data requirements, the correspondence between each piece of system information and the modeling data requirements that are completely corresponding is set as a complete mapping, the correspondence between each piece of system information and the modeling data requirements that are not completely corresponding is set as a partial mapping, and the correspondence between each piece of system information and the modeling data requirements that are completely non-corresponding is set as non-mapping.

4. The method according to claim 2, characterized in that, The underlying model elements include at least a first basic module, a second basic module with sub-modules, state variables, triggering events, fault state transitions, and fault propagation relationships.

5. The method according to claim 2, characterized in that, The system information includes at least modules, components, attributes, and triggering events.

6. A model building apparatus, characterized in that, The device includes: The design model acquisition module is used to acquire the system functional design model; The correspondence acquisition module is used to acquire the element correspondence between the design model modeling elements in the system functional design model and the fault model elements in the corresponding fault transmission model. The fault model elements include basic modules, modules with sub-modules, sub-modules contained in modules, state variables, interaction variables, trigger time, fault state transition and fault transmission relationship. The fault propagation model generation module is used to parse the system functional design model into XMI format data, map the design model modeling elements to the corresponding underlying model elements according to the element correspondence relationship, and represent the mapped underlying model elements with the corresponding graphical fault model elements according to the third correspondence relationship between the underlying model elements and the fault model elements to obtain the fault propagation model. The fault propagation model is used for test analysis. The correspondence acquisition module is further configured to acquire a first correspondence between the underlying model elements of the fault transmission model and the modeling data requirements, a second correspondence between the design model modeling elements of the system functional design model and the system information, and a third correspondence between the underlying model elements and the fault model elements; based on the matching degree between the modeling data requirements in the first correspondence and the system information in the second correspondence, determine the element correspondence between the underlying model elements and the design model modeling elements, wherein the matching degree is based on semantic analysis and identification of each modeling data requirement and each system information to obtain the analysis results, and establish a correspondence between the modeling data requirements with a similarity greater than a preset threshold in the analysis results and the system information; based on the third correspondence, determine the element correspondence between the fault model elements of the fault transmission model and the design model modeling elements in the system functional design model.

7. The apparatus according to claim 6, characterized in that, The correspondence acquisition module is also used to acquire the element correspondence between the design model modeling elements in the preset system function design model and the fault model elements in the corresponding fault transmission model.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 5.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.

Images