功能性的需求用使用用例的术语来描述。
Functional requirements are described in terms of use cases.
每一层反映了一组常见的功能和非功能性的需求。
Each tier reflects a common set of capabilities and nonfunctional requirements.
除了对灵活性和可扩展性的要求外，此方法还能满足一些功能性的需求。
Beyond the requirements for flexibility and scalability, there are also functional requirements that can be fulfilled with this approach.
电影剧本经过多次迭代，逐渐调整直到导演看来符合这些功能性的需求。
The movie script is fine-tuned through many iterations to match the director's vision of meeting these functional requirements.
软件系统中非常重要的非功能性的需求，也应该被确定和管理。
Nonfunctional requirements, which are often of great importance in a software system, are also identified and managed.
为了服务质量和非功能性的需求，必须监视和管理已经部署的服务。
The deployed services must be monitored and managed for quality of service and adherence to non-functional requirements.
基于功能性的需求，有许多不同的分部，例如并行运行的每一个项目都有一个分部。
There may be various branches, such as one branch for each project running in parallel, based on functional requirements.
这些非功能性的需求应该在早期就被具体地定义下来，我会在后面具体解释。
These should be detailed early on, as I will explain later in this chapter.
信息交换与一组功能性的和非功能性的需求相关，表现出获取、传递或使用信息所受的约束的特征。
Information exchange is associated with a set of functional and non-functional requirements characterizing the constraints under which information is captured, transferred, or used.
这意味着对于功能性的需求(关于系统必须实际上做什么的需求)，我们应当使用用例来描述系统的行为。
This means that for functional requirements (requirements regarding what the system must actually do), we apply use cases to describe the system's behavior.
这些需求包含展现的功能，以及对于给定的质量和限制因素，这些展现的功能是怎样实现的（例如，非功能性的需求）。
These requirements include what functionality is exhibited, and also how the functionality is exhibited given required qualities and constraints (i.e., non-functional requirements).
然而，记住此处的测试也应该包括非功能性需求是非常重要的，这些非功能性的需求有安装、备份和失败程序(failure procedure)。
However, it is important to remember that testing here should also encompass non-functional requirements, including installation, backup, and failure procedures.
这个上下文是由这个项目范围以及这个项目的功能性和非功能性需求所提供的。
The context is provided by the scope of the project and by the functional and non-functional requirements for that project.
功能性需求是程序为实现安全性目标所执行的功能。
Functional requirements are functions that the program performs to implement the security objectives.
这些后果可以根据业务需求(功能性和非功能性的)加以验证。
The outcomes can be validated against the business requirements, both functional and nonfunctional.
您可以通过提供应用程序并指定该应用程序的功能性和非功能性需求来构建一个虚拟应用程序模式。
You build a virtual application pattern by supplying your application and specifying both functional and non-functional requirements for that application.
在SOA分析和设计期间识别服务时，会同时收集功能性和非功能性需求，以便定义每个服务的服务水平协议。
As services are identified during SOA analysis and design, both functional and non-functional requirements are collected in order to define a service level agreement for each service.
业务过程设计：用面向服务的方式创建业务流程，分析功能性和非功能性需求。
Business process design: Create business processes in a service-oriented way, analyze their functional and nonfunctional requirements.
由于这种需求方法导致一种将团队成员置于他们所进行的工作种类的功能性“筒仓”中的企业结构，因此必须小心的进行处理。
This requirements method must be approached with caution as it typically leads to an organizational structure that places team members into functional "silos" based on the type of work that they do.
正如我们前面看到的，需求类型可能包括业务需要、特性以及功能性和非功能性的软件需求。
As we saw earlier, requirement types might include business needs, features, and functional and non-functional software requirements.
首个模型应该重点关注于核心的功能需求，而后来添加的附加用例则用于支持非功能性的方面。
The first-cut model should probably focus on the core functional requirements, with additional use cases added later to support the nonfunctional aspects.
通常在这里应该指出相关的(非功能性)需求作为依据。
Typically you should refer back to your (non-functional) requirements here.
XS40XMLSecurityGateway可以满足支持此模式的功能性和非功能性需求。
The XS40 XML Security Gateway meets the functional and non-functional requirements to support this pattern.
如图2所示的ScalingPolicy允许您为您自己的应用程序环境指定功能性和非功能性需求。
Policies like the Scaling Policy shown in Figure 2 allow you to specify functional and non-functional requirements for your application environment.
迁移到PODS4 并没有改变PODS 的功能性需求，但是pureXML 技术简化了元数据处理，有助于满足系统的响应时间和可伸缩性目标。
The migration to PODS4 did not change the PODS functional requirements, but pureXML processing simplified metadata processing while meeting the system's response time and scalability goals.
为什么非功能性，运营性的需求会成为一个问题？
Why nonfunctional, operational requirements can be a problem?
如果使用的是传统的(非soa的)方法，则设计需要处理功能性(如用例和业务流程)和非功能性(如服务质量，即QoS)需求。
As with traditional (non-SOA) approaches, the design needs to address both functional (such as use cases and business processes) and nonfunctional (such as quality of service, or QoS) requirements.
专注于功能性，安全性，性能上的需求百分比是多少？
What percentage of requirements are focused on capability vs. security vs. performance?
不适合放在用例中的需求（功能性和非功能性）应当在补充规约中进行详细描述。
The requirements (functional and non-functional) that do not fit appropriately within the use cases should be detailed in the Supplementary Specifications.
您学习了每种环境的优点、如何考虑使用功能性和非功能性需求之类的标准，以及如何应用模式。
You learned the strengths of each environment, and how to take criteria such as functional and non-functional requirements into consideration, as well as how to apply patterns.
应用推荐