Any advancement over SysML v1.0 is a bonus and SysML v.2.0 will make it easier for SysML to get adopted in general despite the fact that it's already widely used.
Hello, is there any literture on market which introduces the entire language SysML V2 (Diagrams, Syntax, ...) in the mean time? Not limited to differences v1 vs. v2? Means, instead of learning v1 and than check what are the differences to v2, I would prefer to learn directly v2 from scratch. So I dont want to wast time on learning things which will not be used in the near future. I just found the "Don't panic" booklet from OMG which looks like an overview only. Thank you!
Are the SysML 2.0 diagrams same as SysML 1.0? What are the changes between two diagram versions considering 2.0 follows the KerML and 1.0 follows the UML?
The SysML v2 diagrams are specified as views in the model which unlike SysML v1, are formally part of the model. There are several SysML v2 standard views such as a general view, an interconnection view, an action flow view, a state transition view, and others. The SysML v2 standard views can provide similar depictions as the SysML v1 diagram kinds (e.g., block definition diagram, internal block diagram, activity diagram, state machine diagram, etc.) SysML v2 provides additional capabilities to specify user defined views and select the kind of model elements that appear on a diagram and how they appear. The capability to specify user-defined views may take time for the tool vendors to fully support.
Your Lead Engineers should first learn the principles and concepts of Object-Orientation, UML and then SysML. I suspect that they have failed to do that. The origins of SysML are from Software Engineering, hence, why Software Engineers get it, because they were trained to use such specific and specialised notation for complex Systems Design. In my experience, the people who usually complain are non-Software Engineers because they lack the training which they're missing and should be seeking from their current employer. The answer is not to stick to .pptx!! 🤣🤣🤣🤣
Any advancement over SysML v1.0 is a bonus and SysML v.2.0 will make it easier for SysML to get adopted in general despite the fact that it's already widely used.
Hello, is there any literture on market which introduces the entire language SysML V2 (Diagrams, Syntax, ...) in the mean time? Not limited to differences v1 vs. v2? Means, instead of learning v1 and than check what are the differences to v2, I would prefer to learn directly v2 from scratch. So I dont want to wast time on learning things which will not be used in the near future. I just found the "Don't panic" booklet from OMG which looks like an overview only. Thank you!
Are the SysML 2.0 diagrams same as SysML 1.0? What are the changes between two diagram versions considering 2.0 follows the KerML and 1.0 follows the UML?
The SysML v2 diagrams are specified as views in the model which unlike SysML v1, are formally part of the model. There are several SysML v2 standard views such as a general view, an interconnection view, an action flow view, a state transition view, and others. The SysML v2 standard views can provide similar depictions as the SysML v1 diagram kinds (e.g., block definition diagram, internal block diagram, activity diagram, state machine diagram, etc.) SysML v2 provides additional capabilities to specify user defined views and select the kind of model elements that appear on a diagram and how they appear. The capability to specify user-defined views may take time for the tool vendors to fully support.
Are the slides available?
The link to the slides were just added to the video description.
What’s the charge number for watching this? Jk great stuff
"promo sm"
Now its even more complicated. Thats why our lead engineers stick to powerpoint. We need a new lean modelling language asap.
did you watch the entire video, and how acquainted are you with SysML? just trying to understand how I should interpret your comment.
Powerpoint isn't a modeling language...it's a diagramming tool.
Your Lead Engineers should first learn the principles and concepts of Object-Orientation, UML and then SysML. I suspect that they have failed to do that. The origins of SysML are from Software Engineering, hence, why Software Engineers get it, because they were trained to use such specific and specialised notation for complex Systems Design. In my experience, the people who usually complain are non-Software Engineers because they lack the training which they're missing and should be seeking from their current employer. The answer is not to stick to .pptx!! 🤣🤣🤣🤣
@@WilbanksUSMC it's not even a diagramming tool, it's a presentation tool.
Yeah, engineering is tough. It's easier to avoid it by using powerpoint.