Alternate paths in v8.0

[Guillaume]

Hi

I specified a basic path scenario for a use case and a couple of alternate ones.

I can associate an alternate or exception path from a Step that belongs to the Basic Path scenario, but not from an alternate path!
I find this very restrictive. See the example below that is perfectly valid, yet I cannot specify it in EA.

Basic Path
Step 1: [action]
Step 2: [action] OR A1
Step 3: use case end

Alternate A1
Step 1: [action]
Step 2: [action] OR A2
Step 3: use case end

Alternate A2
Step 1: [action]
Step 2: [action] OR Basic Path
Step 3: use case end

Thanks,
Guillaume

[Guillaume]

Further to this, I think there should be additional flexibility to associate the step from any other scenario instead of the path, as shown below:

Basic Path
Step 1: [action]
Step 2: [action] OR A1
Step 3: use case ends

Alternate A1
Step 1: [action]
Step 2: [action] OR A2 (condition1) OR A3 (condition2)
Step 3: use case ends

Alternate A2
Step 1: [action]
Step 2: [action] OR Basic Path Step 2 (condition1)
Step 3: use case ends

Alternate A3
Step 1: [action]
Step 2: [action] OR A2 Step 1 (condition1) OR Basic Path Step 2 (condition2)
Step 3: use case ends

[Guillaume]

Sorry but another comment on this:

When you add an Alternate path to a step within the scenario, and generate the activity diagram, a decision element entitled 'Alternate 1' is shown.
May I suggest that when an alternate path is added to a step, it should be possible to select the following:
- Select the alternate scenario (current behaviour) and any specific step (default = step 1)
- Select one or more Process constraints, with operands, and specify if they are true or false (e.g. constraint 1 = true AND constraint 2 = false) : this would populate the decision element on the activity diagram to make proper use of constraints.

[Paolo F Cantoni]

[size=18]...[/size]
I can associate an alternate or exception path from a Step that belongs to the Basic Path scenario, but not from an alternate path!
I find this very restrictive. See the example below that is perfectly valid, yet I cannot specify it in EA.
[size=18]...[/size]

Hi Guillaume,

Thanks to EAUI, I think you CAN create an alternate path from a non-Basic path.

I agree with you that it should be possible in the normal course of events (I'm not aware of the theoretical reason why it was disabled - perhaps Sparx could enlighten us?), and given that you can do it anyway using this "trick"; Sparx should just enable it...

The "trick" (workaround) is:
Bring up your alternate path.  Change the type to Basic path (but don't save).  The disabled buttons should now enable.  Make the changes, and switch the type back to whatever it was...

Cumbersome I know, but it's a work-around until Sparx fix the Beta.

HTH,
Paolo