Cool video, but presenter sounds like he is either reading from a book or lecturing, instead of just plain talking/explaining, still material is very useful.
Thanks for good question. Defining classes depend upon the Software Engineer or developer. Always try to maintain low coupling high cohesion while software development. So register and de-register can be include in single class.
When do we usually create new objects? Why can't we just have them like the other participants at the beginning ? I am confused ! Also for the reflexive message you showed a recursive message.
I have a problem I am making a sequence diagram for my SW application But I don't know do I make it have one scenario having all functions for a particular user type Or making different scenarios for the same user type Can you help me? When to split system into scenarios ?
Hello thank you so much for the comment. I will try my best to make a video tutorial on it as well. Please don't forget to like, share, and subscribe my channel.
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.
