Sparx Systems Forum
Enterprise Architect => Suggestions and Requests => Topic started by: Emilio on April 03, 2009, 07:24:23 pm
-
EA Version:7.1
In a previous installment about the Relationship Matrix it was discussed about its deficient export capabilities. I have just run across another limitation when doing my data model and mapping the various tables to the requirements and features in the Requirements Model.
The business analyst has created a requirements diagram in which two types have been defined (a) Requirements and (b) Features, these are two types that can be specified in EA.
Additionally and for a good reason, these requirements and features have been created as hierarchies, i.e. REQ-1, REQ-1.1, REQ-1.2, REQ1.-3, REQ-2 etc. and the child requirements (1.1, 1.2, etc.) have been dragged in the Project Browser as a subrequirement of the parent.
Now when that is done I found the following problems with the relationship matrix:
1. In the Source/Target Type combo box you can only select either Requirement or Feature but not both. This makes it difficult to consolidate the relations in one matrix.
2. In our case the Requirements is the target but I see that it only lists the parent requirements (REQ-1, REQ-2, REQ-3) and not the subrequirements (REQ-1.1, REQ-1.2, etc.). This makes it difficult to map items to subrequirements.
-
Hi Emilio,
Just to be clear... Have you tried this in EA 7.5 production (i.e. Build 843 or later)? Now that 7.5 is out there won't be further development of 7.1.
-
1. In the Source/Target Type combo box you can only select either Requirement or Feature but not both. This makes it difficult to consolidate the relations in one matrix.
You can also select <All>, although that may then list more than you want.
2. In our case the Requirements is the target but I see that it only lists the parent requirements (REQ-1, REQ-2, REQ-3) and not the subrequirements (REQ-1.1, REQ-1.2, etc.). This makes it difficult to map items to subrequirements.
Don't know if it will make a difference, but make sure that you have checked 'Include Source Children' and 'Include Target Children' in the options.
-
The company I work at is using v7.1 which was a refreshment of a previous license. We acquired v7.1 last year so I don't think they will buy 7.5 they way things are :(
As for the other reply, yes I had the Include Source Children and Include Target children options enabled in the R.M. options but that does not make any difference (or does not work as expected).
-
The company I work at is using v7.1 which was a refreshment of a previous license. We acquired v7.1 last year so I don't think they will buy 7.5 they way things are :(
As for the other reply, yes I had the Include Source Children and Include Target children options enabled in the R.M. options but that does not make any difference (or does not work as expected).
If you bought an upgrade last year, that includes a year of updates, including a new version if that is released during your release.
I think the children options apply to sub-packages. For me nested elements are included, so I'm not sure why they aren't for you.