
new
In the following example, SysML suggests that ValueType1 tracesFrom Requirement1, and Requirement1 tracesTo ValueType1. ![]() However, PTC's usability studies have shown that Systems Engineers find this unintuitive, so PTC has decided that for the preceding example, ValueType1 tracesTo Requirement1, and Requirement1 tracesFrom ValueType1. Note that when a Requirement is shown on a diagram, you can show the TracesFrom compartment. |
Allocate (only if SysML Profile present) - the Allocate is owned jointly by the Trace and the associated item. The access permissions you have to an Allocate are determined by the access permissions you have to the item that is allocated from - you require write access to both items to create or delete an Allocate.
Problem (only if SysML Profile present)
Rationale (only if SysML Profile present)
Refine - the Refine relationship is owned jointly by the Trace and the associated item. The access permissions you have to a Refine relationship are determined by the access permissions you have to the refined item.
Satisfy (only if SysML Profile present) - the Satisfy relationship is owned jointly by the Trace and the associated Requirement. The access permissions you have to a Satisfy relationship are determined by the access permissions you have to the Trace.
Trace - the Trace relationship is owned jointly by the Trace and the associated item. The access permissions you have to a Trace relationship are determined by the access permissions you have to the item that is traced from.
Verify (only if SysML Profile present) - the Verify relationship is owned jointly by the Trace and the associated Requirement. The access permissions you have to a Verify relationship are determined by the access permissions you have to the Trace.