blocks|key|4609096|text|你应该用你喜欢的任何东西。图表只是一个工具。使用任何最适合您和您的问题的工具。我通常只是使用方框、箭头、曲折、圆圈和小的杆状图形，以及任何我认为能让观众理解要点的东西。简而言之，即使你使用一个标准的图解标准也无关紧要。人们通常很擅长理解图片。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4609097|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|$]]

You should use whatever you like. The diagram is just a tool. Use whatever tool fits you and your problem best. I usually just use boxes and arrows and squiggles and circles and little stick figures and whatever else I think gets the point across to the viewer. In short it doesn't matter if you even use a standard diagraming standard. People are usually pretty good at understanding pictures.

blocks|key|543978|text|流程图详细说明了要遵循的流程。DFD详细说明了通过系统的数据流。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|543979|在流程图中，箭头表示元素之间的控制转移(而不是数据)，元素是指令或决策(或I/O等)。|543980|在DFD中，箭头实际上是元素之间的数据传输，而元素本身就是系统的一部分。|543981|维基百科上有一篇关于DFDs+here的好文章。|offset|length|543982|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Data_Flow_Diagram^0|0|0|0|F|4|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@$H|V|I|W|1|X]]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

A flow chart details the processes to follow. A DFD details the flow of data through a system.

In a flow chart, the arrows represent transfer of control (not data) between elements and the elements are instructions or decision (or I/O, etc).

In a DFD, the arrows are actually data transfer between the elements, which are themselves parts of a system. 

Wikipedia has a good article on DFDs <a href="http://en.wikipedia.org/wiki/Data_Flow_Diagram" rel="noreferrer">here</a>.

blocks|key|4609178|text|数据流程图显示了系统中不同实体和数据存储之间的数据流，而流程图显示了执行任务所涉及的步骤。从某种意义上说，数据流图提供了系统的一个非常高层次的视图，而流程图是一个较低层次的视图(基本上显示了算法)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4609179|是否使用数据流程图或流程图取决于您想要显示的是什么。|4609180|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|$]]

Data flow diagram shows the flow of data between the different entities and datastores in a system while a flow chart shows the steps involved to carried out a task. In a sense, data flow diagram provides a very high level view of the system, while a flow chart is a lower level view (basically showing the algorithm).

Whether you use data flow diagram or flow charts depends on figuring out what is it that you are trying to show.

blocks|key|3764834|text|数据流程图(DFD)和流程图(FC)之间的区别在于，数据流图通常描述系统内的数据流，而流程图通常描述业务流程的详细逻辑。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3764835|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 difference between a data flow diagram (DFD) and a flow chart (FC) are that a data flow diagram typically describes the data flow within a system and the flow chart usually describes the detailed logic of a business process.

blocks|key|3764765|text|数据流和流程图在流程、流程和时序上有所不同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3764766|3764767|Processes|ordered-list-item|offset|length|style|BOLD|3764768|3764769|a.)在DFD上，进程可以并行操作(同时)。|3764770|b.)在流程图上，进程一次执行一个。|3764771|3764772|3764773|Flow|3764774|3764775|a.)DFD显示通过系统的数据的流|3764776|b.)流程图显示了控制+(sequence++transfer+of+control)和的流程图|3764777|3764778|3764779|Timing|3764780|3764781|a.)DFD上的进程可能具有截然不同的时间(每天、每周、按需)|3764782|b.)流程图上的进程是具有一致计时的单个程序的一部分|3764783|entityMap^0|0|0|0|9|0|0|0|0|0|0|0|4|0|0|G|1|0|0|B|M|Q|0|0|0|0|6|0|0|0|V|0|0|Q|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1A|8|@$F|1B|G|1C|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1E|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1F|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|Q|3|R|5|E|7|1I|8|@$F|1J|G|1K|H|I]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1M|8|@$F|1N|G|1O|H|I]]|9|@]|A|$]]|$1|V|3|W|5|6|7|1P|8|@$F|1Q|G|1R|H|I]|$F|1S|G|1T|H|I]]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]|$1|Z|3|10|5|E|7|1W|8|@$F|1X|G|1Y|H|I]]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|20|8|@$F|21|G|22|H|I]]|9|@]|A|$]]|$1|14|3|15|5|6|7|23|8|@$F|24|G|25|H|I]]|9|@]|A|$]]|$1|16|3|-4|5|6|7|26|8|@]|9|@]|A|$]]]|17|$]]

Data Flow and Flow Chart differ in processes, flow, and timing.

<ol>
<li>Processes

a.) On DFDs, processes can operate in parallel (at-the-same-time).

b.) On flowcharts, processes execute one at a time.</li>
</ol>

<hr>

<ol start="2">
<li>Flow

a.) DFDs show the flow of data through a system

b.) Flowcharts show the flow of control (sequence and transfer of control)</li>
</ol>

<hr>

<ol start="3">
<li>Timing

a.) Processes on a DFD can have dramatically different timing (daily, weekly, on demand)

b.) 
Processes on flowcharts are part of a single program with consistent timing</li>
</ol>

blocks|key|1132934|text|DFD显示数据如何在系统中移动，流程图更接近系统执行的操作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1132935|在经典的make+a+cup+of+tea+example中，DFD将显示水、茶、牛奶和糖的去向，而流程图显示了过程。|offset|length|1132936|entityMap|0|LINK|mutability|MUTABLE|url|http://www.bbc.co.uk/schools/gcsebitesize/design/images/dt_mpm_sc8.gif^0|0|4|P|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]]]]

A DFD shows how the data moves through a system, a flowchart is closer to the operations that system does. 

In the classic <a href="http://www.bbc.co.uk/schools/gcsebitesize/design/images/dt_mpm_sc8.gif" rel="nofollow noreferrer">make a cup of tea example</a>, a DFD would show where the water, tea, milk, sugar were going, whereas the flowchart shows the process.

blocks|key|1138228|text|其他的答案已经过了每个东西是什么的基础。在更高的层次上，流程图是设计级的工具，而DFD是更多的分析。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1138229|DFD有一些很好的特性。因为它们显示了数据流，所以当以这种方式绘制图表时，一些事情变得更加明显:一些数据只由几个例程使用，一些例程只使用一些位数据，一些例程涉及所有内容。预先了解这一点有助于组织、重组和规划。|1138230|后续值得探索的是事件-响应图，它基本上是一个DFD，它只显示处理“事件”所需的流程和数据，这意味着外部触发的东西(客户付款等)。|1138231|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|$]]

Other answers have gone over the basics of what each thing is. At the higher level, a flowchart is a design level tool, while DFDs are more analysis.

DFDs have some nice features. Since they show the flow of data, some things become more obvious when charted this way: some data is only used by a few routines, some routines use only some bits of data, some routines touch everything. Seeing that up front helps organize, restructuring, and planning.

A follow-on worth exploring is the Event-Response Diagram, which is basically a DFD only showing process and data needed to process an "event", meaning something triggered externally (customer makes payment, etc.).

blocks|key|4609522|text|数据流图是一种函数关系，它包括输入值和输出值以及存储的内部数据。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4609523|流程图是包含输入值和输出值的过程关系。|4609524|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|$]]

A Data Flow Diagram is functional relationship which includes input values and output values
and internal data stored. 

A Flow Chart is a process relationship which includes input and output values.

blocks|key|4609260|text|流程图描述了程序(参见旧的fortran流程图-当然，google上也有一些流程图)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4609261|数据流程图确定数据的流动，例如，子例程之间或不同程序之间。|4609262|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|$]]

Flow chart describes the program (see old fortran flow charts - surely, there are some floating around on google).

Data flow diagram determines the flow of data, for example, between subroutines, or between different programs.

blocks|key|1133042|text|尽管我使用DFD图表的经验有限，但我可以告诉您，DFD向您展示了数据如何在各个模块之间移动(流动)。此外，DFD可以划分为不同的级别，即在您看到的系统的初始级别(例如，出租电影的系统)作为一个整体(称为上下文级)。该级别可以分解为另一个级别，其中包含活动(例如，租一部电影、还一部电影)以及数据如何流入这些活动(可以是名称、天数等)。现在，您可以为每个活动创建一个子层，详细说明这些活动的许多任务或场景。以此类推。请记住，数据总是在级别之间传递。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1133043|现在，关于流程图，只需记住流程图描述的是一个算法！|1133044|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|$]]

Although my experience with DFD diagrams is limited I can tell you that a DFD shows you how the data moves (flows) between the various modules. Furthermore a DFD can be partitioned in levels, that is in the Initial Level you see the system (say, a System to Rent a Movie) as a whole (called the Context Level). That level could be broken down into another Level that contains activities (say, rent a movie, return a movie) and how the data flows into those activities (could be a name, number of days, whatever). Now you can make a sublevel for each activity detailing the many tasks or scenarios of those activities. And so on, so forth. Remember that the data is always passing between levels.

Now as for the flowchart just remember that a flowchart describes an algorithm!

blocks|key|4609401|text|看一下这个网站|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4609402|http://yourdon.com/strucanalysis/wiki/index.php?title=Chapter_9#The_Flow|offset|length|4609403|它确实能帮助您理解什么是DFD|4609404|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|20|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

have a look to this site 

<a href="http://yourdon.com/strucanalysis/wiki/index.php?title=Chapter_9#The_Flow" rel="nofollow noreferrer">http://yourdon.com/strucanalysis/wiki/index.php?title=Chapter_9#The_Flow</a> 

its really help u to understand what is DFD

blocks|key|1138298|text|上面的答案已经解释过了，但我会试着稍微扩展一下……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1138299|关于这杯茶的观点很好。流程图关注的是任务的物理方面，因此它被用来表示当前为的东西。这在了解情况/交流/培训等方面很有用，如果他们采用了ISO9000标准，etc..You可能会在你的工作场所遇到这些问题。|1138300|数据流图与活动的逻辑方面有关，因此茶的比喻也是一个很好的比喻。如果您将数据流程图与流程流结合使用，则您的数据流将只关注与流程相关的数据/信息流，而不考虑物理方面。如果你想知道为什么这将是有用的，那么它是因为数据流图允许我们从“它是”的情况中移动，并看到它可能/将会是什么。这两种建模方法在结构化分析和设计中很常见，通常由系统/业务分析人员作为业务流程改进/重新设计的一部分使用。|1138301|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|$]]

Between the above answers its been explained but I will try to expand slightly...

The point about the cup of tea is a good one. A flow chart is concerned with the physical aspects of a task and as such is used to represent something as it is currently. This is useful in developing understanding about a situation/communication/training etc etc..You will likley have come across these in your work places, certainly if they have adopted the ISO9000 standards.

A data flow diagram is concerned with the logical aspects of an activity so again the cup of tea analogy is a good one. If you use a data flow diagram in conjunction with a process flow your data flow would only be concerned with the flow of data/information regarding a process, to the exclusion of the physical aspects. If you wonder why that would be useful then its because data flow diagrams allow us to move from the 'as it is' situation and see it that something as it could/will be. These two modelling approaches are common in structured analysis and design and typically used by systems/business analysts as part of business process improvement/re-engineering.

blocks|key|4609482|text|数据流图:表示系统功能分解的建模符号。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4609483|流程图:程序的一步一步的流程。|4609484|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|$]]

Data flow diagram: A modeling notation that represents a functional decomposition of a system.

Flow chart: Step by step flow of a programe.

blocks|key|3764957|text|数据流图正式的结构化分析方法使用数据流图(DFD)来辅助功能分解过程。我从DeMarco+7中学习了结构化分析技术，这些技术代表了当前的约定。总而言之，DFD由四个组件组成：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3764958|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|$]]

Data Flow Diagrams
The formal, structured analysis approach employs the data-flow diagram (DFD) to assist in the functional decomposition process. I learned structured analysis techniques from DeMarco [7], and those techniques are representative of present conventions. To summarize, DFD's are comprised of four components:

I want to know why we use Data Flow Diagrams instead of flow charts.

What is the difference between a data flow diagram and a flow chart?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

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

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

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

社区新版编辑器体验调研

我想知道为什么我们使用数据流程图而不是流程图。

问数据流程图和流程图有什么区别？
EN

回答 14

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问数据流程图和流程图有什么区别？EN

回答 14

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问数据流程图和流程图有什么区别？
EN