在开始编码之前思考和分析软件 [英] thinking and analysis software before start coding

问题描述

是否有任何程序用于思考和分析程序。在开始编码和设计软件之前？

Is there any kind of program for thinking and analysis of a program. before start coding and design a software?

推荐答案

您是否尝试过谷歌 [ ^ ]？不确定您正在寻找什么......您是否正在寻求有关实体关系图 [ ^ ]？或屏幕模型 [ ^ ]？我没有尝试过任何这些，但看起来他们可能会有所帮助，这取决于你真正想要的东西。



祝你好运。如果他们好或不好，我有兴趣知道你是否尝试过。

Have you tried google[^]? Not sure exactly what you are looking for...are you looking for help with entity relationship diagrams[^]? Or screen mock-ups[^]? I haven't tried any of those, but they look like they could be helpful, depending upon what your really looking for.

Good luck. And I'd be interested to know if you try any if they are good or not.

进行思考和分析？是的，是开发人员大脑中的那些人。唯一的问题是不是每个人都有它们运行。



对于计算机软件，它仅用于协助思考和分析。看到不同。大多数开发工具都可归入此类别，因此您的问题太过模糊，无法讨论任何特定工具。



我认为您对软件开发的想法是错误。没有编码之前，仅仅因为现代成功的软件开发人员并不真正编码，这个人开发软件，而活动不能被称为编码。这是不同的：工程。即使你编写代码，你也不是编码，你正在考虑（希望）和制作，并在代码中表达它。这是艺术，科学，设计和工程。



现在，在合理的开发过程中，没有一个阶段是纯粹的。该项目通常从初始阶段开始，但代码甚至在开始时编写：人们尝试不同的技术，做第一个和最基本的原型，然后讨论它们。等等......说主要焦点从一个阶段到另一个阶段会更安全。在建筑阶段，最关注的是建筑。但是有些开发人员很少或根本不参与架构，你认为他们应该休息一下或者在其他/以前的项目上工作吗？不，他们也应该从一开始就参与。



我所听过的最糟糕的想法是软件开发方法和严格的概念架构开始主宰软件开发。有一种幻想，敏捷方法可以保证解决这个谬论，但这只是一种幻觉。方法不是一门真正严格的科学，应该采取一些怀疑态度，并通过常识和经验检查，了解发展的真正目标。换句话说，如果没有使用人类大脑的批判性思考和分析，这种方法就没有了。这将我们带回到第一段，见上文。 :-)

-SA

For thinking and analysis? Yes, the ones in developer's brain. The only problem is that not everyone has them up and running.

As to the computer software, it is only designed to assist thinking and analysis. See the difference. And most of the development tools can be classified into this category, so your question is well too vague to discuss any particular tools.

I think your idea of software development is wrong. There is no "before coding", just because a modern successful software developer does not really "code", this person develops software, and activity cannot be arguably called "coding". This is something different: engineering. Even when you write code, you are not "coding", you are thinking (hopefully) and crafting, and express it in code. This is art, science, design and engineering.

Now, none of the phases, in a reasonable development process, are "pure". The project normally starts from inception phase, but the code is written even during inception: people try different techniques, do very first and most rudimentary prototypes and then discuss them. And so on… It would be safer to say that main focus moves from stage to stage. At the architectural stages, most focus is on architecture. But there are developers who take really little to no part in architecture, do you think they should have a rest or work on other/previous projects? No, they also should participate from the very beginning.

The worst think I ever heard of is when "software development method" and rigid conceptual schema starts dominating over software development. There is an illusion that agile methods guarantee to fix this fallacy, but this is only an illusion. Method is not a real strict science, it should be taken with some skepticism and checked by common sense and experience, understanding of the real goals of development. In other words, the method is nothing without critical thinking and analysis using human brain. Which takes us back to the first paragraph, see above. :-)

—SA

这篇关于在开始编码之前思考和分析软件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！