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.
