Design – Build – Run: Applied Practices and Principles for Production-Ready Software Development

13.4. Documenting the Use Cases

This section wraps up this chapter by specifying the detailed use cases. The storyboards capture the application from the end user's perspective, and the requirements stipulate some processing rules. Now it is time to pull all this information together to give a more complete picture to continue with. The storyboards, requirements, and use cases will be used to further design, build, and test the application. The use cases capture as much information and detail as possible to refine the system and processing. They focus primarily on the main flow, although they do include the primary alternative flows. The use cases documented in this section also contain a "requirements map" section that lists the functional requirements associated with the use case. This really helps when defining the test cases and also ensures that the developer is fully aware of them. It is a good idea to have a set of agreed upon use cases to help with the furtherance of the project. Although the use cases might seem repetitive, they only help to ensure a common understanding of the functionality.

Once again, I'll start at the first storyboard and work around to each one. The commentary will be restricted to only where necessary, as the use cases should be fairly straightforward.

13.4.1. UC-001 Create New Account

The first use case in the series is the Create New Account use case (UC-001). This use case documents the functionality and processing required when users want to ...