Relationship Matrix revisited.

[Emilio]

There are some things that can certainly be improved in the Relationship Matrix.

1. A facility to export it in a friendly way. Sometimes the source/target is so big (complexity of designs) that it becomes very difficult to import that into a Word document. For example it would be nice to be able to break it up during export, perhaps even a transformation facility.

2. When you create a R.M. profile it is saved in your LOCAL version of the model. When your model is coupled to a version control system then that information is NOT stored there as part of the model. This leaves other designers with whom the model is shared to have to manually reconstruct the R.M. profiles. For that reason it would be nice if when you create a R.M. profile, the user is given an option whether the profile is LOCAL (not shared) or SHARED (saved together with the model in the version controlled repository).

I also wonder if imported UML Profiles are stored with the model in the Version Control system or just on the local repository.

[kevin c]

I'd like to second the point about the matrix export... System Architect (Old Telelogic product and now IBM product) does this and I have used this feature quite a bit to do "quick" edits...  I'd say the entire import/export process needs attention to make it easier to quickly modify large amounts of data.  Perhaps a "spreadsheet" view within EA to avoid the export?

There are some things that can certainly be improved in the Relationship Matrix.

1. A facility to export it in a friendly way. Sometimes the source/target is so big (complexity of designs) that it becomes very difficult to import that into a Word document. For example it would be nice to be able to break it up during export, perhaps even a transformation facility.

2. When you create a R.M. profile it is saved in your LOCAL version of the model. When your model is coupled to a version control system then that information is NOT stored there as part of the model. This leaves other designers with whom the model is shared to have to manually reconstruct the R.M. profiles. For that reason it would be nice if when you create a R.M. profile, the user is given an option whether the profile is LOCAL (not shared) or SHARED (saved together with the model in the version controlled repository).

I also wonder if imported UML Profiles are stored with the model in the Version Control system or just on the local repository.

[Eve]

I'd like to second the point about the matrix export... System Architect (Old Telelogic product and now IBM product) does this and I have used this feature quite a bit to do "quick" edits...  I'd say the entire import/export process needs attention to make it easier to quickly modify large amounts of data.  Perhaps a "spreadsheet" view within EA to avoid the export?

Just a question.  What is it you're hoping to achieve with a spreadsheet that isn't done with the current matrix?  (I already think of the matrix as a spreadsheet.)

[kevin c]

Copy/Paste row or column values, create row/column filters,  ability to use the keyboard to set a relationship (not have to right click).  One other feature I used a lot in Telelogic is that a link type could be more advanced than just source/target but could be defined as any object from a simple custom type (C/R/U/D) to an object (A source entity and target entity are joined by a role for example)..

I hope that helps..