SysML-based collaborative design method and apparatus for behavioral architecture of multi-level complex systems
By employing SysML's multi-level complex system behavioral architecture collaborative design method, and through configuring role permissions and joint simulation verification, the model decomposition and integration problems in cross-level collaborative design are solved, achieving high efficiency, consistency, and traceability in complex system design.
Patent Information
- Application Number
- CN202611283420.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-24
- Publication Date
- 2026-11-17
AI Technical Summary
Existing technologies lack cross-level and cross-disciplinary collaborative design processes in complex system design, have insufficient model decomposition and integration mechanisms, and struggle to guarantee design consistency, making it difficult to meet the requirements of efficiency, consistency, and verifiability in the behavioral architecture design of multi-level complex systems.
A collaborative design method for the behavioral architecture of multi-level complex systems based on SysML is adopted. By configuring the role permissions of designers at different levels, model decomposition and integration are achieved. Behavioral design is carried out using module definition diagrams and state machine diagrams. Combined with co-simulation, the consistency of the overall functional logic is verified, ensuring the consistency and traceability of the design process.
It enables efficient collaborative design of multi-level system behavioral architecture, improves the efficiency and accuracy of cross-level and cross-professional collaborative design, and ensures the consistency and traceability of design results.
Smart Images

Figure CN123114419A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of complex system modeling and simulation technology, and more specifically, to a method and apparatus for collaborative design of the behavioral architecture of multi-level complex systems based on the System Modeling Language (SysML). Background Technology
[0002] Complex system design in fields such as aviation, aerospace, shipbuilding, and automotive spans multiple levels, disciplines, and domains, encompassing stages such as requirements analysis, functional behavior design, and architecture design, and requires frequent collaborative work at different stages. Traditional design methodologies, relying on document-based design patterns, inevitably involve extracting and transforming effective information from various documents, leading to several drawbacks in complex system design: First, the ambiguity of natural language easily causes misunderstandings and design iterations; second, documents struggle to automatically adapt to design changes, resulting in low processing efficiency and difficulty in tracking technical status; third, designers are primarily responsible for their own documents rather than directly addressing the design object, hindering early design verification and validation.
[0003] Driven by information technology and modeling techniques, the design of complex systems is gradually shifting from document-based systems engineering to model-based systems engineering (MBSE). SysML, as a unified and verifiable formal modeling language, supports data consistency and traceability from requirements refinement analysis to behavioral architecture design. Currently, model-based behavioral architecture design for complex systems mainly focuses on a comprehensive design process guided by methodologies such as MagicGrid and Harmony-SE. For example, it involves functional design of the system through use case models, function flow models, and architecture models, or identifying key system functions through behavioral diagrams and designing the system architecture through module definition diagrams.
[0004] However, existing collaborative design technologies lack a unified collaborative mechanism for multi-level behavioral architecture decomposition and integration verification. Specifically, they suffer from the following drawbacks: (1) Mainstream design methods are mostly focused on single-level behavioral function design, making it difficult to support multi-level collaborative design scenarios such as platform-system-subsystem levels; (2) Collaborative modeling technologies primarily focus on controlling the editing permissions of model elements, making it difficult to support the entire collaborative design process of overall model distribution, branch model construction and detailed design, and model integration verification; (3) Permission control technologies lack a unified management approach combining role configuration, package permission control, and branches, making it difficult to achieve progressive refinement and consistency verification of behavioral models. Overall, existing design methods still have shortcomings in cross-level collaborative design, model decomposition and integration processes, and permission and branch collaboration mechanisms, making it difficult to meet the requirements of efficiency, consistency, and verifiability in multi-level complex system behavioral architecture design. In conclusion, there is room for improvement in existing technologies. Summary of the Invention
[0005] This invention provides a SysML-based collaborative design method and apparatus for the behavioral architecture of multi-level complex systems, which can solve the technical problems in the prior art such as unclear cross-level and cross-disciplinary collaborative design processes, insufficient model decomposition and integration mechanisms, and difficulty in ensuring design consistency.
[0006] According to one aspect of the present invention, a collaborative design method for the behavioral architecture of multi-level complex systems based on SysML is provided, applicable to collaborative design scenarios of behavioral architecture of complex systems at the platform level, system level, and subsystem level. The collaborative design method for the behavioral architecture of multi-level complex systems includes: S1, configuring the role permissions of designers at different levels to control the viewing and editing scope of design content at each level; S2, the upper-level designer publishes a baseline branch and creates lower-level branches, providing a unified foundation and permission isolation for the parallel refinement design of lower-level designs; S3, lower-level designers refine the behavioral design in their respective branches, realizing independent modeling and logical verification of each subsystem or subsystem; S4, the upper-level designer creates a merged branch and integrates the models of each subsystem or subsystem in step S3, and verifies the overall functional logic consistency through joint simulation, thus completing the collaborative design of the behavioral architecture of multi-level complex systems.
[0007] Furthermore, in step S1, configuring the role permissions of designers at different levels further includes: configuring the superior designer as a product administrator, enabling them to view, edit, and manage online projects; configuring the subordinate designer as a project member, enabling them to view and edit specified online projects; and through fine-grained permission configuration of package elements, granting the subordinate designer read and write permissions for the corresponding design modules, while granting read-only permissions for other modules.
[0008] Furthermore, in step S2, the senior designer takes the task flow or scenario as design input, defines the system's composition architecture through the module definition diagram, defines the port and signal interaction relationships between the components through the internal module diagram, generates baseline branches, and then creates each subordinate branch based on the baseline branches.
[0009] Furthermore, in step S3, refining the behavior design includes: lower-level designers analyzing the activity flow of their respective systems through activity diagrams, designing the state transitions of each system in detail through state machine diagrams, and clarifying the state classification, corresponding activity behaviors, and state transition triggering conditions.
[0010] Further, in step S4, the senior designer creates a merge branch, and merges the refined models from each subordinate branch into the merge branch in turn, recording the model element change information during the merging process; then, a co-simulation is carried out through a custom simulation panel to verify the consistency between the system's static architecture and dynamic behavior. If the system's static architecture and dynamic behavior are consistent, the collaborative design of the multi-level complex system behavior architecture is completed; if a problem is found, the process returns to the corresponding level optimization in step S3 to re-verify the consistency between the optimized system's static architecture and dynamic behavior until the system's static architecture and dynamic behavior are consistent.
[0011] Furthermore, the method can be recursively applied to multi-level complex systems at the platform-system-subsystem level: In platform-system collaborative design, the platform-level designer acts as the superior and the system-level designer acts as the subordinate; steps S2 to S4 are repeated until all subsystem designs are completed; in system-subsystem collaborative design, the system-level designer acts as the superior and the subsystem-level designer acts as the subordinate; steps S2 to S4 are repeated until all subsystem designs are completed.
[0012] According to another aspect of the present invention, a SysML-based collaborative design device for the behavioral architecture of multi-level complex systems is provided. This SysML-based collaborative design device is used to implement the SysML-based collaborative design method for the behavioral architecture of multi-level complex systems as described above. The SysML-based collaborative design device for the behavioral architecture of multi-level complex systems includes: a permission configuration module for configuring the role permissions of designers at different levels, controlling the viewing and editing scope of design content at each level; a model distribution module for allowing higher-level designers to publish baseline branches and create lower-level branches, providing a unified foundation and permission isolation for parallel refinement design at the lower levels; a behavior design module for allowing lower-level designers to refine behavior design in their respective branches, realizing independent modeling and logical verification of each subsystem or subsystem; and a model integration and verification module for allowing higher-level designers to create merged branches and integrate lower-level models, verifying the overall functional logic consistency through joint simulation.
[0013] Furthermore, the permission configuration module configures senior designers as product administrators, granting them the authority to view, edit, and manage online projects; and configures junior designers as project members, granting them the authority to view and edit specified online projects. It also supports fine-grained permission configuration for package elements.
[0014] Furthermore, the model integration and verification module has a built-in simulation engine with a development interface for custom simulation panels. It can display the state transitions, activity flows, and signal interaction data of each system / subsystem in real time. If the simulation does not meet the requirements, the problem can be quickly located and fed back to the behavior design module.
[0015] Furthermore, the device is compatible with the SysML language modeling standard.
[0016] This invention provides a SysML-based collaborative design method for the behavioral architecture of multi-level complex systems. This method, based on SysML, utilizes standardized role-based access control, branched model management, and integrated verification processes to achieve efficient collaborative design of multi-level system behavioral architectures. It ensures consistency and traceability in the design process, significantly improving the efficiency and accuracy of cross-level and cross-disciplinary collaborative design. Therefore, compared with existing technologies, the SysML-based collaborative design method for the behavioral architecture of multi-level complex systems standardizes the design process of complex systems by introducing a collaborative mechanism of branch management and access control, achieving efficient collaboration in multi-level design and ensuring consistency and traceability between design results and design requirements. Attached Figure Description
[0017] The accompanying drawings, which form part of this specification, are provided to further illustrate embodiments of the invention and, together with the textual description, explain the principles of the invention. It is obvious that the drawings described below are merely some embodiments of the invention, and those skilled in the art can obtain other drawings based on these drawings without any creative effort.
[0018] Figure 1 This is a flowchart of a SysML-based collaborative design method for the behavioral architecture of multi-level complex systems according to an embodiment of the present invention;
[0019] Figure 2 This is a module definition diagram of the aircraft platform composition definition according to an embodiment of the present invention;
[0020] Figure 3 This is an internal module diagram of the internal structure of an aircraft platform according to an embodiment of the present invention;
[0021] Figure 4This is a schematic diagram of system branch building and package permission configuration according to an embodiment of the present invention;
[0022] Figure 5 These are detailed design drawings of the behavior of various systems of the aircraft according to embodiments of the present invention;
[0023] Figure 6 This is a schematic diagram of the model integration process according to an embodiment of the present invention;
[0024] Figure 7 This is a schematic diagram of a simulation verification panel according to an embodiment of the present invention;
[0025] Figure 8 This is a schematic diagram of the composition structure of a SysML-based collaborative design device for the behavioral architecture of multi-level complex systems according to an embodiment of the present invention.
[0026] The above figures include the following reference numerals:
[0027] 801. Permission Configuration Module; 802. Model Distribution Module; 803. Behavior Design Module; 804. Model Integration and Validation Module. Detailed Implementation
[0028] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit the present invention or its application or use. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0029] It should be noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments according to this application. As used herein, the singular form is intended to include the plural form as well, unless the context clearly indicates otherwise. Furthermore, it should be understood that when the terms "comprising" and / or "including" are used in this specification, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof.
[0030] Unless otherwise specifically stated, the relative arrangement, numerical expressions, and values of the components and steps set forth in these embodiments do not limit the scope of the invention. It should also be understood that, for ease of description, the dimensions of the various parts shown in the drawings are not drawn to actual scale. Techniques, methods, and devices known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and devices should be considered part of the specification. In all examples shown and discussed herein, any specific values should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values. It should be noted that similar reference numerals and letters in the following figures denote similar items; therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.
[0031] like Figures 1 to 7 As shown in the figure, a SysML-based collaborative design method for the behavioral architecture of multi-level complex systems is provided according to a specific embodiment of the present invention. This method is applicable to collaborative design scenarios of behavioral architecture of complex systems at the platform level, system level, and subsystem level. The collaborative design method for the behavioral architecture of multi-level complex systems includes: S1, configuring the role permissions of designers at different levels to control the viewing and editing scope of design content at each level; S2, the upper-level designer publishes a baseline branch and creates lower-level branches to provide a unified foundation and permission isolation for the parallel refinement design of lower-level designs; S3, lower-level designers refine the behavioral design in their respective branches to achieve independent modeling and logical verification of each subsystem or subsystem; S4, the upper-level designer creates a merged branch and integrates the models of each subsystem or subsystem in step S3, and verifies the overall functional logic consistency through joint simulation to complete the collaborative design of the behavioral architecture of multi-level complex systems.
[0032] This configuration approach provides a SysML-based collaborative design method for the behavioral architecture of multi-level complex systems. This method, based on SysML, utilizes standardized role-based access control, branched model management, and integrated verification processes to achieve efficient collaborative design of multi-level system behavioral architectures. It ensures consistency and traceability in the design process, significantly improving the efficiency and accuracy of cross-level and cross-disciplinary collaborative design. Therefore, compared with existing technologies, the SysML-based collaborative design method for the behavioral architecture of multi-level complex systems provided by this invention standardizes the design process of complex systems by introducing a collaborative mechanism of branch management and access control, achieving efficient collaboration in multi-level design and ensuring consistency and traceability between design results and design requirements.
[0033] Furthermore, in this invention, to avoid misoperation and data conflicts at different levels, step S1 configures the role permissions for designers at different levels, further including: configuring the superior designer as a product administrator, granting them the permission to view, edit, and manage online projects; and configuring the subordinate designer as a project member, granting them the permission to view and edit specified online projects. Simultaneously, through fine-grained permission configuration of package elements, subordinate designers are granted read and write permissions for corresponding design modules, while other modules are read-only, ensuring that personnel at each level can only access the design modules they are responsible for, thus avoiding misoperation and data conflicts.
[0034] Furthermore, in this invention, in order to prevent mutual interference between lower-level branches, in step S2, the upper-level designer takes the task flow or scenario as design input, defines the system's composition architecture through a module definition diagram, defines the port and signal interaction relationships between the components through an internal module diagram, generates a baseline branch as a unified basis for model distribution, and then creates each lower-level branch based on the baseline branch, so that lower-level designers can carry out design independently under the premise of inheriting a unified architecture, thus preventing mutual interference.
[0035] Furthermore, in this invention, step S3, refining the behavior design includes: lower-level designers analyzing the activity flow of their respective systems through activity diagrams, designing the state transitions of each system in detail through state machine diagrams, and clarifying the state classification, corresponding activity behaviors, and state transition triggering conditions.
[0036] As a specific embodiment of the present invention, in order to ensure that the behavioral design of each subsystem / subsystem is carried out independently and to improve the efficiency of parallel design, lower-level designers use SysML models such as activity diagrams and state machine diagrams to construct the detailed behavioral logic of the system in the allocated branches using a state-nested activity approach. This clarifies the state classification, corresponding activity behaviors, and state transition triggering conditions, thus completing the functional logic design and verification at this level. This step ensures that the behavioral design of each subsystem / subsystem is carried out independently and improves the efficiency of parallel design.
[0037] Furthermore, in this invention, in step S4, the senior designer creates a merge branch, sequentially merges the refined models from each subordinate branch into the merge branch, and records the model element change information during the merging process; then, a co-simulation is carried out through a custom simulation panel to verify the consistency between the system's static architecture and dynamic behavior. If the system's static architecture and dynamic behavior are consistent, the collaborative design of the multi-level complex system behavior architecture is completed; if a problem is found, the process returns to the corresponding level optimization in step S3 to re-verify the consistency between the optimized system's static architecture and dynamic behavior until the system's static architecture and dynamic behavior are consistent.
[0038] In a specific embodiment of the present invention, in step S4, the senior designer creates a new merge branch and sequentially merges the refined models of each subordinate branch into the merge branch. Information on the addition, deletion, and modification of model elements during the merging process is recorded to achieve full traceability of the integration process. Then, a full-process joint simulation is conducted through a custom simulation panel to verify the consistency between the system's static architecture and dynamic behavior, and to display the state transitions, signal interactions, and parameter changes of each system / subsystem in real time. If problems are found, the process returns to the corresponding level for optimization, ensuring the accuracy and traceability of the final design results.
[0039] The method of this invention can be recursively applied to multi-level complex systems at the platform level, system level, and subsystem level. This method is universal and applicable to various multi-level complex systems such as aviation and aerospace.
[0040] In platform-system collaborative design, the platform-level designer acts as the superior, and the system-level designer acts as the subordinate. Steps S2 to S4 are repeated until all subsystem designs are completed. Specifically, as a specific embodiment of the present invention, in step S1, the platform-level designer (superior designer) is configured as a product administrator, granting them full access to view, edit, and manage online projects; each subsystem designer (subordinate designer) is configured as a project member, granting them access to view and edit specified online projects. In step S2, the platform designer defines the overall architecture of the aircraft platform using a module definition diagram. The platform designer creates three package elements, moves the corresponding system modules under these package elements, completes the independent division of design modules, and then submits the overall architecture outline design model to the collaborative server to generate a baseline branch. Based on this baseline branch, three subsystem design branches are then created sequentially, with each subsystem branch inheriting the baseline branch model content. In each branch, the platform designer configures package permissions for the corresponding system designer. In step S3, each subsystem designer conducts detailed behavioral design in their corresponding branch using a state-nested activity approach. Each subsystem designer constructs a state machine diagram and activity diagram, and describes the state transition conditions and activity execution flow in detail through nested state activities. In step S4, the platform designer creates a merge branch based on the baseline branch, and integrates the design content of the three subsystem design branches in sequence through the merge branch. During the merge process, the addition, deletion, and modification information of model elements are recorded to achieve full traceability of the integration process. After the model integration is completed, the platform designer develops a custom UI panel, and verifies the self-consistency and correctness of the aircraft platform's functional logic through joint state and activity simulation.
[0041] In the system-subsystem collaborative design, the system-level designer acts as the superior, and the subsystem-level designers act as the subordinates; steps S2 to S4 are repeated until the design of all subsystems is completed. Specifically, as a specific embodiment of the present invention, in step S1, the system-level designer (superior designer) is configured as a product administrator, giving them full operational permissions to view, edit, and manage online projects; each subsystem designer (subordinate designer) is configured as a project member, giving them permission to view and edit specified online projects. In step S2, the system designer defines the system architecture composition through a module definition diagram, creates three package elements, moves the corresponding subsystem modules under the package elements, completes the independent division of design modules, and then submits the overall architecture outline design model to the collaborative server to generate a baseline branch; then, based on this baseline branch, three subsystem design branches are created sequentially, with each subsystem branch inheriting the content of the baseline branch model. In each branch, the system designer configures package permissions for the corresponding subsystem designer. In step S3, each subsystem designer conducts detailed behavioral design in the corresponding branch using a state nesting activity approach. Each subsystem designer constructs a state machine diagram and activity diagram, and describes the state transition conditions and activity execution flow in detail through state nesting activities. In step S4, the system designer creates a merge branch based on the baseline branch, and integrates the design content of the three subsystem design branches in sequence through the merge branch. During the merge process, the addition, deletion, and modification information of model elements are recorded to achieve full traceability of the integration process. After the model integration is completed, the system designer develops a custom UI panel, and verifies the self-consistency and correctness of the system's functional logic through state and activity co-simulation.
[0042] According to another aspect of the invention, such as Figure 8As shown, a SysML-based collaborative design device for the behavioral architecture of multi-level complex systems is provided. This SysML-based collaborative design device is used to implement the SysML-based collaborative design method for the behavioral architecture of multi-level complex systems described above. The SysML-based collaborative design device for the behavioral architecture of multi-level complex systems includes a permission configuration module, a model distribution module, a behavior design module, and a model integration and verification module. The permission configuration module is used to configure the role permissions of designers at different levels, controlling the viewing and editing scope of design content at each level; it supports fine-grained permission configuration for package elements, allowing separate settings for read / write and read-only permissions. The model distribution module is used for upper-level designers to publish baseline branches and create lower-level branches, providing a unified foundation and permission isolation for parallel refinement design at lower levels; it supports generating a platform-level overall architecture summary design model based on module definition diagrams and internal module diagrams, realizing the inheritance and branching management of model content. The Behavior Design module allows lower-level designers to refine behavior designs within their respective branches, enabling independent modeling and logic verification of each subsystem or subsystem. It supports constructing the behavioral logic of systems / subsystems using activity diagrams and state machine diagrams, providing a modeling method for nested activities within states. The Model Integration and Verification module allows upper-level designers to create and merge branches and integrate lower-level models, verifying the overall functional logic consistency through joint simulation. A built-in simulation engine with a development interface for custom simulation panels can display real-time state transitions, activity flows, and signal interaction data for each system / subsystem. If the simulation fails to meet requirements, problems can be quickly located and reported back to the Behavior Design module.
[0043] Furthermore, in this invention, the permission configuration module configures the superior designer as a product administrator, giving them the permission to view, edit, and manage online projects; and configures the subordinate designer as a project member, giving them the permission to view and edit specified online projects, and supports fine-grained permission configuration for package elements.
[0044] The model integration and verification module has a built-in simulation engine and a development interface for custom simulation panels. It can display the state transitions, activity flows and signal interaction data of each system / subsystem in real time. If the simulation does not meet the requirements, the problem can be quickly located and fed back to the behavior design module.
[0045] Furthermore, in this invention, the SysML-based multi-level complex system behavior architecture collaborative design device is compatible with the SysML language modeling standard.
[0046] The present invention provides a SysML-based collaborative design method and apparatus for multi-level complex system behavioral architecture. Through standardized role and permission control, branched model management and integrated verification process, it realizes efficient collaborative design of multi-level system behavioral architecture, ensures the consistency and traceability of the design process, and significantly improves the efficiency and accuracy of cross-level and cross-professional collaborative design.
[0047] To gain a further understanding of the present invention, the following description is provided in conjunction with... Figures 1 to 8 The present invention provides a detailed description of the SysML-based collaborative design method for the behavioral architecture of multi-level complex systems.
[0048] The following is for reference. Figure 1 Taking the collaborative design of a certain unmanned aerial vehicle platform-system behavioral architecture as an example, this paper describes a SysML-based collaborative design method for the behavioral architecture of a multi-level complex system according to an embodiment of the present invention, including the following steps:
[0049] S1 allows you to configure the role permissions for designers at different levels, controlling the scope of viewing and editing of design content at each level.
[0050] S2 allows senior designers to publish baseline branches and create sub-branches, providing a unified foundation and permission isolation for subordinate designers to refine their designs in parallel.
[0051] S3: Lower-level designers refine the behavioral design in their respective branches, enabling independent modeling and logical verification of each subsystem / subsystem.
[0052] In S4, the senior designer creates and merges branches and integrates the lower-level models, and verifies the consistency of the overall functional logic through joint simulation.
[0053] Specifically, according to an embodiment of the SysML-based collaborative design method for the behavioral architecture of multi-level complex systems, in step S1, the platform-level designer (superior designer) is configured as a product administrator, giving them full operational permissions to view, edit, and manage online projects; the ground station designer, control system designer, and power system designer (subordinate designer) are configured as project member roles, giving them permissions to view and edit specified online projects, as shown in Table 1.
[0054] Table 1. Platform - System Designer Roles and Permissions
[0055] Designer's Name Designer Designer Role Modeling permissions lijun Platform Designer Product Administrator View, edit, and manage online projects zhangsan Ground station designer Project members View and edit online projects zhaowei Control System Designer Project members View and edit online projects hanmei Powertrain Designer Project members View and edit online projects
[0056] Specifically, according to an embodiment of the SysML-based collaborative design method for the behavioral architecture of multi-level complex systems, in step S2, the platform designer defines the overall architectural composition of the aircraft platform through a module definition diagram, such as... Figure 2 As shown, the aircraft platform is decomposed into the aircraft and the ground station. The aircraft is further decomposed into the control system, propulsion system, etc. The port composition and signal interaction relationships between the control system, propulsion system, and ground station are defined through an internal module diagram, such as... Figure 3As shown. The platform designer creates three package elements: "Ground Station Design," "Control System Design," and "Power System Design." The corresponding system modules are moved to these package elements, completing the independent division of design modules. The overall architecture outline design model is then submitted to the collaborative server to generate a baseline version. Based on this baseline version, the Ground Station Design branch, Control System Design branch, and Power System Design branch are created sequentially, with each branch inheriting the baseline version model content. Within each branch, the platform designer configures package permissions for the corresponding system designers: for example, in the Ground Station Design branch, the permissions for the Ground Station Designer on the "Ground Station Design" package element are configured as read-write, while the permissions for the "Control System Design" and "Power System Design" package elements are configured as read-only. The Control System and Power System branches are handled similarly. Figure 4 As shown. This achieves access control isolation, ensuring that each system designer can only modify the parts they are responsible for.
[0057] Specifically, according to an embodiment of the SysML-based collaborative design method for the behavioral architecture of multi-level complex systems, in step S3, each system designer conducts detailed behavioral design in the corresponding branch using a state-nested activity approach. Each system designer constructs a state machine diagram and an activity diagram, and describes in detail the state transition conditions and activity execution flow through the state-nested activity approach, such as... Figure 5 As shown. During the ground preparation phase, after the external command center issues mission instructions, the ground station transitions from standby to takeoff control mode, sending an engine start signal to the propulsion system. The propulsion system then transitions from shutdown to operation mode and sends a power-on signal to the control system, which in turn transitions from shutdown to standby mode. After the external command center issues flight preparation instructions, the ground station sends a flight preparation signal to the control system, which then transitions to flight preparation mode and sends self-check results back to the ground station. During the takeoff and climb phase, after the external input and confirmation of the target position, the ground station sends a target position signal to the control system, which completes navigation data loading and sends it back. After the external command center issues a sortie command, the control system transitions to takeoff control mode, and the aircraft enters the runway. After the takeoff command is issued, the control system transitions to climb control mode, and the aircraft begins its climb. Upon reaching cruising altitude, the control system transitions to cruise control mode. During the cruise and mission execution phases, the aircraft approaches the target at cruising speed and performs relevant tasks upon reaching the vicinity of the target position. After the mission is completed, the control system sends a power-off signal to the propulsion system, which then transitions to shutdown mode, and the control system simultaneously transitions to shutdown mode.
[0058] Specifically, according to an embodiment of the SysML-based collaborative design method for the behavioral architecture of multi-level complex systems, in step S4, the platform designer creates a merge branch based on the baseline version. Through the merge branch, the design content from the ground station design branch, control system design branch, and power system design branch is integrated sequentially. During the merging process, the addition, deletion, and modification information of model elements are recorded to achieve full traceability of the integration process. Figure 6 As shown. After the model integration is completed, the platform designers develop a custom UI panel to verify the consistency and correctness of the aircraft platform's functional logic through joint simulation of states and activities, such as... Figure 7 As shown, the simulation verification covers the entire process from ground preparation, takeoff and climb, cruise, and mission execution, displaying the state transitions, signal interactions, and parameter changes of each system in real time. The simulation results show that the behavioral logic of each system of the unmanned aerial vehicle platform is completely consistent with the mission flow scenario, and the static architecture and dynamic behavior are highly consistent, indicating that the verification has passed.
[0059] The above embodiments are only used as an example of platform-system level design. This method is also applicable to system-subsystem level design: the system-level designer acts as the superior, creating branches, configuring permissions, and distributing models for each subsystem according to the above process. Subsystem-level designers refine the design in their respective branches, and finally, the system-level designer integrates and verifies the design. This process can be recursively nested and is suitable for complex systems with any number of levels.
[0060] Therefore, compared with traditional technologies, the SysML-based collaborative design method for the behavioral architecture of multi-level complex systems according to the present invention standardizes the design process of complex systems by introducing a collaborative mechanism of branch management and access control, realizes efficient collaboration of multi-level design, and ensures the consistency and traceability of design results with design requirements.
[0061] This invention also provides a SysML-based collaborative design device for the behavioral architecture of multi-level complex systems. This device employs the aforementioned design method and includes a permission configuration module 801, a model distribution module 802, a behavior design module 803, and a model integration and verification module 804, as follows: Figure 8 As shown.
[0062] The permission configuration module 801 is used to configure the role permissions of platform-level, system-level, and subsystem-level designers to control the viewing and editing scope of design content at different levels. The model distribution module 802 is used for platform-level designers to use task flows or scenarios as design inputs, define system architecture components and port connection relationships, publish baseline branches, and create sub-branches based on the baseline branches, granting editing permissions for each sub-branch to the corresponding system-level designers. The behavior design module 803 is used for each system-level designer to perform detailed behavior design for the system they are responsible for in the corresponding sub-branches. The model integration and verification module 804 is used for platform-level designers to create merge branches, sequentially merge the detailed models from each sub-branch into the merge branch, and perform simulation verification on the integrated model.
[0063] In summary, this invention provides a SysML-based collaborative design method and apparatus for the behavioral architecture of multi-level complex systems. Through standardized role and permission control, branched model management, and integrated verification processes, it achieves efficient collaborative design of multi-level system behavioral architecture, ensures the consistency and traceability of the design process, and significantly improves the efficiency and accuracy of cross-level and cross-professional collaborative design.
[0064] For ease of description, spatial relative terms such as "above," "on top of," "on the upper surface of," "above," etc., are used herein to describe the spatial positional relationship of a device or feature as shown in the figures to other devices or features. It should be understood that spatial relative terms are intended to encompass different orientations in use or operation beyond the orientation of the device as described in the figures. For example, if the device in the figures were inverted, a device described as "above" or "on top of" other devices or structures would subsequently be positioned as "below" or "under" other devices or structures. Thus, the exemplary term "above" can include both "above" and "below." The device may also be positioned in other different ways (rotated 90 degrees or in other orientations), and the spatial relative descriptions used herein will be interpreted accordingly.
[0065] Furthermore, it should be noted that the use of terms such as "first" and "second" to define components is merely for the purpose of distinguishing the corresponding components. Unless otherwise stated, the above terms have no special meaning and therefore should not be construed as limiting the scope of protection of this invention.
[0066] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.
Claims
1. A collaborative design method for the behavioral architecture of a multi-level complex system based on SysML, characterized in that, This multi-level complex system behavior architecture collaborative design method is applicable to scenarios involving platform-level, system-level, and subsystem-level complex system behavior architecture collaborative design. The method includes: S1 allows you to configure the role permissions for designers at different levels, controlling the scope of viewing and editing of design content at each level. S2: Senior designers publish baseline branches and create sub-branches, providing a unified foundation and permission isolation for parallel refinement of designs by lower-level designers; S3, where lower-level designers refine behavioral design in their respective branches, enabling independent modeling and logical verification of each subsystem or subsystem; S4, the senior designer creates and merges branches and integrates the models of each subsystem or sub-system in step S3, verifies the consistency of the overall functional logic through joint simulation, and completes the collaborative design of the behavioral architecture of a multi-level complex system.
2. The SysML-based collaborative design method for the behavioral architecture of multi-level complex systems according to claim 1, characterized in that, In step S1, configuring the role permissions of designers at different levels further includes: configuring the senior designer as a product administrator, giving them the permission to view, edit, and manage online projects; configuring the junior designer as a project member, giving them the permission to view and edit specified online projects; and through fine-grained permission configuration of package elements, granting the junior designer read and write permissions for the corresponding design modules, while granting read-only permissions for other modules.
3. The SysML-based collaborative design method for the behavioral architecture of multi-level complex systems according to claim 1, characterized in that, In step S2, the senior designer takes the task flow or scenario as design input, defines the system's composition architecture through the module definition diagram, defines the port and signal interaction relationships between the components through the internal module diagram, generates a baseline branch, and then creates each subordinate branch based on the baseline branch.
4. The SysML-based collaborative design method for the behavioral architecture of multi-level complex systems according to claim 1, characterized in that, In step S3, the detailed behavior design includes: lower-level designers analyze the activity flow of their respective systems through activity diagrams, design the state transitions of each system in detail through state machine diagrams, and clarify the state classification, corresponding activity behaviors, and state transition triggering conditions.
5. The SysML-based collaborative design method for the behavioral architecture of multi-level complex systems according to claim 1, characterized in that, In step S4, the senior designer creates a merge branch and merges the refined models from each subordinate branch into the merge branch in sequence, recording the model element change information during the merging process. Then, co-simulation is carried out through a custom simulation panel to verify the consistency between the static architecture and dynamic behavior of the system. If the static architecture and dynamic behavior of the system are consistent, the co-design of the behavioral architecture of the multi-level complex system is completed. If a problem is found, return to the corresponding level of optimization in step S3, and re-verify the consistency between the static architecture and dynamic behavior of the optimized system until the static architecture and dynamic behavior of the system are consistent.
6. The SysML-based collaborative design method for the behavioral architecture of multi-level complex systems according to any one of claims 1 to 5, characterized in that, The method can be recursively applied to complex multi-level systems at the platform, system, and subsystem levels: In platform-system collaborative design, the platform-level designer acts as the superior and the system-level designer acts as the subordinate; steps S2 to S4 are repeated until all subsystem designs are completed; In system-subsystem collaborative design, the system-level designer acts as the superior and the subsystem-level designer acts as the subordinate; steps S2 to S4 are repeated until all subsystem designs are completed.
7. A SysML-based collaborative design device for the behavioral architecture of multi-level complex systems, characterized in that, The SysML-based multi-level complex system behavioral architecture collaborative design device is used to implement the SysML-based multi-level complex system behavioral architecture collaborative design method as described in claims 1 to 6. The SysML-based multi-level complex system behavioral architecture collaborative design device includes: The permission configuration module is used to configure the role permissions of designers at different levels, and control the scope of viewing and editing of design content at each level; The model distribution module is used by senior designers to publish baseline branches and create sub-branches, providing a unified foundation and permission isolation for parallel refinement design at the lower level. The behavior design module is used to allow junior designers to refine behavior design in their respective branches, enabling independent modeling and logical verification of each subsystem or subsystem. The model integration and verification module is used by senior designers to create merged branches and integrate lower-level models, and verify the consistency of the overall functional logic through joint simulation.
8. The SysML-based multi-level complex system behavioral architecture collaborative design device according to claim 7, characterized in that, The permission configuration module configures senior designers as product administrators, granting them the authority to view, edit, and manage online projects; and configures junior designers as project members, granting them the authority to view and edit specified online projects. It also supports fine-grained permission configuration for package elements.
9. The SysML-based multi-level complex system behavioral architecture collaborative design device according to claim 7, characterized in that, The model integration and verification module has a built-in simulation engine and a development interface for custom simulation panels. It can display the state transitions, activity processes, and signal interaction data of each system / subsystem in real time. If the simulation does not meet the requirements, the problem can be quickly located and fed back to the behavior design module.
10. The SysML-based multi-level complex system behavioral architecture collaborative design device according to any one of claims 7 to 9, characterized in that, The device is compatible with the SysML language modeling standard.
