在这种情况下我需要使用什么类型的 UML 图？
仅用于我的个人维基，我想绘制一个图表来显示如何通过几个消息队列处理消息。
（例如，xml 消息从 source1 发送到 Queue1，然后传递到系统，在该系统中消息被转换为另一种格式，并且...）
这里我需要什么样的 UML 图？ 另外，如何在 UML 中显示队列？
Just for my personal wiki, I want to draw a diagram that shows how a message is processed via a couple of Message Queues.
(Like, xml message comes from source1 to the Queue1, then it is passed to a system where the message is converted into another format and...)
What kind of UML diagram should I need here?
And additionally, how do I show a Queue in UML?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
顺序和时间最好在序列图中查看。此外，不同部分（源、队列）和参数之间的通信将是可见的。
队列只是一个对象（图顶部的方块）。
Order and time are best seen in an Sequence diagram. Also the communication between the different parts (source, queues) and parameters will be visible.
A queue is just an object (the squares at the top of the diagram).
序列图是一个不错的选择，但在用于与大量步骤交互时存在局限性。他们擅长描述单个操作的步骤，以便参与者与所需的行为相关。我尽量不让任何一个序列图占据超过一页的内容。如果我需要更多，我会将其分成两个单独的图表，因为我通常会由于调用深度而浪费空白，并且交互很快就会变得更难理解而不是更容易。
您可以使用两种类型的图表。在系统级图上，显示队列（或其主机）之间的交互，在序列图上显示单个主机内采取的步骤。
Sequence Diagrams are a good choice but they have limitations when used for interactions with a large number of steps. They excel at describing the steps to a single operation, such that the actors are related to the behavior required. I try not to left any single sequence diagram take up more than one page. If I need more, I break it up into two serarate diagrams because I'm usually wasting whitespace due to the calling depth and the interacting quickly becomes harder to understand instead of easier.
You might use two types of diagrams. On a system-level diagram, show the interaction between the queues (or their hosts), and on a Sequence Diagram show the steps taken within a single host.
我认为最好的东西是活动图。在我看来，这也是展示流程的最佳方式。序列图更难理解，而且有很多混乱（生命线），这只会困扰读者。有两个图表只会让事情变得复杂
I think that the best good is an activity diagram. In my view it is the best way too show process flow. Sequence diagrams are harder to understand and also has a lot of clutter (the lifelines) which just bother the reader. And having two diagrams just makes things complicated