Use-Case Definitions
Recall that in Chapter 4 we defined many use-cases and then assigned them to one of three Remulak project increments. Providing for a more informed estimate while still at an early stage of the project requires an in-depth flyby of all the project's use-cases. At a minimum, before estimating a project, we must do the following:
1. | Identify events. |
2. | Identify use-cases. |
3. | Assign events to use-cases. |
4. | Identify happy paths for all use-cases. |
5. | Identify alternate pathways for all use-cases. |
6. | Produce detailed task steps for all use-case happy paths. |
7. | Assign use-cases to project increments (both use-cases and pathways may need to be assigned because they may be split across increments). |
8. | Describe in detail all use-case pathways ... |
Get Developing Applications with Java™ and UML now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
