According to researches by the adsmember team
इस ट्यूटोरियल में यूज़ केस डायग्राम बनाना सीखें। दोनों शुरुआती और मध्यवर्ती यूएमएल डायग्रामर सिस्टम, अभिनेताओं, मामलों का उपयोग करने और संबंधों को शामिल करने और बढ़ाने पर सभी आवश्यक प्रशिक्षण और उदाहरण पाएंगे। यूएमएल यूज केस डायग्राम एक सिस्टम या एप्लिकेशन दिखाते हैं; फिर वे लोगों, संगठनों, या अन्य प्रणालियों को दिखाते हैं जो इसके साथ सहभागिता करते हैं; और अंत में, वे एक बुनियादी प्रवाह दिखाते हैं कि सिस्टम या एप्लिकेशन क्या करता है। यह ट्यूटोरियल यूज़ केस डायग्राम की चार मुख्य विशेषताओं की व्याख्या करता है: सिस्टम, अभिनेता, उपयोग के मामले और संबंध। एक प्रणाली वह है जो आप विकसित कर रहे हैं। यह एक वेबसाइट, एक सॉफ्टवेयर घटक, एक व्यावसायिक प्रक्रिया, एक ऐप या कई अन्य चीजें हो सकती हैं। आप एक आयत के साथ एक प्रणाली का प्रतिनिधित्व करते हैं। यूज़ केस डायग्राम का अगला पहलू अभिनेता हैं। एक अभिनेता कोई व्यक्ति या कुछ ऐसा होने जा रहा है जो किसी लक्ष्य को प्राप्त करने के लिए हमारे सिस्टम का उपयोग करता है, और उन्हें एक छड़ी की आकृति द्वारा दर्शाया जाता है। उपयोग के मामले ऐसे तत्व हैं जो वास्तव में यह वर्णन करना शुरू करते हैं कि सिस्टम क्या करता है। उन्हें अंडाकार आकार के साथ चित्रित किया गया है और वे एक ऐसी क्रिया का प्रतिनिधित्व करते हैं जो सिस्टम के भीतर किसी प्रकार का कार्य पूरा करती है। यूज़ केस डायग्राम में अंतिम तत्व संबंध हैं, जो दिखाते हैं कि अभिनेता और उपयोग के मामले एक दूसरे के साथ कैसे इंटरैक्ट करते हैं। विभिन्न प्रकार के संबंध हैं (जैसे संबद्धता, शामिल, विस्तार और सामान्यीकरण) जो विभिन्न प्रकार की रेखाओं और तीरों द्वारा दर्शाए जाते हैं। —— अधिक जानें और साइन अप करें:
लिंक्डइन:
source
👍
thank you because our teacher doesn't teach
11 Hours for my end term exam. You guys are saving me from failing. Thanks a lot!!!!!!!
very very helpful
Great work, thank you so much. Super clean explanation.
There may be an error with the diagram. Check Balance, Transfer Funds and Make Payment <<include>> Login right?
for checking balance and return funds , shouldn't we put include to login , because ech time we want to check balance we need to be logged in
best video on use case n use case diagram
Is there a playlist for all diagrams?
grasias
The only thing I'd add to great presentation is that your application being "Banking App" should be safe to say that it's owned by the bank, and so all actions happen within the banks infrastructure.
With that said the actor wouldn't be "Bank" it would "Time". Time being an actor used to set off an automated task any time it is scheduled or called upon.
If someone checks the Balance in an app the user for the bank will be Time. This is because system processes are waiting to be called, or are scheduled to be called.
I'm not sure what others think about this, and I don't actually think having an actor of "Bank" is incorrect per se, I've just never written like such!
Obviously the difference would be if you added in a "Request Support" use case from the customer then you would have a "Customer Support" actor on the opposite side, who would have a use case of something like.. "Manage Support".
If you use "Bank" then what is that actually signifying? Someone at the bank? Automated bank process? It's a bit ambiguous I think.
thanks so much ✨
🤩🤩🤩
I feel like I just got an engineering degree for free
Thank you I had a lecturer who couldn't bother with us most of the semester and didn't even show us a single use case diagram on the white board and guess what the exam is gonna have questions from 100% of the curriculum but we have knowledge gaps with the way our lecturer teaches I am very disappointed and I am very thankful that you and others are giving us this information for free!
Can someone explain why the bank cannot interact with the login? Aren't they provide the details if the user successfully log-on with correct credentials??
I think display login error and verify password is not a use case. It's a step within a use case. We can explain those steps on activity diagram or sequence diagram. Unless there are some steps to display login error maybe it would make sense to make it as a use case
Thank you for the course. It is really interesting what you have taught. However, it should be noted that for small applications (like the example taken), it is very easy to structure the use case diagram. What about structuring large applications with up to 50 use cases?
v pretty
This was absolutely, 1000% helpful! Thank you, thank you, THANK YOU!!!!
love from Bangladesh
where can I download the UML software? the lucid chart in the website looks different from the video.
no you are wrong, "Sneeze" does not include "Close eyes", becasue when i sneeze, I open my eyes to assert dominance.
I paid 5k to learn , I could have just watched YouTube
متشكرين يمزه
Excellent tutorial , and it's very helpful.
Demmmm🔥🔥
Very good video!!
A 4 year YT video still useful, tnx very much😍
Amazing video
Thank you very much!
This was so helpful! Thank you!
Did Lucidchard remove actors for free plan? I can't see the person shape.
Ich liebe Sie.
Excellent explanation 👍
Mam, you are so beautiful!
thank you so much
I love this video
one of the best tutorial I haver seen. Thank you a lot
great lesson, thanks!
Chloe for president!!!!
Nice video. Thank you so much. Grateful to you:)
Thanks Mrs. I really like how to explained the "<< include >>" and "<< extends >>"
Merci ! Domingo n'étais pas capable de l'expliquer aussi clairement
That was an incredible presentation! Thank you…
🏃🏃🏃🏃🏋️🏋️💡💡🌅🌄🌄🌄👠👠👠👠👠🏋️👠👠👠👠🤱🙏🙏🙏