软件架构浅谈:问题域及其解决方法
日期:2007年9月23日 作者: 查看:[大字体 中字体 小字体]-
一、什么是架构
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] 下一页
-
- 软件架构浅谈:问题域及其解决方法 相关文章:
- ·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
- 特别声明:本站除部分特别声明禁止转载的专稿外的其他文章可以自由转载,但请务必注明出处和原始作
- 者.文章版权归文章原始作者所有.对于被本站转载文章的个人和网站,我们表示深深的谢意。如果本站转
- 载的文章有版权问题请联系编辑人员,我们尽快予以更正. 转载请注明来源:http://www.hackhome.com
下一篇:Orcas版C#3.0的新特性
精品推荐
热点TOP10
- ·Visual Studio 2005集成开发环境图解
- ·利用UML类图设计Java应用程序详解(1)
- ·软件工程的未来之路与我们的解决之道?
- ·VS2005(c#)项目调试问题解决方案集锦
- ·Atlas应用程序的调试技巧
- ·代码编写中的心理学与美学
- ·函数库、组件产品的测试方法
- ·IBM 建立商业解决方案中心
- ·IBM Rational推出SOAD策略
- ·通过RUP用例进行需求管理的可追踪性策略(1)
- ·软件项目在变化的需求中获得成功(1)
- ·界面需求的分析方法(1)
- ·探究需求管理的本质(1)
- ·利用数据绑定和模板创建Atlas应用程序
- ·BEA和Siebel联合提供CRM软件
- ·BEA新任亚太区总经理 曾任惠普软件部高管
- ·Java从老虎变野马 好事还是坏事?
- ·Web服务的期望与现实
- ·SAP:未来管理软件将像玩具
- ·面向服务的体系结构的成熟度模型
