I'm struggling a bit with modeling of smart use cases. The system we intend to develop uses reference data, in this case a list of products. Maintaining the products is straightforward, and I was initially tempted to model it in CRUD (Create, Read, Update, Delete) fashion, but did not go into that direction after finding out that this is not recommended in use cases.

Question is, however: how do you properly model trivial functionality like maintaining reference data using smart use cases? I now have a single use case called Manage Products that describes the standard Create flow, with the Read, Update and Delete flows as alternative flows. But I'm not sure whether this is sufficient. What, for instance, if the number of products is large and you require search functionality: I guess this would validate an additional use case Search Products?

Any feedback is appreciated. Would also be great to see more smart use case examples on the ADP website, it would greatly help in understanding the methodology.

Thanks for the response. I would still appreciate to see some example smart use cases, which would greatly extend the comprehensibility of the methodology. I've taken Sander Hoogendoorn's smart use cases course, but would like to learn by example to put it in practice. Is it possible to share some smart use cases?