Modular integrated display interface design method

Abstract

The application discloses a modularized comprehensive display interface design method, which comprises the following steps: analyzing related display interface design criteria, constructing module components of interface display elements, encapsulating each component by using a Docker container, forming an image warehouse, compiling a layout integrated description file, describing the integrated layout of the module components, remotely deploying and integrating the module components, and forming a modularized comprehensive display interface. The application can be used for assisting in simulation test of an avionics system.

Description

Technical Field

[0001] This invention belongs to the field of avionics system simulation technology, specifically relating to a modular integrated display interface design method. Background Technology

[0002] In the process of building a real full-mission combat simulation environment, there is often a lot of human-machine interface development work. The integrated display interface, as a bridge for interaction and information exchange between the operator and the system, plays an important role in the entire simulation environment. Different system simulation environments have different requirements for the interface, so it is crucial to improve the effectiveness, reusability and iteration efficiency of interface development.

[0003] Currently, during the implementation phase of an interface, developers must use interface prototype development based on low-level interactive components (such as buttons, text boxes, etc.). They first assemble the basic components, then build the interface layout and interaction logic. This results in developers implementing the same functionalities multiple times. Furthermore, as requirements diversify, interface designs constantly iterate, requiring developers to make extensive modifications to the existing framework, hindering the rapid generation of interface prototypes. Summary of the Invention

[0004] To overcome the shortcomings of existing technologies, this invention provides a modular integrated display interface design method. By analyzing relevant display interface design principles, it constructs modular components for interface display elements, encapsulates each component using Docker containers to form an image repository, compiles a layout integration description file to describe the integrated layout of the modular components, and remotely deploys and integrates the modular components to form a modular integrated display interface. This invention can be used to assist in the simulation testing of avionics systems.

[0005] The technical solution adopted by this invention to solve its technical problem includes the following steps:

[0006] Step 1: Define the modular integrated display framework;

[0007] The modular integrated display framework consists of three parts: an image library, a server, and a client. The image library is composed of base images of each module component. The server is composed of components selected by container orchestration tools according to description files. The client deploys and integrates the components to form a complete integrated display interface.

[0008] Step 2: Define the communication data format for the module components;

[0009] The communication data of the module component is used to define the interface through which the component interacts with the system, including the component name, interface name, interface meaning, and data type;

[0010] Step 3: Define the build file for the base image of the module component;

[0011] The base image for each module component is the foundation for building each module component. The build file contains the operating system image name, X11 server installation code, and Scade Display base library installation code.

[0012] Step 4: Define the integration description file format for the combination of module components;

[0013] The integration description file describes the layout of the module components, including the layout row ratio definition, layout column ratio definition, layout nesting definition, module component position definition, and module component access port definition.

[0014] Step 5: Model the design elements required for the integrated display interface to form modular components. Modular components are built by integrating various basic elements according to requirements, creating components with specific functions. The internal structure of a modular component includes three parts: interface presentation, internal event flow, and external interface. The interface presentation describes how the component is displayed on the interface, including component size and the composition of internal elements. The internal event flow refers to how the component handles the action attributes of the end user's interaction. The external interface refers to the input and output variables that allow the component to interact with the system's internal systems.

[0015] Step 6: Use a base image to encapsulate each module component and upload it to the image repository. This includes building the base image, containerizing and encapsulating the components, and managing the image repository.

[0016] Step 7: Compile an integration description file; the client describes the integration layout of the module components, remotely deploys and integrates the module components to form a modular integrated display, and finally accesses and operates the integrated display. Specifically, this includes: compiling an integration description file, deploying and integrating module components, and remotely accessing the integrated display; ultimately forming a modular integrated display interface.

[0017] Preferably, the compilation of the integration description file is written in XML.

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

[0019] This invention solves the problems of inconsistent design element standards, low reusability, and repetitive development of the same patterns in the development of integrated display interfaces. Using this invention can significantly improve the development speed of integrated display interfaces, ensure the standardization of interface design elements, increase the reusability of each design element, and greatly improve the development efficiency and quality of integrated display interfaces. Attached Figure Description

[0020] Figure 1 This is a schematic diagram of the modular integrated display interface framework of the present invention.

[0021] Figure 2 This is a schematic diagram of the object relationships of the module components of the present invention. Detailed Implementation

[0022] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0023] The purpose of this invention is to provide a modular integrated display interface design method to improve the reusability of each design element in the interface implementation stage and realize the rapid and efficient development and iteration of integrated display interfaces in different system simulation environments.

[0024] A modular integrated display interface design method includes the following steps:

[0025] Step 1: Define the modular integrated display framework;

[0026] The modular integrated display framework consists of three parts: an image library, a server, and a client. The image library is composed of base images of each module component. The server is composed of components selected by container orchestration tools according to description files. The client deploys and integrates the components to form a complete integrated display interface.

[0027] Step 2: Define the communication data format for the module components;

[0028] The communication data of the module component is used to define the interface through which the component interacts with the system, including the component name, interface name, interface meaning, and data type;

[0029] Step 3: Define the build file for the base image of the module component;

[0030] The base image for each module component is the foundation for building each module component. The build file contains the operating system image name, X11 server installation code, and Scade Display base library installation code.

[0031] Step 4: Define the integration description file format for the combination of module components;

[0032] The integration description file describes the layout of the module components, including the layout row ratio definition, layout column ratio definition, layout nesting definition, module component position definition, and module component access port definition.

[0033] Step 5: Model the design elements required for the integrated display interface to form modular components. Modular components are built by integrating various basic elements according to requirements, creating components with specific functions. The internal structure of a modular component includes three parts: interface presentation, internal event flow, and external interface. The interface presentation describes how the component is displayed on the interface, including component size and the composition of internal elements. The internal event flow refers to how the component handles the action attributes of the end user's interaction. The external interface refers to the input and output variables that allow the component to interact with the system's internal systems.

[0034] Step 6: Use a base image to encapsulate each module component and upload it to the image repository. This includes building the base image, containerizing and encapsulating the components, and managing the image repository.

[0035] Step 7: Compile an integration description file; the client describes the integration layout of the module components, remotely deploys and integrates the module components to form a modular integrated display, and finally accesses and operates the integrated display. Specifically, this includes: compiling an integration description file, deploying and integrating module components, and remotely accessing the integrated display; ultimately forming a modular integrated display interface. Specific implementation examples:

[0037] The technical solution of this invention is as follows: by collecting system display requirements and analyzing the characteristics of a large number of existing integrated display interfaces, and combining relevant design principles, modular components of interface display elements are constructed; for different display interface design requirements, the required design elements are extracted from the modular components and "assembled" to quickly and efficiently construct an integrated display interface.

[0038] The specific embodiments of the present invention are as follows:

[0039] 1) Using ScadeDisplay, a graphical development tool provided by Scade Technology Ltd. (France), the design elements required for the integrated display interface were modeled and modular components were constructed. Each module integrates basic elements according to requirements to build components with specific functions, such as speedometer components, heading gauge components, and horizon components. The internal structure of each component comprises three parts: interface presentation, internal event flow, and external interface. The specific relationships are as follows: Figure 2 As shown. The presentation section describes how the component is displayed on the interface, including component size, the composition of internal elements, etc. The internal event flow refers to how the component handles the action attributes of end-user interactions (such as hover, click, etc.). The external interface refers to the input and output variables that allow the component to interact with the system's internal systems.

[0040] The functionalities and interface definitions of some module components are shown in Table 1:

[0041] Table 1 Functional and Interface Definitions of Module Components

[0042]

[0043]

[0044]

[0045] 2) Build the base image required for the Scade Display program to run using Docker containers, encapsulate each module component, and upload it to the image repository. Specifically, this includes:

[0046] a) Base image building: Write a Dockerfile, add the X11 Server and ScadeDisplay base libraries to the file, and build the base image of the module components using the docker build command.

[0047] b) Containerized encapsulation of components: Based on the base image of the module components, the docker build command is used to create images of each module component.

[0048] c) Image repository management: Push various module components to public or private container repositories using the docker push command.

[0049] 3) Compile an integration description file. The client describes the integration layout of the module components, remotely deploys and integrates the module components to form a modular integrated display. Finally, the integrated display is accessed and operated using the X11 protocol, specifically including:

[0050] a) Compile the integration description file: The integration description file describes the layout of the module components. It is written in XML and has the following format:

[0051]

[0052]

[0053] b) Module component deployment and integration: The client automatically generates a YAML file based on the integration description file and calls the server-side Kubernetes container orchestration tool to deploy and integrate the module components.

[0054] c) Integrated Display Remote Access: The client accesses the interface of the server module components using X11 based on the port defined in the DisplayContent integration description file.

Claims

1. A modular integrated display interface design method, characterized in that, Comprising the following steps: Step 1: define the modular integrated display integration framework; The modular integrated display integration framework specifically includes three parts: mirror library, server and client; wherein, The mirror library is composed of the basic image after the encapsulation of each module component; the server is composed of the module components screened by the container orchestration tool according to the description file; the module components are deployed and integrated on the client to form a complete integrated display interface; Step 2: define the communication data format of the module component; The communication data of the module component is used to define the interface for the component to interact with the system internally, including component name, interface name, interface meaning and data type; Step 3: define the build file of the module component basic image; The module component basic image is the basis for building each module component, and the build file includes the operating system image name, X11 server installation code and Scade Display basic library installation code; Step 4: define the integration description file format of the module component combination; The integration description file is a layout describing the combination of module components, including layout row ratio definition, layout column ratio Example definition, layout nesting definition, module component position definition, module component access port definition; Step 5: model the design elements required for the integrated display interface to form module components; the module component is integrated according to the requirements, and the basic elements are integrated to build a component with specific functions; the internal composition of the module component includes three parts: interface presentation, internal event flow and external interface; the interface presentation part is used to describe how the module component is displayed on the interface, including component size, internal element composition; the internal event flow refers to how the module component handles the action properties of the final user interaction; the external interface refers to the input and output variables for the module component to interact with the system internally; Step 6: encapsulate each module component using the basic image and upload it to the mirror library, which specifically includes Basic image building, component containerization encapsulation, mirror library management; Step 7: compile the integration description file, describe the integration layout of the module components on the client, remotely deploy and integrate the module components to form the modular integrated display, and finally access and operate the integrated display, which specifically includes: compiling the integration description file, module component deployment integration, integrated display remote access; finally form the modular integrated display interface. The integration description file is compiled using xml.

2. The method of claim 1, wherein, ​

Images