MagicGrid traceability subsystem at solution domain

Hi,

I have reading and using the MagicGrid BoK V2, I do have questions about satisfy traceability between textual requirements and model elements.

Below a capture from 3 different diagram from the MagicGrid BoK V2:

  • Satisfy traceability matrix between subsystem textual requirements and model elements on the left.
  • Subsystem textual requirements - top right.
  • Subsystem activity diagram, bottom -right.

The BoK example shows the satisfy traceability AND for behaviour should be done between call behaviour action and states, this matches the SysML standard.

For functional textual requirements.

  • Not all of them traced to call behaviour. Should they be as they capture functions (aka verbs) in the textual requirement?
  • Can a function (aka call behaviour action) within the swinlane have a satisfy traceability link to a functional textual requirement? I think functions within swinlanes are not for the system-of-interest, but convey that subsystems will have to refine further at lower layer. Hence, should it be traced to parent activity only?
  • If it was captured 10 functional textual requirements, should it be captured 10 call behaviour actions?

Thank you,

Hélder Castro

 

MagicGrid