简体   繁体   English

包括用例图 (UML)

[英]Include Use Case Diagram (UML)

I have seen many use case diagrams where a use case can be included to only 1 other use case, is this right or wrong?我看过很多用例图,其中一个用例只能包含在其他 1 个用例中,这是对还是错? I have the understanding that in order for a use case to be included, it must be included to minimum 2 other use cases to be considered.我的理解是,为了包含一个用例,它必须包含在至少 2 个其他要考虑的用例中。 If this is true(minimum 2 use case to be considered an include), if its just linked to 1 other use case, do i just use a normal association?如果这是真的(至少有 2 个用例被视为包含),如果它只是链接到其他 1 个用例,我是否只使用正常关联? thank you谢谢你

This is a recurring question and often interpreted the wrong way.这是一个反复出现的问题,并且经常被错误地解释。 Include does not mean "call" in a functional analysis sense.包含并不意味着功能分析意义上的“调用”。 It means "this is a use case which can optionally be included".这意味着“这是一个可以选择包含的用例”。 Eg if you have a tool box you sell with different tool sets (different licensing for software).例如,如果您有一个工具箱,您会随不同的工具集(软件的不同许可)一起销售。 When you model use cases you synthesize single actions in a form so they build a set that returns some value to the actor.当您对用例建模时,您在表单中合成单个动作,以便它们构建一个集合,向参与者返回一些值。 You will not divide pieces of value into smaller ones.您不会将价值分成更小的部分。

Use cases are about synthesis, not about analysis.用例是关于综合的,而不是关于分析的。 When your use case diagrams start resembling spider webs then your design is broken.当您的用例图开始类似于蜘蛛网时,您的设计就被破坏了。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM