Overview
This activity diagram describes the activities required to prepare an organization for the adoption of SysML v2.
The process involves multiple stakeholder groups including systems engineers, IT engineers, software developers, and an interdisciplinary cross-functional transition team.
Process
The preparation phase begins with establishing a transition team responsible for defining the overall migration strategy and transition plans. These plans typically address migration goals, schedules, budgets, pilot projects, training activities, and methodology evolution.
Pilot projects are then conducted to assess the impact of SysML v2 on existing MBSE practices. Typical pilot objectives include:
- Increasing organizational awareness of SysML v2.
- Building initial SysML v2 expertise.
- Evaluating candidate SysML v1 models for migration.
- Assessing available SysML v2 tooling.
- Establishing migration approaches and practices.
- Evaluating integrations, plugins, and reporting solutions.
- Defining metrics for tracking migration progress.
Systems engineers evaluate and select SysML v2 modeling tools, while IT engineers deploy and configure the required modeling infrastructure and model repositories.
In parallel, software developers adapt existing tool customizations and integrations to operate in a SysML v2 environment. This frequently includes updates to:
- Plugins.
- Reports.
- Scripts.
- External integrations.
After the infrastructure is established, systems engineers update organizational methodologies, training materials, community resources, reference architectures, and reusable assets to support SysML v2.