在 UML 组件图中呈现代理
在 UML 组件图上描述由代理、客户端和服务器（Web、SMTP、IMAP 等）组成的体系结构的最佳方法是什么？
组件之间应该使用什么类型的连接器，是否有一种方法可以表明，尽管客户端和服务器之间存在代理，但客户端仍然对服务器进行寻址，并且对代理并不真正感兴趣（这是特别相关的）如果代理是透明的）？
谢谢你！
What would be the best way for describing an architecture consisting of a proxy, a client and a server (Web, SMTP, IMAP etc) on a UML component diagram?
What kinds of connectors should be used between the components and is there is a way for showing that though there is the proxy between the client and the server, the client still addresses the server and is not really interested in the proxy (this is especially relevant if the proxy is transparent)?
Thank you!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
显示代理的最佳方法是使用构造型，用
<> 对其进行标记。每个人都知道代理是什么，所以这是相当安全的。除此之外，在类之间使用标准 UML 关联。如果您愿意，您还可以将代理和客户端放在一个正方形内，将服务器放在另一个正方形内，以便读者可以理解它们位于“不同”的位置。虽然不是标准 UML，但这将增强图表的语义。
The best way to show the proxy is to use stereotypes, marking it with
<<proxy>>. Everyone know what a proxy is so this is fairly failsafe.Other than that, use standard UML associations between the classes. If you want you can also enclose the proxy and the client inside a square and the server in another square so the reader can understand that they are located in "different" places. While not standard UML, this will enhance the semantics of your diagram.
代理是由（至少）两部分组成的抽象，即设备和软件。我同意代理构造型很有用，但我会将其应用于部署图上的节点和组件。在物理网络级别连接设备；逻辑网络级别（HTTP/SMTP/等）的节点和公开接口级别的组件。
A Proxy is an abstraction made up of (at least) two parts, the device and the software. I agree that a proxy stereotype would be useful but I would apply it to the node and the component on a deployment diagram. Connect the devices at the physical network level; nodes at the logical network level (HTTP/SMTP/etc) and components at the exposed interface level.