Multilevel system interface design and management method based on SysML language

Abstract

The invention discloses a multi-level system interface design and management method based on a SysML language, and the interface design method comprises the steps: 1, in a conceptual design stage, designing a use scene of system operation by adopting the SysML language, and defining an external interface of a system based on an interaction behavior of the system and an external environment in the use scene; step 2, in the logic design stage, defining components in the system, logic interfaces among the components and interface transmission from an external interface of the system to the components by adopting an SysML language; and step 3, in a physical design stage, defining physical interfaces among the components in the equipment layer to express a physical implementation mode of logic interfaces among the equipment. According to the technical scheme, the problems that in traditional system engineering, in a document-based interface definition mode, due to the fact that the consistency of the interfaces can only be guaranteed through manpower, design errors are introduced, and due to an interface management mode, due to the fact that a corresponding N2 graph needs to be established in each system level, the design errors are caused possibly are solved. And unified management of interfaces is not facilitated, and errors are easily introduced in a transmission process.

Description

Technical Field

[0001] The present invention relates to the field of system engineering technology, but is not limited to it, and in particular to a multi-level system interface design and management method based on SysML language. Background Art

[0002] System engineering is an engineering technology for developing complex systems and has been widely used in the aviation field. With the increase in system complexity and integration, traditional system engineering methods can no longer meet the development needs of modern systems.

[0003] Interface issues have always been the focus of complex system development. Failures caused by interface coordination problems are common during system development. Therefore, interface definition and management are an important task in the development of multi-level complex systems. In traditional system engineering, on the one hand, a document-based interface definition method is used to define interface requirements using interface control diagrams and interface control files. Since interface information is scattered in various documents, the consistency of the interface can only be guaranteed by manpower, and there will be inconsistencies in the interface expressions in different documents, which ultimately leads to inconsistent interface definitions and design errors introduced by coordination problems. On the other hand, in interface management solutions, the traditional document-based method uses N 2 Figure management interface, for a complex system with multiple system levels, the interface needs to be passed down layer by layer, and a corresponding N 2 This method is not conducive to the unified management of interfaces, because the documents and N 2 Diagrams cannot express the relationship between upper and lower layer interfaces, and it is easy to introduce errors during the transmission process. Summary of the invention

[0004] The purpose of the present invention is to solve the above problems. The embodiment of the present invention provides a multi-level system interface design and management method based on SysML language to solve the problem of design errors introduced by inconsistent interface definitions due to the document-based interface definition method in traditional system engineering, as the consistency of the interface can only be guaranteed by manpower, and the interface management method, as corresponding N 2 This is not conducive to the unified management of interfaces and is prone to introducing errors during the transmission process.

[0005] The technical solution of the present invention is as follows: In a first aspect, an embodiment of the present invention provides a multi-level system interface design method based on SysML language, comprising:

[0006] Step 1: In the conceptual design phase, SysML is used to design the usage scenarios of the system operation, and the external interface of the system is defined based on the interaction between the system and the external environment in the usage scenarios.

[0007] Step 2: In the logic design phase, SysML is used to define the components in the system, the logical interfaces between the components, and the interface transfer from the system's external interface to the components.

[0008] Step 3, in the physical design phase, define the physical interfaces between the components in the device layer to express the physical implementation of the logical interface between devices.

[0009] Optionally, in the multi-level system interface design method based on SysML language as described above, the multi-level system is divided into a task system layer, a system layer, a subsystem layer, a subsystem layer and a device layer from top to bottom; the step 1 comprises:

[0010] In the conceptual design phase, the SysML language is used in the task system layer to design various usage scenarios for the system operation, and the system functions are identified in each usage scenario. Based on the interaction between the system and the external environment in the designed usage scenarios, the external interface of the system is defined.

[0011] Optionally, in the multi-level system interface design method based on SysML language as described above, in step 1,

[0012] An activity diagram in SysML language is used to define the usage scenario of the system. The scenario activity diagram reflects the interaction between the system and the external environment, and the system function is reflected in the scenario activity diagram;

[0013] The external interface of the multi-level system is defined by an internal block diagram of the SysML language, and the interface relationship between the system and the external environment is represented by connecting the interface defined on the system block with the interface defined on the external environment block.

[0014] Optionally, in the multi-level system interface design method based on SysML language as described above, step 2 comprises:

[0015] Step 21, in the logic design phase, the system function is decomposed into sub-functions undertaken by the components that make up the system, and each sub-function is allocated to each component; each component is formed in the same system level;

[0016] Step 22, for a multi-level system, the sub-functions in the subsystem layer are further decomposed and allocated to components of the subsystem layer or the device layer, and the sub-functions in the subsystem layer are further decomposed and allocated to components of the device layer;

[0017] Step 23, define the logical interface between the components in the system, and the interface transfer from the system external interface to the components.

[0018] Optionally, in the multi-level system interface design method based on SysML language as described above, in step 2,

[0019] An activity diagram in SysML language is used to define the decomposition and allocation of system functions. The activity diagram defines each sub-function decomposed from the system function, and each sub-function and function allocation is implemented by the components of the system;

[0020] Use the block definition diagram of SysML language to define each component of the system;

[0021] The internal block diagram of SysML language is used to define the logical interface between the components in the system, define the interface on each component block, define the interface connection relationship between the component blocks, and define the transmission relationship between the external interface of the system and the component blocks.

[0022] Optionally, in the multi-level system interface design method based on SysML language as described above, step 3 comprises:

[0023] Step 31, for each component distributed at different positions in the device layer, design the physical interface between each component in the device layer, and use a connector to connect the associated physical interfaces;

[0024] Step 32, defining the physical composition of the system, including: the components of the device layer in the system, and the physical interfaces between the components;

[0025] Step 33, defining a mapping relationship between physical interfaces and logical interfaces in the device layer to express the physical implementation of logical interfaces between devices.

[0026] Optionally, in the multi-level system interface design method based on SysML language as described above, in step 2 and step 3,

[0027] The internal block diagram of SysML language is used to define the interface of each component in the device layer, the proxy port in SysML language is used to represent the logical interface, and the full port in SysML language is used to represent the physical interface;

[0028] The type of the logical interface is defined by an interface block, and the type of the physical interface is defined by a block; the interface blocks used to define various types of interfaces and the blocks also define interface requirements and information transmitted in the interface.

[0029] Optionally, in the multi-level system interface design method based on SysML language as described above, in step 3,

[0030] The physical composition of the system is constructed using blocks representing component parts and blocks representing physical interface types in the SysML language.

[0031] In a second aspect, the embodiment of the present invention also provides a multi-level system interface management method based on SysML language, including:

[0032] The interface designed by using the multi-level system interface design method based on SysML language as described in any one of the above items is managed.

[0033] Optionally, in the multi-level system interface management method based on SysML language as described above, the interface management method includes:

[0034] After completing the interface design, use the SysML model to manage the interface, including:

[0035] The information displayed in the table is customized by defining a table template; the required interface information of each level is extracted from the model using the table template to generate an interface management list.

[0036] The beneficial effects of the present invention are as follows: the embodiment of the present invention provides a multi-level system interface design and management method based on SysML language, and defines interfaces in three design stages, namely, conceptual design stage, logical design stage and physical design stage; wherein, in the conceptual design stage, the SysML language is used to design the use scenario of the system operation, and the external interface of the system is defined based on the interactive behavior between the system and the external environment in the use scenario; in the logical design stage, the SysML language is used to define the components in the system, the logical interfaces between the components, and the interface transmission from the system external interface to the components; in the physical design stage, the physical interface between the components in the device layer is defined to express the physical implementation mode of the logical interface between the devices. The technical solution provided by the embodiment of the present invention provides a complete set of interface design and management methods based on SysML language for multi-level systems, defines interfaces in the conceptual design stage, logical design stage and physical design stage, and gradually realizes the transformation from external interface to physical interface; in addition, the interface model is established by using SysML language to realize the uniqueness of interface expression; and the transmission of interfaces at different levels is realized, and the traceability of interfaces is realized; furthermore, the management of interfaces is realized based on the established SysML model. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The accompanying drawings are used to provide a further understanding of the technical solution of the present invention and constitute a part of the specification. Together with the embodiments of the present application, they are used to explain the technical solution of the present invention and do not constitute a limitation on the technical solution of the present invention.

[0038] Figure 1A schematic diagram of a flow chart of a multi-level system interface design method based on SysML language provided in an embodiment of the present invention;

[0039] Figure 2 is a schematic diagram of a scene activity diagram in an embodiment of the present invention;

[0040] Figure 3 A schematic diagram of an external interface of a definition system in an embodiment of the present invention;

[0041] Figure 4 A schematic diagram of system function decomposition in an embodiment of the present invention;

[0042] Figure 5 A schematic diagram of defining system components in an embodiment of the present invention;

[0043] Figure 6 A schematic diagram of defining logical interfaces between components in a system according to an embodiment of the present invention;

[0044] Figure 7 A schematic diagram of defining a physical interface in a definition system according to an embodiment of the present invention;

[0045] Figure 8 A schematic diagram of a physical component of a definition system in a definition system in an embodiment of the present invention;

[0046] Fig. 9 A schematic diagram of a mapping relationship between a physical interface and a logical interface in a system defined in an embodiment of the present invention;

[0047] Fig.10 A schematic diagram of defining a table template in an embodiment of the present invention;

[0048] Fig.11 It is a schematic diagram of logical interface management in an embodiment of the present invention. DETAILED DESCRIPTION

[0049] The accompanying drawings are used to provide a further understanding of the technical solution of the present invention and constitute a part of the specification. Together with the embodiments of the present application, they are used to explain the technical solution of the present invention and do not constitute a limitation on the technical solution of the present invention.

[0050] As described in the above background technology, in traditional system engineering, interface definition and management solutions are difficult to avoid various problems: on the one hand, the document-based interface definition method, because the consistency of the interface can only be guaranteed by manpower, will lead to inconsistent interface expressions in different documents, which will eventually lead to inconsistent interface definitions and design errors caused by coordination problems; on the other hand, the document-based interface management method uses N 2Figure management interface, for a complex system with multiple system levels, the interface needs to be passed down layer by layer, and a corresponding N 2 This method is not conducive to the unified management of interfaces, because the documents and N 2 Diagrams cannot express the relationship between upper and lower layer interfaces, and it is easy to introduce errors during the transmission process.

[0051] Obviously, with the increase of system complexity and integration, the traditional system engineering methods can no longer meet the development needs of modern systems. Model-based system engineering (MBSE) came into being. MBSE uses a unified modeling language to establish system models and define the elements in the system model and the relationship between the elements. On this basis, it can reduce design errors introduced by coordination problems and improve system development efficiency. As the core part of MBSE, SysML language has been widely used in the development of complex systems such as aviation and aerospace.

[0052] In view of the above problems, an embodiment of the present invention provides an interface design and management method based on SysML language, which can be applied to MBSE of helicopters.

[0053] SysML is the foundation of MBSE and is applicable to the architecture definition of various complex physical systems. The method of expressing system architecture using SysML is called MBSE methodology. Many MBSE methodologies have been developed internationally. The methodology is closely related to the characteristics of the system and the working mode of the organization. Each MBSE methodology has its specific application background. These MBSE methodologies generally do not have detailed interface design, transmission and management solutions for multi-level systems.

[0054] The interface design and management method based on SysML language provided in the embodiment of the present invention is applied to MBSE of helicopters. Since a helicopter is a typical multi-level physical system, the definition of the interface involves multiple system levels. The helicopter field adopts five system levels to carry out architecture definition work, namely the mission system layer, the system layer (also known as: the whole machine layer), the subsystem layer, the subsystem layer and the equipment layer. The use of MBSE to carry out work requires solving the problems of interface design and interface transmission at each level. The existing MBSE methodology does not involve the interface design scheme of multi-level systems.

[0055] In summary, the present invention proposes a multi-level system interface design and management method based on SysML language. The main purpose is to solve the following problems:

[0056] 1. Form an interface design process based on SysML language;

[0057] 2. Use SysML language to establish interface model and realize the uniqueness of interface expression;

[0058] 3. Realize the expression and transmission of interfaces at different levels, and establish the traceability relationship between interfaces at different levels;

[0059] 4. Implement interface management based on the established SysML model.

[0060] The present invention provides the following specific embodiments which can be combined with each other. The same or similar concepts or processes may not be described in detail in some embodiments.

[0061] Figure 1 A flowchart of a multi-level system interface design method based on the SysML language provided in an embodiment of the present invention. Among them, the multi-level system is divided into a task system layer, a system layer, a subsystem layer, a subsystem layer and a device layer from top to bottom. The multi-level system interface design method provided in an embodiment of the present invention adopts the definition of interfaces in three design stages, namely the conceptual design stage, the logical design stage and the physical design stage. The external interface of the system is defined in the conceptual design stage, the logical interface between the components of the system is defined in the logical design stage, and the physical interface between the components is defined in the physical design stage.

[0062] like Figure 1 The multi-level system interface design method based on SysML language provided by the embodiment of the present invention includes the following steps:

[0063] Step 1: In the conceptual design phase, SysML is used to design the usage scenarios of the system operation, and the external interface of the system is defined based on the interaction between the system and the external environment in the usage scenarios.

[0064] Step 2: In the logic design phase, SysML is used to define the components in the system, the logical interfaces between the components, and the interface transfer from the system's external interface to the components.

[0065] Step 3, in the physical design phase, define the physical interfaces between the components in the device layer to express the physical implementation of the logical interface between devices.

[0066] In an implementation of the embodiment of the present invention, the implementation of step 1 may include:

[0067] In the conceptual design phase, the SysML language is used in the task system layer to design various usage scenarios for the system operation, and the system functions are identified in each usage scenario. Based on the interaction between the system and the external environment in the designed usage scenarios, the external interface of the system is defined.

[0068] In this implementation, in step 1, an activity diagram of the SysML language is specifically used to define the usage scenario of the system. The scenario activity diagram reflects the interaction between the system and the external environment, and the scenario activity diagram reflects the system function; Figure 2 The figure is a schematic diagram of a scene activity diagram in an embodiment of the present invention.

[0069] The external interface of the multi-level system is defined by the internal block diagram of the SysML language. The interface relationship between the system and the external environment is represented by the connection between the interface defined on the system block and the interface defined on the external environment block. Figure 3 FIG. 1 is a schematic diagram of defining the external interface of the system in an embodiment of the present invention.

[0070] In an implementation of the embodiment of the present invention, the implementation process of the above step 2 may include:

[0071] Step 21, in the logic design phase, the system function is decomposed into various sub-functions undertaken by various components of the system, and each sub-function is allocated to each component; each component is formed in the same system level, and different components of the system are formed in each level;

[0072] Step 22, for a multi-level system, the sub-functions in the subsystem layer are further decomposed and allocated to components of the subsystem layer or the device layer, and the sub-functions in the subsystem layer are further decomposed and allocated to components of the device layer;

[0073] Step 23, define the logical interface between the components in the system, and the interface transfer from the system external interface to the components.

[0074] In step 2 of the implementation, an activity diagram of the SysML language is used to define the decomposition and allocation of system functions. The activity diagram defines each sub-function decomposed from the system function, and each sub-function and function allocation is implemented by the components of the system; Figure 4 FIG. 1 is a schematic diagram of system function decomposition in an embodiment of the present invention.

[0075] In addition, the block definition diagram of SysML language is used to define the various components of the system; Figure 5 FIG. 1 is a schematic diagram of defining system components in an embodiment of the present invention.

[0076] Furthermore, the internal block diagram of SysML language is used to define the logical interface between the components in the system, define the interface on each component block, define the interface connection relationship between each component block, and define the transmission relationship between the external interface of the system and each component block; Figure 6FIG. 1 is a schematic diagram of defining logical interfaces between components in a system according to an embodiment of the present invention.

[0077] In an implementation of the embodiment of the present invention, the implementation process of the above step 3 may include:

[0078] Step 31, for each component distributed at different positions in the device layer, design the physical interface between each component in the device layer, and use a connector to connect the associated physical interfaces; Figure 7 FIG. 1 is a schematic diagram of defining a physical interface in a system according to an embodiment of the present invention.

[0079] Step 32, define the physical composition of the system, including: the components of the device layer in the system, and the physical interfaces between the components; Figure 8 As shown, it is a schematic diagram of defining the physical components of a system in a definition system in an embodiment of the present invention.

[0080] Step 33, define the mapping relationship between the physical interface and the logical interface in the device layer to express the physical implementation method of the logical interface between devices. Fig. 9 FIG. 1 is a schematic diagram of defining a mapping relationship between a physical interface and a logical interface in a system in an embodiment of the present invention.

[0081] In step 2 and step 3 of the above implementation, the internal block diagram of the SysML language is used to define the interface of each component in the device layer, the proxy port (proxyport) in the SysML language is used to represent the logical interface, and the full port (fullport) in the SysML language is used to represent the physical interface.

[0082] The type of logical interface is defined by interface block, and the type of physical interface is defined by block; the interface block used to define various types of interfaces and the block also define interface requirements and information transmitted in the interface.

[0083] In addition, in step 3 of the above implementation, the physical composition of the system is composed of blocks representing component parts and blocks representing physical interface types in the SysML language.

[0084] Based on the multi-level system interface design method based on SysML language provided in the above embodiments of the present invention, an embodiment of the present invention further provides a multi-level system interface management method based on SysML language, including:

[0085] The interface designed by the multi-level system interface design method based on SysML language provided by any of the above embodiments is managed; the specific interface management method can be:

[0086] After completing the interface design, use the SysML model to manage the interface, including:

[0087] The information displayed in the table is customized by defining a table template; the required interface information of each level is extracted from the model using the table template to generate an interface management list.

[0088] The multi-level system interface design and management method based on SysML language provided by the embodiment of the present invention defines interfaces in three design stages, namely, the conceptual design stage, the logical design stage and the physical design stage; wherein, in the conceptual design stage, the SysML language is used to design the use scenario of the system operation, and the external interface of the system is defined based on the interactive behavior between the system and the external environment in the use scenario; in the logical design stage, the SysML language is used to define the components in the system, the logical interfaces between the components, and the interface transmission from the system external interface to the components; in the physical design stage, the physical interface between the components in the device layer is defined to express the physical implementation mode of the logical interface between the devices. The technical solution provided by the embodiment of the present invention provides a complete set of interface design and management methods based on SysML language for multi-level systems, defines interfaces in the conceptual design stage, the logical design stage and the physical design stage, and gradually realizes the transformation from external interface to physical interface; in addition, the interface model is established by using SysML language to realize the uniqueness of interface expression; and the transmission of interfaces at different levels is realized, and the traceability of interfaces is realized; furthermore, the management of interfaces is realized based on the established SysML model.

[0089] The implementation of the multi-level system interface design and management method based on SysML language provided by the present invention is schematically described below through a specific implementation example.

[0090] Implementation Example

[0091] The multi-level system interface design method of this implementation example adopts the definition of interfaces in three design stages, namely the conceptual design stage, the logical design stage and the physical design stage. The external interface of the system is defined in the conceptual design stage, the logical interface between the components of the system is defined in the logical design stage, and the physical interface between the components is defined in the physical design stage. The system is divided into the task system layer, system layer, subsystem layer, subsystem layer and device layer from top to bottom;

[0092] (a) If Figure 1 The process shown in the figure, the implementation example provides a multi-level system interface design method including the following steps:

[0093] Step 1: In the conceptual design phase, design various usage scenarios of the system operation at the task system level, identify system functions in each usage scenario, and define the external interface of the system based on the defined usage scenarios.

[0094] Step 2, in the logical design phase, decompose the system functions into sub-functions undertaken by the various components that make up the system; and allocate each sub-function to each component; for example, one sub-function is allocated to one component (or subsystem or device) formed by multiple subsystems at the same level. After the allocation is completed, define the logical interfaces between the components in the system. For a multi-level system, the decomposition can be continued downwards according to the above method.

[0095] Step 3, the physical design phase focuses on the implementation of the system. Since the components of the device layer may be distributed in different locations and cannot be connected together in geometric space, it is necessary to further design the connection method between the components in the device layer, that is, the physical interface.

[0096] The specific implementation methods of the above three stages are described as follows:

[0097] (1) In the conceptual design phase, the SysML language activity diagram is used to define the system usage scenarios. Figure 2 FIG. 1 is a schematic diagram of a scene activity diagram in an embodiment of the present invention. Figure 2 The scenario activity diagram shown in the figure describes the interaction between the system and the operator. The system function can be identified from the scenario activity diagram. Based on the interaction behavior in the defined scenario activity diagram, the external interface of the system can be further defined. The external interface of the system is defined using the internal block diagram of the SysML language. Figure 3 As shown, it is a schematic diagram of defining the external interface of the system in an embodiment of the present invention, and there is an interface relationship between the system and the operator. An interface pS is defined on the block (Actor) expressing the operator, and an interface PA is defined on the block (System) expressing the system. The two interfaces are connected by a connector to define the interface relationship between the Actor and the System.

[0098] (2) In the logic design phase, the activity diagram of SysML language is used to define the decomposition and allocation of system functions. Figure 4 FIG. 1 is a schematic diagram of system function decomposition in an embodiment of the present invention. Figure 4 It is expressed that the system function (Function) is decomposed into sub-function 1 (Function_1) and sub-function 2 (Function_2), and sub-function 1, sub-function 2 and function allocation are implemented by the system components SystemElement1 and SystemElement2.

[0099] The SysML language block definition diagram is used to define the components of the system. Figure 5 FIG. 1 is a schematic diagram of defining system components in an embodiment of the present invention. Figure 5 The system shown (System) consists of components SystemElement1 and SystemElement2.

[0100] The internal block diagrams of SysML language are used to define the logical interfaces between the components of the system. Figure 6 FIG. 1 is a schematic diagram of defining logical interfaces between components in a system according to an embodiment of the present invention. Figure 6 Define interface pSE2 on the block expressing component SystemElement1, define interface PSE1 on the block expressing SystemElement2, and connect these two interfaces with a connector. Thus, the interface relationship between SystemElement1 and SystemElement2 is defined.

[0101] It is especially important to note that in the logic design phase, interfaces are passed down layer by layer. The following uses the System's external interface pA as an example to illustrate the interface transfer process. Figure 6 The logical interface between SystemElement1 and SystemElement2, components of the System, is defined. Figure 6 The frame of the internal block definition diagram represents System. The interface pA of System is expressed on the frame. Interface pA is defined on the block expressing SystemElement1 and connected to interface pA on the frame with a connector, thereby transferring the interface from System to SystemElement1.

[0102] (3) In the physical design phase, the specific implementation of the interface is defined, and the internal block diagram of the SysML language is also used for expression. The interface expression method from the physical perspective is different from that from the logical perspective. The interface types are divided into logical interfaces and physical interfaces. There are two ways to express interfaces in the SysML language, one is proxyport and the other is fullport. In this invention, proxyport is used to express the logical interface, such as Figure 3 , Figure 6 . Use fullport to express the physical interface, such as Figure 7 FIG. 1 is a schematic diagram of defining a physical interface in a system according to an embodiment of the present invention. Figure 7 fpSE2 and fpSE1 in the diagram are physical interfaces, which are connected by a connector. Thus, the physical interface between SystemElement1 and SystemElement2 is defined.

[0103] The type of logical interface is defined by interface block, and the type of physical interface is defined by block. Figure 6 The interface types of the logical interfaces pSE1 and pSE2 are defined by interface block pSE1_SE2. Figure 7 The interface types of the physical interfaces fpSE1 and fpSE2 are defined using block PhysicalInterface.

[0104] After the interface type is defined, define the physical components of the system. The PhysicalInterface block representing the physical interface type and the SystemElement1 and SystemElement2 blocks representing the components together constitute the physical components of the System, such as Figure 8 As shown, it is a schematic diagram of defining the physical components of a system in a definition system in an embodiment of the present invention.

[0105] These interface blocks that define logical interfaces and physical interfaces further define the requirements of the interfaces and the information transmitted in the interfaces. Fig. 9 FIG. 1 is a schematic diagram of a physical implementation method of defining a logical interface in a system according to an embodiment of the present invention. Fig. 9 The interface block of the logical interface pSE1_SE2 defines the information parameter1 transmitted in the interface.

[0106] Finally, define the mapping relationship between the physical interface and the logical interface in the device layer to express the physical implementation of the logical interface between devices. Fig. 9 , connect pSE1_SE2 and PhysicalInterface with an association relationship, expressing that pSE1_SE2 is implemented by PhysicalInterface. In this way, the parameters and requirements in the logical interface pSE1_SE2 will be passed to the physical interface PhysicalInterface.

[0107] (II) Management methods:

[0108] After the interface definition is completed, you can use the SysML model to manage the interface. By defining a table template, you can customize the information displayed in the table, such as Fig.10 FIG. 1 is a schematic diagram of defining a table template in an embodiment of the present invention. Fig.10 The table template shown in the table extracts the information of the interface block that expresses the logical interface. Applying this table template can extract the required interfaces at each level from the model and generate the following Fig.11 The table shown, Fig.11It is a schematic diagram of logical interface management in an embodiment of the present invention.

[0109] The multi-level system interface design and management method provided by the embodiment of the present invention adopts three design stages to define interfaces. External interfaces are identified in the conceptual design stage, interface allocation and transfer are implemented in the logical design stage, and interface implementation methods are defined in the physical design stage. Among them, in the logical design stage, the SysML internal block definition diagram is used to implement layer-by-layer transfer of interfaces; SysML proxy port is used to define logical interfaces, and SysML full port is used to define physical interfaces; interface block is used to define logical interface specifications, and block is used to define physical interface specifications; based on the interface rules defined in the present invention, all interface information can be extracted according to attributes, which is convenient for interface management.

[0110] Although the embodiments disclosed in the present invention are as above, the contents are only embodiments adopted to facilitate understanding of the present invention and are not intended to limit the present invention. Any technician in the field to which the present invention belongs can make any modifications and changes in the form and details of implementation without departing from the spirit and scope disclosed in the present invention, but the patent protection scope of the present invention shall still be subject to the scope defined in the attached claims.

Claims

1. A multi-level system interface design method based on SysML language, characterized in that: The multi-level system interface design method comprises: Step 1: In the conceptual design phase, SysML is used to design the usage scenarios of the system operation, and the external interface of the system is defined based on the interaction between the system and the external environment in the usage scenarios. Step 2: In the logic design phase, SysML is used to define the components in the system, the logical interfaces between the components, and the interface transfer from the system's external interface to the components. Step 3, in the physical design phase, define the physical interfaces between the components in the device layer to express the physical implementation of the logical interface between devices.

2. The multi-level system interface design method based on SysML language according to claim 1, characterized in that: The multi-level system is divided into a task system layer, a system layer, a subsystem layer, a subsystem layer and a device layer from top to bottom; the step 1 comprises: In the conceptual design phase, the SysML language is used in the task system layer to design various usage scenarios for the system operation, and the system functions are identified in each usage scenario. Based on the interaction between the system and the external environment in the designed usage scenarios, the external interface of the system is defined.

3. The multi-level system interface design method based on SysML language according to claim 2, characterized in that: In the step 1, An activity diagram in SysML language is used to define the usage scenario of the system. The scenario activity diagram reflects the interaction between the system and the external environment, and the system function is reflected in the scenario activity diagram; The external interface of the multi-level system is defined by an internal block diagram of the SysML language, and the interface relationship between the system and the external environment is represented by connecting the interface defined on the system block with the interface defined on the external environment block.

4. The multi-level system interface design method based on SysML language according to claim 3, characterized in that: The step 2 comprises: Step 21, in the logic design phase, the system function is decomposed into sub-functions undertaken by the components that make up the system, and each sub-function is allocated to each component; each component is formed in the same system level; Step 22, for a multi-level system, the sub-functions in the subsystem layer are further decomposed and allocated to components of the subsystem layer or the device layer, and the sub-functions in the subsystem layer are further decomposed and allocated to components of the device layer; Step 23, define the logical interface between the components in the system, and the interface transfer from the system external interface to the components.

5. The multi-level system interface design method based on SysML language according to claim 4, characterized in that: In the step 2, An activity diagram in SysML language is used to define the decomposition and allocation of system functions. The activity diagram defines each sub-function decomposed from the system function, and each sub-function and function allocation is implemented by the components of the system; Use the block definition diagram of SysML language to define each component of the system; The internal block diagram of SysML language is used to define the logical interface between the components in the system, define the interface on each component block, define the interface connection relationship between the component blocks, and define the transmission relationship between the external interface of the system and the component blocks.

6. The multi-level system interface design method based on SysML language according to claim 5, characterized in that: The step 3 comprises: Step 31, for each component distributed at different positions in the device layer, design the physical interface between each component in the device layer, and use a connector to connect the associated physical interfaces; Step 32, defining the physical composition of the system, including: the components of the device layer in the system, and the physical interfaces between the components; Step 33, defining a mapping relationship between physical interfaces and logical interfaces in the device layer to express the physical implementation of logical interfaces between devices.

7. The multi-level system interface design method based on SysML language according to claim 6, characterized in that: In step 2 and step 3, The internal block diagram of SysML language is used to define the interface of each component in the device layer, the proxy port in SysML language is used to represent the logical interface, and the full port in SysML language is used to represent the physical interface; The type of the logical interface is defined by an interface block, and the type of the physical interface is defined by a block; the interface blocks used to define various types of interfaces and the blocks also define interface requirements and information transmitted in the interface.

8. The multi-level system interface design method based on SysML language according to claim 7, characterized in that: In step 3, The physical composition of the system is constructed using blocks representing component parts and blocks representing physical interface types in the SysML language.

9. A multi-level system interface management method based on SysML language, characterized in that: include: The interface designed by the multi-level system interface design method based on SysML language as described in any one of claims 1 to 8 is managed.

10. The multi-level system interface management method based on SysML language according to claim 9, characterized in that: The management method of the interface includes: After completing the interface design, use the SysML model to manage the interface, including: The information displayed in the table is customized by defining a table template; the required interface information of each level is extracted from the model using the table template to generate an interface management list.

Images