blocks|key|5546561|text|简而言之，流程图是一种表示算法或过程的图表类型，它将步骤显示为各种类型的框，并通过将这些步骤与箭头连接起来来排序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5546562|您还可以将流程图视为应用程序逻辑的流程流，同时在某种类型的事件流中连接组件。|5546563|📷|atomic|offset|length|5546564|类的构造函数呢，它们应该在流程图中显示吗？|blockquote|5546565|井类设计不是用流程图来完成的。通常，创建UML图是为了表示类图结构或高级应用程序设计。|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://i.stack.imgur.com/EyjsK.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|X|8|@]|9|@$G|Y|H|Z|1|10]]|A|$]]|$1|I|3|J|5|K|7|11|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|12|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T|U|-4]]]]

In short, a flowchart is a type of diagram that represents an algorithm or process, showing the steps as boxes of various kinds, and their order by connecting these with arrows.

You may also think of a flow chart as a process flow of application logic while connecting components in some type of flow of events. 

<img src="https://i.stack.imgur.com/EyjsK.png" alt="enter image description here">

<blockquote>
 What about the constructors of classes, they supposed to be shown in flowchart or not ?
</blockquote>

Well class design is not done by means of flow chart. Generally a UML diagram is created to present class diagram structure or high-level application design.

blocks|key|1447276|text|维基百科文章很好地涵盖了这一点。在积木下面查看；如果它不在那里，流程图就不会覆盖它。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1447277|流程图主要是为了说明一个包含算法(解决问题的配方)的过程。流程图说明了计算机为解决问题将采取的程序步骤。|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Flowchart|1|http://en.wikipedia.org/wiki/Flowchart#Flowchart_building_blocks^0|0|6|0|H|2|1|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@$A|P|B|Q|1|R]|$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]]|F|$G|$5|H|I|J|C|$K|L]]|M|$5|H|I|J|C|$K|N]]]]

The <a href="http://en.wikipedia.org/wiki/Flowchart" rel="nofollow">Wikipedia article</a> covers this pretty well. Look under <a href="http://en.wikipedia.org/wiki/Flowchart#Flowchart_building_blocks" rel="nofollow">building blocks</a>; if it's not there, a flowchart doesn't cover it.

Flowcharts are mostly meant to illustrate a process that embodies an algorithm (a recipe for solving a problem). The flowchart illustrates the procedural steps that the computer would take to solve the problem.

blocks|key|1447404|text|一般来说，所有输入(通过I/O框)、输出(通过I/O框)、处理(通过程序盒)和决策(通过钻石盒)应该反映在您的流程图中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1447405|说到事件，如果你愿意的话，你可以通过钻石盒把它们说出来。例如：|1447406|如果(用户/系统这样做)，那么|1447407|+do+this+|code-block|syntax|javascript|1447408|否则|1447409|+do+this+|1447410|对于构造函数，需要使用对象图。构造函数是类方法，其唯一目的是在实例化时将对象保持在有效状态。|offset|length|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Object_diagram^0|0|0|0|0|0|0|B|3|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|12|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|13|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|14|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|15|8|@]|9|@$Q|16|R|17|1|18]]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]]]

Generally speaking, all Inputs (via I/O box), Outputs (via I/O box), Processings(via Proceesing box) and Decisions (via Diamond box) should be reflected in your flowchart.

Talking about events, they can be depcited somewhat via the diamond box if you like. For example:

if (user/system does that) then 

<pre><code> do this 
</code></pre>

else 

<pre><code> do this 
</code></pre>

For constructors, you need to use <a href="http://en.wikipedia.org/wiki/Object_diagram" rel="nofollow">Object Diagram</a>. As constructors are class methods whose sole purpose is to keep the object in a valid state when instantiated.

blocks|key|1447460|text|不是故意相反，而是在回答这个问题时：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1447461|“流程图中必须反映哪些类型的流程？”|blockquote|1447462|我想答案不是他们中的任何一个。|1447463|流程图已经有很长时间了。对于开发人员来说，生产这些产品很费时，特别是在商业范围项目所需的数量方面。一旦开发人员开始对它们进行编码并集成在实现和测试过程中发现的逻辑，它们也有一个缺点:很快就过时了。|1447464|在与比尔·柯蒂斯博士+(他是SEICMM1.1的作者之一)和一个有软件过程和心理学(+PhD)背景的人的非正式对话中，他对我和其他人说，我们的图表依赖于高空间的人来理解它们，但是高空间的人可以很容易地从像伪代码这样的软件的文本表示中形成一幅心理图。|offset|length|1447465|大多数面向对象的方法都提倡将流程图和数据流图作为结构化编程甚至预结构化编程的构件。更有用的是一些技术，比如用替代流注释的用例。用例往往以描述某些条件的名义流开始，但控制流的分支不多。分支在其他情况下被涵盖，并且典型地为了简洁引用名义流，只强调了差异。考虑用例而不是流程图的另一个很好的理由是，它们可以很容易地包含尽可能多的文本，以保证清晰性，尽管除了最短的文本之外，所有的文本都会导致将文本优雅地滑动到流程图中的问题，再加上路由和其他手动操作，可能会占用大量的时间，有时会带来很好的好处，有时甚至没有。|entityMap|0|LINK|mutability|MUTABLE|url|http://www.informit.com/authors/bio.aspx?a=3D4B7BFF-7EF3-415F-BA98-907C19487E4F^0|0|0|0|0|2|8|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|W|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|X|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|Z|8|@]|9|@$K|10|L|11|1|12]]|A|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

Not to intentionally be a contrary, but in answer to the question:

<blockquote>
 "What types of processes have to be reflected in flowchart?"
</blockquote>

I think the answer is none of them.

Flow charts have been around a long time. For developers, they are time consuming to produce, particularly in the quantity that would be needed for a commercial scope project. They also have the disadvantage of going stale pretty fast once developers start coding to them and integrating logic discovered during implementation and test.

In casual conversation with <a href="http://www.informit.com/authors/bio.aspx?a=3D4B7BFF-7EF3-415F-BA98-907C19487E4F" rel="nofollow">Dr. Bill Curtis</a>, who was one of the authors of the SEI CMM 1.1 and a person with some background in software process and psychology (a PhD), he said to me and others that our diagrams depend on people being high-spatial to understand them, but people who were high-spatial could pretty easily form a mental picture from text representations of software like pseudo code.

Most of the object oriented methods advocate leaving behind flow charts and also data flow diagram as artifacts of structured programming and even pre-structured programming. More useful are techniques like use cases annotated with alternative flows. Use cases tend to start with a nominal flow that may describe some conditions, but not much branching of the control flow. Branching is covered in alternative cases, and typically references the nominal flow for brevity, accentuating only the differences. Another good reason to consider use cases instead of flow charts is that they can easily include as much text as is needed for clarity, although all but the shortest text can cause problems with gracefully sliding text into flow charts, and combined with routing and other manual manipulations, can eat up a lot of time, sometimes with good benefit, sometimes without.

In visual programming, there are many events which support our application tasks. So, along with user defined processes, should these also be in flowchart or not?

What about the constructors of classes, are they supposed to be shown in flowchart or not?

What types of processes have to be reflected in flowchart?

33 天实现自己的 AI 进化论？发文瓜分机械键盘、耳机等万元奖池！点击参加活动：<a href="https://cloud.tencent.com/developer/article/2503022" target="_blank">https://cloud.tencent.com/developer/article/2503022</a> 
 <img src="https://qcloudimg.tencent-cloud.cn/raw/01543e0407db10898a7ee9f420794432.jpg"/>

技术创作特训营有奖征文

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

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

腾讯云数据库专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云AI代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

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

在可视化编程中，有许多事件支持我们的应用程序任务。那么，随着用户定义的进程，这些是否也在流程图中？类的构造函数是怎样的，它们是否应该在流程图中显示？

问流程图中必须反映哪些类型的流程？
EN

回答 4

Software Engineering用户

Software Engineering用户

Software Engineering用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问流程图中必须反映哪些类型的流程？EN

回答 4

Software Engineering用户

Software Engineering用户

Software Engineering用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问流程图中必须反映哪些类型的流程？
EN