CODEWITHSUNDEEP
umluse-caseuse-case-diagram
ngmir
ngmir

Reputation: 488

UML Use Case Diagram: Do generalisation children inherit include/extends from parent?

Given the following scenario:

[...] The refueling is terminated either when the maximal permissible amount of petrol is dispensed, or when the customer decides to put the hose back into the mounting plate. The amout owed for the petrol dispensed is charged to the customer's credit card account when the refueling process has finished. [...]

Now while trying to model this in a Use Case Diagram I came up with this:

foo

My main question is: Do child use cases inherit include and extend relationships? Is this valid/meaningful?

Upvotes: 0

Views: 1588

Answers (1)

qwerty_so
qwerty_so

Reputation: 36305

You are wrong here (like in the other question). Terminate is no Use Case (at best it's an anti-use case). The same goes for the other bubbles except for bill credit card. The (most likely) missing UC is Fuel car.

Generally: do NOT use generalization with UCs. It's an awful bad idea. An added value is unique (remember: it is related to unique sales proposition). You can (in 99.9% not generalize that, except you have a franchise, which is the only example that would work).

And again: Read Bittner/Spence to understand why UCs are about added value and not about functions.

Upvotes: 1

Related Questions