RIDDL Documentation
Toggle Dark/Light/Auto modeToggle Dark/Light/Auto modeToggle Dark/Light/Auto modeBack to homepage


An epic in RIDDL is a definition that defines a large user story with a set of use cases. This is the same concept as the idea Kent Beck introduced in 1997. In RIDDL, a story gets a little more involved than the usual formulations of a user story:

As an {actor}, I would like {capability}, so that {benefit}


In order to receive {benefit}, as an {actor}, I can {capability}

which have these three ideas:

  • An actor that provides the role played by the narrator of the story
  • A capability that provides the capability used by the narrator
  • A benefit that provides the reason why the narrator wants to use the capability

A RIDDL Story also provides a set of cases that relate the story to other RIDDL components through the steps taken for each [case](/concepts/case/. Each case specifies a set of interactions that define and label the interactions between other RIDDL definitions such as elements, entities, and projections. Cases can also define
examples, to outline user acceptance testing.

Stories are designed to produce sequence diagrams. This allows the intended interaction of some actor (human or not) with the system being designed in RIDDL to support a detailed definition of a user story.

Occurs In