CN112068830B - Avionics system architecture model-oriented design tool - Google Patents
Avionics system architecture model-oriented design tool Download PDFInfo
- Publication number
- CN112068830B CN112068830B CN202010810662.0A CN202010810662A CN112068830B CN 112068830 B CN112068830 B CN 112068830B CN 202010810662 A CN202010810662 A CN 202010810662A CN 112068830 B CN112068830 B CN 112068830B
- Authority
- CN
- China
- Prior art keywords
- model
- plug
- model element
- relation
- type
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000013461 design Methods 0.000 title claims abstract description 59
- 238000011161 development Methods 0.000 claims abstract description 16
- 238000013507 mapping Methods 0.000 claims description 35
- 238000000034 method Methods 0.000 claims description 25
- 230000008569 process Effects 0.000 claims description 20
- 230000005540 biological transmission Effects 0.000 claims description 4
- 230000006870 function Effects 0.000 description 12
- 230000018109 developmental process Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 10
- 230000000694 effects Effects 0.000 description 8
- 230000033772 system development Effects 0.000 description 4
- 230000028654 Type IV pili-dependent aggregation Effects 0.000 description 3
- 238000012938 design process Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004132 cross linking Methods 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 230000008570 general process Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/35—Creation or generation of source code model driven
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a design tool for an avionics system architecture model, which comprises a general modeling and plug-in engine module, a plug-in set design module and a plug-in set configuration module; the plugin set configuration module provides the function of creating and modifying configuration files for users; wherein the configuration file is used for describing rules of the model; the general modeling and plug-in engine module transmits package folders, model views and/or model elements in the model according to the request of the plug-in set design module; and the plug-in set design module invokes the configuration file to carry out compliance check on the request after receiving the secondary development request of the package folder, the model view and/or the model element, and then completes secondary development on the received package folder, model view and/or model element. The invention enables the avionics system developer to follow the development standard under the guidance of the design tool, and can rapidly customize the avionics system architecture model by expanding development or modifying configuration files.
Description
Technical Field
The invention relates to the field of avionics system architecture model design, in particular to a design tool for an avionics system architecture model.
Background
The avionics system of modern civil aircraft is a complex system, the cross-linking subsystem is numerous, and the transmission signal is complex, so that the development of the avionics system becomes a complex project. The avionics system architecture is used for identifying system functions, defining logical interfaces and determining physical implementation, and is a key link in avionics system development activities and is a key success key of avionics system development. Currently, the design process of the avionics system architecture is complex, a development thought based on a model is generally adopted, the design process is modeled by utilizing the standard of an architecture model design tool, and the standardization and consistency of architecture design data are ensured. The market does not lack design tools for the architecture model, however, the design tools are all based on a general modeling language, only support a general modeling process, and developing complex avionics system architecture design modeling based on the general process is often inefficient and cannot meet the specific requirements of the avionics system architecture model design process. Therefore, in order to implement the modeling process for the avionics system architecture model under the premise of considering the development cost of the tool, the design tool needs to be customized based on a commercial universal modeling tool.
Disclosure of Invention
In order to support the requirements of the design of the avionics system architecture model, the invention aims to provide a design tool for the avionics system architecture model. And under the guidance of the design tool, the avionics system developer follows the development specification, and can quickly customize the avionics system architecture model by expanding development or modifying the configuration file.
The invention aims at realizing the following technical scheme:
a design tool for avionics system architecture model comprises a general modeling and plug-in engine module 3, a plug-in set design module 2 and a plug-in set configuration module 1;
the plugin set configuration module 1 provides the function of creating and modifying configuration files for users; wherein the configuration file is used for describing rules of the model;
the general modeling and plug-in engine module 3 delivers package folders, model views and/or model elements in the model according to the request of the plug-in set design module 2;
and the plugin set design module 2 invokes the configuration file to carry out compliance check on the request after receiving the secondary development request of the package folder, the model view and/or the model element, and then completes secondary development on the received package folder, model view and/or model element.
Further, the plug-in set configuration module 1 provides a type matching configuration interface of the model view and the model elements, so that a user agrees on a matching relationship of the model view and the types of the model elements, prevents certain types of model elements from being in certain types of model views, and generates a type matching configuration file of the model view and the model elements after the user finishes agreements;
the plug-in set design module 2 comprises an avionics system module automatic creation plug-in 21, and the operation process is as follows:
step 1-1: reading the model view and model elements from the generic modeling and plug-in engine module 3 according to user selections;
step 1-2: confirming a request of a mapping relation between the created or modified model view and the model element;
step 1-3: judging whether the types of the selected model view and model elements accord with the type matching relation or not by utilizing a type matching configuration file of the model view and the module elements of the plug-in set configuration module 1, and mapping the model elements accord with the type matching relation into the selected model view;
step 1-4: the mapping relation between the created or modified model view and the model element is stored in a table dedicated to the mapping relation in the general modeling and plug-in engine module 3.
Further, the plug-in set configuration module 1 provides a parent-child level applicable type configuration interface for enabling a user to agree on a matching relationship between the type of the model element and the type of the parent-level model element of the model element, prevents creation of a parent-child relationship of the model element which does not accord with the agreement, and generates a parent-child level applicable type configuration file after the agreement is completed;
the plug-in set design module 2 comprises an avionics system port automatic creation plug-in 24, and the operation process is as follows:
step 2-1: reading model elements from the universal modeling and plug-in engine module 3 according to user selection, judging the number of the model elements selected by the user, such as single model elements, and entering step 2-2A; if a plurality of model elements are adopted, the step 2-2B is carried out;
step 2-2A: confirming a request for creating a port model element;
step 2-3A: judging whether a parent level model element exists in the model element or not from a parent level model element field of the model element; if the parent level model element exists, the pop-up dialog box interface records the name of the port model element input by the user, and the step 2-4A is entered;
step 2-4A: judging whether the type of the selected model element and the type of the parent-level model element of the model element accord with the range of the parent-child-level applicable type or not by utilizing the parent-child-level applicable type configuration file of the plug-in set configuration module 1, and creating a port model element on the model element accord with the range;
step 2-5A: storing the name, ID and father level model element of the newly created port model element as records back into the fields of the model element exclusive table of the database or engineering file;
step 2-2B: confirming a request for creating a port model element;
step 2-3B: taking a first selected model element in the selection sequence of the model elements as a sending source end and taking a subsequently selected model element as a receiving terminal;
step 2-4B: judging whether each model element has a parent level model element or not from a parent level model element field of the model element; if the parent level model element exists, the step 2-5B is entered:
step 2-5B: judging whether the type of the selected model element and the type of the parent-level model element of the model element accord with the range of the parent-child-level applicable type or not by utilizing the parent-child-level applicable type configuration file of the plug-in set configuration module 1, and creating a port model element on the model element accord with the range;
step 2-6B: the name, ID, parent level model element of the newly created port class model element is stored as a record back into a field of the model element specific table of the database or engineering file.
Further, the plug-in set configuration module 1 provides a type matching configuration interface of the source end and the terminal, so that a user agrees with a matching relation between the type of the model element of the source end and the type of the model element of the receiving terminal, creation of a model data stream which does not accord with the agreement is prevented, and a type matching configuration file of the source end and the terminal is generated after the user finishes the agreement;
the plug-in set design module 2 comprises an avionics system connection relation automatic creation plug-in 22, and the operation process is as follows:
step 3-1: on the basis of automatically creating port model elements created by the plug-in 24 at the port of the avionics system, judging whether the types of the selected transmission source end and the selected receiving terminal model elements accord with the matching relationship between the source end and the terminal by using the type matching configuration file of the source end and the terminal of the plug-in set configuration module 1, and creating connection relationship model elements among the port model elements in the accord range;
step 3-2; and storing the name, ID data and parent level model elements of the newly created connection relation class model as records back into fields of a model element exclusive table of a database or an engineering file.
Further, the plug-in set configuration module 1 provides a model view configuration interface matched with the model elements, so that a user agrees with a model view range applicable to one model element; generating a model view configuration file matched with the model elements after completing the agreement;
the plug-in set design module 2 comprises an avionics system architecture view automatic creation plug-in 25, and the operation process is as follows:
step 4-1: obtaining model elements from the generic modeling and plug-in engine module according to user selections;
step 4-2: confirming a request for creating a model view;
step 4-3: creating a model view matched with the model element by using a model view configuration file matched with the model element of the plugin set configuration module 1;
step 4-4: the name, ID of the newly created model view is stored as a record back into a field of the model view specific table of the database or engineering file.
Further, the plugin set configuration module 1 provides a mapping relation configuration interface of the display content and the model content, so that a user agrees on the mapping relation between the relation structure of the element relation tree and the model content, the mapping relation configuration interface is used for limiting the normalized expression relation of the model data stream, and a mapping relation configuration file of the display content and the model content is generated after the agreement is completed;
the plug-in set design module 2 comprises an avionics system element relation display plug-in 23, and the operation process is as follows:
step 5-1: obtaining model elements from the generic modeling and plug-in engine module 3 according to user selections;
step 5-2: confirming the element relation display request;
step 5-3: reading parent level model element information of the model element from a database or a field of a model element exclusive table in the engineering file by utilizing an element relation tree relation structure and model content mapping relation defined in a mapping relation configuration file of display content and model content of the plugin set configuration module 1;
step 5-4: the drive generic modeling and plug-in engine module 3 presents the results at the modeling interface.
Further, the plug-in set configuration module 1 provides a configuration interface of the matching relation between the model element types and the package folder paths, so that a user can agree on the positions of the model element types in the package folder, and a configuration file of the matching relation between the model element types and the package folder paths is generated after the agreement is completed;
the plug-in set design module 2 comprises an avionics system architecture model element automatic collection plug-in 26, and the operation process is as follows:
step 6-1: obtaining model elements from the generic modeling and plug-in engine module 3 according to user selections;
step 6-2: confirming the model element automatic collection request;
step 6-3: and moving the selected model element to the designated package folder according to the package folder path matching relation to which the model element type defined by the model element type and the package folder path matching relation configuration file should be moved.
The invention has the beneficial effects that:
the plug-in frame is fully aimed at the field characteristics of avionics system architecture model design, is favorable for rapid customization of avionics system development projects, comprehensively meets the specific requirements of avionics system architecture model design, and has high use value.
Drawings
FIG. 1 is a schematic diagram of a design tool for an avionics system architecture model in accordance with an exemplary embodiment.
FIG. 2 is an example of a model organization in a user interface.
The avionics system module shown in figure 3 automatically creates a flow schematic of the plug-in 21,
FIG. 4 is a model reveal effect after execution of the avionics system module auto-creation plug-in 21.
FIG. 5 is a schematic flow diagram of an avionics system port auto-creation plug-in 24.
FIG. 6 is a model reveal effect after execution of the avionics system port auto-creation plug-in 24.
FIG. 7 is a schematic flow diagram of an avionics system connection auto-creation plug-in 22.
FIG. 8 is a model presentation effect after execution of the avionics system connection automatic creation plug-in 22.
FIG. 9 is a flow diagram of an avionics system architecture view auto-creation plug-in 25.
FIG. 10 is a view of the avionics system architecture after execution of the auto-creation plug-in 25.
FIG. 11 is a schematic flow diagram of avionics system element relationship display plug-in 23.
FIG. 12 is a model reveal effect after execution of the avionics system element relationship display plug-in 23.
FIG. 13 is a schematic flow diagram of the avionics system architecture model element auto-aggregation plug-in 26.
Detailed Description
The invention is described in further detail below with reference to the drawings and examples.
The design tool for the avionics system architecture model shown in this embodiment includes three modules: the general modeling and plug-in engine module 3, the plug-in set design module 2 and the plug-in set configuration module 1.
Plug-in set configuration module
The plug-in configuration module 1 provides the user with the functionality to create and modify configuration files. The configuration file essentially defines rules describing the model for normalizing description and storage of avionics system architecture model data.
The plug-in set configuration module 1 provides the following configuration interfaces to the user:
model view and model element type matching configuration interface: the matching relation between the model view and the model element types is agreed by the user, so that the model element types which are not concerned by the user are prevented from being appeared in the specific model view. The model view and module type matching relation configuration interface generates a type matching configuration file of the model view and the module element after the user completes the appointment.
Parent-child level applicable type configuration interface: the matching relationship between the types of the model elements and the types of the parent-level model elements of the model elements is agreed by the user, so that the creation of the parent-child relationship of the model elements which do not accord with the agreement is prevented. The parent-child level applicable type configuration interface generates a parent-child level applicable type configuration file after the user completes the appointment.
Type matching configuration interface of source end and terminal: the user agrees with the matching relation between the type of the model element of the sending source end and the type of the model element of the receiving terminal, and the creation of the model data stream which does not accord with the agreement is prevented. The type matching configuration interface of the source end and the terminal generates a type matching configuration file of the source end and the terminal after the user completes the appointment.
Model view configuration interface matching model elements: the user is provided with a model view range applicable to a model element; the model view configuration interface matched with the model element generates a model view configuration file matched with the model element after the user completes the appointment.
Mapping relation configuration interface of display content and model content: the mapping relation between the relation structure of the element relation tree and the model content is agreed by a user and is used for limiting the normalized expression relation of the model data stream; and the mapping relation configuration interface of the display content and the model content generates a mapping relation configuration file of the display content and the model content after the user completes the appointment.
Model element type and package folder path matching relation configuration interface: the user is provided with a placement position for specifying the model element type in the package folder. And the model element type and package folder path matching relation configuration interface generates a model element type and package folder path matching relation configuration file after the user completes the appointment.
(II) general modeling and plug-in Engine Module
The general modeling and plug-in engine module 3 adopts a third-party commercial modeling tool, and the third-party commercial modeling tool supports a user to secondarily develop a basic model in a plug-in mode, so that industrialization and specialized customization of a user interface, an application program and the like are realized. Third party business modeling tools typically consist of interface presentation functions (including modeling interfaces, model operation interaction interfaces, plugin management interfaces, user menu interfaces, etc.), application support functions (including model parsing and rendering engines, message management mechanism engines, plugin engines, etc.), and data resource functions (including model databases, model engineering files, etc.). Referring to FIG. 2, the built model of such third party business modeling tools is generally organized as follows:
which package folders are contained in a model;
which model views and model elements are contained in the package folder, and the parent-child layer relationships between model elements in the model views. The types of model elements comprise functional modules, ports, connection relations, the model elements are located in package folders, but not necessarily appear in the model view, the model elements appear in the model view as a mapping of model elements in the model view.
The basic model established in the modeling interface by the user is usually stored in a model database or a model engineering file matched with a third-party commercial modeling tool, and the contents of the model database or the model engineering file record are as follows:
package folder: the method comprises the steps of storing the information in a special table of a package folder, wherein the information such as the name, ID, father package folder and the like of the package folder is recorded in a field of the table;
model view: the method comprises the steps of storing in a table exclusive to a model view, wherein the fields of the table record information such as the name, ID, belonging package folder and the like of the model view;
model element: the method comprises the steps of storing in a table exclusive to model elements, wherein the fields of the table record information such as names, IDs, parent-level model elements, belonging package folders and the like of the model elements;
mapping relation between model view and model element: the mapping relation between the model view ID and the model element ID is recorded in a table special for the mapping relation.
(III) plug-in set design Module
Referring to fig. 1, after receiving a secondary development request of a package folder, a model view and/or a model element, the plugin set design module invokes a configuration file to perform compliance check on the request, and then completes secondary development of the received package folder, model view and/or model element. The package design module 2 provides six sub-packages, which should be used in accordance with the following sequence requirements:
1. the avionics system connection relationship auto-creation plug-in 22 should be used after the avionics system port auto-creation plug-in 24.
2. Avionics system element relationship display plug-in 23 should be used after avionics system connection relationships automatically create plug-in 22.
3. The other sub-plug-ins can be used as required
Each sub-plug-in is described in detail as follows:
the avionics system module automatically creates plug-ins 21: the function of creating a map of the specified model element in the specified model view is realized. The functional modules of the plug-in built model for expressing avionics systems may appear in different model views to provide different products. Referring to the flow chart of the avionics system module automatic creation plug-in 21 shown in FIG. 3, the specific process is as follows:
step 1-1: reading the model view and model elements from the generic modeling and plug-in engine module 3 according to user selections;
step 1-2: confirming a request of a mapping relation between the created or modified model view and the model element;
step 1-3: judging whether the types of the selected model view and model elements accord with the type matching relation or not by utilizing a type matching configuration file of the model view and the module elements of the plug-in set configuration module 1, and mapping the model elements accord with the type matching relation into the selected model view;
step 1-4: the mapping relation between the created or modified model view and the model element is stored in a special table of the mapping relation in the general modeling and plug-in engine module 3, and the result is displayed on the modeling interface, and the display effect is shown in fig. 4.
Avionics system port auto-creation plug-in 24: the method realizes the functions of automatically creating ports at the designated sub-level modules and automatically creating the ports of the corresponding parent level modules, and the functions of automatically creating the ports of the two sub-level modules and all the parent level modules traversed by the connection relationship when the connection relationship is established between the designated two sub-level modules. The avionics system port automatically creates a plug-in built model for expressing ports of sub-level functional modules of avionics system products and also has matched ports in parent level functional modules. Because the avionics system architecture design is decomposed layer by layer, the functional modules gradually increase downwards according to the level, the interface relation between the high-level modules is summarized, and the method is more suitable for port matching coordination between the level suppliers. Referring to the flow chart of the avionics system port auto-creation plug-in 24 shown in FIG. 5, the specific process is as follows:
step 2-1: reading model elements from the universal modeling and plug-in engine module 3 according to user selection, judging the number of the model elements selected by the user, such as single model elements, and entering step 2-2A; if a plurality of model elements are adopted, the step 2-2B is carried out;
step 2-2A: confirming a request for creating a port model element;
step 2-3A: judging whether a parent level model element exists in the model element or not from a parent level model element field of the model element; if the parent level model element exists, the pop-up dialog box interface records the name of the port model element input by the user, and the step 2-4A is entered;
step 2-4A: judging whether the type of the selected model element and the type of the parent-level model element of the model element accord with the range of the parent-child-level applicable type or not by utilizing the parent-child-level applicable type configuration file of the plug-in set configuration module 1, and creating a port model element on the model element accord with the range;
step 2-5A: finally, the name, ID and father level model element of the newly created port model element are used as records to be stored back into the fields of the model element exclusive table of the database or the engineering file, and the results are displayed on the modeling interface of the universal modeling and plug-in engine module 3, and the display results are shown in figure 6.
Step 2-2B: confirming a request for creating a port model element;
step 2-3B: taking a first selected model element in the selection sequence of the model elements as a sending source end and taking a subsequently selected model element as a receiving terminal;
step 2-4B: judging whether each model element has a parent level model element or not from a parent level model element field of the model element; if the parent level model element exists, the step 2-5B is entered:
step 2-5B: judging whether the type of the selected model element and the type of the parent-level model element of the model element accord with the range of the parent-child-level applicable type or not by utilizing the parent-child-level applicable type configuration file of the plug-in set configuration module 1, and creating a port model element on the model element accord with the range;
step 2-6B: the name, ID, and parent level model elements of the newly created port class model elements are stored as records back into fields of the model element specific table of the database or engineering file, and the results are presented at the modeling interface of the generic modeling and plug-in engine module 3, with the display results shown in fig. 6.
Avionics system connection automatically creates plug-ins 22: the connection relation between ports is automatically created for two designated model elements by matching with the avionics system port automatic creation plug-in 24. The model created by the plug-in is used for expressing the interaction relation between the functions of the avionics system product. Referring to the flow chart of the avionics system connection automatic creation plug-in 22 shown in FIG. 7, the specific process is as follows:
step 3-1: on the basis of automatically creating port model elements created by the plug-in 24 at the port of the avionics system, judging whether the types of the selected transmission source end and the selected receiving terminal model elements accord with the matching relationship between the source end and the terminal by using the type matching configuration file of the source end and the terminal of the plug-in set configuration module 1, and creating connection relationship model elements among the port model elements in the accord range;
step 3-: the name, ID data and father level model elements of the newly created connection relation model are stored back as records into the fields of the model element exclusive table of the database or engineering file, and the results are displayed on the modeling interface of the general modeling and plug-in engine module 3, and the display effect is shown in fig. 8.
Avionics system architecture view auto-creation plug-in 25: after a certain model element is specified, other model views applicable to the specified model element are automatically created; the avionics system architecture view automatic creation plug-in built model is used for providing different view types for different view angles expressing avionics system product functions and providing a displayed view for subsequent model creation. Referring to the flow diagram of the avionics system architecture view auto-creation plug-in 25 shown in FIG. 9, the specific process is as follows:
step 4-1: obtaining model elements from the generic modeling and plug-in engine module according to user selections;
step 4-2: confirming a request for creating a model view;
step 4-3: creating a model view matched with the model element by using a model view configuration file matched with the model element of the plugin set configuration module 1;
step 4-4: the name and ID of the newly created model view are stored as records back into fields of the model view specific table of the database or engineering file, and the results are presented at the modeling interface of the generic modeling and plug-in engine module 3, the presented results being shown in fig. 10.
Avionics system element relationship display plug-in 23: the connection relation display of the avionics system module and other model elements is realized until the end point of the connection relation is reached, and the positioning is carried out in the model diagram after the model elements are selected by a support user; the model display interface content realized by the plug-in is used for facilitating a user to quickly acquire the position of the module in the avionics system interface interaction scene, further knowing detailed model information through model positioning on an object of interest, and is particularly suitable for complex avionics system architecture models with huge model quantity. Referring to the flow diagram of the avionics system element relationship display plug-in 23 shown in FIG. 11, the specific process is as follows:
step 5-1: obtaining model elements from the generic modeling and plug-in engine module 3 according to user selections;
step 5-2: confirming the element relation display request;
step 5-3: reading parent level model element information of the model element from a database or a field of a model element exclusive table in the engineering file by utilizing an element relation tree relation structure and model content mapping relation defined in a mapping relation configuration file of display content and model content of the plugin set configuration module 1;
step 5-4: the driving general modeling and plug-in engine module 3 presents the result at the modeling interface, and the presentation effect is shown in fig. 12.
Avionics system architecture model element auto-aggregation plug-in 26: the model elements of the specified type are collected into the specified package folder. In general, when a model element is created, a third-party modeling tool is only stored in a model package folder which is currently opened by a user, so that a model organization structure is disordered, and subsequent model data reading and analysis are inconvenient to develop based on the model. Referring to the flow diagram of the avionics system architecture model element auto-aggregation plug-in 26 shown in FIG. 13, the specific process is as follows:
step 6-1: obtaining model elements from the generic modeling and plug-in engine module 3 according to user selections;
step 6-2: confirming the model element automatic collection request;
step 6-3: the selected model elements are moved to a designated package folder according to the package folder path matching relation to which the model element types defined by the model element types and the package folder path matching relation configuration file should be moved, and the model elements conforming to the type matching relation are moved to the designated package folder;
step 6-4: the results are presented at the modeling interface of the generic modeling and plug-in engine module 3.
Under the avionics system architecture oriented model shown in this embodiment, a user may implement customization of avionics system architecture modeling in the following manner:
1. the general modeling and plug-in engine module 3 is driven to develop architecture design modeling by directly using the function custom configuration file provided by the plug-in set configuration module 1 and the plug-ins provided by the plug-in set design module 2;
2. modifying the function custom configuration file provided by the plug-in set configuration module 1, driving the universal modeling and plug-in engine module 3 through the plug-in set design module 2, and realizing architecture design modeling aiming at a specific avionics system development project;
3. and the plug-in set design module 2 after the secondary development and the combined calling drives the universal modeling and plug-in engine module 3 to realize the architecture design modeling with higher integration level.
It will be understood that equivalents and modifications will occur to those skilled in the art in light of the present invention and their spirit, and all such modifications and substitutions are intended to be included within the scope of the present invention as defined in the following claims.
Claims (7)
1. A design system for avionics system architecture model comprises a general modeling and plug-in engine module, a plug-in set design module and a plug-in set configuration module;
the plugin set configuration module provides the function of creating and modifying configuration files for users; wherein the configuration file is used for describing rules of the model, and comprises:
the model view and model element type matching configuration file is used for appointing the matching relation between the model view and the model element types and preventing certain model elements from appearing in certain model views;
the parent-child level applicable type configuration file is used for appointing the matching relation between the types of the model elements and the types of the parent-level model elements of the model elements and preventing the creation of the parent-child relation of the model elements which do not accord with appointments;
the source end and the type of the terminal are matched with a configuration file, which is used for appointing the matching relation between the type of the model element of the source end and the type of the model element of the receiving terminal, so as to prevent the creation of a model data stream which does not accord with the appointments;
the model view configuration file is matched with the model elements and is used for appointing a model view range applicable to one model element;
the mapping relation configuration file of the display content and the model content is used for agreeing the mapping relation between the relation structure of the element relation tree and the model content and limiting the standardized expression relation of the model data stream;
the model element type and package folder path matching relation configuration file is used for appointing the placement position of the model element type in the package folder;
the general modeling and plug-in engine module transmits package folders, model views and/or model elements in the model according to the request of the plug-in set design module;
and the plug-in set design module invokes the configuration file to carry out compliance check on the request after receiving the secondary development request of the package folder, the model view and/or the model element, and then completes secondary development on the received package folder, model view and/or model element.
2. The design system for the avionics system architecture model according to claim 1, wherein the plugin set configuration module provides a model view and model element type matching configuration interface for a user to agree on a matching relationship between model views and model element types, prevents certain model elements from appearing in certain model views, and generates a model view and module element type matching configuration file after the user finishes agreements;
the plug-in set design module comprises an avionics system module and automatically creates plug-ins, and the operation process is as follows:
step 1-1: reading the model view and the model elements from the universal modeling and plug-in engine module according to user selection;
step 1-2: confirming a request of a mapping relation between the created or modified model view and the model element;
step 1-3: judging whether the types of the selected model view and model elements accord with the type matching relation or not by utilizing a model view of the plug-in set configuration module and a type matching configuration file of the module elements, and mapping the model elements accord with the type matching relation into the selected model view;
step 1-4: and storing the mapping relation between the created or modified model view and the model element into a table special for the mapping relation in the general modeling and plug-in engine module.
3. The design system for the avionics system architecture model according to claim 1, wherein the plug-in set configuration module provides a parent-child level applicable type configuration interface for a user to agree on a matching relationship between a type of a model element and a type of a parent-level model element of the model element, prevents creation of a parent-child relationship of the model element which does not conform to the agreement, and generates a parent-child level applicable type configuration file after the agreement is completed;
the plug-in set design module comprises an avionics system port automatic creation plug-in, and the operation process is as follows:
step 2-1: reading model elements from the universal modeling and plug-in engine module according to user selection, judging the number of the model elements selected by the user, such as single model elements, and entering step 2-2A; if a plurality of model elements are adopted, the step 2-2B is carried out;
step 2-2A: confirming a request for creating a port model element;
step 2-3A: judging whether a parent level model element exists in the model element or not from a parent level model element field of the model element; if the parent level model element exists, the pop-up dialog box interface records the name of the port model element input by the user, and the step 2-4A is entered;
step 2-4A: judging whether the type of the selected model element and the type of the parent-level model element of the model element accord with the range of the parent-child level applicable type or not by utilizing a parent-child level applicable type configuration file of the plug-in set configuration module, and creating a port model element on the model element accord with the range;
step 2-5A: storing the name, ID and father level model element of the newly created port model element as records back into the fields of the model element exclusive table of the database or engineering file;
step 2-2B: confirming a request for creating a port model element;
step 2-3B: taking a first selected model element in the selection sequence of the model elements as a sending source end and taking a subsequently selected model element as a receiving terminal;
step 2-4B: judging whether each model element has a parent level model element or not from a parent level model element field of the model element; if the parent level model element exists, the step 2-5B is entered:
step 2-5B: judging whether the type of the selected model element and the type of the parent-level model element of the model element accord with the range of the parent-child level applicable type or not by utilizing a parent-child level applicable type configuration file of the plug-in set configuration module, and creating a port model element on the model element accord with the range;
step 2-6B: the name, ID, parent level model element of the newly created port class model element is stored as a record back into a field of the model element specific table of the database or engineering file.
4. A design system for an avionics system oriented architecture model of claim 3, wherein; the plug-in set configuration module provides a type matching configuration interface of the source end and the terminal, so that a user agrees with a matching relation between the type of the model element of the source end and the type of the model element of the receiving terminal, creation of a model data stream which does not accord with agreement is prevented, and a type matching configuration file of the source end and the terminal is generated after the user finishes the agreement;
the plug-in set design module comprises an avionics system connection relation automatic creation plug-in, and the operation process is as follows:
step 3-1: on the basis of automatically creating port model elements created by plug-ins on an avionics system port, judging whether the types of the selected transmission source end and the selected receiving terminal model elements accord with the matching relationship between the source end and the terminal by using a type matching configuration file of the source end and the terminal of a plug-in set configuration module, and creating connection relationship model elements among the port model elements in a coincidence range;
step 3-2; and storing the name, ID data and parent level model elements of the newly created connection relation class model as records back into fields of a model element exclusive table of a database or an engineering file.
5. The design system for avionics system architecture models of claim 1, wherein the plug-in configuration module provides a model view configuration interface for matching model elements for a user to agree on a model view range for which the model elements are applicable; generating a model view configuration file matched with the model elements after completing the agreement;
the plug-in set design module comprises an avionics system architecture view automatic creation plug-in, and the operation process is as follows:
step 4-1: obtaining model elements from the generic modeling and plug-in engine module according to user selections;
step 4-2: confirming a request for creating a model view;
step 4-3: creating a model view matched with the model element by using a model view configuration file matched with the model element of the plugin set configuration module;
step 4-4: the name, ID of the newly created model view is stored as a record back into a field of the model view specific table of the database or engineering file.
6. The design system for avionics system architecture model according to claim 1, characterized in that the plugin set configuration module provides a mapping relation configuration interface of display content and model content for a user to agree on a mapping relation between a relation structure of an element relation tree and the model content, and is used for defining a normalized expression relation of a model data stream and generating a mapping relation configuration file of the display content and the model content after the agreement is completed;
the plug-in set design module comprises an avionics system element relation display plug-in, and the operation process is as follows:
step 5-1: obtaining model elements from the generic modeling and plug-in engine module according to user selections;
step 5-2: confirming the element relation display request;
step 5-3: reading parent level model element information of the model element from a database or a field of a model element exclusive table in an engineering file by utilizing an element relation tree relation structure and model content mapping relation defined in a mapping relation configuration file of display content and model content of a plugin set configuration module;
step 5-4: the general modeling and plug-in engine module is driven to display the result on the modeling interface.
7. The design system for avionics system architecture model according to claim 1, wherein the plugin set configuration module provides a configuration interface for matching relationship between model element types and package folder paths, for a user to agree on the placement of the model element types in the package folder, and generates a configuration file for matching relationship between the model element types and the package folder paths after the agreement is completed;
the plug-in set design module comprises an avionics system architecture model element automatic collection plug-in, and the operation process is as follows:
step 6-1: obtaining model elements from the generic modeling and plug-in engine module according to user selections;
step 6-2: confirming the model element automatic collection request;
step 6-3: and moving the selected model element to the designated package folder according to the package folder path matching relation to which the model element type defined by the model element type and the package folder path matching relation configuration file should be moved.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010810662.0A CN112068830B (en) | 2020-08-13 | 2020-08-13 | Avionics system architecture model-oriented design tool |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010810662.0A CN112068830B (en) | 2020-08-13 | 2020-08-13 | Avionics system architecture model-oriented design tool |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112068830A CN112068830A (en) | 2020-12-11 |
| CN112068830B true CN112068830B (en) | 2024-03-15 |
Family
ID=73661599
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010810662.0A Active CN112068830B (en) | 2020-08-13 | 2020-08-13 | Avionics system architecture model-oriented design tool |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112068830B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116204962B (en) * | 2023-03-08 | 2023-09-12 | 北京市建筑设计研究院有限公司 | BIM-based structural design method |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1480133A2 (en) * | 2003-05-22 | 2004-11-24 | Cognos Incorporated | System and method for the development of data models |
| CN104123133A (en) * | 2014-07-01 | 2014-10-29 | 曾安里 | Dragon VVR-VBF modularization development framework platform tool system |
| CN106933570A (en) * | 2017-02-16 | 2017-07-07 | 北京临近空间飞行器系统工程研究所 | Hair control software platform is surveyed in a kind of space flight based on plug-in part technology |
| CN110865942A (en) * | 2019-11-12 | 2020-03-06 | 中国航空无线电电子研究所 | Model rule checking method of comprehensive modular avionics system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7877421B2 (en) * | 2001-05-25 | 2011-01-25 | International Business Machines Corporation | Method and system for mapping enterprise data assets to a semantic information model |
| WO2006135756A1 (en) * | 2005-06-09 | 2006-12-21 | Intepoint, Llc | Multi-infrastructure modeling system |
-
2020
- 2020-08-13 CN CN202010810662.0A patent/CN112068830B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1480133A2 (en) * | 2003-05-22 | 2004-11-24 | Cognos Incorporated | System and method for the development of data models |
| CN104123133A (en) * | 2014-07-01 | 2014-10-29 | 曾安里 | Dragon VVR-VBF modularization development framework platform tool system |
| CN106933570A (en) * | 2017-02-16 | 2017-07-07 | 北京临近空间飞行器系统工程研究所 | Hair control software platform is surveyed in a kind of space flight based on plug-in part technology |
| CN110865942A (en) * | 2019-11-12 | 2020-03-06 | 中国航空无线电电子研究所 | Model rule checking method of comprehensive modular avionics system |
Non-Patent Citations (7)
| Title |
|---|
| DiaSuite: A tool suite to develop Sense/Compute/Control applications;Benjamin Bertran等;Science of Computer Programming;第79卷;第39-51页 * |
| Formal Verification Method for Configuration of Integrated Modular Avionics System Using MARTE;Lisong Wang等;International journal of aerospace engineering;第2018卷;第1-22页 * |
| IMADE: Integrated modular avionic development environment;Bruno Tavares等;2014 IEEE/AIAA 33rd Digital Avionics Systems Conference (DASC);第1-15页 * |
| 基于AADL的航电系统建模技术;田丹 等;航空计算技术;第40卷(第03期);第116-118页 * |
| 基于ARINC653标准的AADL模型配置工具的研究与实现;孟阳;中国优秀硕士学位论文全文数据库 信息科技辑(第1期);I137-60 * |
| 航空装备统一建模与仿真训练平台研究;王志乐 等;计算机测量与控制;第26卷(第8期);第127-132页 * |
| 飞行控制系统数字化设计技术研究;刘兴华;中国博士学位论文全文数据库 工程科技Ⅱ辑(第7期);C031-36 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112068830A (en) | 2020-12-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7043488B1 (en) | Method and system for storing hierarchical content objects in a data repository | |
| US7340481B1 (en) | Method and system for adding user-provided content to a content object stored in a data repository | |
| US6839701B1 (en) | Hitmask for querying hierarchically related content entities | |
| US7089239B1 (en) | Method and system for preventing mutually exclusive content entities stored in a data repository to be included in the same compilation of content | |
| US6611840B1 (en) | Method and system for removing content entity object in a hierarchically structured content object stored in a database | |
| US9003282B2 (en) | Method and system for managing volumes within a compilation of content | |
| US7076494B1 (en) | Providing a functional layer for facilitating creation and manipulation of compilations of content | |
| US7007034B1 (en) | File structure for storing content objects in a data repository | |
| US7346844B1 (en) | Method and system for moving content in a content object stored in a data repository | |
| US6449627B1 (en) | Volume management method and system for a compilation of content | |
| US6986102B1 (en) | Method and configurable model for storing hierarchical data in a non-hierarchical data repository | |
| US7613993B1 (en) | Prerequisite checking in a system for creating compilations of content | |
| US7401097B1 (en) | System and method for creating compilations of content | |
| CN114895990B (en) | Method for realizing dynamic combination application of attached resources based on file backplane | |
| WO2018036342A1 (en) | Csar-based template design visualization method and device | |
| US5850631A (en) | Method for providing a graphical interface for the specification of relationships between two schemas | |
| US7356766B1 (en) | Method and system for adding content to a content object stored in a data repository | |
| US20060047723A1 (en) | Custom database system and method of building the same | |
| CN110889013B (en) | Data association method, device, server and storage medium based on XML | |
| CN112068830B (en) | Avionics system architecture model-oriented design tool | |
| CN111984882A (en) | Data processing method, system and equipment | |
| US20100011018A1 (en) | Custom database system and method of building the same | |
| CN116400914A (en) | Method for quickly constructing web application based on data model | |
| CN114819631A (en) | Multitask visualization method and device, computer equipment and storage medium | |
| CN113761040A (en) | Database and application program bidirectional mapping method, device, medium and program product |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |