Your videos are one of the best materials for newbies in BA as well as professionals in BA. You made it so simple that a newbie would understand and you made it so detailed that a professional would need it. Thanks for all the effort you're putting into your videos.
Hi, Ajibola! You are most welcome! And thank you for your kind words. They really help motivate me to continue putting out valuable content! I hope it serves you well!
This was an extremely clear and informative breakdown of use case graphics! I enjoyed how you discussed the various interactions, such as "include" and "extend"; it definitely makes comprehending use cases a little easier. The banking system provides an excellent example of how everything is connected. Thank you for making this so easy to follow!
Thanks for this content - What I like about this channel is how the BA role and documentation is structured. Too many times BAs get mixed up and try to jump straight into functional requirements without fully developing the use case.
You are very welcome! And I totally agree with your point about jumping into functional requirements too soon. There are so many elements that need to be understood before properly eliciting and specifying these requirements.
Great discussion on use case diagrams! The tips on keeping use case names short and action-oriented are super practical too. Thanks for making this topic so accessible!
You are most welcome. Glad it was helpful! And yes, keeping the use case simply and easy to comprehend is essential to the comprehension of the digram.
Literally, thank you so much! This helped me so much to study for an upcoming exam. I'll make sure to remember the theoritical basis you showed us and excel in that exam!
Thank you for this simplified tutorial and for clarifying the positions and roles of the primary and secondary actors. Please can you do a session for documenting a Use Case Specification?
Thanks Mr. White for this comprehensive tutorial. I had a better understanding of use case diagram and use case documentation after watching the relevant videos. However i have two questions to ask. One is regarding the placement of primary and secondary use case actors and the other is about a scenario where the use case diagram is too large and complex. Q1 => You made mention that the secondary actors should be placed in the right side of the use case diagram. What if an actor serves as a primary actor to a use case but also serves as secondary actor to another use case. Are we to duplicate the actor in both sides of the use case diagram? Q2 => Is it allowed to divide a use case diagram of a system into different sub-diagrams especially if the system use case diagram is too large and complex? Thank you.
You are very welcome! In regards to your questions, see my responses. 1. If you are representing an entire system (system use case) the actor's position will never change because you are looking at the entire use case from start to finish. If you are breaking the use case up by the base use cases, you represent the actor according to how they interact with that specific part of the use case. So the actor's position may change according to what you are focusing on. 2. Yes, you are able to divide the use case up by its components when the system use case is too complex. These are referred to as "base use cases" and also the "sub-use cases". It's also common to represent the use case components using sequence diagrams or activity diagrams. I hope that helps.
In the above example [complete online transaction] is at the top; is that the normal case, or can you have the resulting behavior e.g., [build a home] and the construction or acquire materials at the top
Hi, Donald! Yes, you can have the resulting behavior. The title of the use case diagram should clearly indicate the "main goal" of the completed use case. I hope that helps.
Hi Michael, thanks for the in-depth video. Learned quite a lot. I do have a question. In BA literature I've read elsewhere, I've seen them saying you should only include use cases in a diagram that enable users to achieve a goal. I saw that you have said the same in the tips list. I've heard that a use case such as 'Login' is not considered a goal since users don't really 'want' to login. It has no inherent business value so it's not the actual goal. It's just a task they have to do it in order to get to do something that has business value to reach a goal. But I see that you have still included 'Login' use case in the diagram. I'm confused about this because of the conflicting viewpoints I've been seeing. I'd love to know your rationale behind this.
Hi, Isuru! Great question. In the lesson, I spoke about "base use cases" and "sub-use cases". The base use cases represent the core functionality and generally have some goal. This is what is mostly referenced in discussions regarding use cases. The sub-use case, on the other hand, is a smaller, more specific use case that is part of a larger, overarching use case. It represents a distinct function or interaction instead of a goal. So here, the "login" use case would be a sub-use case and not a base use case. With that said, if the solution was focused on setting up password credentials or security profiles, there may be times where a login will serve as the base use case. I hope that helps.
Thanks for this tutorial. How you do Use Case Diagram and Description for a change to an existing system like making existing fields manadory or removing a option from a drop down list.
You are very welcome! Based on what you've described, I'm thinking a use case would not be the best option. Maybe data mapping combined with a wire frame would be more effective for that type of change.
You're very welcome! And thank you for watching! Also, check out the videos on Use Case Descriptions and Sequence Diagrams if you haven't already. Those videos compliment this one very well.
@@thebadoc Thank you so much for answering. I'm just confused a bit, but what if the intranet is capable of assessing and doing core operations of a system, wouldn't it be apart of a system. Or maybe I'm confused about what a system is.
@@didistone8482 A "system" represents the software application that is being modeled in the use case. It's essentially the subject of the use case diagram.The system/application that is being examined in the project is considered the main system and is the primary focus of the use case. Use cases, actors, and their relationships are all centered around this main system. External systems are those that interact with the main system but are not part of the main system. These external systems are considered actors (which can be a human or a system). I hope that helps!
