mbse:sysml_v2_transition:frequently_asked_question_faq_s
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:frequently_asked_question_faq_s [2024/04/30 21:17] fsalvatore [----] |
mbse:sysml_v2_transition:frequently_asked_question_faq_s [2024/05/07 12:42] (current) fsalvatore [Frequently Asked Question (FAQ's)] |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| ===== Frequently Asked Question (FAQ's) ===== | ===== Frequently Asked Question (FAQ's) ===== | ||
| - | [[https://www.de-bok.org/asset/b35814ecf5efbc67d47a7290440bca2f0ed205a5|Download]] | + | [[https://www.de-bok.org/asset/3b8de9f20f1b734efb4b958465259ccb39fa7c1a|Download]] |
| SysML v2 is the next generation systems modeling language that overcomes many limitations of its predecessor, SysML v1. It is a powerful tool for model-based systems engineering (MBSE) and allows for the representation of various system aspects such as structure, behavior, requirements, analysis cases, verification cases, and traceability. SysML v2 also introduces a new metamodel based on formal semantics, a complementary textual syntax, and a standardized API for model access. The transition from SysML v1 to SysML v2 offers significant potential improvements and potential risks to all organizations and careful planning must be executed for a successful transition. | SysML v2 is the next generation systems modeling language that overcomes many limitations of its predecessor, SysML v1. It is a powerful tool for model-based systems engineering (MBSE) and allows for the representation of various system aspects such as structure, behavior, requirements, analysis cases, verification cases, and traceability. SysML v2 also introduces a new metamodel based on formal semantics, a complementary textual syntax, and a standardized API for model access. The transition from SysML v1 to SysML v2 offers significant potential improvements and potential risks to all organizations and careful planning must be executed for a successful transition. | ||
| Line 73: | Line 73: | ||
| | 6.8| How does a SysML v2 model interact with a UML-based model including a SysML v1 model, a UML model, and a UAF v1 model?| There are different strategies to enable the interaction between a SysML v2 model and any other UML-based model including SysML v1 models, UML models, and UAF v1 models. The general tool integration strategy that was referred to in response to section 5.15is applicable. The strategy should consider the level of coupling between the SysML v2 model and the other model and whether the SysML v2 model and/or the other model are anticipated to undergo significant and frequent change or be relatively static.\\ \\ A typical use case for interacting with a UAF v1 model is that the UAF model describes a system of systems model that is elaborated by a SysML v2 model. In this case, the SysML v2 model is dependent on the UAF model. A way for these two models to interact is to use the SysML v2 API and its external relationship service to establish and maintain dependency relationships between selected elements in the SysML v2 model and selected elements in the UAF model. When UAF v2 becomes available, the UAF v1 model can be converted to a UAF v2 model. The SysML v2 model and the UAF model should be able to interact through the SysML v2 API, or the SysML v2 model can treat the UAF v2 model as a project usage.\\ \\ A typical use case for interacting with a UML model is that the SysML model is the source of the software requirements and UML is used to model the software design. In this case, the UML model is dependent on the SysML v2 model. A similar approach can be used as described above for interacting with a UAF model. The SysML v2 API and its external relationship service can be used to establish and maintain dependency relationships between elements in the UML and elements in the SysML v2 model.\\ \\ There are additional approaches to enable the interaction between a SysML v1 model and a SysML v2 model beyond the use of the API and its external relationship service as described above. If the SysML v1 model is not anticipated to change, then the SysML v1 model can be converted to a SysML v2 model where it can be further elaborated. If the SysML v1 model is subject to further change, the converted SysML v2 model can be treated as a project usage for the SysML v2 model under development. The SysML v1 model can be updated and periodically converted to SysML v2. Branch and merge techniques would be used to manage updates to the project usage, and the impact on the SysML v2 model under development. | | | 6.8| How does a SysML v2 model interact with a UML-based model including a SysML v1 model, a UML model, and a UAF v1 model?| There are different strategies to enable the interaction between a SysML v2 model and any other UML-based model including SysML v1 models, UML models, and UAF v1 models. The general tool integration strategy that was referred to in response to section 5.15is applicable. The strategy should consider the level of coupling between the SysML v2 model and the other model and whether the SysML v2 model and/or the other model are anticipated to undergo significant and frequent change or be relatively static.\\ \\ A typical use case for interacting with a UAF v1 model is that the UAF model describes a system of systems model that is elaborated by a SysML v2 model. In this case, the SysML v2 model is dependent on the UAF model. A way for these two models to interact is to use the SysML v2 API and its external relationship service to establish and maintain dependency relationships between selected elements in the SysML v2 model and selected elements in the UAF model. When UAF v2 becomes available, the UAF v1 model can be converted to a UAF v2 model. The SysML v2 model and the UAF model should be able to interact through the SysML v2 API, or the SysML v2 model can treat the UAF v2 model as a project usage.\\ \\ A typical use case for interacting with a UML model is that the SysML model is the source of the software requirements and UML is used to model the software design. In this case, the UML model is dependent on the SysML v2 model. A similar approach can be used as described above for interacting with a UAF model. The SysML v2 API and its external relationship service can be used to establish and maintain dependency relationships between elements in the UML and elements in the SysML v2 model.\\ \\ There are additional approaches to enable the interaction between a SysML v1 model and a SysML v2 model beyond the use of the API and its external relationship service as described above. If the SysML v1 model is not anticipated to change, then the SysML v1 model can be converted to a SysML v2 model where it can be further elaborated. If the SysML v1 model is subject to further change, the converted SysML v2 model can be treated as a project usage for the SysML v2 model under development. The SysML v1 model can be updated and periodically converted to SysML v2. Branch and merge techniques would be used to manage updates to the project usage, and the impact on the SysML v2 model under development. | | ||
| | 6.9| How do you integrate a SysML v2-based UAFML with SysML v2 models? | Refer to the response in Section 6.8.| | | 6.9| How do you integrate a SysML v2-based UAFML with SysML v2 models? | Refer to the response in Section 6.8.| | ||
| - | | 6.10| What is the impact of SysML v2 transition on integrating MBSE with model-based software engineering (UML)?| This is partially dependent on the methodology. One methodological approach is to treat the SysML v2 model as a source of the software requirements where the software modeling tool would access the SysML v2 model through the SysML v2 API. There may be additional opportunities beginning with pilot projects to explore how to improve integration with model-based software development by using SysML v2 and leveraging the SysML v2 textual notation.\\ \\ Refer to response in section 6.8.| | + | | 6.10| What is the impact of SysML v2 transition on integrating MBSE with model-based software engineering (UML)? |This is partially dependent on the methodology. One methodological approach is to treat the SysML v2 model as a source of the software requirements where the software modeling tool would access the SysML v2 model through the SysML v2 API. There may be additional opportunities beginning with pilot projects to explore how to improve integration with model-based software development by using SysML v2 and leveraging the SysML v2 textual notation.\\ \\ Refer to response in section 6.8.| |
| | 6.11| What is the impact of transitioning from a SysML v1-based UAFML to SysML-v2-based UAFML? | This will be dependent on the approach to how UAF v2 extends SysML v2. In particular, if UAF is specified as a SysML v2 model library, the UAF v1 to UAV v2 transformation could potentially directly leverage the SysML v1 to SysML v2 transformation. The transition from UAF v1 to UAF v2 would be similar to the transition from SysML v1 to SysML v2 enabling UAF to leverage much of what is developed and learned from the SysML v2 transition.| | | 6.11| What is the impact of transitioning from a SysML v1-based UAFML to SysML-v2-based UAFML? | This will be dependent on the approach to how UAF v2 extends SysML v2. In particular, if UAF is specified as a SysML v2 model library, the UAF v1 to UAV v2 transformation could potentially directly leverage the SysML v1 to SysML v2 transformation. The transition from UAF v1 to UAF v2 would be similar to the transition from SysML v1 to SysML v2 enabling UAF to leverage much of what is developed and learned from the SysML v2 transition.| | ||
| | 6.12| Can a view of the SysML v2 model be delivered versus delivering the entire model?| Yes. A view of the model is a specific model element that exposes a subset of the model. The API query capability can be used to generate the view and be specified as a deliverable.| | | 6.12| Can a view of the SysML v2 model be delivered versus delivering the entire model?| Yes. A view of the model is a specific model element that exposes a subset of the model. The API query capability can be used to generate the view and be specified as a deliverable.| | ||
mbse/sysml_v2_transition/frequently_asked_question_faq_s.1714526235.txt.gz ยท Last modified: 2024/04/30 21:17 by fsalvatore
Page Tools
