软件架构乱弹：问题域及其解决方法

关键字：.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.ltesting.net