Spaceflight equipment modeling language design method based on meta-meta model

Abstract

The invention provides an aerospace equipment modeling language design method based on a meta-meta model, and belongs to the technical field of model-based system engineering. The method comprises the following steps: S1, carrying out a classification mapping process of aerospace equipment multi-system and multi-disciplinary design information and a GOPPRR-E meta-model, and constructing a complete meta-model library of GOPPRR-E; s2, classifying according to a general design meta-model, a professional design meta-model and a model design meta-model to form a combination and reuse relationship between meta-model reuse libraries, and constructing a multi-level meta-model reuse library; and S3, organizing and instantiating the multi-level meta-model in the multi-level meta-model reuse library according to the aerospace equipment model design requirements and the demand-function-logic-physical design process, and constructing the aerospace equipment multi-architecture model library. By the adoption of the aerospace equipment modeling language design method based on the meta-meta model, the complexity in the aerospace equipment design process can be dealt with, and the design efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of model-based system engineering, and in particular to a method for designing a modeling language for aerospace equipment based on a meta-meta model. Background Art

[0002] With the continuous evolution of space exploration mission requirements, the design complexity of components, interfaces, etc. in the existing aerospace equipment design process has increased exponentially, which has brought challenges to the cognitive load of designers and forced the design mode of aerospace equipment to transform from a document-based system engineering design mode to a model-based system engineering design mode. Model-based Systems Engineering (MBSE) supports formalization, modeling, design, analysis and verification in the entire life cycle of product and system development through models, providing solutions to the development challenges of complex systems. However, the most mainstream MBSE modeling language for aerospace equipment is the SysML modeling language. Although the language provides a limited number of metamodels, it can describe the requirements, behaviors, components and performance of aerospace equipment by combining metamodels in a graphical modeling way. However, its abstract and simplified characteristics still require engineers to manually identify and establish the conversion relationship between multi-system and multi-disciplinary design information of aerospace equipment and SysML modeling symbols in the process of engineering application. In addition, there is a phenomenon of design information loss in the process of expressing design information of different disciplines through the same modeling elements, and there are problems of inaccurate modeling expression and incomplete discipline information, as follows: (1) Information identification and conversion are difficult, resulting in a lack of information for system design.

[0003] When converting multi-system and multi-disciplinary design information to SysML modeling symbols, engineers need to manually identify and establish conversion relationships. For example, when performing physical architecture analysis on a launch vehicle system during the design process, engineers need to identify the physical interaction process of the system, which may involve interactions between different disciplines, such as mechanics, electronics, and software. The results of physical interaction analysis are usually represented by SysML's internal module diagram, in which physical elements in different fields are associated with other elements through interfaces. This manual conversion process is complex and error-prone, especially when it comes to design information from different disciplines. It is difficult to ensure that all details can be accurately captured and expressed, which can easily lead to loss and incompleteness of information.

[0004] (2) The model syntax is rigidified, which leads to ambiguity in the expression of system modeling.

[0005] Aerospace equipment design involves multiple disciplines, each of which has its own specific design language and process. SysML, as a general modeling language, needs to be able to express the design information of these different fields. However, due to the relatively rigid syntax and semantics of SysML, it may not be able to flexibly adapt to the characteristics of different disciplines. An aerospace equipment project may involve multiple disciplines such as aerodynamic design, structural strength, thermal, and electronic control. Each discipline has its own modeling tools and analysis methods. For example, mechanical engineers may use specific CAD tools to design component mechanical structures, while software engineers may use different programming languages ​​and platforms to develop electronic control systems. As a modeling language, SysML only provides a limited set of models, such as requirement diagrams, model definition diagrams, and other nine basic diagram types of SysML modeling languages. However, in the actual modeling process, these model diagrams cannot cover the customized modeling representation of multi-disciplinary knowledge and multi-behavior architectures such as aerodynamics, structure, and electronic control in the design process of aerospace equipment systems. For example, when designing a launch vehicle, it is necessary to use a module definition diagram to analyze the context of the launch vehicle. However, when decomposing system indicators, the module definition diagram is also used to analyze the relevant parameter indicators of the launch vehicle. The two behaviors are represented by the same view, but the underlying logic between the two behaviors, such as context analysis and parameter indicator decomposition, is quite different, which leads to the model being ambiguous when expressing system architecture information and unable to accurately express the system architecture. Therefore, in the process of modeling aerospace equipment systems, a modeling language with good extensibility and support for customization is needed.

[0006] Based on the actual problems and urgent needs of modeling in the field of aerospace equipment using the existing SysML metamodel, a modeling language for aerospace equipment is urgently needed to promote the development of the field. Summary of the invention

[0007] The purpose of the present invention is to provide a method for designing a modeling language for aerospace equipment based on a meta-meta model, which can cope with the complexity of the aerospace equipment design process and improve the design efficiency.

[0008] To achieve the above object, the present invention provides a method for designing a modeling language for aerospace equipment based on a meta-meta model, comprising the following steps: Step S1, carry out the classification mapping process between multi-system and multi-disciplinary design information of aerospace equipment and GOPPRR-E meta-metamodel, and build a complete meta-model library of GOPPRR-E; Step S2: Based on the complete metamodel library of GOPPRR-E, the library is classified into general design metamodel, professional design metamodel and model design metamodel to form the combination and reuse relationship between the metamodel reuse libraries and construct a multi-level metamodel reuse library; Step S3: According to the design requirements of aerospace equipment models and the demand-function-logic-physical design process, organize and instantiate the multi-level metamodels in the multi-level metamodel reuse library, and build a multi-architecture model library for aerospace equipment based on multi-domain metamodels such as parameters, structure, and power.

[0009] Preferably, in step S1, the GOPPRR-E meta-meta model includes seven elements: graph, object, point, attribute, relationship, role, and extension.

[0010] Preferably, in step S1, the metamodel library of GOPPRR-E includes a graph metamodel, an object metamodel, a point metamodel, an attribute metamodel, a relationship metamodel, a role metamodel and extensions, which are used to define the composition, internal interaction interface relationships and attribute characteristics of multiple systems of aerospace equipment.

[0011] Preferably, the seven basic meta-metamodel elements are instantiated through the GOPPRR-E modeling method, and all metamodel instance definitions are completed through the form-based navigation configuration window of the metamodel definition in the MetaGraph modeling tool.

[0012] Preferably, the graph metamodel is used to define the overall structure in the system; the object metamodel is used to abstractly describe the entities in the graph metamodel instance; the point metamodel refers to the abstract description of the interface in the object metamodel instance that is connected to the relationship metamodel and the role metamodel instance; the attribute metamodel refers to the abstract description of the attribute characteristics of the graph metamodel, object metamodel, relationship metamodel, role metamodel and point metamodel; the relationship metamodel refers to the abstract description of the association relationship between object metamodel instances; the role metamodel is an abstract description of how the relationship metamodel instance is connected to the object metamodel instance; and the extension is an abstract description of the association rules and constraints between the graph metamodel, object metamodel, relationship metamodel, role metamodel, point metamodel and attribute metamodel.

[0013] Preferably, in step S2, the general design metamodel is used to describe basic modeling elements widely used in the process of aerospace equipment development.

[0014] Preferably, in step S2, the professional design metamodel supports customized design of metamodels in specific fields.

[0015] Preferably, in step S2, the model design metamodel is customized based on the general design metamodel and the professional design metamodel.

[0016] Preferably, in step S3, the requirement-function-logic-physical design process includes four steps: requirement analysis, function analysis, logical architecture design and physical architecture design, and supports and implements model construction at different design levels by reusing and organizing the existing metamodel library.

[0017] Preferably, the aerospace equipment multi-architecture model library includes multi-domain metamodels: power metamodel, structural metamodel and overall parameter metamodel; multi-level metamodels: general design metamodel, professional design metamodel and model design metamodel.

[0018] Therefore, the present invention adopts the above-mentioned aerospace equipment modeling language design method based on the meta-meta model, and the beneficial technical effects are as follows: (1) The present invention is developed based on the KARMA language and GOPPRR-E modeling mechanism. By using the seven types of GOPPRR-E (graph-object-point-attribute-relationship-role-extension) meta-model elements, a multi-system and multi-disciplinary model in the field of aerospace equipment can be accurately constructed. It has a high degree of abstraction and flexibility, can cope with the complexity of different disciplines and systems, and solves the limitations of the SysML modeling language in expressing multi-disciplinary information.

[0019] (2) The present invention supports unified modeling of multiple disciplines and systems. Through the combination of GOPPRR-E meta-metamodels, the design information of multiple fields such as mechanical, electrical, hydraulic, and control in aerospace equipment systems can be accurately described. The knowledge and information of each system and discipline can be accurately captured and expressed. Through the unified modeling of multidisciplinary information, the ambiguity problem of SysML in multidisciplinary modeling is avoided. It can not only describe the physical composition of aerospace equipment, but also express its internal interaction relationships and technical parameters, ensuring the accuracy of model expression.

[0020] (3) The present invention provides an extensible modeling language. The design method based on the meta-meta model allows users to customize the meta-model according to different needs and subject characteristics, forming a modeling language that adapts to various mission requirements. The high extensibility enables it to adapt to the design requirements of different types of aerospace equipment, supports the expansion and customization from general design meta-models to specialized design meta-models, and ensures the reusability and adaptability of the model.

[0021] (4) The present invention constructs a multi-level metamodel reuse library for aerospace equipment systems, including a multi-level metamodel reuse library for general design metamodels, professional design metamodels, and model design metamodels, providing a structured and modular metamodel collection. This multi-level metamodel reuse library can be reused in different design tasks, reducing duplication of work, improving design efficiency, and ensuring seamless integration between different subsystems through standardized interfaces and interaction modes. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 Schematic diagram of a design method framework for aerospace equipment modeling language based on meta-meta model. DETAILED DESCRIPTION

[0023] The technical solution of the present invention is further described below through the accompanying drawings and embodiments.

[0024] Unless otherwise defined, technical or scientific terms used in the present invention shall have the common meanings understood by one having ordinary skills in the field to which the present invention belongs.

[0025] The meta-metamodel is composed of the description of the structure and semantics of meta-metadata, and is an abstract language defined to describe the meta-model. The definition of the meta-metamodel is more abstract and concise than the meta-model (that is, the meta-metamodel is a deeper level of abstraction about the meta-metadata itself, that is, it is an abstraction that describes the meta-metadata). A meta-metamodel can define multiple meta-models, and a meta-model is an instance of a meta-metamodel.

[0026] Based on the concept of meta-metamodel, the present invention determines the basic elements required for designing aerospace equipment systems, and then constructs an aerospace equipment modeling language based on metamodel representation. The modeling process follows the modeling theory of GOPPRR-E meta-metamodel, that is, first define the meta-metamodel of the model, then combine the meta-metamodel to define the metamodel, use the metamodel to define a specific domain model, and describe the model layer of the aerospace equipment system through different model combinations.

[0027] Embodiment 1 like Figure 1 FIG. 1 is a schematic diagram of a design method framework of aerospace equipment modeling language based on a meta-meta model of the present invention, which includes the following steps: Step S1, by carrying out the classification mapping process between multi-system and multi-disciplinary design information of aerospace equipment and GOPPRR-E meta-meta-model, a complete meta-model library of GOPPRR-E meta-meta-model and the association relationship between meta-models are constructed.

[0028] According to the seven types of meta-meta-model elements provided by the GOPPRR-E modeling theory, namely graph, object, relationship, attribute, point, role, and extension, combined with the analysis of multi-system and multi-disciplinary design information of aerospace equipment, a complete meta-model library of multi-systems of aerospace equipment and the association relationship between meta-models are formed by constructing a classification mapping between aerospace equipment design information and GOPPRR-E meta-meta-model.

[0029] The complete metamodel library of aerospace equipment system includes graph metamodel, object metamodel, relationship metamodel, point metamodel, attribute metamodel, role metamodel and extension.

[0030] According to the GOPPRR-E modeling theory, the graph metamodel is used to define the overall structure of aerospace equipment multi-system. It is an abstract description of the modeling and design process of aerospace equipment multi-system. It is an element formed by at least one combination of object metamodel, relationship metamodel, attribute metamodel, point metamodel, and role metamodel. For example, aerospace equipment systems include but are not limited to "launch vehicle system", "satellite system", "manned spacecraft system", "unmanned probe system", "space telescope system", etc., all of which have certain internal components. "Launch vehicle system" may include "compressor", "hydraulic pump", "cable network" and other specific components; "satellite system" may include "solar panel", "signal transmitter" and other specific components. Due to the differences in the components of each system field, it is necessary to use a unified "physical composition diagram" graph metamodel to describe the components, interface relationships and other elements contained therein in a unified manner. Therefore, the “physical composition diagram” meta-model includes but is not limited to “launch vehicle” and other object meta-model instances to represent the actual components of the aerospace equipment system; “pneumatic interaction”, “hydraulic interaction”, “electrical interaction”, “signal interaction” and other relationship meta-model instances to describe the interaction between the components of the aerospace equipment; “pneumatic interaction start” and “pneumatic interaction end” and other role meta-model instances to describe the beginning and end of the interaction between the components of the aerospace equipment; “pneumatic port”, “hydraulic port”, “electrical port”, “signal port” and other point meta-model instances to describe the types of aerospace equipment interaction interfaces; “thrust”, “momentum”, “weight”, “volume flow rate”, “compression ratio” and other attribute meta-model instances to describe the key technical parameters and other attributes of the components of the aerospace equipment. Meta-model instances are used to describe the composition of the aerospace equipment system and the internal interaction interface relationship. They are an abstract description of the actual engineering products of the aerospace equipment and are the elements of the collection of the other five meta-model instances.

[0031] According to the GOPPRR-E modeling theory, the object metamodel is used to abstractly describe the entities in the metamodel instance, as well as to describe the start and end of the task. For example, the object metamodel instance contains several point metamodel instances and / or several attribute metamodel instances. The object metamodel instance is mainly used to describe the components of aerospace equipment products, and abstractly describe a certain entity in the metamodel instance. For example, it includes but is not limited to typical object metamodel instances in aerospace equipment systems such as "accumulator", "controller", "sensor", "turbo pump" and "main valve" and other elements. Among them, taking the "turbo pump" as an example, the "turbo pump" is a rectangular box containing a turbine and fuel pump device icon, which represents a specific device in the aerospace equipment system that provides the required propellant pressure and flow for the engine.

[0032] According to the GOPPRR-E modeling theory, the point metamodel refers to the abstract description of the interface in the object metamodel instance that is connected to the relationship / role metamodel instance. The interface refers to the way in which the object metamodel instance transmits matter or information to the outside world under specific conditions. The point metamodel instance is used to describe the interface types and interactive things that interact between the actual components of aerospace equipment products. For example, the engine subsystem generates a lot of heat during operation. This heat needs to interact with external substances through the cooling system to maintain the normal operating temperature of the engine. Therefore, there is heat interaction between the engine subsystem and the outside world. Therefore, the engine subsystem has the "hot port" metamodel element. At the same time, the point metamodel instance cannot exist alone and must be attached to the object metamodel instance.

[0033] According to the GOPPRR-E modeling theory, the attribute metamodel refers to the abstract description of the attribute characteristics of the graph metamodel, object metamodel, relationship metamodel, role metamodel and point metamodel. In the process of instantiating the attribute metamodel to the attribute metamodel, only the attribute metamodel itself is established, and the attribute metamodel does not contain any other metamodel. Therefore, the attribute metamodel instance is used to describe the attributes of aerospace equipment and define the relevant units and dimensional attributes of each attribute. For example, for the object metamodel instance of the engine system turbopump, its typical attribute metamodel instances include volume flow rate (pumping speed), maximum flow, critical fore-stage pressure, compression ratio, base pressure, etc. At the same time, when describing the attribute metamodel instance, it cannot exist alone and must be attached to the other five metamodel instances.

[0034] According to the GOPPRR-E modeling theory, the relational metamodel refers to an abstract description of the association relationship between object metamodel instances, which is associated with the object metamodel instance through the role metamodel instance. In the process of instantiating the relational metamodel to the relational metamodel, the relational metamodel allows the simultaneous inclusion of the role and attribute metamodels. The instance of the relational metamodel can represent the information, energy, and material interaction relationship between object metamodel instances. For example, typical relational metamodel instances describing aerospace equipment include force interaction relationships, hydraulic interaction relationships, signal interaction relationships, and pneumatic interaction relationships.

[0035] According to the GOPPRR-E modeling theory, the role metamodel is an abstract description of how the relational metamodel instance is connected to the object metamodel instance. In the process of instantiating the role metamodel to the role metamodel, in addition to the need to establish the role metamodel itself, the role metamodel can contain the attribute metamodel. The role metamodel instance is used to describe the type and method of input and output of the information transmission relationship between the different components of the actual product. The role metamodel instance is an abstract description of how the relational metamodel instance is connected to the object metamodel instance. For example, typical role metamodel instances include the start and end of "force interaction", "hydraulic interaction" and "signal interaction".

[0036] According to the GOPPRR-E modeling theory, extension is an abstract description of the association rules and constraints between the graph metamodel, object metamodel, relationship metamodel, role metamodel, point metamodel, and attribute metamodel. In the process of instantiation of extension, only the association rules and constraints between the six types of metamodels are established, and the extension does not include any other metamodel. The rules and constraints defined by the extension instance include inclusion, attribute, binding link, decomposition, and sectioning. The inclusion rule describes the inclusion relationship between the graph and the object and relationship; the attribute rule describes the ownership relationship between the other five non-attribute metamodels and the attribute; the binding link rule describes the constraint mode between the object or point and the role metamodel and the constraint mode between the role and the relationship metamodel; the decomposition rule describes that an instance of an object / point / relationship metamodel can be decomposed into a graph instance with an equivalence relationship, and the internal composition of the object / point / relationship metamodel instance is described in detail; the sectioning rule describes that an instance of an object / relationship / point / role metamodel can be sectioned into multiple graph instances from different perspectives, indicating that the graph instance is a detailed description of a certain perspective section of the object (or relationship, point, role) instance.

[0037] Furthermore, seven basic meta-metamodel elements are instantiated through the GOPPRR-E modeling method, and all metamodel instance definitions are completed through the form-based navigation configuration window of the metamodel definition in the MetaGraph modeling tool.

[0038] Step S2, classify according to general design metamodel, professional design metamodel, and model design metamodel, form the combination and reuse relationship between the above metamodel reuse libraries, build a multi-level metamodel reuse library, and finally form a modeling language (SEML) for aerospace equipment.

[0039] The multi-level metamodel reuse library of the modeling language for aerospace equipment is a modular and structured metamodel collection that supports the design and development process of aerospace equipment systems. It is a cluster formed by the combination of general design metamodels, professional design metamodels, and model design metamodels.

[0040] The general design metamodel is used to describe the basic modeling elements widely used in the development of aerospace equipment, that is, to build the basic framework in the development of aerospace equipment: the general design metamodel provides the basic structure and general concepts of the aerospace equipment system, and all professional design metamodels and model design metamodels are expanded and customized based on this basic structure. For example, a typical satellite architecture general metamodel can include abstract definitions of subsystems such as communication, control, and structure. At the same time, by defining standardized interfaces and interaction modes in the general metamodel, it ensures that designs of different professions and models can be seamlessly integrated. For example, the interfaces between all subsystems and the satellite main control system are defined in the general model. Typical interfaces include "signal ports" and "mechanical ports" to ensure interoperability between subsystems.

[0041] The professional design metamodel supports the customized design of metamodels in specific fields. It helps designers to quickly respond to different mission requirements. The professional design metamodel is an extension of the general design metamodel in specific fields. For example, the professional metamodel of the propulsion subsystem of the launch vehicle can be refined in the propulsion subsystem part of the general satellite architecture metamodel to define detailed properties such as thrust, fuel consumption, and engine type. At the same time, the professional design metamodel has high reusability, and a professional design metamodel can be reused in multiple projects or models. For example, the professional design metamodel of the communication system can be applied to multiple different types of spacecraft (such as communication satellites, navigation satellites, etc.) by making a small amount of customization in the model design metamodel, realizing the wide applicability of the professional metamodel. In addition, the professional design metamodel and the general design metamodel can also be associated through inheritance, extension, and combination. For example, the professional design metamodel of the control system can expand the control subsystem part of the general satellite architecture model to specifically implement functions such as attitude adjustment and orbit control.

[0042] The model design metamodel is customized based on the general design metamodel and the professional design metamodel to reflect the needs of a specific project. For example, a communications satellite may need to customize an antenna of a specific frequency or a thruster of a specific power according to mission requirements. Although the model design metamodel has low reusability, it can be directly reused in subsequent iterative designs of the same model. For example, a certain model of rocket can reuse most of the propulsion system design in subsequent improved versions, and only partial adjustments need to be made to meet new requirements. At the same time, the model design metamodel is the model closest to actual implementation and is usually associated with specific simulation, optimization, and verification tools. By inheriting and combining general and professional metamodels, the model design metamodel can be optimized based on existing designs and verified through simulation tools.

[0043] Furthermore, general design metamodels, professional design metamodels and model design metamodels are classified to construct a metamodel reuse library for aerospace equipment, which ensures design consistency through modularization and standardization and supports the expansion and evolution of complex systems.

[0044] Step S3, according to the design requirements of aerospace equipment models and in accordance with the demand-function-logic-physical design process, organize and instantiate the multi-level meta-models in the aerospace equipment modeling language (SEML) meta-model reuse library, and build a multi-architecture model library for aerospace equipment based on multi-domain meta-models such as power, structure, and overall parameters, to achieve a comprehensive and systematic expression of all-factor design information of aerospace equipment.

[0045] The overall design process based on the Requirements-Function-Logical-Physical (RFLP) model has the following main functions: (1) Requirements analysis: Analyze the requirements of stakeholders, including but not limited to design requirements, customer requirements, technical specifications, etc., and finally decompose the requirements into the engineering information of specific products. For example, by analyzing the load requirements and economic requirements in the launch vehicle system requirements, the carrying capacity in the system performance indicators and the reuse function in the functional requirements are clarified, and the complete traceability of the requirements is achieved. (2) Functional analysis: The essence of function is demand, which is a set of requirements formed after being systematically integrated and abstracted according to the relevance of requirements. Functions clarify the tasks of product or system development from a holistic perspective and clearly define the functions and interactions provided by the system. For example, the orbit injection requirements in the launch vehicle system requirements can be decomposed into functions such as thrust provision and attitude control. (3) Logical architecture design: The logical architecture is between the functional and physical implementation architectures. It is the logical implementation method of the functional architecture. It mainly considers which logical components and interactions are used to implement the functions required in the functional architecture. It is a technology-neutral solution and does not specify the specific technical implementation method. For example, from the perspective of physical architecture, the launch vehicle system includes basic components such as the escape tower, life support system, and return capsule for rockets that perform manned space missions; and high-thrust engines and payload cabins for rockets that perform satellite launch missions. From the perspective of logical architecture, the logical components of rockets that perform manned space missions and rockets that perform satellite launch missions are basically the same. They both require an energy source (such as fuel and oxidizer) to power the propulsion system through an interface; a propulsion system (such as an engine) to generate thrust; a control system (such as a navigation and attitude control system) to receive and process attitude signal data through a control interface to ensure that the rocket flies according to the predetermined trajectory, and a structural system (such as a rocket body structure) to carry all these systems and protect the internal equipment. Therefore, the logical architecture does not specify the technical implementation methods, but only looks at how to solve the problem from a logical perspective, and describes the system logical component structure and the interaction between logical components. (4) Physical architecture design: The physical architecture aims to further clarify the physical or technical implementation methods corresponding to the logical components. It requires identifying specific software or hardware components, interface signals, etc., and mapping logical architecture components to corresponding physical architecture components to achieve physical realization. For example, in the overall design of a launch vehicle, its logical architecture design may include the following components: a propulsion subsystem, which is responsible for managing the control and scheduling of rocket propulsion; a navigation and control subsystem: ensuring that the rocket flies according to the predetermined orbit and making dynamic corrections.In the physical architecture of the launch vehicle, the components in the logical architecture are mapped to specific physical implementations. The propulsion subsystem is mapped to liquid rocket engines and solid rocket engines, which are responsible for the thrust output of the rocket; the navigation and control subsystem is mapped to the inertial measurement unit (IMU) and the flight control computer, which obtains the attitude and position data of the rocket through accelerometers, gyroscopes and other devices, and adjusts the direction of the nozzle through the flight control computer. The energy source is mapped to the rocket fuel tank, which is responsible for providing continuous and stable energy for the launch vehicle. The overall design process based on the requirements-function-logic-physical (RFLP) model helps engineers start from requirements and functions and gradually refine them to specific physical implementations, thereby ensuring the operability and feasibility of the system.

[0046] In the overall design process based on the requirements-function-logic-physical (RFLP) model, the model construction at different design levels can be supported and realized by reusing and organizing the existing metamodel library. The reusable metamodel library is a collection of verified general metamodels, professional metamodels, and model metamodels. For example, the standard general metamodels in the design of launch vehicles include but are not limited to the propulsion module metamodel, navigation module metamodel, communication module metamodel, structure module metamodel, thermal control module metamodel, control module metamodel, power module metamodel, etc., which can be directly used in the design of new aerospace equipment. At the same time, in order to achieve a comprehensive and systematic expression of aerospace equipment design, a multi-domain aerospace equipment multi-architecture model library is constructed, including but not limited to: Power model library: covers physical and logical metamodels related to the propulsion system, such as different types of engines, fuel management systems, pressurization and delivery systems, propellants, fuel storage tanks, etc. Structural model library: covers the structural metamodels of rockets or satellites, such as material selection: aluminum alloy, stainless steel, etc.; structural design: sandwich structure, tank structure, composite material structure, etc.; thermal control system: passive thermal control subsystem, active thermal control subsystem, fluid circuit and convection ventilation system, etc. Overall parameter model library: covers the overall parameters and performance indicators of the entire aerospace equipment, such as launch mass, orbital parameters, life, orbital accuracy, carrying capacity, heat exchange, thrust, etc. Based on multi-domain meta-models such as power, structure, and overall parameters and multi-level meta-model reuse libraries, a multi-architecture model library for aerospace equipment is constructed to achieve a comprehensive and systematic expression of all-factor design information and ensure the consistency and reliability of the design.

[0047] It is worth noting that the contents not elaborated in detail in the present invention are all prior art and are well known to those skilled in the art.

[0048] Therefore, the present invention adopts the above-mentioned aerospace equipment modeling language design method based on meta-meta model, and uses the seven types of meta-meta model elements of graph-object-point-attribute-relationship-role-extension (GOPPRR-E) provided by the KARMA language to accurately and completely construct model element information of multiple disciplines such as mechanical-electrical-hydraulic-control and multi-system scales such as engineering overall-system-subsystem-equipment-component-parameter of aerospace equipment, which can solve the problems of inaccurate modeling expression and incomplete subject information in the existing MBSE modeling process using the SysML modeling language.

[0049] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that they can still modify or replace the technical solution of the present invention with equivalents, and these modifications or equivalent replacements cannot cause the modified technical solution to deviate from the spirit and scope of the technical solution of the present invention.

Claims

1. A method for designing a modeling language for aerospace equipment based on a meta-meta model, characterized in that: The following steps are involved: Step S1, carry out the classification mapping process between multi-system and multi-disciplinary design information of aerospace equipment and GOPPRR-E meta-metamodel, and build a complete meta-model library of GOPPRR-E; Step S2: Based on the complete metamodel library of GOPPRR-E, the library is classified into general design metamodel, professional design metamodel and model design metamodel to form the combination and reuse relationship between the metamodel reuse libraries and construct a multi-level metamodel reuse library; Step S3: According to the design requirements of aerospace equipment models and the demand-function-logic-physical design process, organize and instantiate the multi-level metamodels in the multi-level metamodel reuse library to build a multi-architecture model library for aerospace equipment.

2. The method for designing a modeling language for aerospace equipment based on a meta-meta model according to claim 1, characterized in that: In step S1, the GOPPRR-E meta-metamodel includes seven elements: graph, object, node, attribute, relationship, role, and extension.

3. The method for designing a modeling language for aerospace equipment based on a meta-meta model according to claim 1, characterized in that: In step S1, the metamodel library of GOPPRR-E includes graph metamodel, object metamodel, point metamodel, attribute metamodel, relationship metamodel, role metamodel and extensions, which are used to define the composition, internal interaction interface relationships and attribute characteristics of multiple systems of aerospace equipment.

4. The method for designing a modeling language for aerospace equipment based on a meta-meta model according to claim 3, characterized in that: Seven basic meta-metamodel elements are instantiated through the GOPPRR-E modeling method, and all metamodel instance definitions are completed through the form-based navigation configuration window of the metamodel definition in the MetaGraph modeling tool.

5. The method for designing a modeling language for aerospace equipment based on a meta-meta model according to claim 4, characterized in that: The graph metamodel is used to define the overall structure of the system; the object metamodel is used to abstractly describe the entities in the graph metamodel instance; the point metamodel refers to the abstract description of the interface connecting the object metamodel instance with the relationship metamodel and role metamodel instance; the attribute metamodel refers to the abstract description of the attribute characteristics of the graph metamodel, object metamodel, relationship metamodel, role metamodel and point metamodel; The relational metamodel refers to an abstract description of the associations between object metamodel instances; the role metamodel is an abstract description of how relational metamodel instances are connected to object metamodel instances; Extension is an abstract description of the association rules and constraints between the graph metamodel, object metamodel, relationship metamodel, role metamodel, point metamodel, and attribute metamodel.

6. The method for designing a modeling language for aerospace equipment based on a meta-meta model according to claim 1, characterized in that: In step S2, the general design metamodel is used to describe the basic modeling elements widely used in the process of aerospace equipment development.

7. The method for designing a modeling language for aerospace equipment based on a meta-meta model according to claim 1, characterized in that: In step S2, the professional design metamodel supports the customized design of metamodels in specific fields.

8. The method for designing a modeling language for aerospace equipment based on a meta-meta model according to claim 1, characterized in that: In step S2, the model design metamodel is customized based on the general design metamodel and the professional design metamodel.

9. The method for designing a modeling language for aerospace equipment based on a meta-meta model according to claim 1, characterized in that: In step S3, the requirement-function-logic-physical design process includes four steps: requirement analysis, function analysis, logical architecture design, and physical architecture design. It supports and implements model construction at different design levels by reusing and organizing the existing meta-model library.

10. The method for designing a modeling language for aerospace equipment based on a meta-meta model according to claim 1, characterized in that: The multi-architecture model library of aerospace equipment includes multi-domain meta-models: power meta-model, structural meta-model and overall parameter meta-model; Multi-level metamodel: general design metamodel, professional design metamodel, model design metamodel.

Images