A multi-level system interface design and management method based on SysML language

Abstract

The present invention discloses a multi-level system interface design and management method based on the SysML language, wherein the interface design method comprises: step 1, in the conceptual design stage, using the SysML language to design the use scenario of the system operation, and defining the external interface of the system based on the interactive behavior between the system and the external environment in the use scenario; step 2, in the logical design stage, using the SysML language to define the components in the system, the logical interface between the components, and the interface transmission from the system external interface to the components; step 3, in the physical design stage, defining the physical interface between the components in the device layer to express the physical implementation of the logical interface between the devices. The technical solution of the present invention solves the problem of the document-based interface definition method in traditional system engineering, which may lead to design errors introduced by inconsistent interface definitions because the consistency of the interface can only be guaranteed by manpower, and the interface management method, which requires the establishment of corresponding N 2 This is not conducive to the unified management of interfaces and is prone to introducing errors during the transmission process.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of system engineering, and particularly relates to a multi-level system interface design and management method based on a SysML language. BACKGROUND

[0002] System engineering is an engineering technology for developing complex systems, and has been widely applied in the field of aviation. With the improvement of system complexity and integration, the traditional system engineering method cannot meet the development needs of modern systems.

[0003] Interface problems have always been the focus of complex system development, and faults caused by interface coordination problems are widespread in the system development process. Therefore, the definition and management of interfaces are important work in the development of multi-level complex systems. In the traditional system engineering, on the one hand, the interface definition method based on documents is used to define the interface requirements by using interface control diagrams and interface control files. Since the interface information is scattered in various documents, the consistency of the interface can only be guaranteed by manpower, and the phenomenon of inconsistent interface expression forms in different documents may occur, which ultimately leads to uncoordinated definition of the interface and design errors caused by coordination problems. On the other hand, in the interface management scheme, the traditional method based on documents uses N 2 diagrams to manage interfaces. For complex systems with multiple system levels, interfaces need to be passed down layer by layer, and N 2 diagrams corresponding to each system level need to be established. This method is not conducive to the unified management of interfaces, and errors are easily introduced in the transmission process because the documents and N 2 diagrams cannot express the relationship between the upper and lower interfaces. SUMMARY

[0004] The purpose of the present application is to solve the above problems. The embodiments of the present application provide a multi-level system interface design and management method based on a SysML language to solve the problems of the traditional system engineering, that is, the interface definition method based on documents, the consistency of the interface can only be guaranteed by manpower, which may lead to design errors caused by uncoordinated definition of the interface, and the interface management method, since N 2 diagrams corresponding to each system level need to be established, which is not conducive to the unified management of interfaces and is prone to errors in the transmission process.

[0005] The technical scheme of the present application is as follows: in a first aspect, the embodiments of the present application provide a multi-level system interface design method based on a SysML language, which comprises the following steps:

[0006] Step 1: in the conceptual design stage, the use scenario of system operation is designed by using the SysML language, and the external interface of the system is defined based on the interaction behavior of the system and the external environment in the use scenario.

[0007] Step 2, in the logical design phase, define the components in the system, the logical interfaces between the components, and the interface transmission from the external interface of the system to the interfaces between the components using SysML language;

[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 interfaces between the 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 task system layer, system layer, sub-system layer, sub-system layer and device layer from top to bottom; the step 1 comprises:

[0010] Conceptual design phase, in the task system layer, design the use scenarios of the system using SysML language, and identify the system functions in each use scenario, and define the external interface of the system according to the interaction behavior between the system and the external environment in the designed use scenario.

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

[0012] The use scenarios of the system are defined using the activity diagram of SysML language, the interaction behavior between the system and the external environment is embodied in the scenario activity diagram, and the system functions are embodied in the scenario activity diagram;

[0013] The external interface of the multi-level system is defined using the internal block diagram of 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, the step 2 comprises:

[0015] Step 21, in the logical design phase, decompose the system functions into sub-functions undertaken by each component constituting the system, and allocate each sub-function to each component; each component is formed in the same system level;

[0016] Step 22, for a multi-level system, further decompose the sub-functions in the sub-system layer and allocate them to the components in the sub-system layer or the device layer, and further decompose the sub-functions in the sub-system layer and allocate them to the components in the device layer;

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

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

[0019] The activity diagram using SysML language defines the decomposition and allocation of system functions, and each sub-function of the system function decomposition is defined in the activity diagram, and each sub-function and function allocation is implemented by the components of the system;

[0020] The block definition diagram using SysML language defines each component of the system;

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

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

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

[0024] Step 32, define the physical components of the system, including: the components of the device layer in the system, and the physical interface between each component;

[0025] Step 33, 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 the devices.

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

[0027] The internal block diagram using SysML language defines the interface of each component in the device layer, the logical interface is represented by a proxy port in SysML language, and the physical interface is represented by a full port in SysML language;

[0028] Wherein, 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 block and the block used to define various types of interfaces 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 the step 3,

[0030] The physical composition of the system is constituted by blocks representing the components in the SysML language and blocks representing the physical interface types.

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

[0032] The interface designed by the multi-level system interface design method based on the SysML language according to any one of the above is managed.

[0033] Optionally, the multi-level system interface management method based on the SysML language according to the above, the management mode of the interface comprises:

[0034] After the interface design is completed, the interface is managed by using the SysML model, comprising:

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

[0036] The embodiment of the present application provides a multi-level system interface design and management method based on the SysML language, which defines the interface in three design stages, namely the conceptual design stage, the logical design stage and the physical design stage; in the conceptual design stage, the use scenario of the system operation is designed by using the SysML language, and the external interface of the system is defined based on the interaction behavior between the system and the external environment in the use scenario; in the logical design stage, the components in the system, the logical interface between the components and the interface transmission between the external interface of the system and the components are defined by using the SysML language; 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 scheme provided by the embodiment of the present application provides a complete interface design and management method based on the SysML language for the multi-level system, defines the interface in the conceptual design stage, the logical design stage and the physical design stage, and gradually realizes the conversion from the external interface to the physical interface; in addition, the interface model is established by using the SysML language to realize the uniqueness of the interface expression; and the interface transmission in different levels is realized to realize the traceability of the interface; furthermore, the management of the interface is realized based on the established SysML model. BRIEF DESCRIPTION OF DRAWINGS

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

[0038] Figure 1A flowchart of a multi-level system interface design method based on a SysML language according to an embodiment of the present application is provided.

[0039] Figure 2 A schematic diagram of a scenario activity diagram according to an embodiment of the present application is provided.

[0040] Figure 3 A schematic diagram of defining a system external interface according to an embodiment of the present application is provided.

[0041] Figure 4 A schematic diagram of system function decomposition according to an embodiment of the present application is provided.

[0042] Figure 5 A schematic diagram of defining a system component according to an embodiment of the present application is provided.

[0043] Figure 6 A schematic diagram of defining a logical interface between system components according to an embodiment of the present application is provided.

[0044] Figure 7 A schematic diagram of defining a physical interface in a system according to an embodiment of the present application is provided.

[0045] Figure 8 A schematic diagram of defining a system physical component in a system according to an embodiment of the present application is provided.

[0046] Figure 9 A schematic diagram of defining a mapping relationship between a physical interface and a logical interface in a system according to an embodiment of the present application is provided.

[0047] Figure 10 A schematic diagram of defining a table template according to an embodiment of the present application is provided.

[0048] Figure 11 A schematic diagram of logical interface management according to an embodiment of the present application is provided. DETAILED DESCRIPTION

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

[0050] As described in the above background, in traditional system engineering, interface definition and management schemes are difficult to avoid various problems: on the one hand, the interface definition method based on documents, because the consistency of the interface can only be guaranteed by manpower, the phenomenon of inconsistent expression forms of interfaces in different documents will occur, which ultimately leads to inconsistent definition of interfaces, and design errors caused by coordination problems; on the other hand, the interface management method based on documents, using N 2The interface needs to be passed down layer by layer, and the corresponding N 2 Figures, and the N 2 Figures, and the N

[0051] Obviously, with the increase of system complexity and integration, the traditional system engineering method cannot meet the needs of modern system development. Model-based system engineering (MBSE) is emerging, which uses unified modeling language to establish system model and define elements and their relationships in the system model. On this basis, design errors caused by coordination problems can be reduced, and system development efficiency can be improved. SysML language, as the core part of MBSE, has been widely used in the development of complex systems such as aviation and aerospace.

[0052] To solve the above problems, the embodiment of the application provides an interface design and management method based on SysML language, which can be applied to MBSE of a helicopter.

[0053] SysML language is the basis of MBSE and is suitable for architecture definition of various complex physical systems. The method of expressing system architecture using SysML language is called MBSE methodology. Many MBSE methodologies have emerged internationally, and 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 schemes for multi-level systems.

[0054] The interface design and management method based on SysML language provided by the embodiment of the application is applied to MBSE of a helicopter. Since the 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, task system level, system level (also known as: whole machine level), sub-system level, sub-system level and equipment level. The MBSE work needs to solve the problems of interface design and interface transmission of each level. The existing MBSE methodology does not involve the interface design scheme of the multi-level system.

[0055] In summary, the application provides a multi-level system interface design and management method based on SysML language. The following problems are solved:

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

[0057] 2. Establishing an interface model using SysML language to realize the uniqueness of interface expression;

[0058] 3. Realize the expression and transmission of interfaces at different levels and establish traceability relationships 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 that 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 The present invention provides a flowchart of a multi-level system interface design method based on the SysML language according to an embodiment of the present invention. 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 by an embodiment of the present invention adopts the method of defining interfaces in three design stages: 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 various components of the system is defined in the logical design stage, and the physical interface between the various 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 system's operational scenarios and define the system's external interfaces based on the system's interaction with the external environment in the scenarios.

[0064] Step 2: In the logic design phase, SysML is used to define the components of 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 interfaces between devices.

[0066] In one 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 behavior between the system and the external environment in the designed usage scenarios, the external interface of the system is defined.

[0068] In the implementation, the activity diagram of the SysML language is used to define the use scenario of the system in step 1, the interaction between the system and the external environment is embodied in the scenario activity diagram, and the system function is embodied in the scenario activity diagram. Figure 2 As shown in the figure, it is a schematic diagram of the scenario activity diagram in the embodiment of the present application.

[0069] The external interface of the multi-level system is defined by the internal block diagram of the SysML language, and 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 As shown in the figure, it is a schematic diagram of defining the external interface of the system in the embodiment of the present application.

[0070] In an implementation of the embodiment of the present application, the implementation process of step 2 can include:

[0071] Step 21, in the logical design stage, the system function is decomposed into each sub-function taken by each component part of the system, and each sub-function is allocated to each component part; each component part is formed in the same system level, and different component parts of the system are formed in each level;

[0072] Step 22, for the multi-level system, the sub-function in the system level is further decomposed and allocated to the component part in the sub-system level or the device level, and the sub-function in the sub-system level is further decomposed and allocated to the component part in the device level;

[0073] Step 23, the logical interface between each component part in the system is defined, and the interface transmission between the external interface of the system and each component part is defined.

[0074] In step 2 of the implementation, the activity diagram of the SysML language is used to define the decomposition and allocation of the system function, each sub-function decomposed from the system function is defined in the activity diagram, and each sub-function is implemented by the component part of the system; as shown in the figure, Figure 4 As shown in the figure, it is a schematic diagram of the system function decomposition in the embodiment of the present application.

[0075] In addition, the block definition diagram of the SysML language is used to define each component part of the system; as shown in the figure, Figure 5 As shown in the figure, it is a schematic diagram of defining the component part of the system in the embodiment of the present application.

[0076] Furthermore, the internal block diagram of the SysML language is used to define the logical interface between the component parts in the system, the interface on each component part block is defined, and the interface connection relationship between each component part block is defined, and the transmission relationship between the external interface of the system and each component part block is defined; as shown in the figure, Figure 6Fig. 1 is a schematic diagram illustrating the definition of logical interfaces between components in a system according to an embodiment of the present application.

[0077] In one implementation of the embodiment of the present application, the implementation process of step 3 can include:

[0078] Step 31, for each component in the device layer distributed in different locations, design the physical interfaces between the components in the device layer, and connect the associated physical interfaces using connectors; for example, Figure 7 Fig. 2 is a schematic diagram illustrating the definition of physical interfaces in a system according to an embodiment of the present application.

[0079] Step 32, define the physical components of the system, including the components in the device layer of the system and the physical interfaces between the components; for example, Figure 8 Fig. 3 is a schematic diagram illustrating the definition of the physical components of a system according to an embodiment of the present application.

[0080] Step 33, define the mapping relationship between the physical interfaces and the logical interfaces in the device layer, to express the physical implementation of the logical interfaces between devices; for example, Figure 9 Fig. 4 is a schematic diagram illustrating the mapping relationship between the physical interfaces and the logical interfaces in a system according to an embodiment of the present application.

[0081] In steps 2 and 3 of the above implementation, the internal block diagram of the SysML language is used to define the interfaces of the components in the device layer, the proxy port in the SysML language is used to represent the logical interfaces, and the full port in the SysML language is used to represent the physical interfaces.

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

[0083] In addition, in step 3 of the above implementation, the physical components of the system are composed of the blocks representing the components and the blocks representing the types of the physical interfaces in the SysML language.

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

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

[0086] After the interface design is completed, the interface is managed using the SysML model, including:

[0087] By defining a table template, information displayed in the table is customized; the interface information of each level required 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 the SysML language provided by the embodiment of the application defines the interface in three design stages, namely, a conceptual design stage, a logical design stage and a physical design stage; in the conceptual design stage, the SysML language is used to design the use scenario of system operation, and the external interface of the system is defined based on the interaction behavior of the system and the external environment in the use scenario; in the logical design stage, the SysML language is used to define each component in the system, the logical interface between each component, and the interface transmission between the external interface of the system and each component; in the physical design stage, the physical interface between each component in the device layer is defined to express the physical implementation mode of the logical interface between devices. The technical solution provided by the embodiment of the application provides a complete interface design and management method based on the SysML language for a multi-level system, defines the interface in the conceptual design stage, the logical design stage and the physical design stage, and gradually realizes the conversion from the external interface to the physical interface; in addition, the SysML language is used to establish an interface model to realize the uniqueness of interface expression; and the interface transmission in different levels is realized to realize the traceability of the interface; furthermore, the management of the interface is realized based on the established SysML model.

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

[0090] Implementation Example

[0091] The multi-level system interface design method of the implementation example defines the interface in three design stages, namely, a conceptual design stage, a logical design stage and a physical design stage. The external interface of the system is defined in the conceptual design stage, the logical interface between each component of the system is defined in the logical design stage, and the physical interface between each component is defined in the physical design stage. The system is divided into a task system layer, a system layer, a sub-system layer and a device layer from top to bottom;

[0092] As shown in the flowchart of Figure 1 , the multi-level system interface design method provided by the implementation example includes the following steps:

[0093] Step 1, in the conceptual design phase, design the various usage scenarios of the system operation in the task hierarchy layer, and identify the system functions in the various usage scenarios, define the external interface of the system according to the defined usage scenarios.

[0094] Step 2, in the logical design phase, decompose the system functions into sub-functions undertaken by each component part of the system; and allocate each sub-function to each component part; for example, 1 sub-function is allocated to 1 component part formed by multiple subsystems (or subsystems or devices) in the same layer. After the allocation is completed, the logical interface between each component part in the system is defined. For a multi-layer system, it can continue to be decomposed downward according to the above method.

[0095] Step 3, the physical design phase focuses on the implementation of the system, since each component part of the device layer may be distributed in different locations and cannot be connected together in geometric space. Therefore, it is necessary to further design the connection mode between each component part in the device layer, i.e. the physical interface.

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

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

[0098] (2) In the logical design phase, the activity diagram of the SysML language is used to define the decomposition and allocation of the system functions. As shown in Figure 4 , it is a schematic diagram of the system function decomposition in the embodiment of the present application, Figure 4 The system function (Function) is decomposed into sub-function 1 (Function_1) and sub-function 2 (Function_2) in

[0099] The block definition diagram of SysML language is used to define the components of the system. As shown in Figure 5 , it is a schematic diagram for defining the components of the system in the embodiment of the present application, Figure 5 The system (System) is composed of components SystemElement1 and SystemElement2.

[0100] The internal block diagram of SysML language is used to define the logical interface between the components in the system. As shown in Figure 6 , it is a schematic diagram for defining the logical interface between the components in the system in the embodiment of the present application, Figure 6 The interface pSE2 is defined on the block expressing the component SystemElement1, and the interface PSE1 is defined on the block expressing SystemElement2. The two interfaces are connected by the connector. Thus, the interface relationship between SystemElement1 and SystemElement2 is defined.

[0101] It is particularly pointed out that the interface is passed down layer by layer in the logical design stage. The passing process of the interface is described below taking the external interface pA of System as an example. Figure 6 The internal block definition diagram in Figure 6 represents System. The interface pA of System is expressed on the block. The interface pA is defined on the block expressing SystemElement1, and is connected with the interface pA on the block by the connector. Thus, the passing of the interface from System to SystemElement1 is realized.

[0102] (3) In the physical design stage, the specific implementation mode of the interface is defined, and the internal block diagram of SysML language is also used to express. The interface expression mode in the physical perspective is different from that in the logical perspective, and the interface type is divided into logical interface and physical interface. There are two expression modes of the interface in the SysML language, one is proxyport, and the other is fullport. The logical interface is expressed by proxyport in the present application, as shown in Figure 3 , Figure 6 The physical interface is expressed by fullport, as shown in Figure 7 , it is a schematic diagram for defining the physical interface in the system in the embodiment of the present application. Figure 7 The fpSE2 and fpSE1 in are physical interfaces, and they are connected by the 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 type of logical interface pSE1, pSE2 in is defined by interface block pSE1_SE2. Figure 7 The interface type of physical interface fpSE1 and fpSE2 in is defined by block PhysicalInterface.

[0104] After the interface type is defined, the physical composition of the system is defined. The block PhysicalInterface representing the type of physical interface, together with the blocks SystemElement1 and SystemElement2 representing the components, constitute the physical composition of System, as shown in Figure 8 which is a schematic diagram of defining the physical composition of the system in the embodiment of the present application.

[0105] The interface block defining the logical interface and the block defining the physical interface further define the requirements of the interface and the information transferred in the interface. As shown in Figure 9 which is a schematic diagram of defining the physical implementation of the logical interface in the system in the embodiment of the present application, Figure 9 The interface block representing the logical interface pSE1_SE2 defines the information parameter1 transferred in the interface.

[0106] Finally, the mapping relationship between the physical interface and the logical interface in the device layer is defined to express the physical implementation of the logical interface between devices. For example, as shown in Figure 9 pSE1_SE2 and PhysicalInterface are connected by the association relationship, expressing that pSE1_SE2 is implemented by PhysicalInterface. Thus, the parameters and requirements in the logical interface pSE1_SE2 are transferred to the physical interface PhysicalInterface.

[0107] (II) Management method:

[0108] After the interface is defined, the interface can be managed by using the SysML model. By defining the table template, the information displayed in the table is customized, as shown in Figure 10 which is a schematic diagram of defining the table template in the embodiment of the present application, Figure 10 The table template extracts the information of the interface block representing the logical interface. By applying the table template, the required interfaces at each level can be extracted from the model, and the table as shown in Figure 11 is generated. Figure 11A schematic diagram of the logical interface management in the embodiments of the present application.

[0109] The multi-level system interface design and management method provided by the embodiments of the present application defines the interface by three design stages. In the conceptual design stage, the external interface is identified; in the logical design stage, the allocation and transmission of the interface are implemented; and in the physical design stage, the implementation mode of the interface is defined. In the logical design stage, the layer-by-layer transmission of the interface is implemented by using the SysML internal block definition diagram; the logical interface is defined by using the SysML proxy port, and the physical interface is defined by using the SysML full port; the logical interface specification is defined by using the interface block, and the physical interface specification is defined by using the block; based on the interface rules defined by the present application, all the interface information can be extracted according to the attributes, so as to facilitate the interface management work.

[0110] Although the embodiments of the present application are disclosed as above, the content is only the embodiments adopted for the purpose of facilitating the understanding of the present application, and is not intended to limit the present application. Any modification and change in the form and details can be made by any person skilled in the art without departing from the spirit and scope of the present application. The patent protection scope of the present application shall be subject to the scope defined by the appended 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 stage, the use scenarios of system operation are designed by using the SysML language, and the external interface of the system is defined based on the interaction behavior of the system and the external environment in the use scenario; Step 2, in the logical design stage, the components in the system, the logical interface between the components, and the interface transmission between the external interface of the system and the components are defined by using the SysML language; Step 3, 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; Wherein, the multi-level system is divided into task system layer, system layer, sub-system layer, sub-system layer and device layer from top to bottom; the step 1 comprises: In the conceptual design stage, the use scenarios of system operation are designed in the task system layer by using the SysML language, and the system function is identified in each use scenario, and the external interface of the system is defined according to the interaction behavior of the system and the external environment in the designed use scenario; The step 2 comprises: Step 21, in the logical design stage, the system function is divided into each sub-function which is undertaken by each component forming the system, and each sub-function is allocated to each component; each component is formed in the same system layer; Step 22, for the multi-level system, the sub-function in the sub-system layer is further divided and allocated to the components in the sub-system layer or the device layer, and the sub-function in the sub-system layer is further divided and allocated to the components in the device layer; Step 23, the logical interface between the components in the system and the interface transmission between the external interface of the system and the components are defined; The step 3 comprises: Step 31, for each component distributed in different positions in the device layer, the physical interface between the components in the device layer is designed, and the associated physical interface is connected by using the connector; Step 32, the physical composition of the system is defined, including the components in the device layer in the system and the physical interface between the components; Step 33, the mapping relationship between the physical interface and the logical interface in the device layer is defined to express the physical implementation mode of the logical interface between the devices.

2. The method of claim 1, wherein the method is based on a SysML language. In the step 1, The use scenarios of the system are defined by using the activity diagram of the SysML language, the interaction behavior between the system and the external environment is embodied in the scenario activity diagram, and the system function is embodied in the scenario activity diagram; The external interface of the multi-level system is defined by using the 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 and the interface defined on the external environment block.

3. The method of claim 1, wherein the method is based on a SysML language. In the step 2, The decomposition and allocation of the system function are defined by using the activity diagram of the SysML language, each sub-function decomposed from the system function is defined in the activity diagram, and each sub-function and the function allocation are realized by the components of the system; The components of the system are defined by using the block definition diagram of the SysML language; The internal block diagram of the SysML language defines the logical interface between the components in the system, defines the interface on each component block, and defines the interface connection relationship between each component block, and defines the transfer relationship between the external interface of the system and each component block.

4. The method of claim 1, wherein the method is based on a SysML language. In the step 2 and step 3, The internal block diagram of the SysML language defines the interface of each component in the device layer, the logical interface is represented by the proxy port in the SysML language, and the physical interface is represented by the full port in the SysML language. The type of the logical interface is defined by the interface block, and the type of the physical interface is defined by the block; the interface block and the block used to define various types of interfaces also define interface requirements and information transferred in the interface.

5. The method of claim 4, wherein the method is based on a SysML language. In the step 3, The physical composition of the system is composed of blocks representing components and blocks representing physical interface types in the SysML language.

6. A multi-level system interface management method based on SysML language, characterized in that, It includes: The interface designed by the multi-level system interface design method based on the SysML language according to any one of claims 1-5 is managed.

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

Images