Specification: Use cases for CRUD

Posted by Mario Ortegón on Stack Overflow See other posts from Stack Overflow or by Mario Ortegón
Published on 2010-03-15T15:49:48Z Indexed on 2010/03/15 16:09 UTC
Read the original article Hit count: 296

I am writing a Product requirements specification. In this document I must describe the ways that the user can interact with the system in a very high level. Several of these operations are "Create-Read-Update-Delete" on some objects.

The question is, when writing use cases for these operations, what is the right way to do so? Can I write only one Use Case called "Manage Object x" and then have these operations as included Use Cases? Or do I have to create one use case per operation, per object? The problem I see with the last approach is that I would be writing quite a few pages that I feel do not really contribute to the understanding of the problem.

What is the best practice?

© Stack Overflow or respective owner

Related posts about specifications

Related posts about use-case