This article focuses on the latter: the technical requirements.
这篇文章集中讨论了后者：技术需求。
This article concentrates on the technical aspects of SOA projects and how you should define the technical requirements for such projects.
本文集中讨论了SOA项目技术方面的内容，以及您怎样对这种项目的技术需求进行定义。
It may in many cases also require you to compromise on some functional or technical requirements, such as platform support, performance, or footprint (size of the application).
在很多情况下它可能还需要你牺牲一些功能或技术需求，比如平台支持，性能，或覆盖区(应用程序的大小)。
The services map in Figure 7 shows a typical services and application inventory with some typical attributes gathered to document technical requirements for the integration.
图7中的服务地图显示了典型服务和应用程序库存，它具有为记录集成的技术需求而收集的一些典型属性。
You need to define two types of requirements at this stage: the requirements for your services and the technical requirements to support these services.
在这个阶段您需要确定两种类型的需求：您服务的需求以及支持这些服务的技术需求。
Tool selection would require us to do some early exploration into the customer's technical requirements, maintenance plan, and other needs.
在工具选择方面我们需要针对客户的技术需求、维护计划和其他的需要作一些早期的探索工作。
As these services mature, you can define the overall technical requirements for your SOA.
当这些服务成熟以后，您就可以对您的soa定义全面的技术需求。
This article is the second in a series that explores how IBM middleware capabilities can be integrated to address the technical requirements of the financial markets front office.
本文是一个系列文章的第二篇，该系列文章研究如何可以集成IBM中间件功能来解决金融市场前端办公室的技术需求。
In the traditional process, testers are forced to link together groups of technical requirements associated with higher-level user outcomes.
在传统的过程中，测试人员被迫将附有高水平用户结果的技术与需求团队连接起来。
The distribution of master data to other systems must fulfil a myriad of different business and technical requirements.
要想把主数据分发给其他系统，就必须满足许多不同的业务和技术需求。
The first article in this series discusses the technical requirements for Service-Oriented Architecture (SOA) projects.
本系列的第一篇文章讨论了面向服务的体系结构(SOA)项目的技术需求。
These terms often describe a variety of business goals and technical requirements, from hardware-only availability targets to mission-critical targets.
这两个术语经常用来描述各种业务目标和技术需求，从纯硬件可用目标到任务关键型目标。
It would have exposed us to excessive risk and would have been unfair to the customer, had we found out that their technical requirements could be satisfied for much less.
这将给我们带来过多的风险，并且也许对客户来说是不公平的，并且我们能够确定他们的技术需求将被满足吗。
In this three-part series, you explored the requirements process for the entire life cycle of your SOA project beginning with the technical requirements.
通过此包含三个部分的系列文章，您从技术需求开始，了解了SOA项目的整个生命周期的需求流程。
In the first article in this series you learned about determining technical requirements for your Service-Oriented Architecture (SOA) project.
在本系列的第一篇文章中，您已经了解了如何确定面向服务的体系结构(SOA)项目的技术需求。
Constraints are documented in a similar manner to business rules and technical requirements.
约束以类似于业务规则和技术需求的方式进行文档记录。
In this article, you focused less on learning about technical requirements for an initial SOA project and more on where to begin in the requirements gathering process.
在这篇文章中您很少关注对最初SOA项目的技术需求的学习，而更多关注的是从哪入手进行需求获取过程。
It started with a debate about the reasons for examining technical requirements before business requirements.
其中首先讨论了在分析业务需求之前分析技术需求的原因。
In the case of SOA, capturing technical requirements becomes even more difficult.
在一个soa例子中，获取技术需求变得更加困难。
The implementation-centric approach consists of the repeated enhancement of implementation artifacts based on technical requirements and, in many cases, on changing business requirements.
以实现为中心的方法包括对实现方法的重复增强，它基于技术需求，且在大部分情况下基于变化的业务需求。
You also explored the details of different types of technical requirements and the gotchas! You need to watch out for when capturing these requirements.
其中还讨论了不同类型技术需求的细节以及在捕获这些需求时需要注意的各种问题。
My customer and I agreed that it might be worthwhile to spend a day going through some technical requirements and build a formal language for an architecture that could realize those requirements.
我的客户与我都同意值得花上一天的时间去审阅某些技术需求，并为架构建立一门正式语言来体现这些需求。
This requirement borders between business and technical requirements, but you must get your head around it.
此需求既是业务需求，也是技术需求，必须认真加以分析。
How do you capture the technical requirements for your SOA initiative?
您怎样为您的SOA项目获取技术需求？
The technical team that elaborates your to-be-automated business use cases into technical requirements is often even more receptive to this approach.
关于这种方法，精心描述你的自动化业务用例，让技术需求的技术团队通常更容易被接受。
Capturing technical requirements is never an easy task.
获取技术需求从不是一件很容易的事情。
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.
前一篇文章讨论了不同类型技术需求的细节以及在捕获这些需求时需要注意的各种问题。
You delved into the reasons for examining technical requirements before business requirements.
其中对之所以在业务需求前分析技术需求的原因进行了详细的说明。
Technical requirements for your enterprise soa.
您的企业SOA的技术需求。
Technical requirements for your enterprise soa.
您的企业SOA的技术需求。
应用推荐