Integrated Construction Method, Device, and Computer Equipment for Avionics System Graphic Element Model

Abstract

The present invention discloses a method, device, computer equipment and storage medium for integrally constructing an avionics system graphic element model, which is used to improve the accuracy of the integral construction of the avionics system graphic element model. The main technical solution is as follows: identify object information, relationship information, point information, attribute information and role information from the SysML graphic model; determine the point information and attribute information corresponding to the object information, and determine an object library according to the point information and attribute information corresponding to the object information; determine the role information and attribute information corresponding to the relationship information, and determine a relationship library according to the role information and attribute information corresponding to the relationship information; introduce a target object and the target relationship corresponding to the target object from the object library and the relationship library, and create a graphic element model according to the target object and the target relationship corresponding to the target object.

Description

Technical Field

[0001] The present invention relates to the field of avionics technology, and particularly to a method, device, computer equipment and storage medium for integrally constructing an avionics system graphic element model. Background Art

[0002] Arcadia is an integrated systems engineering modeling method for interdisciplinary activities in complex technical systems, developed by the French aerospace company Thales. Inspired by the Unified Modeling Language (UML) and the Systems Modeling Language (SysML), it provides more effective support for systems engineering teams. Its expert method enables traceability between different engineering levels through automatic information exchange, allowing them to comprehensively manage complexity.

[0003] However, when multiple modeling languages are required for domain modeling in the entire life cycle, heterogeneous data generated by different tools makes tool integration difficult, which will greatly increase the design cost and reduce the model construction efficiency. Summary of the Invention

[0004] The present invention provides a method, device, computer equipment and storage medium for integrally constructing an avionics system graphic element model, which is used to improve the construction efficiency of the avionics system graphic element model.

[0005] An embodiment of the present invention provides a method for integrally constructing an avionics system graphic element model, and the method includes:

[0006] Identifying object information, relationship information, point information, attribute information and role information from the SysML graph model;

[0007] Determining the point information and attribute information corresponding to the object information, and determining an object library according to the point information and attribute information corresponding to the object information;

[0008] Determining the role information and attribute information corresponding to the relationship information, and determining a relationship library according to the role information and attribute information corresponding to the relationship information;

[0009] Introducing a target object and a target relationship corresponding to the target object from the object library and the relationship library, and creating a graphic element model according to the target object and the target relationship corresponding to the target object.

[0010] An embodiment of the present invention provides an apparatus for integrally constructing an avionics system graphic element model, and the apparatus includes:

[0011] An identification module, configured to identify object information, relationship information, point information, attribute information and role information from the SysML graph model;

[0012] A determination module, configured to determine point information and attribute information corresponding to the object information, and determine an object library according to the point information and attribute information corresponding to the object information;

[0013] The determination module is further configured to determine role information and attribute information corresponding to the relationship information, and determine a relationship library according to the role information and attribute information corresponding to the relationship information;

[0014] A creation module, configured to introduce a target object and a target relationship corresponding to the target object from the object library and the relationship library, and create a primitive model according to the target object and the target relationship corresponding to the target object.

[0015] A computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the above-mentioned integrated construction method of the avionics system primitive model is implemented.

[0016] A computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the above-mentioned integrated construction method of the avionics system primitive model is implemented.

[0017] An integrated construction method, device, computer device and storage medium for an avionics system primitive model provided by the present invention identify object information, relationship information, point information, attribute information and role information from the SysML diagram model; determine the point information and attribute information corresponding to the object information, and determine an object library according to the point information and attribute information corresponding to the object information; determine the role information and attribute information corresponding to the relationship information, and determine a relationship library according to the role information and attribute information corresponding to the relationship information; introduce a target object and a target relationship corresponding to the target object from the object library and the relationship library, and create a primitive model according to the target object and the target relationship corresponding to the target object. The present invention realizes the modeling business coverage of the design stage life cycle of the avionics system and the automatic generation of a hierarchical and efficient and accurate modeling framework across multiple disciplines and fields, quickly identifies design inputs and forms a model framework database, thereby greatly improving the construction efficiency of the avionics system primitive model. Description of the Drawings

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

[0019] Figure 1 is a flowchart of an integrated construction method of an avionics system primitive model according to an embodiment of the present invention;

[0020] Figure 2 It is a flowchart of a method for integrally constructing a graphic element model of an avionics system according to an embodiment of the present invention;

[0021] Figure 3 It is a modeling hierarchy diagram according to an embodiment of the present invention;

[0022] Figure 4 It is a system diagram of a graphic element model generation system of an avionics system according to an embodiment of the present invention;

[0023] Figure 5 It is a structural block diagram of a device for integrally constructing a graphic element model of an avionics system according to an embodiment of the present invention;

[0024] Figure 6 It is a schematic diagram of a computer device according to an embodiment of the present invention. Specific embodiments

[0025] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0026] In one embodiment, as Figure 1 and Figure 2 shown, a method for integrally constructing a graphic element model of an avionics system is provided, and the method includes the following steps:

[0027] S10. Identify object information, relationship information, point information, attribute information, and role information from the SysML diagram model.

[0028] It should be noted that all the models established in this embodiment are instantiated from the lowest-level meta-metamodel into a metamodel and then instantiated. As Figure 3As shown in the figure, for the meta - meta model layer, it describes the language features of the modeling itself, that is, it identifies and extracts the most basic attributes in the model and defines them in a standardized way. Therefore, the meta - meta model layer is generally the definition of a certain modeling language itself. It is the smallest component unit of the model, just like the definition of data types such as int and float in the code; the meta - model layer effectively associates the definitions identified by the meta - meta model layer to generate the basic structure of the modeling. The structure contains many different types of meta - meta models; while the model layer endows the meta - model structure with certain business properties, assigns specific values to a certain meta - model structure, thereby realizing the construction of the model. There are many types of model construction. Among them, for the overall design and requirement analysis of the civil aircraft avionics system, the graph model is the most common model type, and SysML is the most common language in the graph model.

[0029] The SysML graph model is a system modeling language that expresses the various characteristics and states of the system in terms of requirements, structure, parameters, and behavior. The model based on the SysML language is mainly a graph model, which can be divided into nine types of graphs: model definition graph, activity graph, parameter graph, requirement graph, sequence graph, internal block graph, package graph, and use case graph. Its advantage is that due to its high flexibility, it can express many elements in the avionics system design process, such as requirements, scenarios, functions, and physics. Its disadvantage is that due to its high generality, when modeling the avionics system, the generality of the SysML class diagram leads to the inability to perform specialized modeling for a certain type of characteristic business. Therefore, in this embodiment, by disassembling and identifying the elements of the SysML - based graph model, a set of meta - meta model - driven methodologies are defined, thereby establishing an integrated special meta - model library for avionics system modeling, and finally realizing the rapid generation of the avionics system graph meta - model.

[0030] Specifically, in this embodiment, point information, attribute information, and role information are identified from the SysML graph model, as follows:

[0031] SysML point information identification: By analyzing the SysML graph model, the corresponding point elements are found. Common point elements in SysML include various interfaces in the module, such as proxy interfaces and complete interfaces, etc.; points are usually considered to be covered in the definition of objects. Therefore, the definition of points generally needs to be completed before defining objects.

[0032] SysML attribute information identification: Identify the attribute information in the SysML model, which usually includes various attributes such as value attributes, flow attributes, composition attributes, and reference attributes in the model. Attributes are generally encompassed by relationships or objects. The definition of attributes needs to be completed before defining relationships or objects.

[0033] SysML Role Information Identification: Identify the roles in the SysML model. Roles are bound to both ends of a relationship and define the characteristics of the source and end objects in the relationship. Therefore, the definition of roles needs to be completed before defining the object relationships in the model.

[0034] Based on a method for constructing a metametamodel, six basic attributes of the metametamodel are established: graph, object, relationship, role, point, and property. The six metametamodels are associated using an extended additional constraint to construct a domain-specific metamodel library. The classification basis of the six metametamodels is as follows, where Extension refers to the additional constraint used to construct the metamodel.

[0035] Graph: A collection of some objects, relationships, and roles used to describe the connection relationships between them. For example, there are nine graphs in SysML, such as the block definition diagram, activity diagram, parameter diagram, and requirement diagram;

[0036] Object: A class with many attributes used to represent an existing object. Relationships can be symbolically expressed. For example, blocks, requirements, states, and packages in SysML are all defined as object attributes;

[0037] Relationship: The connection between two or more objects. A relationship cannot exist independently of an object. An object has many attributes, and a relationship can be symbolically expressed. For example, containment, association, composition, and generalization in SysML are defined as relationships.

[0038] Role: A role is used to connect a component and a relationship. After analyzing the instantiation of the relationship connection in SysML, which objects and points are respectively bound to the corresponding start and end declarations in the relationship. For example, in the interface implementation relationship, the start is the implementation part and the end is the contract; in the usage relationship, the start is the customer and the end is the supplier.

[0039] Point: The symbolic expression of a role. A point cannot exist independently of an object and can also have many attributes. For example, flow interfaces and proxy interfaces in SysML are defined as points.

[0040] Property: A property is used to define and describe the characteristics of some metatypes (objects, roles, points, and relationships). For example, values, flows, constraints, compositions, operations, and references in SysML are defined as graph properties.

[0041] Correspond the above metametamodel elements with the elements in the SysML diagram model as shown in Table 1 below:

[0042] Table 1

[0043]

[0044]

[0045] S20. Determine the point information and attribute information corresponding to the object information, and determine the object library according to the point information and attribute information corresponding to the object information.

[0046] After completing the recognition of the points, attributes, and role information in the SysML model, then based on the above definitions of the graph attributes, points, and role metamodels, the specific steps are as follows:

[0047] (1) Define the graph attributes, points, and role metamodels

[0048] 1) Define the graph attribute library:

[0049] The steps to define the graph attributes are as follows:

[0050] a) Create an empty graph attribute

[0051] b) Add the local name of the graph attribute;

[0052] c) Add the data type of the graph attribute, such as integer, boolean, real, and enumeration, etc.;

[0053] d) Add the unit of this attribute;

[0054] e) Add the attribute description.

[0055] f) Complete and store the current graph attribute definition. If all graph attributes are defined, the tool will automatically store them as the graph attribute library; if not, repeat step a).

[0056] 2) Define points. A point is an end on an object that can be bound to the roles at both ends of a relationship for connection. The point model cannot exist alone and can only appear on an object. The steps to define a point are as follows:

[0057] a) Create an empty point;

[0058] b) Add the local name of the point;

[0059] c) Describe and explain this point;

[0060] d) Set the fixed syntax of the point, that is, the style of the point after graphic instantiation, such as circle, rectangle, and triangle;

[0061] e) Set the graph attribute of the point. This attribute is selected from the constructed attribute metamodel library and referenced as the attribute of this point;

[0062] f) Complete and store the current point definition. If all points are defined, the tool will automatically store them as the point library; if not, repeat step a).

[0063] 3) Define the role meta-model

[0064] a) Create a new blank role meta-model;

[0065] b) Add the local name of the role meta-model;

[0066] c) Add a description for this role meta-model;

[0067] d) Set the direction of the point, set as the start or end point, and this direction is for the relationship;

[0068] e) Set the fixed grammar of the role and the style of the role after graphical instantiation, such as arrows, hollow triangles, and solid triangles, etc.;

[0069] f) Set the graph attributes of the role, which are selected from the constructed attribute meta-model library and referenced as the attributes of this role;

[0070] g) Complete and store the current role meta-model definition. If the role meta-model is completely defined, the tool will automatically store it as a role meta-model library. If not, repeat step a).

[0071] (2) Define object attributes and relationships

[0072] 1) The steps for constructing object attributes are as follows:

[0073] a) Create a new blank object

[0074] b) Add the local name of the object attribute;

[0075] c) Add a description for the object attribute;

[0076] d) Add the fixed grammar of the object attribute, that is, the style of the object attribute, such as rectangles, rounded rectangles, circles, and ellipses, etc.;

[0077] e) Add the points of the object attribute, introduce the already created points from the point library onto the object attribute. When setting, the direction of the point needs to be selected, which includes three categories: input, output, and undirected. If the added point library cannot be found in the point library, return to the point construction step to re-create the points;

[0078] f) Add the attributes of the object attribute, introduce them from the constructed graph attribute library as the attributes of this object. If the added graph attributes cannot be found in the graph attribute library, return to the graph attribute construction step to re-create the graph attributes;

[0079] g) Complete and store the current object attribute definition. If the object attribute is completely defined, the tool will automatically store it as an object attribute library. If not, repeat step a).

[0080] 2) The steps for defining relationships are as follows:

[0081] a) Add a new relationship;

[0082] b) Add a local name for the relationship;

[0083] c) Add a description for the relationship;

[0084] d) Add the fixed grammar of the relationship, i.e., the style of the object property, such as dotted line, solid line, and dashed line, etc.;

[0085] e) Add the properties of the relationship, introduced from the constructed graph property library as the properties of this object. If the added graph properties cannot be found in the graph property library, return to the steps of constructing the graph properties to re - establish the graph properties;

[0086] f) Add the roles of the relationship, introduced from the constructed role meta - model library. The relationship should contain at least one start - end role and one end - role, otherwise the instantiation connection of the relationship cannot be carried out. If the added role meta - model cannot be found in the role meta - model library, return to the steps of constructing the role meta - model to re - establish the role meta - model;

[0087] g) Complete and store the current relationship definition. If all the relationships are defined, the tool will automatically store them in the relationship library. If not, repeat step a).

[0088] S30. Determine the role information and attribute information corresponding to the relationship information, and determine the relationship library according to the role information and attribute information corresponding to the relationship information.

[0089] Specifically, the introduction of the target object and the target relationship corresponding to the target object from the object library and the relationship library includes: in response to the user's object dragging operation, introduce the target object from the object library; in response to the user's relationship dragging operation, introduce the target relationship corresponding to the target object from the relationship library.

[0090] (III) The steps of defining the graph meta - model are as follows:

[0091] 1) Create an empty graph meta - model

[0092] 2) Add the basic information of the graph meta - model

[0093] a) Add a local name for the graph meta - model;

[0094] b) Add a description for this graph meta - model;

[0095] c) Add the properties of the graph meta - model, which are selected from the constructed property meta - model library and referenced as the properties of this graph;

[0096] 3) Add the objects and relationships in the graph meta - model

[0097] a) Import the object to be added from the object property library as a modelable object in the diagram. If there is no such object, go back to the step of "defining object properties" to create a new object.

[0098] b) Import the object to be added from the relationship library as a modelable object in the diagram. If there is no such relationship, go back to the step of "defining object properties" to create a new object.

[0099] 4) Define the binding relationships in the diagram

[0100] a) Define which objects and relationships can be connected to the start and end of the relationship in the primitive model. During the definition process, for the points on the object, the output point of the object can only be bound to the start of the relationship, and the input point can only be bound to the end of the relationship.

[0101] b) After defining the binding relationship in the primitive model, connections can be made in the instantiated model.

[0102] 5) Define the decomposition and sectional view in the diagram

[0103] a) Define the decomposition diagram: The decomposition diagram is the internal graphical description of the next level of the object. Only one instantiated diagram model is allowed to correspond to the decomposition of one object instantiation model component. During the decomposition setting process, select all the primitive models that have been created. Among them, when configuring, multiple primitive models can be configured for the decomposition of one object, but after instantiation, only one decomposition diagram can be added to one object.

[0104] b) The sectional view is the refined description of the object from different angles. Multiple instantiated diagram models are allowed to correspond to the sectional view of one object instantiation model component. During the sectional view setting process, the primitive models of the sectional view are selected from all the primitive models that have been created. When configuring, multiple primitive models can be configured for the sectional view of one object, and after instantiation, the number of sectional views is not limited.

[0105] S40. Import the target object and the target relationship corresponding to the target object from the object library and the relationship library, and create a primitive model according to the target object and the target relationship corresponding to the target object.

[0106] Through the above operations, the generated primitive model can support instantiation operations based on business, such as establishing the functional architecture model of the functional class, the functional decomposition model, etc., the physical architecture model in the physical domain, the assembly model, etc., as well as multi-domain and multi-perspective modeling such as logical domain modeling, so as to realize the integrated modeling and analysis of the avionics system by establishing the above primitive model framework.

[0107] A method for integrally constructing a graphic element model of an avionics system provided by an embodiment of the present invention identifies object information, relationship information, point information, attribute information, and role information from a SysML graphic model; determines the point information and attribute information corresponding to the object information, and determines an object library according to the point information and attribute information corresponding to the object information; determines the role information and attribute information corresponding to the relationship information, and determines a relationship library according to the role information and attribute information corresponding to the relationship information; introduces a target object and a target relationship corresponding to the target object from the object library and the relationship library, and creates a graphic element model according to the target object and the target relationship corresponding to the target object. The present invention realizes the modeling service coverage of the life cycle of the design stage of the avionics system and the automatic generation of a hierarchical and efficient and accurate modeling framework for multiple interdisciplinary fields, quickly identifies design inputs and forms a model framework database, thereby greatly improving the construction efficiency of the avionics system graphic element model.

[0108] The following will illustrate the construction process of the graphic element model by way of example:

[0109] The functional architecture model of an avionics system consists of models based on the SysML language, specifically consisting of a model definition diagram and an internal module diagram. Taking this as the input, the corresponding objects, relationships, roles, points, and attributes are identified based on the integrated modeling method:

[0110] Table 2

[0111]

[0112] Through the above identification, a meta-model library for each point, attribute, role, relationship, and object in the table can be established in the integrated modeling tool, and a new graphic element model named "functional architecture" graphic element model can be established. After introducing the established meta-model and defining the binding relationships in the diagram, and establishing the mechanism of decomposition and cross-section, the generation of the "functional architecture" graphic element model is completed. All elements required for the system to perform functional architecture modeling are encapsulated in this graphic element model. In the specific modeling process, according to the business needs of the system function design, rapid drag-and-drop construction of objects and relationships in the diagram, as well as rapid setting of attributes, can be performed. Such a construction method can be applied to the system design stage of the system, scenario, function, logical and physical modeling, and can also be applied to the assembly manufacturing modeling in the manufacturing stage and the service model construction in the operation and maintenance stage. Therefore, it is a process for forming an integrated modeling throughout the entire life cycle of the avionics system.

[0113] In an optional embodiment provided by the present invention, the avionics system graphic element model generation system is as Figure 4 shown, and this system includes:

[0114] Meta-model generator: used to generate meta-model data.

[0115] Machine learning development library: Provides a variety of machine learning algorithms to achieve capabilities such as inference and prediction.

[0116] Framework generator: Can generate a system based on the OWL language, including operation scenarios, functional architecture, logical architecture, and physical architecture model frameworks.

[0117] Ontology conversion module: Realizes the bidirectional conversion between ontology and model, ontology and metamodel, and ontology and modeling framework.

[0118] Text parser: Parses the input text for knowledge extraction.

[0119] Model parser: Parses the input model for data extraction.

[0120] The platform is divided into an application layer, a storage layer, a data layer, and a physical layer. Among them, the application layer processes high-level applications such as the construction of a modeling framework. The storage layer stores business and semantic data in a standardized database. The data layer processes text data and model data, and can convert the data for which the model framework has been built to an external model (SysML, Modelica).

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

[0122] In one embodiment, a device for integrated construction of a graphic element model of an avionics system is provided. This device for integrated construction of a graphic element model of an avionics system corresponds one-to-one with the method for integrated construction of a graphic element model of an avionics system in the above embodiment. As Figure 5 shown, this device for integrated construction of a graphic element model of an avionics system includes: an identification module 10, a determination module 20, and a creation module 30. The detailed description of each functional module is as follows:

[0123] The identification module 10 is used to identify object information, relationship information, point information, attribute information, and role information from the SysML graphic model;

[0124] The determination module 20 is used to determine the point information and attribute information corresponding to the object information, and determine an object library according to the point information and attribute information corresponding to the object information;

[0125] The determination module 20 is further used to determine the role information and attribute information corresponding to the relationship information, and determine a relationship library according to the role information and attribute information corresponding to the relationship information;

[0126] The creation module 30 is used to introduce the target object and the target relationship corresponding to the target object from the object library and the relationship library, and create a primitive model according to the target object and the target relationship corresponding to the target object.

[0127] In an optional embodiment provided by the present invention, the creation module 30 is specifically configured to:

[0128] Create an empty graph attribute, and set the attribute information of the graph attribute, and store the attribute information of the graph attribute in the graph attribute library;

[0129] Create an empty point, and set the point information and graph attribute of the point, and store the point information and graph attribute of the point in the point library correspondingly;

[0130] Create an empty role, and set the role information and graph attribute of the role, and store the role information of the role and the graph attribute in the role primitive model library correspondingly.

[0131] In an optional embodiment provided by the present invention, the creation module 30 is specifically configured to:

[0132] Create an empty object, and set the object information of the object;

[0133] Select the point of the object from the point library, and select the role of the object from the role primitive model library;

[0134] Store the object information, point and role corresponding to the object in the object library.

[0135] In an optional embodiment provided by the present invention, the creation module 30 is specifically configured to:

[0136] Create an empty relationship, and set the relationship information of the relationship;

[0137] Select the graph attribute corresponding to the relationship from the graph attribute library, and select the role corresponding to the relationship from the role model library;

[0138] Store the relationship information, graph attribute and role corresponding to the relationship in the relationship library.

[0139] In an optional embodiment provided by the present invention, the creation module 30 is specifically configured to:

[0140] In response to the user's object dragging operation, introduce the target object from the object library;

[0141] In response to the user's relationship dragging operation, introduce the target relationship corresponding to the target object from the relationship library.

[0142] In an alternative embodiment provided by the present invention, the SysML diagram model is used to describe the connection relationships among objects, relationships, and roles. The SysML diagram model at least includes: module definition diagram, activity diagram, parameter diagram, requirement diagram, sequence diagram, internal block diagram, package diagram, state machine diagram, use case diagram.

[0143] In an alternative embodiment provided by the present invention, the creating module 30 is further configured to:

[0144] Define the decomposition diagram and sectional view of the target object.

[0145] For the specific limitations of the integrated avionics system graphic element model construction device, reference can be made to the limitations on the integrated avionics system graphic element model construction method in the foregoing text, which will not be elaborated here. Each module in the above-mentioned integrated avionics system graphic element model construction device can be implemented in whole or in part by software, hardware, and their combination. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or stored in the memory of the computer device in the form of software, so as to facilitate the processor to call and execute the operations corresponding to the above-mentioned each module.

[0146] In one embodiment, a computer device is provided. The computer device can be a server, and its internal structure diagram can be as Figure 6 shown. The computer device includes a processor, a memory, a network interface, and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, it implements an integrated avionics system graphic element model construction method.

[0147] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, the following steps are implemented:

[0148] Identify object information, relationship information, point information, attribute information, and role information from the SysML diagram model;

[0149] Determine the point information and attribute information corresponding to the object information, and determine an object library according to the point information and attribute information corresponding to the object information;

[0150] Determine the role information and attribute information corresponding to the relationship information, and determine a relationship library according to the role information and attribute information corresponding to the relationship information;

[0151] Introduce a target object and a target relationship corresponding to the target object from the object library and the relationship library, and create a graphic primitive model according to the target object and the target relationship corresponding to the target object.

[0152] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0153] Identify object information, relationship information, point information, attribute information, and role information from the SysML graphic model;

[0154] Determine the point information and attribute information corresponding to the object information, and determine an object library according to the point information and attribute information corresponding to the object information;

[0155] Determine the role information and attribute information corresponding to the relationship information, and determine a relationship library according to the role information and attribute information corresponding to the relationship information;

[0156] Introduce a target object and a target relationship corresponding to the target object from the object library and the relationship library, and create a graphic primitive model according to the target object and the target relationship corresponding to the target object.

[0157] Those of ordinary skill in the art can understand that all or part of the processes of implementing the methods in the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, storage, database, or other medium used in the various embodiments provided in the present application can include non-volatile and / or volatile memories. Non-volatile memories can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memories can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM), etc.

[0158] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be allocated to different functional units and modules as needed, that is, the internal structure of the device is divided into different functional units or modules to complete all or part of the functions described above.

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

Claims

1. An integrated construction method for avionics system graphic element models, characterized in that The method includes: Identifying object information, relationship information, point information, attribute information, and role information from the SysML diagram model; the object information is used to represent an existing object; the relationship information is used to represent the connection between two or more objects; the point information is the interface information in the SysML diagram model; the attribute information is the function information in the SysML model; the role information defines the characteristics of the source and end objects in the SysML model relationship in the relationship. Determining the point information and attribute information corresponding to the object information, and determining an object library according to the point information and attribute information corresponding to the object information. Determining the role information and attribute information corresponding to the relationship information, and determining a relationship library according to the role information and attribute information corresponding to the relationship information. Introducing a target object and the target relationship corresponding to the target object from the object library and the relationship library, and creating a primitive model according to the target object and the target relationship corresponding to the target object. The method further includes: creating an empty diagram attribute, setting the attribute information of the diagram attribute, and storing the attribute information of the diagram attribute in a diagram attribute library; creating an empty point, setting the point information and diagram attribute of the point, and storing the point information and diagram attribute of the point in a point library correspondingly; creating an empty role, setting the role information and diagram attribute of the role, and storing the role information and the diagram attribute of the role in a role primitive model library correspondingly; creating an empty object, and setting the object information of the object; selecting the point of the object from the point library, and selecting the role of the object from the role primitive model library; storing the object information, point, and role corresponding to the object in the object library. Creating an empty relationship, and setting the relationship information of the relationship; selecting the diagram attribute corresponding to the relationship from the diagram attribute library, and selecting the role corresponding to the relationship from the role model library; storing the relationship information, diagram attribute, and role corresponding to the relationship in the relationship library.

2. The method according to any one of claims 1, characterized in that, The introducing a target object and the target relationship corresponding to the target object from the object library and the relationship library includes: In response to a user's object dragging operation, introducing a target object from the object library. In response to a user's relationship dragging operation, introducing the target relationship corresponding to the target object from the relationship library.

3. The method according to claim 2, characterized in that, The SysML diagram model is used to describe the connection relationship between objects, relationships, and roles, and the SysML diagram model at least includes: module definition diagram, activity diagram, parameter diagram, requirement diagram, sequence diagram, internal module diagram, package diagram, state machine diagram, use case diagram.

4. The method according to claim 2, characterized in that The method further includes: Defining a decomposition diagram and a sectional view of the target object.

5. An integrated construction device for an avionics system graphic element model, characterized in that, The device includes: An identification module, configured to identify object information, relationship information, point information, attribute information, and role information from a SysML diagram model; the object information is used to represent an existing object; the relationship information is used to represent the connection between two or more objects; the point information is the interface information in the SysML diagram model; the attribute information is the function information in the SysML model; the role information defines the characteristics of the source and end objects in the SysML model relationship in the relationship. A determination module, configured to determine the point information and attribute information corresponding to the object information, and determine an object library according to the point information and attribute information corresponding to the object information. The determination module is further configured to determine the role information and attribute information corresponding to the relationship information, and determine a relationship library according to the role information and attribute information corresponding to the relationship information. A creation module, configured to introduce a target object and the target relationship corresponding to the target object from the object library and the relationship library, and create a graphic primitive model according to the target object and the target relationship corresponding to the target object. The creation module is further configured to: Create an empty graphic attribute, and set the attribute information of the graphic attribute, and store the attribute information of the graphic attribute in a graphic attribute library; create an empty point, and set the point information and graphic attribute of the point, and store the point information and graphic attribute of the point in a point library in a corresponding manner; create an empty role, and set the role information and graphic attribute of the role, and store the role information and the graphic attribute of the role in a role original model library in a corresponding manner; create an empty object, and set the object information of the object; select the point of the object from the point library, and select the role of the object from the role original model library; store the object information, point, and role corresponding to the object in the object library. Create an empty relationship, and set the relationship information of the relationship; select the graphic attribute corresponding to the relationship from the graphic attribute library, and select the role corresponding to the relationship from the role model library; store the relationship information, graphic attribute, and role corresponding to the relationship in the relationship library.

6. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the integrated construction method of the avionics system graphic primitive model according to any one of claims 1 to 4.

7. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the integrated construction method of the avionics system graphic primitive model according to any one of claims 1 to 4.

Images