Question

Which is NOT a good reason to set a use case at high priority to implement?

A. It describes part of a core business process that the system enables.
B. A favored user class requested it.
C. Other system functions depend on its presence.
D. That use case won't be implemented for months
E. Many users will use it frequently.
F. It's required for regulatory compliance.

Answer 1

The correct answer is D. That use case won't be implemented for months.

Step-by-step explanation:

The correct answer is D. That use case won't be implemented for months. This is not a valid reason to set a use case at high priority because it does not prioritize the needs of the customers or the functionality of the system. Just because a use case won't be implemented for months does not mean it should be given high priority if it is not essential for the core business process, required by regulatory compliance, or if other system functions depend on its presence.