blocks|key|4552039|text|这两个图提供了相同的信息，但是序列图在其布局中强调时间，而通信图在其布局中强调正在通信的对象。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4552040|时间在序列图中是隐含的(它是通过垂直位置推断的)，而它在通信图中是显式给出的(通过数字)。|4552041|引用Scott+Ambler|offset|length|4552042|4552043|通信图和序列图之间的主要区别在于，序列图擅长显示顺序逻辑，但不太擅长为您提供“全景图”，而通信图正好相反。|blockquote|4552044|4552045|entityMap|0|LINK|mutability|MUTABLE|url|http://www.agilemodeling.com/artifacts/communicationDiagram.htm^0|0|0|2|C|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@$F|X|G|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|11|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

Both diagrams give the same information, but the sequence diagram emphasizes time in its layout and the communication diagram emphasizes the objects that are communicating in its layout.

Time is implicit in sequence diagrams (it is inferred by vertical position), while it is given explicitly in communication diagrams (via numbers).

To quote <a href="http://www.agilemodeling.com/artifacts/communicationDiagram.htm" rel="noreferrer">Scott Ambler</a>

<blockquote>
 The main difference between communication diagrams and sequence diagrams is that sequence diagrams are good at showing sequential logic but not that good at giving you a “big picture view” whereas communication diagrams are the exact opposite.
</blockquote>

blocks|key|5968270|text|下面的链接是对序列图和通信之间区别的简短回答。请参考。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5968271|difference+between+sequence+diagram+and+communication|offset|length|5968272|entityMap|0|LINK|mutability|MUTABLE|url|http://www.uml-diagrams.org/sequence-diagrams-questions-answers.html^0|0|0|1H|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

The below link is the short answer for difference between sequence diagram and communication.
Please refer it.

<a href="http://www.uml-diagrams.org/sequence-diagrams-questions-answers.html" rel="nofollow">difference between sequence diagram and communication</a>

blocks|key|1837294|text|序列图以一种栅栏格式说明交互，在这种格式中，每个新对象都被添加到右侧。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1837295|这在代码中可能代表什么？可能，类A有一个名为doOne的方法和一个类型B的属性。此外，类B还有名为doTwo和doThree的方法。也许A类的部分定义是：|1837296|public+class+A
+++{
+++private+B+myB+=+new+B();

+++public+void+doOne()
+++{
+++myB.doTwo();
+++myB.doThree();
+++}
+++//+.+.+
+++}|code-block|syntax|javascript|1837297|通信图以图形或网络格式说明对象交互，其中对象可以放置在图上的任何位置(其墙体草图优势的本质)。|1837298|序列图与通信图的优缺点是什么？|1837299|每种图表类型都有自己的优势，建模师也有独特的偏好--没有绝对“正确”的选择。然而，UML工具通常强调序列图，因为它们具有更大的符号功能。|1837300|序列图比通信图有一些优势。也许最重要的是，UML规范更加以序列图为中心--在符号和语义上投入了更多的精力和精力。因此，更好的工具支持和更多的符号选项可用。此外，使用序列图更容易看到调用流序列--只需从上到下阅读即可。对于通信图，我们必须读取序列号，例如"1:“和"2:”。因此，序列图非常适合用于文档编制或轻松读取反向工程的调用流序列，这些调用流序列是使用UML工具从源代码生成的。|1837301|但另一方面，通信图在应用"UML+as+sketch“在墙上绘制(一种敏捷建模实践)时具有优势，因为它们更节省空间。这是因为方框可以很容易地放置或擦除任何地方-水平或垂直。因此，使用通信图修改墙壁草图也更容易-(在创造性的高变化OO设计工作期间)在一个位置擦除一个框，在其他地方绘制一个新框，然后在它上面画一条线。相反，序列图中的新对象必须总是添加到右边，这是有限制的，因为它会快速消耗和耗尽页面(或墙壁)上的右边空间；垂直维度上的自由空间没有得到有效利用。与通信图相比，在墙上做序列图的开发人员很快就会感受到绘制的痛苦。|1837302|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

Sequence diagrams illustrate interactions in a kind of fence format, in which each new object is added to the right. 

What might this represent in code? Probably, that class A has a method named doOne and an attribute of type B. Also, that class B has methods named doTwo and doThree. Perhaps the partial definition of class A is: 

<pre><code>public class A
 {
 private B myB = new B();

 public void doOne()
 {
 myB.doTwo();
 myB.doThree();
 }
 // . . 
 }
</code></pre>

Communication diagrams illustrate object interactions in a graph or network format, in which objects can be placed anywhere on the diagram (the essence of their wall sketching advantage). 

What are the Strengths and Weaknesses of Sequence vs. Communication Diagrams?

Each diagram type has advantages, and modelers have idiosyncratic preference—there isn't an absolutely "correct" choice. However, UML tools usually emphasize sequence diagrams, because of their greater notational power. 

Sequence diagrams have some advantages over communication diagrams. Perhaps first and foremost, the UML specification is more sequence diagram centric—more thought and effort has been put into the notation and semantics. Thus, tool support is better and more notation options are available. Also, it is easier to see the call-flow sequence with sequence diagrams—simply read top to bottom. With communication diagrams we must read the sequence numbers, such as "1:" and "2:". Hence, sequence diagrams are excellent for documentation or to easily read a reverse-engineered call-flow sequence, generated from source code with a UML tool. 

But on the other hand, communication diagrams have advantages when applying "UML as sketch" to draw on walls (an Agile Modeling practice) because they are much more space-efficient. This is because the boxes can be easily placed or erased anywhere—horizontal or vertical. Consequently as well, modifying wall sketches is easier with communication diagrams—it is simple (during creative high-change OO design work) to erase a box at one location, draw a new one elsewhere, and sketch a line to it. In contrast, new objects in a sequence diagrams must always be added to the right edge, which is limiting as it quickly consumes and exhausts right-edge space on a page (or wall); free space in the vertical dimension is not efficiently used. Developers doing sequence diagrams on walls rapidly feel the drawing pain when contrasted with communication diagrams.

blocks|key|4552167|text|强调消息的时间排序(使用序列图)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4552168|强调交互对象之间的结构关系(使用通信图)。|4552169|参考:UML用户手册|4552170|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

emphasizing the time ordering of messages (using sequence diagrams) 

emphasizing the structural relationships among the objects that interact (using communication diagrams).

reference :UML user manual

blocks|key|1837324|text|面向对象设计中的一个基本规则是根据不同的目的使用不同的图表。在这一点上，序列图用于建模顺序逻辑，同时显示几个对象协作以实现共同目的的行为。可以使用通信图，以前在UML1.x中称为协作图。-阅读更多>>+here+<<和>>+here+<<|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1837325|entityMap|0|LINK|mutability|MUTABLE|url|http://www.agilemodeling.com/artifacts/communicationDiagram.htm#sthash.nqqQjdHp.dpuf|1|http://www.cs.cityu.edu.hk/~wkchan/content/communication-diagram-vs-sequence-diagram-vs-state-machine-diagram^0|2Q|A|0|31|A|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

A fundamental rule in Object Oriented Design is to use different diagrams based on diverse purposes. In this regard, sequence diagrams are used to model sequential logic while to show the behavior of several objects collaborating together to fulfill a common purpose the communication diagrams, formerly known as collaboration diagrams in UML 1.x, can be used. - Read more <a href="http://www.agilemodeling.com/artifacts/communicationDiagram.htm#sthash.nqqQjdHp.dpuf" rel="nofollow">>> here &lt;&lt;</a> and <a href="http://www.cs.cityu.edu.hk/~wkchan/content/communication-diagram-vs-sequence-diagram-vs-state-machine-diagram" rel="nofollow">>> here &lt;&lt;</a>

Could anyone explain me what is the difference between sequence diagram and communication diagram?

What is the difference between sequence diagram and communication diagram?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

谁能给我解释一下序列图和通信图的区别？

问序列图和通信图有什么区别？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问序列图和通信图有什么区别？EN