Remember, Chapter 12 talked about how Usability.gov provides some good information on use cases. They say that a use case is “a written description of how users will perform tasks on your” system. You are going to spend some more time examining use cases so you can become familiar with them and learn when it is a good time to use them.
Part of the reason for use cases is that usually people do not capture these types of ordered requirements when writing shall statements. Use cases help to fix this.
Also, as you have seen in Chapter 12, use cases are written in plain English, albeit they ...
