To answer this question, you need to understand the concept of standards for physically connecting and transferring data between computers and peripheral devices.

Option A) Small Computer System Interface (SCSI) - This option is incorrect. SCSI is a set of standards for connecting and transferring data between computers and peripheral devices, but it does not match the given answer.

Option B) Small Connection System Interface (SCSI) - This option is correct. SCSI is a set of standards for physically connecting and transferring data between computers and peripheral devices. It provides a standard interface for connecting devices such as hard drives, tape drives, and scanners to a computer.

Option C) Secure Connection Server Interface - This option is incorrect. There is no standard called Secure Connection Server Interface related to physically connecting and transferring data between computers and peripheral devices.

Option D) Small Connection Sys Interface - This option is incorrect. It does not match the given answer and is similar to Option B, but with a different abbreviation.

The correct answer is B) Small Connection System Interface. This option correctly identifies the set of standards for physically connecting and transferring data between computers and peripheral devices.

• Thanks
• Wrong explanation

To answer this question, we need to understand the concepts of re-testing and regression testing.

Re-testing refers to running a test again to ensure that a specific issue or bug has been fixed. It involves re-executing the same test case that previously failed to verify if the fix has resolved the problem.

Regression testing, on the other hand, is the process of testing the unchanged parts of a software system to ensure that the modifications or bug fixes have not introduced any new defects or caused unexpected side effects. It aims to validate that the existing functionality has not been affected by the changes.

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

Option A) re-testing is running a test again; regression testing looks for unexpected side effects - This option is correct. It accurately describes the difference between re-testing and regression testing. Re-testing involves running a test again, while regression testing focuses on identifying unexpected side effects caused by changes.

Option B) re-testing looks for unexpected side effects; regression testing is repeating those tests - This option is incorrect. It incorrectly states that re-testing looks for unexpected side effects, which is the role of regression testing.

Option C) re-testing is done after faults are fixed; regression testing is done earlier - This option is incorrect. It incorrectly suggests that re-testing is performed after faults are fixed, while in reality, it is done to verify the effectiveness of the fix. Regression testing, on the other hand, can be performed at any stage of the development cycle to ensure that changes do not introduce new issues.

Option D) re-testing uses different environments, regression testing uses the same environment - This option is incorrect. The environment used for testing does not define the difference between re-testing and regression testing. Both types of testing can be performed in the same or different environments based on the specific requirements.

Option E) re-testing is done by developers, regression testing is done by independent testers - This option is incorrect. The responsibility for re-testing and regression testing can vary depending on the organization and the testing team. While developers may perform re-testing, independent testers can also be involved in both re-testing and regression testing.

Therefore, the correct answer is A) re-testing is running a test again; regression testing looks for unexpected side effects.

• Thanks
• Wrong explanation

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.

• Thanks
• Wrong explanation