Assigning an element to two packages?

[Wai1982]

I have a list of Requirement elements that are relevant across two seperate Packages.

Is it possible to have it stored in both packages so that it is searchable in the package browser for each of them?

Or do I have to actually create two elements - one for each package?

[Helmut Ortmann]

Hi,

it's not possible to have the same thing in two packages.

Besides it makes no sense. It will only bring redundancy to your model which makes it difficult to maintain.

What you can do:
- Have diagram and draw a link of the requirement onto the diagram
- Make a dependency from requirement to package

Think of a package as of a cupboard. A cup can't be in both packages at the same time. You may insert a note to say that you'll find the cup in another cupboard.

Helmut

[KP]

I agree with Helmut. The relationship you are trying to model is that a Requirement "is relevant to" a Package. I don't think ownership is a good modelling construct to model that relationship. A dependency is better, maybe with a stereotype that has some meaning to you.

[Wai1982]

I agree with Helmut. The relationship you are trying to model is that a Requirement "is relevant to" a Package. I don't think ownership is a good modelling construct to model that relationship. A dependency is better, maybe with a stereotype that has some meaning to you.

Hi yes, i didn't think there would be a way - thought it was worth a try.

I'm using dependencies at the moment. All my requirements are linked to one or more "files" (a custom stereotype). But my problem is that each of these requirements have a whole set of tagged values and that a business requirement I have is to be able to look at a "file" and filter out only the requirements that have certain tagged values.

I can use the package browser to filter against the tagged values but I can't filter out the requirements that aren't in my file.

Conversely I can use a diagram and the traceability window to show only requirements that exist within a file but then I can't use the diagram filter to filter out tagged values...

It seems there's no easy way to search both on dependency and tagged values at the same time.  

[KP]

You probably need to look at custom SQL queries then.