The problem with using UML cases is that you have usage diagrams, but there is nothing specific in the text specification. When you follow a unified process (UP), which is the methodology of the creators of UML and uses UML very much, there is an activity called implementation of the use, which consists in determining use cases and, therefore, also scenarios. You can use any behavioral diagram for this. Sequence numbers, machine status diagrams, activity diagrams, communication diagrams, collaboration diagrams, communication overview diagrams and timing diagrams. Diagrams arenice, but sometimes until detailed description, it is often easier to use some simple text usage script usage scripts, for example. lookwhat promotes Alistair Cockburn. However, there are many other ways that have recently gained popularity, mainly through the Behavioral Management (BDD) approach. These are unofficial specifications written in natural language, having a structure that is supported by various tools that can help you generate acceptance tests for your requirements expressed in the specifications. See, for example, Cucumber or Fitnesse for more information.which can help you generate acceptance tests for your requirements expressed in specifications. See, for example, Cucumber or Fitnesse for more information.which can help you generate acceptance tests for your requirements expressed in specifications. See, for example, Cucumber or Fitnesse for more information.