现在，服务已全部由一些提供者提供，我们已经准备好将这些提供者集合起来使用，实现最初的业务需求。
Now that the services are all provided by some provider, we are ready to use these providers in an assembly that fulfills the original business requirements.
由于系统没有集成，大多数企业缺乏有效地聚合数据的能力，因此必须实现许多代价昂贵的自定义代码来满足业务需求。
Because their systems are not integrated, most enterprises lack the ability to effectively aggregate data, and therefore, must implement lots of costly custom code to satisfy business requirements.
这些候选服务代表在实现后能够满足需求并支持业务流程的IT能力。
These candidate services represent IT capabilities which, when implemented, will meet the requirements and support the business process.
在实际的实现中，始终要选择可满足业务需求的最具限制性的过滤，从完全限定的DN开始，然后再从此返回。
In an actual implementation, you should always choose the most restrictive filter that meets the business requirement, starting with a fully-qualified DN and working back from there.
相反，着眼于那些只针对当前迭代或发布的业务需求和实现。
Instead, focus on the immediate business requirement and fulfill just that for your immediate iteration or release.
人们想要满足其业务需求的报告，因此着重于实现这些的功能。
People want reports which meet their business needs, so focus on providing the functionality that does that.
IT资源由IT过程来管理，以实现响应业务需求的目标。
IT resources are managed by the IT processes to achieve IT goals that respond to business requirements.
从业务需求到分析模型，再到实现代码的转换过程的可跟踪能力不足。
This transition from business requirements to analytic models to an implementable code isn't traceable enough.
本文描述了您将在后续部分中实现的组合业务流程的用例和需求。
This article described the use case and requirements of the composite business process that you'll implement in the subsequent parts.
可以通过识别为支持业务需求而定义的特定功能来实现这种分解，如图1所示。
This decomposition is accomplished through the identification of the specific functions that need to be defined to support business requirements, as shown in Figure 1.
实现灵活的体系结构，使之能够适应业务需求的变化。
Enabled flexible architecture that ADAPTS to changes in business needs.
这样，治理确保了业务需求推动了服务交付生命周期的所有方面，并且确保了实现仍旧与业务目标结合在一起。
In this way, governance ensures that business requirements drive all aspects of the service delivery lifecycle, and that the implementation remains constantly aligned with business objectives.
然后我们使用该业务过程来识别需要的业务功能，这些功能可以作为设计方案中能够满足业务需求的服务实现。
We then use this business process to help identify needed business capabilities that can be realized as services in a designed solution that meets the business requirements.
IT成本：非集成的企业中的不灵活性导致实现新业务需求的时间和成本呈指数上升。
It costs: the inflexibility in the non-integrated enterprise causes an exponential increase in time and cost to implement new business requirements.
大多数BPM工具被视为绘制流程图的工具或根据业务需求建模的工作流建模器，以生成一些类似代码的实现构件。
Most of the BPM tools are considered as either tools to draw a flowchart or a workflow modeler from business requirements, which generates some implementation artifacts like code.
它是能够授权IT方面的更改以实现业务需求增强的授权机构。
IT's an empowered body that can grant changes in IT for business requirement enhancements.
本系列的文章关注于怎样获取业务需求，构建能够满足这些需求的服务模型，创建和部署能够实现这些设计的方案。
This series of articles focuses on how to capture business requirements, build services models that fulfill them, and create and deploy solutions that realize the designs.
少数项目团队还遇到了处理系统的IT服务实现的业务需求更改的难题。
And few project teams have trouble handling change in business requirements to systematic realization of IT services.
通常，现有应用程序的操作包含了业务流程的各种需求，使其成为了设计或者实现更改的等价物。
Often the operation of existing applications has taken over the business process requirements to become the equivalent of design or implementation changes.
这显然只是个范例，在特定迭代中加入的功能往往要基于业务需求、优先级、实现的难易程度和其它因素。
Obviously this is just an example and the features you put into a specific iteration are based on business requirements, priority, ease of implementation, and other considerations.
您可以扩展或修改这些模板以满足特定的业务需求，从而减少实现时间和成本，并实现更简单的业务流程。
You can extend or modify these templates to meet specific business needs, thus reducing the time and cost to implement, and enabling simpler business processes.
域分解是通过源自业务组件设计的业务需求规范实现的。
Domain decomposition results from the specification of business requirements originating from the business component design.
大部分现有的实现方法包括创建针对明确的业务需求的解决方案所用的技术。
The majority of existing implementation methodologies include techniques for creating the solution to a well-defined business need.
您需要知道业务需求才能实现这一点，但是，对于时间框架内的这些需求，您了解业务团队吗？
You've asked for business requirements to get to this point, but were you clear with the business team on the time frame of those requirements?
已知现有系统的约束条件，只考虑纯粹的业务需求很可能产生不实际或不可能实现的服务定义。
Considering only pure business requirements is likely to result in service definitions that are impractical or impossible to implement, given the constraints of existing systems.
以实现为中心的方法包括对实现方法的重复增强，它基于技术需求，且在大部分情况下基于变化的业务需求。
The implementation-centric approach consists of the repeated enhancement of implementation artifacts based on technical requirements and, in many cases, on changing business requirements.
执行这些测试的质量工程（QE）团队，在验证应用软件实现客户需求或业务规则方面，扮演了一个支持客户的角色。
The quality engineering (QE) team that performs these tests acts primarily as a customer advocate in verifying the application's ability to fulfill customer needs or business imperatives.
精益治理可以由灵活的架构来实现，因为它们使开发团队对业务的变更的需求进行有效地反应。
Lean governance is enabled by flexible architectures because they enable development teams to react effectively to the changing needs of the business.
要实现业务示例的演变，我们需要添加对乘法和除法服务的需求。
To complete the evolution of the business example, let's add requirements for multiply and divide services.
可适应性——增加对业务用户提出的小型变更的实现来支持短期需求，同时仍然控制在强有力的IT管理范围内。
Adaptability - Increased enablement of small changes by Business users to support short term needs, whilst still controlled within strong it governance.
应用推荐