1
Suggestions and Requests / Relationship Matrix
« on: November 01, 2006, 11:42:07 am »
Hi
Having recently discovered the relationship matrix, I wanted to suggest some features that I would find very helpful.
In many of our diagrams we will NOT be giving a name to decision nodes, it just clutters the diagram (we will use the "Guard" text of the connectors to reveal the decisions being made).
So when we look at the relationship matrix and list requirements with decisons, we find that all decisions look the same in the matrix (i.e. the have no "name" text).
This makes it very hard to see what a decision does unless we right-clikc on it in the matrix.
So looking for a given decision is very time consuming.
So
1. How about an option that lets us name elelments, but supress the displaying of the name in diagrams, for example we could then tell EA to "Supress the display of names for Decision elements" this would then lets us name them and see them easily in the matrix, yet not clutter our activity diagrams.
or
2. If an element (e.g Decision) has no "name" text, then in the matrix display its "Alias" (if it has one). This will let us use Alias as a means of identifying Decisions (and other elements) in the relationship matrix, but (since Alias does not appear in diagrams) avoid cluttering the diagrams.
Personally I think elements should be forced to have names and that they should also have an optional label text. It is this label text that would then be seen in diagrams.
The name can then be used to identify elelments as it is now, but not be used to label them in diagrams etc, it being optional for the user to give a label.
One can envisage a setting too "Use Name As Label" which could be applied to either individual elements or types (eg Decisions, Requirements etc).
With such a setting, we could have this set for all elements, yet disable it for Decisions, this would cause Decisions to appear unnamed in diagrams, the point here being that "Label" is the text displayed in diagrams.
If a user fills in Label property then it gets displayed in diagram else it doesnt. But if user does not fill in Label BUT DOES set "Use Name As Label" then the element will appear in diagrams with its name.
Something like this would decouple names and labels so we could always have and refer to name, yet control what is and isnt seen in diagrams.
Thx
Hugh
Having recently discovered the relationship matrix, I wanted to suggest some features that I would find very helpful.
In many of our diagrams we will NOT be giving a name to decision nodes, it just clutters the diagram (we will use the "Guard" text of the connectors to reveal the decisions being made).
So when we look at the relationship matrix and list requirements with decisons, we find that all decisions look the same in the matrix (i.e. the have no "name" text).
This makes it very hard to see what a decision does unless we right-clikc on it in the matrix.
So looking for a given decision is very time consuming.
So
1. How about an option that lets us name elelments, but supress the displaying of the name in diagrams, for example we could then tell EA to "Supress the display of names for Decision elements" this would then lets us name them and see them easily in the matrix, yet not clutter our activity diagrams.
or
2. If an element (e.g Decision) has no "name" text, then in the matrix display its "Alias" (if it has one). This will let us use Alias as a means of identifying Decisions (and other elements) in the relationship matrix, but (since Alias does not appear in diagrams) avoid cluttering the diagrams.
Personally I think elements should be forced to have names and that they should also have an optional label text. It is this label text that would then be seen in diagrams.
The name can then be used to identify elelments as it is now, but not be used to label them in diagrams etc, it being optional for the user to give a label.
One can envisage a setting too "Use Name As Label" which could be applied to either individual elements or types (eg Decisions, Requirements etc).
With such a setting, we could have this set for all elements, yet disable it for Decisions, this would cause Decisions to appear unnamed in diagrams, the point here being that "Label" is the text displayed in diagrams.
If a user fills in Label property then it gets displayed in diagram else it doesnt. But if user does not fill in Label BUT DOES set "Use Name As Label" then the element will appear in diagrams with its name.
Something like this would decouple names and labels so we could always have and refer to name, yet control what is and isnt seen in diagrams.
Thx
Hugh