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!
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.
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.
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
Me han descontado la suma de 95.40 sin mi previa autorización, me han cargado un plan anual qué yo nunca elegí, necesito que se me regrese de manera inmediata mi dinero, es muy decepcionante lo ocurrido con una empresa de tanto prestigio como esta, con otras esto no pasa.
I'm not 100% sure but I believe its because an include use case is not a base use case so you cannot extend it, even if displaying the error stems from verifying if the password is valid/invalid.
Hi everybody. As I understand it, a usecase is the behavior of an actor using an app, so the usecase to show errors or verify passwords don't seem to come from the user's behavior but from the app side, right? Instead, the log in usecase could be extend changing the password, or something the customer actively does... I don't understand clearly, so I'll just say my thoughts. I hope everyone can help me answer it. Thank you
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)
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.
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
I don't think something like 'Display Login error' is actually a use case, also not as an extend. Also there is hardly a reason for a use case 'Verify password'; it's just a step in the Login use case scenario. Unless the 'Verify password' functionality would be useful as an include in other use cases (can't think of any right now, and they are not in the diagram).
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
Sneeze with open eyes to escape the matrix
Mm w
Translation: sneeze with open eyes to die!😂
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
This video is literally the best, after watching numerous videos without understanding much, this 12 minute video covered everything!! Thank you so much!
is there any relationship with login for all other options like check balance, transfer funds etc
I also wanted to ask that question
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
This was the best video I've seen about Use Case diagram, it's a shame that it has so few views.
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.
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.
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.
Give us memes i want more cheesy boy's raps
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
Me han descontado la suma de 95.40 sin mi previa autorización, me han cargado un plan anual qué yo nunca elegí, necesito que se me regrese de manera inmediata mi dinero, es muy decepcionante lo ocurrido con una empresa de tanto prestigio como esta, con otras esto no pasa.
I have been watching vidoes for 2 hours but this was the only video I needed
Amazing explanation, but
I have one question.
Why didn't the verify password extends Display login error.
If anyone knows please reply
I'm not 100% sure but I believe its because an include use case is not a base use case so you cannot extend it, even if displaying the error stems from verifying if the password is valid/invalid.
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.
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
Very good explanation.
Thanks alot this video is better than the course i pay for at the university
Every sneeze say "Thank God" not say "Excuse me"
Which god exactly 🤨
Hi everybody.
As I understand it, a usecase is the behavior of an actor using an app, so the usecase to show errors or verify passwords don't seem to come from the user's behavior but from the app side, right? Instead, the log in usecase could be extend changing the password, or something the customer actively does...
I don't understand clearly, so I'll just say my thoughts. I hope everyone can help me answer it. Thank you
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)
Thankyou soo much,,,,,i really benefited from your video
Where is the Khloe's use case video?
Why isn’t verify password, display error and verify sufficient funds associated with the bank?
I liked the older videos ):
الله لا تربحك رمضان يا رمضان و حنا نخدمو فالدوفوار بسبتك 😭😭🤦🏼♀️
Jones Elizabeth Robinson Betty Young Charles
What is the background music ASAP needed to lock in
This is a very great explanation! Thumbs up
This isn't complete use case at most right? Like other offers and services
Please do more of the commercials !! Please oh please please please
This was such a great video.
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
Lopez George Smith Lisa Anderson Jessica
pls what's the using constraints different from using conditions
Better than a 2 hour class
When do I choose to use a short use case explanation instead of a detailed one, as a software developer?
from TZ that was so awesome THANK YOU.
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.
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
Does sign up process isn't really included?
Love, Peace and Thanks from South Africa
Thank you so much
I don't think something like 'Display Login error' is actually a use case, also not as an extend. Also there is hardly a reason for a use case 'Verify password'; it's just a step in the Login use case scenario. Unless the 'Verify password' functionality would be useful as an include in other use cases (can't think of any right now, and they are not in the diagram).
Thank you so much 🎉
does the extend always happen after the said use case? 9:48
I hate the fact that I am watching this 😭😭
cool video tho
Impressive. Easy to understand, good explanations, I also like your talking-skill. Well done !
COMSATS wale hazri lagvao 😂
Thankyou for the reference :)
where can I find his insta? Asking for a friend haha
should change the actor bank to admin
thank you for great presentation - I've learned every details of it.
Thank you for making this video.
Thanks Collin! This was wonderfully presented.
Makes learning fun.
thanks from INDIA💖💖
Best explanarion I came across about UML diagrams
Video saved my life in my software development class. 10/10
Thank you very much, I have an exam tomorrow, and this just saved me😭🙌
YOU THE BOSS
Thank you very much.
well explained! thanks for the vid, looking for more of it
I'v watched the older version of this video so many times that I can still hear the lady's voice in my head 😂.
thanks
Thank u so much
This an ownsome explanation. I cannot thank you enough.
Very lucidly" explained Thank you 😊
May God Bless You
it was so helpful and I want to learn from you... thanks
greatttttt
amazing explanation
I understood this better than how i was taught in class. Thank you so much😊
Thank you so much
You made it easy for me.
Thank you so much
good video man 10/10
Kling Mission
Thanks for such awesome explanation of use case diagrams
my guy....thank you
i cant find the actor icon
best best best best
Celine Divide
Help full Thanks from India...!
THANK YOU
Harris Flats
Great video.
Well done.
9:24 *hachoo* 👁️👄👁️
What app is this?
best analogy
great vid on use case definitely helpfull
Thanks so much
you are a good teacher
this is the single video explain uml with simple way
Good explaination 🤩
Thank you
Crisp and clear. Just what I need.
merci beaucoup for such a comprehensive content👍🤛
Thanks
HOLA, ME GUSTO UR UTUB