Structured Scenario editor

[Fred White]

We would like to use the Structured Scenario editor for use cases, but find the limitation that alternate paths cannot contain alternate/exception paths to be a killer (most of our use cases have at least 2 and often 3 or 4 levels of alternate/exception paths).

Any work arounds?  Plans for this limitation to be lifted?

[AndyJ]

Fred,

I've slammed into the same problem and the recommendation was to use <<include>> and <<extend>> use cases...

...I've tried this and found that it is really clumsy, and forces the use case towards functional decomposition, which is very much against the spirit of use cases.

Andy

[AndyJ]

Fred,

I've had a response from Sparx on this issue (via a registered support request raised on November 5)...

They have advised that alternative alternative flows has now been logged as a feature request.

If other users are struggling with this issue, it's probably appropriate to let Sparx know.

[Fred White]

Thanks - I also requested a product change.  I represent our organization, and none of our 6 Business Analysts will be able to use the Structured Scenario editor for use cases as the product stands today.  Making each alternate path a separate use case would multiply the number of use case by 6-10 times and would require retraining the staff in use case structure.