Use Case: Alternatives of Alternative Scenario

[smk]

Hello,

We are using version 8.0 of the EA. She brought an action much nice. Now there is an interface that facilitates the structuring of scenarios of use cases, called "Structured Specification."

We just do not understand why there isn´t the possibility to define alternative scenarios for the alternative scenario. The same happend with the exception scenarios.

In theory it would be possible!

Is there any reason for it, or in future versions of EA this option will be available?

Thanks!

[Geert Bellekens]

Do you consider alternative scenario's to already alternative scenario's a best practice?
Seems a bit too complicated to me.

Geert

[son-of-sargasso]

Weeelll, I dunno Geert,

It all seems like a fine attempt, at a plaudible goal, BUT while the feature is rich, the pastry is a bit dry and the chocolate seems a bit runny.

While it is sooo nice to have a structured UC development tool, the delineations between the UseCase and the scenario seems a bit disjointed.  I mean, if there appears to be a direct link between a scenario and a constraint, then why are the constraints registered at the use case level.  Further the generated artifacts (activity diagrams and (grrrrrrrrrr) test cases) take no notice of the full structure of the structured use case.  The invocation options are meaningless.

Sigh, such a good looking pastry, and such a disappointing taste.

Nevertheless, to get back to smk, please persevere.  I too think there is a value to be gained here.  I am not quite sure what it though.  I too, thought "Hey" here's a nifty way to include alternates that don't affect the (usecase level) scenario outcome.  But I just ended up confused (which isn't such a short trip for me these days).  Good luck, and for what its worth, "me too".

cheers
bruce  

[smk]

Usually we have situations of alternative scenarios of alternative scenario, or even more common exception scenarios of alternative scenario.

Incidentally, the concept is correct flow of events and not scenarios! For one scenario, is the main flow or the combination of the main flow with alternate flows and / or exception.

But back to question, let's take the example of a "register of client" (CRUD).

- Main flow is the retrieve (R).
- Alternate flows will be three (C, U and D).
- Within these alternative create (C) and updade (U) we can have exception flow, for example, "Code not found", "data validation invalid", etc.

In this sense I think it is best practice the "alternative scenarios / exception of the alternative scenario", or using the right concept, alternative flows / exception of alternate flow.