The 'life cycle' of a part object is so important key to explain the difference between aggregation and composition. A lot of tutorials just don't mention this. Thanks for making this tutorial.
Thank you for the beautiful lesson, Margret. Everything relevant, and no weak filler! We have to dig through a lot of dirt to get to the gold-thank you for being the gold! :D
Awesome video tutorial ! you have some unique talent, I generally dont add comments but this video was just too good, Simple videos are so difficult to make !
Unary Associations and Attributes are the same thing. And I hit Like! Really so many times I've seen people saying similar things without telling the exact difference or mentioning that they are same thing with different approaches. Thanks for Saying it straight forward, it isn't hard to say something that it is.
In the house example, is it wrong to say that Mortgage is a composition with House? Can mortgage exist without a house? Or is it that we don't put composition when working with multiplicity?
Hi Margret, regarding the last example, can you explain why there exists a Binary relationship between House and Mortgage? Shouldn't that be a directed line pointing from House to Mortgage?
The idea here is that the house knows about the mortgage, and the mortgage knows about the house. (A mortgage document includes not only information about the mortgage rate, etc. but also the address of the house.)
Very useful and helpful thank you! But could the Mortgage class also be composite to the House Class because without the House Class there would never be a mortgage ?
Are you positive that the only difference between Aggregation and Composition is lifetime of part dependant on lifetime of a whole? How about following difference: In aggregation a part can be part of many different wholes. In composition a part is exclusivly of one whole. Is this statement false or you just forgot to mention that?
Great video.. I see that aggregation and composition differ from association, but it's a little abstract in that I can't see how it changes the ultimate implementation when you're making the distinction between association and aggregation where both have a minimum of 0, max of 1. (Mortgage vs Mailbox) - e.g I think I'd implement them both similarly just going off the diagram, so why bother make the distinction? Bit of a rhetorical question to myself that I will answer eventually :)
The 'life cycle' of a part object is so important key to explain the difference between aggregation and composition. A lot of tutorials just don't mention this. Thanks for making this tutorial.
That example sums up everything I had been trying to understand since last 2 years XD
Super thanks for the video.
Simple, clear, and direct...2 semesters of confusion cleared in
Learned more in 9 minutes than from reading 90 pages of my boring UML textbook. Thank you.
same here
Short, to the point, accurate and clear - one of the best short tutorials that I've seen. Thank you
Thank you for the beautiful lesson, Margret. Everything relevant, and no weak filler! We have to dig through a lot of dirt to get to the gold-thank you for being the gold! :D
Really good video, great explanations. Thanks
Thank you for such a great video like this! Your explanations are straightforward and easy to understand. Thumbs up!
Very well explained. Thank you.
The house example in the end of video is awesome!! easy to understand different associations and the multiplicity!! Thanks a lot!!
Thank you so much for such a good video. I really was helpful. Look forward to more videos!
Simple and easy explained! Thank you!
The best I had seen out of the clutters. Thanks!
Really very easy explanation with real life examples!
It would be great if you organise playlists. thank-you so much!
Thanks a lot, you are the first i found that explained this in a very easy way, thanks
the first video which explain those stuff in a good manner
One semester illustrated nicely in 10 minutes. That was greatly explained. Thank you.
Your way of teaching is simply awesome..
Awesome video tutorial ! you have some unique talent, I generally dont add comments but this video was just too good, Simple videos are so difficult to make !
Such a great explanation. We need more teachers like you. Thank you very much.
This video was just perfect, really great explanation
Unary Associations and Attributes are the same thing. And I hit Like! Really so many times I've seen people saying similar things without telling the exact difference or mentioning that they are same thing with different approaches. Thanks for Saying it straight forward, it isn't hard to say something that it is.
This was great. I didn't know that a unary association == the attribute(s) of a class. That cleared up a lot of confusion for me. Thank you
well done lady. ive understood everything
very good explanation..tomorrow is my ooad exam and watches this video give me a hope to pass the exam. thank you mam
You are the best teacher available. Can you please provide new videos on Mockito?
Thankyou for this video, really helped me understand the relationships in an uml :)
Pulvii vídeo por nos
VERY VERY EXPLAINED
just subbed looking forward to learn java from you
finally a very crystal clear video.
I really liked the last example of the house, good explained
very nicely explained mam, keep it up 👌👌👌🙂🙂🙂🙂
very well explained. I am subscribing to your channel for this. Nice!
Good explanation, thanks! One question: sometimes the arrow that goes from class to class is dashed (or dotted?). What does it mean?
this 9 minute video is way better than my teacher explaining the same thing for 2 hours.
This was so helpful and straight to the point. Thank you
Not exactly the level of difficulty I have wanted, but it is good that are videos where are presented more difficult concepts about class diagrams.
Very helpful and extremely well explained. Thank you very much!
Really very Simply you explained it 😍😍
Nice examples. Well presented. Thanks
Best explanation I got for this topic by far, Thanks
Explained very nicely. really useful. Thank you Margret
Excellent explanation!!!
Your explanation is just wonderful!!!!Thank u mam......
Will be using this for your class.
This video is really helpful! Many thanks madam! Recomended for newbie!
dang! You are so darn good and awesome!! Thank you very much Madame Posch!!
Perfect examples thanks my lady
Very good introduction. I show it to my students
Wow, mam u r awesome, hope study one day live with u
THANKS. Great explanation!
very well explained. A beginner can take it easily. Thanks
Very best explanation. Thank you
This makes everything so so clear, thank you!
In the house example, is it wrong to say that Mortgage is a composition with House? Can mortgage exist without a house? Or is it that we don't put composition when working with multiplicity?
This helped so much with Assignment 6! thanks :)
you just made my day. thanks
Thank you so much. It is easy, simple, direct and clear.
thank you for the explanation, very helpful in understanding uml class diagrams
Very nicely explained 👍
Great content! Thank you so much
Great video. Definitely helped with my understanding. Thanks
a great explanation. simple and clear.. thank you.
best tutorial about class diagrams
Hi Margret, regarding the last example, can you explain why there exists a Binary relationship between House and Mortgage? Shouldn't that be a directed line pointing from House to Mortgage?
The idea here is that the house knows about the mortgage, and the mortgage knows about the house. (A mortgage document includes not only information about the mortgage rate, etc. but also the address of the house.)
@@margretposch4827 Thanks for the clarification. Great vid!
If I could like this video 1000 times, I would
Wonderful Explanation ThankYou Madem
Really your video is very helpful
Thank you for these examples they really help :)
Awesome explanation! Thank you so much!
simply explained..thank you very much..
Really Great video.Thank you
Thank you mam! This was a really great video. :)
Rian Zaman
Why are there no arrows in the last diagram to denote 'has a' Association ?
i like this explanation, cause easy to undestand
Pramanca Utama Manca
Thank you very clear explanations and I love your accent!!
simply explained everything very nicely
thanks alot ! its very easy to understand ! nice work :) :)
Such a good explanation. Thanks for sharing :D
can you explain me too ???
Thank you very much. Yes nice explanation.
Very useful and helpful thank you! But could the Mortgage class also be composite to the House Class because without the House Class there would never be a mortgage ?
Mortgage isn't part of the house so it cant be a whole part relationship (aggregation or composition). This is how I understood it.
THANK YOU!!!!!! This was perfect
thanks for this simple and wonderful explanation!
First time i see the attribute vs relationship role use explained properly
explained with good examples.
its very helpful videos god bless you
wow amazing explanation
great explanations. Thanks
Can we get the slide? Nice job!
Thanks.
Very Well-ExplainedThank you
great explanation 👏
Thank you a lot, Miss!
Tnxxxxx, You Made It Simple Than Ever...
perfect explanation...Thank you.
amazingly explained!
Excellent explained
i have a doubt unary association is entities of same type and binary association is entities of 2 different class
Very helpful ,thank you.
Hi, thank you so much, a very good explanation!
But may you give us your book references which related to your presentation?
Are you positive that the only difference between Aggregation and Composition is
lifetime of part dependant on lifetime of a whole?
How about following difference:
In aggregation a part can be part of many different wholes.
In composition a part is exclusivly of one whole.
Is this statement false or you just forgot to mention that?
Great video.. I see that aggregation and composition differ from association, but it's a little abstract in that I can't see how it changes the ultimate implementation when you're making the distinction between association and aggregation where both have a minimum of 0, max of 1. (Mortgage vs Mailbox) - e.g I think I'd implement them both similarly just going off the diagram, so why bother make the distinction? Bit of a rhetorical question to myself that I will answer eventually :)