Book a Demo

Author Topic: Use case scenario tagged value  (Read 3948 times)

Henrique Narciso

  • EA User
  • **
  • Posts: 86
  • Karma: +0/-0
    • View Profile
Use case scenario tagged value
« on: July 01, 2009, 07:44:14 pm »
Hello,

I would like to have a tagged value in every use case scenario.

The issue I'm trying to resolve is to have traceability between a Change and a specific scenario impact.
I know that I can link a change to a use case but this is not sufficient.

Is there another way to get the same result throught a diferent feature?

thanks in advance!
Henrique Narciso

Luis J. Lobo

  • EA User
  • **
  • Posts: 252
  • Karma: +0/-0
  • IT Consultant
    • View Profile
Re: Use case scenario tagged value
« Reply #1 on: July 01, 2009, 09:08:14 pm »
Why don't describe each use case scenarios in a operation under the use case instead of the scenario tab? The "operation" element is linkable, has project browser representation, could have tagged values...
« Last Edit: July 01, 2009, 09:08:53 pm by Deiser »

Henrique Narciso

  • EA User
  • **
  • Posts: 86
  • Karma: +0/-0
    • View Profile
Re: Use case scenario tagged value
« Reply #2 on: July 01, 2009, 10:10:48 pm »
First of all, Thank you Luis. Gracias!

I think it would be very dificutl for the requirements team.

The way I look at it is to create an addin that links Change elements to Scenarios ( in the t_objectscenarios table). something like using the t_connector table, and use a connector_type = scenario.

Still this is a bit out of what i would like.

Does anyone do requirements change management at a scenario level? if so, how?

Henrique Narciso


Luis J. Lobo

  • EA User
  • **
  • Posts: 252
  • Karma: +0/-0
  • IT Consultant
    • View Profile
Re: Use case scenario tagged value
« Reply #3 on: July 01, 2009, 10:33:02 pm »
Via API it's possible, I think...

Other way is to specify the scenarios in a Linked Document of the Use Case (with your own template, if you prefer)

Then, try this: create a linked document and inside it, right click and "UML | Create and link new element..."

Try this too: create a linked document and inside it, drag and drop an change element of the project browser.

Both ways, the trazability is created vía hyperlink only...
« Last Edit: July 01, 2009, 10:34:31 pm by Deiser »

Henrique Narciso

  • EA User
  • **
  • Posts: 86
  • Karma: +0/-0
    • View Profile
Re: Use case scenario tagged value
« Reply #4 on: July 02, 2009, 07:10:23 pm »
Hello Luis,

The solutions presented are not what we would like to have.
In fact I see adding a column in the database table t_objectscenarios to link.

Does anyone do change management at a scenario level?

It seems that we are more demanding, but we are only try to respond to a simple question.
"how do I get a simple report of requirements impacted by a change at the scenario level?"
If this is not possible,
"how do I get a simple report of requirements based by a change that shows the diferences between the current version and the previous one?"

Has anyone resolved this issue?

thanks in advance,
Henrique