Use Cases - Simplifying Use Cases - Use Case Diagrams

6 important questions on Use Cases - Simplifying Use Cases - Use Case Diagrams

What is normally the diagram kind of a use case diagram?

The diagram header <kind> is usually pkg, though other namespace containers are possible, e.g., class and component.
Report

The Subject or System boundary is usually a....?

The Subject or system boundary is usually a class representing the entire system or a UML component representing a subsystem.
Report

More than one Subject can be shown in the same diagram.

What is true about Use Cases offered by more than one Subject?


Use Cases offered by more than one Subject are repeated in each Subject as necessary.
Report

When do we often create a seperate diagram in the same package?

If a complicated Actor hierarchy is involved, especially if you are displaying properties for the Actors, a separate diagram in the same package is often created.
Report

If a class or component is the <kind> of diagram, and no Subject is depicted, we usually assume that ........... is the Subject

If a class or component is the <kind> of diagram, and no Subject is depicted, we usually assume that the diagram element is the Subject
Report

If the Use Case diagram is shown in a Class, we typically assume that the Subject is ......

if the Use Case diagram is shown in a Class, we typically assume that the Subject is the Class
Report

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
Remember faster, study better. Scientifically proven.
Trustpilot Logo
  • Higher grades + faster learning
  • Never study anything twice
  • 100% sure, 100% understanding
Discover Study Smart