Use Case Model
Anti-Patterns
Use Case anti-patterns are common mistakes I've seen
students make.
Snow Jobs
Use this anti-pattern if you want to intimidate potential
critics with lots of technical jargon:

Bad Actors

Making the subject
an actor

Lazy Use Cases

Confusing Extends
with Generalization

Use case diagram as
a workflow

Internal objects as
actors or use cases

Confusing goals
with UI triggers

Bad/Inconsistent
Language

Scenarios as Use Cases
