Book a Demo

Author Topic: Scenarios in v8: step to extend an existing UC  (Read 4783 times)

Guillaume

  • EA Practitioner
  • ***
  • Posts: 1405
  • Karma: +42/-2
    • View Profile
    • www.umlchannel.com
Scenarios in v8: step to extend an existing UC
« on: February 16, 2010, 04:03:02 am »
Hi

When entering steps for a use case scenario, you have the option to "Link the Step to Use Case" as specified below in EA help:

Either include the actions of an existing Use Case element, extend an existing Use Case element, or invoke a Use Case as the action of the selected step [...]
The appropriate includes, extends or invokes stereotyped connector is created between the current element and the selected Use Case


It looks like the extend association is created the wrong way round;
if you specify that a use case continues to another use case with an extends association, the extends association should be from the other use case to this one, as it is the other one that extends it. Otherwise it should provide the "Extended by" stereotype instead (less used though)



Guillaume

Blog: www.umlchannel.com | Free utilities addin: www.eautils.com


KP

  • EA Administrator
  • EA Expert
  • *****
  • Posts: 2919
  • Karma: +55/-3
    • View Profile
Re: Scenarios in v8: step to extend an existing UC
« Reply #1 on: February 16, 2010, 08:52:15 am »
Quote
It looks like the extend association is created the wrong way round;
It is, and it's being fixed for the next build.
The Sparx Team
[email protected]

Guillaume

  • EA Practitioner
  • ***
  • Posts: 1405
  • Karma: +42/-2
    • View Profile
    • www.umlchannel.com
Re: Scenarios in v8: step to extend an existing UC
« Reply #2 on: February 16, 2010, 07:01:44 pm »
Thanks  :)
Guillaume

Blog: www.umlchannel.com | Free utilities addin: www.eautils.com


Fred Bevan

  • EA User
  • **
  • Posts: 46
  • Karma: +0/-0
    • View Profile
Re: Scenarios in v8: step to extend an existing UC
« Reply #3 on: May 04, 2011, 01:22:29 am »
It looks to me that this is still a problem in version 9 beta 2. Does anyone know if it is fixed in beta 3?