Zig-Zag Pattern in SAF?
parkaneric opened this issue · comments
A question came up when we discussed the VPs System Functional Breakdown whether or not we have a functional tree down through several system layers (system -> sub-system -> module):
Should SAF concept highlight derived requirements in the next layer below from system architecture decisions made?
Example: VP SAF_LogicalInternalExchange defines the exchange between elements within SoI.
Thus, in the sub-system layer a requirement has to be elicited to adress and ensure this architecture decision. An according traceability is required which is not available in SAF concept yet.