分解用例建模中的 CRUD [英] Breaking down CRUD In Use Case Modeling

问题描述

我有一个来自

解决方案

这很好.<> 表示扩展 UC 是可选的.

附带说明:避免 <> 和 <> 因为它们是功能分解的标志.这不是您应该对用例合成做的事情.然而，CRUD 是一个临界案例.所以，这应该没问题.

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?

解决方案

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.

这篇关于分解用例建模中的 CRUD的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！