A method and system for change design and impact analysis of an avionics system model

Abstract

The present invention discloses a method and system for change design and impact analysis of an avionics system model, obtaining an avionics system architecture design model, and determining the model change content to be carried out according to business requirements; comprehensively using model deletion, model merging, model splitting, model hierarchy change, model interaction change, and model attribute information adjustment to carry out change design of the avionics system architecture design model; analyzing the impact after the change of the avionics system architecture design model according to the avionics model expression rules, and feeding back the change impact to the designers, and completing the change after confirmation. The present invention carries out change design on the avionics system model according to design requirements, conducts model changes on the avionics field model, and analyzes the change impact of the model, ensuring the consistency of the context of the avionics system model during the change process.

Description

Technical Field

[0001] The present invention belongs to the field of avionics system architecture modeling, and relates to a method and system for avionics system model change design and impact analysis. Background Art

[0002] Avionics systems are complex systems with intricate cross-linking relationships within the system. To accurately represent the avionics system architecture, the industrial sector has used model-based methods to describe the avionics system architecture design model. Model-based systems engineering practices often use the RFLP (requirements - function - logic - physical) framework to describe complex systems, build models using model elements, model relationships, and model attributes, and present models using graphical modeling languages such as SysML. For users, the decomposition relationships, interaction relationships, etc. of the system are presented in the model diagram.

[0003] During the entire life cycle of the project, business operations such as new addition, deletion, and modification will also occur frequently in avionics system design scenarios. In addition to using modeling work to create new models, relationships, and attributes, more of the model is iterative change. The traditional model change process depends on the system designer's understanding of the avionics system to make changes to the model, which is prone to incomplete changes in model elements, relationships, and attributes, and is also prone to incomplete analysis of the impact of changes by the designer. Moreover, there is a huge workload in model changes, the change process is cumbersome, and the error rate is high. Summary of the Invention

[0004] The object of the present invention is to provide a method for avionics system model change design and impact analysis and a system for implementing this method, which can achieve model change design and impact analysis such as model deletion, model merging, model splitting, model hierarchical change, model interaction change, and model attribute information change, solve the problems of unreasonable granularity design, information interaction errors, and inconsistent relevant model attributes in the avionics system architecture design model, realize efficient changes in the system architecture model design process, perform rapid optimization, and assist system architecture designers in efficiently and accurately carrying out avionics system model change design and impact analysis.

[0005] The object of the present invention is achieved through the following technical solutions:

[0006] A method for avionics system model change design and impact analysis includes the following steps:

[0007] Obtain the avionics system architecture design model, and determine the model change content to be carried out according to business requirements; wherein, the avionics system architecture design model is described using the requirements - function - logic - physical framework, constructed using model elements, model relationships, and model attributes, and the model diagram is presented using a graphical modeling language;

[0008] Carry out the change design of the avionics system architecture design model by comprehensively using model deletion, model merging, model splitting, model hierarchy change, model interaction change, and model attribute information adjustment;

[0009] Analyze the impact after the change of the avionics system architecture design model according to the avionics model expression rules, and feedback the change impact to the designers. After confirmation, complete the change.

[0010] Another object of the present invention is achieved by the following technical solutions:

[0011] A system for implementing the change design and impact analysis method of an avionics system model includes a model display function module, a model change impact analysis module, a model change preview display module, a model change impact report generation module, a model change execution module, and a model database module;

[0012] The model display function module is used to display the avionics model, show the hierarchical nesting relationship of the model using the engineering file tree component, show the model expressed in the graphical modeling language using the drawing board component, show the attribute information of the model using the table component, and at the same time provide interfaces for model deletion, model merging, model splitting, model hierarchy change, model interaction change, and model attribute information adjustment, and provide the model for the user to operate the change;

[0013] The model change impact analysis module is used to analyze other models directly and indirectly affected by the current model adjustment, including element models, relationship models, parameter models, graph models, and model attributes. The analysis basis is the horizontal interaction relationship, vertical allocation relationship, and attribute vertical transmission relationship of the avionics model;

[0014] The model change preview display module uses a graphical method to show the comparison of the core relationships before and after the current model change, and shows the core change points to the user to assist the user in focusing on the analysis;

[0015] The model change impact report generation module is used to output the list of all affected model data to the report in a fixed format to assist the user in comprehensively and completely analyzing the model change;

[0016] The model change execution module provides direct operation interfaces for model deletion, model merging, model splitting, model hierarchy change, model interaction change, and model attribute information adjustment, makes substantial adjustments to the model data, and synchronizes the data to the database;

[0017] The model database module stores model information, including model element tables, model attribute tables, model relationship tables, model charts, etc., and provides database access interfaces for system designers.

[0018] The beneficial effects of the present invention are as follows:

[0019] The method for change design and impact analysis of the avionics system model provided by the present invention involves the change scenarios of the avionics system design model. All model change work can be completed through methods such as model deletion, model merging, model splitting, model level change, model interaction change, and model attribute information adjustment and its impact analysis. The system provided by the present invention can support previewing the change effect before actual change, exporting a report of the complete impact results, and allowing users to confirm whether to make the change, reducing the risk of incorrect changes and ensuring the consistency and correctness of the model during the change process. Description of the Drawings

[0020] Figure 1 It is a functional decomposition model diagram of the avionics system.

[0021] Figure 2 It is a functional interaction model diagram of the avionics system.

[0022] Figure 3 It is a functional-logical interaction model diagram for providing attitude display function.

[0023] Figure 4 It is a schematic diagram of the object relationship of the avionics system architecture design model (partial).

[0024] Figure 5 It is a structure diagram of the model change system.

[0025] Figure 6 It is a schematic diagram of selecting the merged model and the model to be merged.

[0026] Figure 7 It is an operation diagram of merging the model to be merged into the merged model.

[0027] Figure 8 It is a comparison schematic diagram before and after merging.

[0028] Figure 9 It is a schematic diagram of the affected information after merging.

[0029] Figure 10 It is a schematic diagram of the system after merging.

[0030] Figure 11 It is a functional interaction model diagram before merging.

[0031] Figure 12 It is a functional interaction model diagram after merging.

[0032] Figure 13 It is a schematic diagram of the process of the method for change design and impact analysis of the avionics system model. Detailed Description of the Invention

[0033] The present invention will be further described in detail below with reference to the drawings and embodiments.

[0034] Embodiment 1

[0035] A method for change design and impact analysis of an avionics system model shown in this embodiment changes the design of the avionics system architecture design model according to design requirements and analyzes the impact of the change of the avionics system architecture design model, ensuring the consistency of the context of the avionics system architecture design model during the change process. See Figure 13 As shown, the method includes the following steps:

[0036] S100) Obtain the avionics system architecture design model and determine the model change content to be carried out according to business requirements;

[0037] Among them, the avionics system architecture design model uses the RFLP (requirement - function - logic - physical) framework or a similar framework to describe the avionics system, is constructed using model elements, model relationships, and model attributes, and uses graphical modeling languages such as SysML to present model diagrams such as decomposition relationship diagrams, functional interaction diagrams, and functional - logic interaction diagrams, as Figure 1 , Figure 2 , Figure 3 shown.

[0038] Model elements are used to describe the requirements, functions, logical components, physical devices, interaction parameters and messages of the aviation system, and can express interfaces, compositions, and boundaries through nested and inclusion relationships;

[0039] Model relationships are used to express dependencies, interactions, and connections between models;

[0040] Model attributes are used to express the attributes and constraints of model elements and model relationships;

[0041] Model diagrams can present the composition and interaction of the aviation system according to user needs;

[0042] Model diagrams are mappings of model elements and model relationships. Deleting a model diagram will not affect model elements and model relationships, but deleting model elements and model relationships requires deleting all mappings in the model diagrams at the same time. Currently common SysML modeling tools, such as EA (Enterprise Architect), all support automatic changes to the above - mentioned model and diagram mapping relationships.

[0043] As Figure 4 shown, according to the avionics system architecture design model expression rules, there are not only class - and - instance model relationships between model elements, but also model relationships such as dependencies, interactions, and connections.

[0044] When determining the content of model changes to be carried out according to requirements, it includes function deletion, function splitting, function merging, function level change, splitting and merging of function parameters, adjustment of function interaction relationships, change of function and function parameter attributes, change of the allocation relationship between functions and logical components, logical component deletion, logical component splitting, logical component merging, logical component level change, splitting and merging of logical parameters, adjustment of logical interaction relationships, change of logical and logical parameter attributes, deletion of physical devices and their ports and attribute changes, deletion of physical connections and bus type changes, deletion of data and data packaging messages and attribute changes, change of the allocation relationship between logical components and physical devices. According to business requirements, determine the model elements, model relationships, model attributes, model diagrams that need to be adjusted, and the model elements, model relationships, model attributes, model diagrams related to the adjusted model elements.

[0045] S200) Carry out the change design of the avionics system architecture design model, including comprehensively using methods such as model deletion, model merging, model splitting, model level change, model interaction change, and model attribute information adjustment.

[0046] S300) Analyze the impact of the changed avionics system architecture design model according to the avionics model expression rules, including the impact on model element models, relationships, model attributes, diagram models, and model attributes, and feedback the change impact to the designers. After confirmation, complete the change. This step is mainly completed by the computer system.

[0047] The following will explain each change design and impact analysis in detail in combination with the model change requirements.

[0048] (1) Model deletion

[0049] During the design process, if the designer finds that the model element design is redundant or inappropriate and needs to delete the model element and update all the impacts after deletion, the deletion of the model element and information adjustment are required. The model operation should follow the avionics model expression rules, and the impact analysis is as follows:

[0050] 311) According to the avionics model expression rules, judge the impact of the deletion operation of the model element to be deleted on other model elements. If there is a dependency relationship, the sub-model element and its relationship with the sub-model element need to be deleted simultaneously;

[0051] Example: If a physical device is deleted, the port model on the physical device should be deleted simultaneously. At the same time, the physical line connected to the port model should also be deleted;

[0052] 312) When deleting the attribute information of the model element, according to the avionics model expression rules, judge the impact of the deletion operation of the model element to be deleted on the attributes of other model elements. If there is a calculation dependency, the attributes of the affected model elements need to be adjusted;

[0053] Example: If a device - type model has attribute information such as weight or power consumption, after removing a board of a device, it is necessary to correspondingly check and confirm the calculation method or calculation result of the device's attribute information.

[0054] 313) If the model element to be deleted is a class, then it is necessary to delete the instances of the affected model elements, as well as the relevant model elements, model relationships, model attributes, and mappings in the model diagrams.

[0055] Example: If an indivisible functional model - element class is deleted, it is necessary to delete its instances, the model elements related to the instances, the model relationships, the model attributes, and the mappings in the model diagrams.

[0056] 314) If the deleted model element is mapped in multiple model diagrams, then modify the affected model diagrams one by one.

[0057] 315) Delete the node of the model element itself.

[0058] When implementing the deletion function in steps 311 to 315 of this embodiment, it is possible to show the impact analysis of each step to the user through a wizard. After the user confirms the change of the affected content, the change is executed.

[0059] The constraint conditions for model deletion are as follows:

[0060] 1) The number of selected model elements is 1.

[0061] 2) It is not allowed to delete the top - level model elements defined by the avionics system.

[0062] (2) Model merging

[0063] During the design process, the designer finds that the splitting degree of the model elements is inappropriate and the granularity of the model elements is too fine, and model - element merging is required. The model operations should follow the avionics - model expression rules, and the impact analysis is as follows:

[0064] 321) Judge whether merging the model elements to be merged will cause inconsistent model - element expressions or conflicts with the avionics - model expression rules. If the merging conditions are not met, the model elements to be merged should be adjusted first according to the inconsistent or conflicting situations.

[0065] Example: If two functional - class model elements are originally implemented by two different types of physical devices, they cannot be directly functionally merged. If merging is really required, it is necessary to adjust the relationship between the function and the device. Sometimes, it is even necessary to first split the function, then adjust the relationship between the split function and the device, and finally perform the function merging.

[0066] 322) According to the avionics model expression rules, judge the impact of the merging operation of the model elements to be merged on the model attributes, and confirm the model attribute information after merging;

[0067] 323) According to the avionics model expression rules, confirm the model relationships related to the merged model elements, and merge the sub-elements of the original model elements together;

[0068] 324) If the merged model elements are presented as mappings in multiple model diagrams, then the affected model diagrams need to be modified one by one;

[0069] 325) If the model element is a class, then merge the instances of the affected model elements, the model attributes, model relationships, and sub-model elements related to the instances, as well as the mappings in the model diagrams.

[0070] When implementing the merging function in steps 321 to 325 of this embodiment, the impact analysis of each step can be shown to the user through a wizard, and after the user confirms the changes to the affected content, the changes are executed.

[0071] The constraint conditions for model merging are as follows:

[0072] 1) The type of the model diagram where the model element is located must be a decomposition class diagram, such as a function decomposition diagram or a logical definition diagram;

[0073] 2) The number of selected model elements is 2;

[0074] 3) The type of the model element is a functional component or a logical component;

[0075] 4) The top-level model elements defined by the avionics system cannot be merged;

[0076] 5) Two model elements are in the same subsystem and cannot be merged across subsystems;

[0077] 6) If the merged is a functional model, then two functional model elements cannot be assigned to different logical components, but functional model elements that are not assigned logical components are allowed to be merged;

[0078] 7) If the merged is a logical model, then two logical model elements cannot be assigned to different physical components, but logical model elements that are not assigned physical components are allowed to be merged.

[0079] (Three) Model splitting

[0080] During the design process, the designer finds that the model splitting intensity is inappropriate and the granularity of the model is too coarse, and the model needs to be split. The model operation should follow the avionics model expression rules, and the impact analysis is as follows:

[0081] 331) According to the avionics model expression rules, judge the impact of the splitting operation on the model elements to be split on the model attributes, and confirm the model attributes after splitting. When a model element is split into two model elements, the attribute information of the two model elements remains the same except for keyword information such as ID;

[0082] 332) According to the avionics model expression rules, judge the impact of the splitting operation on the model elements to be split on the model relationships, and confirm the relationships between the two model elements after splitting;

[0083] Example 1: There is an allocation relationship between the functional model A and the logical model B. The functional model A is split into functional A1 and functional A2. After splitting, both the functional components A1 and A2 are allocated to the logical component B;

[0084] Example 2: There is an allocation relationship between the functional model A1, the functional model A2, and the logical model B. The functional components A1 and A2 are allocated to the logical component B. If the logical component B is split into B1 and B2, then it should be manually confirmed according to the model expression rules for the model situation after splitting: (1) Functional A1 and A2 are allocated to logical B1, and there is no relationship between functional A1 and A2 and logical B2; (2) Functional A1 is allocated to logical B1, and functional A2 is allocated to logical B2;

[0085] Example 3: There is an inclusion relationship between model A and model B, and model A includes model B. If model B is split into B1 and B2, then after splitting, model A includes model B1 and B2;

[0086] Example 4: There is an inclusion relationship between model A and model B1, and there is an inclusion relationship between model A and model B2. Model A includes B1 and B2. If model A is split into A1 and A2, then it should be manually confirmed according to the model expression rules for the model situation after splitting: (1) The sub-models B1 and B2 are copied, that is, A1 includes B1 and B2, and A2 includes copies of B1 and B2; (2) The sub-models B1 and B2 are split, that is, A1 includes B1 and A2 includes B2;

[0087] Example 5: There is an interaction relationship between model A and model B. Model A sends parameters C1 and C2 to model B. If model A is split into A1 and A2, then it should be manually confirmed according to the model expression rules for the model situation after splitting: (1) Model A1 sends parameters C1 and C2 to model B, and there is no interaction between model A2 and model B; (2) Model A1 sends parameter C1 to model B, and model A2 sends parameter C2 to model B;

[0088] Example 6: Model A and Model B have an interaction relationship. Model A sends parameters C1 and C2 to Model B. If Model B is split into B1 and B2, then it is necessary to manually confirm the situation of the split models according to the model expression rules: (1) Model A sends parameters C1 and C2 to Model B1, and there is no interaction between Model A and Model B2; (2) Model A sends parameter C1 to Model B1, and Model A sends parameter C2 to Model B2;

[0089] 333) If the split model elements are mapped in multiple model diagrams, then the affected model diagrams need to be modified one by one;

[0090] 334) If the model element is a class, it is also necessary to split the model element instances, model attributes, model relationships related to the instances, and the affected model elements, as well as the mappings in the model diagrams.

[0091] When implementing the splitting function in steps 331 to 334 of this embodiment, it is possible to show the impact analysis of each step to the user through a wizard. After the user confirms the changes to the affected content, the changes are executed.

[0092] The constraint conditions for model splitting are as follows:

[0093] 1) The number of selected model elements is 1;

[0094] 2) It is not possible to split the top-level model elements defined by the avionics system;

[0095] 3) After splitting, the two model elements belong to the same subsystem, but cannot have the same name. One of them can have the same name as the element before splitting;

[0096] (IV) Model Hierarchy Change

[0097] During the design process, the designer finds that the hierarchical assignment of the model elements is inappropriate, that is, the hierarchy of the model elements is too high or too low, and the hierarchical change of the model elements needs to be carried out. The operations of the model elements should follow the avionics model expression rules, and the impact analysis is as follows:

[0098] 341) Judge whether the new father node is a sub-element, sub-sub-element or more-layer sub-element of the model element to be changed. If so, the hierarchical change cannot be carried out, and it is necessary to first adjust the hierarchical relationship of the new father node;

[0099] Example: The father node of model element A is model element B, and the father node of model element B is model element C. Then it is not possible to adjust the father node of B to A; it is only possible to first adjust model element A so that its new father node is C, and then adjust the father node of B to A. After the adjustment is completed, the father node of model element B is A, and the father node of model element A is C;

[0100] 342) Change the model relationship between the model element and its father node to the new father node;

[0101] 343) According to the avionics model expression rules, adjust the allocation relationship affected by the change of the model element level and synchronously adjust the allocation relationship of the sub-model elements;

[0102] Example: If the original father node of function element A is function B and the new father node is function C, then it should be manually confirmed according to the model expression rules: (1) If function C is allocated to logic component D, then function A and its sub-elements should be changed to be allocated to logic component D; (2) If function C is not allocated to a logic component, the allocation relationship of function A and its sub-elements remains unchanged;

[0103] 344) According to the avionics model expression rules, judge the impact of the level change operation on the model attributes of the model element to be level-changed, and confirm the model attribute information after the level change;

[0104] Example: The attribute FDAL (function development assurance level) of function model F1 is C, and the FDAL of function model F2 is A. According to the avionics function development requirements, if function F1 becomes a sub-element of function F2, the FDAL of F1 is changed to A, otherwise it does not need to be changed;

[0105] 345) If the model element to be level-changed is presented as a mapping in multiple model diagrams, the affected model diagrams need to be modified one by one;

[0106] 346) If the model element is a class, it is also necessary to change the instances of the affected model elements, the model attributes, model relationships, and sub-model elements related to the instances, as well as the mappings in the model diagrams.

[0107] In this embodiment, when implementing the model level change function of steps 341 to 346, the impact analysis of each step can be presented to the user through a wizard, and after the user confirms the change of the affected content, the change is executed.

[0108] The constraint conditions for model level change are as follows:

[0109] 1) The type of the model diagram where the model element is located must be a decomposition class diagram, such as a function decomposition diagram or a logical definition diagram;

[0110] 2) Select the model element to be changed and the new father element in sequence;

[0111] 3) The new father node cannot be the sub-element, sub-sub-element or multi-layer sub-sub-element of the element to be changed;

[0112] 4) The model element type is a function component or a logical component;

[0113] 5) Hierarchical changes cannot be made to the top-level model elements defined by the system;

[0114] 6) If two model elements belong to the same subsystem, cross-system hierarchical changes are not allowed.

[0115] (5) Model interaction changes

[0116] If the designer finds during the design process that the objects with which the model elements interact need to be modified by the sender and receiver due to design changes, then model element interaction changes need to be carried out. Model operations should follow the rules of avionics model expression, and the impact analysis is as follows:

[0117] 351) If the model element to be changed is the sender, first determine whether the receiver of the interaction parameter is unique, and then add the corresponding sending interface, the relationship with the receiver, and the relationship with the interaction parameter to the new sender, and then delete the original sending interface, the relationship with the receiver, and the relationship with the interaction parameter;

[0118] Example 1: Function A sends interaction parameter C to B1 and B2. At this time, if only function D is to be changed to send interaction parameter C to B1, a situation that does not conform to the model specification (A sends C to B2, D sends C to B1, and it is impossible to distinguish which function constructs the interaction parameter C, which does not conform to the business scenario) will occur. The change should be completed by combining business requirements and comprehensively using the change rules;

[0119] Example 2: In this example, the port naming rule is port + I / O + the port corresponding interaction parameter name + the source ATA name + the source node name. According to the SysML rule, the class name is after the colon. For example, Figure 2 the shown poFCS_Attitude_ATA27FCS_Provide_Attittude_Data:FCS Attitude is the parameter sent by the function of providing attitude data of the ATA27 flight control system. The port of this function instance is double-inherited, one is a function class port and the other is a function parameter. Therefore, when adding a new interface, not only the naming rule should be followed, but also the class and instance need to be updated;

[0120] 352) If the model element to be changed is the receiver, then add the corresponding receiving interface and the relationship with the sender to the new receiver, and then delete the original receiving interface and the relationship with the sender;

[0121] 353) If it is the parameter object of the interaction, first determine whether the new interaction parameter has been agreed to be constructed by other model elements. If it has not been agreed by other model elements, then update the sending interface of the original sender and the receiving interface of the receiver. Otherwise, change operations such as splitting and merging the sender first need to be carried out to constrain the parameter to the required model element;

[0122] 354) If the interaction relationships of the changed model elements are presented as mappings in multiple model diagrams, then the affected model diagrams need to be modified one by one;

[0123] 355) If the adjusted interaction relationship is a class relationship, it is also necessary to adjust the instances of the affected model elements, the interfaces and relationships related to the instances, and the mappings in the model diagrams.

[0124] When implementing the model interaction change function in steps 351 to 355 of this embodiment, it is possible to display the impact analysis of each step to the user through a wizard. After the user confirms the change of the affected content, the change is executed.

[0125] The constraint conditions for model interaction change are as follows:

[0126] 1) The type of the model diagram where the model element is located must be an interaction class diagram, such as a function interaction diagram or a logical interaction diagram, and the new change object is in the same model diagram;

[0127] 2) Select the interaction triple (sender, receiver, interaction parameter) in sequence, then select the type of change, and then select the object of change;

[0128] 3) When changing the sender, the avionics system requires that the original sender has not sent this interaction parameter to other receivers;

[0129] 4) When changing the interaction parameter, the avionics system requires that the new interaction parameter has not been bound and constrained by other senders.

[0130] 5) The sender and the interaction parameter are in the same subsystem, and cross-system interaction changes are not allowed.

[0131] (6) Adjustment of model attribute information

[0132] During the design process, the designer finds that the model attribute information is inconsistent with the current requirements and the information of the model attributes is incorrect, and the information of the model attributes needs to be adjusted. The model operations should follow the avionics model expression rules, and the impact analysis is as follows:

[0133] 361) According to the avionics model expression rules, judge the correlation between the model attribute information to be adjusted and other model attribute information. If there is a value dependency (such as a size relationship, a subordination relationship, etc.), then the information of the relevant model attributes needs to be updated synchronously;

[0134] Example 1: When modifying the attribute value of a parameter model (such as: height), attention should be paid to the adjustment of the unit (such as: meter, foot);

[0135] Example 2: When modifying the attribute information of the equipment board weight, modify the attribute information of the equipment weight;

[0136] 362) If the model element is a class, it is also necessary to adjust the instances of the affected model elements and the attributes related to the instances at the same time.

[0137] When implementing the model attribute information adjustment function in steps 361 to 362 of this embodiment, the impact analysis of each step can be shown to the user through a wizard. After the user confirms the change of the affected content, the change is executed.

[0138] The constraint conditions for the adjustment of model attribute information are as follows:

[0139] 1) The keyword information defined by the system such as the ID of the model element cannot be changed;

[0140] Embodiment 2

[0141] This embodiment provides a system for implementing the change design and impact analysis method of the avionics system model shown in Embodiment 1, including a model display function module, a model change impact analysis module, a model change preview display module, a model change impact report generation module, a model change execution module, and a model database module, as Figure 5 shown.

[0142] The model display function module is used to display the avionics system architecture design model, show the hierarchical nesting relationship of the avionics system architecture design model by using an engineering file tree component, show the model expressed in a graphical modeling language by using a drawing board component, show the attribute information of the model by using a table component, and at the same time provide interfaces for model deletion, model merging, model splitting, model hierarchical change, model interaction change, and model attribute information adjustment to provide the user with the model for operation and change;

[0143] The model change impact analysis module is used to analyze the directly and indirectly affected factors caused by the adjustment of the current model element, including model elements, model relationships, model parameters, model diagrams, and model attributes. The analysis basis is the horizontal interaction relationship, vertical allocation relationship, and vertical attribute transfer relationship of the avionics model;

[0144] The model change preview display module shows the comparison of the core relationships before and after the current model change in a graphical way, shows the core change points to the user, and assists the user in focusing analysis;

[0145] The model change impact report generation module is used to output the list of all affected model data to a report in a fixed format to assist the user in conducting a comprehensive and complete model change analysis;

[0146] The model change execution module provides direct operation interfaces for model deletion, model merging, model splitting, model hierarchical change, model interaction change, and model attribute information adjustment, makes substantial adjustments to the model data, and synchronizes the data to the database;

[0147] The model database module stores model information, including model element tables, model attribute tables, model relationship tables, model diagrams, etc., and provides database access interfaces for system designers.

[0148] Example: Change operation of model merging through the system

[0149] 1) The designer combines business requirements, selects the merged model elements and the model elements to be merged in the human-machine interaction interface. After clicking the merge menu, the human-machine interaction interface provides the merge operation. As Figure 6 shown, the designer selects the model element to be merged Provide Attitude Data and the merged model element 27FA in the human-machine interaction interface, and clicks the menu Merge for subsequent merge operations.

[0150] 2) The human-machine interaction interface prompts the designer that the model elements to be merged will be merged into the merged model elements. As Figure 7 shown, Provide Attitude Data will be merged into 27FA, and click Next to proceed to the next step.

[0151] 3) The change impact analysis module obtains the interaction and traceability relationship information of the merged model elements, and the interaction, ports and traceability relationship information of the model elements to be merged. The model change preview display module displays the distribution of model elements before and after merging in the human-machine interaction interface for the designer to confirm. See Figure 8 shown. The left figure is the distribution of model elements before merging, and the right one is the layout of model elements after merging. By comparison, it can be clearly known which model elements are merged and how the distribution of model elements is different after merging. After confirmation, proceed to the next step.

[0152] 4) According to the information such as the affected functions and function parameters after merging analyzed by the change impact analysis module, it is displayed through the human-machine interaction interface for the designer to confirm. After confirmation, proceed to the next step. As Figure 9 shown, it can be seen the impact on the model diagram, parameters, model and relationship after merging.

[0153] 5) The model change impact report generation module saves the architecture model data of the model elements Provide Attitude Data to be merged and the merged model element 27FA to the specified folder. Then the model change execution module will perform the actual merge on the operation database, transfer the interaction and ports of the model elements to be merged to the merged model elements, delete the function-to-logical assignment connections of the merged model elements and the model elements to be merged, delete the model elements to be merged, update the data of the merged model elements and write them into the database, and update the interaction relationships between the already established models. See Figure 10After reloading the decomposition diagram as shown, it is found that the Provide Attitude Data model has been deleted, and the allocation connection lines from functions to logic have also been deleted. In addition to having a direct impact on model elements, model merging also changes the established interaction diagrams. Through Figure 11 and Figure 12 As shown in the comparison of the model diagrams, it can be seen that the interaction diagrams have also changed synchronously.

[0154] To avoid difficulties in data display caused by excessive model data volume, the system filters data based on the data already displayed in the current diagram on the premise that the selected model complies with the rules, previews the comparison results before and after the change, controls the amount of data displayed, and makes a quick display response.

[0155] It can be understood that for those of ordinary skill in the art, equivalent substitutions or changes can be made according to the technical solution and inventive concept of the present invention, and all such changes or substitutions should fall within the protection scope of the claims appended to the present invention.

Claims

1. A method for change design and impact analysis of an avionics system model, characterized in that Including the following steps: Obtain an avionics system architecture design model, and determine the model change content that needs to be carried out according to business requirements; among them, the avionics system architecture design model is described using a requirements - function - logic - physical framework, constructed using model elements, model relationships, and model attributes, and presents a model diagram using a graphical modeling language; When determining the model change content that needs to be carried out according to requirements, it includes function deletion, function splitting, function merging, function level change, splitting and merging of function parameters, adjustment of function interaction relationships, change of function and function parameter attributes, change of the allocation relationship between functions and logical components, logical component deletion, logical component splitting, logical component merging, logical component level change, splitting and merging of logical parameters, adjustment of logical interaction relationships, change of logical and logical parameter attributes, deletion and attribute change of physical devices and their ports, deletion of physical connections and bus type change, deletion and attribute change of data and data packet messages, change of the allocation relationship between logical components and physical devices, and determine the model elements, model relationships, model attributes, model diagrams that need to be adjusted, and the model elements, model relationships, model attributes, model diagrams related to the adjusted model elements according to business requirements; Comprehensively utilize model deletion, model merging, model splitting, model level change, model interaction change, and adjustment of model attribute information to carry out change design of the avionics system architecture design model; among them, after the change design using model deletion, the impact analysis is as follows: According to the avionics model expression rules, judge the impact of the deletion operation of the model elements to be deleted on other model elements. If there is a dependency relationship, the sub - model elements and their relationships need to be deleted simultaneously; When deleting the attribute information of model elements, according to the avionics model expression rules, judge the impact of the deletion operation of the model elements to be deleted on the attributes of other model elements. If there is a dependency relationship, the attributes of the affected model elements need to be adjusted; If the model element to be deleted is a class, the instances of the affected model elements and the mappings in the related model elements, model relationships, model attributes, and model diagrams need to be deleted; If the deleted model element is mapped in multiple model diagrams, the affected model diagrams are modified one by one; Delete the node of the model element itself; Analyze the impact after the change of the avionics system architecture design model according to the avionics model expression rules, and feedback the change impact to the designers. After confirmation, complete the change.

2. The method for change design and impact analysis of an avionics system model according to claim 1, characterized in that After the change design using model merging, the impact analysis is as follows: Judge whether there will be inconsistent model element expressions or conflicts with the avionics model expression rules when merging the model elements to be merged. If the merging conditions are not met, the model elements to be merged should be adjusted according to the inconsistent or conflicting situations first; According to the avionics model expression rules, judge the impact of the merging operation of the model elements to be merged on the model attributes, and confirm the model attribute information after merging; According to the avionics model expression rules, confirm the model relationships related to the merged model elements, and merge the sub - elements of the original model elements together; If the merged model elements are mapped in multiple model diagrams, the affected model diagrams need to be modified one by one; If the model element is a class, the instances of the affected model elements, the model attributes, model relationships, and sub-model elements related to the instances, as well as the mappings in the model diagrams, are merged.

3. The method for change design and impact analysis of an avionics system model according to claim 1, characterized in that After the change design using model splitting, the impact analysis is as follows: According to the avionics model expression rules, judge the impact of the splitting operation of the model elements to be split on the model attributes, and confirm the model attributes after splitting. When a model element is split into two model elements, the attribute information of the two model elements is the same except for the keyword information; According to the avionics model expression rules, judge the impact of the splitting operation of the model elements to be split on the model relationships, and confirm the relationships between the two model elements after splitting; If the split model elements are mapped in multiple model diagrams, the affected model diagrams need to be modified one by one; If the model element is a class, it is also necessary to split the model element instances, the model attributes, model relationships, and affected model elements related to the instances, as well as the mappings in the model diagrams.

4. The change design and impact analysis method of an avionics system model according to claim 1, characterized in that After the change design using model hierarchy changes, the impact analysis is as follows: Judge whether the new father node is a sub-element, sub-sub-element or more-layer sub-element of the model element to be changed. If so, the hierarchy change cannot be performed, and the hierarchy relationship of the new father node needs to be adjusted first; Change the model relationship between the model element and its father node to the new father node; According to the avionics model expression rules, adjust the allocation relationships affected by the model element hierarchy change and synchronously adjust the allocation relationships of the sub-model elements; According to the avionics model expression rules, judge the impact of the hierarchy change operation of the model element to be hierarchically changed on the model attributes, and confirm the model attribute information after the hierarchy change; If the model elements whose hierarchy is changed are mapped in multiple model diagrams, the affected model diagrams need to be modified one by one; If the model element is a class, it is also necessary to change the instances of the affected model elements, the model attributes, model relationships, and sub-model elements related to the instances, as well as the mappings in the model diagrams.

5. The change design and impact analysis method of an avionics system model according to claim 1, characterized in that After the change design using model interaction changes, the impact analysis is as follows: If the model element to be changed is the sender, first judge whether the receiver of the interaction parameter is unique, and then add the corresponding sending interface, relationship with the receiver, and relationship with the interaction parameter to the new sender, and then delete the original sending interface, relationship with the receiver, and relationship with the interaction parameter; If the model element to be changed is the receiver, add the corresponding receiving interface and relationship with the sender to the new receiver, and then delete the original receiving interface and relationship with the sender; If it is an interaction parameter object, first judge whether the new interaction parameter has been agreed to be constructed for other model elements. If it has not been agreed for other model elements, update the sending interface of the original sender and the receiving interface of the receiver. Otherwise, it is necessary to perform change operations such as splitting and merging the sender first to constrain the parameter to the required model element; If the interaction relationships of the changed model elements are mapped in multiple model diagrams, the affected model diagrams need to be modified one by one; If the adjusted interaction relationship is a class relationship, it is also necessary to adjust the instances of the affected model elements, the interfaces and relationships related to the instances, and the mappings in the model diagram.

6. The method for change design and impact analysis of an avionics system model according to claim 1, wherein After the change design adjusted using the model attribute information, the impact analysis is as follows: According to the avionics model expression rules, judge the relevance between the model attribute information to be adjusted and other model attribute information. If there is a value dependency, it is necessary to synchronously update the information of the relevant model attributes. If the model element is a class, it is also necessary to adjust the instances of the affected model elements and the attributes related to the instances at the same time.

7. A system for implementing the method of change design and impact analysis of an avionics system model according to any one of claims 1 to 6, comprising a model display function module, a model change impact analysis module, a model change preview display module, a model change impact report generation module, a model change execution module, and a model database module, characterized in that: The model display function module is used to display the avionics model, use the engineering file tree component to display the hierarchical nesting relationship of the model, use the drawing board component to display the model expressed in the graphical modeling language, use the table component to display the attribute information of the model, and at the same time provide interfaces for model deletion, model merging, model splitting, model hierarchy change, model interaction change, and model attribute information adjustment, and provide the user with the changed model for operation. The model change impact analysis module is used to analyze other models directly and indirectly affected by the current model adjustment, including element models, relationship models, parameter models, graph models, and model attributes; the analysis basis is the horizontal interaction relationship, vertical allocation relationship, and attribute vertical transmission relationship of the avionics model. The model change preview display module uses a graphical method to display the comparison of the core relationships before and after the current model change, and shows the core change points to the user to assist the user in focusing analysis. The model change impact report generation module is used to output all the affected model data lists to a report in a fixed format to assist the user in performing a comprehensive and complete model change analysis. The model change execution module provides direct operation interfaces for model deletion, model merging, model splitting, model hierarchy change, model interaction change, and model attribute information adjustment, makes substantial adjustments to the model data, and synchronizes the data to the database. The model database module stores model information, including model element tables, model attribute tables, model relationship tables, model charts, and provides database access interfaces for system designers.

Images