Doubt about CRUD Use Cases

Asked

Viewed 1,423 times

0

I have the following question about CRUD Use Cases:

It is said that you should not create several use cases representing each operation of the CRUD, and one should create only one use case for it, as explained in Level of detailing use cases. However, what if only the actor manager, for example, could have access to create and remove, as would be?

1 answer

3


The term is usually used keep up to indicate the CRUD’s, there are many ways to make use case, there is no right way. For cases like this I usually create the use case administer for example, extensions can be used for remove or add user use cases, but remember, the use case should not be complex.

Crud

I found this use case within the stackoverflow itself, I hope to have helped.

Browser other questions tagged

You are not signed in. Login or sign up in order to post.