Use Cases, Alt Flows and Exceptions

[AndyJ]

Hmm...

I'm trying to recreate a set of Use Cases in the Structured Scenario editor.

I have a typical scenario within an alternative flow "Add Person/s" where I would expect two different scenarios:

1. Person exists on the system already and the details are confirmed or updated.

2. Person does not exist on the system already and all details are manually added.

The steps a quite different depending on case 1 or 2 within this alternative flow.

Add Person is not sufficiently interesting to be its own Use Case.

Several of the steps within the alternative flow would usually have exceptions that are minor variations outside of the happy path...

All of these make me wonder why an alternative flow cannot itself branch to an alternative flow and exception flow.

Are others wondering about the practicality of this restriction?

I'm looking at the specifics to see if any of the alternative flows can be rolled up into the basic flow, but this has the potential to create a really ugly, exceptionally long basic flow.

[beginner]

Although I try to avoid it, but sometimes the <<extend>> seems to make sense. I would look at this as UC Add Person which is extended by UC Manually Input New Person.  

b.