To answer this question, you need to understand the concept of software reliability measures and their relationship to testing.
Software reliability measures are used to assess the reliability or stability of a software system. These measures help determine when to stop testing and release the software.
Option A) Exercise system functions in proportion to the frequency they will be used in the released product - This option is the correct answer. When using software reliability measures, it is best to use test cases that mimic the frequency of system functions in the released product. By doing so, you can assess the reliability of the system based on its expected usage patterns.
Option B) Push the system beyond its designed operation limits and are likely to make the system fail - This option is incorrect. While it is important to test the system under stress or extreme conditions, this approach alone may not provide an accurate measure of software reliability. Testing beyond the designed operation limits may not reflect the actual usage of the system and may not provide a reliable indication of its stability.
Option C) Exercise unusual and obscure scenarios that may not have been considered in design - This option is incorrect. While it is important to test for unusual scenarios and edge cases, relying solely on these types of test cases may not provide a comprehensive measure of software reliability. It is best to focus on test cases that reflect the intended usage and frequency of system functions.
Option D) Exercise the most complicated and the most error-prone portions of the system - This option is incorrect. While it is important to thoroughly test complex and error-prone portions of the system, relying solely on these test cases may not provide an accurate measure of software reliability. It is best to consider the overall usage patterns and frequency of system functions when selecting test cases for software reliability measures.
The correct answer is A) Exercise system functions in proportion to the frequency they will be used in the released product. This option is correct because it ensures that the software reliability measures are based on the expected usage patterns and can provide a reliable indication of the system's stability.