Author Topic: Managing satisfy relationships  (Read 4508 times)

MaxBr

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Managing satisfy relationships
« on: January 09, 2014, 03:41:11 am »
Hi
I'm building a SysML requirements management model and have so far created a view containing all requirements. Furthermore, I created other diagrams modeling design elements of the system.

Now I'd like to create another view which displays the "satisfy" relationships between requirement and design elements.

While I could copy all the relationships and design elements into a new view I hope there is another niftier solution, maybe even dynamic when requirements are changed/added in the requirement view.

I'd appreciate any input on how to model such a thing. Thanks!

Helmut Ortmann

  • EA User
  • **
  • Posts: 970
  • Karma: +42/-1
    • View Profile
Re: Managing satisfy relationships
« Reply #1 on: January 09, 2014, 06:40:08 am »
Hi,

think about Relationship Matrix (View, Relationship Matrix).

As you requested it's dynamic.

Helmut
Coaching, Training, Workshop (Addins: hoTools, Search&Replace, LineStyle)

MaxBr

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Managing satisfy relationships
« Reply #2 on: January 09, 2014, 08:26:08 pm »
Thank you Helmut.
I was searching for a more visual solution, so I didn't think about the relationship matrix. But you are right, that provides exactly the information I am looking for.

BUt would it be possible to generate a diagram from the relationship matrix making it visually more appealing? While I appreciate the matrix representation I feel that visual blocks connected in a diagram might be even more comprehendible to the untrained eye.

Max

Helmut Ortmann

  • EA User
  • **
  • Posts: 970
  • Karma: +42/-1
    • View Profile
Re: Managing satisfy relationships
« Reply #3 on: January 09, 2014, 09:29:01 pm »
Hi Max,

there are of course other possible solutions to visualize traceability like:
  • Search / Query
  • Diagram maintained by an Addin

For special things diagrams are a good way to vizualize traceability. Good diagrams require some effort. Automatic mantained diagrams are often not really intuitiv.

In my opinion most users have no problems with Relationship Matrix and a few hand made diagrams for special tasks. It's like an Excel table.

Helmut

Coaching, Training, Workshop (Addins: hoTools, Search&Replace, LineStyle)

philchudley

  • EA User
  • **
  • Posts: 741
  • Karma: +20/-0
  • EA Consultant / Trainer - Sparx Europe
    • View Profile
Re: Managing satisfy relationships
« Reply #4 on: January 09, 2014, 09:46:14 pm »
You might try this

1) Create a new diagram (SysML Requirements will be fine)
2) Drag a Requirement element onto this diagram as a [highlight]link[/highlight]
3) Right-click the Requirement and choose [highlight]Insert Related Elements...[/highlight]

You should see a dialog listing all elements connected to this Requirement via the satisfy relationship

These can then be added to the diagram

You will need to tidy up the layout

Repeat the process for other Requirements

Please note, that although any new satisfy relationships between these Requirements and elements will be reflected on this diagram, any new Requirement or and new Element will not be added automatically, but will have to added using the process defined above.

Hope this helps

Cheers

Phil
Models are great!
Correct models are even greater!

MaxBr

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Managing satisfy relationships
« Reply #5 on: January 09, 2014, 09:58:11 pm »
Thanks a lot Helmut and Phil.

I guess inserting related elements is not too bad. Would it be possible to automate this for several requirements? Unfortunately, I have not too much experience with scripting or anything to that effect.

Anyway, you guys already were a great help!

Max

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +396/-301
  • I'm no guru at all
    • View Profile
Re: Managing satisfy relationships
« Reply #6 on: January 09, 2014, 10:03:21 pm »
You can automate quite a lot. I could think of some script that checks/creates a composite diagram for all requirements (of a package) looks for the requirement to appear in the middle and add all related elements.

q.