The topic of the video is explained really well here . All my queries related to this topic are cleared . Thankyou so much for making this video . Lots of love and prayers to you from my side .
Great Work great explanation This channel really deserves more attention!! Thank you again ...please keep it up I have gone through 7 youtube vids trying to understand the UCD... all of them created questions in my mind more than provided Answers however in your vid i got the whole story in one place you save me alot of time and effort and your explanation was really Complete & perfect
sir the videos is very good. i have a question regarding the actors why because u said that we have primary actor and secodary actor. where secondary actor is the person who interacts after primary actor has made an initiation. but here in the example both actors are named as customer. my doubt is primary actor used all the 4 use cases but why again we have on right the same actor using the same use cases twice. i mean actors representation is done twice(right and left)
Great video! I'm a newbie with some questions....so in this use case are we adding features or do we add the user requirements in the high-level use case?
allah gives you alots alots of happiness I have assigned university assignment for use case diagram and I was just in tension the video you explain is seriously mindblowing lots of prays from here lovely
Thank you so much for watching my video. Also view ruclips.net/video/PiRsKDlZeVk/видео.html for more use case diagram clarification. Don't forget to like, share, and subscribe my channel.
sir, please clear my confusion about login and registration usecases. Can we also draw registration as the extended usecase of login? or it will be wrong to do so?
Thank you so much for watching the video and question. Login and Registration are separate use cases. Whenever the base use case is called by the actor, and extended use case may or may not call. If it calls, then it will call from the base use case internally. In the above case. if login fails, it displays an error, it will not call the registration use case. So login extends the error message. Ya, we can show in extension point as option or link but I suggest, best to show these two use cases separately. And these two use cases have their own extend and include use cases as well. Hope you are clear about it now. Don't forget to like, share, and subscribe the channel.
@@Master2Teach Thank you so much sir for such a good explanation. You mean we will draw both the use cases separately. i have one more question which will clear me all the things. Can we generalize the user as new user and registered user and then connect the login usecase with the registered user and Registration usecase with the new user. And all other usecases which are common will be connected with the parent user? As, i have a project of online food ordering system, so can you please explain me this in the context of my project? I will be really thankful Sir.
The functions of the secondary actor can be same or different. For example, if primary actor tries to register (in order to get the course), now secondary actor may want to approve the registration manually . So in order to approve the registration manually the secondary actor will have to access the registration function. So by accessing the registration function secondary actor can get detail and according to that the secondary actor can reject of accept. If the secondary actor wants to perform a function which primary actor can never perform, in this case the different function has to be created.
Thanks for good question. In use case diagram, primary actors are place in left side whereas secondary are in right side usually. In case of system as an actor which perform certain automatic job can be place on right side but note that there is not hard and fast rules.
Thank you for your question. If student enroll in course then there is association between the student and course class. To support these two classes interaction and further information, Enrollment class will help which is known as Association Class. It hangs with dotted line without arrow head in between student and course class. I hope this will help you to understand the association class.
ok this video is good but more give an examples and more focused on diagram sake of i am information technology student so i have some project for system analysis design .as well as are you do my project ? if you can this projects may be i am happy you works.my tittle project is clinic mgt system . than you so much master
Hello again, I am just beginning to learn system design and coming across your videos is like coming across an ACE. Could you tell me how to get started with this idea, it's for my school. I want to simulate a RENTAL SYSTEM. To rent educational Equipment to Teachers and Palestrants. I want to create a system to control who takes de device, when, time, in stock or not and threturn of this equipment. It will look like renting a DVD or a book and returning it. I don't know if you are able to understand my system. lol thanks
good content but your example at the end is useless because i didn't benefit from it. in my opinion you must first show the textual description of the project and then based on the description you draw the use case diagram. this way we can know how to think when want to draw a use case diagram.
This is really depends on user or client's choice how he/she wants the system to be, but in common this video represents only for a particular use case, not overall, I guess. That's why 'register', 'make payment' or others have not been described clearly.
The relationship in use case diagram that is include and extend are the use cases which are called automatically from the base use case. For example, Login and verify login details, here, login in base use case whereas verify login details is included use case. Whenever user call the login use case, it automatically call the verify login details use case. So for the relationship in use case diagram, we specify or draw include and extend relationship to those use cases which are call automatically from the base use case. As your concern, book courses and make payment and login are all base use cases and login do not call book courses or make payment automatically. So that there is not relationship between them. So need to remember that, use case diagram is system diagram which show the system from the user point of view. It's not the flow diagram. I hope it make you clear. If you have still confusion, pls text me at master2teach@gmail.com. Thank You
In your example diagram what would the use case description be for it? It seems to encompass logging in, registering, booking and making a payment so whilst the diagram makes sense I am a bit confused about what exactly the use case description is because it looks like it could many things.
One more thing, when sneezing you use includes, but surely this is not correct because closing your eyes is something you would do without just sneezing, for example going to sleep, thinking, or just simply "closing your eyes". So is this saying that an included use case can also be actor initiated?
Thanks for good question. Actually the example of closing eyes here is different use case than the other closing eyes. The closing eyes use case while sneezing is called internally from sneezing. So this closing eyes use case while sneezing can't be initiaed directly from actors.
@@Master2Teach so would you usually have 2 separate use cases for the same thing if say on a human we could close eyes sneezing or close eyes in general?
@@Walruz1000 Not sure if it's still relevant for you, but what you use as base use cases all depends on what the client wants. Remember, you have to make a diagram that describes the system usage from the client's perspective. So if sneezing is a use case of your system, closing your eyes will be included in that use case. (As an included use case). If closing your eyes is ANOTHER base use case for your system, then you have to make a separate use case for that function. In this example, "closing your eyes" as an include for sneezing is NOT THE SAME as "closing your eyes" as a base use case in the system. They are two separate use cases.
finally, i can really understand this course
Great tutorial, I search thus topic youtube and watched many videos on this topic but this video is really amazing. Topic is covered so nicely.
thank you for the video! explained very well
Amazing Video. Thank you, sir, for making such an informational video. It really helped me during my final year project. Keep it up sir.
Thank you so much.
Very good tutorial. Thanks ❤
This is lovely! I really enjoyed watching this video; thank you for taking the time to make these videos. Lovely.
Thank you so much!
@@Master2Teach Which UML application are using here?
The topic of the video is explained really well here . All my queries related to this topic are cleared . Thankyou so much for making this video . Lots of love and prayers to you from my side .
Thank you, dear and smart Master! All is simple and detailed, in one time! Perfect!!!
Glad you like it! keep on watching
@@Master2Teach what & how shud bwe mentioned for auto functionality in use case as?
Great Work
great explanation
This channel really deserves more attention!!
Thank you again ...please keep it up
I have gone through 7 youtube vids trying to understand the UCD... all of them created questions in my mind more than provided Answers however in your vid i got the whole story in one place
you save me alot of time and effort and your explanation was really Complete & perfect
Thank you for your great comment. I hope you learn and like the video.
Nice Explanation. Thank you
Thank you for the great comment.
Thanks all my questions have been cleared, thanks for the video it's well explained
Keep it up sir👏👏
Thank you so much.
Really informative video. Thanks so much for making it! :)
Bro ur the best 😭😭
Very well explained
Amazing
please what is the name of the software used for the UML diagram in the video?
So informative video👏👏
Thanks for watching and for the positive comment!
Nicely explained video.
Thanks a lot
How do l start
Best video I ever seen in utube
Dear sir can we make a lot of use cases I mean more then 10 20 ?
Insightful.
Thanks for watching and comment
sir the videos is very good. i have a question regarding the actors why because u said that we have primary actor and secodary actor. where secondary actor is the person who interacts after primary actor has made an initiation. but here in the example both actors are named as customer. my doubt is primary actor used all the 4 use cases but why again we have on right the same actor using the same use cases twice. i mean actors representation is done twice(right and left)
I would like to understand as well
Thank you so much sir
Great clarity.
You're most welcome
you are the best
Very nice sir.. thank you
Thank you, sir. 😊
.
..
...
Thanks for comment. Pls don't forget to like and share the video and subscribe too :)
Too heavy bro
Great video! I'm a newbie with some questions....so in this use case are we adding features or do we add the user requirements in the high-level use case?
Features are user requirements
the example you dropped is it high level use case or expanded
😮😮... Nice one sir.. Keep it up...
Thank you, More Videos on Software Engineering coming soon..
thanks for the video man
Thanks for watching and for the positive comment!
Thanks a lot it was helpful
❤️❤️❤️
Please don't forget to like, share, and subscribe to the channel.
Very good explanation, thank you :)
thanks for the information.
can you indicate the program name?
Super
Contiue i support
Thank you Sir for a good explanation. Was very amazed thank you once again.
You are most welcome
thanks master
thanku so much
Thank you for watching and comment. Don't forget to like, share, and subscribe to the channel.
thanks..
Thank you very much. :-)
Thank you so much for watching video and comment. Pls subscribe for more videos.
allah gives you alots alots of happiness I have assigned university assignment for use case diagram and I was just in tension the video you explain is seriously mindblowing lots of prays from here lovely
love from nepal
Dai Really need your help to understand these concepts
Thank you very much for this lesson.
Thanks for comment. Hope it helps.
thanks
Thank you so much for watching my video. Also view ruclips.net/video/PiRsKDlZeVk/видео.html
for more use case diagram clarification. Don't forget to like, share, and subscribe my channel.
Buenísimo !
Which software you r using here?
thank youuu
Can u get the usecase diagram for smart home management system
Please help me
Thank.youuu
How do l register
What will be the auto functionality mentioned in ysecase as? Can. U te" me
sir, please clear my confusion about login and registration usecases. Can we also draw registration as the extended usecase of login? or it will be wrong to do so?
Thank you so much for watching the video and question. Login and Registration are separate use cases. Whenever the base use case is called by the actor, and extended use case may or may not call. If it calls, then it will call from the base use case internally. In the above case. if login fails, it displays an error, it will not call the registration use case. So login extends the error message. Ya, we can show in extension point as option or link but I suggest, best to show these two use cases separately. And these two use cases have their own extend and include use cases as well.
Hope you are clear about it now. Don't forget to like, share, and subscribe the channel.
@@Master2Teach Thank you so much sir for such a good explanation. You mean we will draw both the use cases separately. i have one more question which will clear me all the things. Can we generalize the user as new user and registered user and then connect the login usecase with the registered user and Registration usecase with the new user. And all other usecases which are common will be connected with the parent user? As, i have a project of online food ordering system, so can you please explain me this in the context of my project? I will be really thankful Sir.
So nice bro, thank you so much
Why secondary actor is also performing functions of primary actor?
Why functions of secondary actor are not different from primary actor?
The functions of the secondary actor can be same or different. For example, if primary actor tries to register (in order to get the course), now secondary actor may want to approve the registration manually . So in order to approve the registration manually the secondary actor will have to access the registration function. So by accessing the registration function secondary actor can get detail and according to that the secondary actor can reject of accept. If the secondary actor wants to perform a function which primary actor can never perform, in this case the different function has to be created.
Sir what app did you use? To create use case diagram
There are lots of software to draw the use case diagram like Visio. We can draw online as well in www.draw.io which is quite easy and free.
automatic system is in left side or right side ?
Thanks for good question. In use case diagram, primary actors are place in left side whereas secondary are in right side usually. In case of system as an actor which perform certain automatic job can be place on right side but note that there is not hard and fast rules.
sir please provide pdf links for uml diagrams...
how is enrollment a class please explain
Thank you for your question. If student enroll in course then there is association between the student and course class. To support these two classes interaction and further information, Enrollment class will help which is known as Association Class. It hangs with dotted line without arrow head in between student and course class. I hope this will help you to understand the association class.
The explanation is good but the words on the screen keeps blocking part of the lesson you are explaining. Thank you
Wow,
Thanks for watching and for the positive comment!
ok this video is good but more give an examples and more focused on diagram sake of i am information technology student so i have some project for system analysis design .as well as are you do my project ? if you can this projects may be i am happy you works.my tittle project is clinic mgt system . than you so much master
Thanks for watching and offer. Definitely pls text me at master2teach@gmail.com
❤
Thanks for watching and for the positive comment!
you forgot to name the actors?
In lectures Ka pdf ha
C3 #Sandeep Gurung
Thank you
Hello again,
I am just beginning to learn system design and coming across your videos is like coming across an ACE.
Could you tell me how to get started with this idea, it's for my school. I want to simulate a RENTAL SYSTEM. To rent educational Equipment to Teachers and Palestrants.
I want to create a system to control who takes de device, when, time, in stock or not and threturn of this equipment. It will look like renting a DVD or a book and returning it.
I don't know if you are able to understand my system. lol thanks
Thank you very much for watching my videos. Please send me all details in email master2teach@gmail.com. I will definitely try my best to help you.
good content but your example at the end is useless because i didn't benefit from it. in my opinion you must first show the textual description of the project and then based on the description you draw the use case diagram. this way we can know how to think when want to draw a use case diagram.
Please make videos module ... Waterfall module .. nd all other...
Why does "Book Courses" or "Make Payment" not include "Login"? i can't book a course without logging in. Thank you for the video btw.
This is really depends on user or client's choice how he/she wants the system to be, but in common this video represents only for a particular use case, not overall, I guess.
That's why 'register', 'make payment' or others have not been described clearly.
The relationship in use case diagram that is include and extend are the use cases which are called automatically from the base use case. For example, Login and verify login details, here, login in base use case whereas verify login details is included use case. Whenever user call the login use case, it automatically call the verify login details use case. So for the relationship in use case diagram, we specify or draw include and extend relationship to those use cases which are call automatically from the base use case. As your concern, book courses and make payment and login are all base use cases and login do not call book courses or make payment automatically. So that there is not relationship between them. So need to remember that, use case diagram is system diagram which show the system from the user point of view. It's not the flow diagram. I hope it make you clear. If you have still confusion, pls text me at master2teach@gmail.com. Thank You
Hi
Nepali ho?
Yep
dude you copied that sneeze example from another video. at least credit that video
Thanks for the comment, the example is from SE Book.
በአማርኛ ብሆን አርፍኖ
Thanks for watching and for the positive comment!
bro puri video dekhni ki ap na taati ha
In your example diagram what would the use case description be for it? It seems to encompass logging in, registering, booking and making a payment so whilst the diagram makes sense I am a bit confused about what exactly the use case description is because it looks like it could many things.
One more thing, when sneezing you use includes, but surely this is not correct because closing your eyes is something you would do without just sneezing, for example going to sleep, thinking, or just simply "closing your eyes". So is this saying that an included use case can also be actor initiated?
Thanks for good question. Actually the example of closing eyes here is different use case than the other closing eyes. The closing eyes use case while sneezing is called internally from sneezing. So this closing eyes use case while sneezing can't be initiaed directly from actors.
@@Master2Teach so would you usually have 2 separate use cases for the same thing if say on a human we could close eyes sneezing or close eyes in general?
@@Walruz1000 Not sure if it's still relevant for you, but what you use as base use cases all depends on what the client wants. Remember, you have to make a diagram that describes the system usage from the client's perspective. So if sneezing is a use case of your system, closing your eyes will be included in that use case. (As an included use case). If closing your eyes is ANOTHER base use case for your system, then you have to make a separate use case for that function.
In this example, "closing your eyes" as an include for sneezing is NOT THE SAME as "closing your eyes" as a base use case in the system. They are two separate use cases.
@@NavidIsANoob I took the exam a while back but still relevant and your response is very helpful, appreciate the reply, thanks.
thanks