NFRs change more frequently than functional requirements.
NFR比功能需求的变化频率高。
The SOA COE works with the business team to capture the NFRs from the customer.
SOACOE与业务团队合作从客户那里捕获NFR。
To this base IT requirement, the Operations staff can add their own "context" NFRS.
对于该基底IT需求，运营员工可以添加他们自己的“内容”nfrs。
Response time might be derived from the nonfunctional requirements (NFRs) specified for the functionality of the service.
响应时间可以通过为服务的功能指定的非功能需求(NonFunctional requirement,NFR)派生得到。
As stated earlier, it is important to understand the NFRs for a service, and maximum message size should be part of those NFRs.
如前所述，重要的是要理解服务的NFRs，最大消息大小应该是那些NFRs的一部分。
The SOA COE architects are responsible for defining interfaces, message flows, nonfunctional requirements (NFRs), and lower-level functional requirements.
SOACOE架构师负责定义接口、消息流和非功能需求(nonfunctional requirement,NFR)，以及低级功能需求。
Step 2, the logical deployment NFRs, registers mainly NFRs that originate from technology and architecture, including Development decisions during application design.
步骤2，逻辑性部署NFRs，注册了来自技术和结构的 NFRs，包括程序设计阶段的开发决策。
In this article, we concentrate on those NFRs that are directly related to the production environment of the new system and to the set of processes that support its operations.
在本文中，我们将会集中讨论那些与新系统的产品环境直接关联的NFRs，以及与系列进程相联系的NFRs，以支持其运营。
While testing NFRs is imperative for the successful adoption of SOA applications, remember that in the absence of specific quantified requirements (where possible) you can run into trouble.
虽然测试NFR是成功采用SOA应用程序所必不可少的步骤，但请记住，如果没有具体的量化要求(在可能的情况下)，则可能会遇到麻烦。
While testing NFRs is imperative for the successful adoption of SOA applications, remember that in the absence of specific quantified requirements (where possible) you can run into trouble.
虽然测试NFR是成功采用SOA应用程序所必不可少的步骤，但请记住，如果没有具体的量化要求(在可能的情况下)，则可能会遇到麻烦。
应用推荐