SysML v2-oriented model enhancement and bidirectional conversion method and system

Abstract

The invention discloses a SysML v2-oriented model enhancement and bidirectional conversion method and system.The method comprises the steps that a source SysML v2 model is received and analyzed to establish source model resources, and the source SysML v2 model is SysML v2 text representation or an EMF instance model corresponding to the SysML v2 text representation; mapping model elements in the source model resources into intermediate model elements based on a preset SysMININE meta-model, and generating an intermediate model; performing enhancement processing on the intermediate model; and outputting the enhanced intermediate model as a SysMMine model in an EMF format, and converting the SysMMine model in the EMF format into SysML v2 text representation through a reverse mapping mechanism. By means of the scheme, semantic abstraction and logic isolation of SysML v2 can be achieved, follow-up processing is independent of a specific source format, and the model management capacity and interoperability are improved.

Description

Technical Field

[0001] This application generally relates to the technical field of model transformation, management, and optimization of system modeling languages. More specifically, this application relates to a method and system for model enhancement and bidirectional transformation for SysML v2. Background Art

[0002] With the increasing complexity of systems, model-based systems engineering (MBSE) has become the core method for realizing the full-life cycle management of systems. As a key support for MBSE, the system modeling language SysML v2 has significantly improved the modeling ability of complex systems by enhancing language precision, expressiveness, and interoperability. However, the existing technologies still have the following limitations in practical applications: First, the semantic integrity of the EMF model is insufficient: When current SysML v2 tools are converted into EMF models, only explicit modeling elements (such as attributes and connections) are retained, while derived information (such as inherited deduced attributes and dependency transitivity) is ignored. This results in a lack of a complete semantic context during model verification and analysis, limiting the ability of automated reasoning and cross-tool collaboration. For example, in system architecture verification, implicit dependency relationships cannot be directly obtained from the EMF model, and manual logic needs to be supplemented, increasing the risk of errors and iterative costs.

[0003] Second, there are defects in model structure complexity and understandability: The EMF implementation of SysML v2 directly maps the language specification, resulting in a deep model hierarchy and redundant reference relationships (such as multi-level nested type definitions). Developers need to deeply understand the underlying metamodel structure when analyzing the model, with a high learning cost and prone to errors. For example, verification engineers need to traverse complex reference paths to locate specific state machine behaviors, reducing the efficiency of model review.

[0004] Third, the model management mechanism is lacking: Existing technologies lack systematic management support for SysML v2 models, including functions such as version control, modular reuse, and relationship tracking. For example, in the digital twin scenario, model elements cannot be updated and rolled back as needed, resulting in difficulties in multi-version model collaboration; in large-team collaboration, there is a lack of a unified interface to manage model changes, which is prone to consistency conflicts.

[0005] Fourth, there are limitations in the toolchain functions: Existing tools (such as SysON and SysIDE) focus on model editing and visualization but do not integrate the core functions of model management. For example, although SysIDE supports efficient editing of text syntax, it lacks the ability to globally retrieve and analyze dependencies of model elements; the graphical editing of SysON does not provide a model version comparison or incremental update mechanism, making it difficult to support engineering collaboration requirements.

[0006] In view of this, there is an urgent need to provide a model enhancement and bidirectional conversion solution for SysML v2, which improves the practicability and scalability of model-driven engineering by integrating semantic enhancement, structural optimization, and full life cycle management. Summary of the Invention

[0007] To solve at least one or more of the above-mentioned technical problems, the present application proposes a model enhancement and bidirectional conversion solution for SysML v2 in multiple aspects.

[0008] In a first aspect, the present application provides a model enhancement and bidirectional conversion method for SysML v2, including: receiving and parsing a source SysML v2 model to establish source model resources, where the source SysML v2 model is a SysML v2 text representation or its corresponding EMF instance model; applying a rule script to map model elements in the source model resources to intermediate model elements based on a preset SysMLine meta-model to generate an intermediate model; performing enhancement processing on the intermediate model; outputting the enhanced intermediate model as a SysMLine model in EMF format, and converting the SysMLine model in EMF format into a SysML v2 text representation through a reverse mapping mechanism.

[0009] In some embodiments, when receiving a SysML v2 text representation, a SysML v2 original model is constructed through the SysML v2 text representation, and the SysML v2 original model is converted into an EMF instance model through a SysML v2 Pilot tool or a syntax tree generation tool.

[0010] In some embodiments, after converting the SysML v2 original model into an EMF instance model, an enhanced conversion mechanism is introduced into the SysMLine framework to complement the missing semantic information in the converted EMF instance model.

[0011] In some embodiments, the missing semantic information includes the semantic subset relationship that an attribute should have.

[0012] In some embodiments, the rule script is SysML2SysMLine.etl.

[0013] In some embodiments, during the process of performing enhancement processing on the intermediate model, at least one of the following steps is executed: complementing the missing derived semantic information in the intermediate model through static analysis and rule derivation; automatically generating attribute identification and value range information of the intermediate model through an EOL script; simplifying and reconstructing the structure of the intermediate model.

[0014] In some embodiments, after enhancing the intermediate model, one of the following steps is performed on the enhanced intermediate model: automatically modifying the structure or content of the enhanced intermediate model through an EOL script; performing a naming convention check and a structural consistency check on the enhanced intermediate model through an EVL verification engine.

[0015] In some embodiments, the derived semantic information includes isDerived information, direction information, and multiplicityRange information.

[0016] In some embodiments, simplifying and reconstructing the structure of the intermediate model includes eliminating intermediate levels and merging redundant links.

[0017] In a second aspect, the present application provides a set of model enhancement and bidirectional conversion systems for SysML v2, which implements model enhancement and bidirectional conversion for SysML v2 by using the model enhancement and bidirectional conversion method for SysML v2 described in any embodiment of the first aspect. The system includes: a model import module for receiving and parsing a source SysML v2 model to establish source model resources, where the source SysML v2 model is a SysML v2 text representation or its corresponding EMF instance model; a model conversion module for applying a rule script to map model elements in the source model resources to intermediate model elements based on a preset SysMLine meta-model to generate an intermediate model; a model enhancement module for enhancing the intermediate model; and a model export module for outputting the enhanced intermediate model as a SysMLine model in EMF format and converting the SysMLine model in EMF format to a SysML v2 text representation through a reverse mapping mechanism.

[0018] Through the model enhancement and bidirectional conversion solution for SysML v2 provided above, embodiments of the present application support two input formats, namely SysML v2 text representation and EMF instance model, to ensure that the toolchain can adapt to different development environments and meet diverse user needs. By mapping the source model to an intermediate model based on a preset SysMLine meta-model through a rule script, semantic abstraction and logical isolation of SysML v2 are achieved, enabling subsequent processing to be independent of the specific source format and enhancing model management capabilities and interoperability. By enhancing the intermediate model, domain-specific optimizations can be injected to improve the analyzability and reuse value of the model. By using the reverse mapping mechanism to write back the enhanced processing result as a SysML v2 text representation, a bidirectional mapping mechanism between the original SysML v2 model and the SysMLine model is achieved, supporting forward import and reverse transmission of the model, and enhancing the ecological compatibility and engineering usability of the SysML v2 model.

[0019] Further, in some embodiments, when receiving the SysML v2 text representation, a SysML v2 original model is constructed through the SysML v2 text representation, and the SysML v2 original model is converted into an EMF instance model through the SysML v2 Pilot tool or the syntax tree generation tool, and an enhanced conversion mechanism is introduced in the SysMLine framework to complement the missing semantic information in the converted EMF instance model. This not only maintains the semantic consistency of the SysML v2 original model, but also lays a structurally complete model foundation for subsequent analysis, verification, export, etc. operations while ensuring standard compatibility.

[0020] Even further, in some embodiments, during the process of enhancing the intermediate model, by complementing the missing derived semantic information in the intermediate model, the implicit or not explicitly defined intermediate model semantics can be automatically deduced through logical rules, and the logical break caused by the source model format difference or information loss can be repaired. By automatically generating the attribute identification and value range information of the intermediate model, the metadata of the intermediate model elements can be dynamically extended, and the attribute definitions can be standardized to adapt to the corresponding data format requirements. By simplifying and reconstructing the structure of the intermediate model, the model hierarchical relationship can be optimized, irrelevant details or intermediate state data can be eliminated, and the core logical expression can be focused on, accelerating the subsequent conversion and verification processes.

[0021] Still further, in some embodiments, after enhancing the intermediate model, by automatically modifying the structure or content of the enhanced intermediate model, it is possible to support the dynamic adjustment of the model structure based on preset rules and improve the model logical clarity. By performing naming convention verification and structural consistency check on the enhanced intermediate model, the model readability can be ensured, and reverse quality feedback can be provided to form a continuous optimization mechanism. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] By reading the following detailed description with reference to the accompanying drawings, the above and other objects, features, and advantages of the exemplary embodiments of the present application will become readily understood. In the drawings, several embodiments of the present application are shown in an exemplary and non-limiting manner, and the same or corresponding reference numerals represent the same or corresponding parts, wherein: Figure 1 shows an exemplary flowchart of the model enhancement and bidirectional conversion method for SysML v2 according to an embodiment of the present application; Figure 2 shows an exemplary structural block diagram of the model enhancement and bidirectional conversion system for SysML v2 according to an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0023] The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are some, but not all, of the embodiments of the present application. All other embodiments obtained by those skilled in the art based on the embodiments of the present application without creative efforts fall within the protection scope of the present application.

[0024] It should be understood that the terms "including" and "comprising" used in the specification and claims of the present application indicate the presence of the described features, wholes, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or their combinations.

[0025] It should also be understood that the terms used in the specification of the present application are only for the purpose of describing specific embodiments and are not intended to limit the present application. As used in the specification and claims of the present application, unless the context clearly indicates otherwise, the singular forms "a", "an", and "the" are intended to include the plural forms. It should be further understood that the term "and / or" used in the specification and claims of the present application refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0026] Figure 1 An exemplary flowchart of the model enhancement and bidirectional conversion method 100 for SysML v2 according to the embodiments of the present application is shown.

[0027] As Figure 1 shown, in step S110, the source SysML v2 model is received and parsed to establish the source model resources.

[0028] Specifically, the source SysML v2 model is the SysML v2 text representation or its corresponding EMF instance model.

[0029] In the embodiments of the present application, when the SysML v2 text representation is received, the SysML v2 original model is constructed through the SysML v2 text representation, and the SysML v2 original model is converted into an EMF instance model through the SysML v2 Pilot tool or the syntax tree generation tool.

[0030] In the embodiments of the present application, in the process of constructing the SysML v2 original model through SysML v2 text representation, first, define the model organizational structure (such as creating packages) and declare the core model elements (such as defining blocks and defining requirements). Second, establish the relationships between model elements (such as inheritance relationships, composition relationships, association relationships, etc.). Then, add constraints and rules to declare the restrictive conditions for model elements. Finally, introduce other model files through import, and use a SysML v2 compatible tool (such as the SysML v2 API at HYPERLINK "https: / / sysml.org") to check for text syntax errors and ensure logical consistency (such as no cycles in inheritance relationships, reasonable constraint conditions, etc.) to obtain the SysML v2 original model.

[0031] Specifically, when converting the SysML v2 original model to an EMF instance model through the SysML v2 Pilot tool, it is converted to an EMF instance model through the SysML2XMI function provided by the SysML v2 Pilot tool. Since XMI (XML Metadata Interchange) is an OMG-standard data exchange format, the XMI file generated by SysML2XMI realizes the standardized mapping of the SysML v2 model to the EMF instance model, ensuring that the model can be seamlessly exchanged between different tools (such as modeling tools in the Eclipse ecosystem).

[0032] In the embodiments of the present application, after converting the SysML v2 original model to an EMF instance model, an enhanced conversion mechanism is introduced in the SysMLine framework to complement the missing semantic information in the converted EMF instance model.

[0033] In the embodiments of the present application, the aforementioned missing semantic information includes the proper semantic subset relationship of attributes.

[0034] In some embodiments of the present application, when converting the SysML v2 original model to an EMF instance model, for the attribute "mass" in PartDefinition Vehicle, the information about its proper semantic subset relationship (Subsetting) is lost and it is only mapped to an isolated AttributeUsage entity. To solve this problem, an enhanced conversion mechanism is introduced in the SysMLine framework to complement the missing semantic information without modifying the original EMF instance model. For example, the Subsetting of the attribute "mass" is explicitly complemented to "ISQBase::mass".

[0035] By introducing an enhanced The conversion mechanism complements the missing semantic information in the EMF instance model obtained by conversion, can complement the missing SysML v2-specific concepts in the EMF instance model, and ensure that the semantic information of model elements is completely retained. At the same time, ensure that the converted EMF model is strictly consistent with the original SysML v2 model in terms of structure (such as classes, associations, inheritance) and dynamic behavior (such as state machines, activity diagrams), avoiding logical breaks. In addition, it can automatically fill in implicit semantic information, reduce manual intervention, and improve conversion efficiency.

[0036] After step S110 is executed, in step S120, the rule script is applied to map the model elements in the source model resource to intermediate model elements based on a preset SysMLine metamodel, generating an intermediate model.

[0037] In an embodiment of the present application, the rule script is SysML2SysMLine.etl.

[0038] The semantic mapping from the source SysML metamodel to the intermediate model based on the preset SysMLine metamodel is realized through the SysML2SysMLine.etl script, effectively making up for problems such as insufficient information in the source SysML metamodel. This conversion not only includes adjustments to the syntax structure, but also realizes the accurate migration of domain semantics through element type conversion rules.

[0039] In an embodiment of the present application, during the execution of step S120, first, the elements (such as FeatureMembership, Import, etc.) of the source SysML model and their nested structures (such as the hierarchical relationship of OwningMembership) are parsed. At the same time, mapping rules are defined through the ETL script (SysML2SysMLine.etl) to semantically correspond SysML v2 elements to the core classes of the SysMLine metamodel. For example: FeatureMembership of SysML v2 is mapped to the Feature abstract class of SysMLine, and its specific subclasses (such as PortUsage, PartUsage) directly inherit to retain semantic details; the complex membership relationships of SysML v2 (such as NamespaceMembership) are converted to the flattened Relationship type of SysMLine, explicitly marking the dependency direction and context.

[0040] Secondly, expand the multi-level nested OwningMembership structure in the source SysML model into independent elements of SysMLine, establish connections through direct associations (such as Relationship), eliminate redundant encapsulation, and convert the Import relationship of SysML v2 into explicit tags of SysMLine (such as Dependency or ImportRelationship), simplifying cross-package reference resolution, that is, making the process of an element in one SysML package referring to or depending on an element defined in another SysML package easier and clearer.

[0041] Next, through logical judgments in the ETL script (such as analyzing element types or association relationships), automatically fill in boolean flags such as isDerived and isOrdered in SysMLine to make the information more concise.

[0042] Finally, finally output an intermediate model instance that conforms to the SysMLine metamodel. Its elements, attributes, and relationships are all instantiated through EMF (Eclipse Modeling Framework) structures to ensure compatibility with the SysMLine toolchain. At the same time, it is more suitable for management and verification, laying a foundation for subsequent operations such as verification, change, and write-back.

[0043] Through the process of executing step S120 above, strict semantic mapping rules (such as directly mapping the Port direction attribute to PortDefinition) can be used to ensure that the intermediate model faithfully reflects the original design intention of SysML v2 and avoid information loss during the conversion process. At the same time, eliminate the deep nesting of SysML v2, making elements directly accessible (such as without having to cross multiple levels to resolve Port attributes), reducing the complexity of model traversal. By explicitizing flags such as isReadOnly, enhance the readability of the model content, facilitating developers and tools to quickly understand the constraints. Secondly, by injecting attributes such as isDerived, provide a basis for model verification and optimization, such as identifying features that need to be dynamically calculated. Support reverse engineering and impact analysis through the valuePart and type_ fields, such as tracing the impact path of requirement changes on specific model elements. In addition, the generated intermediate model is implemented based on EMF and can be directly integrated into modeling tools or code generators supported by SysMLine, and provide a conversion bridge for the long-term coexistence of SysML v2 and SysMLine, supporting the migration and collaboration of models between heterogeneous tools.

[0044] After step S120 is executed, in step S130, enhance the intermediate model.

[0045] In an embodiment of the present application, during the process of enhancing the intermediate model, at least one of the following steps is performed: complementing the missing derived semantic information in the intermediate model through static analysis and rule derivation, automatically generating the attribute identifiers and value range information of the intermediate model through EOL scripts, and simplifying and reconstructing the structure of the intermediate model. That is, one of these steps can be executed, two of these steps can be executed, or all three of these steps can be executed.

[0046] In an embodiment of the present application, the aforementioned derived semantic information includes isDerived information, direction information, and multiplicityRange information.

[0047] Logical contradictions caused by manual filling are avoided through rule derivation. For example, the multiplicityRange information is automatically inferred based on the class relationship at both ends of the association to prevent multiplicity range conflicts. By complementing the missing derived semantic information in the intermediate model, it is possible to ensure that the intermediate model contains all necessary metadata (such as association direction, multiplicity constraints, etc.), providing a complete input for subsequent verification and conversion. At the same time, by generating complete semantic information through complementing the missing derived semantic information in the intermediate model, the intermediate model can be directly used in the automated tool chain, reducing manual intervention and improving development efficiency. In addition, complementing information such as direction (association direction) and isDerived (derived attribute marker) makes the intermediate model more readable and reduces users' misunderstanding of implicit logic.

[0048] In an embodiment of the present application, automatically generating the attribute identifiers and value range information of the intermediate model through EOL scripts can perform one of the following two steps: dynamically expanding the metadata of the intermediate model elements and standardizing the attribute definitions to adapt to the corresponding data format requirements.

[0049] In an embodiment of the present application, simplifying and reconstructing the structure of the aforementioned intermediate model includes eliminating intermediate levels and merging redundant links.

[0050] By eliminating intermediate levels and merging redundant links, the structure of the intermediate model can be made more refined, intuitive, and engineering-usable.

[0051] In an embodiment of the present application, after enhancing the intermediate model, at least one of the following two steps is performed on the enhanced intermediate model: automatically modifying the structure or content of the enhanced intermediate model through EOL scripts and performing naming convention verification and structural consistency checking on the enhanced intermediate model through the EVL verification engine. That is, one of these two steps can be executed, or all of these two steps can be executed.

[0052] By automatically modifying the structure or content of the enhanced intermediate model, it is possible to support the dynamic adjustment of the model structure based on preset rules, improving the logical clarity of the model. By performing naming convention verification and structural consistency checking on the enhanced intermediate model, the readability of the model can be ensured, and reverse quality feedback can be provided to form a continuous optimization mechanism.

[0053] After step S130 is executed, in step S140, the enhanced intermediate model is output as a SysMLine model in EMF format, and the SysMLine model in EMF format is converted into a SysML v2 text representation through a reverse mapping mechanism.

[0054] In an embodiment of the present application, during the process of outputting the enhanced intermediate model as a SysMLine model in EMF format, the serialization function provided by the EMF framework is used to write the enhanced intermediate model that already exists in memory, conforms to the SysMLine metamodel definition, and has undergone enhancement processing into a persistent file (such as an XMI format), and this file follows the specifications defined by the SysMLine metamodel, which defines the format of the SysMLine model, thus forming a SysMLine model in EMF format.

[0055] In an embodiment of the present application, during the process of converting the SysMLine model in EMF format into a SysML v2 text representation through a reverse mapping mechanism, first, a mapping rule file (such as an Xtext grammar or a QVT script) is created to map the SysMLine model in EMF format to the syntax structure of SysML v2. Secondly, by executing the SysMLine2SysML.egx script to traverse the SysMLine model in EMF format, text conforming to the SysML v2 text syntax (such as a.sysml file) is generated. Then, the generated text is subjected to syntax checking through the SysML v2 official toolchain (such as the SysML v2 API) to ensure that it conforms to the specifications.

[0056] By executing step S140, it is possible to achieve the backhaul of the enhanced intermediate model and semantic preservation.

[0057] In summary, through the model enhancement and bidirectional transformation solution for SysML v2 provided above, the embodiments of the present application support two input formats, namely the SysML v2 text representation and the EMF instance model, ensuring that the toolchain can adapt to different development environments and meet diverse user requirements. By mapping the source model to an intermediate model based on the preset SysMLine metamodel through rule scripts, semantic abstraction and logical isolation of SysML v2 are achieved, making subsequent processing independent of the specific source format and enhancing model management capabilities and interoperability. By performing enhancement processing on the intermediate model, domain-specific optimizations can be injected to improve the analyzability and reuse value of the model. Through the reverse mapping mechanism, the enhanced processing results are written back as the SysML v2 text representation, implementing a bidirectional mapping mechanism between the original SysML v2 model and the SysMLine model, supporting forward import and reverse transmission of the model, and enhancing the ecological compatibility and engineering usability of the SysML v2 model.

[0058] Further, in some embodiments, when receiving the SysML v2 text representation, a SysML v2 original model is constructed through the SysML v2 text representation, and the SysML v2 original model is converted into an EMF instance model through the SysML v2 Pilot tool or the syntax tree generation tool, and an enhanced conversion mechanism is introduced in the SysMLine framework to complement the missing semantic information in the converted EMF instance model. This not only maintains the semantic consistency of the SysML v2 original model but also lays a structurally complete model foundation for subsequent analysis, verification, export, etc. while ensuring standard compatibility.

[0059] Furthermore, in some embodiments, during the enhancement process of the intermediate model, by complementing the missing derived semantic information in the intermediate model, the semantics of the intermediate model that are implicit or not explicitly defined can be automatically deduced through logical rules, and the logical discontinuities caused by differences in the source model format or information loss can be repaired. By automatically generating the attribute identifiers and value range information of the intermediate model, the metadata of the intermediate model elements can be dynamically extended, and the attribute definitions can be standardized to adapt to the corresponding data format requirements. By simplifying and reconstructing the structure of the intermediate model, the model hierarchy relationship can be optimized, irrelevant details or intermediate state data can be removed, and the core logical expression can be focused on, accelerating the subsequent conversion and verification processes.

[0060] Furthermore, in some embodiments, after enhancing the intermediate model, by automatically modifying the structure or content of the enhanced intermediate model, it is possible to support dynamic adjustment of the model structure based on preset rules, improving the logical clarity of the model. By performing naming convention verification and structural consistency checking on the enhanced intermediate model, the readability of the model can be ensured, and reverse quality feedback can be provided to form a continuous optimization mechanism.

[0061] The embodiment of the present application also provides a model enhancement and bidirectional conversion system for SysML v2, which can perform model enhancement and bidirectional conversion for SysML v2 by using the aforementioned model enhancement and bidirectional conversion method 100 for SysML v2, or can also use other methods for model enhancement and bidirectional conversion for SysML v2, and the present application does not limit this here.

[0062] Figure 2 Shows an exemplary structural block diagram of the model enhancement and bidirectional conversion system for SysML v2 according to the embodiment of the present application.

[0063] As Figure 2 shown, the system 200 includes a model import module 210, a model conversion module 220, a model enhancement module 230, and a model export module 240. In the embodiment of the present application, the model import module 210, the model conversion module 220, the model enhancement module 230, and the model export module 240 can be separate units or can also be integrated in the same integrated circuit, and the present application does not limit this here.

[0064] Specifically, the model import module 210 is used to receive and parse the source SysML v2 model to establish source model resources, where the source SysML v2 model is a SysML v2 text representation or its corresponding EMF instance model.

[0065] Specifically, the model conversion module 220 is used to map the model elements in the aforementioned source model resources to intermediate model elements based on a preset SysMLine meta-model by applying a rule script, generating an intermediate model.

[0066] Specifically, the model enhancement module 230 is used to perform enhancement processing on the aforementioned intermediate model.

[0067] Specifically, the model export module 240 is used to output the enhanced intermediate model as a SysMLine model in EMF format and convert the SysMLine model in EMF format to a SysML v2 text representation through a reverse mapping mechanism.

[0068] When the system 200 performs model enhancement and bidirectional conversion for SysML v2 by using the aforementioned model enhancement and bidirectional conversion method 100 for SysML v2, the aforementioned step S110 is executed by the model import module 210, the aforementioned step S120 is executed by the model conversion module 220, the aforementioned step S130 is executed by the model enhancement module 230, and the aforementioned step S140 is executed by the model export module 240. For the specific execution process, reference can be made to the foregoing text, which will not be elaborated herein.

[0069] Although multiple embodiments of the present application have been shown and described herein, it will be apparent to those skilled in the art that such embodiments are provided by way of example only. Many variations, changes, and alternative approaches may occur to those skilled in the art without departing from the spirit and scope of the present application. It should be understood that various alternatives to the embodiments of the present application described herein may be employed in practicing the present application. The appended claims are intended to define the scope of protection of the present application and thus cover equivalents or alternatives within the scope of these claims.

Claims

1. A model enhancement and bidirectional conversion method for SysML v2, characterized in that including: Receiving and parsing a source SysML v2 model to establish source model resources, where the source SysML v2 model is a SysML v2 text representation or its corresponding EMF instance model; Applying a rule script to map model elements in the source model resources to intermediate model elements based on a preset SysMLine meta-model, generating an intermediate model; Performing enhancement processing on the intermediate model; Outputting the enhanced intermediate model as a SysMLine model in EMF format and converting the SysMLine model in EMF format to a SysML v2 text representation through an inverse mapping mechanism.

2. The method for model enhancement and bidirectional transformation for SysML v2 according to claim 1, wherein When receiving a SysML v2 text representation, constructing a SysML v2 original model through the SysML v2 text representation and converting the SysML v2 original model to an EMF instance model through a SysML v2 Pilot tool or a syntax tree generation tool.

3. The method for model enhancement and bidirectional transformation for SysML v2 according to claim 2, wherein After converting the SysML v2 original model into an EMF instance model, an enhanced conversion mechanism is introduced in the SysMLine framework to complement the missing semantic information in the converted EMF instance model.

4. The method for model enhancement and bidirectional transformation for SysML v2 according to claim 3, wherein The missing semantic information includes the semantic subset relationship that an attribute should have.

5. The method for model enhancement and bidirectional transformation for SysML v2 according to claim 1, wherein The rule script is SysML2SysMLine.etl.

6. The method for model enhancement and bidirectional transformation for SysML v2 according to claim 1, wherein During the process of performing enhancement processing on the intermediate model, at least one of the following steps is executed: Completing the missing derived semantic information in the intermediate model through static analysis and rule derivation; Automatically generating attribute identifiers and value range information of the intermediate model through an EOL script; Simplifying and reconstructing the structure of the intermediate model.

7. The method for model enhancement and bidirectional transformation for SysML v2 according to claim 6, wherein After performing enhancement processing on the intermediate model, one of the following steps is executed on the enhanced intermediate model: Automatically modifying the structure or content of the enhanced intermediate model through an EOL script; Performing naming convention verification and structural consistency check on the enhanced intermediate model through an EVL verification engine.

8. The method for model enhancement and bidirectional transformation for SysML v2 according to claim 6, wherein The derived semantic information includes isDerived information, direction information, and multiplicityRange information.

9. The method for model enhancement and bidirectional transformation for SysML v2 according to claim 6, wherein The simplifying and reconstructing the structure of the intermediate model includes eliminating intermediate levels and merging redundant links.

10. A model enhancement and bidirectional conversion system for SysML v2, characterized in that Implementing model enhancement and bidirectional conversion for SysML v2 by using the SysML v2-oriented model enhancement and bidirectional conversion method according to any one of claims 1-9. The system includes: A model import module for receiving and parsing a source SysML v2 model to establish source model resources, where the source SysML v2 model is a SysML v2 text representation or its corresponding EMF instance model; A model conversion module for applying a rule script to map model elements in the source model resources to intermediate model elements based on a preset SysMLine meta-model, generating an intermediate model; A model enhancement module for performing enhancement processing on the intermediate model; A model export module for outputting the enhanced intermediate model as a SysMLine model in EMF format and converting the SysMLine model in EMF format to a SysML v2 text representation through an inverse mapping mechanism.

Images