Very well done. Thanks. Everytime I question myself on something re: SysML, I always seem to keep coming back to your video to continually refresh the fundamentals of the 4 pillars. I appreciate you sharing your knowledge. Cheers.
I work as a CAD/CAM/CAE person and no matter how hard I try, I'm completely lost when it comes to understanding something like SysML. This presentation is well paced and thought out and yet I'm completely lost. Funny that one vender of SysML diagramming tools is called "no magic" well to me...it is magic! Same goes for requirements management, it gives me the creeps--though I understand it's important!!!
I agree. I do most of my work in CAD and I don't understand the point of SysML and tools like Modelio. Is it a brain mapping tool? What does it output? It isn't equipped for extensive simulations so I can't use it to model vehicles very well. Right now I'm more tempted to put out the money for a dedicated vehicle modeling program.
@@ben-2368 I'm a software guy and we make plenty of UML diagrams (UML is the father of SysML etc. etc.) and most of them can infact be used to produce code, both by hand (the diagrams define structure and behaviour of programs) or automatically (diagram to code and vice versa) but for SysML, I dunno man. I don't see why I should use SysML over UML, UML is (at least to me) even more readable than this. Block diagrams just feel like an even more abstract version of a class diagram, which in itself differs in how you implement it based on your language.. This just seems too abstract to me.. I mean abstractions are nice, but this is as abstract as it gets and almost obscures things.. But oh well. Maybe I'm just missing the entire point of it
SysML is probably not for you. It was developed to provide a formal language for describing system level needs, properties, top level analyses, interfaces and requirements, as opposed to relying solely on textual specifications. Some of my students have never had to develop system level specifications, and are much more comfortable with more concrete engineering concepts. I just hope you recognize that the system specifications need to come from somewhere, and it might be a good idea to model them before the detail design engineers like yourself are forced to comply with them.
perfect: quick yet comprehensive. good ramp up, especially for software engineers who already familiar with UML. In terms of 4 pillars, it is subjectively a very definition of any software or system architecture
Excellent presentation, Rick -- thank you. If you're up to it, it'd be helpful to see a similar presentation on OPM (Object Process Methodology), which takes different approach in some ways, by including processes (not only objects). Personally, for a complex system, SysML helps remove ambiguity and complexity, among other benefits, and I like it. I have yet to apply OPM, and I'm curious as to how they will differ. Thank you so much.
Nice pace man!. Other videos are basically just reciting the official docs where they mention every type of connection etc. At least here you give a good overview of what most people will want to use.
A program that turns mathematical principles into flowcharts. Is the friction block considering the coefficient of friction and can you see all the mathematical equations use across all the blocks?
Setting Systems Engineering back more than 50 years. As a Systems Engineer practicing for 36 years I am dumbfounded. Apparently Object Oriented S/W programming needs have now driven a redesign of Systems Engineering practices so that the coders' job can be done without the need to think. If SysML turns out anything like Object Oriented Code, the documentation generated will be nearly indecipherable and scattered willy nilly so that putting it into an understandable description of what the system does will take longer than the design required in the first place. I do appreciate the explanation however, it is well presented. I just fail to see the utility in SysML other than placating the needs of OO programmers. It certainly doesn't do much to help understand what a system is actually supposed to be doing as far as I can see.
![PASULOL รามเกียรติ์ ตอนที่ 4 นนทกพบรัก [Ramakien Ep.4: Nonthok in love]](http://i.ytimg.com/vi/tMUQgmZzf_A/mqdefault.jpg)
Hands down the best video I have found on the mindset and approach to MBSE in SysML.
I'm stupefied that this is the first I'm hearing of SysML.
Thanks, Rick. I prefer SysML because it simplifies things. Thanks.
Very well done. Thanks. Everytime I question myself on something re: SysML, I always seem to keep coming back to your video to continually refresh the fundamentals of the 4 pillars. I appreciate you sharing your knowledge. Cheers.
I work as a CAD/CAM/CAE person and no matter how hard I try, I'm completely lost when it comes to understanding something like SysML. This presentation is well paced and thought out and yet I'm completely lost. Funny that one vender of SysML diagramming tools is called "no magic" well to me...it is magic! Same goes for requirements management, it gives me the creeps--though I understand it's important!!!
I agree. I do most of my work in CAD and I don't understand the point of SysML and tools like Modelio.
Is it a brain mapping tool? What does it output? It isn't equipped for extensive simulations so I can't use it to model vehicles very well. Right now I'm more tempted to put out the money for a dedicated vehicle modeling program.
@@ben-2368 I'm a software guy and we make plenty of UML diagrams (UML is the father of SysML etc. etc.) and most of them can infact be used to produce code, both by hand (the diagrams define structure and behaviour of programs) or automatically (diagram to code and vice versa) but for SysML, I dunno man. I don't see why I should use SysML over UML, UML is (at least to me) even more readable than this. Block diagrams just feel like an even more abstract version of a class diagram, which in itself differs in how you implement it based on your language.. This just seems too abstract to me.. I mean abstractions are nice, but this is as abstract as it gets and almost obscures things..
But oh well. Maybe I'm just missing the entire point of it
SysML is probably not for you. It was developed to provide a formal language for describing system level needs, properties, top level analyses, interfaces and requirements, as opposed to relying solely on textual specifications. Some of my students have never had to develop system level specifications, and are much more comfortable with more concrete engineering concepts. I just hope you recognize that the system specifications need to come from somewhere, and it might be a good idea to model them before the detail design engineers like yourself are forced to comply with them.
Excellent tutorial on SysML. Well worth the time!
perfect: quick yet comprehensive. good ramp up, especially for software engineers who already familiar with UML. In terms of 4 pillars, it is subjectively a very definition of any software or system architecture
Excellent presentation, Rick -- thank you. If you're up to it, it'd be helpful to see a similar presentation on OPM (Object Process Methodology), which takes different approach in some ways, by including processes (not only objects). Personally, for a complex system, SysML helps remove ambiguity and complexity, among other benefits, and I like it. I have yet to apply OPM, and I'm curious as to how they will differ. Thank you so much.
What's the difference between processes and behavior?
Fantastic tutorial wish you had more content available!
Amazing.. at 2x speed ! The clarity and punch 🎉
This was an excellent presentation.
Nice pace man!. Other videos are basically just reciting the official docs where they mention every type of connection etc. At least here you give a good overview of what most people will want to use.
Excellent illustration of the four pillars!
Very clear examples of the SysML diagrams with examples. Thanks.
great video - thanks for sharing your knowledge
Play it at 2x speed and it's only 15 minutes :-)
Perferct explanation, i`ll dig into it.
Thank you so much!
Great Video
Thank you!
It makes it a bit more clear to me!
Is there a way to create use case diagram and relate to other diagrams in the model?
Can you please share the presentation used for the explanation.
Thanks! This was a nice first view on SysML
A program that turns mathematical principles into flowcharts. Is the friction block considering the coefficient of friction and can you see all the mathematical equations use across all the blocks?
¿Cómo obtengo las plantillas de sysml para vice 2010?
Thank you this was very helpful
I like it !
Setting Systems Engineering back more than 50 years.
As a Systems Engineer practicing for 36 years I am dumbfounded. Apparently Object Oriented S/W programming needs have now driven a redesign of Systems Engineering practices so that the coders' job can be done without the need to think.
If SysML turns out anything like Object Oriented Code, the documentation generated will be nearly indecipherable and scattered willy nilly so that putting it into an understandable description of what the system does will take longer than the design required in the first place.
I do appreciate the explanation however, it is well presented. I just fail to see the utility in SysML other than placating the needs of OO programmers. It certainly doesn't do much to help understand what a system is actually supposed to be doing as far as I can see.
Low Talker