Detail misuse cases   Jump to: navigation, search     •
Communicate potential risks to stakeholder.   • Communicate
rationale for security-relevant decisions to stakeholder.     •
Requirements Specifier     • As required; typically occurring
multiple times per iteration, and most frequently in Inception
and Elaboration iterations   Identify misuse cases  Misuse cases
are identical to use cases, except that they are meant to detail
common attempted abuses of the system. Like use cases, misuse
cases require understanding the actors that are present in the
system. Those actors should be mapped to capabilities, if
possible. Misuse cases should be designed for each actor, and
one should also consider uses cases for nefarious collaborating
actors.  As with normal use cases, one should expect misuse
cases to require adjustment over time. Particularly, it is
common to start with high-level misuse cases, and refine them as
the details of the system are better understood.  Determining
misuse cases generally constitutes