I am writing a product requirements specification. In this document, I must describe how the user interacts with the system at a very high level. Some of these operations are “Create-Read-Update-Delete” for some objects.
The question is, when writing use cases for these operations, what is the correct way to do this? Can I write only one example of using “Manage object x” and then include these operations as “Use cases”? Or do I need to create one use case for each operation, for each object? The problem that I see with the latter approach is that I would write several pages that, in my opinion, really do not contribute to understanding the problem.
What is the best practice?
source
share