A business analyst (BA) is working on a payment system (PS) implementation. A set of systems which should interact with a new system has been identified. The business analyst defined that a user with role of
"Supervisor" in the PS must pass a two-factor authentication before an execution of the functions: "Change system parameters" and "Set up new supervisor." A user must have the role of "Supervisor" to use the standard functions "Send mail notification" or "Send SMS notification".
The BA defined the following use cases:
*"Change system parameters"
*"Setup new supervisor"
*"Send mail notification"
*"Send SMS notification"
*"Send notification"
*"Pass a two-factor authentication"
The BA wants to create a Use Case diagram.
What standard relationship should be defined between "Change system parameters", "Setup new supervisor" and "Pass a two-factor authentication"?


Correct Answer: D
Explanation
Option D shows the correct use of the include relationship between the three use cases. This means that the
"Pass a two-factor authentication" use case is a mandatory part of both the "Change system parameters" and the "Setup new supervisor" use cases, and it always occurs whenever either of them is executed. The arrow points from the base use case to the included use case, as per the UML notation. Option C is incorrect because it uses the protect relationship, which is a non-standard extension of the UML notation. It indicates that the
"Pass a two-factor authentication" use case is a security requirement for the other two use cases, but it does not specify how or when it is executed. Options A and B are incorrect because they use the extend relationship, which means that the "Pass a two-factor authentication" use case is an optional extension of the other two use cases, and it only occurs under certain conditions. This does not reflect the requirement that the two-factor authentication is mandatory for both functions. References:
[A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3], Chapter 10:
Techniques, pp. 424-425.
[UML 2.5 Specification], Chapter 18: Use Cases, pp. 637-638.