It's been brought to our attention that the relationship shown at 2:38 is incorrect. Please disregard this example and refer to the correct book example provided at 3:28.
Why would I use the copy relationship? What is the purpose of copy-pasting the same requirement into a new element? Seems like it will just generate bloat
Good question, we'll lead with we don't often use the copy relationship for the bloating reason you mentioned. One reason to use the copy relationship is to enable the requirement to be located in two locations within the containment tree. This can be methodology driven. For example, we may have a system model and several subsystem models and system level requirements and subsystem level requirements. System level requirements live within the system model, and subsystem requirements live within their respective models. The system model can then project use the subsystem level projects. Some system level requirements will be copied and sent down to one specific subsystem requirements. There should be a copy relationship between the two requirements (the one at the system level in the system model and the requirement at the subysystem level within the project used subsystem model)
It's been brought to our attention that the relationship shown at 2:38 is incorrect. Please disregard this example and refer to the correct book example provided at 3:28.
Why would I use the copy relationship? What is the purpose of copy-pasting the same requirement into a new element? Seems like it will just generate bloat
Good question, we'll lead with we don't often use the copy relationship for the bloating reason you mentioned.
One reason to use the copy relationship is to enable the requirement to be located in two locations within the containment tree. This can be methodology driven.
For example, we may have a system model and several subsystem models and system level requirements and subsystem level requirements. System level requirements live within the system model, and subsystem requirements live within their respective models. The system model can then project use the subsystem level projects. Some system level requirements will be copied and sent down to one specific subsystem requirements. There should be a copy relationship between the two requirements (the one at the system level in the system model and the requirement at the subysystem level within the project used subsystem model)