As you add use cases to your project you may find step sequences that are common to multiple use cases. Or you may have some use cases where the flow of events is too long making it hard to read. In either case you may find it useful to refactor your use case, that is, break out a subset of steps into a new use case.
Begin by selecting the steps you wish to move out1, right clicking on any of the selected steps, and selecting Move to new Use Case, if the new use case may be referenced by other use cases, or Move to child Use Case, if the new use case is only applicable to the current use case:
You can add a meaningful name and brief description to the new use case:
When you finish creating the use case, the selected steps from the original use case – along with any extensions you’d added to those steps– will be created in the new use case.
1You can refactor Extension steps in addition to Main Success Scenario steps. To refactor extension steps only select the steps, not the extension condition.
I think it would be helpful to show in this article or to reference a follow up article that shows how to have multiple Use Cases then reference this newly created Use Case. I don't know how to do that.
Hi David,
You can reference a use case just by typing its ID. When you enter "UC-" in any text field, CaseComplete will bring up a list of use cases to help you find the one you want to reference. Alternatively you can right click/Insert use case ID link (or press Ctrl+L) to bring up the list. Doing it this way lets you filter the list by name as you type.