Book a Demo

Author Topic: Orphaned scenarios  (Read 4552 times)

Doug Blake

  • EA User
  • **
  • Posts: 102
  • Karma: +0/-0
    • View Profile
Orphaned scenarios
« on: June 13, 2012, 12:26:37 am »
I think I ought to let you all know of my experiences today.

I have a pile (about 20) of use cases nost with some structured scenarios, ie a basic path and several alternate paths.

Firstly, when creating new alternate paths, you get a dialogue listing other alternate scenarios that you can use. Renaming and deleting these scenarios seems to be difficult for EA to accomplish, but that is not my main point, although it may have something to do with the problems I got today.

I decided that I didnt like the order that my Use Cases were sitting in the Project Browser, so I selected them and moved some of them up and down using those pretty green arrows. Then I regenerated my document using eaDocX. Imagine my surprise, when the document showed alternate scenarios from some use cases appearing in other use cases. I used the built in document generator and that too showed similar, but not the same, results.

Is there a problem with the model I ask myself? Too darn right there is. On the face of it, the scenarios look OK, but the pick lists for new alternat paths are wrong. And to confirm it all, I exported the XMI which shows categorically that there are scearios that dont show up in the model!!! There are orphans in there and they dont show up when you Validate or Integrity check the model.

XMI does have its uses however, I deleted the rogue scenarios and re-imported the XMI and all is hunky dory once more in the land of EA. At least I only had to delete extra stuff and not insert missing stuff.

I have registered a bug report, but it seems that you have to be precise about what you put in the model and dont mess about with it afterwards.

Its still a brilliant tool and save loads of effort, lets hope they get on top of this problem.
DGB Using 12.0.1214 / eaDocX 3.6.2.1 / MSSQL / TFS / Windows 7 / IE11

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Orphaned scenarios
« Reply #1 on: June 13, 2012, 12:49:51 am »
Hmmm. I'd suspect a bug in EaDocX rather than in EA.

q.

Doug Blake

  • EA User
  • **
  • Posts: 102
  • Karma: +0/-0
    • View Profile
Re: Orphaned scenarios
« Reply #2 on: June 13, 2012, 12:54:02 am »
Quote
Hmmm. I'd suspect a bug in EaDocX rather than in EA.
q.

As I said, the data in the XMI was wrong ...
And EAs docGen also showed the wrong result ...
DGB Using 12.0.1214 / eaDocX 3.6.2.1 / MSSQL / TFS / Windows 7 / IE11

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Orphaned scenarios
« Reply #3 on: June 13, 2012, 01:45:07 am »
Sorry, I did not read well enough...

q.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Orphaned scenarios
« Reply #4 on: June 13, 2012, 04:12:11 pm »
Oops, were you able to reliably reproduce the problem?

Geert

Doug Blake

  • EA User
  • **
  • Posts: 102
  • Karma: +0/-0
    • View Profile
Re: Orphaned scenarios
« Reply #5 on: June 13, 2012, 04:56:49 pm »
Not really Geert, it took me an hour to recover, after a further hour trying to find out what the problem was. Its not really something I want to repeat at the moment. However, I have EAPed my use case project and do intend to come back to it when I have time.
DGB Using 12.0.1214 / eaDocX 3.6.2.1 / MSSQL / TFS / Windows 7 / IE11