blocks|key|110712|text|流程图，不--+Sequence+diagrams，是的。我试着让他们保持在一个非常高的水平，以便快速地将想法传达给某人。我不会试图把每一个细节都弄清楚。如果它看起来很重要，我可能会补充另一个图来显示边缘情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|110713|它很适合作为草图进行交流--我认为它不适合作为规范(但可以很好地介绍详细的部分)|110714|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Sequence_diagram^0|8|H|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Flowcharts, no -- <a href="http://en.wikipedia.org/wiki/Sequence_diagram" rel="nofollow noreferrer">Sequence diagrams</a>, yes. I try to keep them at a very high-level to communicate the idea to someone quickly. I do not try to get every detail in. I might supplement with another diagram to show an edge case, if it seems important. 

It's great for communication as a sketch -- I think it's not right for a specification (but would be a good intro to a detailed section)

blocks|key|4311182|text|是的，我同意。重点是让您理解流程图，而不是暗示您应该将它们用于逐行代码覆盖。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4311183|老实说，除了演示，我不知道你为什么还要浪费时间在伪代码上，除非它是一些非常低级的编程。|4311184|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|$]]

Yeah, I agree. The point was to get you to understand flow charts, not to imply that you should use them for line-by-line code coverage.

I don't know why you'd even waste time with pseudo-code except for demonstration, honestly, unless it's some really low-level programming.

blocks|key|1411942|text|真实代码的假设和时间的流程图，从来没有(在30年内)被发现有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1411943|作为引出需求的辅助讨论……所以当我们在这里的时候，会发生什么？你怎么决定..。如果大于95%25，你会怎么做？可能会有帮助。某一类用户发现白板上的这样的图表很容易谈论。|1411944|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 charts for the ifs and whiles of real code, never (in 30 years) found useful.

As a discussion aid for elicitng requirements ... so when we're here, what could happen? ... how would you decide ... what would you do if it's > 95% ... Can be helpful. A certain kin d of user finds such diagrams on the whiteboard easy to talk about.

blocks|key|1411949|text|我觉得流程图中的细节并不是很有帮助。我在一张纸上使用UML风格的技术。在组设置中使用白板。中级类图和序列图对于组织您的想法和传达您的设计意图非常有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1411950|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|$]]

I don't find great detail in a flowchart to be very helpful. I use UML-style techniques on a sheet of paper. Use a whiteboard in a group setting. Mid-level class diagrams and sequence diagrams can be extremely helpful to organize your ideas and communicate your design intentions.

blocks|key|1094493|text|有时在白板上描述流程，但从来没有在实际的设计或文档中。我会更多地用“流程图”来描述它们，因为我并不总是对形状很挑剔。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1094494|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|$]]

Sometimes on a whiteboard to describe a process, but never in actual design or documentation. I'd describe them more as "flowchart-like" since I'm not always particular about the shapes.

blocks|key|4311302|text|老实说，我非常高兴我被要求随同流程图一起完成任何作业。它们让我从结构上思考，我所缺少的东西(也许，在一定程度上仍然缺乏)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4311303|因此，不要急于跳上“我要去弹三角钢琴”的潮流，流程图真的很管用。|4311304|我没有一次发现自己在非平凡的逻辑上有一点困难。在一张纸上以流程图的形式列出逻辑之后(需要几分钟)，我不可避免地变得清晰起来。|4311305|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|$]]

To be absolutely honest, I am extremely glad I was required to accompany any assignment with flowcharts. They made me think structurally, something I was lacking (and, perhaps, still lacking to a certain extent).

So don't be quick to jump on a "I'm off to play the grand piano" bandwagon, flowcharts really do work.

Not once did I find myself in a bit of a bind in non-trivial logic. After laying out the logic in the flowchart form on a sheet of paper (takes a couple of minutes), it all inevitably becomes clear to me.

blocks|key|1094583|text|我自己不用它们。但是一个偶尔编程的同事会这样做。对于他来说，这是一种非常方便的方式来记住他一年前编写的那个程序的细节。他不太会编程，所以学习序列图之类的东西对他来说是不值得的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1094584|这也是一种很难编程的人很容易读懂的图表类型。在他的位置上这是一个加分。|1094585|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|$]]

I don't use them myself. But a coworker who only programs every once in a while does. It's a very handy way for him to remember the nuts-and-bolts of that program he wrote a year ago. He doesn't do much programming, so it's not worth it for him to learn sequence diagrams and things like that. 

It's also the type of diagram that other pple that hardly ever program will be able to read easily. Which in his position is a plus.

blocks|key|110847|text|我们有一个内部应用程序，其中包含一些相当复杂的工作流程。流程图构成了系统这一部分规范的很大一部分。因此，是的，流程图是描述系统的有用工具。它们通常也被非技术人员理解，如果它们是用户需求的一部分，这是很有用的。不，我通常不会在非常低的级别上使用它们，也不会期望系统的一部分只通过流程图进行规范或记录。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|110848|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|$]]

We have an in-house application that has some fairly complex workflow in it. A flowchart forms a big part of the spec of this part of the system. So yes, Flowcharts are a useful tool for spec'ing a system. They are also normally understood by non-technical people which is useful if they are part of a user requirements. No, I would not normally use them at a very low level, nor would I expect part of a system to only be spec'ed or documented by flowcharts.

blocks|key|4311453|text|如果你有兴趣的话，TDD是一个很好的选择，可以用来编写具体的代码，而且它还有很多其他的好处。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4311454|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Test-driven_development^0|9|3|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<a href="http://en.wikipedia.org/wiki/Test-driven_development" rel="nofollow noreferrer">TDD</a> is a good option for nuts and bolts code, if you are so inclined, and it comes with a lot of other benefits.

blocks|key|4311506|text|我们有一个很大的有机增长的应用程序，几乎没有文档，所以使用流程图来记录应用程序中的组件已被证明对操作的业务方面非常有用，因为即使他们也不知道所有东西是如何组合在一起的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4311507|它们不是逐行级别的，但确实涵盖了业务逻辑的所有分支以及后续处理和输出(尽管不遵循严格的流程图规则-某些块描述了多个流程)。|4311508|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|$]]

We have a large organically grown application that has very little documentation, so using flow charts to document components within the application has proven very usefull to the business side of the operation, as even they don't understand how everything fits together.

They aren't at line by line level, but do cover all branches of business logic with the subsequent processing and outputs (although not following strict flow chart rules - some blocks describe multiple processes).

When in school it was often a requirement to flowchart the little programs that we wrote line for line.

Those flow charts tended, due to the size of the pictures, to be very large and were often tedious to draw.

It was always to such detail that you were essentially writing code anyway.

I use flowchart/UML style techniques to develop higher level things but when it gets down to actual loops and what not it seems like overkill. 

I will often pseudo-code more detailed algorithms but still not to the super fine grained point.

Is this just one of those things where in school things were so tiny there would be nothing else to 'Flow-Chart' so they had use do the minutia?

Does anyone actually use flowcharts for nuts and bolts code anymore?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

当我们在学校的时候，经常需要用流程图把我们逐行编写的小程序画出来。由于图片的大小，这些流程图往往非常大，绘制起来往往很繁琐。它总是如此详细，以至于你本质上是在写代码。我使用流程图/UML风格的技术来开发更高层次的东西，但是当它深入到实际的循环和其他东西时，它似乎有点过分了。我会经常伪代码，更详细的算法，但仍然不到超细粒...

问有没有人真的还在使用流程图来处理具体的代码？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问有没有人真的还在使用流程图来处理具体的代码？EN