To answer this question, we need to understand the concept of fault fixing and its associated cost. Let's go through each option to understand why it is correct or incorrect:
Option A) Is not important - This option is incorrect because the cost of fixing a fault is indeed important. Faults can lead to product failures, customer dissatisfaction, and additional expenses in the long run.
Option B) Increases as we move the product towards live use - This option is correct. As the product moves closer to live use, the cost of fixing a fault typically increases. This is because faults found during testing or in the early stages of development are generally easier and cheaper to fix compared to faults found in the later stages or after the product is already live.
Option C) Decreases as we move the product towards live use - This option is incorrect. The cost of fixing a fault usually increases rather than decreases as the product moves towards live use, as explained in Option B.
Option D) Is more expensive if found in requirements than functional design - This option is incorrect because it is not a general rule. The cost of fixing a fault can vary depending on various factors, including the complexity of the fault, the stage at which it is found, and the effort required to fix it. It is not necessarily true that faults found in requirements are always more expensive to fix than faults found in the functional design.
Option E) Can never be determined - This option is incorrect. While it may not be possible to determine the exact cost of fixing a fault in advance, it is generally possible to estimate the cost based on factors such as the time required, resources needed, and the impact of the fault on the product.
The correct answer is B) Increases as we move the product towards live use. This option is correct because the cost of fixing a fault typically increases as the product moves closer to live use.
