Same, I was taught a more basic level use case diagram in class and even that was barely explained well, i'm so thankful this video exists, it's soo much better and concise
oh my god I'm trying to understand this damn concept for 3 weeks now in university and you explained it better in a 12 minute video. god bless u really thanks and bravo for the great job
This video is literally the best, after watching numerous videos without understanding much, this 12 minute video covered everything!! Thank you so much!
you can be good at some thing but may not be a good teach. all these other videos confused me even more than i was before and you explained everything in a fraction of a time they did and 1000% better. thank you
My self Animesh Thakur here is the summary of the video 01:37 A system in a use case diagram is represented by a rectangle and defines the scope of the application or process being developed. 02:31 Actors, depicted by stick figures, represent individuals, organizations, or systems interacting with the developed system to achieve specific goals. 04:02 Use cases, represented by ovals, describe actions or tasks performed within the system and should be descriptive and logically ordered. 05:35 Relationships in use case diagrams, such as associations, depict interactions between actors and use cases to achieve system goals. 06:39 Include relationships demonstrate dependency between a base use case and an included use case, executed every time the base use case is executed. 08:45 Extend relationships allow for optional behavior extension of a base use case, happening only under certain conditions. 10:43 Generalization relationships, or inheritance, illustrate common behaviors shared by a parent use case and specialized behaviors of child use cases. 11:46 Extension points in use cases offer detailed versions of extend relationships, providing options for branching behavior within the system.
I believe "Pay from checking" and "Pay from savings" are extensions of the "Make payment" use case. Also, "Display login error" is an extension of "Verify password" use case.
Listened to a 2hr lecture and didn't understand a thing, and then one of my friends sent me this video. The funny thing is that the lecturer who taught us used the same exact example and the same exact diagram. which means she watched this but still failed to explain this 12-minute video in 2 hours.
I prefer the last version of this video which had a female instructor, it was short and concise. I don't mean to undermine this instructor's ability in anyway though
Quick question: shouldn't the "Verify sufficient funds" relationship involve the "Bank" actor as well? Or is it unnecessary because the bank is already interacting with both "Transfer funds" and "Make payment" through an include relationship?
The include and exclude part is where i fail to understand this video. Isn't the use case like check balance should be behind include of login? what i understand is that if you don't login, then you cannot check balance since login use case has to be met first. another thing that i'm still confused is what would the diagram look like if the actor has 2 roles, as primary and secondary actor? yes a bank might 'react' to customer use case, but what if the bank wants to do somethin within the app that doesn't involve customer? say, make a report of money that cashed out? Would love to hear the explanation with different use case, since if i recall this is a "remaster" version of another UML use case diagrams video from you guys, thank you!
use case diagrams are about what to do rather than how to do. user can login, check balance, transfer funds. these are the things that user can do. but how to check balance? you have to login first. that is what you are saying. your idea can represent better in a sequence diagram not in an use case diagram. hope this helps. if i am wrong please do correct me.
Good video for starters. However, i feel that "display login error" could be emiited, since for any transaction, you will have a database call, a network call which can fail for all functionalities (transfer funds, make payment, etc)
This single video did more for me than an entire paid class.. good job!
Nah i see no memes here
true. very good video and explanation, and straight to the point.
Same, I was taught a more basic level use case diagram in class and even that was barely explained well, i'm so thankful this video exists, it's soo much better and concise
exactly
this guy explained things in 12 minutes that my professor could not explain in 4 hours
best leture on use-case diagrams on the whole youtube. went through 4 other videos but none explained as well as this one. great job.
Nah i see no memes here
oh my god I'm trying to understand this damn concept for 3 weeks now in university and you explained it better in a 12 minute video. god bless u really thanks and bravo for the great job
same!! how can they explain things SO WELL and make it SO EASY while my class does the exact opposite!!!!!!!!
This video is literally the best, after watching numerous videos without understanding much, this 12 minute video covered everything!! Thank you so much!
Thanks! My teacher didn't care enough to actually teach us this so this is perfect.
I watched three videos from my online classes but did not understand a thing. This small video got my confidence back in me. Thank you.
This was the best video I've seen about Use Case diagram, it's a shame that it has so few views.
Sneeze with open eyes to escape the matrix
Mm w
Translation: sneeze with open eyes to die!😂
Wow
the best video on this topic understood include exclude and generalization in a minute loved that sneeze example a lot.
I have been watching vidoes for 2 hours but this was the only video I needed
dude is the best lecturer one should have he explain it better than my lecturer who's been with me for the past 4 months
Excellent explanation. Thank you. Something even Professor at a prestigious university in DC, USA could not do.
Video saved my life in my software development class. 10/10
Thank you so much. Been struggling with these relationships in use case diagrams.The sneeze close eyes.....analogy got me cracking up though😂😂🤣🤣
The best video on use case diagram. Thank you so much.
Thank you for the easy to understand Use Case example. This clarified many questions I had.
Top quality and outstanding explanation !!! You are a great teacher
Thanks a lot, this video helps me with my homework.
If you are from Mexico and study software, this video help you to create diagram's in UML.
I understood this better than how i was taught in class. Thank you so much😊
simplicity personified! nice delivery coach
Thanks alot this video is better than the course i pay for at the university
gosh this video was much more helpful than my 2,000 euros class. thank you guys so much for this!! aamazingggggg
Clear and straight to the point. Real nice video 👍
Excellently explained. This is a masterpiece.
Impressive. Easy to understand, good explanations, I also like your talking-skill. Well done !
Thank you very much, I have an exam tomorrow, and this just saved me😭🙌
this is one of the best video in all use case diagram videos in youtube thanks
man this video is a recap of a whole course
should have watched this 10 minute clip instead of 3 hours lectures . God bless you!!!!!
you can be good at some thing but may not be a good teach. all these other videos confused me even more than i was before and you explained everything in a fraction of a time they did and 1000% better.
thank you
Thanks Collin! This was wonderfully presented.
Makes learning fun.
simplified, concise and very well explained
Love, Peace and Thanks from South Africa
My self Animesh Thakur here is the summary of the video
01:37 A system in a use case diagram is represented by a rectangle and defines the scope of the application or process being developed.
02:31 Actors, depicted by stick figures, represent individuals, organizations, or systems interacting with the developed system to achieve specific goals.
04:02 Use cases, represented by ovals, describe actions or tasks performed within the system and should be descriptive and logically ordered.
05:35 Relationships in use case diagrams, such as associations, depict interactions between actors and use cases to achieve system goals.
06:39 Include relationships demonstrate dependency between a base use case and an included use case, executed every time the base use case is executed.
08:45 Extend relationships allow for optional behavior extension of a base use case, happening only under certain conditions.
10:43 Generalization relationships, or inheritance, illustrate common behaviors shared by a parent use case and specialized behaviors of child use cases.
11:46 Extension points in use cases offer detailed versions of extend relationships, providing options for branching behavior within the system.
Thanks for such awesome explanation of use case diagrams
I believe "Pay from checking" and "Pay from savings" are extensions of the "Make payment" use case. Also, "Display login error" is an extension of "Verify password" use case.
Very good explanation.
This an ownsome explanation. I cannot thank you enough.
Best explanarion I came across about UML diagrams
This is a very great explanation! Thumbs up
Crisp and clear. Just what I need.
best video for understanding basic of use case
You are the best I sleep in this course
WHat an incredible video! This made this sooooo much more simple!
thank you for the informative video! i appreciate the effort and enjoy watching this video
Amazing explanation
Better than a 2 hour class
Thankyou soo much,,,,,i really benefited from your video
thank you for great presentation - I've learned every details of it.
Very nicely explained. Loved it ❤
Thankyou for teaching cristal clear like this. One of the best teachers😊😊😊
it was so helpful and I want to learn from you... thanks
Help full Thanks from India...!
thanks from INDIA💖💖
This was such a great video.
Thanks a lot for the clear explanations💜
Very lucidly" explained Thank you 😊
this is the single video explain uml with simple way
wow that was impressive
great explanation
well explained! thanks for the vid, looking for more of it
Listened to a 2hr lecture and didn't understand a thing, and then one of my friends sent me this video. The funny thing is that the lecturer who taught us used the same exact example and the same exact diagram. which means she watched this but still failed to explain this 12-minute video in 2 hours.
Thank you so much
You made it easy for me.
Thank you so much
merci beaucoup for such a comprehensive content👍🤛
is there any relationship with login for all other options like check balance, transfer funds etc
I also wanted to ask that question
amazing explanation
I liked the older videos ):
It video was great , good job done sir
You are the best
Great explanation. Thanks.
Thanks so much
you are a good teacher
May God Bless You
Greatly explained 🙂
This Video is the BEST!!!!
so clear and understandable
You are the best ❤
great explanation
what happaned to the older use case diagram video?
Huh I'm not the only one who noticed it
@@marosmincak5754 maybe there was something wrong with the last one and they delete it
They unlisted it because they made an updated video. If you have the link to the original video you can still watch it
I am also looking for it
That is so much better
I prefer the last version of this video which had a female instructor, it was short and concise. I don't mean to undermine this instructor's ability in anyway though
I agreeeeeeeeeeeee with you , where is she's video?
@@mosaad7885 dont know why they took it down. But I have it on my PC
Quick question: shouldn't the "Verify sufficient funds" relationship involve the "Bank" actor as well? Or is it unnecessary because the bank is already interacting with both "Transfer funds" and "Make payment" through an include relationship?
The include and exclude part is where i fail to understand this video.
Isn't the use case like check balance should be behind include of login? what i understand is that if you don't login, then you cannot check balance since login use case has to be met first.
another thing that i'm still confused is what would the diagram look like if the actor has 2 roles, as primary and secondary actor? yes a bank might 'react' to customer use case, but what if the bank wants to do somethin within the app that doesn't involve customer? say, make a report of money that cashed out? Would love to hear the explanation with different use case, since if i recall this is a "remaster" version of another UML use case diagrams video from you guys, thank you!
use case diagrams are about what to do rather than how to do. user can login, check balance, transfer funds. these are the things that user can do. but how to check balance? you have to login first. that is what you are saying. your idea can represent better in a sequence diagram not in an use case diagram. hope this helps. if i am wrong please do correct me.
thank you ,best explanation
great vid on use case definitely helpfull
Good video for starters. However, i feel that "display login error" could be emiited, since for any transaction, you will have a database call, a network call which can fail for all functionalities (transfer funds, make payment, etc)
Thank you for making this video.
great tutorial , thanks
Perfect explanation 😄 thanks a lot!
Well done.
I'v watched the older version of this video so many times that I can still hear the lady's voice in my head 😂.
from TZ that was so awesome THANK YOU.
Great video.
Give this man a Bells
Thanks dude helped a lot
thank you!! the examples were so good:)
Crazy helpful bro
Good explaination 🤩
Very helpful thank you
easy to understand. Thank you
Thank you so much 🎉
Thank you so much
thanks a lot it is a masterpiece