SysML-based system digital modeling technology and method
Patent Information
- Application Number
- CN202511643636.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-11
- Publication Date
- 2026-10-27
AI Technical Summary
[0004]针对上述情况,本发明提出一种基于SysML的体系数字化建模技术与方法,构建统一的体系数字化建模框架,提升数字化结构建模的表达能力、扩展能力与分析能力,解决当前建模方式缺乏结构性、系统性、动态适应性的问题
[0018]1、本发明在体系数字化建模中引入系统工程领域的标准化建模语言SysML,整合多类视图工具开展建模工作,这种方式有效实现了体系结构、行为、需求等核心要素的一体化表达,成功解决建模中多要素分散描述、关联逻辑薄弱的问题,使模型能够更系统地呈现体系各维度间的内在联系,同时适配体系规划、活动建模、体系发展推演等多个场景。
Smart Images

Figure CN122987274A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of digital modeling, and more particularly to a system digital modeling technology and method based on SysML. Background Technology
[0002] With the continuous deepening of digital construction, the requirements for the systematicness and accuracy of system modeling in various complex application scenarios are constantly increasing, and digital modeling technology is also gradually developing through practical exploration. Early modeling and analysis mostly relied on structured documents, Excel spreadsheets, or customized software tools, which met basic modeling needs at specific stages. Later, with the increasingly widespread application of systems engineering methods in the engineering field, SysML, as a general-purpose modeling language for systems engineering, began to be initially promoted in product development, system integration, and other fields due to its comprehensive advantages in structural modeling, behavioral modeling, requirement traceability, and parameter constraints. However, in the specific field of system digital modeling, the application of SysML has not yet formed a complete systematic methodology. How to utilize it to build a unified modeling framework between structural units, system capability modules, task links, and resource allocation is still in its early stages of technological exploration, and a mature general technical path has not yet been established.
[0003] Existing modeling techniques still have many significant limitations in practical applications. Traditional modeling methods generally suffer from coarse modeling granularity and vague structural hierarchy division. Model elements lack effective reuse mechanisms, and the behavioral logic of different modules is difficult to organically link, making it difficult to meet the needs of modern composite application models for systematic analysis of system composition, task flow, and resource allocation. At the same time, existing system modeling methods lack unified semantic model support and mature visualization modeling tools, making it difficult to effectively carry out cross-level collaborative definition and structural logic verification, which greatly limits the in-depth advancement of model-driven system planning, deduction, and verification analysis. Even some published related patent technologies, such as patent CN103593516B, although proposing a system architecture model construction method based on the DoDAF specification, do not combine the standardized architecture of SysML and fail to form an integrated modeling framework covering structure, behavior, resources, and requirements. Similarly, they are difficult to adapt to the characteristics of rapid system evolution, complex coupling, and joint applications, ultimately resulting in significant constraints on the efficiency, accuracy, and reusability of modeling work. Summary of the Invention
[0004] To address the above issues, this invention proposes a SysML-based system digital modeling technology and method, constructing a unified system digital modeling framework to enhance the expressive, extensible, and analytical capabilities of digital structural modeling, thus solving the problems of current modeling methods lacking structure, systematicity, and dynamic adaptability.
[0005] The technical solution adopted in this invention is as follows:
[0006] The system digital modeling technology and method based on SysML includes the following steps:
[0007] Step S1: Establish a digital system decomposition structure model, construct a multi-level composition structure of force units based on SysML's Block Definition Diagram, and form a complete system architecture tree;
[0008] Step S2: Construct a behavioral model, using Activity Diagram to describe the work execution process, command and control links, and work collaboration relationships of each unit;
[0009] Step S3: Define the system mission and requirements model. Based on the Requirement Diagram, define the task requirements, constraints, and verification indicators, and support the traceability link between the requirement item structure and behavior model.
[0010] Step S4: Establish a system capability configuration and resource relationship model, and use Parametric Diagram to construct resource configuration parameters and constraint relationships;
[0011] Step S5 involves model integration and analysis of the system modeling to form a unified model structure view and behavior analysis map.
[0012] Furthermore, in step S1, the system decomposition structure model supports user-defined system templates. Each Block structure unit within the system template can inherit a set of common attributes and allows for the extension of specific attributes to adapt to different organizational units or application scenarios.
[0013] Furthermore, in step S2, the behavior model supports multi-task flow modeling, and uses parallel structure, selection structure and branch structure to abstractly model the job process, satisfying the logical description of the behavior of multiple independent units in complex collaborative tasks.
[0014] Furthermore, in step S3, the requirement model building process supports hierarchical inheritance of requirement items, functional decomposition and verification path configuration. Each requirement is bound to a specific independent structural unit or task node, and the relationship between the requirement and the structural model (satisfy) and the behavioral model (verify) is automatically established.
[0015] Furthermore, in step S4, during the establishment of the resource relationship model, each type of resource is defined as a Block node and expressed in a formulaic way through Constraint Block.
[0016] Furthermore, in step S5, model integration defines multiple perspectives through the Model View mechanism and performs consistency checks and coverage analysis based on model validation tools.
[0017] Compared with the prior art, the significant advantages of this invention are:
[0018] 1. This invention introduces SysML, a standardized modeling language in the field of systems engineering, into the digital modeling of the system. It integrates multiple types of view tools to carry out modeling work. This approach effectively realizes the integrated expression of core elements such as system architecture, behavior, and requirements, and successfully solves the problems of scattered description of multiple elements and weak correlation logic in modeling. This enables the model to present the internal connections between various dimensions of the system more systematically, while adapting to multiple scenarios such as system planning, activity modeling, and system development simulation.
[0019] 2. This invention builds a complete architecture tree based on SysML's BDD, while also supporting user-defined architecture templates. This allows each Block structure unit within the template to inherit a set of common attributes and extend specific attributes according to different organizational units or application scenarios. This enables multi-level and multi-dimensional architecture unit modeling, meeting the full-process structure definition requirements from top-level system planning to specific implementation. It effectively breaks through the limitation of traditional modeling, which can only cover a single level, and improves the model's adaptability to different scenarios.
[0020] 3. When constructing the system mission and requirement model, this invention supports hierarchical inheritance of requirement items, functional decomposition, and verification path configuration. It binds each requirement to a specific independent structural unit node and automatically establishes a "satisfy" relationship between the requirement and the structural model, and a "verify" relationship with the behavioral model. This enables bidirectional traceability between requirements and structural / behavioral models, significantly improves the logical consistency and verifiability of the model, reduces errors caused by manual correlation operations, and further ensures the quality of modeling and the accuracy of system planning and verification work.
[0021] 4. This invention forms a reusable component library by classifying and organizing the Block structure. In model applications, it supports configuration-based reuse and variable-driven automatic reconfiguration. At the same time, it allows Block structure units to extend specific attributes according to specific scenarios. This gives the model good scalability and reusability, supports rapid modeling and multi-scenario reuse under different task backgrounds, reduces the time and manpower costs of repeated modeling, reduces the cost of model building and maintenance, and improves the response efficiency to rapidly changing requirements.
[0022] 5. This invention utilizes SysML's Parametric Diagram to construct resource configuration parameters and constraint relationships to achieve parameterized simulation of resources. During the model integration phase, a unified model structure view and behavioral analysis map are formed. Consistency verification and coverage analysis are performed using model validation tools. This method can serve as the model foundation layer for system development deduction and system evaluation analysis platforms, providing solid model support for benefit evaluation analysis, system development deduction and optimization design, and effectively improving the standardization level of modeling in information engineering. Attached Figure Description
[0023] The accompanying drawings, which form part of this application, are used to provide a further understanding of the application and to make other features, objects, and advantages of the application more apparent. The illustrative embodiments and descriptions of this application are used to explain the application and do not constitute an undue limitation of the application.
[0024] In the attached diagram:
[0025] Figure 1 This is a flowchart of the system digital modeling technology and method based on SysML in this embodiment.
[0026] Figure 2 This is a schematic diagram illustrating the principle of the system digital modeling technology and method based on SysML in this embodiment. Detailed Implementation
[0027] The detailed description of the following embodiments is used to illustrate the principles of this application, but should not be used to limit the scope of this application. That is, the system digital modeling technology and method based on SysML in this application are not limited to the described embodiments.
[0028] Example 1
[0029] like Figure 1-2 As shown, the system digital modeling technology and method based on SysML specifically includes the following steps:
[0030] Step S1: Establish a digital system decomposition structure model. Based on SysML's Block Definition Diagram, construct a multi-level composition structure of force units to form a complete system architecture tree. The system decomposition structure model supports user-defined system templates. Each Block structure unit within the system template can inherit a set of common attributes and allows the extension of specific attributes to adapt to different organizational units or application scenarios.
[0031] The detailed processing steps are as follows:
[0032] Step S11: Load the knowledge base and form a Block template based on the complex product dependencies and the architectural structure pattern;
[0033] Step S12: Build the system architecture tree. The tree-like hierarchical structure is built from top to bottom. Starting from the top-level planning, the application scenarios, mission tasks, behavioral activities, and constituent items are defined level by level. Each Block node has a unique identifier.
[0034] Step S13: Define node types and attribute sets, set Block categories according to functions, task domains, etc., and each type of Block inherits the common attribute set and supports extended attribute definitions;
[0035] Step S14: Establish component structure relationships, use the "part" relationship to construct the structural relationships between each block, and form a complete system composition structure;
[0036] Step S15: Establish a Package organization structure, classify and place various Block structures into Packages to form a reusable component library, providing support for rapid modeling under different task backgrounds.
[0037] Further, in step S2, a behavioral model is constructed. The Activity Diagram is used to describe the job execution process, command and control link, and job collaboration relationship of each unit. The behavioral model supports multi-task flow modeling and uses parallel structure, selection structure and branch structure to abstractly model the job process, satisfying the logical description of the behavior of multiple independent units in complex collaborative tasks.
[0038] The detailed processing steps are as follows:
[0039] Step S21: Define typical task flow: Define the start, execution, transfer, and termination nodes of each stage of the task based on the job flow diagram;
[0040] Step S22: Construct action nodes, modeling each key action as an action node;
[0041] Step S23: Construct control flow and data flow, using arrows to connect each behavior node to indicate the task execution order and conditional logic; for nodes involving input and output data, add Object Flow to indicate data transfer;
[0042] Step S24: Define the association between behavior and structure. Each behavior node is bound to one or more Block structural units as executors to ensure the consistency between the behavior model and the structure model.
[0043] Further, in step S3, define the system mission and requirements model. Based on the Requirement Diagram, define task requirements, constraints, and verification indicators. Support the traceability link between the requirement item structure and behavior model. The requirement model establishment process supports hierarchical inheritance, functional decomposition, and verification path configuration of requirement items. Each requirement is bound to a specific independent structural unit or task node. Support the automatic establishment of satisfaction with the structural model and verification with the behavior model.
[0044] The detailed processing steps are as follows:
[0045] Step S31: Establish a requirement hierarchy structure, define three categories of requirements: “task requirements”, “performance indicators”, and “capability requirements”, and decompose them step by step to form a requirement tree structure.
[0046] Step S32: Define requirement attributes, defining fields such as number, name, description, verification criteria, source (e.g., superior order, regulation), priority, and status for each requirement;
[0047] Step S33: Establish requirement traceability relationships. Use the "satisfy" relationship to bind the Block in the structural model to the requirement item it needs to satisfy; use the "verify" relationship to associate the behavioral model or test node with the requirement item it needs to verify.
[0048] Step S34: Output requirement verification view: Automatically generate a tracing chain diagram between requirements, structure and behavior based on the above configuration, which will facilitate subsequent verification and analysis.
[0049] Further, in step S4, a system capability configuration and resource relationship model is established. Parametric Diagram is used to construct resource configuration parameters and constraint relationships for system units, personnel, materials, and spare parts. In the establishment of the resource relationship model, each type of resource is defined as a Block node and expressed in a formula through Constraint Block.
[0050] The detailed processing steps are as follows:
[0051] Step S41: Define resource blocks: Model each type of resource as an independent block unit. Each block has parameter attributes such as quantity, consumption rate, and battery life.
[0052] Step S42: Establish constraint expressions: Use Constraint Blocks to construct mathematical expression relationships, such as resource consumption = job duration × unit resource consumption rate;
[0053] Step S43: Bind structural nodes: Bind the Constraint Block to the Block property through the Binding Connector to configure the data transmission path;
[0054] Step S44: Support parameterized simulation of dynamic resource allocation: Input variables such as task duration to automatically calculate resource demand thresholds and provide input for decision support.
[0055] Further, in step S5, model integration and analysis are performed on the system model to form a unified model structure view and behavior analysis map. Model integration defines multiple perspectives through the Model View mechanism and performs consistency verification and coverage analysis based on model verification tools.
[0056] The detailed processing steps are as follows:
[0057] Step S51: Construct the model view system and create multiple Views and Viewpoints, such as the structure view, requirement view, task view, resource view, benefit evaluation perspective, etc.
[0058] Step S52: Perform model consistency verification by calling the model verification engine in SysML tools (such as MagicDraw) to check for issues such as attribute consistency, dependency cycles, and unconnected nodes.
[0059] Step S53: Output the model cross-tracing matrix and derive the mapping relationship table between requirements and structure, behavior and resources to achieve verification traceability and responsibility alignment;
[0060] Step S54: Support model reuse and dynamic updates. The structure and task models support configuration-based reuse, and the requirement and resource models support variable-driven automatic reconfiguration to meet the needs of rapid modeling and version iteration.
[0061] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus.
[0062] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention.
[0063] The present invention and its embodiments have been described above. This description is not restrictive, and the accompanying drawings are only one embodiment of the present invention; the actual structure is not limited thereto. In conclusion, if those skilled in the art are inspired by this description and design similar structures and embodiments without departing from the spirit of the invention, such designs should fall within the protection scope of the present invention.
Claims
1. A system digital modeling technology and method based on SysML, characterized in that, Includes the following steps: Step S1: Establish a digital system decomposition structure model, construct a multi-level composition structure of force units based on SysML's Block Definition Diagram, and form a complete system architecture tree; Step S2: Construct a behavioral model, using Activity Diagram to describe the work execution process, command and control links, and work collaboration relationships of each unit; Step S3: Define the system mission and requirements model. Based on the Requirement Diagram, define the task requirements, constraints, and verification indicators, and support the traceability link between the requirement item structure and behavior model. Step S4: Establish a system capability configuration and resource relationship model, and use Parametric Diagram to construct resource configuration parameters and constraint relationships; Step S5 involves model integration and analysis of the system modeling to form a unified model structure view and behavior analysis map.
2. The system digital modeling technology and method based on SysML according to claim 1, characterized in that, In step S1, the system decomposition structure model supports user-defined system templates. Each Block structure unit within the system template can inherit a set of general attributes and allows for the extension of specific attributes to adapt to different organizational units or application scenarios.
3. The system digital modeling technology and method based on SysML according to claim 2, characterized in that, In step S2, the behavior model supports multi-task flow modeling, and uses parallel structure, selection structure and branch structure to abstractly model the job process, satisfying the logical description of the behavior of multiple independent units in complex collaborative tasks.
4. The system digital modeling technology and method based on SysML according to claim 3, characterized in that, In step S3, the requirement model establishment process supports hierarchical inheritance of requirement items, functional decomposition and verification path configuration. Each requirement is bound to a specific independent structural unit or task node, and the relationship between the requirement and the structural model (satisfy) and the behavioral model (verify) is automatically established.
5. The system digital modeling technology and method based on SysML according to claim 4, characterized in that, In step S4, during the establishment of the resource relationship model, each type of resource is defined as a Block node and expressed in a formulaic way through ConstraintBlock.
6. The system digital modeling technology and method based on SysML according to claim 5, characterized in that, In step S5, the model integration defines multiple perspectives through the Model View mechanism and performs consistency verification and coverage analysis based on the model verification tool.