2006-03-27 校对记要
校对文件: roman.xml
第15章第2节
标题
- Handling changing requirements
应对
要求需求变化
第一段
- Despite your best efforts to pin your customers to the ground and extract exact requirements from them on pain of horrible nasty things involving scissors and hot wax, requirements will change. Most customers don't know what they want until they see it, and even if they do, they aren't that good at articulating what they want precisely enough to be useful. And even if they do, they'll want more in the next release anyway. So be prepared to update your test cases as requirements change.
尽管你竭尽努力地分析你的客户需求,并点灯熬油地提炼出
相应精确的
要需求,但
要求是需求还是会变化的。 大部分客户在看到产品前不知道他们
要想要什么。即便知道,也不
能很好地善于精确表述出他们的有效需求。即便能表述出来,他们
下一次在下一个版本一定
要会要求更多的功能。 因此你需要
让你的独立测试做好更新准备做好更新测试用例的准备以应对
要求需求的改变。
第2段
- Suppose, for instance, that you wanted to expand the range of the Roman numeral conversion functions. Remember the rule that said that no character could be repeated more than three times? Well, the Romans were willing to make an exception to that rule by having 4 M characters in a row to represent 4000. If you make this change, you'll be able to expand the range of convertible numbers from 1..3999 to 1..4999. But first, you need to make some changes to the test cases.
假设你想要扩展罗马数字转换
函数的范围。
记住 这条原则 :没有哪个字符可以重复三遍以上 还记得“没有哪个字符可以重复三遍以上”这条规则 吗?
啊哈!罗马数字可以连续出现 4 次M 字符来表示 4000 便是一个例外呃, 现在罗马人希望给这条规则来个例外,用连续出现 4 个M 字符来表示 4000。 如果
你做出这个改变这样改了,你
则就可以把转换范围从 1..3999 扩展到 1..4999。 但首先,你先要对
独立测试测试用例进行修改。