Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • Just to clarify how the diagram is working: So, a Use Case diagram is not representing actual software components (e.g. it can be constructed early on, before any code is written), it's just meant to be a high-level picture of various things users/actors expect they'll be able to do. So, each blob that has a line coming from an actor is basically an independent operation. Now the "include" arrow points towards the thing that's included; Withdraw, Deposit and Transfer all share a common step (Validation), but can be executed independently. Here, you can't execute Valid cust. directly. 1/2 Commented May 21, 2022 at 13:12
  • If Valid customer is executed as, say, a part of Transfer, it will not also execute Deposit and Withdraw. But Deposit and Withdraw can each independently invoke Valid customer. Kind of like one function can be called by three other functions, but calling one of those will not call all the others. Note, however, that a use case is not a function - it's a thing the system can do that's of some value to the actor; it consists of a number of steps that may require a coordinated effort of many functions to be executed. 2/2 Commented May 21, 2022 at 13:12