本文探讨了从用户视角定义问题的重要性，指出有时最有效的解决方案并非编写复杂的计算机程序。例如，若要获得年度利润报告而已有季度利润数据，手动汇总这些数据可能比编程更简单快捷。
The problem definition should be in user language, and the problem should be described from a user's point of view. It usually should not be stated in technical computer terms. The best solution might not be a computer program. Suppose you need a report that shows your annual profit. You already have computerized reports that show quarterly profits. If you're locked into the programmer mindset, you'll reason that adding an annual report to a system that already does quarterly reports should be easy. Then you'll pay a programmer to write and debug a time-consuming program that calculates annual profits. If you're not locked into the programmer mindset, you'll pay your secretary to create the annual figures by taking one minute to add up the quarterly figures on a pocket calculator.
The exception to this rule applies when the problem is with the computer: compile times are too slow or the programming tools are buggy. Then it's appropriate to state the problem in computer or programmer terms.
扫一扫
994
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
