这篇文章集中讨论了后者：技术需求。
This article focuses on the latter: the technical requirements.
您的企业SOA的技术需求。
可追踪到业务需求的技术需求
您怎样为您的SOA项目获取技术需求？
How do you capture the technical requirements for your SOA initiative?
获取技术需求从不是一件很容易的事情。
企业SOA的技术需求。
这个需求既是技术需求，也是业务需求。
This requirement borders being a technical requirement and a business requirement.
此协议差别带来了应用程序和系统集成的技术需求。
This protocol disparity raises technology requirements for application and systems integration.
在一个soa例子中，获取技术需求变得更加困难。
In the case of SOA, capturing technical requirements becomes even more difficult.
约束以类似于业务规则和技术需求的方式进行文档记录。
Constraints are documented in a similar manner to business rules and technical requirements.
ESB并不需要任何这样的业务需求，仅仅需要技术需求。
ESBs don't need any of those annoying business requirements, only technology requirements.
其中首先讨论了在分析业务需求之前分析技术需求的原因。
It started with a debate about the reasons for examining technical requirements before business requirements.
当这些服务成熟以后，您就可以对您的soa定义全面的技术需求。
As these services mature, you can define the overall technical requirements for your SOA.
此需求既是业务需求，也是技术需求，必须认真加以分析。
This requirement borders between business and technical requirements, but you must get your head around it.
其中对之所以在业务需求前分析技术需求的原因进行了详细的说明。
You delved into the reasons for examining technical requirements before business requirements.
他们能帮助你评定技术需求和期望，并在我们的产品线中找到最适合的。
They can help assess what your technical needs are, what expectations you have, and find the best fit among our product line.
要想把主数据分发给其他系统，就必须满足许多不同的业务和技术需求。
The distribution of master data to other systems must fulfil a myriad of different business and technical requirements.
技术(Technical)范畴包括学习对象的技术需求和技术特征。
The technical category groups the technical requirements and technical characteristics of the learning object.
对于这5个业务情景的业务需求，下面的技术需求是通用的且可追踪的。
The following technical requirements were common and traceable to the business requirements of the five business scenarios.
首先，这不是什么新的东西，您应该总是紧盯商业需求，而不是技术需求。
First, and this is nothing new, you should always keep your eye firmly on business needs, not technology needs.
本系列的第一篇文章讨论了面向服务的体系结构(SOA)项目的技术需求。
The first article in this series discusses the technical requirements for Service-Oriented Architecture (SOA) projects.
其中还讨论了不同类型技术需求的细节以及在捕获这些需求时需要注意的各种问题。
You also explored the details of different types of technical requirements and the gotchas! You need to watch out for when capturing these requirements.
一项重要的技术需求是，SaaS应用程序可以在一个基础结构中承载多个承租者。
A key technical requirement is that an SaaS application can enable housing of multiple tenants within one infrastructure.
从明确技术需求到团队过程和工具培训的过程应在初始版本的开发中持续二到三个月。
The process — from specifying technology requirements to team process and tool training — should take from two to three months early in the initiative.
前一篇文章讨论了不同类型技术需求的细节以及在捕获这些需求时需要注意的各种问题。
The previous article explores the details of different types of technical requirements and the various gotchas! That you need to watch out for when capturing these requirements.
这两个术语经常用来描述各种业务目标和技术需求，从纯硬件可用目标到任务关键型目标。
These terms often describe a variety of business goals and technical requirements, from hardware-only availability targets to mission-critical targets.
本文集中讨论了SOA项目技术方面的内容，以及您怎样对这种项目的技术需求进行定义。
This article concentrates on the technical aspects of SOA projects and how you should define the technical requirements for such projects.
关于这种方法，精心描述你的自动化业务用例，让技术需求的技术团队通常更容易被接受。
The technical team that elaborates your to-be-automated business use cases into technical requirements is often even more receptive to this approach.
许多网上电脑商店过去主要靠打印出来的产口目录进行销售，上面清楚地写明了技术需求。
Many of the online computer stores used to sell exclusively through printed catalogs, addressing the technically astute.
许多网上电脑商店过去主要靠打印出来的产口目录进行销售，上面清楚地写明了技术需求。
Many of the online computer stores used to sell exclusively through printed catalogs, addressing the technically astute.
应用推荐