Question

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

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

Answer 1

The correct answer is B. That use case won't be implemented for months. It is important to prioritize use cases based on their urgency and impact on other system functions, user needs, business processes, and regulatory requirements.

Step-by-step explanation:

This is because setting a use case at high priority means that it should be implemented sooner rather than later. However, if a use case won't be implemented for months, it would not make sense to prioritize it at a high level.

For example, if there are other use cases that are more critical and need to be implemented sooner, it would be better to prioritize those first and then come back to the use case that won't be implemented for months. Additionally, it's important to consider user needs, business processes, and regulatory requirements when setting priorities for use cases. Use cases that are crucial for other system functions, requested by favored user class, enable core business processes, or are required for regulatory compliance should be given high priority.