System architecture and system architecture integrated modeling method

Abstract

The invention provides a system architecture and a system architecture integrated modeling method. The method comprises the following steps: step 1, constructing a system architecture based on a language transformation mechanism and an integrated language application mechanism of the system architecture; 2, constructing a system architecture based on a data exchange mechanism and an integrated tool chain of the system architecture; step 3, constructing an integrated modeling framework of the matrix type system architecture and the system architecture; according to the system architecture and the system architecture integrated modeling method, the unique data source advantage of the system model is fully played, the modeling workload is reduced, the information consistency between hierarchies is ensured, the research and development quality of complex equipment is improved, and the research and development period of the complex equipment is shortened.

Description

Technical Field

[0001] The present application belongs to the technical field of overall design of complex equipment, and in particular, relates to a method for integrating system architecture and system architecture modeling. Background Art

[0002] System architecture design is to carry out architecture design from a higher perspective. In the field of equipment development, the most commonly used methodology is the DoDAF modeling framework. The framework is divided into capability viewpoint, operational viewpoint, system viewpoint and service viewpoint. The purpose is to carry out modeling analysis, system contribution rate assessment and system architecture design.

[0003] The system architecture focuses on the aircraft platform and conducts modeling and analysis of the aircraft's requirements, functions, and architecture.

[0004] There are a lot of data and model interaction requirements at the two architectural levels, but the methodologies are basically developed independently, which results in a serious split. Is there any integrated modeling method in the existing technology? Summary of the invention

[0005] Purpose of the invention: This application conducts research from three aspects: architecture and system architecture modeling language, tools and methodology, establishes a model-based architecture and system architecture integrated language application mechanism, tool chain platform and architecture design method framework, and realizes the integrated design of architecture and system architecture.

[0006] The present application provides a method for integrating system architecture and system architecture modeling, the method comprising the following steps:

[0007] Step 1: Build an integrated language application mechanism based on the system architecture and system architecture of the language conversion mechanism;

[0008] Step 2: Build an integrated tool chain of system architecture and system architecture based on data exchange mechanism;

[0009] Step 3: Build an integrated modeling framework for matrix architecture and system architecture.

[0010] Preferably, the language conversion mechanism includes a language element conversion mechanism, a language element inheritance mechanism, a language element tracing mechanism, a language element extension mechanism and a model conversion mechanism.

[0011] Preferably, the step 1 specifically includes:

[0012] Build a mechanism for converting system architecture and system architecture language elements;

[0013] Build the inheritance mechanism of system architecture and system architecture language elements;

[0014] Build a system architecture and system architecture language element traceability mechanism;

[0015] Build an extension mechanism based on architecture and system architecture language elements;

[0016] Build a model conversion mechanism for the system architecture and system architecture based on language conversion standards;

[0017] Based on the language element conversion mechanism, the language element inheritance mechanism, the language element tracing mechanism, the language element extension mechanism and the model conversion mechanism, a system architecture and system architecture integrated modeling language application framework is constructed.

[0018] Preferably, the data exchange mechanism includes a file data exchange mechanism, an API developed data exchange mechanism, and a data bus data exchange mechanism.

[0019] Preferably, step 2 comprises:

[0020] Build file-based data exchange mechanisms for architecture and system architecture;

[0021] Build data exchange mechanism based on API development for system architecture and system architecture;

[0022] Build the data exchange mechanism based on data bus for system architecture and system architecture;

[0023] Based on the data exchange mechanism of the files, the data exchange mechanism of API development, and the data exchange mechanism of the data bus, an integrated tool chain of system architecture and system architecture is constructed.

[0024] Preferably, the step 3 specifically includes:

[0025] Step 301, constructing a "three-ring" V model for the integrated design of system architecture and system architecture;

[0026] Step 302: Create an integrated modeling framework mechanism;

[0027] Step 303: Based on the “three-ring” V model and integrated modeling framework mechanism of the architecture and system architecture integrated design, a “three-layer” integrated modeling framework of the architecture and system architecture based on the model and centered on the architecture design is constructed.

[0028] Preferably, the step 301 specifically includes:

[0029] Construct a “three-ring” V model for model-based architecture and system architecture integrated design.

[0030] Preferably, the step 302 specifically includes:

[0031] Construct a framework mechanism for two integrated modeling methods.

[0032] Beneficial technical effects of this application:

[0033] The system architecture and system architecture integrated modeling method constructed in this application fully utilizes the advantage of the system model's only data source, reduces modeling workload, ensures information consistency between levels, improves the quality of complex equipment research and development, and shortens the development cycle of complex equipment. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 is a schematic diagram of a language element conversion mechanism provided in an embodiment of the present application;

[0035] Figure 2 It is a schematic diagram of the language element derivation inheritance mechanism provided in an embodiment of the present application;

[0036] Figure 3 is a schematic diagram of a language element dependency mechanism provided in an embodiment of the present application;

[0037] Figure 4 is a schematic diagram of a language element expansion mechanism provided in an embodiment of the present application;

[0038] Figure 5 is a schematic diagram of a language conversion mechanism based on the SysPhs standard provided in an embodiment of the present application;

[0039] Figure 6 is a schematic diagram of a language conversion mechanism based on the Sym standard provided in an embodiment of the present application;

[0040] Figure 7 It is a schematic diagram of a "three-core" integrated modeling language application framework centered on a class architecture modeling language application provided by an embodiment of the present application;

[0041] Figure 8 This is a schematic diagram of a model file data interaction mechanism that complies with XMI, XML and MOF standards provided in an embodiment of the present application;

[0042] Fig. 9 It is a schematic diagram of a model file data interaction mechanism that complies with the AP233 standard and is provided in an embodiment of the present application;

[0043] Fig.10 It is a schematic diagram of a model file data interaction mechanism that complies with the FMI standard and is provided in an embodiment of the present application;

[0044] Fig.11 It is a schematic diagram of a model file data interaction mechanism that complies with the ReqIF standard provided in an embodiment of the present application;

[0045] Fig.12 It is a schematic diagram of a data interaction mechanism based on software API development provided in an embodiment of the present application;

[0046] Fig.13 Schematic diagram of the data interaction mechanism of the OSLC-based Web service provided in the embodiment of the present application;

[0047] Fig.14 is a schematic diagram of a data interaction mechanism based on DDS provided in an embodiment of the present application;

[0048] Fig.15 It is a schematic diagram of a tool chain design framework based on a model architecture and system architecture integration centered on architecture modeling software provided in an embodiment of the present application;

[0049] Fig.16 It is a schematic diagram of a "triangle" integrated tool chain design framework centered on architecture modeling software provided by an embodiment of the present application;

[0050] Fig.17 It is a schematic diagram of a modeling tool selection path based on economic analysis provided in an embodiment of the present application;

[0051] Fig.18 It is a schematic diagram of the "three-ring" V model of the model-based system architecture and system architecture provided in the embodiments of the present application;

[0052] Fig.19 It is a schematic diagram of the construction mechanism of the integrated modeling method provided in the embodiment of the present application;

[0053] Fig. 20 It is a schematic diagram of the framework of a "three-layer" integrated modeling method centered on architecture design provided in an embodiment of the present application;

[0054] Fig.21 It is a schematic diagram of the compliance of the methodological framework provided in the embodiments of the present application with the ISO 15288 standard. DETAILED DESCRIPTION

[0055] The present application provides a method for integrated modeling of system architecture and system architecture, the method comprising the following steps: constructing an integrated language application mechanism of system architecture and system architecture based on a language conversion mechanism;

[0056] Build an integrated tool chain for architecture and system architecture based on data exchange mechanism; build an integrated modeling framework for matrix architecture and system architecture. This application establishes an integrated language application mechanism, tool chain platform and architecture design method framework for architecture and system architecture based on model, and realizes the integrated design of architecture and system architecture.

[0057] See also Figure 1-Figure 21 The present application provides a method for integrating system architecture and system architecture modeling, comprising the following steps:

[0058] Step 1: Build an integrated language application mechanism based on the system architecture and system architecture of the language conversion mechanism;

[0059] Step 2: Build an integrated tool chain of system architecture and system architecture based on data exchange mechanism;

[0060] Step 3: Build an integrated modeling framework for matrix architecture and system architecture.

[0061] Wherein, step 1 specifically includes:

[0062] Build a conversion mechanism between system architecture and system architecture language elements. Based on the underlying common meta-object construction mechanism MOF, it can realize the conversion between system architecture model elements (SysML) and system architecture model elements (UAFML), software architecture model elements (UML) and embedded architecture model elements (MARTE), forming a class architecture modeling language element conversion mechanism, such as Figure 1 .

[0063] Constructing an architecture and system architecture language element inheritance mechanism. In the process of system modeling, derivation or inheritance (Generalization) is a frequently used technical means. Downstream model elements can obtain all existing information of upstream model elements through derivation or inheritance. On this basis, the model can be added, deleted, and modified as needed, thereby reducing modeling time and improving information consistency. This application is based on the underlying common meta-object construction mechanism MOF to realize the construction of language element derivation or inheritance mechanisms between system architecture model elements (SysML) and system architecture model elements (UAFML), software architecture model elements (UML), and embedded architecture model elements (MARTE), such as Figure 2 .

[0064] Build a system architecture and system architecture language element traceability mechanism. The information dependency (Dependency) of language elements is a modeling mechanism often used in the same-level or cross-level modeling. Establishing information dependency relationships between elements is the basis for conducting model information statistics, relationship analysis, and change impact analysis. Information dependency is a weak coupling relationship mechanism relative to model transformation and model derivation. This relationship only indicates that changes to the upstream model may affect downstream model elements. Common model element information traceability relationships include use (Use), refinement (Refine), realization (Realization), trace (Trace) and allocation (Allocate). This application is based on the underlying common meta-object construction mechanism MOF to realize the construction of a language element dependency mechanism between system architecture model elements (SysML) and system architecture model elements (UAFML), software architecture model elements (UML) and embedded architecture model elements (MARTE), such as Figure 3 .

[0065] Build an extension mechanism for system architecture and system architecture language elements. In the process of system modeling, the original model elements sometimes cannot accurately express certain modeling requirements, and it is necessary to use the extension mechanism (Extension) of the modeling language elements to build some new constructs (stereotypes) to supplement the lack of original model element expressiveness. This application can build an extension mechanism for architecture modeling language elements based on the underlying common meta-object construction mechanism MOF, such as Figure 4 .

[0066] Construct a model conversion mechanism for architecture and system architecture based on language conversion standards. OMG released the SysPhs standard, which expands the semantics and syntax required for simulation models based on SysML, supports unified modeling of architecture data and simulation data in the same SysML modeling environment, and realizes the conversion of SysML modeling language to common physical simulation languages ​​(Modelica and Simulink). This application constructs an architecture modeling language conversion mechanism based on the SysPhs standard, such as Figure 5 Before the SysPhs standard was released, in order to achieve the conversion from SysML architecture modeling language to simulation language Modelica, OMG released the Sym standard and developed SysML4Modelica Profile to support the conversion of system architecture and simulation architecture at the language level. This application builds a language conversion mechanism based on the Sym standard, such as Figure 6 .

[0067] Based on the language element conversion mechanism, the language element inheritance mechanism, the language element traceability mechanism, the language element extension mechanism and the model conversion mechanism, an integrated modeling language application framework for system architecture and system architecture is constructed. Priority is given to mechanisms based on language element application, and integrated modeling is carried out in the same architecture modeling software, which can achieve good conversion and traceability relationships between multi-level architectures. If the same modeling environment cannot meet the needs of more professional modeling and analysis processes, you can consider using a cross-language application mechanism to maintain the consistency of two-level architecture information and reduce the waste caused by repeated modeling, thereby constructing a "three-heart" modeling language application framework centered on the application of class architecture modeling language, such as Figure 7 .

[0068] Wherein, step 2 specifically includes:

[0069] Build a file-based data exchange mechanism for system architecture and system architecture. Based on XMI, XML and MOF standards, data file exchange between tool software that supports OMG organizational language families UML, SysML, MARTE, UAF and UPDM can be realized, that is, support model data exchange based on XMI file format between system architecture modeling tools (support UAF or UPDM), software architecture modeling tools (support UML) and embedded system architecture modeling tools (support MARTE), and build a model file data interaction mechanism based on XMI, XML and MOF standards, such as Figure 8 ; Based on the AP233 standard, a file data interaction mechanism is built between different architecture modeling tools and professional design tools, such as Fig. 9 ; Based on the FMI standard, a file data interaction mechanism is built between the architecture modeling tool and the simulation modeling design tool, such as Fig.10 ; Based on the ReqIF standard, a file data interaction mechanism is built between the architecture modeling tool and the requirements management tool, such as Fig.11 .

[0070] Build data exchange mechanisms between different software based on software API development, such as Fig.12 .

[0071] Build a data exchange mechanism between the architecture and system architecture based on the data bus. Build a data interaction mechanism between the architecture modeling tool and the requirements management tool based on the OSLC Web service, such as Fig.13 . Based on DDS, the data interaction mechanism between architecture modeling tools and system simulation tools is constructed, such as Fig.14 .

[0072] Based on the data exchange mechanism of the files, the data exchange mechanism of API development, and the data exchange mechanism of the data bus, an integrated tool chain of system architecture and system architecture is constructed, such as Fig.15 .

[0073] From the framework, we can see that the tools that interact with the data of the architecture modeling tool are divided into management modeling tools, design modeling tools and simulation modeling tools. The architecture modeling tool is in the center. Design and simulation are carried out on the basis of architecture design. The tool chain jointly supports management work, thus constructing a "triangle" integrated tool chain design framework, such as Fig.16 .

[0074] From an economic perspective, when selecting a modeling tool, it is necessary to examine the software's compliance with the data transfer mechanism. First, the architecture and system architecture modeling should be as unified as possible, and the engineering import mechanism can be used to achieve seamless data transfer and use; if cross-tool software is required, it is recommended to give priority to software that meets specific document-based data exchange mechanisms, such as supporting XMI, AP233, FMI, ReqIF and other standard file import and export, or supporting OSLC Web service-based data exchange mechanisms to achieve data synchronization. If the document-based interaction mechanism cannot meet the requirements, consider a DDS-based data exchange mechanism and purchase data interaction middleware. Finally, consider point-to-point development based on software API. Therefore, this application constructs a modeling tool selection path based on economic analysis, such as Fig.17 .

[0075] Wherein, step 3 specifically includes:

[0076] Construct a "three-ring" V model of integrated design of model-based system architecture and system architecture. Based on the classic V model of aviation equipment development and combined with the experience of helicopter development, this application constructs a "three-ring" V model of integrated design of model-based system architecture and system architecture with helicopter characteristics. This model integrates system design and system design process, and is divided into three layers of strategy, mission and equipment at the system level, and three layers of helicopter, system and equipment at the system level, such as Fig.18. In the specific development process, the system engineering small closed loop is first carried out, including three closed loops: functional logic design and verification closed loop, one-dimensional design and simulation verification closed loop, and multi-dimensional design and simulation verification closed loop. Functional logic design and verification mainly refers to system architecture design, using UAF or DODAF system design framework and UAFML to carry out system requirements analysis and architecture design; one-dimensional design and simulation verification mainly refers to the time deduction and system contribution rate evaluation process carried out in combination with probabilistic algorithms; multi-dimensional design and simulation verification mainly refers to the system design and visual simulation deduction process in time and space; after completing the system engineering small closed loop, the system architecture design results, including equipment requirements, the interaction relationship between equipment and external systems, and the equipment operation background environment, will be passed to the system layer in the form of a model. A small closed loop of system engineering is carried out at the system level, specifically including three closed loops: system functional logic design and verification closed loop, system one-dimensional design and simulation verification closed loop, and system multi-dimensional design and simulation verification closed loop. The system functional logic design and simulation closed loop is similar to the system level, which mainly carries out demand capture, functional analysis and architecture design, and is generally carried out using the SysML modeling language combined with a certain modeling method; one-dimensional design and simulation closed loop mainly refers to system physical modeling and simulation based on the Modelica modeling language combined with one-dimensional modeling tools (MWorks, Dymola or AMEsim); multi-dimensional design and simulation mainly involves three-dimensional modeling, multi-physical field modeling and simulation analysis processes; after completing the system and system small closed loops, a multi-level virtual integration verification closed loop can be carried out, and the system-level high-confidence model can be brought into the system level to carry out system-level virtual integration simulation verification. After the physical entity manufacturing of the system is completed, a multi-level virtual-reality integration verification closed loop can be carried out to gradually realize the digital twin process of virtual-reality synchronization.

[0077] Construct two integrated modeling method framework creation mechanisms. Two ideas are used to construct integrated modeling methods. One is to use the system architecture modeling method UAF as the main body, extending from the system architecture layer downward to the system architecture layer; the other is to use the system architecture as the main body and extend upward to the system architecture layer, such as Fig.19 In order to be compatible with DoDAF, MoDAF and NAF equipment system modeling frameworks and enterprise architecture modeling frameworks, the UAF system modeling framework retains too many views, which need to be adaptively tailored during the system architecture modeling process. In contrast, the MagicGrid system architecture is relatively stable and simple, and is suitable as the main body of the integrated modeling framework.

[0078] Based on the “three-ring” V model of the integrated design of the system architecture and system architecture and the creation mechanism of the integrated modeling method framework, a “three-layer” integrated modeling method framework of the system architecture and system architecture based on the model centered on the architecture design is constructed, such as Fig. 20The integrated modeling method framework is divided into three layers: the system architecture layer, the system architecture layer, and the design implementation layer. Each layer consists of several domains. The system architecture layer consists of the strategic domain, the task domain, and the equipment domain. The system architecture layer is consistent with the MagicGrid methodology and consists of the problem domain and the solution domain. The design implementation layer consists of the design domain, the manufacturing domain, and the operation domain. Each column in the methodology is a perspective. The intersection of each domain and a certain perspective is the presentation and modeling process of the system or system under a certain perspective of the domain. On the basis of inheriting the five modeling perspectives of MagicGrid (demand, structure, behavior, parameters, and professional engineering), this method framework expands a "verification closed loop" perspective, thereby realizing the entire system engineering process of demand capture, functional analysis, architecture design, physical design, and verification closed loop; the strategic domain is to carry out modeling analysis at the national level, analyze the national strategic goals and the strategic resources that need to be deployed to achieve the strategic goals, as well as the strategic actions to be taken, and analyze and construct strategic success measurement indicators; the task domain and the equipment domain are to carry out modeling analysis at the industry level. In order to meet the national strategic actions, combined with their own advantages and challenges, the required task capabilities are analyzed. Taking the mission capability as input, analyze the required mission resource structure and the mission actions to be taken. Taking the mission domain as input, analyze the equipment structure and equipment functions required to implement the mission, and provide support for equipment project establishment; the problem domain of the system architecture is to carry out modeling analysis at the level of successfully developing a piece of equipment, and take the system architecture modeling results as input to sort out and analyze all stakeholders of the developed equipment to capture equipment-related requirements. With the mission action as the background environment, carry out functional analysis and decomposition of the equipment, build the functional logic prototype of the system, and clarify the functional performance requirements and logical architecture of the system; the solution domain of the system architecture is to carry out modeling analysis at the level of providing specific solutions, and carry out preliminary solution design from the three levels of helicopters, systems and equipment; the design domain, manufacturing domain and operation domain of design implementation are to carry out the physical design, simulation, integration and operation process of helicopters, systems and equipment from the perspective of physical implementation.

[0079] This application conducts a conformity analysis of the 15288 standard to demonstrate the correctness of the integrated approach created, such as Fig.21The modeling of the system architecture layer corresponds to the business or mission analysis process in the standard. The problem domain in the system architecture layer corresponds to the stakeholder needs and requirements definition process in the standard. The helicopter, system and equipment requirements analysis in the solution domain corresponds to the system requirements definition process in the standard. The structure, behavior and parameter modeling corresponds to the architecture definition process in the standard. The design domain corresponds to the design definition process and the design implementation process in the standard. The manufacturing and operation domains correspond to the integration process, transition process and operation process in the standard. The professional engineering perspective corresponds to the system analysis process in the standard. The verification closed-loop perspective corresponds to the verification process and validation process in the standard. The analysis shows that the constructed system architecture and system architecture integrated design method conform to the ISO 15288 standard, covering most of the analysis processes of the technical process in the standard, of which the maintenance process and the disposal process are not covered. process) and is beyond the scope of this application.

[0080] It should be noted that:

[0081] (1) An integrated language application mechanism based on the system architecture and system architecture of the language conversion mechanism;

[0082] (2) An integrated tool chain for architecture and system architecture based on data exchange mechanisms;

[0083] (3) An integrated modeling framework for matrix architecture and system architecture.

[0084] The system architecture and system architecture integrated modeling method constructed in this application fully utilizes the advantage of the system model's only data source, reduces modeling workload, ensures information consistency between levels, improves the quality of complex equipment research and development, and shortens the development cycle of complex equipment.

Claims

1. A method for integrating system architecture and system architecture modeling, characterized in that: The method comprises the following steps: Step 1: Build an integrated language application mechanism based on the system architecture and system architecture of the language conversion mechanism; Step 2: Build an integrated tool chain of system architecture and system architecture based on data exchange mechanism; Step 3: Build an integrated modeling framework for matrix architecture and system architecture.

2. The method according to claim 1, characterized in that The language conversion mechanism includes a language element conversion mechanism, a language element inheritance mechanism, a language element tracing mechanism, a language element extension mechanism and a model conversion mechanism.

3. The method according to claim 2, characterized in that The step 1 specifically includes: Build a mechanism for converting system architecture and system architecture language elements; Build the inheritance mechanism of system architecture and system architecture language elements; Build a system architecture and system architecture language element traceability mechanism; Build an extension mechanism based on architecture and system architecture language elements; Build a model conversion mechanism for the system architecture and system architecture based on language conversion standards; Based on the language element conversion mechanism, the language element inheritance mechanism, the language element tracing mechanism, the language element extension mechanism and the model conversion mechanism, a system architecture and system architecture integrated modeling language application framework is constructed.

4. The method according to claim 1, characterized in that: The data exchange mechanism includes a file data exchange mechanism, an API development data exchange mechanism, and a data bus data exchange mechanism.

5. The method according to claim 4, characterized in that The step 2 comprises: Build file-based data exchange mechanisms for architecture and system architecture; Build data exchange mechanism based on API development for system architecture and system architecture; Build the data exchange mechanism based on data bus for system architecture and system architecture; Based on the data exchange mechanism of the files, the data exchange mechanism of API development, and the data exchange mechanism of the data bus, an integrated tool chain of system architecture and system architecture is constructed.

6. The method according to claim 1, characterized in that The step 3 specifically includes: Step 301, constructing a "three-ring" V model for the integrated design of system architecture and system architecture; Step 302: Create an integrated modeling framework mechanism; Step 303: Based on the "three-ring" V model and integrated modeling framework mechanism of the architecture and system architecture integrated design, a model-based architecture and system architecture "three-layer" integrated modeling framework centered on architecture design is constructed.

7. The method according to claim 6, characterized in that The step 301 specifically includes: Construct a "three-ring" V model for model-based architecture and system architecture integrated design.

8. The method according to claim 6, characterized in that The step 302 specifically includes: Construct a framework mechanism for two integrated modeling methods.

Images