Which test design technique is most appropriate for an item with the highest risk?

The rationale for selecting decision table testing for system testing when addressing an item with the highest risk lies in the technique’s ability to effectively handle complex scenarios that involve multiple inputs and varying conditions. Decision table testing allows testers to visualize and systematically evaluate different combinations of inputs and their corresponding expected outcomes. This is especially useful for high-risk items where ambiguous requirements or interactions may exist.

By using decision table testing, testers can ensure that all functional requirements are covered and that the system behaves correctly under various potential scenarios, which is crucial when the stakes are high. This systematic approach mitigates the risk of oversight in testing by making it clear which combinations of inputs need to be verified.

In the context of component testing, decision testing is appropriate as it evaluates the logical decisions within the application, ensuring each path through the code is executed and validated. This attention to decision points aids in identifying defects that could lead to significant issues, thus aligning well with a risk-based approach to testing.

Overall, the combination of decision testing at the component level and decision table testing at the system level represents a structured method for ensuring thorough coverage of risks, making it the optimal choice for high-risk items.