blocks|key|643122|text|这在很大程度上取决于您的需求；我对您的示例的直觉是，您应该这样做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|643123|您如何显示它也取决于您的需求。如果需要在数字屏幕上显示订单总数，请包括数字屏幕。如果该部分未指定(例如，可能是收据、语音输出、解释性舞蹈)，则只需说"show+order+total+(以某种方式)“。它可以像一个带标签的盒子一样简单，或者，如果你的工具允许的话，一个看起来像数字屏幕的对象。|643124|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

That depends largely on your requirements; my gut feeling for your example is yes you should.

How you show it also depends on your requirements. If it is necessary to show the order total on a digital screen, include the digital screen. If that part is unspecified (i.e. could be receipt, voice output, interpretive dance) then you just say "show order total (somehow)". It could be as simple as a labelled box or, if your tool lets you, an object that looks like a digital screen.

blocks|key|5107825|text|不，你不应该这样做。有几个原因。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5107826|5107827|用例通常用于传达功能需求。需求应该与解决方案无关。他们应该概述一个系统应该做什么，而不是“如何做”。如果您有一个必须操作的给定接口，那么您应该将其记录为约束，而不是用例。参见A.Cockburn，Writing+Effective+Use+Cases，第191页“修复的错误:太多的用户界面details"|ordered-list-item|5107828|Use案例从用户的角度描述了与系统的交互”(+system+:+Too+many+interface+cases+)。您可能希望将系统也包括为参与者；但是仍然...：|offset|length|style|BOLD|5107829|...你描述的用例可能太细粒度了。参见A.+Cockburn，“编写有效的用例”，第192页，“错误修复:非常低的目标水平”|5107830|5107831|如果您仍然希望在用例图中突出显示该方面(根据您的需要，这可能是有用的)，那么可以考虑将用例命名为"verify+order+total“，并将其分配给您的主要参与者。对于子函数级别来说，这将是非常好的。|5107832|entityMap^0|0|0|0|M|1P|0|0|1Q|0|0|0|2T|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|V|8|@$H|W|I|X|J|K]]|9|@]|A|$]]|$1|L|3|M|5|E|7|Y|8|@$H|Z|I|10|J|K]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|12|8|@$H|13|I|14|J|K]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|R|$]]

No, you should not. For several reasons.

<ol>
<li>Use cases are typically used to convey functional requirements. Requirements should be solution-independent. They should outline "what" a system should do but not "how". If you have a given interface that you must operate with, then you'd document that as a constraint, not as a use case. See A. Cockburn, Writing Effective Use Cases, p. 191 "Mistakes Fixed: Too many user interface details"</li>
<li>Use cases describe the interaction with a system from a user's point of view. You may want to include the system as an actor as well; but then still...:</li>
<li>... the use case you describe would probably be too fine grained. See A. Cockburn, Writing Effective Use Cases, p. 192 "Mistakes Fixed: Very low goal levels"</li>
</ol>

If you still want to highlight that aspect in your use case diagram (which can be useful depending on your needs) then consider naming the use case "verify order total" and assign it to your primary actor. IMO that would be perfectly fine for a subfunction level.

blocks|key|1757864|text|您概述的需求应该包含在用例本身中，或者作为活动图的一部分，活动图“分解”每个用例。在用例图上显示如此详细的需求是不合适的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1757865|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The requirement you outline should either be included in the Use Case itself or as part of an Activity Diagram which 'explodes' each Use Case. It is not appropriate to show such a detailed requirement on a Use Case diagram

My system is a soda can machine. You can put a coin and buy soda from this machine. The interface is a keypad and digital screen. 

One of my requirements is that the user can put x dollars into machine and then add items to his order. Then, the machine will show him the order total. 

That is, "show user order total"
Should I show this in my use case diagram? If yes, then how do i show it?

Should interface be part of a system in use case diagram?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我的系统是一台汽水罐装机。你可以投一枚硬币，然后从这台机器上买汽水。界面是键盘和数字屏幕。我的一个需求是，用户可以将x美元放入机器中，然后将商品添加到他的订单中。然后，机器会向他显示订单总数。也就是说，"show user order total“我应该在我的用例图中显示它吗？如果是，那么我如何显示它？

问在用例图中，接口应该是系统的一部分吗？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在用例图中，接口应该是系统的一部分吗？EN