你在哪里画的设计和建筑之间的界线？ [英] Where do you draw the line between design and architecture?

问题描述

借助敏捷架构问题让我怀疑这一点。

The Agile architecture question makes me wonder this.

请问这取决于什么正在建造的？做应用程序（我的意思是单
        这里的计算程序）有一个架构？

Does it depends of what is being build ? Do applications (I mean single computing program here) have an architecture ?

更新：试图澄清的问题，我给关于这个问题我认为：我所定义的架构为系统组件的切割和组件之间的关系，而设计是关于实习生的组件。难道这种看法共享？

UPDATE: to try to clarify the question, I'll give my opinion on the question: I defined the architecture as the cutting of the system in components, and the relationships between the components ;while the design is about the interns of the component. Is this opinion shared ?

推荐答案

这真的很简单：建筑是关于您对符合非功能性的要求设计决定：如成本，可维护性，性能，可靠性的要求，可用性和安全性。这是关于一个Web应用程序：您可以在数不胜数的方式建造它，从运行为CGI（实际上，以前我们做到这一点），一个Python Web应用程序，在J2EE应用程序，在应用LAMP一个大的C程序。任何人也有同样的功能行为，他们都将张贴在同一页面;差异进来当您尝试改变C程序的数据库或负载平衡你的大LAMP的应用程序。

It's really fairly simple: architecture is about the design decision you make to meet the "non-functional" requirements: requirements like cost, maintainability, performance, reliability, availability, and security. This about a web application: you can build it in a zillion ways, from a big C program that runs as a CGI (really, we used to do that), a Python webapp, to a J2EE application, to a LAMP application. Any of them would have the same functional behavior, they all would post the same pages; the differences come in when you try to change the C program's database or load-balance your big LAMP application.

这篇关于你在哪里画的设计和建筑之间的界线？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！