Author Topic: Structured Scenarios - Multiple Alternate Flows (Read 5287 times)

brucebanner · « **on:** March 05, 2011, 11:35:04 pm »

Hi

Having the ability to have an Alternate flow coming off an Alternate flow would be very useful. At the moment you can only have this off the Main flow and is proving very annoying.

AlanT · « **Reply #1 on:** March 07, 2011, 05:03:44 am »

   I agree that this would be a good enhancement.

   I am also frustrated that I cannot get a general timeframe (not a specific date) for the release of the next major version of EA.

   Alan

skiwi · « **Reply #2 on:** March 07, 2011, 02:27:59 pm »

The beta of the next major version is out.
Tell us if this feature is there and works!

Eve · « **Reply #3 on:** March 07, 2011, 02:34:29 pm »

No, it's not.

AlanT · « **Reply #4 on:** March 07, 2011, 03:32:17 pm »

I would hope it would be announced! Alan

brucebanner · « **Reply #5 on:** March 08, 2011, 01:56:41 am »

Hi Simon

Do you have any plans to include it in version 9?

qwerty · « **Reply #6 on:** March 08, 2011, 03:29:04 am »

from V9 changes:
Structured Scenarios

Auto-Complete in structured scenario editor improved when using space to accept selected word
Prevented situation where one alternate path could have two distinct joining steps
Test case generation modified to update connector lists for current Element
Activity and State Diagram generation modified to re-use elements for alternate path instead of recreating them
Activity and State Diagram generation modified increase left margin
Sequence Diagram generation modified to only include step numbers if 'Show Sequence Numbering' is disabled
Linking Step to a Use Case when editing from initial creation updated to ensure link is created on correct step
Highlight of glossary terms and referenced elements improved in situations where one is a substring of another

obviously not

q.

Roel · « **Reply #7 on:** May 05, 2011, 12:47:16 am »

I find the structured scenarios a big plus of EA, but not being able to add an alternative flow to another alt.flow is one of the biggest limitations I've experienced with the structured scenarios.

Ofcourse it is questionable whether an alt.flow should have another alt. flow or should be an include-use case instead. However, an alt.flow should at least be able to have an exception flow in my opinion.

Are there any plans to add this feature in a next version of EA?

dillon042603 · « **Reply #8 on:** May 17, 2011, 07:34:23 am »

I don't believe that every alternate of an alternate should be another use case; although, everyone is taught differently. I was taught that CRUD (create, read, update and delete) all go into one use case. It is normally one of the first alternates that you have and I'm sure you can imagine that there may be lots of alternates from this initial decision. The way that EA is designed doesn't allow for any alternates from this and it is my biggest complaint. Thank goodness that the diagram will let you create as many alternates of alternates that you want. I am currently piloting the tool and there are many people that don't want to use it for this very reason. Most of our BAs only create a word template for their use cases, but are willing to create a diagram if the tool will generate the word document for them. Until it will generate the document, I have to create the diagrams and a separate word document on my own. I really hope that a fix for this is coming soon!

qwerty · « **Reply #9 on:** May 17, 2011, 03:36:02 pm »

FWIW: We create UC docu by writing enumerated steps in the basic path. Extensions/Exceptions refer to these numbers adding a character and a reason (e.g. "2a some failure occured"). The needed steps are once again enumerated. So you can introduce extensions to extensions (e.g. "2a3a some more extension").

q.

Sparx Systems Forum

News: