软件架构浅谈：问题域及其解决方法

• 　　一、什么是架构

  　　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.

  　　The system architecture determines how hard or easy it is to implement a given feature. Good architectures are those in which it is considered easy to create the features desired. In that the way to judge whether an architecture is good is whether the architecture is good for the purposes to which it is applied.

  　　The definition of goodness has to be related to fitness for purpose. Is this glove good? I don't know. What are you doing with the glove? Are you throwing snowballs, cooking barbeques, or playing golf? There's a set of changes that are going to occur to a software system over time. Probably the utilitarian or most useful definition of goodness is the answer to this question: are the changes that will keep this system successful in this domain in this product line relatively easy? If they are, then it's probably a good architecture.

• [1] [2] [3] [4] 下一页 
• 复制本页网址和标题，发送给你QQ/Msn的好友一起分享
  
  
• 软件架构浅谈：问题域及其解决方法 相关文章：
• ·AUTO病毒可导致某些杀毒软件失效
• ·诺顿杀毒软件正式版用户找回密码的方法
• ·节哀顺便病毒感染安全软件致防御失效
• ·免费绘图软件Paint.NET推出3.2正式版
• ·三维景观软件Vue 5 Esprit函数碎片节点
• ·微软会发布Win Server 2008 RC2？
• ·小巧设计软件完成电子杂志个性化设计
• ·挑战可靠性 6款文件加密软件残酷测试
• ·微软官网Microsoft.com安全防护趣闻
• ·卡巴斯基报告称恶意软件近三成来自中国
• 软件架构浅谈：问题域及其解决方法 相关软件
• ·PSP游戏镜像压缩转换软件 ISO Compressor
• ·支持新PSP、PS3直接播放的视频转换软件
• ·手机游戏：动物园大亨(微软正版)
• ·软件路由器论坛精华文摘第一期
• ·微软IE网络霸业十年回眸
• ·经典抓图软件SnagIt高级图文教程
• ·微软Visio绘图工具
• ·微软Office技巧大赛优秀作品
• ·C#文档中文版(微软)
• ·手机无贼-防盗监听软件v1.0.0719

上一篇:用PHP程序直接调用文本文件内容实例

下一篇:Orcas版C#3.0的新特性

• 特别声明：本站除部分特别声明禁止转载的专稿外的其他文章可以自由转载，但请务必注明出处和原始作
• 者.文章版权归文章原始作者所有.对于被本站转载文章的个人和网站，我们表示深深的谢意。如果本站转
• 载的文章有版权问题请联系编辑人员,我们尽快予以更正. 转载请注明来源：http://www.hackhome.com

精品推荐

热点TOP10

特别推荐