Most people don't bother but doing a good job requires to think over basics and not adopt bad habits. This is quite challenging and I confess that sometimes I also fall back to Manage. So instead the reason why you manage something is the real use case (e.g. Share With Anyone Place your diagram in multiple locations, and all duplicates automatically update.
In many cases the focus on the real business was lost. Create and edit diagrams with your team in real time. Usually the "managing" itself is not directly business related. So when looking from a business perspective, a Login is not a use case, but a simple constraint (you can do the business relevant things only when you are logged in). You can constrain maintenance operations to certain actors separately.Įdit Regarding Login (one of my favorites): Use cases are most commonly used to describe business context (exactly as you are doing).
Also with CRUD use cases I would not separate them but have a Maintain instead (which itself is some borderline use case since maintaining something is not directly business relevant). But I guess one can understand what you are trying to communicate.Īs a side note: Login is not a business use case.
0 kommentar(er)
