Use Case Relationships
You may recall that we decided that login and logout do not meet the litmus test of being use cases because they do not provide something of value to the customer. They are really part of the various HomeDirect use cases, such as Browse account balances and Transfer funds. So, we somehow have to reuse the sequence of events required for login and logout.
The UML notation provides “include” and “extend” relationships, which can be used to model such reuse within use cases.
Include
An include relationship allows you to capture a common piece of functionality in a separate use case, and then “include” the use case in another use case via the include relationship. The include relationship is shown as a dependency relationship ...
Get Developing Enterprise Java Applications with J2EE™ and UML now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
