Use Cases - Simplifying Use Cases - Include

6 important questions on Use Cases - Simplifying Use Cases - Include

With large Use Cases, you may often find that several Use Cases share common subgoals or common subbehaviors. To share without duplication.

How can we do this?

Using the <<Include>> mechanism

Because the behavior is part of the Base Use Case, the Base Use Case is..

is not complete without the Included Use Case, and the goals of the Base cannot be completely met without the inclusion.

What are the boxes with the folded corners?

They are Notes that add commentary to a diagram.
  • Higher grades + faster learning
  • Never study anything twice
  • 100% sure, 100% understanding
Discover Study Smart

What happens with the included contents?

The Included Use Case’s contents insert inside the Base Use Case.

It is not like a subroutine call as there are no parameters nor return values.

It is more like a copy and paste, or an in-line macro expansion.

How many incuded use cases may be connected to a base use case?

There are no limits on the number of Included Use Cases connected to a Base, as long as each Included Use Case is necessary to meet the Base’s goals and complete the required functionality.

In UML 2.5 we use the term <<include>> .
What were the earlier terms for the <<include>> mechanism?

<<includes>>

<<uses>>

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