Avionics collaborative design method and system based on SysML

Through the SysML method, the operation scenarios of avionics system are obtained and analyzed, and the functional and logical architecture models are established, which solves the problems of document-centered inaccuracy and poor data transmission in avionics design, and realizes efficient collaborative design and data management, reducing the problem of Change costs.

CN112163337BActive Publication Date: 2024-11-05BEIJING AERONAUTIC SCI & TECH RES INST OF COMAC +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202011033097.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-09-27
Publication Date
2024-11-05
Estimated Expiration
2040-09-27

AI Technical Summary

Technical Problem

The document-centric approach in existing avionics design is not accurate enough, and data transmission between tools is not smooth, resulting in design problems being exposed in the later stage of R&D, high cost of change of funds and time, and lack of real-time collaboration and data management efficiency.

Method used

The avionics collaborative design method based on SysML is adopted, and by obtaining operation scenarios and analyzing them, system functions and logical architecture models are established, document output is realized, online preview and review are supported, software acquisition costs are reduced, and real-time collaboration of the design process is achieved.

Benefits of technology

It improves the accuracy and flexibility of the design, enhances data transmission among tools, reduces change costs, and realizes real-time collaboration and data management efficiency of the model.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112163337B_ABST
    Figure CN112163337B_ABST
Patent Text Reader

Abstract

The present invention discloses an avionics collaborative design method and system based on SysML. The method comprises: obtaining an operation scenario and analyzing the operation scenario; analyzing system functions and logical architecture layers according to the operation scenario; modeling the logical architecture according to the logical architecture layer; and outputting a document according to the avionics collaborative design result. The present invention solves the technical problems in the prior art that the document-centric design is not accurate and flexible enough and the data transmission between tools is not smooth.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of avionics, and in particular to an avionics collaborative design method and system based on SysML. Background Art

[0002] At present, the IPD platform is widely used within the aviation manufacturing industry. It is a knowledge management and task management platform. The preservation of engineering models is limited to uploading and downloading source files. Model files are exported from professional tools and uploaded to the knowledge management platform. When they need to be viewed and modified, they are downloaded to the local computer. If the downloaded model is not what is needed, it will cause a waste of resources. Secondly, the model content generated by professional design tools can only be viewed within the professional tools. It is impossible to preview and review the model online, which makes it difficult to connect with the R&D process and visualize the design process products. At this time, the cost of purchasing software needs to be increased. At the same time, if several people want to view and modify the same model, they need to install the corresponding design software on multiple computers. The model review and test verification in the team collaboration process need to be carried out after the modeling is completed. It is impossible to view and review in real time, and it is impossible to realize the real-time communication of internal personnel information within the system. The design collaboration tasks rely on manual allocation, and the collaboration relies on manual communication. In addition, there are also problems such as the large amount of data generated in the design process, different formats, lack of unified version management, and difficulty in reuse in the design process.

[0003] Due to the current technology for the development of complex integrated electronic systems for ongoing or future models, the existing document-centric system development methods have shown their drawbacks; the current early design models are not accurate enough and can only achieve static analysis. Design problems are not exposed until the physical verification in the later stages of development, and the cost of change is high in terms of capital and time; model-based concepts and foreign tools are gradually introduced but not fully integrated into the R&D process, data transmission between tools is not smooth, and upstream design results are difficult to directly inherit as downstream design inputs; R&D data are scattered, and the correlation and consistency between data require manual management.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiment of the present invention provides an avionics collaborative design method and system based on SysML, so as to at least solve the technical problems in the prior art that the document-centric design is not accurate and flexible enough and the data transmission between tools is not smooth.

[0006] According to one aspect of an embodiment of the present invention, there is provided an avionics collaborative design method based on SysML, including: acquiring an operation scenario and analyzing the operation scenario; analyzing system functions and logical architecture layers according to the operation scenario; modeling a logical architecture according to the logical architecture layer; and outputting a document according to the avionics collaborative design result.

[0007] Optionally, before obtaining the operation scenario and analyzing the operation scenario, the method further includes: importing a demand analysis tool according to system requirements.

[0008] Optionally, analyzing the system functions and the logical architecture layer according to the operation scenario includes: analyzing and designing the system functions according to the operation scenario; and designing the logical architecture layer according to the operation scenario and the system functions.

[0009] Optionally, after analyzing the system functions and logical architecture layers according to the operating scenario, the method further includes: checking whether the system functions are correct according to preset specifications, and generating a check result.

[0010] Optionally, outputting a document according to the avionics collaborative design result includes: editing the avionics collaborative design result through a preset template to generate document data; and storing the document data.

[0011] Optionally, the document data may be downloaded at any time by executing a download instruction.

[0012] According to another aspect of an embodiment of the present invention, there is also provided an avionics collaborative design system based on SysML, including: an acquisition module, used to acquire an operation scenario and analyze the operation scenario; an analysis module, used to analyze system functions and logical architecture layers according to the operation scenario; a modeling module, used to model the logical architecture according to the logical architecture layer; and an output module, used to output documents according to the avionics collaborative design results.

[0013] Optionally, the system further includes: an import module, used to import a demand analysis tool according to system requirements.

[0014] Optionally, the analysis module includes: an analysis unit, used to analyze and design the system function according to the operation scenario; and a logic unit, used to design the logical architecture layer according to the operation scenario and the system function.

[0015] Optionally, the system further includes: a checking module, configured to check whether the system functions correctly according to preset specifications and generate a checking result.

[0016] Optionally, the output module includes: a document unit, used to edit the result of the avionics collaborative design through a preset template to generate document data; and a storage unit, used to store the document data.

[0017] Optionally, the document data may be downloaded at any time by executing a download instruction.

[0018] According to another aspect of an embodiment of the present invention, a computer program product including instructions is further provided. When the instructions are executed on a computer, the computer is enabled to execute an avionics collaborative design method based on SysML.

[0019] According to another aspect of an embodiment of the present invention, a non-volatile storage medium is further provided, wherein the non-volatile storage medium includes a stored program, wherein when the program is run, the device where the non-volatile storage medium is located is controlled to execute an avionics collaborative design method based on SysML.

[0020] According to another aspect of an embodiment of the present invention, there is also provided an electronic device, comprising a processor and a memory; the memory stores computer-readable instructions, and the processor is used to run the computer-readable instructions, wherein the computer-readable instructions execute a SysML-based avionics collaborative design method when running.

[0021] In the embodiment of the present invention, the operation scenario is obtained and analyzed; according to the operation scenario, the system function and logical architecture layer are analyzed; according to the logical architecture layer, the logical architecture is modeled; according to the avionics collaborative design result, the document is output, which solves the technical problems of the document-centric design in the prior art that is not accurate and flexible enough and the data transmission between tools is not smooth. This technical solution puts forward new requirements for system collaborative design in combination with the complex characteristics of the avionics system, and it is necessary to adopt a model-centric system engineering method for new technologies and new requirements; it is necessary to establish a digital model of the electronic system in the early stage of design, and through knowledge-guided design, realize hierarchical dynamic verification of the avionics design model imported into the system to ensure that the model granularity of the collaborative design is consistent with the interface relationship; at the same time, in view of the problem that the model library cannot be previewed online, the model of the knowledge base cannot be analyzed, viewed and reviewed online, and the design process product cannot be visualized in the prior art, a data online explicit method based on a web page is provided to realize online browsing of the itemized requirements in the requirement management tool, support online browsing of the SysML model of the SysML-based design tool, and do not need to install a proprietary design modeling tool, saving software acquisition costs, and realizing real-time collaboration of design processes, system requirements and models. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0023] Figure 1 is a flow chart of an avionics collaborative design method based on SysML according to an embodiment of the present invention;

[0024] Figure 2 is a structural block diagram of an avionics collaborative design system based on SysML according to an embodiment of the present invention;

[0025] Figure 3 is a system functional module diagram according to an embodiment of the present invention;

[0026] Figure 4 is a system architecture diagram according to an embodiment of the present invention;

[0027] Figure 5 is a system requirements capture and collaboration process according to an embodiment of the present invention;

[0028] Figure 6 is a system function analysis process according to an embodiment of the present invention;

[0029] Figure 7 is a system logic architecture analysis process according to an embodiment of the present invention;

[0030] Figure 8 This is a report generation process according to an embodiment of the present invention. DETAILED DESCRIPTION

[0031] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0032] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0033] According to an embodiment of the present invention, a method embodiment of an avionics collaborative design method based on SysML is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0034] Embodiment 1

[0035] Figure 1 is a flowchart of an avionics collaborative design method based on SysML according to an embodiment of the present invention, such as Figure 1 As shown, the method comprises the following steps:

[0036] Step S102, obtaining an operation scenario and analyzing the operation scenario.

[0037] Optionally, before obtaining the operation scenario and analyzing the operation scenario, the method further includes: importing a demand analysis tool according to system requirements.

[0038] Specifically, when designing an avionics collaborative system, it is first necessary to capture system requirements in order to build a collaborative system based on the requirements. The platform can import requirements for specific demand analysis tools. After the external top-level requirements are imported through the platform interoperability module, the web version of the requirements online browsing function provided by the platform can be used to implement pre-processing operations such as editing and organizing the requirements. At the same time, in order to facilitate the rapid application of the top-level requirements in subsequent system design, a copy of the top-level requirements is saved in the platform project library and an index is established to the original data in the specific demand analysis tool to ensure synchronization and consistency in the future. The specific demand capture process is as follows: Figure 5 As shown, Figure 5 This is a system requirement capture and collaboration process according to an embodiment of the present invention.

[0039] In addition, the embodiment of the present invention needs to design an avionics collaborative platform based on the SysML environment. The avionics collaborative design system includes a demand management module, a system design function module, an interface design management module, a configuration management function module, a process management function module, a knowledge management module, and a document management module. Figure 3 As shown:

[0040] 1. Requirements management module: Integrates the itemized requirements in different requirements management tools and supports file formats such as DXL, CSV, and XLS.

[0041] 2. System design function module: Use methodology to design avionics systems. The entire design process is divided into three stages: operation scenario analysis, system function analysis, and logical architecture analysis. In each stage, the design model is used as the development input for the next stage.

[0042] 3. Interface design management module: It includes two functions: interface design and management. The interface design function includes two parts: traceability of the integrated model interface and hierarchical verification of the integrated model interface; the interface management function realizes the management of the scene interaction interface, functional interface, and logical interface.

[0043] 4. Configuration management function module: perform version control on the products in the avionics system design and development process, and support the management of versions and baselines of each product at each design stage.

[0044] 5. Process management functional module: includes two functions: formulation and solidification of design specifications and integration of design process. The formulation and solidification of design specifications mainly includes the management and control of six aspects, including demand management, system design, project management, configuration changes, modeling specifications, and report generation; the integration function of the design process mainly realizes the coordination and integration of different processes, such as demand management process, system design process, project management process, configuration change process, etc.

[0045] 6. Knowledge management module: Visually manage model assets in the avionics design and development process, and conduct compliance analysis on model design results to achieve model reuse.

[0046] 7. Document management module: manage the documents required in the avionics design and development process and realize automatic document publishing.

[0047] In addition, if Figure 4 As shown, Figure 4 is a system architecture diagram according to an embodiment of the present invention. Figure 4A method and system for avionics design collaboration is proposed as shown. The method can automatically match the avionics requirements in the requirement management tool with the model generated by the SysML-based design modeling tool to the built-in process wizard in the avionics design collaboration system, thereby improving the collaborative efficiency of avionics model design.

[0048] In the process of avionics system design and development, the main line is based on requirements and models. Through reasonable organization, the requirements and models of the same level are mapped and imported into the avionics collaborative design system for collaborative design and integration. Avionics requirements are hierarchically divided into user requirements, system requirements and subsystem requirements. The design model corresponding to these requirements is hierarchically divided into operation scenario models, system function models and logical architecture models. These models are generated by SysML-based design modeling tools and traceably linked to the requirements in the requirements management tool. In the design process of a single model, there is no need to consider the interface matching and requirement traceability relationship with other models, but in the collaborative design and integration process of multiple models, the granularity of the model and the matching of the interface need to be considered. The process specification built into the avionics system design system consists of three parts: operation scenario analysis, system function analysis, and logical architecture analysis. The system can associate avionics user requirements and scenario models through the operation scenario analysis process and method, associate avionics system requirements and functional models through the system function analysis process and method, and associate avionics system requirements and logical models through the logical architecture analysis process and method. The imported avionics model elements are visually analyzed in the system according to the SysML structure diagram and behavior diagram, which is convenient for model specification verification, demand and model element traceability, and model interface matching and integration. The operation scenario analysis, system function analysis, and logical architecture analysis process accurately match the model interface with the avionics requirements through detailed method steps, so that the model granularity in the avionics system design system is consistent, and the model interface is named and integrated according to unified rules. The product of collaborative design can automatically generate model design files through the system's document predefined templates, completing the model drive and result report release of the avionics collaborative design process.

[0049] It should be noted that the SysML described in the embodiment of the present invention refers to the object management organization OMG's decision to propose a new system modeling language, SysML (Systems Modeling Language), based on the reuse and expansion of a subset of UML2.0, as a standard modeling language for system engineering. Just as UML is used to unify the modeling languages ​​used in software engineering, the purpose of SysML is to unify the modeling languages ​​used in system engineering. SysML defines semantics for the structural model, behavioral model, requirement model and parameter model of the system. The structural model emphasizes the hierarchy of the system and the interconnected relationship between objects, including classes and assemblies. The behavioral model emphasizes the behavior of objects in the system, including their activities, interactions and state history. The requirement model emphasizes the traceability relationship between requirements and the satisfaction relationship between the design and the requirements. The parameter model emphasizes the constraint relationship between the attributes of the system or component. SysML provides complete semantics for model representation. Like UML, the structure of the SysML language is also based on a four-layer metamodel structure: meta-metamodel, metamodel, model and user object. The meta-metamodel layer has the highest level of abstraction and is the model that defines the metamodel description language. It provides the most basic concepts and mechanisms for defining the elements and various mechanisms of the metamodel. The metamodel is an instance of the meta-metamodel and defines the model of the model description language. The metamodel provides various packages for expressing the system, definition types of model elements, tagged values ​​and constraints, etc. The model is an instance of the metamodel and defines the model of the description language for a specific domain. User objects are instances of the model. Any complex system is seen by the user as specific objects that communicate with each other in order to achieve the functions and performance of the complex system.

[0050] Step S104: analyzing the system functions and logical architecture layers according to the operation scenario.

[0051] Optionally, analyzing the system functions and the logical architecture layer according to the operation scenario includes: analyzing and designing the system functions according to the operation scenario; and designing the logical architecture layer according to the operation scenario and the system functions.

[0052] Optionally, after analyzing the system functions and logical architecture layers according to the operating scenario, the method further includes: checking whether the system functions are correct according to preset specifications, and generating a check result.

[0053] Specifically, at the system function analysis layer, such as Figure 6As shown in the figure, the system engineer first imports the avionics top-level requirements into the SysML-based design modeling tool. The import method can be from a specific requirement analysis tool; the second is from the platform project library. Among them, the import method can also be a more convenient and fast top-level requirement import function provided by the collaborative design platform for system engineers, which can ensure the consistency of the top-level requirements imported by different system engineers. After importing the top-level requirements, the system engineer can carry out a new design according to the design and development process specifications built into the platform, or browse and search for existing reusable components in the knowledge base from the collaborative design platform. At any time during the design process, the system engineer can trigger and request the collaborative design platform to verify whether the design results in his current design modeling tool meet the design specifications. If there are design results that do not meet the design specifications, the design modeling tool will give a design specification prompt. After completing the design work, the system engineer can submit his design results to the collaborative design work platform so that other system engineers can browse and use their design models online.

[0054] Step S106: Modeling the logical architecture according to the logical architecture layer.

[0055] Specifically, in this embodiment, through system function analysis and logical architecture design, the preliminary platform function and logical framework are obtained, and then at the logical architecture analysis layer, the collaborative design platform has built-in corresponding design modeling specifications, and the system engineer carries out logical architecture modeling according to the design modeling specifications of the logical architecture layer, such as Figure 7 As shown in the figure, the operation process is similar to the system function analysis layer. The system engineer first imports the avionics top-level requirements into the SysML-based design modeling tool. The import method can be from a specific requirement analysis tool; the second is from the platform project library. Among them, the import method can also be the more convenient and fast top-level requirement import function provided by the collaborative design platform for system engineers, which can ensure the consistency of the top-level requirements imported by different system engineers.

[0056] Step S108: outputting a document according to the avionics collaborative design result.

[0057] Optionally, outputting a document according to the avionics collaborative design result includes: editing the avionics collaborative design result through a preset template to generate document data; and storing the document data.

[0058] Optionally, the document data may be downloaded at any time by executing a download instruction.

[0059] Specifically, Figure 8 As shown, Figure 8It is a report generation process according to an embodiment of the present invention, which automatically generates documents for the process or result products of collaborative design through predefined templates in the system (in compliance with military standards, institute standards or other relevant specifications). When the project progresses to a specific stage, the report document manager can issue an instruction to generate a report document based on a certain report document template on the system design platform. The document generation engine loads the report document template and extracts the required data from the data source tool. The automatically generated report document file can be stored in the report document list of the collaborative design platform for download.

[0060] Through the above steps, the technical effect of flexible and accurate design of avionics collaborative platform can be achieved.

[0061] Embodiment 2

[0062] Figure 2 is a structural block diagram of an avionics collaborative design system based on SysML according to an embodiment of the present invention, such as Figure 2 As shown, the system includes:

[0063] The acquisition module 20 is used to acquire the operation scenario and analyze the operation scenario.

[0064] Optionally, the system further includes: an import module, used to import a demand analysis tool according to system requirements.

[0065] Specifically, when designing an avionics collaborative system, it is first necessary to capture system requirements in order to build a collaborative system based on the requirements. The platform can import requirements for specific demand analysis tools. After the external top-level requirements are imported through the platform interoperability module, the web version of the requirements online browsing function provided by the platform can be used to implement pre-processing operations such as editing and organizing the requirements. At the same time, in order to facilitate the rapid application of the top-level requirements in subsequent system design, a copy of the top-level requirements is saved in the platform project library and an index is established to the original data in the specific demand analysis tool to ensure synchronization and consistency in the future. The specific demand capture process is as follows: Figure 5 As shown, Figure 5 This is a system requirement capture and collaboration process according to an embodiment of the present invention.

[0066] In addition, the embodiment of the present invention needs to design an avionics collaborative platform based on the SysML environment. The avionics collaborative design system includes a demand management module, a system design function module, an interface design management module, a configuration management function module, a process management function module, a knowledge management module, and a document management module. Figure 3 As shown:

[0067] 1. Requirements management module: Integrates the itemized requirements in different requirements management tools and supports file formats such as DXL, CSV, and XLS.

[0068] 2. System design function module: Use methodology to design avionics systems. The entire design process is divided into three stages: operation scenario analysis, system function analysis, and logical architecture analysis. In each stage, the design model is used as the development input for the next stage.

[0069] 3. Interface design management module: It includes two functions: interface design and management. The interface design function includes two parts: traceability of the integrated model interface and hierarchical verification of the integrated model interface; the interface management function realizes the management of the scene interaction interface, functional interface, and logical interface.

[0070] 4. Configuration management function module: perform version control on the products in the avionics system design and development process, and support the management of versions and baselines of each product at each design stage.

[0071] 5. Process management functional module: includes two functions: formulation and solidification of design specifications and integration of design process. The formulation and solidification of design specifications mainly includes the management and control of six aspects, including demand management, system design, project management, configuration changes, modeling specifications, and report generation; the integration function of the design process mainly realizes the coordination and integration of different processes, such as demand management process, system design process, project management process, configuration change process, etc.

[0072] 6. Knowledge management module: Visually manage model assets in the avionics design and development process, and conduct compliance analysis on model design results to achieve model reuse.

[0073] 7. Document management module: manage the documents required in the avionics design and development process and realize automatic document publishing.

[0074] In addition, if Figure 4 As shown, Figure 4 is a system architecture diagram according to an embodiment of the present invention. Figure 4 A method and system for avionics design collaboration is proposed as shown. The method can automatically match the avionics requirements in the requirement management tool with the model generated by the SysML-based design modeling tool to the built-in process wizard in the avionics design collaboration system, thereby improving the collaborative efficiency of avionics model design.

[0075] In the process of avionics system design and development, the main line is based on requirements and models. Through reasonable organization, the requirements and models of the same level are mapped and imported into the avionics collaborative design system for collaborative design and integration. Avionics requirements are hierarchically divided into user requirements, system requirements and subsystem requirements. The design model corresponding to these requirements is hierarchically divided into operation scenario models, system function models and logical architecture models. These models are generated by SysML-based design modeling tools and traceably linked to the requirements in the requirements management tool. In the design process of a single model, there is no need to consider the interface matching and requirement traceability relationship with other models, but in the collaborative design and integration process of multiple models, the granularity of the model and the matching of the interface need to be considered. The process specification built into the avionics system design system consists of three parts: operation scenario analysis, system function analysis, and logical architecture analysis. The system can associate avionics user requirements and scenario models through the operation scenario analysis process and method, associate avionics system requirements and functional models through the system function analysis process and method, and associate avionics system requirements and logical models through the logical architecture analysis process and method. The imported avionics model elements are visually analyzed in the system according to the SysML structure diagram and behavior diagram, which is convenient for model specification verification, demand and model element traceability, and model interface matching and integration. The operation scenario analysis, system function analysis, and logical architecture analysis process accurately match the model interface with the avionics requirements through detailed method steps, so that the model granularity in the avionics system design system is consistent, and the model interface is named and integrated according to unified rules. The product of collaborative design can automatically generate model design files through the system's document predefined templates, completing the model drive and result report release of the avionics collaborative design process.

[0076] It should be noted that the SysML described in the embodiment of the present invention refers to the object management organization OMG's decision to propose a new system modeling language, SysML (Systems Modeling Language), based on the reuse and expansion of a subset of UML2.0, as a standard modeling language for system engineering. Just as UML is used to unify the modeling languages ​​used in software engineering, the purpose of SysML is to unify the modeling languages ​​used in system engineering. SysML defines semantics for the structural model, behavioral model, requirement model and parameter model of the system. The structural model emphasizes the hierarchy of the system and the interconnected relationship between objects, including classes and assemblies. The behavioral model emphasizes the behavior of objects in the system, including their activities, interactions and state history. The requirement model emphasizes the traceability relationship between requirements and the satisfaction relationship between the design and the requirements. The parameter model emphasizes the constraint relationship between the attributes of the system or component. SysML provides complete semantics for model representation. Like UML, the structure of the SysML language is also based on a four-layer metamodel structure: meta-metamodel, metamodel, model and user object. The meta-metamodel layer has the highest level of abstraction and is the model that defines the metamodel description language. It provides the most basic concepts and mechanisms for defining the elements and various mechanisms of the metamodel. The metamodel is an instance of the meta-metamodel and defines the model of the model description language. The metamodel provides various packages for expressing the system, definition types of model elements, tagged values ​​and constraints, etc. The model is an instance of the metamodel and defines the model of the description language for a specific domain. User objects are instances of the model. Any complex system is seen by the user as specific objects that communicate with each other in order to achieve the functions and performance of the complex system.

[0077] The analysis module 22 is used to analyze the system functions and logical architecture layers according to the operation scenario.

[0078] Optionally, the analysis module includes: an analysis unit, used to analyze and design the system function according to the operation scenario; and a logic unit, used to design the logical architecture layer according to the operation scenario and the system function.

[0079] Optionally, the system further includes: a checking module, configured to check whether the system functions correctly according to preset specifications and generate a checking result.

[0080] Specifically, at the system function analysis layer, such as Figure 6As shown in the figure, the system engineer first imports the avionics top-level requirements into the SysML-based design modeling tool. The import method can be from a specific requirement analysis tool; the second is from the platform project library. Among them, the import method can also be a more convenient and fast top-level requirement import function provided by the collaborative design platform for system engineers, which can ensure the consistency of the top-level requirements imported by different system engineers. After importing the top-level requirements, the system engineer can carry out a new design according to the design and development process specifications built into the platform, or browse and search for existing reusable components in the knowledge base from the collaborative design platform. At any time during the design process, the system engineer can trigger and request the collaborative design platform to verify whether the design results in his current design modeling tool meet the design specifications. If there are design results that do not meet the design specifications, the design modeling tool will give a design specification prompt. After completing the design work, the system engineer can submit his design results to the collaborative design work platform so that other system engineers can browse and use their design models online.

[0081] The modeling module 24 is used to model the logical architecture according to the logical architecture layer.

[0082] Specifically, in this embodiment, through system function analysis and logical architecture design, the preliminary platform function and logical framework are obtained, and then at the logical architecture analysis layer, the collaborative design platform has built-in corresponding design modeling specifications, and the system engineer carries out logical architecture modeling according to the design modeling specifications of the logical architecture layer, such as Figure 7 As shown in the figure, the operation process is similar to the system function analysis layer. The system engineer first imports the avionics top-level requirements into the SysML-based design modeling tool. The import method can be from a specific requirement analysis tool; the second is from the platform project library. Among them, the import method can also be the more convenient and fast top-level requirement import function provided by the collaborative design platform for system engineers, which can ensure the consistency of the top-level requirements imported by different system engineers.

[0083] The output module 26 is used to output documents according to the avionics collaborative design results.

[0084] Optionally, the output module includes: a document unit, used to edit the result of the avionics collaborative design through a preset template to generate document data; and a storage unit, used to store the document data.

[0085] Optionally, the document data may be downloaded at any time by executing a download instruction.

[0086] Specifically, Figure 8 As shown, Figure 8It is a report generation process according to an embodiment of the present invention, which automatically generates documents for the process or result products of collaborative design through predefined templates in the system (in compliance with military standards, institute standards or other relevant specifications). When the project progresses to a specific stage, the report document manager can issue an instruction to generate a report document based on a certain report document template on the system design platform. The document generation engine loads the report document template and extracts the required data from the data source tool. The automatically generated report document file can be stored in the report document list of the collaborative design platform for download.

[0087] According to another aspect of an embodiment of the present invention, a computer program product including instructions is further provided. When the instructions are executed on a computer, the computer is enabled to execute an avionics collaborative design method based on SysML.

[0088] According to another aspect of an embodiment of the present invention, a non-volatile storage medium is further provided, wherein the non-volatile storage medium includes a stored program, wherein when the program is run, the device where the non-volatile storage medium is located is controlled to execute an avionics collaborative design method based on SysML.

[0089] According to another aspect of an embodiment of the present invention, there is also provided an electronic device, comprising a processor and a memory; the memory stores computer-readable instructions, and the processor is used to run the computer-readable instructions, wherein the computer-readable instructions execute a SysML-based avionics collaborative design method when running.

[0090] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0091] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0092] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0093] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0094] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0095] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0096] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A SysML-based avionics collaborative design method, characterized in that: include: Obtaining an operation scenario and analyzing the operation scenario; According to the operation scenario, the system function and logical architecture layer are analyzed; wherein, at the system function analysis layer, the top-level avionics requirements are imported into the SysML-based design modeling tool, and a new design is performed according to the design and development process specifications built into the collaborative design platform, or the reusable components already in the knowledge base are browsed and searched from the collaborative design platform, triggering and requesting the collaborative design platform to verify whether the design results in the current design modeling tool meet the design specifications; wherein, the avionics requirements are hierarchically divided into user requirements, system requirements and subsystem requirements, and the design model hierarchies corresponding to these requirements are hierarchically divided into operation scenario models, system function models and logical architecture models, all of which are generated by the SysML-based design modeling tool and traceably linked to the requirements in the requirements management tool; Modeling a logical architecture according to the logical architecture layers; Outputting documents according to the avionics collaborative design results; Wherein, analyzing the system functions and logical architecture layers according to the operation scenario includes: Analyze and design system functions according to the described operation scenarios; Designing the logical architecture layer according to the operation scenario and the system functions; The method further comprises: Automatically match the avionics requirements in the requirements management tool with the model generated by the SysML-based design modeling tool to the built-in process wizard in the avionics design collaborative system; the avionics design collaborative system includes:

1. Requirements management module: integrating the itemized requirements in different requirements management tools; 2. System design function module: dividing the entire design process into three stages: operation scenario analysis, system function analysis, and logical architecture analysis. Each stage uses the design model as the development input for the next stage; 3. Interface design management module: including the design and management of interfaces; the interface design function includes two parts: traceability of the integrated model interface and hierarchical verification of the integrated model interface; the interface management function realizes the management of the scenario interaction interface, functional interface, and logical interface; 4. .Configuration management function module: version control of products in the avionics system design and development process, and support for version and baseline management of each product in each design stage; 5.Process management function module: includes two functions: formulation and solidification of design specifications and integration of design processes. The formulation and solidification of design specifications include the management and control of six aspects: demand management, system design, project management, configuration changes, modeling specifications, and report generation; the integration function of the design process realizes the coordination and integration of different processes; 6.Knowledge management module: visual management of model assets in the avionics design and development process, and compliance analysis of model design results to realize model reuse; 7.Document management module: manage the documents required in the avionics design and development process and realize automatic document publishing; The method further comprises: System engineers import the top-level avionics requirements into the SysML-based design modeling tool. The import method is that the collaborative design platform provides the system engineers with the top-level requirements import function. After importing the top-level requirements, the system engineers browse and search for existing reusable components in the knowledge base from the collaborative design platform. At any time in the design process, the system engineers can trigger and request the collaborative design platform to verify whether the design results in their current design modeling tool meet the design specifications. If there are design results that do not meet the design specifications, the design modeling tool will give a design specification prompt. After completing the design work, the system engineer will submit his design results to the collaborative design work platform so that other system engineers can browse and use their design models online.

2. The method according to claim 1, characterized in that Before obtaining the operation scenario and analyzing the operation scenario, the method further includes: Import requirement analysis tools based on system requirements.

3. The method according to claim 1, characterized in that After analyzing the system functions and logical architecture layers according to the operation scenario, the method further includes: Check whether the system functions correctly according to preset specifications and generate inspection results.

4. The method according to claim 1, characterized in that: The document output according to the avionics collaborative design result includes: Edit the result of the avionics collaborative design using a preset template to generate document data; The document data is stored.

5. The method according to claim 4, characterized in that The document data can be downloaded at any time by executing a download instruction.

6. An avionics collaborative design system based on SysML, characterized in that: include: An acquisition module, used to acquire an operation scenario and analyze the operation scenario; An analysis module is used to analyze the system function and logical architecture layer according to the operation scenario; wherein, at the system function analysis layer, the top-level avionics requirements are imported into the SysML-based design modeling tool, and a new design is performed according to the design and development process specifications built into the collaborative design platform, or the reusable components already in the knowledge base are browsed and searched from the collaborative design platform, triggering and requesting the collaborative design platform to verify whether the design results in the current design modeling tool meet the design specifications; wherein, the avionics requirements are hierarchically divided into user requirements, system requirements and subsystem requirements, and the design model corresponding to this requirement is hierarchically divided into an operation scenario model, a system function model and a logical architecture model, and these models are all generated by the SysML-based design modeling tool, and are traceably linked to the requirements in the requirement management tool; A modeling module, used for modeling the logical architecture according to the logical architecture layer; An output module, used for outputting documents according to the avionics collaborative design results; Demand management module: integrates itemized requirements from different demand management tools; System design function module: The entire design process is divided into three stages: operation scenario analysis, system function analysis, and logical architecture analysis. In each stage, the design model is used as the development input for the next stage; Interface design management module: includes two functions: interface design and management. The interface design function includes two parts: traceability of the integrated model interface and hierarchical verification of the integrated model interface. The interface management function realizes the management of the scene interaction interface, functional interface, and logical interface. Configuration management function module: performs version control on products in the avionics system design and development process, and supports version and baseline management of each product at each design stage; Process management function module: including the formulation and solidification of design specifications and the integration of design processes. The formulation and solidification of design specifications includes the control of six aspects: demand management, system design, project management, configuration changes, modeling specifications, and report generation. The integration function of the design process realizes the coordination and integration of different processes. Knowledge management module: Visually manage model assets in the avionics design and development process, and perform compliance analysis on model design results to achieve model reuse; Document management module: manages the documents required in the avionics design and development process and realizes automatic document publishing; Wherein, the analysis module includes: An analysis unit, used to analyze and design system functions according to the operation scenario; A logic unit, used for designing the logic architecture layer according to the operation scenario and the system function; The system further comprises: The inspection module is used to check whether the system functions are correct according to preset specifications and generate inspection results; it includes: the system engineer imports the avionics top-level requirements into the SysML-based design modeling tool, and the import method is that the collaborative design platform provides the system engineer with the top-level requirement import function; after importing the top-level requirements, the system engineer browses and searches for existing reusable components in the knowledge base from the collaborative design platform. At any time in the design process, the system engineer can trigger and request the collaborative design platform to verify whether the design results in his current design modeling tool meet the design specifications; if there are design results that do not meet the design specifications, the design modeling tool will give a design specification prompt. After completing the design work, the system engineer will submit his design results to the collaborative design work platform so that other system engineers can browse and use their design models online.

7. The system according to claim 6, characterized in that The system further comprises: Import module, used to import requirement analysis tools according to system requirements.

8. The system according to claim 6, characterized in that The output module comprises: A document unit, used for editing the result of the avionics collaborative design through a preset template to generate document data; A storage unit is used to store the document data.

9. The system according to claim 8, characterized in that The document data can be downloaded at any time by executing a download instruction.

10. A computer program product comprising instructions, characterized in that When the instructions are executed on a computer, the computer is enabled to execute the method according to any one of claims 1 to 5.

11. A non-volatile storage medium, characterized in that: The non-volatile storage medium includes a stored program, wherein the program controls the device where the non-volatile storage medium is located to execute the method according to any one of claims 1 to 5 when the program is executed.

12. An electronic device, characterized in that: The method comprises a processor and a memory, wherein the memory stores computer-readable instructions, and the processor is used to execute the computer-readable instructions, wherein the computer-readable instructions execute the method according to any one of claims 1 to 5 when executed.