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 | Last revision Both sides next 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/04 16:51] fsalvatore [2.6 Deploy MBSE with SysML v2 to programs] |
||
|---|---|---|---|
| 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
