你怎么写任何code计划之前的应用程序的架构？ [英] How do you plan an application's architecture before writing any code?

问题描述

有一件事我写任何code之前计划应用程序的架构奋斗。

One thing I struggle with is planning an application's architecture before writing any code.

我并不是收集需求缩小在应用程序需要做什么，而是有效地想着奠定了整体类，数据和流程结构的好方法，并遍历这些想法让我有即使打开IDE前记行动可靠的计划。目前，它是所有易刚刚打开IDE，创建一个空白的项目，开始写位和乙，让设计从那里长出来。

I don't mean gathering requirements to narrow in on what the application needs to do, but rather effectively thinking about a good way to lay out the overall class, data and flow structures, and iterating those thoughts so that I have a credible plan of action in mind before even opening the IDE. At the moment it is all to easy to just open the IDE, create a blank project, start writing bits and bobs and let the design 'grow out' from there.

我收集UML是做到这一点的一种方式，但我与它没有经验，因此似乎有点模糊不清。

I gather UML is one way to do this but I have no experience with it so it seems kind of nebulous.

如何您编写任何code计划之前的应用程序的架构？如果UML是要走的路，你能推荐一个简洁实用的介绍为短小的应用程序开发人员？

How do you plan an application's architecture before writing any code? If UML is the way to go, can you recommend a concise and practical introduction for a developer of smallish applications?

我AP preciate输入。

I appreciate your input.

推荐答案

我真正找到了在纸上或白板上写的第一关是非常关键的。然后，如果你想移动到UML，但没有什么比手工起初只是画它的灵活性。

I really find that a first-off of writing on paper or whiteboard is really crucial. Then move to UML if you want, but nothing beats the flexibility of just drawing it by hand at first.

这篇关于你怎么写任何code计划之前的应用程序的架构？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！