@@geekific When you design a system you describe its expected behaviour from interacting persons and systems perspective with a Use Case Diagram right? But would it be logical to create a Sequence diagram to describe the details of and sequence of every single use case? So to say a Sequence Diagram is a level lower in the design phase.
Yes! I agree it is a lower design level phase, however you may find that sometimes it is an overkill to represent every single scenario with a sequence diagram, make sure you don't abuse and spend more time on it than it actually needs! Hope this helps :)
best explaination on whole internet
just u left the relationships in use case diagrams
Amazing explanation
You rocks, I am fan of urs. Watching all videos
Thank you for making a wonderful video
Brilliant!
I have seen such diagrams of late but now I could correlate.
Nice! Glad I could help :)
Amazing explanation
super, thanks
Thanks soo much
Do similar videos for other type of diagrams too :)
I will of course they're on the way! Thanks :)
Thanks
My pleasure! :)
😍😍😍
my professor got mad coz he told us " use cases like Browse items , view etc.. " can't be called an use case..
is it logical to day you create a Sequence Diagram for every Use Case?
Hello, am not sure I got your question can u rephrase it please?
@@geekific When you design a system you describe its expected behaviour from interacting persons and systems perspective with a Use Case Diagram right? But would it be logical to create a Sequence diagram to describe the details of and sequence of every single use case?
So to say a Sequence Diagram is a level lower in the design phase.
Yes! I agree it is a lower design level phase, however you may find that sometimes it is an overkill to represent every single scenario with a sequence diagram, make sure you don't abuse and spend more time on it than it actually needs! Hope this helps :)