英语翻译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 ens

英语翻译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 ens
英语翻译
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.

英语翻译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 ens
在项目开始阶段就进行检测程序最有效,应该要比书写代码提前许久.首先应认证需求文档的有效性；接下来,在项目的后继阶段,检测应主要集中在保证应用程序代码的质量上.在项目的开始阶段,进行具体的设计和编码工作之前,消除与需求相关的缺陷可以将返工的可能性降到最低,返工的代价是昂贵的.
软件或系统的需求说明必须极其准确详细地描述其功能.满足需求的最大的挑战来自于与提出需求者的沟通.每项需求务求准确清晰的阐述,以便阅读者对其做同样的理解.
如果撰写需求文档有统一的方式,那么负责搜集各种需求的责任人就可以有效参与需求的满足过程了.一旦某项需求成品可见,就可以通过询问该责任人细节性问题来进行测试.为了确认每项需求都得到满足,并且每个人对需求的理解相同,可以进行多种需求测试.

在计画的开始的最有效的测试计画开始,久在任何的计画密码之前已经被写。 需求文件被查证第一; 然后，在计画的较迟的阶段中，测试能专注于确定申请密码的质量。 贵的重做被藉由除去在计画的生活方面很早的需求讲的缺点减到最少, 在详细的设计之前或编码工作。
给一个软件申请或系统的需求规格一定最后描述棒的细节的它的功能性。 需求发展的最挑战性方面之一是与正在供应需求的人沟通。 每个需求应该精确地而且...

全部展开

在计画的开始的最有效的测试计画开始,久在任何的计画密码之前已经被写。 需求文件被查证第一; 然后，在计画的较迟的阶段中，测试能专注于确定申请密码的质量。 贵的重做被藉由除去在计画的生活方面很早的需求讲的缺点减到最少, 在详细的设计之前或编码工作。
给一个软件申请或系统的需求规格一定最后描述棒的细节的它的功能性。 需求发展的最挑战性方面之一是与正在供应需求的人沟通。 每个需求应该精确地而且清楚地被陈述，因此，它能同样地被了解读它的每一个人。
如果有证明需求的一致方法, 它对对于聚集有效地参与需求程序的需求是有责任的保管赌注的人是可能的。 一旦一个需求被做看得见就，它能被藉由提出被详细说明疑问的保管赌注的人测试而且澄清。 多种需求测试能被申请确定每个需求是有关的, 而且每个人有它的意义的相同理解。

收起