问题4：根据过时的需求规格说明书编写代码
技巧3：建立和参与需求规格说明书检查
Tip 3: Establish and Participate in Requirements Specification Reviews
详细说明见阳光酒店管理系统需求规格说明书。
A detailed explanation see the sunshine hotel management system requirements specification.
软件做了《产品需求规格说明书》中没提到的事情。
The software does something that the product specification doesn't mention.
此为酒店管理系统的软件需求规格说明书，内容详细。
This is the hotel management system for software requirements specification and detailed.
提出了一个检测嵌入式实时软件需求规格说明的方法。
A method checking requirements specification of embedded real time software is presented.
本需求规格说明书同时也是作为系统验收的唯一依据。
The requirements specification is also the sole basis for acceptance as a system.
软件做了《产品需求规格说明书》中规定不应该做的事情。
The software does something that the product specification says it shouldn't do.
软件没有做《产品需求规格说明书》中规定应该做的事情。
The software doesn't do something that the product specification says it should do.
模拟执行是一种重要的需求规格说明书(SRS)的检测方法。
Simulation execution is an important check method of software requirements specifications (SRS).
例如，软件需求规格说明书(SRS)工件是需求详细说明人负责的。
For example, the artifact Software Requirements Specification (SRS) is owned by the Requirements Specifier.
产品待办事项列表代替了传统的需求文档，比如市场和产品的需求规格说明书。
The product backlog supersedes traditional requirements artifacts, such as market and product requirements specifications.
它们分别是需求获取、需求分析、需求规格说明编写、需求验证、需求管理。
They are requirements elicitation, requirements analysis, requirements specification, requirements validation and requirements management.
这个问题解决得好坏直接影响到需求规格说明的质量，进而影响到最终软件产品的质量。
How to solve this problem directly influences the quality of requirements specification, as well as the final software production.
在瀑布开发中，设计人员和开发人员试图达到他们期望的行为，就是代码满足需求规格说明。
In waterfall development, the designers and developers try to achieve the desired behavior as best they can by complying with the specification.
是分析问题或项目失败的最可靠的方法之一，如一个复杂的软件项目的需求规格说明书却很简单。
One of the most reliable methods of ensuring problems, or failure, in a large, complex software project is to have poorly documented requirements specifications.
问题在于试图在最开始定义全面的需求规格说明已经证明是非常的危险决策，因此我们不用rup来做这件事。
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.
好的RM实践为管理需求规格说明书清楚地确定了一个中央知识库，这样每个人都能总是得到最新的需求版本。
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.
术语表是消除需求规格说明书中模糊性并避免误解的简单却强有力的手段，应该由分析人员拥有、开发和维护。
A glossary document that is owned, developed, and maintained by the analyst is a simple yet powerful way to remove ambiguity from requirements specifications and avoid misunderstandings.
在一些公司中的项目计划中没有需求规格说明书了，而以功能需求文档，设计文档或者以其他不同形式描述需求。
In some organizations requirements may end up in high level project plans, functional specification documents, in design documents, or in other documents at various levels of detail.
如果你习惯于预先编写全面深入的需求规格说明书的话，你就会发现Scrum其实是一种本质上完全不一样的方法。
If you are used to creating comprehensive and detailed requirements specifications up front, recognize that Scrum encourages a fundamentally different approach.
这里我们引出的重要概念就是，业务需求规格说明应该描述系统的行为，而不是它的设计。我们经常从客户那里得到类似的反应。
When we introduce the important concept that business specifications should describe the behavior of the system, and not its design, we often get a similar reaction from our clients.
在一些非常少见的实例中，当每个人都对项目目标有一个非常强的理解时，就已经不需要描述需求了——或者需求规格说明可以是最小程度的。
In rare instances, when everyone has an extremely strong understanding of the project goals, there is no need to state requirements — or the requirements specifications can be minimal.
术语表不需要列出需求规格说明书中用过的每一个词汇，但是它必须包含可能有歧义的词汇。 术语表通过给出需求规格说明书中关键词汇的定义，消除了模糊性。
The glossary does not need to list every term used in the requirement specifications, but it should definitely include any that might be subject to multiple interpretations.
规格说明的第二种形式与需求非常不同。
The second form of specification is very different from requirements.
它要求建立需求、规格说明、测试计划和交付。
It requires establishing requirements, specification, test planning, and rollout.
这就保证规格说明的实际性，并提供了更加符合涉众需求的实际的指导和现实的架构。
This keeps the specifications realistic, providing real guidance and realistic architectures that are more in tune with the stakeholders' needs.
每个分解级别都强制进行设计决策，提供正在进行的合成，连接需求和设计规格说明，并增加系统详细内容。
Each level of decomposition forces design decisions, providing ongoing synthesis, coupling of requirements and design specifications, and increasing system detail.
补充规格说明描述了影响多个用例的需求。
Supplementary specifications describe requirements that affect multiple use cases.
补充规格说明描述了影响多个用例的需求。
Supplementary specifications describe requirements that affect multiple use cases.
应用推荐