片语

quality requirements and specification质量要求和详细说明

Technical requirements specification技术要求规范

systems requirements specification系统要件说明书

Interface Requirements Specification接口要求规范书

general requirements VDE Specification一般规定

requirements specification model需求描述模型

Marketing Requirements Specification市场要求规格

requirements specification method需求描述方法

Requirements and specification要求和规范

interpellation质询；要求说明（一般由议员在议会中向内阁部长等提出）

英汉例句

• in 1985, we were looking at many different ways to define a problem by writing good requirements, and a software requirements specification (srs) was the main vehicle programmers used to record them.

  在1985 年，我们一直在寻找许多不同的方法来定义问题，如书面写好需求，软件需求说明书（srs）是用来记录它们的主要载体。

• this plain text starts its life as a requirements specification for code that has yet to be written.

  用纯文本作为编好的代码需求说明。

• the requirements specification is also the sole basis for acceptance as a system.

  本需求规格说明书同时也是作为系统验收的唯一依据。

• soa-aligned, process-driven use case modeling, if done well, results in better fidelity of a requirements specification to the real solution.

  与soa一致的流程驱动的用例建模工作如果完成得当，能够提高需求规范与实际解决方案的对应关系。

• for example, the artifact software requirements specification (srs) is owned by the requirements specifier.

  例如，软件需求规格说明书（srs）工件是需求详细说明人负责的。

• this is the hotel management system for software requirements specification and detailed.

  此为酒店管理系统的软件需求规格说明书，内容详细。

• similarly, if your requirements specification is merely a giant list in no particular order, you will not be able to use it.

  与此相似，如果你的需求规约只是一张毫无规则的大列表，你也没办法使用它。

• user stories seem to be the requirements specification vehicle of choice for many agile projects; although other approaches, like use cases, are acceptable.

  用户的经历往往是很多敏捷项目的需求规范的传达手段；虽然还存在很多其它方法，例如用例等。

• the sorts of things that normally would go in a functional requirements specification often go into the implementation details.

  那些通常归入功能性需求规范的东西常被放入实现细节。

• we can read the requirements specification and the code and do a very good job of ensuring that the implementation is correct.

  我们可以阅读需求规约和代码，并能够很好地保证实现是正确的。

• figure 2-3: overlapping requirements specification and development iterations

  图2-3：需求规范与开发迭代的重叠

• good rm practice dictates that the team clearly designate a central repository for the requirements specification document so that everyone always has access to the latest version.

  好的rm实践为管理需求规格说明书清楚地确定了一个中央知识库，这样每个人都能总是得到最新的需求版本。

• as an extra step, it is also a good idea to notify the team (via e-mail, phone, meeting, etc.) when the requirements specification document has been updated.

  此外，与项目团队交流（通过电子邮件、电话、会议等）需求已经被更新的消息也是一种良好、健康的实践。

• the point is that trying to define a comprehensive requirements specification upfront proves to be a spectacularly risky decision, so we don「t do that with rup.

  问题在于试图在最开始定义全面的需求规格说明已经证明是非常的危险决策，因此我们不用rup 来做这件事。

• the four most common requirement gathering processes are the traditional software requirements specification (srs), use cases, features, and user stories.

  四种最常见的需求收集过程是传统的软件收集规范（softwarerequirements specification，srs）、用例（usecases）、功能特性（features）和用户情景（userstories）。

• the bulk of the requirements specification is contained in the mapping document.

  大多数需求规范都包含于映射文档中。

• additionally, i found the technique useful to separate functionality documented in use cases, and non-functionality documented in the supplementary requirements specification (srs).

  另外，我发现这项技术在分割用例所记录的功能性需求时很有用，同样，对于附加需求规范（srs）中记录的非功能性需求也很有用。

• this entails defining a set of questions and activities that will be applicable across many requirements specification documents, and be understandable to the readers of the specifications.

  这将可以定义一套可以跨越许多需求规范文件的问题和行为，对于这些规范的读者来说也是可以理解的。

• tip 3: establish and participate in requirements specification reviews

  技巧3：建立和参与需求规格说明书检查

• this would extend the typical developers」 model of iterative development to include the requirements specification of the release and its system testing.

  这将扩展典型的迭代式开发模型以包括发行的需求规范及其系统测试。

• the software requirements specification (srs) is one of the oldest requirements gathering processes.

  软件需求规范（srs）是最古老的需求收集过程之一。