Effective software test
Chapter 1. Requirements Phase
The most effective testing programs start at the beginning of a project, long before
any program code has been written. The requirements documentation is verified
first; then, in the later stages of the project, testing can concentrate on ensuring the
quality of the application code. Expensive reworking is minimized by eliminating
requirements-related defects early in the project's life, prior to detailed design or
coding work.
The requirements specifications for a software application or system must
ultimately describe its functionality in great detail. One of the most challenging
aspects of requirements development is communicating with the people who are
supplying the requirements. Each requirement should be stated precisely and
clearly, so it can be understood in the same way by everyone who reads it.
If there is a consistent way of documenting requirements, it is possible for the
stakeholders responsible for requirements gathering to effectively participate in the
requirements process.As soon as a requirement is made visible, it can be tested
and clarified by asking the stakeholders detailed questions. A variety of
requirement tests can be applied to ensure that each requirement is relevant, and
that everyone has the same understanding of its meaning.
[翻译如下]
有效软件测试
第一章 需求术语
最有效的软件测试应该在项目的初期启动，在程序代码开始编写之前应该被完成。需求文档应当首先被确认；接着在以后的项目阶段中，测试能够集中保证在应用程序代码的质量上。在项目生命周期的早期，在详细设计和代码工作之前，通过消除与需求相关的缺陷可以最小化代价昂贵的代码重写工作
一个应用软件或者系统的需求说明书必须详尽的描述软件最终的功能特性。一个最具挑战性的需求开发方面就是保持与需求提供者的交流。每一条需求应该陈述精准和清晰，如此才可以让任何读它的人能够明白。
如果有一种一致的需求编写方法的话，将负责需求收集的利益关系人（甲方）有效的参与到需求的进程中来是可行的。一旦需求变得可见，它就可以被用来测试和通过询问利益关系人（甲方）被询问的详尽问题来澄清。对需求的多样性测试可以被用来确保每一个相关的需求，并且却确保每一个人对同一个需求有相同的理解。
遇到的生词：
Consistent：adj.
一致的,调和的,坚固的, [数、统]相容的
Stakeholder：n.
赌金保管者
PS：什么东西不用，就会忘记。磕磕碰碰的翻译完一点点,发现好多不通的地方,都不好意思贴上来,不如去买本汉语的来看了.
