Problem 4: Obsolete Requirements Specifications
问题4：根据过时的需求规格说明书编写代码
Prototype method is an important check method of Software Requirements Specifications (SRS).
原型化方法是需求检测中的重要方法之一。
Simulation execution is an important check method of software requirements specifications (SRS).
模拟执行是一种重要的需求规格说明书(SRS)的检测方法。
The individual test cases are driven by use cases, and not supplemental, non-functional requirements specifications.
单个的测试用例是由用例驱动的，而不是附加的，非功能性需求规格。
The product backlog supersedes traditional requirements artifacts, such as market and product requirements specifications.
产品待办事项列表代替了传统的需求文档，比如市场和产品的需求规格说明书。
The team then cuts and pastes graphics from the slides to create formal project documentation, including requirements specifications.
然后团队从幻灯片上剪切并粘贴图形，创建正式的项目文档，包括需求规范。
Other possible external factors include key personnel leaving the project or customers changing the requirements specifications.
另外可能的外部因素还包括项目核心人员的离职和客户变更需求说明等。
As we also noted earlier, attributes provide supplemental information that helps you understand and use requirements specifications more effectively.
也如我们前面注意到的，属性提供了补充信息，使你更加有效地理解和使用需求规约。
Rational Application Developer simplifies the process of creating Web services in a top-down approach based on requirements specifications and UML models.
RationalApplication Developer根据需求规范和uml模型，采用自顶向下的方法简化Web服务的创建流程。
If you are used to creating comprehensive and detailed requirements specifications up front, recognize that Scrum encourages a fundamentally different approach.
如果你习惯于预先编写全面深入的需求规格说明书的话，你就会发现Scrum其实是一种本质上完全不一样的方法。
One of the most reliable methods of ensuring problems, or failure, in a large, complex software project is to have poorly documented requirements specifications.
是分析问题或项目失败的最可靠的方法之一，如一个复杂的软件项目的需求规格说明书却很简单。
Business analysts struggle with writing good requirements specifications, effectively communicating requirements and their changes, and correctly interpreting customer needs.
业务分析需要努力写出好的需求规格，有效的沟通需求及其变更，同时正确地解释客户的需要。
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.
在一些非常少见的实例中，当每个人都对项目目标有一个非常强的理解时，就已经不需要描述需求了——或者需求规格说明可以是最小程度的。
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.
术语表是消除需求规格说明书中模糊性并避免误解的简单却强有力的手段，应该由分析人员拥有、开发和维护。
When Requirements Specifications are not formally evaluated, the design and coding activities often result in numerous changes to the scope and definition of the functions being delivered.
如果需求没有得到正式评价，就常会导致设计和编码活动产生对早期提交的功能范围和定义的大量修改。
It may be desirable to manage non-canonical software requirements to facilitate requirements development and improve the quality of requirements specifications during the requirements stage.
对软件需求阶段的非规范信息进行有效管理有助于改进需求获取过程，提高需求质量。
This situation can be remedied to an extent by modifying COTS without compromising on military specifications and requirements.
通过修改COTS坚持军用规格和要求使这一状况在一定程度上得到改进。
For applications that implement interfaces or specifications, the requirements are the same as the specification document published by a designated authority.
对于实现接口或规范的应用程序，需求应该与指定的权威机构发布的规范文档相同。
You will need clear communication across geographical boundaries to ensure that the right application is developed on time, using the right requirements and quality specifications.
您需要跨越地域边界进行清晰地通信，以确保准时开发正确的应用程序，使用正确的需求及质量规范。
However, a service specification contains quality of service requirements in addition to specifications of realized operations.
然而，除了所实现的操作规范之外，服务规范还包括服务质量需求的规范。
Superstitious 10 conformance to accessibility requirements usually results in designs that meet specifications but are not necessarily optimal or even operational.
与易访问性需求迷信地保持10一致经常导致满足规范的设计，但不是必要地理想甚至可操作。
Many of them now include accessibility requirements in their purchasing specifications.
许多公司现在将易访问性需求包含到他们的采购规格中。
Communication with the technical team members to transform the established requirements into technical specifications that can be coded and tested to.
与技术团队成员沟通，以将确定的要求转换为能进行编码和测试的技术规范。
They can also be used for the review and inspection of project plans, requirements definitions, specifications, design documents, test plans, operations manuals, and user manuals.
它们还可用于检查项目计划、需求定义、规范、设计文档、测试计划、操作手册和用户手册。
In this case, the business processes may be thought of as specifications of the requirements for what an SOA solution must do.
在这种情况下，业务过程可能被视作SOA解决方案必须处理的需求的规范。
Early and frequent customer contact combined with a simple requirements spreadsheet replace traditional functional specifications and sophisticated use case diagrams.
早期的频繁的客户接触与简单的需求电子数据表代替了传统的功能规格说明书和复杂的用例图。
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.
补充规格说明描述了影响多个用例的需求。
Both specifications provide conformance and interoperability requirements for vendors' implementations.
两个规范提供了厂商的实现的一致性和互操作性需求。
Both specifications provide conformance and interoperability requirements for vendors' implementations.
两个规范提供了厂商的实现的一致性和互操作性需求。
应用推荐