軟件架構亂彈：問題域及其解決方法

關鍵字：.net一、什么是架構
　　1. 和架構相關的幾個問題域
　　架構需要解決的非業務問題域包括如下：
　　A 系統目標：系統性能，穩定性.
　　B.項目目標：開發成本，質量
　　C.項目過程：需求的不確定性和開發過程的團隊協作性
　　不同的問題域，解決之道也不相同！而同一問題域的不同層次的要求，解決之道也不盡相同。

　　2. 什么是架構
　　架構到底是啥，愚以為下面的這段英文描述的很清楚。

　　That's like asking, what is culture? Culture is the way you do things in a group of people. Architecture is the way you do things in a software product. You could argue by analogy, then, that architecture is to a software product as culture is to a team. It is how that team has established and chosen its conventions，

　　Which leads us inevitably to the question of “goodness”? How do you know if an architecture is good? Consider an architecture that isn't built using a strong domain model, and instead relies heavily on stored procedures. That might be OK, or it might not be OK. You could have decided that part of your architecture is to use a really strong domain model and not use stored procedures, right? So an architecture is some reasonable regularity about the structure of the system, the way the team goes about building its software, and how the software responds and adapts to its own environment. How well the architecture responds and adapts, and how well it goes through that construction process, is a measure of whether that architecture is any good.

原文轉自：http://www.anti-gravitydesign.com