求英译中 计算机类的 翻出来要看的懂讲的通2.What goes into the requirements document? The definition of the ideal requirements document is simple:It should contain everything you need to know to write software that is accepta

求英译中 计算机类的 翻出来要看的懂讲的通2.What goes into the requirements document? The definition of the ideal requirements document is simple:It should contain everything you need to know to write software that is accepta
求英译中 计算机类的 翻出来要看的懂讲的通
2.What goes into the requirements document?
 The definition of the ideal requirements document is simple:It should contain everything you need to know to write software that is acceptable to the customer,and no more.
 (1) Every statement should be valid for all acceptable products; none should depend on implementation decisions.
 (2) The document should be complete in the sense that if a product satisfies every statement,it should be acceptable.
 (3) Where information is not available before development must begin,the areas of incompleteness should be explicitly indicated.
 (4) The product should be organized as a reference document rather than an introductory narrative about the system.
 Although it takes considerable effort to produce such a document,and a reference work is more difficult to browse than an introduction,it saves labor in the long run.
 The information that is obtained in this stage is recorded in a form that allows easy reference throughout the project.
3.Who writes the requirements document?
 Ideally,the requirements document would be written by the users or their representatives.
 In fact,users are rarely equipped to write such a document.Instead,the software developers must produce a draft document and get it reviewed and,eventually,approved by the user representatives.
4.How is the requirements document organized?
 (1) Computer Specification:a specification of the machines on which the software must run.
 (2) Input/Output Interfaces:a specification of the interfaces that the software must use in order to communicate with the outside world;
 (3) Specification of Output Values:for each output,a specification of its value in terms of the state and history of the system's environment;
 (4) Timing Constraints:for each output,how often,or how quickly,the software is required to recompute it;
 (5) Accuracy Constraints:for each output,how accurate it is required to be.
 (6) Likely Changes:if the system is required to be easy to change,the requirements should contain a definition of the areas that are considered likely to change.
 (7) Undesired Event Handling.

求英译中 计算机类的 翻出来要看的懂讲的通2.What goes into the requirements document? The definition of the ideal requirements document is simple:It should contain everything you need to know to write software that is accepta
2,怎么去?进入需求文档
本文件的理想需求定义很简单：它应包含所有你需要知道写的软件都能接受的客户,并没有更多.
（1）每个语句应适用于所有可以接受的产品,任何人都不应取决于执行的决定.
（2）文件应该是完整的,即如果产品满足每一个声明,它应该可以接受.
（3）凡信息不可用在发展前必须开始,不完备的地区,应明确表示.
（4）产品应组织作为参考文件,而不是有关系统的介绍说明.
虽然需要相当大的努力产生这样的文件,以及参考的工作更加困难,浏览比介绍,这样可以节省长远的劳动.
的是在这一阶段获得的信息记录的形式,使整个项目的参考.
3.谁写的需求文档?
理想情况下,要求的文件将被写入由用户或其代表.
事实上,用户很少有能力写出这样的文件.相反,软件开发商必须出示一份文件草案,并获得专家组审查,并最终由用户代表的批准.
4.如何组织文件的要求?
（1）电脑规格：1的机器上运行的软件必须规范.
（2）输入/输出接口：一个接口,该软件的使用必须以沟通与外界规范;
（3）输出值规格：每个输出,其价值在国家和系统的环境历史的规范;
（4）时序约束：每个输出,频率多快,软件需要重新计算它;
（5）精度的限制：每个输出,它是如何准确须.
（6）可能发生的变化：如果系统必须易于变化,要求应包含一个被认为可能改变地方的定义.
（7）非自愿的事件处理.