UML use case diagrams

Learn how to make Use Case Diagrams in this tutorial. Both beginners and intermediate UML diagrammers will find all the necessary training and examples on systems, actors, use cases, and include and extend relationships.
UML Use Case Diagrams show a system or application; then they show the people, organizations, or other systems that interact with it; and finally, they show a basic flow of what the system or application does.
This tutorial explains the four main characteristics of Use Case Diagrams: systems, actors, use cases, and relationships.
A system is whatever you’re developing. It could be a website, a software component, a business process, an app, or any number of other things. You represent a system with a rectangle.
The next aspect of Use Case Diagrams are actors. An actor is going to be someone or something that uses our system to achieve a goal, and they're represented by a stick figure.
Use Cases are elements that really start to describe what the system does. They're depicted with an oval shape and they represent an action that accomplishes some sort of task within the system.
The final element in Use Case Diagrams are relationships, which show how actors and use cases interact with each other. There are different types of relationships (like association, include, extend, and generalization) that are represented by varying types of lines and arrows.
--
00:00 Introduction
00:20 Overview
01:01 Lucidchart - Free Diagramming Software
01:37 Systems
02:08 Actors
03:06 Primary and Secondary Actors
03:57 Use Cases
05:06 Relationships Overview
05:19 Association Relationships
07:17 Include Relationships
08:21 Extend Relationships
09:18 Include and Extend Relationships
10:14 Generalization Relationships
11:49 Conclusion
--
Learn more at: training.lucid.co
Sign up at: www.lucidchart.com
Follow us:
Facebook: / lucidsoftware
Twitter: / lucidsoftware
Instagram: / lucidsoftware
LinkedIn: / luci. .

[@davidalejandrodelosreyesos146]

This single video did more for me than an entire paid class.. good job!

[@-.-K._.]

Nah i see no memes here

[@karimkarroum2198]

true. very good video and explanation, and straight to the point.

[@rlfpotatoking9253]

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

[@anandcp1]

exactly

[@vaiebhavpatil2340]

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.

[@-.-K._.]

Nah i see no memes here

[@christaehrstein]

Thank you for the easy to understand Use Case example. This clarified many questions I had.

[@maraki_zrg]

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

[@tanyap7401]

This video is literally the best, after watching numerous videos without understanding much, this 12 minute video covered everything!! Thank you so much!

[@ezeozokam5002]

I understood this better than how i was taught in class. Thank you so much😊

[@dolunay-]

I have been watching vidoes for 2 hours but this was the only video I needed

[@sofonsteigernduwayezu2427]

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

[@taha5539]

This was the best video I've seen about Use Case diagram, it's a shame that it has so few views.

[@olabisibabayemi]

simplicity personified! nice delivery coach

[@abhijitkumbhar1]

Best explanarion I came across about UML diagrams

[@zubaerahammed]

Excellently explained. This is a masterpiece.

[@user-ii7pb3yv3y]

Love, Peace and Thanks from South Africa

[@nethmihimalsha965]

Thankyou for teaching cristal clear like this. One of the best teachers😊😊😊

[@tayyabsami258]

Thanks alot this video is better than the course i pay for at the university

[@StepPanda3K]

Thank you very much, I have an exam tomorrow, and this just saved me😭🙌

[@neerajshrivastava5600]

Top quality and outstanding explanation !!! You are a great teacher

[@momtoube743]

Thanks so much
you are a good teacher

[@madiegeorgiana1208]

thank you!! the examples were so good:)

[@malakmalak4830]

Perfect explanation 😄 thanks a lot!

[@dinushachathuranga7657]

Thanks a lot for the clear explanations💜

[@divkairawan1424]

This is a very great explanation! Thumbs up

[@Sylvia-ly4wj]

simplified, concise and very well explained

[@nipunajith]

Great explanation. Thanks.

[@reason7895]

This Video is the BEST!!!!

[@shreyasawankar7601]

Help full Thanks from India...!

[@nikanoran.n.c8401]

Thankyou soo much,,,,,i really benefited from your video

[@surendernegi3154]

Thanks for such awesome explanation of use case diagrams

[@yusufnzm]

This was such a great video.

[@user-su4yz5om5w]

best video for understanding basic of use case

[@nicka3203]

Very good explanation.

[@andy-moggo]

so clear and understandable

[@levanuc7906]

Better than a 2 hour class

[@VisualVibesGallery3820]

Thank you for making this video.

[@rachaelezugwu3678]

Thank you so much
You made it easy for me.
Thank you so much

[@romanulhaq_asrar]

this is one of the best video in all use case diagram videos in youtube thanks

[@mirika_a_ziela4184]

You are the best ❤

[@achmadsyarif5129]

thank you ,best explanation

[@MohamadModather99]

Thank you very much!!

[@himashaerandana3432]

Thanks dude helped a lot

[@HadiEbrahimi-yq9yj]

it was so helpful and I want to learn from you... thanks

[@YBIG05]

merci beaucoup for such a comprehensive content👍🤛

[@abdallahgasem628]

great tutorial , thanks

[@Subayin]

thanks a lot it is a masterpiece

[@faizunnur4456]

Thank you very much.

[@mvuyisimtwa9224]

Thank you so much 🎉

[@beko4733]

good job !
its very helpful for me

[@captainduki]

easy to understand. Thank you

[@zohaibsameer1998]

Greatly explained 🙂

[@candidate3512]

Very helpful thank you

[@mss7807]

wow that was impressive
great explanation

[@muhammadsamy7740]

that's so perfect thanks alot

[@thanhduongphan315]

Good explaination 🤩

[@OlwethuMkhize922]

Give this man a Bells

[@code_spot]

very useful thanks.

[@MercyDedeFoli]

It video was great , good job done sir

[@Heshi540]

Thank you so much

[@CuteKittens23]

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

[@impe-ri-vous9089]

Crazy helpful bro

[@anonymousz7205]

great vid on use case definitely helpfull

[@dhavalkalaria5384]

Thankyou for the reference :)

[@MartinFaehrmann]

Thank you so much 👌

[@3Dprintingshorts]

Thanks a lot 🙏

[@venom2390]

Thank you ❤️

[@alikograce.5520]

great explanation

[@Mr_Zimm]

Great video.

[@yasminejas5007]

thank you so much!

[@gauthamkrishnan5948]

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.

[@HaadiAnwary]

good video man 10/10

[@ines9226]

Thank u so much

[@leartbajrami3589]

amazing explanation

[@lemannsz]

Thank youuuuuuuuu really help

[@Malhiza_MamBhele]

YOU THE BOSS

[@user-sq1qu5tv5h]

this video amazingggg

[@kavindagihan]

Fantastic🎉

[@achmadsyarif5129]

best analogy

[@EduardoMengesMattje]

ótimo vídeo

[@yacine5046]

this is the single video explain uml with simple way

[@frankdaniel49]

Sneeze with open eyes to escape the matrix

[@marymwabili9044]

Mm w

[@0xmkay]

I'v watched the older version of this video so many times that I can still hear the lady's voice in my head 😂.

[@radouane5376]

Thanks

[@user-em9xp3tw7t]

is there any relationship with login for all other options like check balance, transfer funds etc

[@EthanHunt-fg5sk]

I also wanted to ask that question

[@thainoodleboii]

thanks

[@ThabisoNgwane]

asombrosa

[@NAGM_CODE]

Every sneeze say "Thank God" not say "Excuse me"

[@ranasameh2086]

good job

[@acepilot4196]

what happaned to the older use case diagram video?

[@marosmincak5754]

Huh I'm not the only one who noticed it

[@acepilot4196]

@@marosmincak5754 maybe there was something wrong with the last one and they delete it

[@devanushjoseph]

They unlisted it because they made an updated video. If you have the link to the original video you can still watch it

[@mifzeena7390]

I am also looking for it

[@gilead1618]

That is so much better

[@bugraozturk275]

Thanksss

[@admildomanuel544]

Great tutorial

[@just_master9034]

No. We need the snek

[@ragnarokk347]

woww!

[@odddellarobbia4]

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!

[@riDdLer20025]

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.

[@ilikerainworld]

I liked the older videos ):

[@dniyan7369]

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.

[@2dsingerofgorillaz907]

Please do more of the commercials !! Please oh please please please

[@user-ef9xs4mk7e]

Amazing explanation, but
I have one question.
Why didn't the verify password extends Display login error.
If anyone knows please reply

[@duckman03]

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.

[@hudahabib-zq2oc]

greatttttt

[@hensleysapom3525]

When do I choose to use a short use case explanation instead of a detailed one, as a software developer?

[@khangvi2936]

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

[@weepingwallflower8017]

does the extend always happen after the said use case? 9:48

[@youssefh.s.8043]

what is the programme that you were using