Is the extended use case a required behavior?

Is the extended use case a required behavior?

• A. Yes
• B. No
• C. Optional
• D. Not specified

Answer: (B)

In use-case modeling, an extend relationship captures optional, conditional behavior that supplements a base use case. Because this extra behavior only happens under specific conditions and is not part of the base flow, it is not required. So the extended use case is not a required behavior. If you thought of it as optional, that aligns with the idea that extension occurs only when triggered, rather than being mandatory for every execution. The option implying it’s always performed would be incorrect, and saying it’s not specified would ignore how extensions are used to model optional paths.

In use-case modeling, an extend relationship captures optional, conditional behavior that supplements a base use case. Because this extra behavior only happens under specific conditions and is not part of the base flow, it is not required. So the extended use case is not a required behavior. If you thought of it as optional, that aligns with the idea that extension occurs only when triggered, rather than being mandatory for every execution. The option implying it’s always performed would be incorrect, and saying it’s not specified would ignore how extensions are used to model optional paths.