mbse:sysml_v2_transition:sysml_v1_to_sysml_v2_transition_guidance
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
mbse:sysml_v2_transition:sysml_v1_to_sysml_v2_transition_guidance [2024/04/04 16:49] fsalvatore [2.5 Considerations for deploying SysML v2 to programs] |
mbse:sysml_v2_transition:sysml_v1_to_sysml_v2_transition_guidance [2024/04/09 15:30] fsalvatore [2.3 Conduct Pilots to Assess the Impact on Current MBSE Practices] |
||
|---|---|---|---|
| Line 54: | Line 54: | ||
| Other typical pilot projects may address one or more of the following pilot objectives: | Other typical pilot projects may address one or more of the following pilot objectives: | ||
| - | 1. Increase awareness of the SysML v2 Modeling Language and its differences with SysML v1 | + | 1. Increase awareness of the SysML v2 Modeling Language and its differences with SysML v1\\ |
| - | 2. Learn the SysML v2 Modeling Language and build the workforce skill base | + | 2. Learn the SysML v2 Modeling Language and build the workforce skill base\\ |
| - | 3. Evaluate current SysML v1 models to define criteria and assess there suitability for model conversion | + | 3. Evaluate current SysML v1 models to define criteria and assess there suitability for model conversion\\ |
| - | 4. Establish approach for converting SysML v1 models to SysML v2 models | + | 4. Establish approach for converting SysML v1 models to SysML v2 models\\ |
| - | 5. Pre-process SysML v1 models to position them for successful transformation to SysML v2 | + | 5. Pre-process SysML v1 models to position them for successful transformation to SysML v2\\ |
| - | 6. Evaluate and recommend changes to existing methodology | + | 6. Evaluate and recommend changes to existing methodology\\ |
| - | 7. Evaluate tools as they become available | + | 7. Evaluate tools as they become available\\ |
| - | 8. Evaluate current customizations, integrations, plugins etc. and strategize their migration to SysML v2 | + | 8. Evaluate current customizations, integrations, plugins etc. and strategize their migration to SysML v2\\ |
| - | 9. Establish metrics to help manage the transition process and evaluate improvements | + | 9. Establish metrics to help manage the transition process and evaluate improvements\\ |
| ==== 2.4 Update Modeling Infrastructure ==== | ==== 2.4 Update Modeling Infrastructure ==== | ||
| Line 103: | Line 103: | ||
| An additional question is whether the entire model needs to be converted, or perhaps just a portion of the model. There may be cases where only a portion of the model needs to be converted to achieve the program objectives. For example, the new program may only be addressing selected subsystems and may not require the detailed model of all subsystems be converted, or the SysML v1 model may include parametric models to support analysis that may not be required of the SysML v2 model at this time. | An additional question is whether the entire model needs to be converted, or perhaps just a portion of the model. There may be cases where only a portion of the model needs to be converted to achieve the program objectives. For example, the new program may only be addressing selected subsystems and may not require the detailed model of all subsystems be converted, or the SysML v1 model may include parametric models to support analysis that may not be required of the SysML v2 model at this time. | ||
| - | ==== 2.6 Deploy MBSE with SysML v2 to programs ==== | + | ==== 2.6 Deploy MBSE with SysML v2 to Programs ==== |
| Deploying MBSE with SysML v2 to a program should address the deployment considerations described previously. The program stakeholders must be involved in the decision and support the decision for this to be successful. The organization transition/improvement team should assist the program by providing the organizational infrastructure and technical support. | Deploying MBSE with SysML v2 to a program should address the deployment considerations described previously. The program stakeholders must be involved in the decision and support the decision for this to be successful. The organization transition/improvement team should assist the program by providing the organizational infrastructure and technical support. | ||
| Line 119: | Line 119: | ||
| === 2.6.1 Monitor the Improvements === | === 2.6.1 Monitor the Improvements === | ||
| - | The organization and the program should monitor the results of the transition to SysML v2. Key metrics should include productivity and quality metrics that address the needs of the current program and provide inputs for future cost estimating, and other typical systems engineering metrics (e.g., requirements satisfaction, technical performance measures, etc.). This information can be used to refine and update the organizational infrastructure. | + | The organization and the program should monitor the results of the transition to SysML v2. Key metrics should include productivity and quality metrics that address the needs of the current program and provide inputs for future cost estimating, and other typical systems engineering metrics (e.g., requirements satisfaction, technical performance measures). This information can be used to refine and update the organizational infrastructure. |
| Lessons learned and program successes should also be captured to provide inputs for improving the modeling infrastructure and sharing this information across the organization. | Lessons learned and program successes should also be captured to provide inputs for improving the modeling infrastructure and sharing this information across the organization. | ||
| - | |||
mbse/sysml_v2_transition/sysml_v1_to_sysml_v2_transition_guidance.txt · Last modified: 2024/04/09 15:30 by fsalvatore
Page Tools
