1
General Board / Re: Assigning an element to two packages?
« on: August 01, 2014, 09:59:05 am »Quote
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.
