Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

<<The name of the use case should be a concise verb phrase that captures the essence of the activity being described.  Example: "send a message", "authenticate to a service", "discover a transaction endpoint".>>

Description

<<Provide a description of the use case.>>

Actors

<<Provide a list of the actors, including what type of entity they are and what their role in the use case.>>

<<Should we consider including bad actors who do not do what they are "supposed to".>>

AliceA person who sends a message.
BobA person who receives a message.
MalA person who intercepts a message.

Prerequisites / Assumptions

<<Provide a description of all assumptions or prerequisites that need to be in place for the use case to be applicable or possible.>>

Use Case Steps/Sequence Diagram

<<Provide the list of steps.>>

1Alice sends Bob a Ressage.
2Bob thinks about it.
3Bob sends Alise a Response.

<<Do we want to use sequence diagrams?  There's a nice online tool here.>>

 

  • No labels