Use Cases - Simplifying Use Cases - Generalization
6 important questions on Use Cases - Simplifying Use Cases - Generalization
What can be generalized / specialized in a Use Case diagram?
What happens if an Actor is Specialized?
They also, as expected, inherit any properties that are declared on the general Use Case.
How would we intepret the diagram if we dropped the generalization and instead connected the Admin directly to the Logon Use Case ?![]()
Both a User Actor and an Admin Actor would be needed to Logon.
- Higher grades + faster learning
- Never study anything twice
- 100% sure, 100% understanding
What is the rule if more than one Actor connect to the Use Case?
They all must be available for the Use Case to proceed.
What is a benefit of using Actor Generalization?
Whatever requirements, diagrams, or goals we attach to the general Use Case are also applied to the specific Use Cases, though we can....
This approach also allows us to add simply new specialized Use Cases,
The question on the page originate from the summary of the following study material:
- A unique study and practice tool
- Never study anything twice again
- Get the grades you hope for
- 100% sure, 100% understanding
![Trustpilot Logo](/images/design_2020/lp/clp-trustpilot-en.png)