Jan'uary » 日志 » 软件工程中最易犯的十大错误
软件工程中最易犯的十大错误
Jan 发表于 2005-03-10 08:52:12
由一位在软件工程方面有近十年经验的专家根据自己的经验总结出以下10个常见问题:
1. 解决方案比要解决的问题还要复杂
2. 基于自己的需求而不是用户的需求来设计
3. 疏于优雅的处理所有可能的出错情况
4. 不去保护用户的隐私
5. 期待用户会去(或者应该去)阅读所有文档
6. 期待用户掌握了(或者应该掌握)技术知识/术语
7. 期待用户会(或者应该会)在使用某些功能先进行配置
8. 总是试图去猜测用户的意图(而不是通过交流来了解)
9. 不知道什么时候对软件进行重构(要么是无效的重构,要么是在需要重构的时候没有去做)
10. 没有尽可能的提高软件的可维护性和代码的可理解性
The Ten Worst Engineering Pitfalls
Posted by special contributor Keith F. Kelly on 2005-03-09 02:19:16 UTC
I've been a professional software engineer for close to ten years. Based on my experience, I recently attempted to enumerate the ten worst engineering "traps" most developers seem (for whatever reason) prone to fall into. Here's the list I came up with. It should be noted that wherever two of these come into conflict, the item close to the top of the list wins.
The Ten Worst Engineering Pitfalls
1. The solution is more problematic than the problem it was created to solve.
2. Basing the design on your own motives rather than on users' needs.
3. Neglecting to handle all possible failure cases gracefully.
4. Failing to protect users' privacy.
5. Expecting that users will (or should have to) read anything.
6. Expecting that users will (or should have to) possess technical knowledge or jargon.
7. Expecting that users will (or should have to) configure something before using it.
8. Challenging or attempting to guess the user's intent.
9. Not knowing when to re-architect (either doing it pointlessly, or avoiding it when needed).
10. Failing to make the implementation as maintainable and understandable as possible.
1. 解决方案比要解决的问题还要复杂
2. 基于自己的需求而不是用户的需求来设计
3. 疏于优雅的处理所有可能的出错情况
4. 不去保护用户的隐私
5. 期待用户会去(或者应该去)阅读所有文档
6. 期待用户掌握了(或者应该掌握)技术知识/术语
7. 期待用户会(或者应该会)在使用某些功能先进行配置
8. 总是试图去猜测用户的意图(而不是通过交流来了解)
9. 不知道什么时候对软件进行重构(要么是无效的重构,要么是在需要重构的时候没有去做)
10. 没有尽可能的提高软件的可维护性和代码的可理解性
The Ten Worst Engineering Pitfalls
Posted by special contributor Keith F. Kelly on 2005-03-09 02:19:16 UTC
I've been a professional software engineer for close to ten years. Based on my experience, I recently attempted to enumerate the ten worst engineering "traps" most developers seem (for whatever reason) prone to fall into. Here's the list I came up with. It should be noted that wherever two of these come into conflict, the item close to the top of the list wins.
The Ten Worst Engineering Pitfalls
1. The solution is more problematic than the problem it was created to solve.
2. Basing the design on your own motives rather than on users' needs.
3. Neglecting to handle all possible failure cases gracefully.
4. Failing to protect users' privacy.
5. Expecting that users will (or should have to) read anything.
6. Expecting that users will (or should have to) possess technical knowledge or jargon.
7. Expecting that users will (or should have to) configure something before using it.
8. Challenging or attempting to guess the user's intent.
9. Not knowing when to re-architect (either doing it pointlessly, or avoiding it when needed).
10. Failing to make the implementation as maintainable and understandable as possible.
收藏:
QQ书签
del.icio.us
订阅:
Google
抓虾
