Your System Is Legacy; Design for It
2015-08-31 11:32
239 查看

EvEn iF youR SySTEM iS BlEEding EdgE and developed in the latest tech- nology, it will be legacy to the next guy. Deal with it! The nature of software today means things go out of date fast. If you expect your system to go into production and survive, even for a few months, then you need to accept that maintenance developers will need to fix things up. This means several things:
• Clarity: It should be obvious what role components and classes perform.
• Testability: Is your system easy to verify?
• Correctness: Do things work as designed or as they should? Eliminate quick and nasty fixes.
• Traceability: Can Ernie the Emergency Bug Fixer—who has never seen the code before—jump into production, diagnose a fault, and put in a fix? Or does he need an eight-week handover?
Try to think of a different team opening up the codebase and working out what’s happening. This is fundamental for great architecture. It doesn’t have to be oversimplified or documented to the hilt; a good design will document itself in many ways. The way a system behaves in production can also expose the design. For example, a sprawling architecture with ugly dependencies will often behave like a caged animal in production. Spare a thought for (usually more junior) developers who may have to debug defects.

Legacy tends to be a bad word in software circles, but in reality, all software systems should endure the tag. It is not a bad thing, as it may indicate that your system is durable, meets expectations, and has business value. Any software system that has never been called legacy has probably been canned before launch—which is not the sign of a successful architecture.
Dave Anderson is a principal software engineer at Belfast software company Liberty IT, which supplies IT solutions for Fortune 100 company Liberty Mutual. Dave has more than 10 years’ experience in the software industry with many leading-edge IT companies across several different industries and countries.
Your System Is Legacy; Design for It
Dave AndersonEvEn iF youR SySTEM iS BlEEding EdgE and developed in the latest tech- nology, it will be legacy to the next guy. Deal with it! The nature of software today means things go out of date fast. If you expect your system to go into production and survive, even for a few months, then you need to accept that maintenance developers will need to fix things up. This means several things:
• Clarity: It should be obvious what role components and classes perform.
• Testability: Is your system easy to verify?
• Correctness: Do things work as designed or as they should? Eliminate quick and nasty fixes.
• Traceability: Can Ernie the Emergency Bug Fixer—who has never seen the code before—jump into production, diagnose a fault, and put in a fix? Or does he need an eight-week handover?
Try to think of a different team opening up the codebase and working out what’s happening. This is fundamental for great architecture. It doesn’t have to be oversimplified or documented to the hilt; a good design will document itself in many ways. The way a system behaves in production can also expose the design. For example, a sprawling architecture with ugly dependencies will often behave like a caged animal in production. Spare a thought for (usually more junior) developers who may have to debug defects.

Legacy tends to be a bad word in software circles, but in reality, all software systems should endure the tag. It is not a bad thing, as it may indicate that your system is durable, meets expectations, and has business value. Any software system that has never been called legacy has probably been canned before launch—which is not the sign of a successful architecture.
Dave Anderson is a principal software engineer at Belfast software company Liberty IT, which supplies IT solutions for Fortune 100 company Liberty Mutual. Dave has more than 10 years’ experience in the software industry with many leading-edge IT companies across several different industries and countries.
相关文章推荐
- SQLServer优化资料整理(二)
- vbox里面的Ubuntu虚拟机与主机win7之间设置共享文件夹
- 一般处理程序+html 的CRUD
- PHP 加密的几种方式
- socket通信
- 分布式系统初识
- Android拨号器---熟练控件与布局的应用
- 哈夫曼压缩
- Android界面布局
- win2003中iis与asp设置Session会话过期时间的问题
- 扫雷小游戏的设计与实现
- 类和对象的理解
- 接口与抽象类
- 画板感想与小结
- 批处理命令调用WINRAR对文件进行压缩
- 我的生活,我的积累
- 几种常见数据库连接池的使用比较
- UIViewController方法调用顺序
- 一次向svn中增加所有新增文件 svn add all new files
- 关于友元,重载的使用说明