Breaking down CRUD In Use Case Modeling

自古美人都是妖i 提交于 2019-12-24 04:09:07

问题


I have a follow up question from CRUD in a use-case diagram?

If i am required to break down complex use case such as "Manage User" (Let's assume this is complex), would it be alright to extend them into different cases? Or should i use include?


回答1:


This is fine. <<extend>> means that the extending UC is optional.

As a side note: avoid <<extend>> and <<include>> since they are a sign of functional decomposition. And that's not what you are supposed to do with use case synthesis. CRUD however is a borderline case. So, this should be fine.



来源:https://stackoverflow.com/questions/41550770/breaking-down-crud-in-use-case-modeling

标签
易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!