![]() ![]() ![]() 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. The result is often better with this direction. So, it is an unfortunate quandary what kind of UML diagrams use case diagrams are. You may change to left to right using the left to right direction command. UML 2.5 FTF - Beta 1 moved use cases out of behavior modeling to UML supplementary concepts. startuml 'default top to bottom direction user1 -> (Usecase 1) user2 -> (Usecase 2) enduml. So instead the reason why you manage something is the real use case (e.g. The general default behavior when building diagram is top to bottom. In many cases the focus on the real business was lost. 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 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |