他们中一些有特定的硬件和软件需求。
Some of them do have specific hardware and software requirements.
下面列出了最终的硬件与软件需求。
Here's the list of the final hardware and software requirements.
许多软件需求技术对方法都是可适用的。
Many software requirements techniques are applicable to methods.
图一：软件需求和业务规则之间的关系。
Figure 1: Relationships between software requirements and business rules.
一旦具体化，这些用例就会包含软件需求。
Once specified, those use cases contain the software requirements.
图五：描述业务规则到软件需求中的改变。
Figure 5: Tracing changes in business rules to software requirements.
图2显示了上面讨论的产品的一些软件需求。
Figure 2 shows some of the software requirements for the products discussed above.
第一章节提出了一个广义而又详细的软件需求。
The first chapter offers a broad, yet detailed overview of software requirements.
扩展已存在EclipseIDE的软件需求。
Software requirements for extending an existing Eclipse ide.
然而，由于业务环境可能快速变化，软件需求也应当如此。
However, because business environments can change quickly, software requirements ought to follow.
在SR2中，同样的软件需求又一次被另一个规则复杂化了。
In SR2, the same software requirement is again complicated by another rule.
这种控制利用使其成为所有HR系统的软件需求实现了自动化。
This control is automated by making it a common software requirement for all HR systems.
如果你这样追踪追不下去，软件需求很可能就没有业务合理性。
If you cannot trace it in this way, the software requirement probably does not have a business justification.
然而，当软件需求的细节嵌入到合同中时，你的组织可能有信任问题。
However, when detailed software requirements are embedded in contracts, odds are your team has trust issues.
注意你可以用两种格式之一指定功能性软件需求：声明形式和用例形式。
Note that you can specify functional software requirements in one of two formats: declarative and use case.
WidgetCo的新体系结构包括两个方面：软件需求和硬件需求。
WidgetCo's new architecture has two sides: the software needs and the hardware needs.
设置一个以软件为中心的需求工具，为项目提供一幅软件需求的清晰图像。
Setup a software-centric requirements tool to give a clear picture of the software requirements for projects.
您在软件需求部分所下载的tagHandlers-0.9.jar
tagHandlers-0.9.jar from the location you downloaded it to in the Software requirements section
软件需求通常描述已经存在的或是未来的软件系统，并且应该与业务需求同步。
Software requirements are usually documented for existing or future software systems and should be in-sync with business requirements.
通过向更高层次的业务或者说用户需求来追踪软件需求，你可以确认它的价值。
By tracing a software requirements to higher-level business, or user requirements, you can ensure that it has value.
例如，软件需求规格说明书(SRS)工件是需求详细说明人负责的。
For example, the artifact Software Requirements Specification (SRS) is owned by the Requirements Specifier.
在Fairley的书中，“软件需求定义”一章的大部分是关于不同的说明方法。
A large portion of the chapter entitled "Software Requirements Definition" in Fairley's book is about different specification methods.
例如，你如果决定用用例来规约软件需求，你的指南就应该告诉你如何写出事件流程。
For example, if you decide to specify software requirements with use cases, then your guidelines should tell you how to write the flows of events.
让我们退回来再看看这样一些情节，它们将展示业务需求和软件需求之间的不同之处。
Let's step back and look at some scenarios, which show some differences between business requirements and software requirements.
将业务规则从软件需求中剥离出来是对于描述、分析和确认需求都很有好处的一项技术。
Dissecting business rules from software requirements is a good technique for depicting, analyzing, and validating requirements.
他最感兴趣的是软件开发最佳实践引导他开发用例概念，从而更好地识别和描述软件需求。
His interest in software development best practices led him to develop the concept of use cases as a way to better identify and specify software requirements.
正如我们前面看到的，需求类型可能包括业务需要、特性以及功能性和非功能性的软件需求。
As we saw earlier, requirement types might include business needs, features, and functional and non-functional software requirements.
同有关软件需求及与其关联的业务规则的讨论类似，业务规则也可以同特定的用例步骤相联系。
Similar to the discussion about software requirements and their association to business rules, business rules could be linked to a particular use-case step.
它有定义的检查点，是详细说明软件需求活动的结果，也是由需求详细说明人执行的。
It has checkpoints defined and is the result of the activity Detail the Software Requirements, also performed by the Requirements Specifier.
但是，从那些混杂在一起的陈述中分离出来的需求，需要被联结到软件需求中来建立上下文关系。
However, dissected requirements, which become granular statements, need to be linked to the software requirements to establish the context.
应用推荐