This activity diagram describes the execution of the SysML v1 to SysML v2 transformation process.
The transformation produces a SysML v2 project from a prepared SysML v1 source model using a transformation tool conformant with the SysML v1-to-v2 Transformation Specification.
The process begins with selecting a transformation tool that supports the SysML v1-to-v2 transformation specification.
For one-off migrations, a new SysML v2 project is created. For incremental migrations, an existing SysML v2 project may be reused.
The transformation environment then prepares the target structure by:
- Creating a target SysML v2 project.
- Creating namespaces for the migrated project.
- Creating namespaces for individual subprojects.
Before execution, systems engineers may customize the standard transformation mappings. This allows organizations to adapt the migration process to project-specific requirements.
Typical customization activities include:
- Modifying standard SysML v1-to-v2 mappings.
- Defining profile-to-library mappings.
- Defining stereotype-to-metadata mappings.
- Storing reusable mapping configurations.
The transformation process then executes the migration of supported artifacts, including:
- Model elements.
- Diagrams.
- Tables.
- Matrices.
- Relation maps.
- Supported custom extensions.
The transformation should also generate reports identifying unsupported or non-transformed elements, allowing users to address these items during later migration stages.
After transformation, validation warnings and errors are reviewed and the generated model may be inspected manually before continuing to post-processing.