Book a Demo

Author Topic: tagged values in relationship matrix  (Read 3583 times)

Sebastian Gliss

  • EA Novice
  • *
  • Posts: 11
  • Karma: +0/-0
    • View Profile
tagged values in relationship matrix
« on: August 15, 2011, 07:07:49 pm »
Hello there,

may be I am on the wrong way, so first I like to tell you what I like to achieve: I am doing use case modeling for a product, which is in the market in two major version (like a product generation):
- Version 1
- Version 2
I would like two show, which usecases and requirements apply to version 1 and which apply to version 2.
So I have a node, containing all the usecases, for v1 and v2. Then I have defined a tagged value named 'Version' and set value 1, 2 or both. It would be better if using the tagged value twice (i.e. Version=1, Version=2) for an element for both/all versions but thats a side problem.

After doing that, I am trying to create a releationship matrix, showing e.g. the usecases on the x axis, and a collumn for each value of the tagged value "Version" (three in this example).
But I don't have a possibility to choose that tagged value as a target.
It seems that I have not get the concept, but I know clearly what I like to do.

I have also thought about using 'Scenarios' for distinction of versions, but I also do not find 'scenario' for using as a source or target.

How would you reflect different generations of the same application?
I need all the Major Versions in one model, as the application evolves and people like to know which feature or requirement or usecase comes from which generation of the software.

I am just looking for the right way...  :-/


Thanks in advance

Sebastian

Sebastian Gliss

  • EA Novice
  • *
  • Posts: 11
  • Karma: +0/-0
    • View Profile
Re: tagged values in relationship matrix
« Reply #1 on: August 15, 2011, 10:09:15 pm »
Well, may be I have an answer by myself:

I stepped away from tagged values and did the following:

Created two Features V1 and V2.
Openend the relationship matrix (source = UseCase, target = feature)
Then defined the realization links using the relationship matrix.

voila.
I think tagged values are not suitable for this scenario.

Luis J. Lobo

  • EA User
  • **
  • Posts: 252
  • Karma: +0/-0
  • IT Consultant
    • View Profile
Re: tagged values in relationship matrix
« Reply #2 on: August 17, 2011, 08:19:30 pm »
The relationship matrix, by definition and as its name indicates, is designed to show relations between elements, not the elements and its properties in rows/columns.