Author Topic: Relationship Matrix (Read 5150 times)

RedEric · « **on:** November 17, 2014, 08:46:14 pm »

I have imported via DOORS a set of requirements and was wondering if it is possible to create a link between the Requirements and Sequence Diagrams using the Relationship Matrix.

OpenIT Solutions · « **Reply #1 on:** November 17, 2014, 09:17:24 pm »

Hi,

I don't think you can form a relationship between a diagram and an element (ie a requirement) via the relationship matrix (or any other means).

You would have to create an element then add the sequence diagram to it as a child (composite) diagram. Then relate your requirement to this element.

Regards,

Jon.

qwerty · « **Reply #2 on:** November 17, 2014, 11:14:53 pm »

How can requirements appear in SDs??

q.

jfzouain · « **Reply #3 on:** November 18, 2014, 05:43:56 am »

If you drop the requirement imported (elements) to the Class (element-objects) inside the Sequence Diagram, you can see the link of the requirement inside the Class, go to Rules, Requirements.

Now you can create your Matrix, betwen those 2 packages (Requirement and Sequence).

You can only create the Matrix betweel elements of different Diagram, not the Diagram itself.

qwerty · « **Reply #4 on:** November 18, 2014, 08:06:18 am »

Does not work for me (V11). When I drag a requirement onto a SD I always get a lifeline. Either as instance or as object. Both does not make any sense,

q.

jfzouain · « **Reply #5 on:** November 18, 2014, 08:30:40 am »

After you create a Sequence Diagram by dragging classes to the Sequence Diagram as instance (creating your lifeline), then you drag your requirements to the Object Class, works for me in version 11.

qwerty · « **Reply #6 on:** November 18, 2014, 12:05:57 pm »

I see what you mean. But those "Internal Requirements" are actually responsibilities. Also you can not "see" them directly and they are not linked with a connector. I don't know why EA creates a responsibility with such a drag operation. There might be a reason. But finally I can't see how a requirement would appear in a SD in any way (to come back to the OP). A requirement can't lead to a design decision A must communicate with B because of this. No customer would ask "code a FOR loop and not a WHILE".

q.

jfzouain · « **Reply #7 on:** November 19, 2014, 01:58:05 am »

That is how you create the Relationship Matrix in EA, you drag it in top of the element, this is how is done when you want to create a Relationship Matrix between Requirements and Use Cases.
It works pretty nice.

Sparx Systems Forum

News: