我们是否将业务规则放入业务用例图中？
我想为特定问题绘制业务用例图。 这个问题有一定的规律。现在我想问的是： 绘制业务用例时放入业务规则是否正确？
I wanna to draw a business use case diagram for a specified problem.
The problem has some rules. Now I wanna to ask that:
Is it correct to put business rules when drawing business use case?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我想说的是，添加任何能让你的图表更容易理解的信息都是正确的。如果您找不到要包含的信息的正确图表项，请使用注释。
I would say that it is correct to add any information that makes your diagram easier to understand. If you can't find the proper diagram item for the information you want to include, use comments.
我同意@Konamiman 的观点，即我们“应该”对图表进行一些灵活性是合理的，我们的目标是沟通。在这种特殊情况下，我预计业务规则主要是系统的内部实现功能，因此当我们描述业务用例（系统如何使用）时，我们可能不需要提及它们。 “批准保险索赔”很可能是系统的一个用例，并且可能在内部使用业务规则，但是图表的读者需要知道这一点吗？
我可以想象您可能还有其他“更改业务规则”用例。
I agree with @Konamiman that some flexibility in what we "should" do with our diagrams is reasonable, our objective is to communicate. In this particular situation I would have expected Business Rules to be a largely internal implementation feature of a system and so when we describe the Business Use cases (how the system is used) we probably don't need to mention them. "Approve Insurance Claim" may well be a use case for the system, and probably uses Business Rules internally, but does the reader of the diagram need to know that?
I can imagine that you may have additional "Change Business Rule" use case.