Who is a stakeholder in a use case specification?

Who is a stakeholder in a use case specification?

• A. The designer
• B. The developer
• C. Someone or something with interest in the behavior of the system
• D. The tester

Answer: (C)

A stakeholder in a use case specification is anyone—person, group, or even another system—that has an interest in how the system behaves or what it delivers. That broad idea covers end users who will use the system, business sponsors and managers who rely on its outcomes, regulators who require compliance, and other systems that interact with it. The description “someone or something with interest in the behavior of the system” fits this definition exactly. The roles like designer, developer, or tester are part of building and verifying the system, but they are defined by their duties rather than by having a stake in how the system behaves.

A stakeholder in a use case specification is anyone—person, group, or even another system—that has an interest in how the system behaves or what it delivers. That broad idea covers end users who will use the system, business sponsors and managers who rely on its outcomes, regulators who require compliance, and other systems that interact with it. The description “someone or something with interest in the behavior of the system” fits this definition exactly. The roles like designer, developer, or tester are part of building and verifying the system, but they are defined by their duties rather than by having a stake in how the system behaves.