Which action links ExecutionLists to the relevant Requirements in Tosca?

Which action links ExecutionLists to the relevant Requirements in Tosca?

• A. Drag and drop the ExecutionLists to the relevant Requirements.
• B. Drag and drop the ExecutionLists to the relevant RequirementSet.
• C. Manually enter ExecutionList IDs in the Requirement.
• D. Create a new ExecutionList for each Requirement.

Answer: (B)

In Tosca, you link an ExecutionList to the set of requirements it should cover by dragging the ExecutionList onto the relevant RequirementSet. The RequirementSet acts as the grouping container for those requirements, so attaching the ExecutionList to it binds the entire set of requirements to that execution plan. This makes the test run apply to all requirements contained in that set, rather than just a single item. Dragging the ExecutionList to an individual Requirement would connect it to only that one item, not the whole group, which isn’t the intended way to map executions to the scope of work. Manually entering ExecutionList IDs isn’t a typical workflow in Tosca, and creating a new ExecutionList for each Requirement would fragment the linkage instead of leveraging the organized set.

In Tosca, you link an ExecutionList to the set of requirements it should cover by dragging the ExecutionList onto the relevant RequirementSet. The RequirementSet acts as the grouping container for those requirements, so attaching the ExecutionList to it binds the entire set of requirements to that execution plan. This makes the test run apply to all requirements contained in that set, rather than just a single item.

Dragging the ExecutionList to an individual Requirement would connect it to only that one item, not the whole group, which isn’t the intended way to map executions to the scope of work. Manually entering ExecutionList IDs isn’t a typical workflow in Tosca, and creating a new ExecutionList for each Requirement would fragment the linkage instead of leveraging the organized set.