To answer this question, we need to understand what makes a requirement testable. A testable requirement is one that can be objectively verified or validated through testing.

Let's go through each option to understand why it is correct or incorrect:

Option A) The system shall be user friendly - This requirement is not testable because "user friendly" is a subjective term and can vary from person to person. It is difficult to measure or quantify what makes a system "user friendly."

Option B) The safety-critical parts of the system shall contain 0 faults - This requirement is not testable because it is practically impossible to guarantee that there will be zero faults in any system. Even with extensive testing, it is unlikely to achieve a fault-free system.

Option C) The response time shall be less than one second for the specified design load - This requirement is testable because it provides a clear and measurable criterion. The response time can be objectively measured and compared against the specified limit of one second.

Option D) The system shall be built to be portable - This requirement is not testable because "portable" is a vague term and can be interpreted in different ways. It does not provide any specific criteria or measurable attributes to determine if the system is portable or not.

The correct answer is Option C. This option is testable because it provides a clear and measurable criterion for the response time of the system.

• Thanks
• Wrong explanation

To estimate the amount of re-testing likely to be required, you can consider a combination of factors. Let's go through each option to understand why it is correct or incorrect:

Option A) Metrics from previous similar projects - This option is correct because analyzing metrics from previous similar projects can provide insights into the amount of re-testing that may be required. By studying historical data, you can identify patterns and trends that can help estimate the effort needed for re-testing.

Option B) Discussions with the development team - This option is correct because engaging in discussions with the development team can provide valuable information about the changes made to the software, any known issues, and potential areas that may require re-testing. The development team's expertise and insights can help in estimating the amount of re-testing needed.

Option C) Time allocated for regression testing - This option is incorrect because while the time allocated for regression testing is a factor to consider, it alone may not provide a comprehensive estimation of the amount of re-testing required. The time allocated can vary based on project constraints and timelines, but it may not accurately reflect the actual effort needed for re-testing.

Option D) a&b - This option is correct because both metrics from previous similar projects and discussions with the development team are important factors in estimating the amount of re-testing likely to be required. By combining historical data and insights from the development team, you can make a more informed estimation.

The correct answer is D. This option is correct because both metrics from previous similar projects and discussions with the development team are valuable sources of information for estimating the amount of re-testing likely to be required.

• Thanks
• Wrong explanation