Very informative. This lecture allowed me to look at UML under different angle and now UML looks to me quite attractive and (what is the most important) *practical* 👍
This was very, very helpful. It looks like I'll have to look for the rest of the video on the OMG website because the full version still hasn't replaced the truncated version here. I see that I'll need more than an overview to start using UML or SysML, anyway. Judging by the terminology used, the audience comprised software folks because definitions of UML terms depended on understanding OOP terms. For example, the section on Class Diagrams used OOP terms to define UML terms. For systems engineers who aren't programmers, the boutique terminology is ambiguous and confusing. The implication that I need to study OOP in order to understand UML and study UML in order to understand SysML is very discouraging.
I see some logic fails, e.g. including UC as a nonworking part, why does the author connect this to the actor? In UML we can read UC model is not an internal structure, why author show internal parts of the code (extends, include)?? and so on...
uml --- the language that has no machine- and human readable text form. no, the xml serialization of uml models is _not_ human-readable... and the specification that is deliberately underspecified and _needs_ specialization (to SysML or AUTOSAR or whathaveyou) --- which in theory are free to redefine everything if they deem it necessary. So to understand one of the derivatives, you need to dig through the UML, then the derivative and then revisit UML again for the fine print. that said, uml has a few very clever concepts, like redefining and splitting attributes on refinement, and partial diagrams, the unification of which gives the complete picture. I think it took a very wrong turn when it thought drawing diagrams was the future of construction and implementation of software systems.
As a student who doesn't yet have any experience in professional software development, I found this lecture inaccessible. If I could better see the slide when the camera is zoomed out, then it might have been slightly easier to grasp. Then again, the benefit of that could well be trivial anyway. Please pardon my frustration. I was assigned this video by my professor and am annoyed to have no idea what he expects me to take away from it.
@ahmedhassan3276 Hello, sure! I estimate that, in the course where I was assigned this video, we students weren't meant to take away anything particularly specific. We subsequently took a small quiz on basic ideas of UML modeling, but not it didn't really test on anything unique to this video, which I consider to be its higher-level commentaries on UML's value in industry. (Btw, I somewhat hazily recall this lecture's content, as it was several months ago that I watched it.) I think our instructor's main intent in assigning us this video was to get us some exposure to the wide of UML diagrams. If I'm being petty, I think I could've skipped watching 80% of the video without any cost to my grade. Hope this is helpful somehow
Very informative.
This lecture allowed me to look at UML under different angle and now UML looks to me quite attractive and (what is the most important) *practical* 👍
for me this is one of the best introductions into UML and SysML -!!
This was very, very helpful. It looks like I'll have to look for the rest of the video on the OMG website because the full version still hasn't replaced the truncated version here. I see that I'll need more than an overview to start using UML or SysML, anyway.
Judging by the terminology used, the audience comprised software folks because definitions of UML terms depended on understanding OOP terms. For example, the section on Class Diagrams used OOP terms to define UML terms. For systems engineers who aren't programmers, the boutique terminology is ambiguous and confusing. The implication that I need to study OOP in order to understand UML and study UML in order to understand SysML is very discouraging.
is there any source that we can reach this slide?
very informative and easy to understand video
I'm trying to sunset quite a large framework, this will be helpful
Спасибо!
Thanks for this.
I see some logic fails, e.g. including UC as a nonworking part, why does the author connect this to the actor? In UML we can read UC model is not an internal structure, why author show internal parts of the code (extends, include)?? and so on...
19:32 Class Diagram: Order Information Model
uml --- the language that has no machine- and human readable text form. no, the xml serialization of uml models is _not_ human-readable...
and the specification that is deliberately underspecified and _needs_ specialization (to SysML or AUTOSAR or whathaveyou) --- which in theory are free to redefine everything if they deem it necessary.
So to understand one of the derivatives, you need to dig through the UML, then the derivative and then revisit UML again for the fine print.
that said, uml has a few very clever concepts, like redefining and splitting attributes on refinement, and partial diagrams, the unification of which gives the complete picture.
I think it took a very wrong turn when it thought drawing diagrams was the future of construction and implementation of software systems.
Any answer on the second part? It is a great introduction to sysml by the way
Let me check into this.
It is abt 5 minutes short. I'll have to delete it and upload it again this week.
You can also watch the full version on the OMG BrightTalk channel at www.omg.org/webinars/index.htm but you have to create a login.
@@ObjectMgmtGroup Is it still available?
Answering to myself: I just checked, it's still online :)
OMG have BPMN for business process modelling, now UML prepares activity diagrams for algorithms (methods) not for business processes...
The video isn't complete. Is the 2nd part provided?
Let me check into this.
It is abt 5 minutes short. I'll have to delete it and upload it again this week.
@@ObjectMgmtGroup thank you so much, it's a good video
You can also watch the full version on the OMG BrightTalk channel at www.omg.org/webinars/index.htm but you have to create a login.
@@francescobenacci6611 Thank you for watching.
Class diagram as a database? Again? Mixing domain model (namespace) with code architecture? Again? Hm...
As a student who doesn't yet have any experience in professional software development, I found this lecture inaccessible.
If I could better see the slide when the camera is zoomed out, then it might have been slightly easier to grasp. Then again, the benefit of that could well be trivial anyway.
Please pardon my frustration. I was assigned this video by my professor and am annoyed to have no idea what he expects me to take away from it.
any thoughts? similar situation here
@ahmedhassan3276 Hello, sure!
I estimate that, in the course where I was assigned this video, we students weren't meant to take away anything particularly specific. We subsequently took a small quiz on basic ideas of UML modeling, but not it didn't really test on anything unique to this video, which I consider to be its higher-level commentaries on UML's value in industry. (Btw, I somewhat hazily recall this lecture's content, as it was several months ago that I watched it.)
I think our instructor's main intent in assigning us this video was to get us some exposure to the wide of UML diagrams.
If I'm being petty, I think I could've skipped watching 80% of the video without any cost to my grade.
Hope this is helpful somehow
Thanks for your time, helpful indeed.
I dig the cringe jokes - too bad the audience was too stuffy to yield to the hilarity.