Book a Demo

Author Topic: Alternate path restriction in Use Case Scenario  (Read 5384 times)

tomeggi

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Alternate path restriction in Use Case Scenario
« on: October 17, 2012, 12:42:17 am »
I am using Use Case Structured Scenarios very intensively because we also use them for creating test cases within another tool (Enterprise Tester).

I have to deal with a limitation of Use Case Structured Scenarios within EA (i am using EA 9.3 build 9.3.933): I can define alternate and/or exception path for a step within the basic scenario but it is not possible doing the same within an alternate or exception path.

How can I bypass this restriction or will EA provide this feature sometimes in the near future?
« Last Edit: October 17, 2012, 12:43:18 am by tomeggi »

[email protected]

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: Alternate path restriction in Use Case Scenario
« Reply #1 on: December 29, 2015, 09:37:46 am »
I have the same problem. I remember that in older version was possible create create alternate and/or exception from step in alternate scenario.

Why there is this restriction?

What's the paper,  article ou standard used to create this restriction?

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Alternate path restriction in Use Case Scenario
« Reply #2 on: December 29, 2015, 02:26:23 pm »
It has never been possible to create alternate/exception scenarios for anything but the main scenario.

And although I don't think the tool should restrict this, it is not a bad idea to restrict yourself to this in order to keep the scenarios simple. Exception on alternate on alternate => spaghetti

Geert

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Alternate path restriction in Use Case Scenario
« Reply #3 on: December 29, 2015, 08:48:59 pm »
I would not call a two-level exception spaghetti. Nor a three-level alternative.

q.