Child pages
  • Use Case Template DG-BSC
Skip to end of metadata
Go to start of metadata

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


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

Champion / Stakeholder

<<Identify the champion(s) who will develop the use case, and stakeholder(s) with a tangible interest in the use case.>>


<<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

<<At the risk of being pedantic - sequence diagrams are farther down the development chain. Before we get there we should be able to articulate a use case using a use case diagram, n'est ce pas?

<<Provide the list of steps.>>

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

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

End State

Describe the end state or states at the end of the Use Case. If the use case proceeds as it is supposed to, what is the successful (and hopefully testable) end state. If the use case does not proceed, how does it fail?



  • No labels

1 Comment

  1. I add "End State" to the template. If this is a use case that describes how a process works, then the end state (success or failure) should be a describable state that can be used as input to a successor process or system.